Skip to content
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

Support hosts in FIPS mode #194

Open
ayohrling opened this issue Oct 31, 2018 · 1 comment · May be fixed by #290
Open

Support hosts in FIPS mode #194

ayohrling opened this issue Oct 31, 2018 · 1 comment · May be fixed by #290

Comments

@ayohrling
Copy link

Currently, gemstash does not run on systems that are configured in FIPS mode. There are a couple spots that utilize MD5 digests that need to be replaced for valid operation. Results in the following logs when running the server and timeouts for too many connection resets in fetching gems:

md5_dgst.c(82): OpenSSL internal error, assertion failed: Digest MD5 forbidden in FIPS mode!
[2018-10-31 13:30:47 +0000] - INFO - [16128] - Worker 0 (pid: 16242) booted, phase: 0
md5_dgst.c(82): OpenSSL internal error, assertion failed: Digest MD5 forbidden in FIPS mode!
[2018-10-31 13:30:52 +0000] - INFO - [16128] - Worker 0 (pid: 16254) booted, phase: 0
md5_dgst.c(82): OpenSSL internal error, assertion failed: Digest MD5 forbidden in FIPS mode!
[2018-10-31 13:30:57 +0000] - INFO - [16128] - Worker 0 (pid: 16266) booted, phase: 0
md5_dgst.c(82): OpenSSL internal error, assertion failed: Digest MD5 forbidden in FIPS mode!
[2018-10-31 13:31:02 +0000] - INFO - [16128] - Worker 0 (pid: 16276) booted, phase: 0
@ayohrling
Copy link
Author

Am hoping for some feedback here. I feel like this should be low-hanging fruit. PR is in, we have to work from builds off my fork to use gemstash until this is merged upstream.

@benklop benklop linked a pull request Mar 18, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants