-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Require TLS 1.3 on client-facing ports #454
base: main
Are you sure you want to change the base?
Conversation
I tested with -tls1_2 option of openssl s_client that TLS 1.2 connections are no longer possible on any ports except port 25. Port 25 requires at least TLS 1.2 for encrypted connections.
I think "client-facing" means here Delta <-> Chatmail server (submission and imap ports)
and not MTA SMTP (port 25) server-to-server connections.
…On Mon, Nov 11, 2024 at 17:58 -0800, feld wrote:
I'm not up to speed on how widespread TLSv3 is for SMTP right now. Could this break the ability to send messages to other mail servers that don't support TLSv3?
--
Reply to this email directly or view it on GitHub:
#454 (comment)
You are receiving this because you are subscribed to this thread.
Message ID: ***@***.***>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit hesitant to approve this; some people with outdated desktop clients might have followed our instructions in https://delta.chat/en/2023-12-13-chatmail to setup a nine account. Yes, it's an unlikely scenario, but for them it would break.
And I don't see why it's necessary? Wouldn't any more recent official client use TLSv1.3 anyway? No need to force it server-side.
We do not support non-delta chat clients and any recent client supports TLS 1.3. It has existed for more than 5 years.
It makes development easier because I don't have to check if openssl-s_client or python IMAP library or core has by chance decided to connect using TLS 1.2. Security-wise this avoids downgrade attacks. TLS 1.3 downgrade protection is a hack to make it compatible with TLS 1.2 and by the time it detects downgrade it has already finished TLS 1.2 handshake, exposing server TLS certificate to middleboxes, so it's not prefect. Not having TLS 1.2 on the server makes it impossible to even start connecting with TLS 1.2. |
Let's postpone this until we make Delta Chat releases that use Rustls to connect to chatmail servers. Otherwise Delta Chat on Windows or macOS may not support TLS 1.3. Unlikely because macOS forces users to upgrade all the time and minimum supported version is Windows 10 due to Electron requirements. |
I tested with -tls1_2 option
of openssl s_client
that TLS 1.2 connections
are no longer possible
on any ports except port 25.
Port 25 requires at least TLS 1.2
for encrypted connections.