From owner-freebsd-ports@FreeBSD.ORG Tue Apr 14 13:54:20 2009 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A74901065687; Tue, 14 Apr 2009 13:54:20 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id 7232A8FC16; Tue, 14 Apr 2009 13:54:20 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from [192.168.1.151] (adsl-1-210-55.bna.bellsouth.net [65.1.210.55]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id n3EDsE62004793 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Apr 2009 09:54:14 -0400 (EDT) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: Dmitry Morozovsky In-Reply-To: References: <1239343955.4933.113.camel@shumai.marcuscom.com> <1239667718.1304.66.camel@shumai.marcuscom.com> <1239669463.1304.67.camel@shumai.marcuscom.com> <1239670126.1304.75.camel@shumai.marcuscom.com> <3f1fd1ea0904131951u5e6b211dlbb55af484d91e63b@mail.gmail.com> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-+4UIIHhRVfndcEN2X75e" Organization: FreeBSD Date: Tue, 14 Apr 2009 08:54:09 -0500 Message-Id: <1239717249.1407.9.camel@wombat.2hip.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.0 FreeBSD GNOME Team Port X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RCVD_IN_SORBS_DUL,RDNS_DYNAMIC autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net Cc: gnome@freebsd.org, ports@freebsd.org, Joe Marcus Clarke , Michal Varga Subject: Re: HEADS UP: GNOME 2.26 available for FreeBSD X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2009 13:54:21 -0000 --=-+4UIIHhRVfndcEN2X75e Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2009-04-14 at 14:24 +0400, Dmitry Morozovsky wrote: > On Tue, 14 Apr 2009, Michal Varga wrote: >=20 > MV> On Tue, Apr 14, 2009 at 3:13 AM, Dmitry Morozovsky w= rote: > MV> > Dear Joe Marcus, > MV> > > MV> > DM> JMC> What versions of gnome-keyring and seahorse do you have? > MV> > DM> > MV> > DM> marck@revamp:/usr/ports> pkg_info | egrep 'gnome-keyring|seahor= se' > MV> > DM> gnome-keyring-2.26.0 A program that keeps passwords and other s= ecrets > MV> > DM> seahorse-2.26.0 GNOME application for managing encryption k= eys (PGP, SSH) > MV> > > MV> > After > MV> > > MV> > portupgrade -f seahorse gnome-keyring > MV> > > MV> > and reboot > MV> > > MV> > still the same effect... > MV> > > MV> > Of course, I can wipe packages installed and set it up from scratch= , but I > MV> > would prefer a bit safer way if at all possible ;-) > MV> > > MV> Well, I have no idea what a "Terminal remote login" in this particula= r > MV> context is, so this may not be of any help, but I've seen this issue > MV> before: > MV>=20 > MV> "Before the upgrade, I had once pop-up asking for my key passphrase, = then > MV> let me use this private key during my (home) session without further = asking.. > MV> Now, when I try to connect to the host which even possibly want to ch= eck > MV> whether I want to present some key there, I got the pop-up. I even ch= ecked that > MV> I can connect to the host in question using plain xterm, and have usu= al > MV> password qiery." > MV>=20 > MV> I've been in similiar situation some time ago, when new > MV> gnome-keyring/seahorse (it started with one of the recent versions, > MV> don't remember exactly when, but definitely before 2.26 was > MV> introduced) for some surely interesting reason insisted on creating a > MV> very own keyring every other reboot - while originally you were using > MV> one default keyring (let's call it "default") for storing your > MV> passwords, now gnome-keyring kept creating a new one named "login" an= d > MV> always set it as the default one. > MV>=20 > MV> That "login" keyring was even more special in that that nothing store= d > MV> in it ever worked, it still kept asking for passwords and even then > MV> was not able to use them (and lost them on the next reboot anyway.. > MV> Maybe that's a feature, don't know, don't care). I've run into this o= n > MV> a few different machines, every time I needed to open 'seahorse', get > MV> to Passwords tab, delete the "login" keyring, set the original > MV> "default" as the default keyring (first time I wiped them all and > MV> created a clean one to be sure, but as it turned out later, this > MV> wasn't needed), after that, passwords worked fine again. This > MV> procedure again and again for a few days/reboots, until seahorse > MV> miraculously stopped this madness and let my default keyring be, well= , > MV> default (yes, just like that). > MV>=20 > MV> Anyway, if you weren't there yet, check seahorse gui for what keyring > MV> are you really using, maybe you've hit the same issue with the "login= " > MV> stupidity.. >=20 > Yes, seahorse shows me two keyrings; however, deleting "login" one does n= ot fix=20 > the situation: if in the Terminal I try to open tab which ssh's to outer = host,=20 > I immediately got the popup with=20 >=20 > "There was an error creating the child process for this terminal" >=20 > nothing in this tab is started, and tab is just hanging. >=20 > "login" keyring sometimes got recreated, sometimes not, but the effect ab= ove is=20 > totally reproducible. If I am following this correctly, the functionality you are talking about is actually provided by seahorse-agent, which is installed with the seahorse-plugins port now. Unless something has changed with the default session (and I don't think it has, since my keyrings still work) we wrap the session with ssh-agent and seahorse-agent if they are found. robert. --=20 Robert Noland FreeBSD --=-+4UIIHhRVfndcEN2X75e Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEABECAAYFAknklYEACgkQM4TrQ4qfRONosACePoX1ICaIoLt7K76EfmdR6meu fVsAn2Bc/g+q0TsjhNqMkNvgNvtH9hjJ =MHV9 -----END PGP SIGNATURE----- --=-+4UIIHhRVfndcEN2X75e--