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

Cannot add GPG signing sub-key #6529

New Issue
Closed
opened 2025-11-02 06:58:37 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 06:58:37 -06:00
Owner
Copy Link

Originally created by @etanot on GitHub (Dec 16, 2020).

Type:

Bug report

Description

When I'm trying to add my GPG signing sub-key, Gitea shows me this error message:

This GPG key is not usable with any email address associated with your account.

Basically, I run gpg --armor --export <signing-sub-key-id>! (notice, I've added a ! at end of ID, to tell GPG to only export my master key and specific sub-key information, see this gnupg-users mailing list thread). I've no issue with adding my sub-key this way to Github and Gitlab.

Steps to Reproduce

  • Run gpg --armor --export <signing-sub-key-id>! command.
  • Copy the output of the command (public key).
  • Go Settings -> SSH/GPG keys -> Manage GPG keys.
  • Click on Add key button in Manage GPG keys section.
  • Paste the copied public key.
  • Now, click on green Add key button.

Expected Output

Key should be added successfully.

Actual Output

Getting this error message, This GPG key is not usable with any email address associated with your account.

Originally created by @etanot on GitHub (Dec 16, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.14.0+dev-389-g88b585c2e (https://try.gitea.io) - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (https://try.gitea.io/user/settings/keys) - [ ] No ##### Type: Bug report ## Description When I'm trying to add my GPG signing sub-key, Gitea shows me this error message: `This GPG key is not usable with any email address associated with your account.` Basically, I run `gpg --armor --export <signing-sub-key-id>!` (notice, I've added a `!` at end of ID, to tell GPG to only export my master key and specific sub-key information, see [this gnupg-users](https://lists.gnupg.org/pipermail/gnupg-users/2017-January/057400.html) mailing list thread). I've no issue with adding my sub-key this way to Github and Gitlab. ### Steps to Reproduce - Run `gpg --armor --export <signing-sub-key-id>!` command. - Copy the output of the command (public key). - Go `Settings -> SSH/GPG keys -> Manage GPG keys`. - Click on `Add key` button in `Manage GPG keys` section. - Paste the copied public key. - Now, click on green `Add key` button. ### Expected Output Key should be added successfully. ### Actual Output Getting this error message, `This GPG key is not usable with any email address associated with your account.`
GiteaMirror commented 2025-11-02 06:58:38 -06:00
Author
Owner
Copy Link

@a1012112796 commented on GitHub (Dec 16, 2020):

@finn0 hello, Now gitea only allow add public gpg keys bounded with the user's email.

@a1012112796 commented on GitHub (Dec 16, 2020): @finn0 hello, Now gitea only allow add public gpg keys bounded with the user's email.
GiteaMirror commented 2025-11-02 06:58:38 -06:00
Author
Owner
Copy Link

@etanot commented on GitHub (Dec 17, 2020):

Thanks @a1012112796, then closing this bug report and opening another issue for the feature request.

@etanot commented on GitHub (Dec 17, 2020): Thanks @a1012112796, then closing this bug report and opening another issue for the feature request.
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
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#6529
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?