-
-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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
test_crypt segfaults when using libxcrypt instead of libcrypt #76816
Comments
Currently in Fedora glibc stopped providing libcrypt[0] a change which is slowly being upstreamed as well[1] in favor of the libxcrypt project[2]. This causes a segfault when importing the crypt module as python assumes that crypt.h is always available. Providing a working patch from the libxcrypt maintainer. I'll convert the patch into a PR. [0] https://fedoraproject.org/wiki/Changes/Replace_glibc_libcrypt_with_libxcrypt |
Incidentally, why did this manifest as a segfault rather than a compilation error? |
yes, go ahead |
Sorry to bump an old thread, but - does <crypt.h> need to be in the public Python.h header? Or would it be enough to be in _cryptmodule.c, which is the code that uses crypt_r()? I can provide a quick patch to change that if that seems sound. |
Geoffrey Thomas: Benjamin Peterson: |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: