public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: OpenSSH FIPS 140-2
Date: Tue, 25 Jun 2019 03:06:00 -0000	[thread overview]
Message-ID: <3823ab71-6770-278d-b604-688bfcf98315@SystematicSw.ab.ca> (raw)
In-Reply-To: <e5f252b902f04393b6d581eb28e655fe@aaccorp.com>

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:
https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules/search

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
modes.

-- 
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:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2019-06-25  3:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-24 18:50 Pinzone, Gerard
2019-06-25  3:06 ` Brian Inglis [this message]
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=3823ab71-6770-278d-b604-688bfcf98315@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).