-
-
Notifications
You must be signed in to change notification settings - Fork 121
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
added fips flag #290
base: main
Are you sure you want to change the base?
added fips flag #290
Conversation
👋 Thanks for the interest in Gemstash. There are tests covering the returned configuration, and they now fail. |
looks like there were some additional differences in that config too. i've addressed those so that spec passes now. |
@@ -35,6 +39,8 @@ | |||
puma_workers: 1 | |||
cache_expiration: 1800 | |||
cache_max_size: 500 | |||
storage_adapter: local | |||
s3_path: gemstash/s3_storage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These were not due to changes I made, but were needed to get the spec to pass
@benklop could you rebase this PR with master please, thank you! 🙇 |
Description:
Currently gemstash is not usable in environments with fips enforcement. #195 Tried to resolve this but has stalled for 3 years since it seems this needs to be enabled with a flag. @olleolleolle updated the changeset to add such a flag, but the changes never made it back here. In the meantime the diff stopped applying cleanly, I have fixed that and opened this PR.
I have made this use the config file option
fips
instead of a flag.I will abide by the code of conduct.