OpenSSH FIPS 140-2

Brian Inglis
Tue Jun 25 03:06:00 GMT 2019

On 2019-06-24 12:50, Pinzone, Gerard wrote:
> I've been able to build OpenSSL 1.0.2 with FIPS support on Cygwin 32-bit and 
> native Windows using Visual Studio. The 64-bit edition of Cygwin doesn't
> build the FIPS module correctly. There is a workaround, but that workaround 
> invalidates the FIPS build requirements, thus the resulting binary will not
> be approved without a private certification that costs lots of $$$. I'd like
> to get OpenSSH to work with the OpenSSL I've built under 32-bit Cygwin, but
> that might require a custom build of OpenSSH. The latest Cygwin uses the
> newer 1.1.1 branch of OpenSSL, so I don't know if that will cause any
> compatibility problems.

> Having a FIPS 140-2 OpenSSH on a Windows OS is important for those in the 
> financial and government sector. Microsoft's port of OpenSSH uses LibreSSL
> (I think) and cannot be FIPS certified. It looks like Cygwin is our only
> hope.
I believe the implementation has to be validated and certified by NIST, so if
that is required, you will have to use an implementation with NIST
certification, listed at:

Enter either OpenSSH or OpenSSL in the Module Name box to search.

Check each certification for details of the hardware and software required to be
used to be compliant.

Please also remember the advice to only use FIPS modules where legally required,
and never enable anything which is historical, inactive, or has been revoked, as
it has been broken.

For good security use currently recommended non-FIPS algorithms, ciphers, and

Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list