[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: ssh private key password



On Fri, 2009-01-09 at 10:47 -0600, Jerry Amundson wrote:
> On Fri, Jan 9, 2009 at 10:39 AM, Matthias Clasen <mclasen redhat com> wrote:
> > On Fri, 2009-01-09 at 09:12 -0500, John W. Linville wrote:
> >> On Thu, Jan 08, 2009 at 07:43:15PM -0500, Matthias Clasen wrote:
> >> > On Thu, 2009-01-08 at 23:42 +0100, nodata wrote:
> >> > > Am Donnerstag, den 08.01.2009, 17:21 -0500 schrieb Ricky Zhou:
> >> > > > On 2009-01-08 11:02:14 PM, nodata wrote:
> >> > > > > I'm wondering when this changed (F10)? I'm sure it didn't act like this
> >> > > > > in F9.
> >> > > > >
> >> > > > > In F9, I would only be prompted to enter my passphrase if I sshed to a
> >> > > > > box that accepted pubkey authentication and a ssh-agent did not already
> >> > > > > have the key.
> >> > > > > In F10 it asks earlier: when ssh-add is run.
> >> > > > When you run ssh-add, you are *asking* for the passphrase to be stored
> >> > > > with ssh-agent, so of course, it has to ask for your passphrase.  This
> >> > > > is the very purpose of ssh-add.  Could you be confusing ssh-add with
> >> > > > something else?
> >> > >
> >> > > No, I'm just getting annoyed that a GUI is popping up when I am using a
> >> > > command line app. Not sure of the point of it, it seems counter
> >> > > intuitive.
> >> >
> >> > If you don't want this, you can turn it off with
> >> > gconftool-2 -s -t bool /apps/gnome-keyting/daemon-components/ssh false
> >>
> >> Sorry for the troll, but I just had to admire this.  One has to love
> >> the easy discoverability of GNOME configuration methods... :-)
> >
> > If you prefer, setting
> >
> > SSH_AUTH_SOCK=
> >
> > in your shell works just as well. How is that for discoverability ?
> 
> Now my system (new F10 from KDE Live) is *not* popping up the GUI window.
> [jerry jerry-opti755 ~]$ gconftool-2 -g
> /apps/gnome-keyring/daemon-components/ssh
> true
> [jerry jerry-opti755 ~]$ env | grep SSH
> SSH_AGENT_PID=2320
> SSH_AUTH_SOCK=/tmp/ssh-bfNSeF2292/agent.2292
> SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
> 
> Is this a bug? :-)
No, this means you are running the regular openssh ssh-agent and not a
gnome-keyring as replacement for ssh-agent.

-- 
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
                                              Turkish proverb


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]