From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Anderson Subject: Re: org-crypt & multiple recipients Date: Mon, 26 Oct 2015 14:45:00 -0500 Message-ID: <562E82BC.1080101@cmdln.org> References: <562D6820.9070203@cmdln.org> <87a8r66mcc.fsf@pinto.chemeng.ucl.ac.uk> <87611u9e8f.fsf@univ-nantes.fr> <874mhdc1pm.fsf@pinto.chemeng.ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43863) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zqnhi-0003YQ-2c for emacs-orgmode@gnu.org; Mon, 26 Oct 2015 15:45:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zqnhd-0008AR-3J for emacs-orgmode@gnu.org; Mon, 26 Oct 2015 15:45:14 -0400 Received: from mail-lf0-x235.google.com ([2a00:1450:4010:c07::235]:35555) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zqnhc-0008A9-Q0 for emacs-orgmode@gnu.org; Mon, 26 Oct 2015 15:45:09 -0400 Received: by lfbn126 with SMTP id n126so126850994lfb.2 for ; Mon, 26 Oct 2015 12:45:07 -0700 (PDT) In-Reply-To: <874mhdc1pm.fsf@pinto.chemeng.ucl.ac.uk> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: =?UTF-8?Q?Gr=c3=a9goire_Jadi?= , Org Mode List On 10/26/2015 06:24 AM, Eric S Fraga wrote: > On Monday, 26 Oct 2015 at 10:21, Grégoire Jadi wrote: >> GPG supports multiple-recipient with --recipient > > I stand corrected! Thanks. Interesting hybrid encryption approach. > > However, although the main text is not copied, the header (which has the > session key, as it is called, used to encrypt the main text) is so there > will need to be a structure which has the multiple headers, one for each > recipient, in the org file. Thanks for the link describing the multiple-recipient handling, good read. 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?