X-Spam-Check-By: sourceware.org
Message-ID: <fe5564c70705251106w3357d62bp5772de1ceea09aee@mail.gmail.com>
Date: Fri, 25 May 2007 11:06:11 -0700
From: "Eric Matsui" <etmatsui AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: GnuPG 2.0.4 working -- almost
In-Reply-To: <46571C08.9070600@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <uwsywde9q DOT fsf AT KUROSUKE DOT i-did-not-set--mail-host-address--so-tickle-me> 	 <46571C08 DOT 9070600 AT gmail DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 5/25/07, morgan gangwere <0 DOT fractalus AT gmail DOT com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> etmatsui AT gmail DOT com wrote:
> > I managed to build GnuPG 2.0.4.
> >
> > Unfortunately, the one feature, which was the reason why I wanted to
> > build it in the first place, isn't working properly.  And that is to
> > use gpg-agent in daemon mode.
> >
> > The problem seems to boil down to this.  When running as a daemon,
> > gpg-agent spawns a new thread when it receives a request for a
> > passphrase from gpg2.  The thread, in turn, calls
> > assuan_pipe_connect(), which is supposed to fork a subprocess that
> > launches pinentry.  Even though fork() does return a convincingly
> > PID-like number, alas, the child is never born (or perhaps dies before
> > executing any code).
> >
> > When running as pipe server (as in the case when gpg-agent is launched
> > directly by gpg2), the same assuan_pipe_connect() function is used to
> > launch pinentry.  The differences are that it is not called from a
> > thread, and that, most importantly, it works as it should.  The child
> > process is born, does its job, and dies happily with the knowledge of
> > job well done.
> >
> > I found out that the issue of pth threads and forking was raised in
> > the past (6 years ago):
> > http://cygwin.com/ml/cygwin/2001-05/msg01131.html
> >
> > I was wondering if there's been further developments on this ever
> > since.
> >
> > Any input will be appreciated.
> >
> erm... why not look at what the Windows official version does? they
> seem to have fixed the threading (at least in what I use)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFGVxwHCF9T/dUsmAgRAtCfAJ47aNKvAfMs5/XmdwpkKrPjQ2l0bwCdEMrE
> 1MAFWaYqDfEAMLKQwMIwiUY=
> =mbD1
> -----END PGP SIGNATURE-----
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/

1.4.7 is the latest in the portable standalone branch, so it doesn't
use gpg-agent.
But maybe I'm missing your point?
I looked through the 1.4.7 source just in case, and it doesn't seem to
use pth at all.

-- 
Eric

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/