Closed ecrsecurity closed 5 years ago
This is suspicious. Is is possible that you have some other pyasn1 version installed which is not visible to pip and dpkg?
One way to track that down would be to run a simple script (which fails) giving -v
option to your Python interpreter along the way (to see which modules it actually imports).
python -v your-failing-script.py 2>&1 | grep pyasn1
Good call. I found an old pyasn1 .0.1.9 in my dist-packages directory, wiped it, and problem solved. Thanks!
This is suspicious. Is is possible that you have some other pyasn1 version installed which is not visible to pip and dpkg?
One way to track that down would be to run a simple script that fails that way giving
-v
option to your Python interpreter (to see which modules it actually imports).python -v your-failing-script.py 2>&1 | grep pyasn1
Awesome!
Any python library I attempt to use which imports pysnmp gives the same error.
Yes, I have read https://github.com/etingof/pysnmp/issues/69 and several other similar bug reports in projects which use pysnmp all of which point to updating pyasn1. However I have already updated pyasn1, and the solution of removing the OS packaged version is not an option for me because I have other packages which require python-asn1 as a dependency.
I have some packages installed by my package manager also on Kali (Debian) Linux
Other sources on the web claim that this problem is caused by pyasn1 version < 0.2.3 but even the OS package is newer than that. Is this an error from out of date pyasn1? If so, what is the minimum required version?