SASL Support for External Certiticates

[a-diker]

Currently the issue is that the application thinks that SASL Support is SASL Username + password,
but now in days SASL uses Exerntal certificates for example tor, can this feature be added or I am glad to help!

[jhthorsen]

You can set "SASL authentication mechanism" to "External" with a fingerprint. Convos automatically generates the certificate for you, but you can choose to override it (manually) if you like.

This is not what you want?

[a-diker]

How do you do that? Cannot find any guide on doing this seems like it's unsupported to generate the certificate?

…

On Tue., Jun. 14, 2022, 18:16 Jan Henning Thorsen, ***@***.***> wrote: You can set "SASL authentication mechanism" to "External" with a fingerprint. Convos automatically generates the certificate for you, but you can choose to override it (manually) if you like. This is not what you want? — Reply to this email directly, view it on GitHub <#752 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZUBPBML4WZ7KMQ33IPOJYLVPEADNANCNFSM5YXXIDTQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[a-diker]

An example is you cannot use tor with SASL plain for Brite force attacks the server require you use an cert but that cannot be added You can enter a username and password [PLAIN] butnusing a certificate is currently not supported by Limechat

…

On Sun., Jun. 19, 2022, 07:51 Alex Diker, ***@***.***> wrote: How do you do that? Cannot find any guide on doing this seems like it's unsupported to generate the certificate? On Tue., Jun. 14, 2022, 18:16 Jan Henning Thorsen, < ***@***.***> wrote: > You can set "SASL authentication mechanism" to "External" with a > fingerprint. Convos automatically generates the certificate for you, but > you can choose to override it (manually) if you like. > > This is not what you want? > > — > Reply to this email directly, view it on GitHub > <#752 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AZUBPBML4WZ7KMQ33IPOJYLVPEADNANCNFSM5YXXIDTQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[jhthorsen]

https://convos.chat/blog/2021/12/23/connecting-to-libera-from-digitalocean

[a-diker]

That's not using the client that's using a separate client on a web app

…

On Sun., Jun. 19, 2022, 07:57 Jan Henning Thorsen, ***@***.***> wrote: https://convos.chat/blog/2021/12/23/connecting-to-libera-from-digitalocean — Reply to this email directly, view it on GitHub <#752 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZUBPBKI4P4HVALQUGVRCVDVP4DMJANCNFSM5YXXIDTQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jhthorsen]

I don't understand "That's not using the client that's using a separate client on a web app".

[jhthorsen]

Looks like this issue has gone stale.

[TehPeGaSuS]

I could be wrong, but I believe they're asking for a way to upload/use an already generated certificate.
So it could be re-used every time without generating new certs for each connection.
That way if we need to reinstall Convos, etc, logins won't break because new certificates were generated.

[jhthorsen]

The certificates are stored in $CONVOS_HOME, so they can be replaced. Just not from the web gui.