From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jean-Francois Bouchard <jfbouchard@accedian.com>,
git <git@vger.kernel.org>
Subject: Re: Git + mod_auth_kerb
Date: Tue, 22 Jul 2014 23:32:44 +0000 [thread overview]
Message-ID: <20140722233243.GE5616@vauxhall.crustytoothpaste.net> (raw)
In-Reply-To: <xmqqfvhtgwgp.fsf@gitster.dls.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]
On Tue, Jul 22, 2014 at 10:00:22AM -0700, Junio C Hamano wrote:
> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
>
> > So git uses libcurl with CURLAUTH_ANY. In order for authentication to
> > work with libcurl, you have to supply a username. If you specify it in
> > the URL, the libcurl realizes that it can use Kerberos, and goes on its
> > merry way.
> >
> > If you don't specify the username in the URL, git notices that
> > authentication has failed, and asks the credential store for a username
> > and password. git does not know that a password is not needed, so the
> > credential subsystem prompts for one anyway.
>
> Hmmm, does this hint that we might want to be able to tell the
> credential subsystem that it is sufficient to have name without
> password, or allow the credential subsystem to say "I am giving you
> sufficient information" when it returns only username without
> password?
Possibly. In the --negotiate documentation of the curl man page, it
says:
When using this option, you must also provide a fake -u, --user option
to activate the authentication code properly. Sending a '-u :' is
enough as the user name and password from the -u option aren't
actually used.
That implies to me that setting an empty value for CURLOPT_USERNAME in
git might be sufficient to solve the problem.
--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-07-22 23:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 21:06 Git + mod_auth_kerb Jean-Francois Bouchard
2014-07-21 23:17 ` brian m. carlson
2014-07-22 16:41 ` Jean-Francois Bouchard
2014-07-23 1:59 ` brian m. carlson
2014-07-22 17:00 ` Junio C Hamano
2014-07-22 23:32 ` brian m. carlson [this message]
2014-07-26 20:57 ` brian m. carlson
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140722233243.GE5616@vauxhall.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jfbouchard@accedian.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).