Johannes Schindelin 114042a3dd http(s): automatically try NTLM authentication first
It is common in corporate setups to have permissions managed via a
domain account. That means that the user does not really have to log in
when accessing a central repository via https://, but that the login
credentials are used to authenticate with that repository.

The common way to do that used to require empty credentials, i.e. hitting
Enter twice when being asked for user name and password, or by using the
very funny notation https://:@server/repository

A recent commit (5275c3081c (http: http.emptyauth should allow empty (not
just NULL) usernames, 2016-10-04)) broke that usage, though, all of a
sudden requiring users to set http.emptyAuth = true.

Which brings us to the bigger question why http.emptyAuth defaults to
false, to begin with.

It would be one thing if cURL would not let the user specify credentials
interactively after attempting NTLM authentication (i.e. login
credentials), but that is not the case.

It would be another thing if attempting NTLM authentication was not
usually what users need to do when trying to authenticate via https://.
But that is also not the case.

So let's just go ahead and change the default, and unbreak the NTLM
authentication. As a bonus, this also makes the "you need to hit Enter
twice" (which is hard to explain: why enter empty credentials when you
want to authenticate with your login credentials?) and the ":@" hack
(which is also pretty, pretty hard to explain to users) obsolete.

This fixes https://github.com/git-for-windows/git/issues/987

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
2016-12-09 17:53:05 +01:00
2016-11-29 23:28:00 +01:00
2016-11-30 18:03:10 +01:00
2016-11-29 23:29:15 +01:00
2016-10-17 13:25:20 -07:00
2016-11-30 18:03:10 +01:00
2016-11-30 18:01:54 +01:00
2016-09-26 17:46:44 -07:00
2016-11-11 13:56:30 -08:00
2016-11-22 13:55:20 -08:00
2016-11-22 13:55:20 -08:00
2016-09-29 15:42:18 -07:00
2016-11-30 18:01:54 +01:00
2016-10-10 14:03:50 -07:00
2016-10-31 13:15:21 -07:00
2016-11-29 23:28:00 +01:00
2016-10-31 13:15:21 -07:00
2016-10-31 13:15:21 -07:00
2016-10-27 14:58:50 -07:00
2016-09-29 15:42:18 -07:00
2016-10-04 10:50:06 +02:00
2016-11-30 18:03:10 +01:00
2016-11-30 17:52:48 +01:00
2016-10-14 01:36:12 +00:00
2016-11-29 12:23:07 -08:00
2016-11-30 18:03:10 +01:00
2016-10-04 10:50:06 +02:00
2016-09-29 15:42:18 -07:00
2016-11-30 18:01:54 +01:00
2016-11-30 18:03:10 +01:00
2016-09-26 16:09:18 -07:00
2016-09-29 15:42:18 -07:00
2016-09-25 16:44:13 -07:00
2016-09-29 15:42:18 -07:00
2016-10-17 13:25:21 -07:00
2016-11-29 23:28:47 +01:00
2016-10-28 09:01:23 -07:00
2016-10-26 13:14:45 -07:00
2016-10-10 14:03:50 -07:00
2016-10-11 14:24:02 -07:00
2016-10-10 14:03:50 -07:00
2016-09-29 15:42:18 -07:00
2016-11-10 13:17:30 -08:00
2016-10-10 14:03:46 -07:00
2016-10-31 13:15:21 -07:00
2016-11-30 15:30:36 +01:00
2016-09-29 15:42:18 -07:00
2016-10-28 09:01:23 -07:00
2016-10-31 13:15:22 -07:00
2016-10-27 14:58:48 -07:00
2016-10-27 14:58:48 -07:00
2016-09-29 15:42:18 -07:00
2016-10-31 13:15:21 -07:00
2016-11-29 23:28:18 +01:00
2016-10-04 10:50:06 +02:00

Git for Windows

Join the chat at https://gitter.im/git-for-windows/git

This is Git for Windows, the Windows port of Git.

The Git for Windows project is run using a governance model. If you encounter problems, you can report them as GitHub issues, discuss them on Git for Windows' Google Group, and contribute bug fixes.

Git - fast, scalable, distributed revision control system

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals.

Git is an Open Source project covered by the GNU General Public License version 2 (some parts of it are under different licenses, compatible with the GPLv2). It was originally written by Linus Torvalds with help of a group of hackers around the net.

Please read the file INSTALL for installation instructions.

Many Git online resources are accessible from http://git-scm.com/ including full documentation and Git related tools.

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.txt for a useful minimum set of commands, and Documentation/git-.txt for documentation of each command. If git has been correctly installed, then the tutorial can also be read with man gittutorial or git help tutorial, and the documentation of each command with man git-<commandname> or git help <commandname>.

CVS users may also want to read Documentation/gitcvs-migration.txt (man gitcvs-migration or git help cvs-migration if git is installed).

The user discussion and development of Git take place on the Git mailing list -- everyone is welcome to post bug reports, feature requests, comments and patches to git@vger.kernel.org (read Documentation/SubmittingPatches for instructions on patch submission). To subscribe to the list, send an email with just "subscribe git" in the body to majordomo@vger.kernel.org. The mailing list archives are available at http://news.gmane.org/gmane.comp.version-control.git/, http://marc.info/?l=git and other archival sites.

The maintainer frequently sends the "What's cooking" reports that list the current status of various development topics to the mailing list. The discussion following them give a good reference for project status, development direction and remaining tasks.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (depending on your mood):

  • random three-letter combination that is pronounceable, and not actually used by any common UNIX command. The fact that it is a mispronunciation of "get" may or may not be relevant.
  • stupid. contemptible and despicable. simple. Take your pick from the dictionary of slang.
  • "global information tracker": you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room.
  • "goddamn idiotic truckload of sh*t": when it breaks
Description
No description provided
Readme 592 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%