From owner-freebsd-gnome@FreeBSD.ORG  Sun Jan 18 02:39:53 2009
Return-Path: <owner-freebsd-gnome@FreeBSD.ORG>
Delivered-To: freebsd-gnome@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 989971065672
	for <freebsd-gnome@freebsd.org>; Sun, 18 Jan 2009 02:39:53 +0000 (UTC)
	(envelope-from marcus@marcuscom.com)
Received: from creme-brulee.marcuscom.com
	(marcuscom-pt.tunnel.tserv1.fmt.ipv6.he.net
	[IPv6:2001:470:1f00:ffff::1279])
	by mx1.freebsd.org (Postfix) with ESMTP id 270988FC13
	for <freebsd-gnome@freebsd.org>; Sun, 18 Jan 2009 02:39:53 +0000 (UTC)
	(envelope-from marcus@marcuscom.com)
Received: from [IPv6:2001:470:1f00:2464::4] (shumai.marcuscom.com
	[IPv6:2001:470:1f00:2464::4])
	by creme-brulee.marcuscom.com (8.14.3/8.14.3) with ESMTP id
	n0I2dXKh018053; Sat, 17 Jan 2009 21:39:33 -0500 (EST)
	(envelope-from marcus@marcuscom.com)
From: Joe Marcus Clarke <marcus@marcuscom.com>
To: "Denise H. G." <darcsis@gmail.com>
In-Reply-To: <864ozyskxn.fsf@pluton.xbsd.name>
References: <86vdsghdum.fsf@pluton.xbsd.name>
	<1232157465.1547.20.camel@shumai.marcuscom.com>
	<864ozyskxn.fsf@pluton.xbsd.name>
Content-Type: multipart/signed; micalg="pgp-sha1";
	protocol="application/pgp-signature";
	boundary="=-E/Rn4H1J/iz62LmkVAbM"
Organization: MarcusCom, Inc.
Date: Sat, 17 Jan 2009 21:39:53 -0500
Message-Id: <1232246393.51752.6.camel@shumai.marcuscom.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.24.3 FreeBSD GNOME Team Port 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NO_RELAYS
	autolearn=ham version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on
	creme-brulee.marcuscom.com
Cc: freebsd-gnome@freebsd.org
Subject: Re: Should Gnome2 meta port include security/pinentry-gtk2?
X-BeenThere: freebsd-gnome@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: GNOME for FreeBSD -- porting and maintaining
	<freebsd-gnome.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-gnome>,
	<mailto:freebsd-gnome-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-gnome>
List-Post: <mailto:freebsd-gnome@freebsd.org>
List-Help: <mailto:freebsd-gnome-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-gnome>,
	<mailto:freebsd-gnome-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Jan 2009 02:39:53 -0000


--=-E/Rn4H1J/iz62LmkVAbM
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sat, 2009-01-17 at 10:52 +0800, Denise H. G. wrote:
> Joe Marcus Clarke <marcus@marcuscom.com> writes:
>=20
> > On Thu, 2009-01-15 at 21:56 +0800, Denise H. G. wrote:
> >> It seems that without security/pinentry-gtk2, seahorse wouldn't get fu=
ll
> >> functions, such as adding new names to an existing key.
> >
> > Is this documented anywhere?
> >
> > Joe
> >
>=20
> I haven't found it on seahorse's official site. But I got this on
> redhat's bug archives and gentoo's:
>=20
> https://bugzilla.redhat.com/show_bug.cgi?id=3D474419
> http://bugs.gentoo.org/show_bug.cgi?id=3D159505

Interesting because I don't see anywhere in the seahorse code where
pinentry is executed.  In fact, seahorse is working just fine for me
without pinentry.  Can you provide a sequence I can test which will
illustrate the problem caused by lacking pinentry-gtk2?

Joe

--=20
PGP Key : http://www.marcuscom.com/pgp.asc

--=-E/Rn4H1J/iz62LmkVAbM
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)

iEYEABECAAYFAklylngACgkQb2iPiv4Uz4c5MACfZ+YVM7jL7q5N6x6xAaus1cPb
9e8AmgLOaYcJ+ollkhQzkW/INjxM3P5r
=oqqs
-----END PGP SIGNATURE-----

--=-E/Rn4H1J/iz62LmkVAbM--