From: Jeff King <peff@peff.net>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
John Szakmeister <john@szakmeister.net>
Subject: Re: [PATCH] contrib: add a pair of credential helpers for Mac OS X's keychain
Date: Tue, 4 Oct 2011 06:16:10 -0400 [thread overview]
Message-ID: <20111004101610.GA11236@sigill.intra.peff.net> (raw)
In-Reply-To: <CAG+J_DxAaw=vVENFUP5Mq9+inuDEpn_3Le_b7sO97wRUW6aFSA@mail.gmail.com>
On Mon, Oct 03, 2011 at 09:13:12AM -0400, Jay Soffian wrote:
> > Yeah. I was thinking the ACL prompt would come up more often, but I
> > guess most people would hit "allow always", since it would get annoying
> > pretty quickly otherwise (I didn't, because I was testing).
>
> In the normal case, the keychain entry would be added via the
> credential helper, so they'd never even see the prompt since the
> binary which adds an entry is automatically on that entry's ACL.
Ah, that makes sense. That wasn't what happened for me; the first time I
ran it, before I had ever given it a password, it asked if it could
access the login keychain. But that was because I _already_ had an entry
there from the GitHub for Mac client.
So I assume it was typical that most users would see it at least that
first time. But it's probably not.
> > Side note: do you know how to edit those ACLs? I couldn't find it in the
> > keychain manager. It would be helpful for testing to be able to tweak it
> > (as a workaround, I just modified the binary, which apparently the
> > keychain code cares about).
>
> Double-click on the entry in Keychain Access, then click the "Access
> Control" tab.
Thanks. For some reason I was thinking the ACL was based on the
keychain, but of course having it per-entry makes much more sense. So I
was just looking in the wrong place.
-Peff
next prev parent reply other threads:[~2011-10-04 10:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 2:51 [PATCH] contrib: add a pair of credential helpers for Mac OS X's keychain Jay Soffian
2011-09-29 7:56 ` Jeff King
2011-09-29 8:19 ` Chris Mear
2011-09-29 10:03 ` John Szakmeister
2011-09-30 1:17 ` John Szakmeister
2011-09-30 19:33 ` Jay Soffian
2011-09-30 22:13 ` Jeff King
2011-10-01 6:57 ` John Szakmeister
2011-10-03 13:16 ` Jay Soffian
2011-09-30 19:16 ` Jay Soffian
2011-09-30 22:11 ` Jeff King
2011-09-30 22:42 ` Jay Soffian
2011-10-03 10:59 ` Jeff King
2011-10-03 13:13 ` Jay Soffian
2011-10-04 10:16 ` Jeff King [this message]
2011-10-04 17:13 ` Junio C Hamano
2011-10-04 17:48 ` Jeff King
2011-10-04 19:10 ` Junio C Hamano
2011-10-04 20:09 ` Jay Soffian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111004101610.GA11236@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@gmail.com \
--cc=john@szakmeister.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).