From: "Pinzone, Gerard" <GPinzone@aaccorp.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: OpenSSH FIPS 140-2
Date: Mon, 24 Jun 2019 18:50:00 -0000 [thread overview]
Message-ID: <e5f252b902f04393b6d581eb28e655fe@aaccorp.com> (raw)
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.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2019-06-24 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 18:50 Pinzone, Gerard [this message]
2019-06-25 3:06 ` Brian Inglis
2019-06-25 13:45 Pinzone, Gerard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e5f252b902f04393b6d581eb28e655fe@aaccorp.com \
--to=gpinzone@aaccorp.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).