Differences between version 29 and previous revision of SSHKeys.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 29 | Last edited on Tuesday, June 30, 2009 11:26:01 pm | by JohnBillings | Revert |
| Older page: | version 28 | Last edited on Tuesday, June 30, 2009 11:24:32 pm | by JohnBillings | Revert |
@@ -20,9 +20,9 @@
# or
ssh-keygen -t rsa
</verbatim>
-There is ongoing discussion on which algorithm is "better". Define better? Are you talking about security or efficiency? Do a google on ["RSA vs DSA"|http://www.google.co.nz/search?hl=en&q=rsa+vs+dsa] and decide for yourself. At the end of the day, either or get the job of securing your communication from eavesdroppers done. Someday it's inevitable these algorithms will become obsolete and replaced by something else.
+There is ongoing discussion on which algorithm is "better" [RSA] or [DSA]
. Define better? Are you talking about security or efficiency? Do a google on ["RSA vs DSA"|http://www.google.co.nz/search?hl=en&q=rsa+vs+dsa] and decide for yourself. At the end of the day, either or get the job of securing your communication from eavesdroppers done. Someday it's inevitable these algorithms will become obsolete and replaced by something else.
!!! Distributing public keys
If you accepted the defaults for ssh-keygen(1) you should have two new files in <tt>~~/.ssh</tt>, <tt>id_dsa</tt> and <tt>id_dsa.pub</tt> (or <tt>id_rsa</tt> and <tt>id_rsa.pub</tt>). The <tt>.pub</tt> file is your ''public'' key. You transfer a copy of this key to all remote hosts that you wish to use your key pair with. The easy way to do so is by using ssh-copy-id(1):
