From: Werner Koch <wk@gnupg.org>
Subject: Re: PGG/GPG Integration bug (somewhat nasty & urgent), potential
Date: Thu, 12 May 2005 17:48:19 +0200 [thread overview]
Message-ID: <87br7g1m4c.fsf@wheatstone.g10code.de> (raw)
In-Reply-To: <m3fywum8jf.fsf@brain.gnuhh.org> (Georg C. F. Greve's message of "Wed, 11 May 2005 11:11:32 +0200")
On Wed, 11 May 2005 11:11:32 +0200, Georg C F Greve said:
> pgg should completely IGNORE anything to do with pass phrases and not
> submit any pass-phrase related command line options (save those
> dealing with gpg-agent) for the gpg-agent to work properly.
The way to do this is by checking the $GPG_AGENT_INFO. If it has been
set there won't be any need to ask for the passphrase at all.
Salam-Shalom,
Werner
prev parent reply other threads:[~2005-05-12 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 8:44 PGG/GPG Integration bug (somewhat nasty & urgent), potential mailcrypt concept bug Georg C. F. Greve
2005-05-04 18:16 ` Georg C. F. Greve
2005-05-09 19:25 ` Simon Josefsson
2005-05-11 9:11 ` Georg C. F. Greve
2005-05-12 15:48 ` Werner Koch [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87br7g1m4c.fsf@wheatstone.g10code.de \
--to=wk@gnupg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).