From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ben Key Newsgroups: gmane.emacs.devel Subject: Re: Modifying Emacs to use the Mac OS X Keychain Services Date: Fri, 10 Jun 2011 19:30:31 -0500 Message-ID: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: dough.gmane.org 1307752272 782 80.91.229.12 (11 Jun 2011 00:31:12 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 11 Jun 2011 00:31:12 +0000 (UTC) To: Emacs Development , Ted Zlatanov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 11 02:31:08 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 1QVC6W-0000jq-Ag for ged-emacs-devel@m.gmane.org; Sat, 11 Jun 2011 02:31:08 +0200 Original-Received: from localhost ([::1]:49771 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QVC6V-0004Q6-8N for ged-emacs-devel@m.gmane.org; Fri, 10 Jun 2011 20:31:07 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:54646) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QVC6I-0004Q0-D3 for Emacs-devel@gnu.org; Fri, 10 Jun 2011 20:30:55 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QVC6H-00053z-Ja for Emacs-devel@gnu.org; Fri, 10 Jun 2011 20:30:54 -0400 Original-Received: from mail-bw0-f41.google.com ([209.85.214.41]:62678) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QVC6H-00053v-DM for Emacs-devel@gnu.org; Fri, 10 Jun 2011 20:30:53 -0400 Original-Received: by bwz17 with SMTP id 17so3285555bwz.0 for ; Fri, 10 Jun 2011 17:30:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:from:date:message-id:subject:to :content-type; bh=uhU5ANN32BQ6kXpV+52Mx17mp7LkwNiXwKLhJXn8i9s=; b=Wvr2rGNFQQjd1y65aAcuNIEDO9PcQvrRwjWRYM3mZKsAWxmqoyO9o+pBaN+tKTU4H8 czuFSaHXM089HnmAvBt32sQXyV+KRs41YvUnBHyacpmxP58PzeDCm4LuAceM8rqwwguq ENut12TbX0YE477aVIPAswRgAPUciBBkjIKuI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=umNJdjxMyT168jkR6sv4UEf8jXNed7RPpdGVCacqM6Zb7QDI+Qgsd3sgJMLDh1qhY9 pUHj9LY5i5bGX7LzjYGg/cEWpnjdtp37iP6joqkcVdrPP1uhPZ5eAB20PYnRZmiRpwhQ 66yrfA7GF8R9l9UB5Tjq1WNWFrz6nbJt/Aev8= Original-Received: by 10.204.26.200 with SMTP id f8mr2353280bkc.99.1307752251211; Fri, 10 Jun 2011 17:30:51 -0700 (PDT) Original-Received: by 10.204.59.212 with HTTP; Fri, 10 Jun 2011 17:30:31 -0700 (PDT) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.214.41 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:140360 Archived-At: Hello, Ted Zlatanov wrote: > Please throw an error if the requested keychain doesn't exist, same as > above. It may be more useful to only throw the error for the "session" or "secrets:session" values for the keychain parameter and to handle values other than "login," "secrets:Login," "default," "secrets:default," "session", or "secrets:session" as an indication that a keychain file named ~/Library/Keychains/{keychain}.keychain should be used. If this keychain file exists, I can open it using SecKeychainOpen. If the keychain file does not exist I can create it with SecKeychainCreate. What do you think of this idea? > Don't be afraid of diverging from the Secrets API. The Keychain > Services API is not the same thing, we know that. Please add that > parameter to the calls. OK. I will abandon my attempt to conform to the Secrets API. This will actually make things a little easier. I will provide a Keychain and Service Name parameter for each of my new functions. > Are you providing both SecKeychain*GenericPassword and > SecKeychain*InternetPassword? Yes, I will provide access to both the Generic Password and Internet Password functions.