From: Robert Pluim <rpluim@gmail.com>
To: Colin Baxter <m43cap@yandex.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: epa and keys
Date: Mon, 11 May 2020 16:23:09 +0200 [thread overview]
Message-ID: <m2h7wmft4i.fsf@gmail.com> (raw)
In-Reply-To: <878shydceq.fsf@yandex.com> (Colin Baxter's message of "Mon, 11 May 2020 10:54:53 +0100")
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
>>>>> On Mon, 11 May 2020 10:54:53 +0100, Colin Baxter <m43cap@yandex.com> said:
Colin> Hello,
Colin> I want to sign an email (mail mode, not message mode) using M-x
Colin> epa-mail-sign <RET>.
Colin> I would have expected to have been presented with a list of keys from
Colin> which to choose, but, instead, I am asked to enter my password for the
Colin> first key in my key-ring. (The first key is effectively the default, if
Colin> no default key is explicitly set). Unfortunately, I want to sign with
Colin> another key in my key-ring.
Colin> How can I force epa to present me with a choice of keys rather than the
Colin> first? I am using gpg (GnuPG) 2.0.26.
C-u M-x epa-mail-sign
should do that, which is not described in the docstring nor in the
manual. Thereʼs an epa-mail-mode minor mode as well with more
convenient bindings for the signing and encrypting commands.
Iʼd recommend message-mode and mml-secure-sign-pgp, but that has other
annoying bugs in its unconfigured state that I haven't fixed yet.
Robert
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCAAvFiEEq83Vx/IYGRGbZc3zPXrkx5EPYUAFAl65X84RHHJwbHVpbUBn
bWFpbC5jb20ACgkQPXrkx5EPYUB4XxAAuuVuPWOzyi8EYa9t8EWx+V8QI9oB0N7G
vfqpyqKgETUZUCpTyuWhUFTZ/TJZYZ5DKUXIOu6F4Bdsex9+Au//IfOMdz+xqBzk
Mu82mkj1svdBljuabAKUmnY/Pm6PYINZyNd9J8pZEJk3lagJGOHG9lA8SSwp2Z0G
U8AGuHAp2iCbyNbBqw0pflKItih7amD7maKaiiCHW0NWVlv2oi4LTV24UOWCoee7
Q8sxpsdRGY5iRPwH5UixT8hLns7vKY279LvnfPxHzDM3uF9muSQReceB5DbfY4xK
C5nyVLTJyPqgoeaBNcvAJLtZWpZlufyF68Ko8jqDOv3UXvaYkoq1HvAs8OzFCvXO
aW+xLuFrIc/m/02RPiUKMN+V/rilbpfWo7Nf1CEttCWrprz9OdFI784dQ5A9H/bP
F2YhEKgQklLM8EyHM715GVvITytHgDNTCVdABeuN9XlFgEkaS8PeT3gyomPapJLD
6a36ZKJGJycH8fzgxG5D+c8H1gZj2np4WOumcKDB/GZsHhwCJQO0VdTRo8CLa179
mRhYMOCagbGsx+LroToqysnZEMDilOoZzNTckQud6PQ8ZiKDv2NljN4g8jQbFBT1
5lIIePlGIRRLYUItNbPMxLAq7tMooDsYivrxqV/jISZhRiyNE+mYVf+Eba7kcK9W
oGLxcJpRMTg=
=0Y9z
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2020-05-11 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 9:54 epa and keys Colin Baxter
2020-05-11 14:23 ` Robert Pluim [this message]
2020-05-11 14:48 ` Colin Baxter
2020-05-12 7:32 ` Robert Pluim
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2h7wmft4i.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=m43cap@yandex.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).