Jeff King fe29a9b7b0 credential: die() when parsing invalid urls
When we try to initialize credential loading by URL and find that the
URL is invalid, we set all fields to NULL in order to avoid acting on
malicious input. Later when we request credentials, we diagonse the
erroneous input:

	fatal: refusing to work with credential missing host field

This is problematic in two ways:

- The message doesn't tell the user *why* we are missing the host
  field, so they can't tell from this message alone how to recover.
  There can be intervening messages after the original warning of
  bad input, so the user may not have the context to put two and two
  together.

- The error only occurs when we actually need to get a credential.  If
  the URL permits anonymous access, the only encouragement the user gets
  to correct their bogus URL is a quiet warning.

  This is inconsistent with the check we perform in fsck, where any use
  of such a URL as a submodule is an error.

When we see such a bogus URL, let's not try to be nice and continue
without helpers. Instead, die() immediately. This is simpler and
obviously safe. And there's very little chance of disrupting a normal
workflow.

It's _possible_ that somebody has a legitimate URL with a raw newline in
it. It already wouldn't work with credential helpers, so this patch
steps that up from an inconvenience to "we will refuse to work with it
at all". If such a case does exist, we should figure out a way to work
with it (especially if the newline is only in the path component, which
we normally don't even pass to helpers). But until we see a real report,
we're better off being defensive.

Reported-by: Carlo Arenas <carenas@gmail.com>
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
2020-04-19 16:10:58 -07:00
2019-12-06 16:27:36 +01:00
2019-12-06 16:27:36 +01:00
2020-03-17 13:25:33 -07:00
2018-03-15 15:00:46 -07:00
2017-07-06 18:14:44 -07:00
2018-05-22 14:25:26 +09:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-03-13 15:28:54 -07:00
2017-11-15 12:14:28 +09:00
2018-03-06 14:54:07 -08:00
2017-05-25 13:08:23 +09:00
2017-05-08 15:12:57 +09:00
2017-05-08 15:12:57 +09:00
2017-12-27 11:16:25 -08:00
2017-12-27 11:16:25 -08:00
2017-08-03 11:08:10 -07:00
2018-03-06 14:54:07 -08:00
2017-05-02 10:46:41 +09:00
2018-05-22 14:25:26 +09:00
2018-02-13 10:17:12 -08:00
2018-02-13 10:17:12 -08:00
2017-10-24 10:19:06 +09:00
2018-03-06 14:54:07 -08:00
2017-01-25 14:42:37 -08:00
2018-03-06 14:54:07 -08:00
2018-02-13 13:39:08 -08:00
2019-12-06 16:27:18 +01:00
2019-12-06 16:27:18 +01:00
2018-02-13 13:39:04 -08:00
2018-02-15 14:55:43 -08:00
2018-02-02 11:28:41 -08:00
2018-02-02 11:28:41 -08:00
2017-12-08 09:16:27 -08:00
2017-12-08 09:16:27 -08:00
2018-03-06 14:54:07 -08:00
2018-02-15 14:55:43 -08:00
2018-05-22 14:25:26 +09:00
2018-02-22 10:08:05 -08:00
2019-12-06 16:27:36 +01:00
2019-12-06 16:27:36 +01:00
2018-05-21 23:55:12 -04:00
2019-12-06 16:27:36 +01:00
2019-12-06 16:27:36 +01:00
2020-03-17 13:25:33 -07:00
2018-02-13 10:17:12 -08:00
2017-11-21 14:05:30 +09:00
2018-03-06 14:54:07 -08:00
2017-06-24 14:28:41 -07:00
2018-02-22 10:08:05 -08:00
2018-02-22 10:08:05 -08:00
2017-01-30 14:17:00 -08:00
2017-09-06 17:19:54 +09:00
2018-03-06 14:54:07 -08:00
2018-03-15 15:00:46 -07:00
2018-03-06 14:54:07 -08:00
2017-12-27 12:28:06 -08:00
2017-11-22 14:11:56 +09:00
2018-03-06 14:54:07 -08:00
2018-02-02 11:28:41 -08:00
2018-03-06 14:54:07 -08:00
2017-08-22 10:29:03 -07:00
2017-05-29 12:34:43 +09:00
2019-12-06 16:26:55 +01:00
2017-12-13 11:14:25 -08:00
2017-12-06 09:23:44 -08:00
2017-10-17 10:51:29 +09:00
2017-12-12 10:41:15 -08:00
2017-12-19 11:33:55 -08:00
2018-01-16 12:16:54 -08:00
2019-12-06 16:27:36 +01:00
2020-03-17 13:25:33 -07:00
2018-01-22 11:32:51 -08:00
2017-03-31 08:33:56 -07:00
2018-02-27 10:33:58 -08:00
2018-05-21 23:55:12 -04:00
2017-03-31 08:33:56 -07:00
2017-09-29 11:23:43 +09:00
2018-03-06 14:54:07 -08:00
2018-03-14 12:01:05 -07:00
2019-12-06 16:27:18 +01:00
2018-05-22 14:18:06 +09:00
2019-12-06 16:27:36 +01:00
2019-12-06 16:27:36 +01:00
2018-02-22 10:08:05 -08:00
2017-08-26 22:55:04 -07:00
2019-12-06 16:27:36 +01:00
2018-02-13 13:39:04 -08:00
2018-02-13 13:39:04 -08:00
2019-12-06 16:27:18 +01:00
2017-06-24 14:28:41 -07:00
2019-12-06 16:27:36 +01:00
2018-03-29 15:39:59 -07:00
2018-05-22 14:15:14 +09:00
2018-05-21 23:50:11 -04:00
2018-02-22 10:08:05 -08:00

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 https://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 https://public-inbox.org/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
Git with broken hash generation to generate collisions between object IDs. Don't use this!
https://undefinedbehavior.de/posts/commit-vandalism/
Readme 217 MiB
Languages
C 50%
Shell 38.2%
Perl 5.5%
Tcl 3.5%
Python 0.9%
Other 1.7%