Skip to content

Expiry date of GPG key is reported wrong #6599

@tastytea

Description

@tastytea
  • Gitea version (or commit ref): 1.7.6
  • Git version:
  • Operating system:
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

I added a GPG key that expires 2020-04-05.

% LC_ALL=C gpg --list-keys 59346E0EA35C67E5
pub   rsa4096/59346E0EA35C67E5 2017-06-17 [SC] [expires: 2020-04-05]
      Key fingerprint = D5B4 C43B 48A8 79F6 3529  36E6 5934 6E0E A35C 67E5
uid                 [ultimate] tastytea <tastyteaXtastytea.de>
uid                 [ultimate] gentooXtastytea.de
sub   rsa4096/CA258ACA1C76DAA7 2017-06-17 [E] [expires: 2020-04-05]
sub   dsa3072/CFC39497F1B26E07 2018-07-16 [S] [expires: 2020-04-05]

Gitea claims that it is valid until 2022-01-23.

Screenshots

screenshot_2019-04-13T06:07:36

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions