From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: Signing messages (pgpmime)
Date: Fri, 27 Nov 2015 21:39:48 +0100 [thread overview]
Message-ID: <877fl3ch2j.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87k2p3urb5.fsf@tullinup.koldfront.dk> ("Adam =?utf-8?Q?Sj?= =?utf-8?Q?=C3=B8gren=22's?= message of "Fri, 27 Nov 2015 21:21:18 +0100")
Adam writes:
> I have had pgpmime working flawlessly (with my OpenPGP-card and
> card-reader) previously, but it is very seldom I use it.
>
> Today when I wanted to sign an outgoing message, I chose "Sign Message"
> in the menu, and after pressing C-c C-c I was prompted for the pin, and
> the cardreader blinked as it usually does.
>
> But then I got these errors:
>
> Sending...
> Generating hashcash...done
> Mark set [2 times]
> error in process filter: Process epg not running [2 times]
> mml2015-sign: Wrong type argument: char-or-string-p, nil
Hm, setting epg-debug to t and looking in *epg-debug* I see that the
pin I enter isn't tranferred correctly:
[GNUPG:] NEED_PASSPHRASE_PIN OPENPGP 1 D276000124010101000100000BDD0000/C40B1B7D09A9326AFD181FB7B728D4441E65DD19
[GNUPG:] GET_HIDDEN passphrase.pin.ask
[GNUPG:] GOT_IT
gpg: PIN for CHV1 is too short; minimum length is 6
[GNUPG:] SC_OP_FAILURE 2
gpg: signing failed: bad passphrase
gpg: signing failed: bad passphrase
I'm pretty sure I'm typing the pin correctly, as decryption works...
Hm.
Best regards,
Adam
--
"I'm only civil because I don't know any swear words." Adam Sjøgren
asjo@koldfront.dk
next prev parent reply other threads:[~2015-11-27 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 20:21 Adam Sjøgren
2015-11-27 20:39 ` Adam Sjøgren [this message]
2015-11-27 20:43 ` Adam Sjøgren
2015-11-27 20:50 ` Adam Sjøgren
2015-11-27 22:25 ` Signing messages (pgpmime) [solved] Adam Sjøgren
2015-11-28 6:25 ` Teemu Likonen
2015-11-28 10:11 ` Adam Sjøgren
2015-11-28 11:36 ` Teemu Likonen
2015-11-28 11:49 ` Adam Sjøgren
2015-11-28 12:16 ` Adam Sjøgren
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=877fl3ch2j.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=ding@gnus.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).