public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: "brian m. carlson" <sandals@crustytoothpaste•net>
Cc: Jean-Francois Bouchard <jfbouchard@accedian•com>,
	git <git@vger•kernel.org>
Subject: Re: Git + mod_auth_kerb
Date: Tue, 22 Jul 2014 10:00:22 -0700	[thread overview]
Message-ID: <xmqqfvhtgwgp.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140721231721.GB5616@vauxhall.crustytoothpaste.net> (brian m. carlson's message of "Mon, 21 Jul 2014 23:17:21 +0000")

"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?

  parent reply	other threads:[~2014-07-22 17:00 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 [this message]
2014-07-22 23:32     ` brian m. carlson
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqfvhtgwgp.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=jfbouchard@accedian$(echo .)com \
    --cc=sandals@crustytoothpaste$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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