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.

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

Problem: curve keys getsockopt uninitialised read #1805

Merged
merged 1 commit into from
Feb 16, 2016

Conversation

bluca
Copy link
Member

@bluca bluca commented Feb 16, 2016

Solution: always initialised zmq::options_t class variables arrays to
avoid reading uninitialised data when CURVE is not yet configured and
a getsockopt ZMQ_CURVE_{SERVER | PUBLIC | SECRET]KEY is issued.

Solution: always initialised zmq::options_t class variables arrays to
avoid reading uninitialised data when CURVE is not yet configured and
a getsockopt ZMQ_CURVE_{SERVER | PUBLIC | SECRET]KEY is issued.
hintjens added a commit that referenced this pull request Feb 16, 2016
Problem: curve keys getsockopt uninitialised read
@hintjens hintjens merged commit df6876a into zeromq:master Feb 16, 2016
@hintjens
Copy link
Member

Does this risk an access violation? If so we should backport to 4.1.x stable.

@bluca bluca deleted the uninitialised_sockopt branch February 16, 2016 13:22
@bluca
Copy link
Member Author

bluca commented Feb 16, 2016

It's a corner case, given one has to use a curve sockopt when curve is not enabled, but I suppose better safe than sorry. I'll do the backport shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants