Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Jon <ghia at ccs.neu.edu> writes: > Thanks to everyone who replied. I gave up on trying to use one key. I > made a seperate key pair for putty and comercial SSH. > > Putty allows you to copy the key in OpenSSH format right from the puttygen > program. For comercial SSH I had to do the following: > > $ ssh-keygen -i -f rsa_putty.pub >> .ssh/authorized_keys > > Passwords are turned off and my firewall is happy now... thanks again. It's important to note that putty uses the ssh v1 protocol, which has a major flaw in its CRC calculation. Because of this, the v1 protocol isn't any more secure than telnet. My personal preference is to use OpenSSH everywhere. When I have to use Windows, I install the cygwin tools, which includes OpenSSH and also has XFree86 as an extra add-on. -- John Abreau / Executive Director, Boston Linux & Unix ICQ 28611923 / AIM abreauj / JABBER jabr at jabber.org / YAHOO abreauj Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9 PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 344 bytes Desc: not available URL: <http://lists.blu.org/pipermail/discuss/attachments/20020319/e80fbbf9/attachment.sig>
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |