GPG KEY FAILS IF SEC KEY START FROM 0

[phyr0s]

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

Description

If GPG key starts from 0, gitea doesn't recognize the key. If the key starts from other numbers it works fine, however if key starts from 0 it does not work.

...

Screenshots

Here is the key added in the config options, as you can see start from 0 the key. That key is extracted from --> gpg --list-secret-keys --keyid-format LONG -->

This is the commit signed, gitea doesn't recognize the key

I tried same key in GITHUB and GITLAB and woks perfect. It's means that is a bug from gitea

[sapk]

I wonder if this is related to #6778 where we didn't find the root cause but the key fingerprint seems to start with 0.

For this specific case can you provide a generated private/public key pair (not yours) ?
I will add it to the test suite to confirm and maybe fix the case if it is on our side.

[phyr0s]

@sapk Take it, no password needed
test23.zip

[zeripath]

@videmort so I'm not certain that is necessarily the preceding zero as that should go in to the db without the preceding zero. Could you check if it is in the db with the keyid with/without the preceding the zero?

I wonder if you're being hit with the Timezone bug?

[zeripath]

Sorry I finally got round to generating a key with a zero leading ID