bpo-44309: Add support for yescrypt in crypt.#26526
bpo-44309: Add support for yescrypt in crypt.#26526besser82 wants to merge 3 commits intopython:mainfrom
Conversation
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). Recognized GitHub usernameWe couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames: This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
be75e6d to
e70e534
Compare
|
I left a comment on bpo that explains why I'm against this feature. |
a9ab912 to
baefd10
Compare
https://bugs.python.org/issue44309 Signed-off-by: Björn Esser <[email protected]>
Co-authored-by: Serhiy Storchaka <[email protected]>
baefd10 to
72e0009
Compare
|
@besser82, many thanks for your PR. Unfortunately, the I hope that this does not dissuade you from contributing to CPython in the future 🙂 |
Proposed PR adds support for a new method in the crypt module:
yescrypt. It is considered stronger as SHA512 or blowfish and as strong as argon2 for crypt() purpose. The hashing method was developed by the author of the blowfish crypt method, and was based on scrypt. It is supported on most Linux distributions, that ship with libxcrypt as a replacement for the glibc crypt library: Fedora, Debian, Ubuntu, OpenSUSE and many others.
https://bugs.python.org/issue44309