|author||Daniel Kahn Gillmor <firstname.lastname@example.org>||2019-07-25 12:38:52 -0400|
|committer||Sean Whitton <email@example.com>||2019-07-29 07:38:09 +0100|
Hopefully this tool is useful for other people, not just for myself and Anarcat. Signed-off-by: Daniel Kahn Gillmor <firstname.lastname@example.org>
Diffstat (limited to 'email-extract-openpgp-certs.1.pod')
1 files changed, 57 insertions, 0 deletions
diff --git a/email-extract-openpgp-certs.1.pod b/email-extract-openpgp-certs.1.pod
new file mode 100644
@@ -0,0 +1,57 @@
+email-extract-openpgp-certs - extract OpenPGP certificates from an e-mail
+B<email-extract-openpgp-certs> < B<message.eml> | B<gpg> B<--import>
+B<email-extract-openpgp-certs> extracts all the things it can find
+that look like they might be OpenPGP certificates in an e-mail, and
+produces them on standard output.
+It currently knows about how to find OpenPGP certificates as
+attachments of MIME type application/pgp-keys, and Autocrypt: style
+ $ notmuch show --format-raw id:email@example.com > test.eml
+ $ email-extract-openpgp-certs < test.eml | gpg --import
+B<email-extract-openpgp-certs> currently does not try to decrypt
+encrypted e-mails, so it cannot find certificates that are inside the
+message's cryptographic envelope.
+B<email-extract-openpgp-certs> does not attempt to validate the
+certificates it finds in any way. It does not ensure that they are
+valid OpenPGP certificates, or even that they are of a sane size. It
+doeds not try to establish any relationship between the extracted
+certificates and the messages in which they are sent. For example, it
+does not check the Autocrypt addr= attribute against the message's From:
+Importing certificates extracted from an arbitrary e-mail in this way
+into a curated keyring is not a good idea. Better to extract into an
+ephemeral location, inspect, filter, and then selectively import.
+=head1 SEE ALSO
+gpg(1), https://autocrypt.org, https://tools.ietf.org/html/rfc4880, https://tools.ietf.org/html/rfc3156
+B<email-extract-openpgp-certs> and this manpage were written by Daniel
+Kahn Gillmor, with guidance and advice from many others.