-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[9740] ESMTPSender: dont't force TLSv1.0 by default #1225
Conversation
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.
Hi Martin!
Thanks so much for your contribution to Twisted.
The correct fix, here, if you want proper TLS security on twisted.mail
connections, would be to drop ClientContextFactory
entirely, and use optionsForClientTLS
. Dropping TLS 1.0 as a protocol version is good, but security-wise this change is almost meaningless, as ssl.ClientContextFactory
doesn't verify certificates, or hostnames, or really provide ''any'' proper security properties. (Separate to this change, it should be deprecated and removed from Twisted entirely.)
Dropping in optionsForClientTLS
here should not be much harder that just fixing the protocol version, and it would have the added benefit that it would use a whole slew of ''other'' better security attributes as well. Would you mind modifying your patch to do that?
Thanks!
@glyph thanks for quick review. I tried to replace the Anyway the TLS negotiation goes further now before rejecting my server's self-signed cert:laughing:. Oh well, probably a good time to replace it with LetsEncrypt one. |
Installed LE certificate & now matrix-synapse can send emails through postfix configured to only use TLS1.1 or higher with this patch. |
Thanks again for your contribution! I think the compatibility break is acceptable given the security needs here. Please do re-add the |
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 think @mmilata has addressed the review feedback, and this PR now looks OK.
@mmilata thank you for contributing to Twisted! |
@rodrigc: Can you release a new version with this fix? Several projects like Matrix wait you... @mmilata: Thanks! Ticket: matrix-org/synapse#6211 |
@Neustradamus I am not the release manager for Twisted, so cannot release a new version. @hawkowl is the release manager for Twisted. |
Dear @gjabell, @madpsy, @fadenb, @neilisfragile, @thereapman, @sbiberhofer, @henry-nicolas, @plamenh, @richvdh, @vmario89, @ChatCloud, @MisterAlainDev, @schwukas, @kaiyou, @babolivier, @mmilata, @clokep, @n3m3s1s, @Half-Shot, @exarkun, @anoadragon453: A good news, there are some "20.11.0" test-builds here: Time to test :) cc: @glyph. |
@Neustradamus you've already been asked not to mention the entire world over at matrix-org/synapse#6211. If people are interested they will follow the issue themselves. Don't be obnoxious. |
Good news the 21.02.0 RC1 is out! |
Good news, the 21.02.0 stable version is out!
Thanks a lot to @mmilata for this very important contribution and @rodrigc, @glyph and @twisted (Twisted Matrix Labs) team. |
Hello, I've also been bitten by matrix-org/synapse#6211 and would like to see if the fix is acceptable for inclusion in Twisted.
Contributor Checklist:
review
to the keywords field in Trac, and putting a link to this PR in the comment; it shows up in https://twisted.reviews/ now.