FIPS 140-2 Compliant Encryption Algorithms
Our institution just began enforcing FIPS 140-2 compliance for encryption in Windows 10. The latest version of the Illiad client now balks on connection, producing a error with the option to save feedback. We've traced this to a Windows registry key that enables compliance with FIPS 140-2. If we disable the policy temporarily, Illiad Client connects as expected. The trouble is, we're not permitted to disable the policy.
Is there a way for the current version of Illiad Client to use a FIPS 140-2 compliant encryption algorithm or can it be an option for a future version? This will only become more problematic for government/military clients.
Here's a little background from an independent article https://www.howtogeek.com/245859/why-you-shouldnt-enable-fips-compliant-encryption-on-windows/
Comments
Hi Stephen
I've forwarded this to our support staff to get back to you with an answer regarding this security issue.
Please sign in to leave a comment.