Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ssh key ecdsa_sk support #11203

Closed
8 tasks
markuman opened this issue Apr 24, 2020 · 1 comment · Fixed by #13462
Closed
8 tasks

ssh key ecdsa_sk support #11203

markuman opened this issue Apr 24, 2020 · 1 comment · Fixed by #13462
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality

Comments

@markuman
Copy link

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

Description

openssh 8.2 introduced native u2f support with the new key type ecdsa_sk.
Currently it is not possible to add such key to your gitea profile

error log

2020/04/24 06:50:06 ...user/setting/keys.go:96:KeysPost() [E] AddPublicKey: calcFingerprintSSHKeygen: 'ssh-keygen -lf /tmp/gitea_keytest979760198' failed with error 'exec(101286:AddPublicKey) failed: exit status 255(<nil>) stdout:  stderr: /tmp/gitea_keytest979760198 is not a public key file.\01503d
	': /tmp/gitea_keytest979760198 is not a public key file.\01503d

example public key

[email protected] AAAAInNrLWVjZHNhLXNoYTItbmlzdHAyNTZAb3BlbnNzaC5jb20AAAAIbmlzdHAyNTYAAABBBGh2rclhwbyMMGVsERVKAgbYMlVmF7r7AYSddt6cZsTnG4V6XA2/mbKZlohsMRRJvURrUb0FR+izCIK9FY52cJwAAAAEc3NoOg== solo

@lafriks lafriks added the type/enhancement An improvement of existing functionality label Apr 24, 2020
@stale
Copy link

stale bot commented Jun 23, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label Jun 23, 2020
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Jun 24, 2020
@stale stale bot removed the issue/stale label Jun 24, 2020
@go-gitea go-gitea locked and limited conversation to collaborators Mar 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants