--- Lester Caine <[EMAIL PROTECTED]> wrote: <snip> > So while a switch may have seemed appropriate at the time, > personally I think > it was probably premature and like Paul - I am unwilling to > manually submit > keys to a site which requests them via email. So I will remain a > lurker rather > than becoming more actively involved.
If I understand you correctly, you are implying that there is a security risk involved in disseminating your ssh *public* key?! Would you care to enlighten me on the whereabouts of any data to prove this? Even if it is true that there is a significant security risk, I am certain that there is a way to use one public/private key pair for cvs.linuxcnc.org, and to keep your "regular" public key private, thus eliminating the perceived security risk. According to the following link, using a public/private key pair with SSH is *more* secure than using a password: http://the.earth.li/~sgtatham/putty/0.53b/htmldoc/Chapter8.html Mark ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
