-
Notifications
You must be signed in to change notification settings - Fork 226
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
Zeromq 4.3.2 is not linked against libsodium on Windows #12031
Comments
Thanks for the report @chrisjbillington. I'll bring it up with the team. |
Confirmed:
|
Please test @chrisjbillington |
(in ten minutes once the upload finishes) |
Brilliant, can confirm I have fast crypto once more. Thanks very much! |
mingwandroid
added a commit
to AnacondaRecipes/aggregate
that referenced
this issue
Sep 16, 2020
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A problem previously resolved in #515 has regressed, and the Windows zeromq package no longer makes use of libsodium. This means zeromq CURVE encryption is very slow, and, according to the zeromq developers, should not be used in production as the fallback tweetnacl is not audited or maintained.
Copy-pasting my comment from issue #515, which it seems hasn't been seen (feel free to re-open that issue and close this one if appropriate):
This has regressed, I am once again seeing slow crypto in pyzmq as shipped by Anaconda in Windows. It looks like the zeromq package is no longer being built with libsodium on Windows as of 4.3.2. Here is a test script that prints dlls from the
<prefix>\Library
directory loaded into the process when pyzmq has been imported. It only prints libzmq.But after downgrading to zeromq 4.3.1 libsodium is listed as well:
click to see output of downgrade command
And this lines up with the observed crypto speed, being slower when lisodium is not loaded.
The text was updated successfully, but these errors were encountered: