DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=VHgz9iVIgfKuObeK
	5p+1Z0YyWCL+Sy+e48f1uVicVfuAQEYt2clXlU0uNcSLLTOKLc+PKjrEOXBtdU4/
	1Wa9zgsTG/kx+lBMIzsHOKvZHpSDVZ1WF0JDjMGaa7CvTsQFWqyIH9z5GeJQy5yE
	fou7G27MmLaqyxq/Vryk8wnSTY8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Reply-To: Brian.Inglis@SystematicSw.ab.ca
Subject: Re: OpenSSH FIPS 140-2
To: cygwin@cygwin.com
References: <e5f252b902f04393b6d581eb28e655fe@aaccorp.com>
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Openpgp: preference=signencrypt
Message-ID: <3823ab71-6770-278d-b604-688bfcf98315@SystematicSw.ab.ca>
Date: Mon, 24 Jun 2019 21:06:41 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <e5f252b902f04393b6d581eb28e655fe@aaccorp.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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