Is it safe to still use radicale with passlib? #1965
lahwaacz
started this conversation in
External Packaging
Replies: 2 comments 1 reply
-
|
"passlib" is still supported, there is also a detection implemented in case bcrypt >= 5.0.0 and passlib(libpass) < 1.9.3 and bcrypt hashes found in htpasswd authentication file: Radicale/radicale/auth/htpasswd.py Line 122 in a4a3931 Fedora/EL has a simple adjustment in packaging included for 3.6.0: https://src.fedoraproject.org/rpms/radicale/blob/rawhide/f/radicale.spec#_240 |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Wiki also updated: https://github.com/Kozea/Radicale/wiki Notes added by 4fb1672 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Radicale 3.6.0 replaced the PyPI/passlib dependency with PyPI/libpass. However, as I pointed out here, both passlib and libpass packages from PyPI install the same package name in site-packages, an environment breaks if both packages get installed. Arch Linux packages passlib and there is no way to package libpass. Is it safe to upgrade radicale on Arch Linux and use it with passlib, or are there already breaking changes in the API?
Beta Was this translation helpful? Give feedback.
All reactions