doc: Describe FIPSDIR environment variable #3752
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
|
cc @nodejs/crypto I would like to have one more LGTM on this, just to be sure |
|
Oh, and LGTM. Thank you! |
|
LGTM. |
|
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 <michael_dawson@ca.ibm.com> Reviewed-By: Shigeki Ohtsu <ohtsu@iij.ad.jp> Reviewed-By: Fedor Indutny <fedor@indutny.com>
|
landed as 9f71a31 |
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 <michael_dawson@ca.ibm.com> Reviewed-By: Shigeki Ohtsu <ohtsu@iij.ad.jp> Reviewed-By: Fedor Indutny <fedor@indutny.com>
Closed
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 <michael_dawson@ca.ibm.com> Reviewed-By: Shigeki Ohtsu <ohtsu@iij.ad.jp> Reviewed-By: Fedor Indutny <fedor@indutny.com>
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 <michael_dawson@ca.ibm.com> Reviewed-By: Shigeki Ohtsu <ohtsu@iij.ad.jp> Reviewed-By: Fedor Indutny <fedor@indutny.com>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.