Good point.
good point about command line passwords.
I did this:
used keygen to generate a public key on the local side
(I did not supply a password when prompted when creating this)
I copied this public key into the "authorized" file on the remote side.
now when I t ype:
ssh -P -l username my.host.com
I get logged in without a password prompt.
This is using RSA I believe.
I think that leaving the password out is acceptable, If I understand
correctly- this is just to provide another layer security beyond the
exchanging of the keys.
If there are any ssh experts out there, I would like to hear comments.
-----Original Message-----
From: Eric Z. Ayers ">eric.ayers@mindspring.com>
To: Jeff Dilcher ">dilcher@cueva.com>
Cc: Yu, Jerry ">z.yu@Ptek.com>; ">ale@ale.org ">ale@ale.org>
Date: Wednesday, April 05, 2000 6:59 PM
Subject: Re: [ale] ssh without a manually supplied password
>No security concious software is going to allow you to specify a
>password on the commandline, because anyone would be able to see your
>password by running 'ps'
>
>Jeff Dilcher writes:
> > Yes, the problem I have, however, is that ssh-add seems to require
> > you to type in your password in at the console, rather than accepting
> > a command line argument, as I wish it would. I may be missing something
> > obvious, though, so if you know otherwise, let me know!
> >
> > -Jeff
> >
> >
> > -----Original Message-----
> > From: Yu, Jerry ">z.yu@Ptek.com>
> > To: Jeff Dilcher ">dilcher@cueva.com>
> > Cc: ">ale@ale.org ">ale@ale.org>
> > Date: Wednesday, April 05, 2000 12:51 PM
> > Subject: Re: [ale] ssh without a manually supplied password
> >
> >
> > >you can generate a new pair of keys with a empty (null) passphrase.
> > >security risk blah blah. wonder if you can change the existing keys to
do
> > >that.
> > >
> > >you can set up ssh-agent (with ssh-add). ssh-add actually take
passphrase
> > >from command line arguments. So, you can do a little init script to
> > >wrap this up and tie it to your system run level. With the permission
> > >carefully set, it could be somewhat safer than the null-passphrase
> > >approach.
> > >
> > >Jerry Yu
> > >Systems Engineer https://punch/~zyu
> > >Premiere Technologies ">zyu@tc.net
> > >404-262-8544 (O)
> > >
> > >On Thu, 6 Apr 2000, Jeff Dilcher wrote:
> > >
> > >#Hello,
> > >#
> > >#I am thinking of setting up Fetchmail to reqularly check an ISP
> > >#for mail within an SSH session.
> > >#
> > >#I would like to have happen without me having to type in a
> > >#password at any point.
> > >#
> > >#I think I read that you can have SSH only prompt for a password
> > >#on the first connection only using an authorization agent. I would
> > >#like to never have to input a password manually.
> > >#
> > >#Is this possible?
> > >#
> > >#--
> > >#To unsubscribe: mail ">majordomo@ale.org with "unsubscribe ale" in
message
> > body.
> > >#
> > >
> > >--
> > >To unsubscribe: mail ">majordomo@ale.org with "unsubscribe ale" in
message
> > body.
> > >
> >
> > --
> > To unsubscribe: mail ">majordomo@ale.org with "unsubscribe ale" in message
body.
>--
>To unsubscribe: mail ">majordomo@ale.org with "unsubscribe ale" in message
body.
>
--
To unsubscribe: mail ">majordomo@ale.org with "unsubscribe ale" in message body.