fanf 99/12/14 09:45:17
Modified: . devnotes.html
Log:
One of my colleages noted that this page recommends using
unencrypted ssh keys. It's better to use the ssh-agent.
Submitted by: Mike Bristow <[EMAIL PROTECTED]>
Revision Changes Path
1.13 +6 -5 apache-devsite/devnotes.html
Index: devnotes.html
===================================================================
RCS file: /home/cvs/apache-devsite/devnotes.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- devnotes.html 1999/10/12 21:47:08 1.12
+++ devnotes.html 1999/12/14 17:45:17 1.13
@@ -220,11 +220,12 @@
</LI>
<LI>On your local system generate your SSH public key file
<SAMP>~/.ssh/identity.pub</SAMP> via <SAMP>ssh-keygen</SAMP> and then put
- it in <SAMP>~/.ssh/authorized_keys</SAMP> on the repository system. This
- will allow you to access the repository without having to enter a
password
- for each CVS operation. But make sure that you didn't enter a passphrase
- when running <SAMP>ssh-keygen</SAMP> or you need to enter that one
- instead of the password (which would be no gain).
+ it in <SAMP>~/.ssh/authorized_keys</SAMP> on the repository system. If
you
+ use the <SAMP>ssh-agent</SAMP> this will allow you to access the
repository
+ without having to enter a password for each CVS operation. Use
+ <SAMP>ssh-add</SAMP> and enter your passphrase once when you start a
+ session, and <SAMP>ssh-add -D</SAMP> at the end of the session to
+ delete your unencrypted key from the agent.
</LI>
</OL>
<HR>
