Remove restriction on signature algorithm used in the server and client certificates #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -2,7 +2,7 @@ | |||
| <?xml-stylesheet type='text/xsl' href='./rfc2629.xslt' ?> | |||
|
|
|||
| <?rfc compact="yes" ?> | |||
| <?rfc sortrefs="yes" ?> | |||
| <?rfc sortrefs="syes" ?> | |||
There was a problem hiding this comment.
Looks like you made a typo "syes" vs "yes" here.
There was a problem hiding this comment.
Right. Fixed this. Thanks.
yoavnir
added a commit
that referenced
this pull request
Nov 4, 2015
…ificate-signatures Remove restriction on signature algorithm used in the server and client certificates
yoavnir
deleted the
yoavnir-remove-restrictions-on-certificate-signatures
branch
yoavnir
added a commit
that referenced
this pull request
Nov 4, 2015
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
TLS 1.1 and earlier required the signature algorithm in the certificate to match that of the public key. TLS 1.2 removed this restriction. Since RFC 4492 predated TLS 1.2 it reflected the same restriction. Here we remove it.