AW: AES-cipher offload to engine in openssl-fips

[Richard Levitte]

On Thu, 28 Feb 2019 00:51:24 +0100,
Dr. Matthias St. Pierre wrote:
> 
> 
> > Uhm, I'm confused. I thought we were talking about 3.0?
> 
> Well, the original post started at FIPS 2.0:
> 
>   > I am using openssl-fips-2.0.16 and openssl-1.0.2e.
>   https://mta.openssl.org/pipermail/openssl-users/2019-February/009919.html

Yes, it did...  and then evolved, as threads on the Internet often do
(or for that matter, in physical life too).

> But it seems like the discussion in the thread has drifted a little
> towards the FIPS 3.0 future, which explains our mutual confusion.

Yup :-)

> For that reason it is even more important that we don't use legacy
> terms like "FIPS capable" in the context of FIPS 3.0 and stick to
> "FIPS Providers" (or whatever correct new terms are; I'm currently
> not 100% up-to-date) instead.

Cool, we agree then :-)

"FIPS provider" is what we use within the team, or sometimes "FIPS
provider module".  They are synonymous, but the latter is more
precise.

Cheers,
Richard

-- 
Richard Levitte         levitte at openssl.org
OpenSSL Project         http://www.openssl.org/~levitte/