enable zmq CURVE security - #553
Merged
Merged
Conversation
Member
Author
|
I'm a bit concerned that enabling CURVE security seems to often trigger SIGABRT. Not clear why, but unless this is a threadsafety violation, all such crashes are by definition libzmq bugs. |
Member
Author
|
Turns out CURVE cannot be used in applications that close contexts and/or issue keys while contexts are running: zeromq/libzmq#4241 |
minrk
force-pushed
the
curve-security
branch
2 times, most recently
from
September 8, 2021 07:37
014c2cc to
fe2f398
Compare
enabled by default if available uses CURVE to encrypt traffic / authenticate connections everywhere CURVE key is distributed in connection files just like the HMAC digest key is currently
libzmq has a critical bug where issuing keys while a zmq context might handle a message closes libsodium's handle on urandom, which can result in a crash. The bug mainly occurs when `zmq.curve_keypair()` is called or a context (any context) is closed. The bug cannot be fully avoided, but can at least make sure we don't issue keys before connecting sockets within a given application.
minrk
force-pushed
the
curve-security
branch
from
September 15, 2021 07:54
fe2f398 to
c3ad8a5
Compare
minrk
force-pushed
the
curve-security
branch
from
September 15, 2021 09:33
a1dea49 to
1e77c69
Compare
allows distributing credentials in a separate channel from connection files
minrk
force-pushed
the
curve-security
branch
from
September 15, 2021 09:34
1e77c69 to
b147dd5
Compare
This was referenced May 5, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Not enabled by default, due to zeromq/libzmq#4241, but with pyzmq 22.3 this should affect few users.
closes #552
uses CURVE to encrypt traffic / authenticate connections everywhere
CURVE key is distributed in connection files just like the HMAC digest key is currently
closes #268 by adding support for loading keys from the env
IPP_CURVE_{SECRET|PUBLIC|SERVER}KEY