Hi Steve,

Thanks a lot for the explanation. We have range of products that provides
network connectivity.

1.  On these  we would be using TPM to provide additional security.

2.  On the products that are bit slow in software cryptographic operation,
we also would be using hardware acceleration chips, that would do crypto
operations.


In my previous post related to TPM like how to deal with Non-FIPS compliant
TPM chips, does it need any change in FIPS module size etc?

In this post I wanted to know to support an hardware accelerator that
supports FIPS enabled algorithms implemented apart from supporting the
hardware from OpenSSL side, do we need to make changes in FIPS module as
well.

Both posts looks similar. I apologize  I should have clearly mentioned
these 2 posts are in different contexts.

Thanks a lot.

Regards
Jayalakshmi


On Sat, Jul 5, 2014 at 10:46 PM, Dr. Stephen Henson <st...@openssl.org>
wrote:

> On Sat, Jul 05, 2014, Jayalakshmi bhat wrote:
>
> > Hi All,
> >
> > We want to support a hardware accelerator on our device. We are using
> > OpenSSL with OpenSSL FIPS Object module. I wanted to know if we can add
> > engine support in OpenSSL FIPS Object module.
> >
>
> If you literally mean adding ENGINE support to the OpenSSL FIPS Object
> module
> then you can but it would IMHO be a pointless exercise. The ENGINE code was
> stripped out to keep the number of dependencies down in the module.
>
> If you mean add ENGINE support to the FIPS capable OpenSSL then you don't
> need
> to as ENGINE support is already there.
>
> I suggest you explain exactly what you want to do.
>
> Steve.
> --
> Dr Stephen N. Henson. OpenSSL project core developer.
> Commercial tech support now available see: http://www.openssl.org
> ______________________________________________________________________
> OpenSSL Project                                 http://www.openssl.org
> User Support Mailing List                    openssl-users@openssl.org
> Automated List Manager                           majord...@openssl.org
>

Reply via email to