On Tue, 2009-04-14 at 04:52 +0400, Dmitry Morozovsky wrote: > On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: > > JMC> > JMC> Then I guess I misunderstand the problem. Are you having a > problem with > JMC> > JMC> seahorse-agent acting as an SSH agent? > JMC> > > JMC> > It seems to be so. > JMC> > > JMC> > Let me explain the situation a bit: > JMC> > > JMC> > My home machine, RELENG_7/i386, with fresh source and fresh ports > tree, acts as > JMC> > my window to my work servers, some of them recognising my SSH key as > trusted. > JMC> > > JMC> > Before the upgrade, I had once pop-up asking for my key passphrase, > then > JMC> > let me use this private key during my (home) session without further > asking. > JMC> > > JMC> > Now, when I try to connect to the host which even possibly want to > check > JMC> > whether I want to present some key there, I got the pop-up. I even > checked that > JMC> > I can connect to the host in question using plain xterm, and have > usual > JMC> > password qiery. > JMC> > JMC> What versions of gnome-keyring and seahorse do you have? > > ma...@revamp:/usr/ports> pkg_info | egrep 'gnome-keyring|seahorse' > gnome-keyring-2.26.0 A program that keeps passwords and other secrets > seahorse-2.26.0 GNOME application for managing encryption keys (PGP, SSH)
Go to 2.26.1 on both, and see if the problem persists. Joe > -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome
signature.asc
Description: This is a digitally signed message part
