github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 18:48:08 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Auto generated GPG signing keys #11751

New Issue
Open
opened 2025-11-02 09:46:40 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 09:46:40 -06:00
Owner
Copy Link

Originally created by @prologic on GitHub (Sep 30, 2023).

Feature Description

Hey team 👋 Can we please consider adding an Admin UI option to auto-generate a GPG Signing key for the server and just make that a thing? I really don't want to get in there and do this by hand, and honestly don't feel like that's really necessary.

Screenshots

No response

Originally created by @prologic on GitHub (Sep 30, 2023). ### Feature Description Hey team 👋 Can we please consider adding an Admin UI option to auto-generate a GPG Signing key for the server and just make that a thing? I really don't want to get in there and do this by hand, and honestly don't feel like that's really necessary. ### Screenshots _No response_
GiteaMirror added the type/proposal label 2025-11-02 09:46:40 -06:00
GiteaMirror commented 2025-11-02 09:46:40 -06:00
Author
Owner
Copy Link

@e-desouza commented on GitHub (Oct 11, 2023):

In the interim, it would be great to have instructions of how to generate/consume these keys in an unattended environment.
There are various instructions online (e.g using --pinentry-mode=loopback) which don't work with gitea and generate errors like Inappropriate ioctl for device, not a tty device etc.

@e-desouza commented on GitHub (Oct 11, 2023): In the interim, it would be great to have instructions of how to generate/consume these keys in an unattended environment. There are various instructions online (e.g using --pinentry-mode=loopback) which don't work with gitea and generate errors like `Inappropriate ioctl for device`, `not a tty device` etc.
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 type/proposal
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#11751
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?