From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Simon.Richter@hogyros.de
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH 3/3] Allow empty user name in HTTP authentication
Date: Fri, 13 May 2022 23:51:38 +0000 [thread overview]
Message-ID: <Yn7vCg6Rl7TYRw82@camp.crustytoothpaste.net> (raw)
In-Reply-To: <20220513070416.37235-4-Simon.Richter@hogyros.de>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
On 2022-05-13 at 07:04:16, Simon.Richter@hogyros.de wrote:
> From: Simon Richter <Simon.Richter@hogyros.de>
>
> When using a Personal Access Token in Microsoft DevOps server, the username
> can be empty, so users might expect that pressing return on an username
> prompt will work.
I don't think this is a good idea. libcurl relies on CURLOPT_USERPWD
being set to enable authentication, and before the appearance of
http.emptyAuth, it was extremely common for Kerberos users to specify an
empty username to get Git to authenticate properly. I probably still
have some repositories on my system configured that way.
I believe GitHub can also accept an empty username with a PAT, but it
can also accept a dummy (e.g., "token"), which I would hope Azure DevOps
can do as well. In such a case, the documentation for Azure DevOps
should just be updated to tell people to specify something like "token"
or their username.
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
prev parent reply other threads:[~2022-05-14 1:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 7:04 [PATCH 0/3] Allow configuration of HTTP authentication method Simon.Richter
2022-05-13 7:04 ` [PATCH 1/3] Rename proxy_authmethods -> authmethods Simon.Richter
2022-05-13 19:50 ` Junio C Hamano
2022-05-13 7:04 ` [PATCH 2/3] Add config option/env var to limit HTTP auth methods Simon.Richter
2022-05-13 20:26 ` Junio C Hamano
2022-05-13 7:04 ` [RFC PATCH 3/3] Allow empty user name in HTTP authentication Simon.Richter
2022-05-13 23:51 ` brian m. carlson [this message]
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=Yn7vCg6Rl7TYRw82@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=Simon.Richter@hogyros.de \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.