On 26/02/2020 21:06, Dr Paul Dale wrote:
> You should be able to set the environment variable OPENSSL_CONF to
> test/fips.cnf which will then load a FIPS only configuration.
>
> Teething problems are expected. Not everything has been activated in
> the FIPS module but enough has to do some TLS
You should be able to set the environment variable OPENSSL_CONF to
test/fips.cnf which will then load a FIPS only configuration.
Teething problems are expected. Not everything has been activated in the FIPS
module but enough has to do some TLS.
Pauli
--
Dr Paul Dale | Distinguished Architect
> That's 5 weeks from now, I'd thought the basic structure might be present
> now.
It is. You probably have to look at the tests to see how to use things.
On Wed, Feb 26, 2020 at 11:44 AM Salz, Rich wrote:
>
> The 3.0 release is a work in progress and is not done yet.
>
> FIPS 3.0 === OpenSSL 3.0, using a FIPS-validated crypto provider which will
> be part of OpenSSL 3.0.
>
> The architecture documents are at https://www.openssl.org/docs
Rich, I'v
The 3.0 release is a work in progress and is not done yet.
FIPS 3.0 === OpenSSL 3.0, using a FIPS-validated crypto provider which will be
part of OpenSSL 3.0.
The architecture documents are at https://www.openssl.org/docs
On 2/26/20, 2:40 PM, "Sam Roberts" wrote:
On Wed, Feb 26, 2020 at
On Wed, Feb 26, 2020 at 8:36 AM Salz, Rich wrote:
>
> >I'd like to give this a spin, to get an idea what's going to be
> involved in porting from FIPS2.0 to 3.0, any pointers on where to
> start?
>
> Per the blog post, "most applications should just need to be recompiled." :)
>
> Get t
>I'd like to give this a spin, to get an idea what's going to be
involved in porting from FIPS2.0 to 3.0, any pointers on where to
start?
Per the blog post, "most applications should just need to be recompiled." :)
Get the source via instructions here: https://www.openssl.org/source
On Tue, Feb 25, 2020 at 8:00 PM Matt Caswell wrote:
> alpha1, 2020-03-31: Basic functionality plus basic FIPS module
I'd like to give this a spin, to get an idea what's going to be
involved in porting from FIPS2.0 to 3.0, any pointers on where to
start?
Sam
On Wednesday, 26 February 2020 08:59:01 CET, Phani 2004 wrote:
Thanks for the quick response Matt.
My command was :
openssl s_client -connect 10.29.20.26 -cipher ECDHE-RSA-AES128-SHA -tls1_2.
I did not realise that "2" was not copied.
I am trying to implement combined algo support on our engine
