From: "Grégoire Jadi" <gregoire.jadi@univ-nantes.fr>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: Org Mode List <emacs-orgmode@gnu.org>, Nick Anderson <nick@cmdln.org>
Subject: Re: org-crypt & multiple recipients
Date: Mon, 26 Oct 2015 10:21:52 +0100 [thread overview]
Message-ID: <87611u9e8f.fsf@univ-nantes.fr> (raw)
In-Reply-To: <87a8r66mcc.fsf@pinto.chemeng.ucl.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
Eric S Fraga writes:
> On Sunday, 25 Oct 2015 at 18:39, Nick Anderson wrote:
>> I was playing with org-crypt today and it's pretty nifty.
>>
>> While encrypting things for myself is the primary use case, I have other
>> team members that also use org-mode. It occurred to me that it would be
>> neat if I could specify a list of users to encrypt a node for. Then we
>> could share an org file and a node could be decrypted by individual.
>
> This is fundamentally difficult with a public key encryption system: you
> would have to have separate copies of the encrypted text, one for each
> recipient?
>
> Maybe you could have a separate private/public key pair that is shared
> for group work instead?
GPG supports multiple-recipient with --recipient
See
https://stackoverflow.com/questions/597188/encryption-with-multiple-different-keys/23725786#23725786
And the answer below explains how GPG/PGP does to not have to copy the
text for each recipient.
https://stackoverflow.com/questions/597188/encryption-with-multiple-different-keys/28206835#28206835
Best,
--
Grégoire Jadi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2015-10-26 9:22 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 [this message]
2015-10-26 11:24 ` Eric S Fraga
2015-10-26 19:45 ` Nick Anderson
2015-10-27 14:20 ` Eric S Fraga
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=87611u9e8f.fsf@univ-nantes.fr \
--to=gregoire.jadi@univ-nantes.fr \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.