ssh fetcher: Since MD5 -> SHA256 move Windows FIPS warning is no longer needed
This commit is contained in:
parent
30fce55d38
commit
dfa2cc4fff
|
@ -44,19 +44,7 @@ namespace Sparkles {
|
||||||
}
|
}
|
||||||
|
|
||||||
if (RequiredFingerprint != null) {
|
if (RequiredFingerprint != null) {
|
||||||
string host_fingerprint;
|
string host_fingerprint = DeriveFingerprint (host_key);
|
||||||
|
|
||||||
try {
|
|
||||||
host_fingerprint = DeriveFingerprint (host_key);
|
|
||||||
|
|
||||||
} catch (InvalidOperationException e) {
|
|
||||||
// "Unapproved cryptographic algorithms" won't work when FIPS is enabled on Windows.
|
|
||||||
// Software like Cisco AnyConnect can demand this feature is on, so we show an error
|
|
||||||
Logger.LogInfo ("Auth", "Unable to derive fingerprint: ", e);
|
|
||||||
errors.Add ("error: Can't check fingerprint due to FIPS being enabled");
|
|
||||||
|
|
||||||
return false;
|
|
||||||
}
|
|
||||||
|
|
||||||
if (host_fingerprint == null || RequiredFingerprint!= host_fingerprint) {
|
if (host_fingerprint == null || RequiredFingerprint!= host_fingerprint) {
|
||||||
Logger.LogInfo ("Auth", "Fingerprint doesn't match");
|
Logger.LogInfo ("Auth", "Fingerprint doesn't match");
|
||||||
|
|
Loading…
Reference in a new issue