[profanity] libmesode functionality in Profanity

Stefan stefan at debxwoody.de
Mon Jun 15 20:48:52 CEST 2020

Am Montag, den 15.06.2020 um 00:00:07 +0300 schrieb Dmitry Podgorny:
> First, libstrophe continues working based on connection TLS flags (disable,
> mandatory, trust, etc). Then, on cert verification failure, connection
> disconnects, but with error code that indicates TLS failure. Notice that
> libstrophe has the same behaviour now, but error code needs to be unified.
> Finally, new function will be provided to retrieve the certificate from
> connection, so application will be able to display it.

I like this. It would be nice to have something like this:

> For Profanity it will look like this: when connection is disconnected due to
> cert failure, Profanity will show a help about danger and that user can use the
> "trust" flag at their own risk. The flag can be stored in the account
> configuration as well.

+1 - I think there is already a "tls.policy" which can be used by the
account settings. 

Mit freundlichen Grüßen,
Diese E-Mail wurde mit GnuPG digital signiert:
Fingerabdruck: A602 F768 93F1 38B4 A8EF  DDD5 C2DC 916F 3575 1C24 
Instant Messaging via Extensible Messaging and Presence Protocol (XMPP)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.notraces.net/pipermail/profanity/attachments/20200615/b7a24c41/attachment.sig>

More information about the profanity mailing list