From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.bugs Subject: Re: bug#7487: 24.0.50; Gnus nnimap broken Date: Wed, 15 Dec 2010 08:39:18 -0600 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <877hfb14o9.fsf@lifelogs.com> References: <8739q54g7x.fsf@lifelogs.com> <8762uxob2f.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1292424023 26068 80.91.229.12 (15 Dec 2010 14:40:23 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 15 Dec 2010 14:40:23 +0000 (UTC) To: bug-gnu-emacs@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Dec 15 15:40:19 2010 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PSsWX-0002xT-Ua for geb-bug-gnu-emacs@m.gmane.org; Wed, 15 Dec 2010 15:40:18 +0100 Original-Received: from localhost ([127.0.0.1]:41648 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PSsWW-0000l3-9B for geb-bug-gnu-emacs@m.gmane.org; Wed, 15 Dec 2010 09:40:08 -0500 Original-Path: usenet.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!newsgate.news.xs4all.nl!news2.euro.net!newsfeed.freenet.ag!news.albasani.net!not-for-mail Original-Newsgroups: gnu.emacs.bug Original-Lines: 40 Original-X-Trace: news.albasani.net eEjR9RyrSnf59DcVFLJmZCGmmw19QZQTNOmVUyDpw7RCFb7ZbU1RGpTcX0YiRr88OkLaPpZ/bv9v3ctuMsqglSeotJeXAcgDFXUTlY4EMaKs4TInWlPQb3NZfQD5Igc1 Original-NNTP-Posting-Date: Wed, 15 Dec 2010 14:39:23 +0000 (UTC) X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Cancel-Lock: sha1:1eKlelv0QqAZmwfc3LE8awyjGXc= sha1:3OPyD6uiDVMXhlr2hsgzF1d0YJQ= User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux) Injection-Info: news.albasani.net; logging-data="xFN6/GrQy9Xb7piL4W6MN2zjLcHLsp/z9wHgatLYan90Uo/5GB58wUtmmp7aV3ozWBKhrJYnREwEoGL/whJBYifEMPsrZKIyxyD/oMas+a3j5BduLyaCrlbxDjsOJFuc"; mail-complaints-to="abuse@albasani.net" Original-Xref: usenet.stanford.edu gnu.emacs.bug:69853 X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:42535 Archived-At: On Wed, 15 Dec 2010 11:06:42 +0900 Daiki Ueno wrote: DU> BTW, I forgot to mention in the previous response, I think it overkill DU> to make epa-file to encrypt files with symmetric encryption by default, DU> because as long as a file is visited in a buffer, epa-file remembers the DU> last used encryption method (in epa-file-encrypt-to local variable), DU> which will be used on the next save-buffer. So a user should see the DU> key selection UI only the first time she saves the buffer. DU> Default symmetric might be useful when Emacs does visit/save/kill-buffer DU> repeatedly, but I think it is a rare case. I agree. The user may not even know the implications of symmetric encryption. So IMHO this should be an external option (maybe requested by setting `epa-file-encrypt-to' to 'ask if it's nil) which would change the current key selection UI as follows (this is a refinement of my previous UI proposal): 1) show prompt "Do you want to encrypt %s with a passphrase (symmetric) or with a specific key? (p/k/P/K/h)" 2) on `h', show some help, mentioning for instance that this question is asked only once per file and link to the EPA manual 3) on `p', proceed without the key selection UI 4) on `k', proceed with the current key selection UI 5) on `P' or `K', save the choice as a new customized default for `epa-file-encrypt-to' All of this shouldn't involve auth-source.el beyond setting `epa-file-encrypt-to' to 'ask if it's nil. That way other packages can use this same approach. So this inconveniences users at least once, but gives them a chance to understand what's going on, and with `P' will not be asked again. What do you think? Ted