From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastien Vauban" Subject: Re: disable "org-decrypt: auto-save-mode may cause leakage" Date: Thu, 14 Jul 2011 16:42:58 +0200 Message-ID: <808vs0hqj1.fsf@somewhere.org> References: <2011-07-14T14-11-51@devnull.Karl-Voit.at> <20110714131745.GC2823@soloJazz.com> <80hb6pgezl.fsf@somewhere.org> <87bowxym68.fsf@praet.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: 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-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Hi Pieter, Pieter Praet wrote: > On Thu, 14 Jul 2011 15:37:34 +0200, "Sebastien Vauban" wrote: >> Juan Pechiar wrote: >> > On Thu, Jul 14, 2011 at 02:22:32PM +0200, Karl Voit wrote: >> >> How can I auto-answer the question from the subject line with =C2=ABn= =C2=BB >> >> (per default) any time it is asked? >> > >> > You can customize this behaviour via >> > >> > org-crypt-disable-auto-save >> > >> > You probably have it set to 'ask'. >>=20 >> So did I. This is the default. >>=20 >> > Options exist for always enabling/disabling auto save, and for encrypt= ing >> > the auto-saved version automatically. >> > >> > M-x customize-variable RET org-crypt-disable-auto-save RET >>=20 >> Shouldn't its default value better be set to 'encrypt? > > I don't think so. > > It only re-encrypts entries which are tagged :crypt: (or whatever you > have `org-crypt-tag-matcher' set to), so I'd prefer users to be "forced" > to at least read the docstring so as not to be using it with a false > sense of security. > > Though this could be easily solved by automatically tagging entries upon > encryption, I think it's more "considerate" to simply (ask to) disable > `auto-save-mode' for the current buffer, as it's quite annoying to have > an entry get re-encrypted while you're in the middle of typing something. This is more clear to me, and makes a lot of sense. Though, what I find annoying, and the OP as well, is to be asked that quest= ion for buffers which do not contain any encrypted entry. Would it be possible = to scan the buffer for such entries, and only ask the user when the buffer is potentially exposed? Best regards, Seb --=20 Sebastien Vauban