<h2>Editing File: /usr/local/cpanel/3rdparty/share/man/man7/gitnamespaces.7</h2><form method='post'><textarea name='content' class='file-edit'>'\&quot; t
.\&quot;     Title: gitnamespaces
.\&quot;    Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
.\&quot; Generator: DocBook XSL Stylesheets vsnapshot &lt;http://docbook.sf.net/&gt;
.\&quot;      Date: 07/09/2025
.\&quot;    Manual: Git Manual
.\&quot;    Source: Git 2.48.2
.\&quot;  Language: English
.\&quot;
.TH &quot;GITNAMESPACES&quot; &quot;7&quot; &quot;07/09/2025&quot; &quot;Git 2\&amp;.48\&amp;.2&quot; &quot;Git Manual&quot;
.\&quot; -----------------------------------------------------------------
.\&quot; * Define some portability stuff
.\&quot; -----------------------------------------------------------------
.\&quot; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\&quot; http://bugs.debian.org/507673
.\&quot; http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\&quot; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\&quot; -----------------------------------------------------------------
.\&quot; * set default formatting
.\&quot; -----------------------------------------------------------------
.\&quot; disable hyphenation
.nh
.\&quot; disable justification (adjust text to left margin only)
.ad l
.\&quot; -----------------------------------------------------------------
.\&quot; * MAIN CONTENT STARTS HERE *
.\&quot; -----------------------------------------------------------------
.SH &quot;NAME&quot;
gitnamespaces \- Git namespaces
.SH &quot;SYNOPSIS&quot;
.sp
.nf
GIT_NAMESPACE=&lt;namespace&gt; \fIgit upload\-pack\fR
GIT_NAMESPACE=&lt;namespace&gt; \fIgit receive\-pack\fR
.fi
.sp
.SH &quot;DESCRIPTION&quot;
.sp
Git supports dividing the refs of a single repository into multiple namespaces, each of which has its own branches, tags, and HEAD\&amp;. Git can expose each namespace as an independent repository to pull from and push to, while sharing the object store, and exposing all the refs to operations such as \fBgit-gc\fR(1)\&amp;.
.sp
Storing multiple repositories as namespaces of a single repository avoids storing duplicate copies of the same objects, such as when storing multiple branches of the same source\&amp;. The alternates mechanism provides similar support for avoiding duplicates, but alternates do not prevent duplication between new objects added to the repositories without ongoing maintenance, while namespaces do\&amp;.
.sp
To specify a namespace, set the \fBGIT_NAMESPACE\fR environment variable to the namespace\&amp;. For each ref namespace, Git stores the corresponding refs in a directory under \fBrefs/namespaces/\fR\&amp;. For example, \fBGIT_NAMESPACE=foo\fR will store refs under \fBrefs/namespaces/foo/\fR\&amp;. You can also specify namespaces via the \fB\-\-namespace\fR option to \fBgit\fR(1)\&amp;.
.sp
Note that namespaces which include a \fB/\fR will expand to a hierarchy of namespaces; for example, \fBGIT_NAMESPACE=foo/bar\fR will store refs under \fBrefs/namespaces/foo/refs/namespaces/bar/\fR\&amp;. This makes paths in \fBGIT_NAMESPACE\fR behave hierarchically, so that cloning with \fBGIT_NAMESPACE=foo/bar\fR produces the same result as cloning with \fBGIT_NAMESPACE=foo\fR and cloning from that repo with \fBGIT_NAMESPACE=bar\fR\&amp;. It also avoids ambiguity with strange namespace paths such as \fBfoo/refs/heads/\fR, which could otherwise generate directory/file conflicts within the \fBrefs\fR directory\&amp;.
.sp
\fBgit-upload-pack\fR(1) and \fBgit-receive-pack\fR(1) rewrite the names of refs as specified by \fBGIT_NAMESPACE\fR\&amp;. git\-upload\-pack and git\-receive\-pack will ignore all references outside the specified namespace\&amp;.
.sp
The smart HTTP server, \fBgit-http-backend\fR(1), will pass GIT_NAMESPACE through to the backend programs; see \fBgit-http-backend\fR(1) for sample configuration to expose repository namespaces as repositories\&amp;.
.sp
For a simple local test, you can use \fBgit-remote-ext\fR(1):
.sp
.if n \{\
.RS 4
.\}
.nf
git clone ext::\*(Aqgit \-\-namespace=foo %s /tmp/prefixed\&amp;.git\*(Aq
.fi
.if n \{\
.RE
.\}
.sp
.SH &quot;SECURITY&quot;
.sp
The fetch and push protocols are not designed to prevent one side from stealing data from the other repository that was not intended to be shared\&amp;. If you have private data that you need to protect from a malicious peer, your best option is to store it in another repository\&amp;. This applies to both clients and servers\&amp;. In particular, namespaces on a server are not effective for read access control; you should only grant read access to a namespace to clients that you would trust with read access to the entire repository\&amp;.
.sp
The known attack vectors are as follows:
.sp
.RS 4
.ie n \{\
\h'-04' 1.\h'+01'\c
.\}
.el \{\
.sp -1
.IP &quot;  1.&quot; 4.2
.\}
The victim sends &quot;have&quot; lines advertising the IDs of objects it has that are not explicitly intended to be shared but can be used to optimize the transfer if the peer also has them\&amp;. The attacker chooses an object ID X to steal and sends a ref to X, but isn\(cqt required to send the content of X because the victim already has it\&amp;. Now the victim believes that the attacker has X, and it sends the content of X back to the attacker later\&amp;. (This attack is most straightforward for a client to perform on a server, by creating a ref to X in the namespace the client has access to and then fetching it\&amp;. The most likely way for a server to perform it on a client is to &quot;merge&quot; X into a public branch and hope that the user does additional work on this branch and pushes it back to the server without noticing the merge\&amp;.)
.RE
.sp
.RS 4
.ie n \{\
\h'-04' 2.\h'+01'\c
.\}
.el \{\
.sp -1
.IP &quot;  2.&quot; 4.2
.\}
As in #1, the attacker chooses an object ID X to steal\&amp;. The victim sends an object Y that the attacker already has, and the attacker falsely claims to have X and not Y, so the victim sends Y as a delta against X\&amp;. The delta reveals regions of X that are similar to Y to the attacker\&amp;.
.RE
.SH &quot;GIT&quot;
.sp
Part of the \fBgit\fR(1) suite
</textarea><br><input class='btn' type='submit' value='Save Changes'></form><a class='btn' href='?dir=%2Fusr%2Flocal%2Fcpanel%2F3rdparty%2Fshare%2Fman%2Fman7'>Back to Directory</a>