-
Notifications
You must be signed in to change notification settings - Fork 19
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
python: migrate away from crypt
library
#318
Comments
I suppose we should replace it with hashlib? |
Maybe we should switch to https://pypi.org/project/legacycrypt/ instead. |
ah, if we already use that, sure! I was thinking that maybe passlib would be an option too, but best to keep dependencies low. |
wait, we are doing our crypto with a random library with 2 github stars? |
Yes, passlib is probably better. Or doveadm that we already have, i.e. reverting #49 Calling doveadm should be somewhat cheap because we only do this when user is created, for logging in there is no need to call a subprocess. |
I am not sure this whole crypt->passlib or other mechanism is really worth it. |
Who knows, maybe there is a better crypt replacement then. |
yeah, makes sense I guess |
We're still working on it because it is basically finished and only the CI is broken. If we realize it is not actually finished we will probably close it. |
Now it is finally broken. |
I initially tried switching to hashlib that seems to be the recommended lib in the standard lib, but crypt does random salting while hashlib doesn't and in theory that makes it vulnerable to rainbow-something attacks so I decided to go with the smaller change |
crypt
is removed in Python 3.13 which is currently in beta.The text was updated successfully, but these errors were encountered: