Re: rsh or ssh and authorization over a masqueraded connection.

1997-06-10 Thread Rob Browning
Christoph Lameter <[EMAIL PROTECTED]> writes: > You can simply decrypt the private key and then no passwords are required. I couldn't figure out how to do that, but isn't that a little unsafe? After some more investigation, it looks like the way ssh wants you to do this is with ssh-agent and ssh

Re: rsh or ssh and authorization over a masqueraded connection.

1997-06-10 Thread Christoph Lameter
On 9 Jun 1997, Rob Browning wrote: >Christoph Lameter <[EMAIL PROTECTED]> writes: > >> You need to run keygen and then put your public key on the host you >> want to reach. Get rid of the .shosts file and the pain of >> passwords is gone. You can put your private key on any account you >> want to

Re: rsh or ssh and authorization over a masqueraded connection.

1997-06-10 Thread Rob Browning
Christoph Lameter <[EMAIL PROTECTED]> writes: > You need to run keygen and then put your public key on the host you > want to reach. Get rid of the .shosts file and the pain of > passwords is gone. You can put your private key on any account you > want to use to connect from. I had tried that, b

Re: rsh or ssh and authorization over a masqueraded connection.

1997-06-10 Thread Christoph Lameter
Use RSA User authentication instead of RSA Host authentication. You need to run keygen and then put your public key on the host you want to reach. Get rid of the .shosts file and the pain of passwords is gone. You can put your private key on any account you want to use to connect from. In artic