From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Uday S Reddy Newsgroups: gmane.emacs.help Subject: Re: can emacs use the mac os x keychain? Date: Mon, 26 Jul 2010 15:47:30 +0100 Organization: Janet Usenet Reading Service. Message-ID: References: <370a1897-25aa-418f-9631-1570dfa99de3@z7g2000yqb.googlegroups.com> <87633kaess.fsf@lifelogs.com> <8d7c78ee-6ba8-448a-8f86-3d585e1af77f@u32g2000vbc.googlegroups.com> <87vd8z2myy.fsf@lifelogs.com> <01ea3506-d715-491d-b360-3abf34e98013@i31g2000yqm.googlegroups.com> <87r5iq1hjk.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1291851742 12339 80.91.229.12 (8 Dec 2010 23:42:22 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 8 Dec 2010 23:42:22 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Dec 09 00:42:18 2010 Return-path: Envelope-to: geh-help-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 1PQTeM-0000yt-E8 for geh-help-gnu-emacs@m.gmane.org; Thu, 09 Dec 2010 00:42:18 +0100 Original-Received: from localhost ([127.0.0.1]:56692 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PQTdD-0000B6-HI for geh-help-gnu-emacs@m.gmane.org; Wed, 08 Dec 2010 18:41:07 -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!82.197.223.108.MISMATCH!feeder2.cambriumusenet.nl!feed.tweaknews.nl!192.87.166.28.MISMATCH!tudelft.nl!txtfeed1.tudelft.nl!dedekind.zen.co.uk!zen.net.uk!hamilton.zen.co.uk!feed4.jnfs.ja.net!jnfs.ja.net!times.reader.netnews.ja.net!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 30 Original-NNTP-Posting-Host: acws-0068.cs.bham.ac.uk Original-X-Trace: north.jnrs.ja.net 1280155651 28052 147.188.194.56 (26 Jul 2010 14:47:31 GMT) Original-X-Complaints-To: usenet@north.jnrs.ja.net Original-NNTP-Posting-Date: Mon, 26 Jul 2010 14:47:31 +0000 (UTC) User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) In-Reply-To: <87r5iq1hjk.fsf@lifelogs.com> Original-Xref: usenet.stanford.edu gnu.emacs.help:180074 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:76210 Archived-At: Ted Zlatanov wrote: > USR> Another question that I always wondered about. Does auth-source allow > USR> for multiple logins on the same server/protocol combination? > > Not currently. The first one found is picked IIRC. I think it would > make the UI significantly more complex to allow multiples and perhaps > confuse users. The advanced users that need that can typically use > aliases for the server name. Do you see a need for it? Yes, I think it is needed. Some people maintain multiple email accounts on ISP's like gmail, hotmail etc. In organizations, it is common for people to have a personal email account and, separately, one or more role-based or team email accounts (techsupport, sales, admissions, ...). I know that many novice users might find it hard to deal with it. But, gmail and hotmail are educating them fast. So, yes, restricting to single email accounts per server would be a serious limitation. I am not sure what you mean by UI getting complex. The only user interaction seems to be to ask for a passphrase. (There is a problem at the moment because it doesn't say passphrase for which auth-source. So, if somebody happens to use multiple auth-sources with different passphrases, they would be in trouble!) If you instead mean the API getting complex, one could call auth-source-user-or-password with '("login" "password") as the MODE and get back a list of results. A simple `assoc' would give the desired password. Cheers, Uday