Re: [REGRESSION 2.10.2] problematic "empty auth" changes
- From
brian m. carlson <sandals@crustytoothpaste.net>
- Date
- Dec 9, 2016, 22:19 UTC
- Message-ID
- <20161209221854.re6qf3e5225wxvge@genre.crustytoothpaste.net>
- In-Reply-To
- <1481231552.20894.20.camel@frank>
On Thu, Dec 08, 2016 at 04:12:32PM -0500, David Turner wrote:
Show 9 quoted lines
> I know of no reason that shouldn't work. Indeed, it's what we use do > internally. So far, nobody has reported problems. That said, we have > exactly three sets of git servers that most users talk to (two different > internal; and occasionally github.com for external stuff). So our > coverage is not very broad. > > If you're going to do it, tho, don't just do it for Windows users -- do > it for everyone. Plenty of Unix clients connect to Windows-based auth > systems.
Let me echo this. This would make Kerberos (and probably other forms of SPNEGO) work out of the box, which would reduce a lot of confusion that people have.
I can confirm enabling http.emptyAuth works properly with Kerberos, including with fallback to Basic, so I see no reason why we shouldn't do it.
-- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | https://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: https://keybase.io/bk2204