forked from TrueCloudLab/distribution
sha256 when generating certificates
Small detail, but when generating certificates using sha256 is recommended. See for example http://googleonlinesecurity.blogspot.se/2014/09/gradually-sunsetting-sha-1.html. Signed-off-by: Thomas Sjögren <konstruktoid@users.noreply.github.com>
This commit is contained in:
parent
36d4e365aa
commit
e39583cc9d
1 changed files with 2 additions and 2 deletions
|
@ -284,7 +284,7 @@ source](https://github.com/docker/distribution/releases/tag/v2.0.0).
|
|||
5. Use SSL to generate some self-signed certificates.
|
||||
|
||||
$ openssl req \
|
||||
-newkey rsa:2048 -nodes -keyout certs/domain.key \
|
||||
-newkey rsa:2048 -nodes -sha256 -keyout certs/domain.key \
|
||||
-x509 -days 365 -out certs/domain.crt
|
||||
|
||||
This command prompts you for basic information it needs to create the certificates.
|
||||
|
@ -420,7 +420,7 @@ procedure. The directory includes an example `compose` configuration.
|
|||
2. Use SSL to generate some self-signed certificates.
|
||||
|
||||
$ openssl req \
|
||||
-newkey rsa:2048 -nodes -keyout domain.key \
|
||||
-newkey rsa:2048 -nodes -sha256 -keyout domain.key \
|
||||
-x509 -days 365 -out domain.crt
|
||||
|
||||
This command prompts you for basic information it needs to create certificates.
|
||||
|
|
Loading…
Reference in a new issue