Re: [Discuss-gnuradio] savannah access

[Eric Blossom]

On Tue, Dec 20, 2005 at 03:30:53PM -0500, cswiger wrote:
>
> Savannah just seems to be hosed as far as registering new
> public keys.  I've generated public keys, with passphrase,
> on several machines (ssh-keygen -t dsa), put the keys on
> other host machines  (in ~/.ssh/authorized_keys2, with permission 600)
> and can log in fine.  One nice trick is to make a public key
> w/o passphrase, put it on a host and get instant ssh access
> without having to type a password or phrase.

You can run them without passphrases, but I wouldn't recommend it.
Instead, use keys with passphrases and use ssh-agent.  You'll only
have to enter the passphrase once with ssh-add (but at least you
*will* enter it), then you're good to go for the remainder of the
session.  On KDE and GNOME, I believe that they start ssh-agent for
you if they detect the presence of ~/.ssh.  You'll still need to do
the ssh-add.  If you created your first ssh key in this login session,
you may need to logout and relogin to have it start ssh-agent for you.

address@hidden eb]$ ps aux | grep ssh
root      4046  0.0  0.1  3204 1300 ?        Ss   Dec17   0:00 /usr/sbin/sshd
eb        5049  0.0  0.0  2880  716 ?        Ss   Dec17   0:00 
/usr/bin/ssh-agent -- /bin/sh -c #!/bin/sh??exec /usr/bin/startkde


> ssh -v on Working machines:
> 
> debug1: Offering public key: /home/chuck/.ssh/id_dsa
> debug1: Server accepts key: pkalg ssh-dss blen 434     <--- yea!
> debug1: PEM_read_PrivateKey failed
> debug1: read PEM private key done: type <unknown>
> Enter passphrase for key '/home/chuck/.ssh/id_dsa':
> 
> 
> on cvs.sv.gnu.org:
> 
> debug1: Offering public key: /home/chuck/.ssh/id_dsa
> debug1: Authentications that can continue: publickey
> debug1: No more authentication methods to try.       <--- rats
> Permission denied (publickey).
> 
> 
> Machine directly on the cable modem (no firewall) running
> OpenBSD can't get through.
> 
> Keys are put in: https://savannah.gnu.org/account/editsshkeys.php
> Wait an hour, email address@hidden for help, etc.
> My default ssh-keygen bit-length is 1024, they don't say otherwise.
> Will keep trying.
> 
> --Chuck

No clue.

Eric