On Tue, 2009-04-14 at 04:46 +0400, Dmitry Morozovsky wrote: > On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: > > JMC> > JMC> > remote login using ssh keys with the following message in the > logs (sorry, > JMC> > JMC> > can't reproduce the message from Terminal popup window) > JMC> > JMC> > > JMC> > JMC> > Apr 12 11:54:37 <console.info> revamp kernel: Apr 12 11:54:37 > <auth.notice> > JMC> > JMC> > revamp gnome-keyring-ask: couldn't allocate secure memory to > keep passwords and > JMC> > JMC> > or keys from being written to the disk > JMC> > JMC> > > JMC> > JMC> > Any hints to fix this? RELENG_7/i386 > JMC> > JMC> > JMC> > JMC> This error is normal, and not fatal. How do you have PAM > configured for > JMC> > JMC> SSH? > JMC> > > JMC> > > JMC> > Hrrm, this is from client side, not from server, how can PAM intervent > with > JMC> > this? > JMC> > JMC> Then I guess I misunderstand the problem. Are you having a problem with > JMC> seahorse-agent acting as an SSH agent? > > It seems to be so. > > Let me explain the situation a bit: > > My home machine, RELENG_7/i386, with fresh source and fresh ports tree, acts > as > my window to my work servers, some of them recognising my SSH key as trusted. > > Before the upgrade, I had once pop-up asking for my key passphrase, then > let me use this private key during my (home) session without further asking. > > Now, when I try to connect to the host which even possibly want to check > whether I want to present some key there, I got the pop-up. I even checked > that > I can connect to the host in question using plain xterm, and have usual > password qiery.
What versions of gnome-keyring and seahorse do you have? 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