Hi,
I am having difficulty finding a book that describes IPsec that includes IKEv2
and is preferably aimed at using Linux crypto. Can anyone recommend such a
book ?
Also, how do I find info on the cypto APIs eg. how to use cryptd (2.6.24
kernel) ?
I'm working on a project that uses an embedded hardware encryption engine that
needs to use async off-load. Is cryptd the entity for async hardware crypto
off-loading ?
Thanks,
Dean
MontaVista Software
Hi.
On Fri, Oct 31, 2008 at 03:08:48PM +0000, Dean Jenkins ([email protected]) wrote:
> I am having difficulty finding a book that describes IPsec that includes IKEv2
> and is preferably aimed at using Linux crypto. Can anyone recommend such a
> book ?
There is no such book I believe.
> Also, how do I find info on the cypto APIs eg. how to use cryptd (2.6.24
> kernel) ?
>
> I'm working on a project that uses an embedded hardware encryption engine that
> needs to use async off-load. Is cryptd the entity for async hardware crypto
> off-loading ?
cryptd is an software engine example of how hardware driver could be implemented.
--
Evgeniy Polyakov
Hi Evgeniy,
> > Also, how do I find info on the cypto APIs eg. how to use cryptd (2.6.24
> > kernel) ?
> >
> > I'm working on a project that uses an embedded hardware encryption engine
> > that needs to use async off-load. Is cryptd the entity for async hardware
> > crypto off-loading ?
>
> cryptd is an software engine example of how hardware driver could be
> implemented.
Are you saying that to implement an async hardware driver I could use the APIs
used by cryptd and create my own hwcryptd ?
If yes, is there any documentation for the APIs used by cryptd ?
Thanks,
Regards,
Dean Jenkins
MontaVista Software
Hi Dean.
On Mon, Nov 03, 2008 at 10:50:59AM +0000, Dean Jenkins ([email protected]) wrote:
> > cryptd is an software engine example of how hardware driver could be
> > implemented.
>
> Are you saying that to implement an async hardware driver I could use the APIs
> used by cryptd and create my own hwcryptd ?
Yes for the APIs used in cryptd, but usually hardware driver does not
need to have any threads attached, since completion of the event is
handled in the interrupt handler.
> If yes, is there any documentation for the APIs used by cryptd ?
No, there is no documentation except source code.
In some files you can even find this comments:
* HEAVY TODO: needs to kick Herbert XU to write documentation.
Herbert is a crypto maintainer who created async crypto interfaces you
found in cryptd. You can also check hardware crypto drivers in
drivers/crypto/ directory.
--
Evgeniy Polyakov