Narrowly-scoped SSH keys #8394

Closed
opened 2025-11-02 08:04:43 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @raboof on GitHub (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

Originally created by @raboof on GitHub (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_
GiteaMirror added the type/proposal label 2025-11-02 08:04:43 -06:00
Author
Owner

@bendem commented on GitHub (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

@bendem commented on GitHub (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](https://user-images.githubusercontent.com/2681677/217471082-2620dfeb-755a-47fb-9f50-c01b9431bfb1.png)
Author
Owner

@raboof commented on GitHub (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 commented on GitHub (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!
Author
Owner

@bendem commented on GitHub (Feb 8, 2023):

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

@bendem commented on GitHub (Feb 8, 2023): You could require PR for your branch, I think that would prevent deploy keys from committing. Untested though.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#8394