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.

Sign up for GitHub

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

Jump to bottom

Do not allow inactive users to access repositories using private keys (#3887) #3889

Merged
merged 2 commits into from
May 2, 2018
Merged

Do not allow inactive users to access repositories using private keys (#3887) #3889

merged 2 commits into from
May 2, 2018

Conversation

lafriks
Copy link
Member

@lafriks lafriks commented May 2, 2018

Backport #3887

@lafriks lafriks added type/bug topic/security Something leaks user information or is otherwise vulnerable. Should be fixed! labels May 2, 2018
@lafriks lafriks added this to the 1.4.1 milestone May 2, 2018
@techknowlogick
Copy link
Member

techknowlogick commented May 2, 2018 •
edited
Loading

LGTM. CI fail seems unrelated.

@bkcsoft bkcsoft added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label May 2, 2018
@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 May 2, 2018
@lafriks lafriks merged commit e35d7ae into go-gitea:release/v1.4 May 2, 2018
@lafriks lafriks deleted the backport/fix_ssh_inactive_user branch May 2, 2018 17:37
@lenidh lenidh mentioned this pull request May 12, 2018
Closed
7 tasks
@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.
Reviewers

@sapk sapk sapk approved these changes

Assignees
No one assigned
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! type/bug
Projects
None yet
Milestone
1.4.1
Development

Successfully merging this pull request may close these issues.
4 participants
@lafriks @techknowlogick @sapk @bkcsoft