This is an automated email from the ASF dual-hosted git repository. duncangrant pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
The following commit(s) were added to refs/heads/master by this push: new da85bb4 Refine the previous comment about ssh-keygen new a5b30ff Merge pull request #294 from infrastation/master da85bb4 is described below commit da85bb41e5a3dc8b85db8c274b6f26aed91b036f Author: Denis Ovsienko <de...@ovsienko.info> AuthorDate: Thu Oct 3 10:56:46 2019 +0100 Refine the previous comment about ssh-keygen --- guide/locations/_ssh-keys.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/guide/locations/_ssh-keys.md b/guide/locations/_ssh-keys.md index d087922..adebcba 100644 --- a/guide/locations/_ssh-keys.md +++ b/guide/locations/_ssh-keys.md @@ -26,13 +26,15 @@ If you don't have an SSH key, create one with: $ ssh-keygen -t rsa -N "" -m PEM -f ~/.ssh/id_rsa ``` -**Note:** For previous versions of OpenSSL, the `-m PEM` flag is not necessary. -However, for newer versions of OpenSSL, if the `-m PEM` flag is omitted, the -key produced will be in OPENSSL format, not RSA format. To determine if a key -is in the correct format, `cat` the key and the first line should read as follows: +**Note:** For previous versions of OpenSSH, the `-m PEM` flag is not necessary. +However, for newer versions of OpenSSH, if the `-m PEM` flag is omitted, the +generated key will be in RFC4716 format, not PEM format. Check the first line of +the generated secret key file, which should be as follows: ```bash +$ head -n 1 ~/.ssh/id_rsa -----BEGIN RSA PRIVATE KEY----- +$ ```