Anyone had a chance to look at this? I would really appreciate any help
someone offers.
Thanks,
--
Peter Barton
NetProtec
Original Message
Subject: OpenSSL FIPS 140-2 Compliant
From:
Date: Sat, July 26, 2014 10:15 am
To: openssl-users@openssl.org
I am attempting to compile
I am attempting to compile a current version of OpenVPN against an
OpenSSL-1.0.1h source that I compiled calling the OpenSSL-fips-2.0.5
module. I created libssl.a and libcrypto.a and I have been trying,
unsuccessfully, to compile the OpenVPN-2.3.4 calling these libraries. I
am far from an expert in
On Sun, Mar 16, 2014 at 5:49 AM, srikanth wrote:
> Hi,
>
> We are working on making our application FIPS 140-2 Compliant.
There's no such thing as FIPS Compliant. You use validated
cryptography, or you don't use validated cryptography.
If your marketing department calls your product FIPS
{Complia
process to build.
Do I need to build both fips module and openssl module by editing the
openssl.spec file to build both.
Appreciate help on this as I am new to the FIPS.
Thanks &Regards,
Srikanth
--
View this message in context:
http://openssl.6102.n7.nabble.com/OPENSSL-FIPS-140-2-tp48860.html
> I have one question in this. What did you mean by Suite B Algorithms ?
Google "crypto suite b" Or heck, even just "suite b"
/r$
--
Principal Security Engineer
Akamai Technology
Cambridge, MA
__
OpenSSL Project
ools Development
Bangalore, India
Contact : 402-56859
From: Jeffrey Walton
To: openssl-users@openssl.org
Date: 01/10/2013 10:08 PM
Subject:Re: How to link openssl FIPS 140-2 object module with openssl
binary
Sent by:owner-openssl-us...@openssl.org
On Thu, Ja
)
283-bit Elliptic Curves (Binary Fields)
AES-128
SHA-256
So, you have to plug in the required parameters.
Jeff
> From: Jeffrey Walton
> To: openssl-users@openssl.org
> Date: 01/10/2013 04:01 PM
> Subject:Re: How to link openssl FIPS 140-2 object module with op
correct algos /keys from
standard openssl lib ( without FIPS lib) to satisfy NIST SP 800-131 A
requirements ?
Thanks & Regards,
Nayna Jain
From: Jeffrey Walton
To: openssl-users@openssl.org
Date: 01/10/2013 04:01 PM
Subject:Re: How to link openssl FIPS 140-2 object module
On Thu, Jan 10, 2013 at 3:07 AM, Nayna Jain wrote:
>
> Hi,
>
> I want to use FIPS compliant algorithms and keys. For that I understand, I
> need to have Openssl FIPS object library along with default openssl.
>
> However, I am not understanding how to install them. My questions are :
>
> 1. Both a
Hi,
I want to use FIPS compliant algorithms and keys. For that I understand, I
need to have Openssl FIPS object library along with default openssl.
However, I am not understanding how to install them. My questions are :
1. Both are tar.gz. Should I run ./Configure, make and make install for
bot
ly 15, 2010 6:18 AM
To: openssl-users@openssl.org
Subject: Re: openssl FIPS 140-2 certificate after 2010
David Stafford wrote:
> What are the issues, if any, with using the "FIPS module" after the
> end of 2010 ?
> Does the certificate number 1051 become invalid ?
>
My
David Stafford wrote:
What are the issues, if any, with using the "FIPS module" after the
end of 2010 ?
Does the certificate number 1051 become invalid ?
My best guess at this point is that the OpenSSL FIPS Object Module v1.2
(aka the #1051 validation) proper remains usable, as that exact a
What are the issues, if any, with using the "FIPS module" after the
end of 2010 ?
Does the certificate number 1051 become invalid ?
Thanks,
David Stafford
__
OpenSSL Project http://www.openssl.org
U
Good news for developers and vendors of software for the U.S. and
Canadian government market where FIPS 140-2 validated cryptography is
required.
The "OpenSSL FIPS Object Module", a software component compatible with
the OpenSSL API, has been FIPS 140-2 validated (see certificate #1051
and Securit
Good news for developers and vendors of software for the U.S. and
Canadian government market where FIPS 140-2 validated cryptography is
required.
The "OpenSSL FIPS Object Module", a software component compatible with
the OpenSSL API, has been FIPS 140-2 validated (see certificate #733 and
Sec
15 matches
Mail list logo