Replace unmaintained PyCrypto dependancy #19
Comments
|
I am all for rebasing pysnmp onto the cryptography! If you would you be able to come up with a PR, that would be awesome! ;-) |
|
Switched to PyCryptodome since bd01807. Thank you for the heads up! |
vincentbernat
pushed a commit
to vincentbernat/pysnmp
that referenced
this issue
Dec 3, 2023
Commit 67563a1 introduced a bug while converting legacy asyncio API to new "async def" style. Previous methods where NOT decorated with @asyncio.coroutine and returned a Future object being awaitable. Updated code still returns a Future object but adds async keyword to function definition leading to awaitable function returning awaitable Future. That breaks existing API.
vincentbernat
pushed a commit
to vincentbernat/pysnmp
that referenced
this issue
Dec 3, 2023
Fix asyncio hlapi double awaitable returns (Fix etingof#19)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The PyCrypto project is no longer maintained: pycrypto/pycrypto#173
There is also at least one known exploitable vulnerability: pycrypto/pycrypto#176
Alternatives:
cryptography- the official Python Cryptographic Authority packagepycryptodome- a maintained fork of PyCryptoAnother benefit of this move is it makes it easier for Windows users to install because both of these alternatives host official binary wheels on PyPI.
The text was updated successfully, but these errors were encountered: