- Add <acronym> tags around RSA and DSA words,
- ensure reader that the ~/.ssh/authorized_files is pure file and not directory [1], - simplify the last part of para, - 8 spaces = tab, while here. PR: docs/116879 [1]
This commit is contained in:
parent
94cfcf8f17
commit
6d4cd2ff49
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=30860
1 changed files with 7 additions and 6 deletions
|
|
@ -4220,12 +4220,13 @@ bb:48:db:f2:93:57:80:b6:aa:bc:f5:d5:ba:8f:79:17 user@host.example.com
|
|||
<filename>~/.ssh/id_dsa</filename> or
|
||||
<filename>~/.ssh/id_rsa</filename>, whereas the public key is
|
||||
stored in <filename>~/.ssh/id_dsa.pub</filename> or
|
||||
<filename>~/.ssh/id_rsa.pub</filename>, respectively for DSA and
|
||||
RSA key types. The public key must be placed in
|
||||
<filename>~/.ssh/authorized_keys</filename> of the remote
|
||||
machine in order for the setup to work. Similarly, RSA version
|
||||
1 public keys should be placed in
|
||||
<filename>~/.ssh/authorized_keys</filename>.</para>
|
||||
<filename>~/.ssh/id_rsa.pub</filename>, respectively for
|
||||
<acronym>DSA</acronym> and <acronym>RSA</acronym> key types.
|
||||
The public key must be placed in the
|
||||
<filename>~/.ssh/authorized_keys</filename> file of the remote
|
||||
machine for both <acronym>RSA</acronym> or
|
||||
<acronym>DSA</acronym> keys in order for the setup to
|
||||
work.</para>
|
||||
|
||||
<para>This will allow connection to the remote machine based upon
|
||||
SSH keys instead of passwords.</para>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue