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

Narrowly-scoped SSH keys #18374

Closed
raboof opened this issue Jan 23, 2022 · 3 comments
Closed

Narrowly-scoped SSH keys #18374

raboof opened this issue Jan 23, 2022 · 3 comments
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@raboof
Copy link

raboof commented Jan 23, 2022

Feature Description

I think it would be great if it were possible to register SSH keys that are only valid for a particular repo, or even a particular branch - somewhat like 'deploy keys', but with write permissions.

This might be useful for example when some external process automatically creates and pushes commits: that external process could be given its own SSH key, so that when it might get compromised only that particular repo is affected.

Screenshots

No response

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Jan 25, 2022
@bendem
Copy link

bendem commented Feb 8, 2023

  • somewhat like 'deploy keys', but with write permissions.

What about deploy keys but with write permissions? Is there anything wrong with them?

image

@raboof
Copy link
Author

raboof commented Feb 8, 2023

Awesome! I could've sworn that wasn't there back in January, but I must have simply missed it.

It would still be nice to have it on the branch level rather than on the repo level, but this is already sufficient to close this request, I think.

Thanks for pointing it out!

@raboof raboof closed this as completed Feb 8, 2023
@bendem
Copy link

bendem commented Feb 8, 2023

You could require PR for your branch, I think that would prevent deploy keys from committing. Untested though.

@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

3 participants