Date: Mon, 13 Apr 2009 20:48:46 -0400 From: Joe Marcus Clarke <marcus@FreeBSD.org> To: Dmitry Morozovsky <marck@rinet.ru> Cc: gnome@FreeBSD.org, ports@FreeBSD.org Subject: Re: HEADS UP: GNOME 2.26 available for FreeBSD Message-ID: <1239670126.1304.75.camel@shumai.marcuscom.com> In-Reply-To: <alpine.BSF.2.00.0904140439310.2317@woozle.rinet.ru> References: <1239343955.4933.113.camel@shumai.marcuscom.com> <alpine.BSF.2.00.0904140344130.2317@woozle.rinet.ru> <1239667718.1304.66.camel@shumai.marcuscom.com> <alpine.BSF.2.00.0904140427160.2317@woozle.rinet.ru> <1239669463.1304.67.camel@shumai.marcuscom.com> <alpine.BSF.2.00.0904140439310.2317@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-cnE4yGqv/ygjMXc/nPeC Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2009-04-14 at 04:46 +0400, Dmitry Morozovsky wrote: > On Mon, 13 Apr 2009, Joe Marcus Clarke wrote: >=20 > JMC> > JMC> > remote login using ssh keys with the following message in t= he logs (sorry,=20 > JMC> > JMC> > can't reproduce the message from Terminal popup window) > JMC> > JMC> >=20 > JMC> > JMC> > Apr 12 11:54:37 <console.info> revamp kernel: Apr 12 11:54:= 37 <auth.notice>=20 > JMC> > JMC> > revamp gnome-keyring-ask: couldn't allocate secure memory t= o keep passwords and=20 > JMC> > JMC> > or keys from being written to the disk > JMC> > JMC> >=20 > JMC> > JMC> > Any hints to fix this? RELENG_7/i386 > JMC> > JMC>=20 > JMC> > JMC> This error is normal, and not fatal. How do you have PAM con= figured for > JMC> > JMC> SSH? > JMC> >=20 > JMC> >=20 > JMC> > Hrrm, this is from client side, not from server, how can PAM inter= vent with=20 > JMC> > this? > JMC>=20 > JMC> Then I guess I misunderstand the problem. Are you having a problem = with > JMC> seahorse-agent acting as an SSH agent? >=20 > It seems to be so. >=20 > Let me explain the situation a bit: >=20 > My home machine, RELENG_7/i386, with fresh source and fresh ports tree, a= cts as=20 > my window to my work servers, some of them recognising my SSH key as trus= ted. >=20 > Before the upgrade, I had once pop-up asking for my key passphrase, then=20 > let me use this private key during my (home) session without further aski= ng. >=20 > Now, when I try to connect to the host which even possibly want to check=20 > whether I want to present some key there, I got the pop-up. I even checke= d that=20 > I can connect to the host in question using plain xterm, and have usual=20 > password qiery. What versions of gnome-keyring and seahorse do you have? Joe --=20 Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome --=-cnE4yGqv/ygjMXc/nPeC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAknj3WwACgkQb2iPiv4Uz4fxmgCfa+kXydJ0fId2xYETeXTWiaaa NyAAn1jfKL3FsU3ITgUguXRInQtfrjLX =xYgg -----END PGP SIGNATURE----- --=-cnE4yGqv/ygjMXc/nPeC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1239670126.1304.75.camel>