Ok, I finally figure out my issues. I was setting the environment variables
when I should not have been. The "make depend" set will setup all the fips
dependencies you need. So I was shooting myself in the foot so to speak.
Using the commands listed in the Security Policy for OpenSSL worked fine
on
Hello Jacques,
On Wed, Jun 17, 2015 at 3:47 PM, Jacques FLORENCE <
jacques.p.flore...@gmail.com> wrote:
> I want to create an engine for ECDSA, and implement my own signing
> operation in hardware.
> But I want to use the default verify operation to be used.
> Is there currently a way to do that?
> I want to create an engine for ECDSA, and implement my own signing
> operation in hardware.
> But I want to use the default verify operation to be used.
> Is there currently a way to do that?
Yosh.
I think you can declare a new ECDSA_METHOD structure and keep the
references to the openssl ecdsa
I want to create an engine for ECDSA, and implement my own signing
operation in hardware.
But I want to use the default verify operation to be used.
Is there currently a way to do that?
There is an ECDSA_METHOD_set_verify function, but it looks like there is no
ECDSA_METHOD_get_verify, that I coul
Hi,
I need to encrypt CMS and, to do so, verify the certificat chain.
All the certificats and CRLs are downloaded from a LDAP repository.
But, I want to reuse the certificat chain verification, whatever is the
origin
of certificats and CRLs in the chain (database, files, LDAP, HTTP), because