github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-13 19:37:47 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

[PR #3889] [MERGED] Do not allow inactive users to access repositories using private keys (#3887) #17127

New Issue
Closed
opened 2025-11-02 12:26:56 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 12:26:56 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/go-gitea/gitea/pull/3889
Author: @lafriks
Created: 5/2/2018
Status: ✅ Merged
Merged: 5/2/2018
Merged by: @lafriks

Base: release/v1.4 ← Head: backport/fix_ssh_inactive_user

📝 Commits (2)

  • c730288 Do not allow inactive users to access repositories using private keys (#3887)
  • a37a92d Merge branch 'release/v1.4' into backport/fix_ssh_inactive_user

📊 Changes

1 file changed (+6 additions, -0 deletions)

View changed files

📝 cmd/serv.go (+6 -0)

📄 Description

Backport #3887

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/go-gitea/gitea/pull/3889 **Author:** [@lafriks](https://github.com/lafriks) **Created:** 5/2/2018 **Status:** ✅ Merged **Merged:** 5/2/2018 **Merged by:** [@lafriks](https://github.com/lafriks) **Base:** `release/v1.4` ← **Head:** `backport/fix_ssh_inactive_user` --- ### 📝 Commits (2) - [`c730288`](https://github.com/go-gitea/gitea/commit/c7302880cfd39eed01e15347f0706df9a2876787) Do not allow inactive users to access repositories using private keys (#3887) - [`a37a92d`](https://github.com/go-gitea/gitea/commit/a37a92d4c333b123bd0a844b28fd90f0b16abaa9) Merge branch 'release/v1.4' into backport/fix_ssh_inactive_user ### 📊 Changes **1 file changed** (+6 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `cmd/serv.go` (+6 -0) </details> ### 📄 Description Backport #3887 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-02 12:26:56 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#17127
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?