#264 sr.ht and all services should support TLS 1.3 a month ago

Comment by ~crocmagnon on ~sircmpwn/sr.ht

For the record I asked: http://mailman.nginx.org/pipermail/nginx-devel/2020-September/013467.html

There are still blockers for them to enable it by default:

• http://mailman.nginx.org/pipermail/nginx/2018-November/057194.html
• http://mailman.nginx.org/pipermail/nginx/2020-June/059541.html

#264 sr.ht and all services should support TLS 1.3 a month ago

Comment by ~crocmagnon on ~sircmpwn/sr.ht

Well thanks for this very constructive discussion! :)

#264 sr.ht and all services should support TLS 1.3 a month ago

Comment by ~crocmagnon on ~sircmpwn/sr.ht

I won't fight tooth and nail about it but configuration files exist for a reason and offering a more recent version of a security protocol doesn't seem like a very difficult change, especially since it's just one config line.

#264 sr.ht and all services should support TLS 1.3 a month ago

Ticket created by ~crocmagnon on ~sircmpwn/sr.ht

Currently the maximum supported seems to be TLS 1.2.

The relevant config for nginx:

ssl_protocols TLSv1.2 TLSv1.3;

Since the certs are provided by Let's Encrypt: if the certificates installation in nginx is managed by certbot, you can edit the file at /etc/letsencrypt/options-ssl-nginx.conf (at least on debian-based distros).

#423 Error when sending mail with accents in the filename of an attachment 3 months ago

Comment by ~crocmagnon on ~sircmpwn/aerc2

Fix screenshot link from previous comment, sorry for the trouble.

#424 Support smartcards for PGP 3 months ago

feature added by ~crocmagnon on ~sircmpwn/aerc2

#424 Support smartcards for PGP 3 months ago

pgp added by ~crocmagnon on ~sircmpwn/aerc2

#424 Support smartcards for PGP 3 months ago

Ticket created by ~crocmagnon on ~sircmpwn/aerc2

This ticket has been created in response to #420. It's not a priority since PGP needs to be implemented and stable first.

aerc's own keyring should add support for smartcards. Importing the "reference" to a private key stored on a smartcard should be allowed.

#420 Use existing gpg keyring / support smarcards 3 months ago

Comment by ~crocmagnon on ~sircmpwn/aerc2

Thanks for your answer. Is smartcard support planned then? As it was my original issue I could reopen a ticket for this specific use case.

#420 Use existing gpg keyring / support smarcards 3 months ago

Comment by ~crocmagnon on ~sircmpwn/aerc2

IMO relying on existing and established tools such as gpg would be the best way to provide support for these features without requiring too much development effort (I guess) and without having to reinvent the wheel.

Also, users with existing keyrings would have a much nicer experience since it would allow them to use what they already have and not have a separate tool to manage when importing keys and trusting them.