Invaild expiration date shown for GPG key without expiry date #791
Labels
No labels
accessibility
bug
bug
infrastructure
Codeberg
contributions welcome
docs
duplicate
enhancement
infrastructure
legal
licence / ToS
please chill
we are volunteers
public relations
question
question
user support
s/Forgejo
s/Forgejo/migration
s/Pages
s/Weblate
s/Woodpecker
security
service
upstream
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Codeberg/Community#791
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
I just found the following for my "never going to expire" GPG key in the SSH / GPG Keys settings page:
What's that "Jan 01, 0001"? That's 2021 years ago!
Anyway, is it a good idea to not have a expiry date?
Opened a bug fix at https://github.com/go-gitea/gitea/pull/22171
Merged to Gitea, but looks like it hasn't reached Codeberg yet. Should I wait until the fix to land here or close it now?
It will be fixed when Codeberg pulls the next update. Closing for now as this will be seen live in a few days.
I see this is closed, but I have this problem as well. GPG keys made on Windows with Kleopatra and a never expire. I also changed the key to expire and had the same issue with verification and a time difference error:
The provided GPG key, signature and token do not match or token is out-of-date.Hello, that's a different problem. That's related to GPG verification, but your screenshot says it's already verified. If it's still a problem, feel free to open a new issue about it.
for the Verified keys though it shows Verified, this just says, it matches.
I can start a new issue. Thanks!