From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Jones Subject: Re: org-crypt and PROPERTIES location Date: Fri, 20 Mar 2009 11:27:49 -0600 Message-ID: <86fxh8xfxm.fsf@pmade.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LkiVs-0005Tu-6o for emacs-orgmode@gnu.org; Fri, 20 Mar 2009 13:28:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LkiVn-0005SB-Fe for emacs-orgmode@gnu.org; Fri, 20 Mar 2009 13:28:07 -0400 Received: from [199.232.76.173] (port=52778 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LkiVn-0005S7-BA for emacs-orgmode@gnu.org; Fri, 20 Mar 2009 13:28:03 -0400 Received: from main.gmane.org ([80.91.229.2]:52374 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LkiVm-0004Rq-Rb for emacs-orgmode@gnu.org; Fri, 20 Mar 2009 13:28:03 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LkiVl-00081d-PA for emacs-orgmode@gnu.org; Fri, 20 Mar 2009 17:28:01 +0000 Received: from 75-166-120-184.hlrn.qwest.net ([75.166.120.184]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 20 Mar 2009 17:28:01 +0000 Received: from mlists by 75-166-120-184.hlrn.qwest.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 20 Mar 2009 17:28:01 +0000 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Carsten Dominik writes: > we don't have a good function for this. Also, it is not so much about > extracting the contents, more about finding the boundaries. In some > ways I think it would actually be better to use a tag for encryption > instead of a property, because this would allow to encrypt everything > except the headline. What about we change this to a tag crypt_KEY? > Hmm, I am not sure if encryption keys would make valid tags..... AFAIK, the key ID is only needed for encryption. The encrypted text will contain a pointer to the key needed for decryption. Therefore, I suggest that we do this: - Have a defcustom for the default key ID to use (I think it will be very common that you'll use the same key to encrypt everything) - Allow overriding the key ID in an inheritable property (if you need to encrypt a heading using a different key than the default) - Use a tag matcher to specify headings to encrypt (another defcustom that will be used to find headings that should be encrypted before-save) - Encrypt everything under the heading, including properties (even if the property has the key ID, it won't be needed for decryption, so the entire contents can be encrypted) Am I missing anything? > I'd very much like to see this improved and stabilized, so that we can > include this with Org, this would be valuable to have. I am sure John > would not mind if you did the final steps with it. Am I right, John? I had a private conversation with John, and he's completely open to me putting the finishing touches on org-crypt and getting it included in the org distribution. Are there any org-crypt users out there that want to throw in their $0.02? -- Peter Jones, http://pmade.com pmade inc. Louisville, CO US