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

Rocky Linux 9 (Fedora 34) cannot recognize the signature added by Gitea #14003

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

Originally created by @ExplodingDragon on GitHub (Jan 16, 2025).

Due to https://github.com/ProtonMail/go-crypto/pull/208, RPM versions < 4.17 cannot recognize signature information generated by ProtonMail/go-crypto. (see https://github.com/ProtonMail/go-crypto/issues/263)

There is no need to consider fixing this issue until a better solution is available; this issue is only for archiving purposes.

Affected versions : all versions after a8e7caedfa.

Originally created by @ExplodingDragon on GitHub (Jan 16, 2025). Due to https://github.com/ProtonMail/go-crypto/pull/208, `RPM versions < 4.17` cannot recognize signature information generated by `ProtonMail/go-crypto`. (see https://github.com/ProtonMail/go-crypto/issues/263) There is no need to consider fixing this issue until a better solution is available; this issue is only for archiving purposes. **Affected versions** : all versions after a8e7caedfa062cd8ea34f722806b3f162d24e939.
GiteaMirror added the type/bugtype/upstream labels 2025-11-02 10:59:47 -06:00
GiteaMirror commented 2025-11-02 10:59:48 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jan 16, 2025):

The ProtonMail/go-crypto 1.1.x is required by go-git 5.13

And yes, according to https://github.com/ProtonMail/go-crypto/issues/263, it is a regression in go-crypto 1.1 ..... I guess it should be fixed by upstream, either revert to the old behavior, or introduce an option

ps: Gitea 1.23.x is also affected because go-git there was also upgraded to 5.13 to fix security issues (#33133 in 1.23)

@wxiaoguang commented on GitHub (Jan 16, 2025): The `ProtonMail/go-crypto 1.1.x` is required by `go-git 5.13` * https://github.com/go-git/go-git/blob/v5.12.0/go.mod (go-crypto 1.0) * https://github.com/go-git/go-git/blob/v5.13.0/go.mod (go-crypto 1.1) And yes, according to https://github.com/ProtonMail/go-crypto/issues/263, it is a regression in go-crypto 1.1 ..... I guess it should be fixed by upstream, either revert to the old behavior, or introduce an option ps: Gitea 1.23.x is also affected because go-git there was also upgraded to 5.13 to fix security issues (#33133 in 1.23)
GiteaMirror commented 2025-11-02 10:59:48 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Feb 27, 2025):

Upstream has merged the fix: Make Issuer Key ID signature subpacket non-critical ProtonMail/go-crypto#266

@wxiaoguang commented on GitHub (Feb 27, 2025): Upstream has merged the fix: Make Issuer Key ID signature subpacket non-critical ProtonMail/go-crypto#266
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/bug type/upstream
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#14003
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?