From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Nick Anderson <nick@cmdln.org>
Cc: "Org Mode List" <emacs-orgmode@gnu.org>,
"Grégoire Jadi" <gregoire.jadi@univ-nantes.fr>
Subject: Re: org-crypt & multiple recipients
Date: Tue, 27 Oct 2015 14:20:30 +0000 [thread overview]
Message-ID: <874mhcz93l.fsf@ucl.ac.uk> (raw)
In-Reply-To: <562E82BC.1080101@cmdln.org> (Nick Anderson's message of "Mon, 26 Oct 2015 14:45:00 -0500")
On Monday, 26 Oct 2015 at 14:45, Nick Anderson wrote:
[...]
> But I guess I don't understand why there would have to be a header for
> each recipient (other than current implementation limitations with
> org-crypt).
>
> Currently the CRYPTKEY property identifies the email address or KEY that
> you want to encrypt for. If I have multiple of the same property the one
> that is listed first seems to be used.
>
> What if there were a CRYPTKEYS property that took a space separated list
> of keys or emails?
The logic, AFAIK, is that the main text is encrypted with a so-called
session key. The key for this is then encrypted for each recipient
using their public key and only they can decrypt (with their private
key) this element, called a header. Therefore, if you have multiple
recipients, you need multiple headers, i.e. multiple copies of the
session key each encrypted for a single recipient.
I hope this makes sense.
No matter how you do it, encrypting some text for multiple recipients
using PKI requires multiple copies of something, whether the original
text or a key used to encrypt that text.
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.2, Org release_8.3.2-209-gba4d33
prev parent reply other threads:[~2015-10-27 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 23:39 org-crypt & multiple recipients Nick Anderson
2015-10-26 8:54 ` Eric S Fraga
2015-10-26 9:21 ` Grégoire Jadi
2015-10-26 11:24 ` Eric S Fraga
2015-10-26 19:45 ` Nick Anderson
2015-10-27 14:20 ` Eric S Fraga [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874mhcz93l.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=gregoire.jadi@univ-nantes.fr \
--cc=nick@cmdln.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).