gitea.com does not accept RFC8332 RSA SHA-2 signature algorithms rsa-sha2-256/512 #27

Closed
opened 2022-05-31 15:23:05 +00:00 by rozhuk.im · 4 comments

According to this:
https://www.openssh.com/txt/release-8.2

ssh-rsa is going to deprecation, but rsa-sha2-256/512 is secure and should be used.

But I am get error on push:

git@gitea.com: Permission denied (publickey).
remote: sign_and_send_pubkey: no mutual signature supported
remote: git@gitea.com: Permission denied (publickey).
According to this: https://www.openssh.com/txt/release-8.2 ```ssh-rsa``` is going to deprecation, but ```rsa-sha2-256/512``` is secure and should be used. But I am get error on push: ``` git@gitea.com: Permission denied (publickey). ``` ``` remote: sign_and_send_pubkey: no mutual signature supported remote: git@gitea.com: Permission denied (publickey). ```

This is related to an issue with golang itself: https://github.com/golang/go/issues/49269

This is related to an issue with golang itself: https://github.com/golang/go/issues/49269
Author

At least it can be workarounded then OpenSSH server used to handle ssh proto - in my installation it works fine.

At least it can be workarounded then OpenSSH server used to handle ssh proto - in my installation it works fine.
Owner

Gitea.com is using internal ssh server.

Gitea.com is using internal ssh server.
Author

Fixed.

Fixed.
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/gitea.com#27
No description provided.