From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tom Tromey Newsgroups: gmane.emacs.devel Subject: Re: Moving files from lisp/gnus/ to lisp/net/? Date: Sat, 10 Nov 2007 12:53:47 -0700 Message-ID: References: <2366.81.51.30.174.1098020712.squirrel@yxa.extundo.com> <87y7dd2e0f.fsf@mocca.josefsson.org> Reply-To: tromey@redhat.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1194725953 22322 80.91.229.12 (10 Nov 2007 20:19:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 10 Nov 2007 20:19:13 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org To: Simon Josefsson Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 10 21:19:17 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IqwnU-0007bP-DT for ged-emacs-devel@m.gmane.org; Sat, 10 Nov 2007 21:19:16 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IqwnI-0000H5-R1 for ged-emacs-devel@m.gmane.org; Sat, 10 Nov 2007 15:19:04 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IqwnF-0000GK-Pd for emacs-devel@gnu.org; Sat, 10 Nov 2007 15:19:01 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IqwnB-0000FO-8p for emacs-devel@gnu.org; Sat, 10 Nov 2007 15:19:01 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IqwnB-0000FL-56 for emacs-devel@gnu.org; Sat, 10 Nov 2007 15:18:57 -0500 Original-Received: from mx1.redhat.com ([66.187.233.31]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Iqwn6-00055i-J1; Sat, 10 Nov 2007 15:18:52 -0500 Original-Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.1) with ESMTP id lAAKIk9R032251; Sat, 10 Nov 2007 15:18:46 -0500 Original-Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id lAAKIkJa001424; Sat, 10 Nov 2007 15:18:46 -0500 Original-Received: from opsy.redhat.com (ton.yyz.redhat.com [10.15.16.15]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id lAAKIZvj009691; Sat, 10 Nov 2007 15:18:38 -0500 Original-Received: by opsy.redhat.com (Postfix, from userid 500) id 8306C378320; Sat, 10 Nov 2007 12:53:47 -0700 (MST) X-Attribution: Tom In-Reply-To: <87y7dd2e0f.fsf@mocca.josefsson.org> (Simon Josefsson's message of "Mon\, 05 Nov 2007 11\:16\:48 +0100") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.990 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:82915 Archived-At: >>>>> "Simon" == Simon Josefsson writes: Simon> Another point of view is that several parts of Emacs already contains Simon> code to cache passwords. Reducing that code duplication is what Simon> triggered me to write password.el. I also wrote something along these lines. I just never got around to hooking it up to all the places in Emacs that ask for passwords. Emacs is about the only major program I use any more that doesn't have some kind of keyring support... Simon> The existing `read-passwd' API is not suitable for password.el, Simon> because each password needs to be associated with an Simon> application-dependent 'key'. Yeah. In my approach, I used an alist for the key, as this fit better with what the Gnome keyring uses. I also wrote a little utility program so that Emacs could easily talk to the keyring... if you want that, I'm happy to send it along. Simon> Regarding naming, possibly `password-read-and-cache' should be removed. Simon> The problem with it is that it enters passwords into the cache without Simon> allowing applications to verify that the password is correct. However, Simon> applications could detect this and use `password-cache-remove', but it Simon> seems less reliable to me. I agree. Forgetting to remove a bad password is less friendly than forgetting to add a good one. Tom