The fipsinstall program runs the platform tests. I.e. you need to run
fipsinstall on the device at some point.
> Or are you suggesting that the presence of a standalone tool might influence
> the contents of such a security policy?
Yes. Well maybe. I’ll posit the possibility at the next
On Mon, Jul 27, 2020 at 3:39 PM Dr Paul Dale wrote:
> These are questions better asked of a FIPS lab since they are the experts
> and we are not.
>
>
That is a fair response.
I expect that your alternative installation process’s validity will depend
> on the security policy and what it says
These are questions better asked of a FIPS lab since they are the experts and
we are not.
I expect that your alternative installation process’s validity will depend on
the security policy and what it says needs to be done. This hasn’t been
written yet so there is no answer at this point.
Hi all,
I'm replacing OpenSSL 1.0.2 with OpenSSL 3.0 in an embedded environment
with very limited flash space. We need and use libcrypto and libssl but we
have no need for the openssl binary. To date it was never necessary to ship
this utility in our product. Now with OpenSSL 3.0 it appears the
> Grepping through all of my OpenSSL sources, I see only the
> above mention and one in 'Configurations\10-main.conf'.
>
> So how/when is 'gdi32.dll' needed? Maybe it was true in the old-days?
My guess is that you are right and that it was needed only for the function
readscreen(), used by
Hello lists.
I've a question/doubt about this passage in
NOTES-Windows.txt:
Linking your application
This section applies to all "native" builds.
If you link with *static OpenSSL libraries* then you're expected to
additionally link your application with
