From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: Modifying Emacs to use the Mac OS X Keychain Services Date: Sun, 05 Jun 2011 15:01:37 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <878vtgnj32.fsf@lifelogs.com> References: Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1307304138 4567 80.91.229.12 (5 Jun 2011 20:02:18 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 5 Jun 2011 20:02:18 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jun 05 22:02:14 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QTJWW-00032s-Cd for ged-emacs-devel@m.gmane.org; Sun, 05 Jun 2011 22:02:12 +0200 Original-Received: from localhost ([::1]:47152 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QTJWV-0003WF-Dk for ged-emacs-devel@m.gmane.org; Sun, 05 Jun 2011 16:02:11 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:42032) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QTJWH-0003WA-2l for emacs-devel@gnu.org; Sun, 05 Jun 2011 16:01:58 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QTJWF-0000T5-Pc for emacs-devel@gnu.org; Sun, 05 Jun 2011 16:01:56 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:58811) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QTJWF-0000Sl-DZ for emacs-devel@gnu.org; Sun, 05 Jun 2011 16:01:55 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QTJWC-0002wQ-Kp for emacs-devel@gnu.org; Sun, 05 Jun 2011 22:01:52 +0200 Original-Received: from c-67-186-102-106.hsd1.il.comcast.net ([67.186.102.106]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 05 Jun 2011 22:01:52 +0200 Original-Received: from tzz by c-67-186-102-106.hsd1.il.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 05 Jun 2011 22:01:52 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 32 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: c-67-186-102-106.hsd1.il.comcast.net 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" Mail-Copies-To: never User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:aIgL/k9v2avJXaoOAox+3M540l8= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 80.91.229.12 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:140211 Archived-At: On Sun, 5 Jun 2011 13:54:20 -0500 Ben Key wrote: BK> As I mentioned before, I am attempting to add ns-keychain functions that BK> match the secrets.el API as closely as possible. I am adding a ns-keychain BK> function for each secrets- function that has the same parameters as the BK> secrets- function. So far in my work, I have been mapping the collection BK> parameter to the serviceName parameter of the various Keychain Services API BK> functions. By default, I am using the default Keychain to store the data BK> but adding a user configurable option to allow another keychain file to be BK> used. Right, so the name of the collection is the serviceName as far as the OS is concerned. That means it could be stored anywhere, right? BK> But, after taking another look at auth-source.el, I am wondering if this was BK> the correct design decision. I am wondering if I should instead be BK> interpreting the collection parameter as an indication of which keychain BK> file to store the passwords in. I could interpret the value "default" for BK> the collection parameter as an indication that the default keychain should BK> be used. I could interpret the value "Login" or "secrets:Login" as an BK> indication that the Login keychain should be used. Other values for BK> collection parameter could be interpreted as an indication that the data BK> should be stored in a file {collection}.keychain in ~/Library/Keychains. BK> Which interpretation of the collection parameter is the correct one? I ask BK> because I want to be sure to get this right. Does the user care what file it's stored in? Can you have any serviceName in any file, or is there some connection or dependency between the two? Ted