-
Notifications
You must be signed in to change notification settings - Fork 431
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
Remove tls.server.supported_ciphers field #662
Conversation
Unlike the client, the server can't provide a list of it's supported ciphers in its hello message.
@webmat Was this already released? |
@ruflin Yes it was. Since it's a field that doesn't make sense, I propose we release ECS 1.3.1 with only this removal in it. @dcode or @dainperkins you guys agree this field doesn't make sense, right? |
@ruflin To clarify. During the exchange, the client says which ciphers it supports -- captured at The server picks which one to chose, and the selected cipher should be captured in At no point are there server side "supported ciphers" we can capture. I think this was a copy/pasta mistake ;-) |
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.
LGTM. Thanks for the quick fix @adriansr!
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.
LGTM
Unlike the client, the server doesn't provide a list of supported ciphers in its hello message.
Unlike the client, the server doesn't provide a list of supported ciphers in its hello message.
Unlike the client, the server doesn't provide a list of supported ciphers in its hello message.
Unlike the client, the server doesn't provide a list of supported ciphers in its hello message.