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

Correctly check http git access rights for reverse proxy authorized users (#3721) #3743

Merged
merged 2 commits into from
Apr 4, 2018

Conversation

lafriks
Copy link
Member

@lafriks lafriks commented Mar 30, 2018

Backport #3721

@lafriks lafriks added the topic/security Something leaks user information or is otherwise vulnerable. Should be fixed! label Mar 30, 2018
@lafriks lafriks added this to the 1.4.1 milestone Mar 30, 2018
@tboerger tboerger added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Mar 30, 2018
@lunny
Copy link
Member

lunny commented Mar 30, 2018

CI failed but #3744 will fix that.

@bkcsoft bkcsoft added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Mar 31, 2018
@lafriks lafriks merged commit 641d481 into go-gitea:release/v1.4 Apr 4, 2018
@lafriks lafriks deleted the backport/rev_proxy_auth branch April 4, 2018 17:06
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. topic/security Something leaks user information or is otherwise vulnerable. Should be fixed!
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants