From: Markus Hennecke <markus-hennecke@markus-hennecke.de>
Subject: Re: mcabber: TLS does not work, libmouth update crashes
To: ports@openbsd.org
Date: Wed, 3 Jan 2024 10:03:53 +0100

Am 03.01.2024 um 00:51 schrieb Klemens Nanni:
> Anyone successfully using mcabber?
> Plain -current without config fails to connect via TLS:
> 
> 	$ mcabber
> 	/set jid = user@example.com
> 	/set server = example.com
> 	/set password = secret
> 	/connect
> 	[00:41:16] No configuration file has been found.
> 	[00:41:41] Connecting to server: pimux.de
> 	[00:41:41]  with resource mcabber.ccd21665
> 	[00:41:42] Disconnected, reason: 3->'LM_DISCONNECT_REASON_ERROR'
> [interleaved stderr]
> 	** (process:70988): WARNING **: 00:42:51.509: SSL_connect(): -1 / SSL_ERROR_SSL
> 	** (process:70988): WARNING **: 00:42:51.509:    error:1404E0BF:SSL routines:ST_BEFORE_CONNECT:no protocols available
> 
> '/set tls = 1' (default) makes no difference.
> 
> Updating outdated(/unmaintained/dead) loudmouth to 1.5.4 and rebuilding
> mcabber only causes various different *-after-free errors, this is my
> minimal reproducer

Can you retry without any patches for loudmouth 1.5.4? The port that is 
sitting in my tree looks the same Makefile wise, but I have an empty/no 
patches directory. That version builds on arm64 and connects just fine 
to my server offering TLSv1.3. I can recheck on amd64 later.

But AFAIR that build of loudmouth-1.5.4 was breaking the freetalk port 
that crashed during connect the last time I checked.

Kind regards
Markus