RE: nCipher HSM kernel driver submission feedback request

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

 



> > The driver code for the hardware is straightforward and does not
> > contain any cryptographic components as the cryptography is handled
> > within the hardware's secure boundary. We have no plans to use the
> > linux kernel crypto APIs as our customers require compliance to the FIPS
> 140 standard or the eIDAS regulations.
>
> But what I said was, you NEED to use the linux kernel crypto apis as you need
> to not try to create your own.
>
> Just because this is the way you did it before, does not mean it is the correct
> thing to do.
>
> So what is wrong if you do use the existing apis?  What is preventing you
> from doing that?
>

Sorry Greg but I'm not understanding what the issue is. Can you please explain a
bit more what you mean with the apis?

Our driver code is just a tube between proprietary code on the host machine and
proprietary code on the HSM. We are not trying to create our own linux crypto
apis because all the crypto stuff is happening in the existing proprietary code.

Regards,
Dave


David Kim
Senior Software Engineer
Tel: +44 1223 703449

nCipher Security
One Station Square
Cambridge CB1 2GA
United Kingdom





[Index of Archives]     [Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

  Powered by Linux