From: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: [PATCH 52/59] config.txt: move transfer.* to a separate file
Date: Sat, 20 Oct 2018 14:38:41 +0200 [thread overview]
Message-ID: <20181020123848.2785-53-pclouds@gmail.com> (raw)
In-Reply-To: <20181020123848.2785-1-pclouds@gmail.com>
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
---
Documentation/config.txt | 72 +------------------------------
Documentation/transfer-config.txt | 71 ++++++++++++++++++++++++++++++
2 files changed, 72 insertions(+), 71 deletions(-)
create mode 100644 Documentation/transfer-config.txt
diff --git a/Documentation/config.txt b/Documentation/config.txt
index 4b1efe0a95..b70f98baba 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -670,77 +670,7 @@ include::submodule-config.txt[]
include::tag-config.txt[]
-transfer.fsckObjects::
- When `fetch.fsckObjects` or `receive.fsckObjects` are
- not set, the value of this variable is used instead.
- Defaults to false.
-+
-When set, the fetch or receive will abort in the case of a malformed
-object or a link to a nonexistent object. In addition, various other
-issues are checked for, including legacy issues (see `fsck.<msg-id>`),
-and potential security issues like the existence of a `.GIT` directory
-or a malicious `.gitmodules` file (see the release notes for v2.2.1
-and v2.17.1 for details). Other sanity and security checks may be
-added in future releases.
-+
-On the receiving side, failing fsckObjects will make those objects
-unreachable, see "QUARANTINE ENVIRONMENT" in
-linkgit:git-receive-pack[1]. On the fetch side, malformed objects will
-instead be left unreferenced in the repository.
-+
-Due to the non-quarantine nature of the `fetch.fsckObjects`
-implementation it can not be relied upon to leave the object store
-clean like `receive.fsckObjects` can.
-+
-As objects are unpacked they're written to the object store, so there
-can be cases where malicious objects get introduced even though the
-"fetch" failed, only to have a subsequent "fetch" succeed because only
-new incoming objects are checked, not those that have already been
-written to the object store. That difference in behavior should not be
-relied upon. In the future, such objects may be quarantined for
-"fetch" as well.
-+
-For now, the paranoid need to find some way to emulate the quarantine
-environment if they'd like the same protection as "push". E.g. in the
-case of an internal mirror do the mirroring in two steps, one to fetch
-the untrusted objects, and then do a second "push" (which will use the
-quarantine) to another internal repo, and have internal clients
-consume this pushed-to repository, or embargo internal fetches and
-only allow them once a full "fsck" has run (and no new fetches have
-happened in the meantime).
-
-transfer.hideRefs::
- String(s) `receive-pack` and `upload-pack` use to decide which
- refs to omit from their initial advertisements. Use more than
- one definition to specify multiple prefix strings. A ref that is
- under the hierarchies listed in the value of this variable is
- excluded, and is hidden when responding to `git push` or `git
- fetch`. See `receive.hideRefs` and `uploadpack.hideRefs` for
- program-specific versions of this config.
-+
-You may also include a `!` in front of the ref name to negate the entry,
-explicitly exposing it, even if an earlier entry marked it as hidden.
-If you have multiple hideRefs values, later entries override earlier ones
-(and entries in more-specific config files override less-specific ones).
-+
-If a namespace is in use, the namespace prefix is stripped from each
-reference before it is matched against `transfer.hiderefs` patterns.
-For example, if `refs/heads/master` is specified in `transfer.hideRefs` and
-the current namespace is `foo`, then `refs/namespaces/foo/refs/heads/master`
-is omitted from the advertisements but `refs/heads/master` and
-`refs/namespaces/bar/refs/heads/master` are still advertised as so-called
-"have" lines. In order to match refs before stripping, add a `^` in front of
-the ref name. If you combine `!` and `^`, `!` must be specified first.
-+
-Even if you hide refs, a client may still be able to steal the target
-objects via the techniques described in the "SECURITY" section of the
-linkgit:gitnamespaces[7] man page; it's best to keep private data in a
-separate repository.
-
-transfer.unpackLimit::
- When `fetch.unpackLimit` or `receive.unpackLimit` are
- not set, the value of this variable is used instead.
- The default value is 100.
+include::transfer-config.txt[]
uploadarchive.allowUnreachable::
If true, allow clients to use `git archive --remote` to request
diff --git a/Documentation/transfer-config.txt b/Documentation/transfer-config.txt
new file mode 100644
index 0000000000..4a5dfe2fc1
--- /dev/null
+++ b/Documentation/transfer-config.txt
@@ -0,0 +1,71 @@
+transfer.fsckObjects::
+ When `fetch.fsckObjects` or `receive.fsckObjects` are
+ not set, the value of this variable is used instead.
+ Defaults to false.
++
+When set, the fetch or receive will abort in the case of a malformed
+object or a link to a nonexistent object. In addition, various other
+issues are checked for, including legacy issues (see `fsck.<msg-id>`),
+and potential security issues like the existence of a `.GIT` directory
+or a malicious `.gitmodules` file (see the release notes for v2.2.1
+and v2.17.1 for details). Other sanity and security checks may be
+added in future releases.
++
+On the receiving side, failing fsckObjects will make those objects
+unreachable, see "QUARANTINE ENVIRONMENT" in
+linkgit:git-receive-pack[1]. On the fetch side, malformed objects will
+instead be left unreferenced in the repository.
++
+Due to the non-quarantine nature of the `fetch.fsckObjects`
+implementation it can not be relied upon to leave the object store
+clean like `receive.fsckObjects` can.
++
+As objects are unpacked they're written to the object store, so there
+can be cases where malicious objects get introduced even though the
+"fetch" failed, only to have a subsequent "fetch" succeed because only
+new incoming objects are checked, not those that have already been
+written to the object store. That difference in behavior should not be
+relied upon. In the future, such objects may be quarantined for
+"fetch" as well.
++
+For now, the paranoid need to find some way to emulate the quarantine
+environment if they'd like the same protection as "push". E.g. in the
+case of an internal mirror do the mirroring in two steps, one to fetch
+the untrusted objects, and then do a second "push" (which will use the
+quarantine) to another internal repo, and have internal clients
+consume this pushed-to repository, or embargo internal fetches and
+only allow them once a full "fsck" has run (and no new fetches have
+happened in the meantime).
+
+transfer.hideRefs::
+ String(s) `receive-pack` and `upload-pack` use to decide which
+ refs to omit from their initial advertisements. Use more than
+ one definition to specify multiple prefix strings. A ref that is
+ under the hierarchies listed in the value of this variable is
+ excluded, and is hidden when responding to `git push` or `git
+ fetch`. See `receive.hideRefs` and `uploadpack.hideRefs` for
+ program-specific versions of this config.
++
+You may also include a `!` in front of the ref name to negate the entry,
+explicitly exposing it, even if an earlier entry marked it as hidden.
+If you have multiple hideRefs values, later entries override earlier ones
+(and entries in more-specific config files override less-specific ones).
++
+If a namespace is in use, the namespace prefix is stripped from each
+reference before it is matched against `transfer.hiderefs` patterns.
+For example, if `refs/heads/master` is specified in `transfer.hideRefs` and
+the current namespace is `foo`, then `refs/namespaces/foo/refs/heads/master`
+is omitted from the advertisements but `refs/heads/master` and
+`refs/namespaces/bar/refs/heads/master` are still advertised as so-called
+"have" lines. In order to match refs before stripping, add a `^` in front of
+the ref name. If you combine `!` and `^`, `!` must be specified first.
++
+Even if you hide refs, a client may still be able to steal the target
+objects via the techniques described in the "SECURITY" section of the
+linkgit:gitnamespaces[7] man page; it's best to keep private data in a
+separate repository.
+
+transfer.unpackLimit::
+ When `fetch.unpackLimit` or `receive.unpackLimit` are
+ not set, the value of this variable is used instead.
+ The default value is 100.
--
2.19.1.647.g708186aaf9
next prev parent reply other threads:[~2018-10-20 12:40 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 12:37 [PATCH 00/59] Split config.txt Nguyễn Thái Ngọc Duy
2018-10-20 12:37 ` [PATCH 01/59] config.txt: move advice.* to a separate file Nguyễn Thái Ngọc Duy
2018-10-20 12:37 ` [PATCH 02/59] config.txt: move core.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:37 ` [PATCH 03/59] config.txt: move add.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:37 ` [PATCH 04/59] config.txt: move alias.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:37 ` [PATCH 05/59] config.txt: move am.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:37 ` [PATCH 06/59] config.txt: move apply.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:37 ` [PATCH 07/59] config.txt: move blame.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:37 ` [PATCH 08/59] config.txt: move branch.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:37 ` [PATCH 09/59] config.txt: move browser.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:37 ` [PATCH 10/59] config.txt: move checkout.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 11/59] config.txt: move clean.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 12/59] config.txt: move color.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 13/59] config.txt: move column.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 14/59] config.txt: move commit.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 15/59] config.txt: move credential.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 16/59] config.txt: move completion.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 17/59] config.txt: move difftool.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 18/59] config.txt: move fastimport.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 19/59] config.txt: move filter.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 20/59] config.txt: move fsck.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 21/59] config.txt: move gc.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 22/59] config.txt: move gitweb.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 23/59] config.txt: move grep.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 24/59] config.txt: move gpg.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 25/59] config.txt: move guitool.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 26/59] config.txt: move help.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 27/59] config.txt: move ssh.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 28/59] config.txt: move i18n.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 29/59] " Nguyễn Thái Ngọc Duy
2018-10-21 19:40 ` Andrei Rybak
2018-10-20 12:38 ` [PATCH 30/59] config.txt: move init.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 31/59] config.txt: move instaweb.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 32/59] config.txt: move interactive.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 33/59] config.txt: move log.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 34/59] config.txt: move mailinfo.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 35/59] config.txt: move mailmap.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 36/59] config.txt: move man.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 37/59] config.txt: move mergetool.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 38/59] config.txt: move notes.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 39/59] config.txt: move pack.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 40/59] config.txt: move pager.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 41/59] config.txt: move pretty.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 42/59] config.txt: move protocol.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 43/59] config.txt: move remote.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 44/59] config.txt: move remotes.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 45/59] config.txt: move repack.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 46/59] config.txt: move rerere.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 47/59] config.txt: move sequencer.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 48/59] config.txt: move showBranch.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 49/59] config.txt: move splitIndex.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 50/59] config.txt: move status.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 51/59] config.txt: move tag.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` Nguyễn Thái Ngọc Duy [this message]
2018-10-20 12:38 ` [PATCH 53/59] config.txt: move uploadarchive.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 54/59] config.txt: move uploadpack.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 55/59] config.txt: move url.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 56/59] config.txt: move user.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 57/59] config.txt: move versionsort.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 58/59] config.txt: move web.* " Nguyễn Thái Ngọc Duy
2018-10-20 12:38 ` [PATCH 59/59] config.txt: move worktree.* " Nguyễn Thái Ngọc Duy
2018-10-20 19:25 ` [PATCH 00/59] Split config.txt Ævar Arnfjörð Bjarmason
2018-10-20 19:30 ` Duy Nguyen
2018-10-20 19:41 ` Ævar Arnfjörð Bjarmason
2018-10-20 23:29 ` Junio C Hamano
2018-10-22 14:42 ` Duy Nguyen
2018-10-22 19:22 ` Stefan Beller
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181020123848.2785-53-pclouds@gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).