You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if you make any web-based commits, such as merging a pull request, the commit shows up as being authored by the user but signed by Gitea as per the GPG key installed during the Gitea configuration phase.
What I'd like is to be able to sign all web-based activities with my own signing key that can be verified via user settings.
Is there a reason why that isn't an option if we have steps in place to verify the user is who they claim to be, such as 2FA?
Configuring the system to use my signing key is not an option since there are others who share the service so it would appear as if though I was signing their web commits.
Screenshots
No response
The text was updated successfully, but these errors were encountered:
Feature Description
Currently if you make any web-based commits, such as merging a pull request, the commit shows up as being authored by the user but signed by Gitea as per the GPG key installed during the Gitea configuration phase.
What I'd like is to be able to sign all web-based activities with my own signing key that can be verified via user settings.
Is there a reason why that isn't an option if we have steps in place to verify the user is who they claim to be, such as 2FA?
Configuring the system to use my signing key is not an option since there are others who share the service so it would appear as if though I was signing their web commits.
Screenshots
No response
The text was updated successfully, but these errors were encountered: