-
Notifications
You must be signed in to change notification settings - Fork 272
fails when box is in FIPS mode #882
Comments
thanks @davidkarlsen , the pointer to a solution is appreciated. we just ran into this ourselves as well so we'll update here. |
@zhill any idea which release it will go into? |
bump |
* Adds usedforsecurity=false for all hashlib invocations for fips support * Switch from hashlib.md5 to hashlib.new("md5",...) for MacOS and linux support of usedforsecurity=False option * Switch to use psycopg2 instead of psycopg2-binary for FIPs compatibility MacOS users will need to install postgres and openssl (brew install postgres openssl) and setup LIBRARY_PATH and DYLD_LIBRARY_PATH to point to the openssl lib dir in order for the install of psycopg2 to work from source instead of using psycopg2-binary. Signed-off-by: Zach Hill <[email protected]>
* Adds usedforsecurity=false for all hashlib invocations for fips support * Switch from hashlib.md5 to hashlib.new("md5",...) for MacOS and linux support of usedforsecurity=False option * Switch to use psycopg2 instead of psycopg2-binary for FIPs compatibility MacOS users will need to install postgres and openssl (brew install postgres openssl) and setup LIBRARY_PATH and DYLD_LIBRARY_PATH to point to the openssl lib dir in order for the install of psycopg2 to work from source instead of using psycopg2-binary. Signed-off-by: Zach Hill <[email protected]>
Hi @davidkarlsen I've got some changes in testing, in #985. If things look ok when we do more testing, then either 0.9.4 or the next minor release will have the fix. |
* Adds usedforsecurity=false for all hashlib invocations for fips support * Switch from hashlib.md5 to hashlib.new("md5",...) for MacOS and linux support of usedforsecurity=False option * Switch to use psycopg2 instead of psycopg2-binary for FIPs compatibility MacOS users will need to install postgres and openssl (brew install postgres openssl) and setup LIBRARY_PATH and DYLD_LIBRARY_PATH to point to the openssl lib dir in order for the install of psycopg2 to work from source instead of using psycopg2-binary. Signed-off-by: Zach Hill <[email protected]>
Have been testing the #985 fix and more updates are needed to handle SQLAlchemy (may need to monkey patch it). Will update here, but did not make 0.9.4. We are going to have to get FIPS compliant test infrastructure to ensure this is correct in CI, so may take more time than available for the next feature release as well. But, we are working on it and will continue updates as we make progress. |
Hey @zhill, just ran into basically this exact same issue on a RHEL7 installation. Any chance there's any updates on this since mid May? |
* Adds usedforsecurity=false for all hashlib invocations for fips support * Switch from hashlib.md5 to hashlib.new("md5",...) for MacOS and linux support of usedforsecurity=False option * Switch to use psycopg2 instead of psycopg2-binary for FIPs compatibility MacOS users will need to install postgres and openssl (brew install postgres openssl) and setup LIBRARY_PATH and DYLD_LIBRARY_PATH to point to the openssl lib dir in order for the install of psycopg2 to work from source instead of using psycopg2-binary. Signed-off-by: Zach Hill <[email protected]>
* Adds usedforsecurity=false for all hashlib invocations for fips support * Switch from hashlib.md5 to hashlib.new("md5",...) for MacOS and linux support of usedforsecurity=False option * Switch to use psycopg2 instead of psycopg2-binary for FIPs compatibility MacOS users will need to install postgres and openssl (brew install postgres openssl) and setup LIBRARY_PATH and DYLD_LIBRARY_PATH to point to the openssl lib dir in order for the install of psycopg2 to work from source instead of using psycopg2-binary. Signed-off-by: Zach Hill <[email protected]>
Closed by #1193 and released in v0.10.2 |
See similar issue and how to avoid it: s3tools/s3cmd#1005
chart version:
The text was updated successfully, but these errors were encountered: