-
Notifications
You must be signed in to change notification settings - Fork 2
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
Fixs1.1 rc1 merge cipher list into main #1
base: main
Are you sure you want to change the base?
Conversation
Initial version of CipherList as extracted from V1.0 specification
CBC and SHA1 are deprecated for TLS1.2 and above. Also added revision table to log key updates
@nhorlock you are ahead of the game! We do not have a markdown version of FIXS yet. The first one will be v1.1 RC1. I will leave out the cipher list in order to then merge your request into the main branch when there is a markdown version for the v1.1 RC1 spec. |
No problem, this can be a standalone file without the MD but hopefully we
can move to an MD form of the RC1 after the meeting this week
…On Mon, 15 Feb 2021 at 14:45, Hanno Klein ***@***.***> wrote:
@nhorlock <https://github.com/nhorlock> you are ahead of the game! We do
not have a markdown version of FIXS yet. The first one will be v1.1 RC1. I
will leave out the cipher list in order to then merge your request into the
main branch when there is a markdown version for the v1.1 RC1 spec.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATWGASRCQIZGAR7XHMN7G3S7EXRHANCNFSM4XUWGHYQ>
.
|
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.
Please change the pull request to apply to RC2 and not RC1. Any change to an RC needs to be made to the next RC version.
| Version | Note | ||
|---------|------ | ||
| Initial | First commit, replicates FIXS V1.0 text | ||
| 2021.1 | Updated to remove CBC and SHA1 as these deprecated for use with TLS1.2 and above. |
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.
| 2021.1 | Updated to remove CBC and SHA1 as these deprecated for use with TLS1.2 and above. | |
| 2021.1 | Updated to remove CBC and SHA1 as these are deprecated for use with TLS1.2 and above. |
|
||
### Authentication | ||
#### TLS Certificate Authentication | ||
The following cipher suite list when using certificates for authentication. This includes using certificates in Simple TLS in conjunction with FIXA. The list ensures Forward Secrecy, avoids deprecated ciphers and should achieve good performance. The cipher suites are specified in our order of preference, starting with the most preferred cipher suite. |
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.
The following cipher suite list when using certificates for authentication.
I am sure there is something missing between "list" and "when". Maybe "should be used" or "should be considered" or "is recommended"?
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | ||
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 | ||
``` | ||
This list matches what is recommended as best practice from SSL Labs currently (November 2016), except we have given preference to performance of the TLS Record Protocol rather than the TLS Handshake Protocol's performance. The list should be used in conjunction with Session Caching. |
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.
Maybe omit the word "currently" in conjunction with November 2016. :)
``` | ||
This list matches what is recommended as best practice from SSL Labs currently (November 2016), except we have given preference to performance of the TLS Record Protocol rather than the TLS Handshake Protocol's performance. The list should be used in conjunction with Session Caching. | ||
|
||
The list details ECDSA certificate cipher suites followed by RSA certificate ones. It is possible to support both an ECDSA certificate and a RSA certificate at an end point, but only one certificate can be used at a time. In practice, only one kind of certificate is needed. Thus, if you are using an RSA certificate, the ECDSA cipher suites will be ignored so they can be omitted. Likewise, the RSA cipher suites will be ignored and can be omitted for an ECDSA certificate. |
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.
The list details ECDSA certificate cipher suites followed by RSA certificate ones. It is possible to support both an ECDSA certificate and a RSA certificate at an end point, but only one certificate can be used at a time. In practice, only one kind of certificate is needed. Thus, if you are using an RSA certificate, the ECDSA cipher suites will be ignored so they can be omitted. Likewise, the RSA cipher suites will be ignored and can be omitted for an ECDSA certificate. | |
The list details ECDSA certificate cipher suites followed by RSA certificate ones. It is possible to support both an ECDSA certificate and an RSA certificate at an end point, but only one certificate can be used at a time. In practice, only one kind of certificate is needed. Thus, if you are using an RSA certificate, the ECDSA cipher suites will be ignored so they can be omitted. Likewise, the RSA cipher suites will be ignored and can be omitted for an ECDSA certificate. |
This is the initial version plus first revision of the cipherlist as extracted from the FIXS specification.
This contains the externalised cipher list and has been updated to remove ciphers that have been deprecated since it was first created (CBC and SHA1)
It does not add new ciphers listed on IANA,