Skip to content
This repository was archived by the owner on Jul 31, 2025. It is now read-only.

Conversation

@justincormack
Copy link
Contributor

The best test we currently have for whether Notary is running in a FIPS
compliant environment is whether the MD5 hash function is registered when
crypto/md5 is linked in to the program. This function is not available
in FIPS mode as it is not an allowed hash function.

Signed-off-by: Justin Cormack [email protected]

@HuKeping
Copy link
Contributor

The const FIPSEnvVar in the testcode fail the CI

@justincormack
Copy link
Contributor Author

Ah ok, we still have a force override, will adjust.

@justincormack
Copy link
Contributor Author

Ok fixed up the way tests work cc @cyli

The best test we currently have for whether Notary is running in a FIPS
compliant environment is whether the MD5 hash function is registered when
crypto/md5 is linked in to the program. This function is not available
in FIPS mode as it is not an allowed hash function.

Fix the tests to not use environment variables but private functions
instead. This allows parallel testing and is cleaner.

Signed-off-by: Justin Cormack <[email protected]>
Copy link
Contributor

@cyli cyli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks for fixing this @justincormack

@HuKeping
Copy link
Contributor

Thanks @justincormack

LGTM!

@HuKeping HuKeping merged commit ab322b6 into notaryproject:master Mar 28, 2018
@justincormack justincormack deleted the fips-test branch March 28, 2018 16:02
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants