On Wed, Mar 14, 2001 at 10:17:31AM +0100, Thomas Roessler wrote:
> On 2001-03-13 18:47:45 +0100, Rejo Zenger wrote:
>
> > set pgp_encrypt_sign_command="pgpewrap gpg --passphrase-fd 0 -v --batch
> > --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r
> > -- %f"
>
> Add "--textmode" behind "--encrypt --sign".
I saw the "--always-trust" and hoped that setting the similar
"completes_needed = 0" in pgp 6.5.8 would fix the problem with
encryption (and encryption and signing). Alas, I had already set it
with no change.
There is a bug in Mutt or pgp6.rc: When encrypting to an untrusted key
pgp 6.5.8 prompts for confirmation that the untrusted key should be
used. The default response is "N" and when "y" is entered it is
apparently not sent to pgp so the encryption fails.
An ugly hack to make it work is to remove "+batchmode" from the
encrypt and encrypt & sign sections in pgp6.rc. This results in pgp
waiting for a response (with no prompt message) after "y" is entered,
so another "y" and <enter> can be blindly (there is no prompt or key
echo) entered and the encryption proceeds without error.
Is there some simple way to feed the first "y" to pgp so this ugly
hack can be avoided?
Is it fixed in the development version?
This is the third time I've posted about this without responses. As
far as I can tell, the problem exists for everyone who tries to use
pgp 6.5.8 with Mutt.
TIA,
-rex
