kyle at memoryhole
Jul 20, 2006, 5:09 PM
Views: 1461
Permalink
|
|
1.4.4 unable to reopen standard input error
|
|
Hello,
I recently upgraded gnupg from 1.4.2 to 1.4.4, and suddenly I am
running into a nasty problem.
I use mutt on MacOS X (10.4.7) for all my email needs, and one of the
things I can do (well, used to be able to do) is decode and reply to
“traditional” pgp-encoded email (a-la what is generated by pine users
who send encrypted email). After upgrading gnupg, I can no longer
reply to emails that have been encrypted in the “traditional”
(translation: inline ascii) manner. I can decrypt them just fine, but
whatever re-decryption mutt does when replying merely produces:
gpg: fatal: unable to reopen standard input, output, or error
The command that mutt runs to decode such email is this:
gpg --status-fd=2 --no-verbose --quiet --batch --output - %f
Where "%f" is replaced by the name of the file to decrypt (mutt saves
the encrypted message to a file and then runs gpg on it).
I understand there was a patch that went into gnupg 1.4.4
(http://lists.gnupg.org/pipermail/gnupg-devel/2006-May/022915.html
patch-stdout.reopen.patch) that may have something to do with this. Is
there anything I can do to fix this? I'm tempted to track down that
patch and reverse it on my 1.4.4 source, to see if that doesn't fix
it.
Interestingly, other people on the mutt mailing lists who also use
gnupg 1.4.4 (but do so on Linux) do not have the problem.
~Kyle
--
He who dares not offend cannot be honest.
-- Thomas Paine
|
1.4.4 unable to reopen standard input error
