Jeff King 7f0e4f6ac2 ls-refs: ignore very long ref-prefix counts
Because each "ref-prefix" capability from the client comes in its own
pkt-line, there's no limit to the number of them that a misbehaving
client may send. We read them all into a strvec, which means the client
can waste arbitrary amounts of our memory by just sending us "ref-prefix
foo" over and over.

One possible solution is to just drop the connection when the limit is
reached. If we set it high enough, then only misbehaving or malicious
clients would hit it. But "high enough" is vague, and it's unfriendly if
we guess wrong and a legitimate client hits this.

But we can do better. Since supporting the ref-prefix capability is
optional anyway, the client has to further cull the response based on
their own patterns. So we can simply ignore the patterns once we cross a
certain threshold. Note that we have to ignore _all_ patterns, not just
the ones past our limit (since otherwise we'd send too little data).

The limit here is fairly arbitrary, and probably much higher than anyone
would need in practice. It might be worth limiting it further, if only
because we check it linearly (so with "m" local refs and "n" patterns,
we do "m * n" string comparisons). But if we care about optimizing this,
an even better solution may be a more advanced data structure anyway.

I didn't bother making the limit configurable, since it's so high and
since Git should behave correctly in either case. It wouldn't be too
hard to do, but it makes both the code and documentation more complex.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-09-15 12:25:19 -07:00
2021-09-10 11:46:32 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-07-22 13:05:54 -07:00
2021-07-13 16:52:50 -07:00
2021-08-12 14:00:52 -07:00
2021-05-10 16:59:47 +09:00
2021-03-08 09:56:34 -08:00
2021-01-21 15:50:00 -08:00
2019-09-28 14:04:16 +09:00
2021-03-13 16:00:09 -08:00
2021-06-14 10:16:06 +09:00
2021-04-27 16:31:39 +09:00
2021-05-07 12:47:41 +09:00
2019-07-09 15:25:44 -07:00
2021-01-23 17:14:07 -08:00
2020-08-10 10:23:57 -07:00
2021-07-13 16:52:50 -07:00
2021-03-13 16:00:09 -08:00
2021-07-16 17:42:53 -07:00
2020-07-06 22:09:13 -07:00
2021-03-13 16:00:09 -08:00
2021-08-06 12:52:15 -07:00
2021-07-30 12:14:27 -07:00
2021-07-28 13:17:57 -07:00
2020-07-30 19:18:06 -07:00
2020-07-28 15:02:17 -07:00
2020-03-24 15:04:43 -07:00
2021-08-24 15:33:23 -07:00
2019-11-18 15:21:28 +09:00
2021-07-13 16:52:53 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2019-11-18 15:21:28 +09:00
2021-09-10 11:46:28 -07:00
2021-07-28 13:17:59 -07:00
2021-03-13 16:00:09 -08:00
2021-04-27 16:31:39 +09:00
2021-07-28 13:17:58 -07:00
2021-03-13 16:00:09 -08:00
2021-04-08 13:23:25 -07:00
2021-04-08 13:23:25 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2020-03-24 15:04:44 -07:00
2020-03-24 15:04:44 -07:00
2021-08-24 15:32:37 -07:00
2021-08-04 13:28:52 -07:00
2021-07-26 12:01:26 -07:00
2021-03-13 16:00:09 -08:00
2021-02-05 16:40:45 -08:00
2020-12-14 10:21:36 -08:00
2020-10-27 15:09:50 -07:00
2021-08-24 15:33:23 -07:00
2021-09-10 11:46:30 -07:00
2021-02-17 17:21:40 -08:00
2021-09-15 12:25:19 -07:00
2019-11-13 10:09:10 +09:00
2019-11-18 15:21:29 +09:00
2021-04-14 13:47:54 -07:00
2021-07-28 13:17:59 -07:00
2020-07-30 19:18:06 -07:00
2019-09-05 14:10:18 -07:00
2021-07-22 13:35:20 -07:00
2021-07-22 13:35:20 -07:00
2021-05-04 12:09:43 +09:00
2019-11-10 16:00:54 +09:00
2021-09-10 11:46:27 -07:00
2021-05-04 11:52:02 +09:00
2021-05-04 11:52:02 +09:00

Build status

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-<commandname>.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://lore.kernel.org/git/, http://marc.info/?l=git and other archival sites.

Issues which are security relevant should be disclosed privately to the Git Security mailing list git-security@googlegroups.com.

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 581 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%