The provided SSH key, signature or token do not match or token is out-of-date

Gitea Usages

Alexey September 19, 2023, 8:50pm 1

I just setup and use last version if Gitea via proxmox.
I add my ssh keys and all works fine BUT,
When i try to check my rsa keys with gitea web-interface i have massage:

The provided SSH key, signature or token do not match or token is out-of-date.

I try to:

1. use basic RSA keys;
2. use new Ed25519 keys;
3. Try to use 1Password SSH auth.
   No result, i still get this message, but ssh work correctly.
   To check keys i use this:

echo -n 'number from GITEA web interface' | ssh-keygen -Y sign -n gitea -f Path_to_Private_key

You can check SHA256 in screen below

RSA_keys1221×409 183 KB

noraltavir September 20, 2023, 8:41am 2

The same problem when using Windows SSH.

Alexey September 20, 2023, 9:21am 3

I saw that users have a similar topic on Github about this problem with Gitea RSA check in web console, and it is also not resolved.

simplyniceweb September 4, 2024, 6:32pm 4

github.com/go-gitea/gitea

When I add ssh key to an account, I get Can not verify your SSH key: ... asn1: structure error: tags don't match

opened 05:50PM - 31 Jan 23 UTC

lasersPew

type/bug

### Description When I add ssh key to an account, I get Can not verify your SSH… key: failed to parse DER encoded public key as either PKIX or PEM RSA Key: asn1: structure error: tags don't match (16 vs {class:1 tag:15 length:112 isCompound:true}) {optional:false explicit:false application:false private:false defaultValue: tag: stringType:0 timeType:0 set:false omitEmpty:false} publicKeyInfo @2 asn1: structure error: tags don't match (16 vs {class:1 tag:15 length:112 isCompound:true}) {optional:false explicit:false application:false private:false defaultValue: tag: stringType:0 timeType:0 set:false omitEmpty:false} PublicKey @2 ### Gitea Version 1.18.1 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist https://gist.github.com/lasersPew/749f3818a1cba92f35de084dabb35840 ### Screenshots   ### Git Version 2.36.3 ### Operating System alpine 3.16.3 ### How are you running Gitea? Using Docker CLI inside Alpine 0.17 in WSL, no Docker Desktop using WSL2 kernel. Set things up using Portainer, Stacks specifically. Here's the config: ``` yaml version: "3" networks: gitea: external: false services: server: image: gitea/gitea:1.18.1 container_name: gitea environment: - USER_UID=1000 - USER_GID=1000 - GITEA__database__DB_TYPE=postgres - GITEA__database__HOST=db:5432 - GITEA__database__NAME=gitea - GITEA__database__USER=gitea - GITEA__database__PASSWD=password1 restart: always networks: - gitea volumes: - /config/gitea:/data:rw - /etc/timezone:/etc/timezone:ro - /etc/localtime:/etc/localtime:ro - /config/git:/git:rw ports: - 3001:3000 - 2222:22 depends_on: - db db: image: postgres:14.6-alpine container_name: gitea-db restart: always environment: - POSTGRES_USER=gitea - POSTGRES_PASSWORD=password1 - POSTGRES_DB=gitea networks: - gitea volumes: - /config/postgres:/var/lib/postgresql/data ``` ### Database PostgreSQL

Please read this comment, it works on my end. Maximize the git bash and run the command.

MrSuddenJoy September 4, 2024, 8:06pm 5

@Alexey: the error message you are getting simply means that Gitea was not able to verify provided key really belongs to you. This maybe due to number of reasons.