ssh: support rsa-sha2-256/512 on the server side
This lets clients know we support rsa-sha2-256/512 signatures from ssh-rsa public keys. OpenSSH prefers to break the connection rather than attempting trial and error, apparently. We don't enable support for the "ext-info-s" because we're not interested in any client->server extensions. This also replaces isAcceptableAlgo which was rejecting the rsa-sha2-256/512-cert-v01@openssh.com public key algorithms. Tested with OpenSSH 9.1 on macOS Ventura. Fixes golang/go#49269 Updates golang/go#49952 Co-authored-by: Nicola Murino <nicola.murino@gmail.com> Co-authored-by: Kristin Davidson <kdavidson@atlassian.com> Change-Id: I4955c3b12bb45575e9977ac657bb5805b49d00c3 Reviewed-on: https://go-review.googlesource.com/c/crypto/+/447757 Run-TryBot: Filippo Valsorda <filippo@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Roland Shoemaker <roland@golang.org> Reviewed-by: Nicola Murino <nicola.murino@gmail.com> Reviewed-by: Michael Knyszek <mknyszek@google.com>
This commit is contained in:
co-authored by
Nicola Murino
Kristin Davidson
parent
21d60a1521
commit
6fad3dfc18
@@ -132,9 +132,7 @@ func TestClientAuthPublicKey(t *testing.T) {
|
||||
if err := tryAuth(t, config); err != nil {
|
||||
t.Fatalf("unable to dial remote side: %s", err)
|
||||
}
|
||||
// Once the server implements the server-sig-algs extension, this will turn
|
||||
// into KeyAlgoRSASHA256.
|
||||
if len(signer.used) != 1 || signer.used[0] != KeyAlgoRSA {
|
||||
if len(signer.used) != 1 || signer.used[0] != KeyAlgoRSASHA256 {
|
||||
t.Errorf("unexpected Sign/SignWithAlgorithm calls: %q", signer.used)
|
||||
}
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user