Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Wrong alert returned when client doesn't provide "signature_algorithms" #100

Open
kriskwiatkowski opened this issue Jun 25, 2018 · 0 comments
Open

Wrong alert returned when client doesn't provide "signature_algorithms" #100

kriskwiatkowski opened this issue Jun 25, 2018 · 0 comments
Labels
bug open for community contribution

Comments

@kriskwiatkowski
Copy link
Contributor

Draft of TLS 1.3 says in 4.2.3:

If a server is authenticating via a
   certificate and the client has not sent a "signature_algorithms"
   extension, then the server MUST abort the handshake with a
   "missing_extension" alert (see Section 9.2).

Currently code doesn't send this code as "missing_extension" alert is not even on a list of alerts
@kriskwiatkowski kriskwiatkowski changed the title Wrong return code when client doesn't send signature_algorithms Wrong alert returned when client doesn't provide "signature_algorithms" Jun 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug open for community contribution
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kriskwiatkowski