This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update the TLS cipher string and provide configurability for TLS on outgoing federation #5550
Update the TLS cipher string and provide configurability for TLS on outgoing federation #5550
Changes from 5 commits
30c4f16
2b41967
5f1ab1b
3190043
fd71127
8fdc630
c50c06e
1872924
ed2dd72
e341403
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 I'd go with
federation_client_minimum_tls_version
, but w/eThere 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.
Why are we setting
NO_TLSv1
? I though the point was to optionally support it?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.
This is server, not client. Our server cipher string requires TLS 1.2 anyway to negotiate any of the ciphers, so this just makes the handshake a little simpler.
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.
Is this a bad security choice?
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.
AES128-CCM-8 is "not the best", AES128-CCM is just slow. They're not good ciphers that anything will ever pick, and advertising them makes our cipher string longer. (OpenSSL 1.1.1 started advertising it by default, so this update just makes it the same ciphers as when this originally landed)