Can't connect when FIPS is enforced on Windows.

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.

In my case, I got the error when I used Shared connection Mode. But when I tried Direct Connection Mode, I managed to connect to the database.

Since SHA1 class is not FIPS compliant but HMACSHA1 is, changing the line from

var sha = SHA1.Create();

to

var sha = new HMACSHA1();

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.