Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[19.03]: gitea: 1.7.5 -> 1.7.6 #59391

Merged
merged 1 commit into from Apr 13, 2019
Merged

Conversation

flokli
Copy link
Contributor

@flokli flokli commented Apr 13, 2019

see #59387.

From release notes:

SECURITY: Prevent remote code execution vulnerability with mirror repo URL settings

Motivation for this change
Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

From [release notes](https://github.com/go-gitea/gitea/releases/tag/v1.7.6):

SECURITY: Prevent remote code execution vulnerability with mirror repo URL settings
(cherry picked from commit 7578ec4)
@flokli
Copy link
Contributor Author

flokli commented Apr 13, 2019

@GrahamcOfBorg test gitea

@flokli
Copy link
Contributor Author

flokli commented Apr 13, 2019

aarch64-linux tests passed on ofborg, the x86_64-linux locally. Merging.

@flokli flokli merged commit cd79d70 into NixOS:release-19.03 Apr 13, 2019
@flokli flokli deleted the 19.03/gitea-1.7.6 branch April 13, 2019 11:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants