Hostea
/
website
3
2
Fork 2
Code Issues 5 Pull Requests Projects Releases Wiki Activity

new deploy: 2022-06-03T12:04:47+00:00

pages
Loïc Dachary 2022-06-03 12:04:47 +00:00 committed by dachary
parent 4f51500abd
commit cdf7368c31
7 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
blog/atom.xml
View File

@ -139,7 +139,7 @@
<p>It is safe to <a href="https://lab.forgefriends.org/forgefriends/forgefriends/-/merge_requests/50/diffs">disable the security check in Gitea</a>. It is not vulnerable to <strong><a href="https://github.com/git-for-windows/git/security/advisories/GHSA-vw2c-22j4-2fh2">CVE-2022-24765</a></strong> because it calls the git CLI <a href="https://github.com/go-gitea/gitea/blob/main/modules/git/command.go#L160">after changing its working directory</a> to be the git repository targeted by the command (for instance <a href="https://github.com/go-gitea/gitea/blob/main/modules/git/diff.go#L38-L45">diff</a>) or a temporary directory. Therefore <strong>it will not explore the parent directories looking for a git configuration file</strong>.</p> <p>It is safe to <a href="https://lab.forgefriends.org/forgefriends/forgefriends/-/merge_requests/50/diffs">disable the security check in Gitea</a>. It is not vulnerable to <strong><a href="https://github.com/git-for-windows/git/security/advisories/GHSA-vw2c-22j4-2fh2">CVE-2022-24765</a></strong> because it calls the git CLI <a href="https://github.com/go-gitea/gitea/blob/main/modules/git/command.go#L160">after changing its working directory</a> to be the git repository targeted by the command (for instance <a href="https://github.com/go-gitea/gitea/blob/main/modules/git/diff.go#L38-L45">diff</a>) or a temporary directory. Therefore <strong>it will not explore the parent directories looking for a git configuration file</strong>.</p>
<p>The security check is triggered because the repository is owned by an unexpected user (root instead of git typically) and <strong>not because a parent directory is owned by an unexpected user</strong>. This, in itself, is a problem worth investigating but it is unrelated and was revealed by the newer security check of git even though it does not match the threat described in <strong><a href="https://github.com/git-for-windows/git/security/advisories/GHSA-vw2c-22j4-2fh2">CVE-2022-24765</a></strong>.</p> <p>The security check is triggered because the repository is owned by an unexpected user (root instead of git typically) and <strong>not because a parent directory is owned by an unexpected user</strong>. This, in itself, is a problem worth investigating but it is unrelated and was revealed by the newer security check of git even though it does not match the threat described in <strong><a href="https://github.com/git-for-windows/git/security/advisories/GHSA-vw2c-22j4-2fh2">CVE-2022-24765</a></strong>.</p>
<p>It appears non trivial to enforce a consistent ownership of files and directories, either within docker or outside docker when networked file systems are involved. The Gitea server was not troubled by this inconsistency so far because the permissions allow it to write and read where expected, regardless of the owner. It is not worth looking into but it is ancient and unrelated.</p> <p>It appears non trivial to enforce a consistent ownership of files and directories, either within docker or outside docker when networked file systems are involved. The Gitea server was not troubled by this inconsistency so far because the permissions allow it to write and read where expected, regardless of the owner. It is not worth looking into but it is ancient and unrelated.</p>
<p>Gitea runs under a dedicated user, either when installed <a href="https://docs.gitea.io/en-us/install-from-binary/#recommended-server-configuration">from binary</a> or from <a href="https://docs.gitea.io/en-us/install-with-docker/">docker</a> and <a href="https://github.com/go-gitea/gitea/blob/main/modules/git/git.go#L196-L207">modifies the global git configuration</a> depending on the git version at initialization time. Fixing the problem can therefore be done by <a href="https://lab.forgefriends.org/forgefriends/forgefriends/-/merge_requests/50/diffs#bcd72ff867cbd1ddd5b6518c3a05b5f1a6021286_209_209">disabling the security check in the global git config file at initialization time</a>. It also requires a minimum version of git 2.36 to be installed, which is the case for Gitea docker images with <a href="https://github.com/go-gitea/gitea/pull/19871">versions >= 1.16.9</a>.</p> <p>Gitea runs under a dedicated user, either when installed <a href="https://docs.gitea.io/en-us/install-from-binary/#recommended-server-configuration">from binary</a> or from <a href="https://docs.gitea.io/en-us/install-with-docker/">docker</a> and <a href="https://github.com/go-gitea/gitea/blob/main/modules/git/git.go#L196-L207">modifies the global git configuration</a> depending on the git version at initialization time. Fixing the problem can therefore be done by <a href="https://lab.forgefriends.org/forgefriends/forgefriends/-/merge_requests/50/diffs#bcd72ff867cbd1ddd5b6518c3a05b5f1a6021286_209_209">disabling the security check in the global git config file at initialization time</a>. It also requires a minimum version of git 2.36 to be installed, which is the case for Gitea docker images with <a href="https://github.com/go-gitea/gitea/pull/19876">versions >= 1.16.9</a>.</p>
</content> </content>
</entry> </entry>
<entry xml:lang="en"> <entry xml:lang="en">

2
blog/unsafe-repository-is-owned-by-someone-else/index.html
View File

@ -251,7 +251,7 @@
<p>It is safe to <a href="https://lab.forgefriends.org/forgefriends/forgefriends/-/merge_requests/50/diffs">disable the security check in Gitea</a>. It is not vulnerable to <strong><a href="https://github.com/git-for-windows/git/security/advisories/GHSA-vw2c-22j4-2fh2">CVE-2022-24765</a></strong> because it calls the git CLI <a href="https://github.com/go-gitea/gitea/blob/main/modules/git/command.go#L160">after changing its working directory</a> to be the git repository targeted by the command (for instance <a href="https://github.com/go-gitea/gitea/blob/main/modules/git/diff.go#L38-L45">diff</a>) or a temporary directory. Therefore <strong>it will not explore the parent directories looking for a git configuration file</strong>.</p> <p>It is safe to <a href="https://lab.forgefriends.org/forgefriends/forgefriends/-/merge_requests/50/diffs">disable the security check in Gitea</a>. It is not vulnerable to <strong><a href="https://github.com/git-for-windows/git/security/advisories/GHSA-vw2c-22j4-2fh2">CVE-2022-24765</a></strong> because it calls the git CLI <a href="https://github.com/go-gitea/gitea/blob/main/modules/git/command.go#L160">after changing its working directory</a> to be the git repository targeted by the command (for instance <a href="https://github.com/go-gitea/gitea/blob/main/modules/git/diff.go#L38-L45">diff</a>) or a temporary directory. Therefore <strong>it will not explore the parent directories looking for a git configuration file</strong>.</p>
<p>The security check is triggered because the repository is owned by an unexpected user (root instead of git typically) and <strong>not because a parent directory is owned by an unexpected user</strong>. This, in itself, is a problem worth investigating but it is unrelated and was revealed by the newer security check of git even though it does not match the threat described in <strong><a href="https://github.com/git-for-windows/git/security/advisories/GHSA-vw2c-22j4-2fh2">CVE-2022-24765</a></strong>.</p> <p>The security check is triggered because the repository is owned by an unexpected user (root instead of git typically) and <strong>not because a parent directory is owned by an unexpected user</strong>. This, in itself, is a problem worth investigating but it is unrelated and was revealed by the newer security check of git even though it does not match the threat described in <strong><a href="https://github.com/git-for-windows/git/security/advisories/GHSA-vw2c-22j4-2fh2">CVE-2022-24765</a></strong>.</p>
<p>It appears non trivial to enforce a consistent ownership of files and directories, either within docker or outside docker when networked file systems are involved. The Gitea server was not troubled by this inconsistency so far because the permissions allow it to write and read where expected, regardless of the owner. It is not worth looking into but it is ancient and unrelated.</p> <p>It appears non trivial to enforce a consistent ownership of files and directories, either within docker or outside docker when networked file systems are involved. The Gitea server was not troubled by this inconsistency so far because the permissions allow it to write and read where expected, regardless of the owner. It is not worth looking into but it is ancient and unrelated.</p>
<p>Gitea runs under a dedicated user, either when installed <a href="https://docs.gitea.io/en-us/install-from-binary/#recommended-server-configuration">from binary</a> or from <a href="https://docs.gitea.io/en-us/install-with-docker/">docker</a> and <a href="https://github.com/go-gitea/gitea/blob/main/modules/git/git.go#L196-L207">modifies the global git configuration</a> depending on the git version at initialization time. Fixing the problem can therefore be done by <a href="https://lab.forgefriends.org/forgefriends/forgefriends/-/merge_requests/50/diffs#bcd72ff867cbd1ddd5b6518c3a05b5f1a6021286_209_209">disabling the security check in the global git config file at initialization time</a>. It also requires a minimum version of git 2.36 to be installed, which is the case for Gitea docker images with <a href="https://github.com/go-gitea/gitea/pull/19871">versions &gt;= 1.16.9</a>.</p> <p>Gitea runs under a dedicated user, either when installed <a href="https://docs.gitea.io/en-us/install-from-binary/#recommended-server-configuration">from binary</a> or from <a href="https://docs.gitea.io/en-us/install-with-docker/">docker</a> and <a href="https://github.com/go-gitea/gitea/blob/main/modules/git/git.go#L196-L207">modifies the global git configuration</a> depending on the git version at initialization time. Fixing the problem can therefore be done by <a href="https://lab.forgefriends.org/forgefriends/forgefriends/-/merge_requests/50/diffs#bcd72ff867cbd1ddd5b6518c3a05b5f1a6021286_209_209">disabling the security check in the global git config file at initialization time</a>. It also requires a minimum version of git 2.36 to be installed, which is the case for Gitea docker images with <a href="https://github.com/go-gitea/gitea/pull/19876">versions &gt;= 1.16.9</a>.</p>
</div> </div>
<br> <br>

2
tags/gitea/atom.xml
View File

@ -139,7 +139,7 @@
&lt;p&gt;It is safe to &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs&quot;&gt;disable the security check in Gitea&lt;&#x2F;a&gt;. It is not vulnerable to &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt; because it calls the git CLI &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;command.go#L160&quot;&gt;after changing its working directory&lt;&#x2F;a&gt; to be the git repository targeted by the command (for instance &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;diff.go#L38-L45&quot;&gt;diff&lt;&#x2F;a&gt;) or a temporary directory. Therefore &lt;strong&gt;it will not explore the parent directories looking for a git configuration file&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt; &lt;p&gt;It is safe to &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs&quot;&gt;disable the security check in Gitea&lt;&#x2F;a&gt;. It is not vulnerable to &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt; because it calls the git CLI &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;command.go#L160&quot;&gt;after changing its working directory&lt;&#x2F;a&gt; to be the git repository targeted by the command (for instance &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;diff.go#L38-L45&quot;&gt;diff&lt;&#x2F;a&gt;) or a temporary directory. Therefore &lt;strong&gt;it will not explore the parent directories looking for a git configuration file&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt;
&lt;p&gt;The security check is triggered because the repository is owned by an unexpected user (root instead of git typically) and &lt;strong&gt;not because a parent directory is owned by an unexpected user&lt;&#x2F;strong&gt;. This, in itself, is a problem worth investigating but it is unrelated and was revealed by the newer security check of git even though it does not match the threat described in &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt; &lt;p&gt;The security check is triggered because the repository is owned by an unexpected user (root instead of git typically) and &lt;strong&gt;not because a parent directory is owned by an unexpected user&lt;&#x2F;strong&gt;. This, in itself, is a problem worth investigating but it is unrelated and was revealed by the newer security check of git even though it does not match the threat described in &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt;
&lt;p&gt;It appears non trivial to enforce a consistent ownership of files and directories, either within docker or outside docker when networked file systems are involved. The Gitea server was not troubled by this inconsistency so far because the permissions allow it to write and read where expected, regardless of the owner. It is not worth looking into but it is ancient and unrelated.&lt;&#x2F;p&gt; &lt;p&gt;It appears non trivial to enforce a consistent ownership of files and directories, either within docker or outside docker when networked file systems are involved. The Gitea server was not troubled by this inconsistency so far because the permissions allow it to write and read where expected, regardless of the owner. It is not worth looking into but it is ancient and unrelated.&lt;&#x2F;p&gt;
&lt;p&gt;Gitea runs under a dedicated user, either when installed &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-from-binary&#x2F;#recommended-server-configuration&quot;&gt;from binary&lt;&#x2F;a&gt; or from &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-with-docker&#x2F;&quot;&gt;docker&lt;&#x2F;a&gt; and &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;git.go#L196-L207&quot;&gt;modifies the global git configuration&lt;&#x2F;a&gt; depending on the git version at initialization time. Fixing the problem can therefore be done by &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs#bcd72ff867cbd1ddd5b6518c3a05b5f1a6021286_209_209&quot;&gt;disabling the security check in the global git config file at initialization time&lt;&#x2F;a&gt;. It also requires a minimum version of git 2.36 to be installed, which is the case for Gitea docker images with &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;pull&#x2F;19871&quot;&gt;versions &amp;gt;= 1.16.9&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt; &lt;p&gt;Gitea runs under a dedicated user, either when installed &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-from-binary&#x2F;#recommended-server-configuration&quot;&gt;from binary&lt;&#x2F;a&gt; or from &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-with-docker&#x2F;&quot;&gt;docker&lt;&#x2F;a&gt; and &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;git.go#L196-L207&quot;&gt;modifies the global git configuration&lt;&#x2F;a&gt; depending on the git version at initialization time. Fixing the problem can therefore be done by &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs#bcd72ff867cbd1ddd5b6518c3a05b5f1a6021286_209_209&quot;&gt;disabling the security check in the global git config file at initialization time&lt;&#x2F;a&gt;. It also requires a minimum version of git 2.36 to be installed, which is the case for Gitea docker images with &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;pull&#x2F;19876&quot;&gt;versions &amp;gt;= 1.16.9&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
</content> </content>
</entry> </entry>
<entry xml:lang="en"> <entry xml:lang="en">

2
tags/hostea/atom.xml
View File

@ -139,7 +139,7 @@
&lt;p&gt;It is safe to &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs&quot;&gt;disable the security check in Gitea&lt;&#x2F;a&gt;. It is not vulnerable to &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt; because it calls the git CLI &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;command.go#L160&quot;&gt;after changing its working directory&lt;&#x2F;a&gt; to be the git repository targeted by the command (for instance &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;diff.go#L38-L45&quot;&gt;diff&lt;&#x2F;a&gt;) or a temporary directory. Therefore &lt;strong&gt;it will not explore the parent directories looking for a git configuration file&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt; &lt;p&gt;It is safe to &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs&quot;&gt;disable the security check in Gitea&lt;&#x2F;a&gt;. It is not vulnerable to &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt; because it calls the git CLI &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;command.go#L160&quot;&gt;after changing its working directory&lt;&#x2F;a&gt; to be the git repository targeted by the command (for instance &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;diff.go#L38-L45&quot;&gt;diff&lt;&#x2F;a&gt;) or a temporary directory. Therefore &lt;strong&gt;it will not explore the parent directories looking for a git configuration file&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt;
&lt;p&gt;The security check is triggered because the repository is owned by an unexpected user (root instead of git typically) and &lt;strong&gt;not because a parent directory is owned by an unexpected user&lt;&#x2F;strong&gt;. This, in itself, is a problem worth investigating but it is unrelated and was revealed by the newer security check of git even though it does not match the threat described in &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt; &lt;p&gt;The security check is triggered because the repository is owned by an unexpected user (root instead of git typically) and &lt;strong&gt;not because a parent directory is owned by an unexpected user&lt;&#x2F;strong&gt;. This, in itself, is a problem worth investigating but it is unrelated and was revealed by the newer security check of git even though it does not match the threat described in &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt;
&lt;p&gt;It appears non trivial to enforce a consistent ownership of files and directories, either within docker or outside docker when networked file systems are involved. The Gitea server was not troubled by this inconsistency so far because the permissions allow it to write and read where expected, regardless of the owner. It is not worth looking into but it is ancient and unrelated.&lt;&#x2F;p&gt; &lt;p&gt;It appears non trivial to enforce a consistent ownership of files and directories, either within docker or outside docker when networked file systems are involved. The Gitea server was not troubled by this inconsistency so far because the permissions allow it to write and read where expected, regardless of the owner. It is not worth looking into but it is ancient and unrelated.&lt;&#x2F;p&gt;
&lt;p&gt;Gitea runs under a dedicated user, either when installed &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-from-binary&#x2F;#recommended-server-configuration&quot;&gt;from binary&lt;&#x2F;a&gt; or from &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-with-docker&#x2F;&quot;&gt;docker&lt;&#x2F;a&gt; and &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;git.go#L196-L207&quot;&gt;modifies the global git configuration&lt;&#x2F;a&gt; depending on the git version at initialization time. Fixing the problem can therefore be done by &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs#bcd72ff867cbd1ddd5b6518c3a05b5f1a6021286_209_209&quot;&gt;disabling the security check in the global git config file at initialization time&lt;&#x2F;a&gt;. It also requires a minimum version of git 2.36 to be installed, which is the case for Gitea docker images with &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;pull&#x2F;19871&quot;&gt;versions &amp;gt;= 1.16.9&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt; &lt;p&gt;Gitea runs under a dedicated user, either when installed &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-from-binary&#x2F;#recommended-server-configuration&quot;&gt;from binary&lt;&#x2F;a&gt; or from &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-with-docker&#x2F;&quot;&gt;docker&lt;&#x2F;a&gt; and &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;git.go#L196-L207&quot;&gt;modifies the global git configuration&lt;&#x2F;a&gt; depending on the git version at initialization time. Fixing the problem can therefore be done by &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs#bcd72ff867cbd1ddd5b6518c3a05b5f1a6021286_209_209&quot;&gt;disabling the security check in the global git config file at initialization time&lt;&#x2F;a&gt;. It also requires a minimum version of git 2.36 to be installed, which is the case for Gitea docker images with &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;pull&#x2F;19876&quot;&gt;versions &amp;gt;= 1.16.9&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
</content> </content>
</entry> </entry>
<entry xml:lang="en"> <entry xml:lang="en">

2
tags/problem/atom.xml
View File

@ -139,7 +139,7 @@
&lt;p&gt;It is safe to &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs&quot;&gt;disable the security check in Gitea&lt;&#x2F;a&gt;. It is not vulnerable to &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt; because it calls the git CLI &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;command.go#L160&quot;&gt;after changing its working directory&lt;&#x2F;a&gt; to be the git repository targeted by the command (for instance &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;diff.go#L38-L45&quot;&gt;diff&lt;&#x2F;a&gt;) or a temporary directory. Therefore &lt;strong&gt;it will not explore the parent directories looking for a git configuration file&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt; &lt;p&gt;It is safe to &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs&quot;&gt;disable the security check in Gitea&lt;&#x2F;a&gt;. It is not vulnerable to &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt; because it calls the git CLI &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;command.go#L160&quot;&gt;after changing its working directory&lt;&#x2F;a&gt; to be the git repository targeted by the command (for instance &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;diff.go#L38-L45&quot;&gt;diff&lt;&#x2F;a&gt;) or a temporary directory. Therefore &lt;strong&gt;it will not explore the parent directories looking for a git configuration file&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt;
&lt;p&gt;The security check is triggered because the repository is owned by an unexpected user (root instead of git typically) and &lt;strong&gt;not because a parent directory is owned by an unexpected user&lt;&#x2F;strong&gt;. This, in itself, is a problem worth investigating but it is unrelated and was revealed by the newer security check of git even though it does not match the threat described in &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt; &lt;p&gt;The security check is triggered because the repository is owned by an unexpected user (root instead of git typically) and &lt;strong&gt;not because a parent directory is owned by an unexpected user&lt;&#x2F;strong&gt;. This, in itself, is a problem worth investigating but it is unrelated and was revealed by the newer security check of git even though it does not match the threat described in &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt;
&lt;p&gt;It appears non trivial to enforce a consistent ownership of files and directories, either within docker or outside docker when networked file systems are involved. The Gitea server was not troubled by this inconsistency so far because the permissions allow it to write and read where expected, regardless of the owner. It is not worth looking into but it is ancient and unrelated.&lt;&#x2F;p&gt; &lt;p&gt;It appears non trivial to enforce a consistent ownership of files and directories, either within docker or outside docker when networked file systems are involved. The Gitea server was not troubled by this inconsistency so far because the permissions allow it to write and read where expected, regardless of the owner. It is not worth looking into but it is ancient and unrelated.&lt;&#x2F;p&gt;
&lt;p&gt;Gitea runs under a dedicated user, either when installed &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-from-binary&#x2F;#recommended-server-configuration&quot;&gt;from binary&lt;&#x2F;a&gt; or from &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-with-docker&#x2F;&quot;&gt;docker&lt;&#x2F;a&gt; and &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;git.go#L196-L207&quot;&gt;modifies the global git configuration&lt;&#x2F;a&gt; depending on the git version at initialization time. Fixing the problem can therefore be done by &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs#bcd72ff867cbd1ddd5b6518c3a05b5f1a6021286_209_209&quot;&gt;disabling the security check in the global git config file at initialization time&lt;&#x2F;a&gt;. It also requires a minimum version of git 2.36 to be installed, which is the case for Gitea docker images with &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;pull&#x2F;19871&quot;&gt;versions &amp;gt;= 1.16.9&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt; &lt;p&gt;Gitea runs under a dedicated user, either when installed &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-from-binary&#x2F;#recommended-server-configuration&quot;&gt;from binary&lt;&#x2F;a&gt; or from &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-with-docker&#x2F;&quot;&gt;docker&lt;&#x2F;a&gt; and &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;git.go#L196-L207&quot;&gt;modifies the global git configuration&lt;&#x2F;a&gt; depending on the git version at initialization time. Fixing the problem can therefore be done by &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs#bcd72ff867cbd1ddd5b6518c3a05b5f1a6021286_209_209&quot;&gt;disabling the security check in the global git config file at initialization time&lt;&#x2F;a&gt;. It also requires a minimum version of git 2.36 to be installed, which is the case for Gitea docker images with &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;pull&#x2F;19876&quot;&gt;versions &amp;gt;= 1.16.9&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
</content> </content>
</entry> </entry>
<entry xml:lang="en"> <entry xml:lang="en">

2
tags/troubleshoot/atom.xml
View File

@ -139,7 +139,7 @@
&lt;p&gt;It is safe to &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs&quot;&gt;disable the security check in Gitea&lt;&#x2F;a&gt;. It is not vulnerable to &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt; because it calls the git CLI &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;command.go#L160&quot;&gt;after changing its working directory&lt;&#x2F;a&gt; to be the git repository targeted by the command (for instance &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;diff.go#L38-L45&quot;&gt;diff&lt;&#x2F;a&gt;) or a temporary directory. Therefore &lt;strong&gt;it will not explore the parent directories looking for a git configuration file&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt; &lt;p&gt;It is safe to &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs&quot;&gt;disable the security check in Gitea&lt;&#x2F;a&gt;. It is not vulnerable to &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt; because it calls the git CLI &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;command.go#L160&quot;&gt;after changing its working directory&lt;&#x2F;a&gt; to be the git repository targeted by the command (for instance &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;diff.go#L38-L45&quot;&gt;diff&lt;&#x2F;a&gt;) or a temporary directory. Therefore &lt;strong&gt;it will not explore the parent directories looking for a git configuration file&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt;
&lt;p&gt;The security check is triggered because the repository is owned by an unexpected user (root instead of git typically) and &lt;strong&gt;not because a parent directory is owned by an unexpected user&lt;&#x2F;strong&gt;. This, in itself, is a problem worth investigating but it is unrelated and was revealed by the newer security check of git even though it does not match the threat described in &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt; &lt;p&gt;The security check is triggered because the repository is owned by an unexpected user (root instead of git typically) and &lt;strong&gt;not because a parent directory is owned by an unexpected user&lt;&#x2F;strong&gt;. This, in itself, is a problem worth investigating but it is unrelated and was revealed by the newer security check of git even though it does not match the threat described in &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt;
&lt;p&gt;It appears non trivial to enforce a consistent ownership of files and directories, either within docker or outside docker when networked file systems are involved. The Gitea server was not troubled by this inconsistency so far because the permissions allow it to write and read where expected, regardless of the owner. It is not worth looking into but it is ancient and unrelated.&lt;&#x2F;p&gt; &lt;p&gt;It appears non trivial to enforce a consistent ownership of files and directories, either within docker or outside docker when networked file systems are involved. The Gitea server was not troubled by this inconsistency so far because the permissions allow it to write and read where expected, regardless of the owner. It is not worth looking into but it is ancient and unrelated.&lt;&#x2F;p&gt;
&lt;p&gt;Gitea runs under a dedicated user, either when installed &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-from-binary&#x2F;#recommended-server-configuration&quot;&gt;from binary&lt;&#x2F;a&gt; or from &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-with-docker&#x2F;&quot;&gt;docker&lt;&#x2F;a&gt; and &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;git.go#L196-L207&quot;&gt;modifies the global git configuration&lt;&#x2F;a&gt; depending on the git version at initialization time. Fixing the problem can therefore be done by &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs#bcd72ff867cbd1ddd5b6518c3a05b5f1a6021286_209_209&quot;&gt;disabling the security check in the global git config file at initialization time&lt;&#x2F;a&gt;. It also requires a minimum version of git 2.36 to be installed, which is the case for Gitea docker images with &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;pull&#x2F;19871&quot;&gt;versions &amp;gt;= 1.16.9&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt; &lt;p&gt;Gitea runs under a dedicated user, either when installed &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-from-binary&#x2F;#recommended-server-configuration&quot;&gt;from binary&lt;&#x2F;a&gt; or from &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-with-docker&#x2F;&quot;&gt;docker&lt;&#x2F;a&gt; and &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;git.go#L196-L207&quot;&gt;modifies the global git configuration&lt;&#x2F;a&gt; depending on the git version at initialization time. Fixing the problem can therefore be done by &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs#bcd72ff867cbd1ddd5b6518c3a05b5f1a6021286_209_209&quot;&gt;disabling the security check in the global git config file at initialization time&lt;&#x2F;a&gt;. It also requires a minimum version of git 2.36 to be installed, which is the case for Gitea docker images with &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;pull&#x2F;19876&quot;&gt;versions &amp;gt;= 1.16.9&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
</content> </content>
</entry> </entry>
<entry xml:lang="en"> <entry xml:lang="en">

2
tags/upgrade/atom.xml
View File

@ -71,7 +71,7 @@
&lt;p&gt;It is safe to &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs&quot;&gt;disable the security check in Gitea&lt;&#x2F;a&gt;. It is not vulnerable to &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt; because it calls the git CLI &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;command.go#L160&quot;&gt;after changing its working directory&lt;&#x2F;a&gt; to be the git repository targeted by the command (for instance &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;diff.go#L38-L45&quot;&gt;diff&lt;&#x2F;a&gt;) or a temporary directory. Therefore &lt;strong&gt;it will not explore the parent directories looking for a git configuration file&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt; &lt;p&gt;It is safe to &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs&quot;&gt;disable the security check in Gitea&lt;&#x2F;a&gt;. It is not vulnerable to &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt; because it calls the git CLI &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;command.go#L160&quot;&gt;after changing its working directory&lt;&#x2F;a&gt; to be the git repository targeted by the command (for instance &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;diff.go#L38-L45&quot;&gt;diff&lt;&#x2F;a&gt;) or a temporary directory. Therefore &lt;strong&gt;it will not explore the parent directories looking for a git configuration file&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt;
&lt;p&gt;The security check is triggered because the repository is owned by an unexpected user (root instead of git typically) and &lt;strong&gt;not because a parent directory is owned by an unexpected user&lt;&#x2F;strong&gt;. This, in itself, is a problem worth investigating but it is unrelated and was revealed by the newer security check of git even though it does not match the threat described in &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt; &lt;p&gt;The security check is triggered because the repository is owned by an unexpected user (root instead of git typically) and &lt;strong&gt;not because a parent directory is owned by an unexpected user&lt;&#x2F;strong&gt;. This, in itself, is a problem worth investigating but it is unrelated and was revealed by the newer security check of git even though it does not match the threat described in &lt;strong&gt;&lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git-for-windows&#x2F;git&#x2F;security&#x2F;advisories&#x2F;GHSA-vw2c-22j4-2fh2&quot;&gt;CVE-2022-24765&lt;&#x2F;a&gt;&lt;&#x2F;strong&gt;.&lt;&#x2F;p&gt;
&lt;p&gt;It appears non trivial to enforce a consistent ownership of files and directories, either within docker or outside docker when networked file systems are involved. The Gitea server was not troubled by this inconsistency so far because the permissions allow it to write and read where expected, regardless of the owner. It is not worth looking into but it is ancient and unrelated.&lt;&#x2F;p&gt; &lt;p&gt;It appears non trivial to enforce a consistent ownership of files and directories, either within docker or outside docker when networked file systems are involved. The Gitea server was not troubled by this inconsistency so far because the permissions allow it to write and read where expected, regardless of the owner. It is not worth looking into but it is ancient and unrelated.&lt;&#x2F;p&gt;
&lt;p&gt;Gitea runs under a dedicated user, either when installed &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-from-binary&#x2F;#recommended-server-configuration&quot;&gt;from binary&lt;&#x2F;a&gt; or from &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-with-docker&#x2F;&quot;&gt;docker&lt;&#x2F;a&gt; and &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;git.go#L196-L207&quot;&gt;modifies the global git configuration&lt;&#x2F;a&gt; depending on the git version at initialization time. Fixing the problem can therefore be done by &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs#bcd72ff867cbd1ddd5b6518c3a05b5f1a6021286_209_209&quot;&gt;disabling the security check in the global git config file at initialization time&lt;&#x2F;a&gt;. It also requires a minimum version of git 2.36 to be installed, which is the case for Gitea docker images with &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;pull&#x2F;19871&quot;&gt;versions &amp;gt;= 1.16.9&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt; &lt;p&gt;Gitea runs under a dedicated user, either when installed &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-from-binary&#x2F;#recommended-server-configuration&quot;&gt;from binary&lt;&#x2F;a&gt; or from &lt;a href=&quot;https:&#x2F;&#x2F;docs.gitea.io&#x2F;en-us&#x2F;install-with-docker&#x2F;&quot;&gt;docker&lt;&#x2F;a&gt; and &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;blob&#x2F;main&#x2F;modules&#x2F;git&#x2F;git.go#L196-L207&quot;&gt;modifies the global git configuration&lt;&#x2F;a&gt; depending on the git version at initialization time. Fixing the problem can therefore be done by &lt;a href=&quot;https:&#x2F;&#x2F;lab.forgefriends.org&#x2F;forgefriends&#x2F;forgefriends&#x2F;-&#x2F;merge_requests&#x2F;50&#x2F;diffs#bcd72ff867cbd1ddd5b6518c3a05b5f1a6021286_209_209&quot;&gt;disabling the security check in the global git config file at initialization time&lt;&#x2F;a&gt;. It also requires a minimum version of git 2.36 to be installed, which is the case for Gitea docker images with &lt;a href=&quot;https:&#x2F;&#x2F;github.com&#x2F;go-gitea&#x2F;gitea&#x2F;pull&#x2F;19876&quot;&gt;versions &amp;gt;= 1.16.9&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
</content> </content>
</entry> </entry>
<entry xml:lang="en"> <entry xml:lang="en">