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

doc: Describe FIPSDIR environment variable #3752

Closed
wants to merge 1 commit into from

Conversation

stefanmb
Copy link
Contributor

It is possible to install the FIPS validated OpenSSL cryptographic module to a custom location, without violating the requirement for calling ./configure without custom arguments.

As per the OpenSSL User Guide, it is possible to use the FIPSDIR
environment variable to specify a custom install path for the
validated cryptographic module.
@mscdex mscdex added the doc Issues and PRs related to the documentations. label Nov 11, 2015
@mhdawson mhdawson self-assigned this Nov 11, 2015
@mhdawson mhdawson added the crypto Issues and PRs related to the crypto subsystem. label Nov 11, 2015
@indutny
Copy link
Member

indutny commented Nov 11, 2015

cc @nodejs/crypto I would like to have one more LGTM on this, just to be sure

@indutny
Copy link
Member

indutny commented Nov 11, 2015

Oh, and LGTM. Thank you!

@shigeki
Copy link
Contributor

shigeki commented Nov 12, 2015

LGTM.
/.config is a shell script and used only for building on Unix systems and ms/do_fips.bat is on Windows. But building FIPS on Windows is a different issue so let it as is.

@mhdawson
Copy link
Member

Doc change only so not going to run CI build on it

mhdawson pushed a commit that referenced this pull request Nov 12, 2015
As per the OpenSSL User Guide, it is possible to use the FIPSDIR
environment variable to specify a custom install path for the
validated cryptographic module.

PR-URL: #3752
Reviewed-By: Michael Dawsson <[email protected]>
Reviewed-By: Shigeki Ohtsu <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
@mhdawson
Copy link
Member

landed as 9f71a31

@mhdawson mhdawson closed this Nov 12, 2015
rvagg pushed a commit that referenced this pull request Nov 13, 2015
As per the OpenSSL User Guide, it is possible to use the FIPSDIR
environment variable to specify a custom install path for the
validated cryptographic module.

PR-URL: #3752
Reviewed-By: Michael Dawsson <[email protected]>
Reviewed-By: Shigeki Ohtsu <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
@rvagg rvagg mentioned this pull request Dec 17, 2015
MylesBorins pushed a commit that referenced this pull request Dec 29, 2015
As per the OpenSSL User Guide, it is possible to use the FIPSDIR
environment variable to specify a custom install path for the
validated cryptographic module.

PR-URL: #3752
Reviewed-By: Michael Dawsson <[email protected]>
Reviewed-By: Shigeki Ohtsu <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
MylesBorins pushed a commit that referenced this pull request Jan 19, 2016
As per the OpenSSL User Guide, it is possible to use the FIPSDIR
environment variable to specify a custom install path for the
validated cryptographic module.

PR-URL: #3752
Reviewed-By: Michael Dawsson <[email protected]>
Reviewed-By: Shigeki Ohtsu <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
@MylesBorins MylesBorins mentioned this pull request Jan 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crypto Issues and PRs related to the crypto subsystem. doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants