HADOOP-18202. create-release fails fatal: unsafe repository#4188
Merged
steveloughran merged 1 commit intoapache:trunkfrom Apr 18, 2022
Merged
Conversation
Since CVE-2022-24765 in April 2022, git refuses to work in directories whose owner != the current user, unless explicitly told to trust it. This patches the create-release script to trust the /build/source dir mounted from the hosting OS, whose userid is inevitably different from that of the account in the container running git. Change-Id: I1646d7f5d098252c12b000c51a99f9df11919306
Contributor
Author
|
gets to the git clean command without problems |
This was referenced Apr 18, 2022
|
🎊 +1 overall
This message was automatically generated. |
Contributor
Author
|
thx. my full test of this pr (run the script) is still going on and appears to have uploaded snapshot 3.4.0 artifacts. |
asfgit
pushed a commit
that referenced
this pull request
Apr 18, 2022
Since April 2022/CVE-2022-24765, git refuses to work in directories whose owner != the current user, unless explicitly told to trust it. This patches the create-release script to trust the /build/source dir mounted from the hosting OS, whose userid is inevitably different from that of the account in the container running git. Contributed by: Steve Loughran, Ayush Saxena and the new git error messages Change-Id: I855a105e6d0ab533468f9436578c8d4f81b0840b
asfgit
pushed a commit
that referenced
this pull request
Apr 18, 2022
Since April 2022/CVE-2022-24765, git refuses to work in directories whose owner != the current user, unless explicitly told to trust it. This patches the create-release script to trust the /build/source dir mounted from the hosting OS, whose userid is inevitably different from that of the account in the container running git. Contributed by: Steve Loughran, Ayush Saxena and the new git error messages Change-Id: I855a105e6d0ab533468f9436578c8d4f81b0840b
HarshitGupta11
pushed a commit
to HarshitGupta11/hadoop
that referenced
this pull request
Nov 28, 2022
) Since April 2022/CVE-2022-24765, git refuses to work in directories whose owner != the current user, unless explicitly told to trust it. This patches the create-release script to trust the /build/source dir mounted from the hosting OS, whose userid is inevitably different from that of the account in the container running git. Contributed by: Steve Loughran, Ayush Saxena and the new git error messages
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since CVE-2022-24765 in April 2022, git refuses to work in directories
whose owner != the current user, unless explicitly told to trust it.
This patches the create-release script to trust the /build/source
dir mounted from the hosting OS, whose userid is inevitably different
from that of the account in the container running git.
Description of PR
How was this patch tested?
going to test the PR on my build machine (a different laptop)
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?