Just closing the loop here -- this appears to no longer be an issue with v1.5 in Anaconda. -Robin
Sent from my iPhone > On Aug 23, 2016, at 8:04 AM, Paul Kehrer <paul.l.keh...@gmail.com> wrote: > > This is likely to be something related to anaconda, but I'm not sure how to > go about debugging exactly why you're seeing this occur. It *looks* like it's > attempting to load an old _openssl.so with a new cryptography. > > -Paul > >> On August 23, 2016 at 12:58:20 PM, Robin Fishbein via Cryptography-dev >> (cryptography-dev@python.org) wrote: >> >> Hello, >> >> >> I imagine this may have a trivial explanation, or perhaps indicate some >> quirk on my machine, but it looks as though some desired functionality isn’t >> available on my machine with version 1.4. I wanted to share this in case it >> indicates some wider issue of interest, and helps me learn a little about >> how cryptography works under the hood. >> >> >> >> Windows 7, 64-bit, Python 3.5.1, and I believe OpenSSL 1.0.2. I use paramiko >> for SFTP, and when updating paramiko (on a whim) to 2.0.2 with Anaconda, it >> had me update cryptography as well, to version 1.4, or maybe it was 1.3 at >> first — either one experiences the issue. When attempting an SSH connect, I >> get a traceback ending with this: >> >> >> >> File >> "C:\Users\...\AppData\Local\Continuum\Anaconda3\lib\site-packages\cryptography\hazmat\bindings\openssl\binding.py", >> line 73, in wrapper >> >> if lib.Cryptography_STATIC_CALLBACKS: >> >> >> >> AttributeError: cffi library '_openssl' has no function, constant or global >> variable named 'Cryptography_STATIC_CALLBACKS' >> >> >> >> When I manually carry out some of the imports in the source... >> >> from cryptography.hazmat.bindings._openssl import ffi, lib >> >> ...and then look at what auto-complete shows for lib, I don’t see >> Cryptography_STATIC_CALLBACKS, which is consistent with the AttributeError. >> I don’t yet understand where to look for the source underneath the >> bootstrapped _openssl.*.pyd file. >> >> >> >> The SSH connection and all subsequent functionality work fine with the >> latest versions of paramiko and cffi as long as I revert cryptography to >> 1.0.2. >> >> >> >> -Robin Fishbein >> >> >> >> _______________________________________________ >> Cryptography-dev mailing list >> Cryptography-dev@python.org >> https://mail.python.org/mailman/listinfo/cryptography-dev > _______________________________________________ > Cryptography-dev mailing list > Cryptography-dev@python.org > https://mail.python.org/mailman/listinfo/cryptography-dev
_______________________________________________ Cryptography-dev mailing list Cryptography-dev@python.org https://mail.python.org/mailman/listinfo/cryptography-dev
