The SSH server implementation fails to verify that the signature algorithm used in a public-key authentication signature matches the algorithm specified in the authentication request. In the `server read auth request pk` function within `russh/src/server/encrypted.rs`, the server uses the requested algorithm `pubkey algo` only to decode the key, while the actual signature verification relies on the algorithm embedded within the signature blob itself. This allows a client with a valid RSA private key to claim the use of `rsa-sha2-512` while actually providing a valid `ssh-rsa` SHA-1 signature. This can lead to the bypass of security restrictions for servers that disable SHA-1 or result in misleading audit logs for applications that record the requested algorithm.