Differences between version 20 and predecessor to the previous major change of SSHKeys.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 20 | Last edited on Thursday, October 27, 2005 1:10:40 pm | by MatthiasDallmeier | Revert |
| Older page: | version 19 | Last edited on Friday, August 26, 2005 5:03:02 pm | by JohnMcPherson | Revert |
@@ -23,9 +23,9 @@
(DSA keys are probably preferable to RSA keys.)
!!! Distributing public keys
-If you accepted the defaults for ssh-keygen(1) you should have two new files in ~/.ssh, __id_dsa__ and __id_dsa.pub__ (or id_rsa and id_dsa
.pub)%%%
+If you accepted the defaults for ssh-keygen(1) you should have two new files in ~/.ssh, __id_dsa__ and __id_dsa.pub__ (or __
id_rsa__
and __
id_rsa
.pub__
)%%%
The .pub file is your public key, you need to upload it to all remote hosts that you want to use Keys with.%%%
You need a __.ssh__ directory in your home on the remote machine. This directory must not be group or world writable. Keys go into the __.ssh/authorized_keys__ file, which must also not be group or world writable.
One any local machine that you wish to ssh *from*, you must have the private key __id_dsa__ (unless you forward an "ssh agent", discussed below) and it must not be readable by anyone other than the owner.
Obviously the directory and these files must be owned by the correct user. If the permissions are wrong, [SSH] will refuse to read them (without telling you, unfortunately - it only cries to syslogd(8)). [Debian] provides a ssh-copy-id(1) program which does all this automagically. Just say
