FS#76475 : [profanity][libstrophe] Stop working after openssl upgrade

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#76475 - [profanity][libstrophe] Stop working after openssl upgrade

Attached to Project: Community Packages
Opened by Obs (obspm) - Monday, 07 November 2022, 16:53 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:04 GMT

Task Type	Bug Report
Category	Packages
Status	Closed
Assigned To	Levente Polyak (anthraxx) freswa (frederik)
Architecture	All
Severity	Medium
Priority	Normal
Reported Version
Due in Version	Undecided
Due Date	Undecided
Percent Complete
Votes	1 Florent (misaflo) (2022-11-24)
Private	No

Details

Description:

After upgrade openssl, profanity stop working. Unable to connect to the server (who don't have any modification). Inside the log of profanity I can see

Additional info:
2022-11-07T16:39:07.465524+01: xmpp: DBG: sock_connect() to jabber.********:5222 returned 7
2022-11-07T16:39:07.465606+01: xmpp: DBG: Attempting to connect to jabber.********
2022-11-07T16:39:07.474330+01: xmpp: DBG: connection successful
2022-11-07T16:39:07.474841+01: conn: DBG: SENT: <?xml version="1.0"?><stream:stream to="********" xml:lang="en" version="1.0" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/stre
ams">
2022-11-07T16:39:07.584559+01: xmpp: DBG: RECV: <stream:stream from="jabber.********" id="9m7c3wbmff" lang="en" version="1.0">
2022-11-07T16:39:07.595130+01: xmpp: DBG: RECV: <features xmlns="http://etherx.jabber.org/streams"><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/><mechanisms xmlns="urn:ietf:params:xml:ns
:xmpp-sasl"><mechanism>PLAIN</mechanism></mechanisms><compression xmlns="http://jabber.org/features/compress"><method>zlib</method></compression><ver xmlns="urn:xmpp:features:rosterver"/><c h
ash="sha-1" xmlns="http://jabber.org/protocol/caps" ver="xYYpwaf5xaWLtTrszNhdKl4ghd0=" node="https://www.igniterealtime.org/projects/openfire/"/></features>
2022-11-07T16:39:07.624510+01: conn: DBG: SENT: <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
2022-11-07T16:39:07.653474+01: xmpp: DBG: RECV: <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
2022-11-07T16:39:07.653557+01: xmpp: DBG: handle proceedtls called for proceed
2022-11-07T16:39:07.653573+01: xmpp: DBG: proceeding with TLS
2022-11-07T16:39:07.699287+01: tls: DBG: Certificate verification passed
2022-11-07T16:39:07.699365+01: tls: DBG: Certificate was not presented by peer
2022-11-07T16:39:07.699376+01: tls: DBG: error=SSL_ERROR_SSL(1) errno=0 lasterror=0
2022-11-07T16:39:07.699389+01: tls: DBG: error:0A000126:SSL routines::unexpected eof while reading
2022-11-07T16:39:07.700409+01: conn: DBG: Couldn't start TLS! error -3 tls_error 1
2022-11-07T16:39:07.710891+01: xmpp: DBG: Send error occurred, disconnecting.
2022-11-07T16:39:07.710949+01: xmpp: DBG: Closing socket.
2022-11-07T16:39:07.710991+01: prof: DBG: Connection handler: XMPP_CONN_DISCONNECT
2022-11-07T16:39:07.711005+01: prof: DBG: Connection handler: Login failed
2022-11-07T16:39:07.711017+01: prof: DBG: Connection handler: No reconnect timer
2022-11-07T16:39:07.711090+01: prof: INF: Login failed
2022-11-07T17:38:16.596005+01: prof: DBG: Input received: /quit
2022-11-07T17:38:16.596077+01: prof: INF: Profanity is shutting down...

In the user interface I got a “login failed”
* config and/or log files etc.

The config of profanity doesn't change. The configuration/version/etc. of the server doesn't change either.

Steps to reproduce:

Just have to launch profanity.

This task depends upon

Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:04 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/profanity/issues/1

Comments (7)
Related Tasks (0/0)

Comment by Obs (obspm) - Monday, 07 November 2022, 16:55 GMT

S*it....forget to add :

Version of packages:
[root@io ~][linux]$ pacman -Q|grep profan
profanity 1:0.13.1-1
[root@io ~][linux]$ pacman -Q|grep openssl
openssl 3.0.7-2

All packages are up2date.

Comment by loqs (loqs) - Monday, 07 November 2022, 18:07 GMT

Please try rebuilding libstrophe with the attached patch applied and see if the issue is still present or changes the error message.
If this appears to solve the issue it needs to go upstream to libstrophe for verification.

test.patch (0.5 KiB)

Comment by Obs (obspm) - Monday, 07 November 2022, 19:44 GMT

Well....I'll try but absolutly no guarantee....I'm not a dev and never compile myself any package (not talking library can brake lot of thing).

I'll keep you inform

Comment by loqs (loqs) - Monday, 07 November 2022, 20:14 GMT

bsdtar -xf libstrophe-1\:0.12.2-2.src.tar.gz
cd libstrophe/
makepkg -rsi

libstrophe-1:0.12.2-2.src.tar... (1.7 KiB)

Comment by Obs (obspm) - Monday, 07 November 2022, 21:22 GMT

Thanks.

So no after compiling with AUR files it's still not working with almost the same error :

2022-11-07T22:14:23.306501+01: conn: DBG: SENT: <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
2022-11-07T22:14:23.327180+01: xmpp: DBG: RECV: <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
2022-11-07T22:14:23.327239+01: xmpp: DBG: handle proceedtls called for proceed
2022-11-07T22:14:23.327253+01: xmpp: DBG: proceeding with TLS
2022-11-07T22:14:23.378408+01: tls: DBG: Certificate verification passed
2022-11-07T22:14:23.378449+01: tls: DBG: Certificate was not presented by peer
2022-11-07T22:14:23.378457+01: tls: DBG: error=SSL_ERROR_ZERO_RETURN(6) errno=0 lasterror=0
2022-11-07T22:14:23.379272+01: conn: DBG: Couldn't start TLS! error -3 tls_error 6
2022-11-07T22:14:23.389674+01: conn: DBG: SENT: </stream:stream>
2022-11-07T22:14:23.389732+01: xmpp: DBG: Send error occurred, disconnecting.
2022-11-07T22:14:23.389747+01: xmpp: DBG: Closing socket.
2022-11-07T22:14:23.389787+01: prof: DBG: Connection handler: XMPP_CONN_DISCONNECT
2022-11-07T22:14:23.389800+01: prof: DBG: Connection handler: Login failed
2022-11-07T22:14:23.389812+01: prof: DBG: Connection handler: No reconnect timer
2022-11-07T22:14:23.389907+01: prof: INF: Login failed

So it's «missing» the line «error:0A000126:SSL routines::unexpected eof while reading» and the tls error number change from 1 to 6.

I check (in case I miss something) the lib build inside the directory got same md5sum as the lib in the /usr/lib

thanks

Comment by loqs (loqs) - Monday, 07 November 2022, 21:37 GMT

Restore the packaged libstrophe.
# pacman -S libstrophe
Extract the attached openssl.cnf which has the legacy provider enabled then from the same directory run profanity using that openssl.cnf with
OPENSSL_CONF="$PWD/openssl.cnf" profanity

openssl.cnf (12 KiB)

Comment by Obs (obspm) - Monday, 07 November 2022, 22:01 GMT

Hi.

Still no joy.

[me@io ~][linux]$ export OPENSSL_CONF=/home/me/openssl.cnf
[me@io ~][linux]$ profanity
[me@io ~][linux]$ ls -l /home/me/openssl.cnf
-rw-r--r-- 1 me me 12339 7 nov. 22:56 /home/me/openssl.cnf
[me@io ~][linux]$

and same error as previous (first post)

Thanks

	Tasks related to this task (0)

Duplicate tasks of this task (0)

Arch Linux

Community Packages

FS#76475 - [profanity][libstrophe] Stop working after openssl upgrade

Details

Loading...