Fix Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass

[lamcodeofpwnosec]

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass. ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

[Shaptic]

This seems to be a copy-paste of CVE-2024-45337? This does not apply to this repository, as it only uses crypto/sha256 for hashing which is entirely unaffected by this CVE.