-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Reset session in/out pointers in mbedtls_ssl_session_reset() #1942
Reset session in/out pointers in mbedtls_ssl_session_reset() #1942
Conversation
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.
Thanks for catching an fixing this. I'll add a test in #1939 by reconnecting, which will exercise session_reset()
followed by get_record_expansion()
.
ChangeLog
Outdated
@@ -10,6 +10,8 @@ Bugfix | |||
* Add ecc extensions only if an ecc based ciphersuite is used. | |||
This improves compliance to RFC 4492, and as a result, solves | |||
interoperability issues with BouncyCastle. Raised by milenamil in #1157. | |||
* Fix potential segmentation fault in mbedtls_ssl_get_max_frag_len() |
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.
Why would there be a segmentation fault? Please be more specific. Null pointer dereference?
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.
@gilles-peskine-arm Ok, it would be more precise to say that it's a potential use-after-free. Shall I change the wording accordingly?
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.
Now that Gilles mentions it, I'm thinking perhaps we should always avoid the wording "segmentation fault" regardless of the cause, as it's a platform-specific behaviour.
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.
@gilles-peskine-arm @mpg Changed.
@hanno-arm Note: #1939 is now based on this. In order to avoid unnecessary complexity, please refrain from rewriting history in this PR from now on. |
Fixes #1941.