Re: Can applications built with 'FIPS Capable OpenSSL' be called as 'FIPS 140-2' certified?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Dipak B <deepak.redmi2@xxxxxxxxx>, "openssl-users@xxxxxxxxxxx" <openssl-users@xxxxxxxxxxx>
Subject: Re: Can applications built with 'FIPS Capable OpenSSL' be called as 'FIPS 140-2' certified?
From: "Salz, Rich via openssl-users" <openssl-users@xxxxxxxxxxx>
Date: Wed, 3 Jul 2019 17:07:45 +0000
Accept-language: en-US
In-reply-to: <CAMd_dYWTG_ecL3pZvGRDcSLvC1QPS+vcBggUwtCL2UmUumTzsg@mail.gmail.com>
References: <CAMd_dYWTG_ecL3pZvGRDcSLvC1QPS+vcBggUwtCL2UmUumTzsg@mail.gmail.com>
Reply-to: "Salz, Rich" <rsalz@xxxxxxxxxx>
User-agent: Microsoft-MacOutlook/10.1a.0.190609

Didn’t you just ask this question? :)

If you followed the Win32 build instructions *exactly* and you build your application to turn on FIPS mode and link against the canister, then yes.

If you made changes to the process, then no.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: Can applications built with 'FIPS Capable OpenSSL' be called as 'FIPS 140-2' certified?
  - From: Dipak B

References:
- Can applications built with 'FIPS Capable OpenSSL' be called as 'FIPS 140-2' certified?
  - From: Dipak B

Prev by Date: Can applications built with 'FIPS Capable OpenSSL' be called as 'FIPS 140-2' certified?
Next by Date: Re: Can applications built with 'FIPS Capable OpenSSL' be called as 'FIPS 140-2' certified?
Previous by thread: Can applications built with 'FIPS Capable OpenSSL' be called as 'FIPS 140-2' certified?
Next by thread: Re: Can applications built with 'FIPS Capable OpenSSL' be called as 'FIPS 140-2' certified?
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux] [Linux OMAP] [Linux MIPS] [ECOS] [Asterisk Internet PBX] [Linux API]

Powered by Linux