You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a Windows machine has the FIPS 140-2 restriction enabled then connections failed with a message that the encryption being used is not FIPS compliant.
The text was updated successfully, but these errors were encountered:
Since SHA1 class is not FIPS compliant but HMACSHA1 is, changing the line from
varsha=SHA1.Create();
to
varsha=newHMACSHA1();
might suffice.
However, I tried to reproduce the error but there are differences between the latest release, which is almost two years old, and the current master. It might have been solved already in another way.
It would be great if a new release can be published soon.
When a Windows machine has the FIPS 140-2 restriction enabled then connections failed with a message that the encryption being used is not FIPS compliant.
The text was updated successfully, but these errors were encountered: