From: "Georg C. F. Greve" <greve@gnu.org>
Subject: Re: PGG/GPG Integration bug (somewhat nasty & urgent), potential mailcrypt concept bug
Date: Wed, 04 May 2005 20:16:25 +0200 [thread overview]
Message-ID: <m3zmvaua9y.fsf@reason.gnuhh-core> (raw)
In-Reply-To: <m31x8o8zs1.fsf@brain.gnuhh.org> (Georg C. F. Greve's message of "Tue, 03 May 2005 10:44:14 +0200")
[-- Attachment #1.1: Type: text/plain, Size: 222 bytes --]
|| On Tue, 03 May 2005 10:44:14 +0200
|| "Georg C. F. Greve" <greve@gnu.org> wrote:
gg> b) fix the caching of PINs
Fortunately, I was able to resolve this one myself.
Patch attached.
Regards,
Georg
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: pgg-gpg.patch --]
[-- Type: text/x-patch, Size: 685 bytes --]
--- pgg-gpg.el.orig 2005-05-03 14:55:30.000000000 +0200
+++ pgg-gpg.el 2005-05-04 12:03:44.000000000 +0200
@@ -99,13 +99,13 @@
(if (and pgg-cache-passphrase
(progn
(goto-char (point-min))
- (re-search-forward "^\\[GNUPG:] GOOD_PASSPHRASE\\>" nil t)))
+ (re-search-forward "^\\[GNUPG:] \\(GOOD_PASSPHRASE\\>\\)\\|\\(SIG_CREATED\\)" nil t)))
(pgg-add-passphrase-cache
(or key
(progn
(goto-char (point-min))
(if (re-search-forward
- "^\\[GNUPG:] NEED_PASSPHRASE \\w+ ?\\w*" nil t)
+ "^\\[GNUPG:] NEED_PASSPHRASE\\(_PIN\\)? \\w+ ?\\w*" nil t)
(substring (match-string 0) -8))))
passphrase)))
[-- Attachment #1.3: Type: text/plain, Size: 226 bytes --]
--
Georg C. F. Greve <greve@gnu.org>
Free Software Foundation Europe (http://fsfeurope.org)
Join the Fellowship and protect your freedom! (http://www.fsfe.org)
[-- Attachment #2: Type: application/pgp-signature, Size: 306 bytes --]
next prev parent reply other threads:[~2005-05-04 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 8:44 Georg C. F. Greve
2005-05-04 18:16 ` Georg C. F. Greve [this message]
2005-05-09 19:25 ` Simon Josefsson
2005-05-11 9:11 ` Georg C. F. Greve
2005-05-12 15:48 ` PGG/GPG Integration bug (somewhat nasty & urgent), potential Werner Koch
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=m3zmvaua9y.fsf@reason.gnuhh-core \
--to=greve@gnu.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).