Derek Morr wrote:
> Hi Garrett,
>
> I've already started on both userspace and kernel drivers for padlock.
> They're only in my local svn repository, but I'll see if I can get them
> publicly accessible.
>
> The KCF driver isn't too functional at the moment (I was just discussing this
> with Darren in #opensolaris this morning). Since the driver is for on-die
> functions, I'm not sure how to make it attach, short of making it a pseudo
> device.
>
> The userspace (PKCS11) driver has SHA-1, SHA-256, HMAC-SHA-1 and HMAC-SHA-256
> done. I'm working on the AES support now (it's written, but it still buggy).
>
> -derek
> --
> This message posted from opensolaris.org
> _______________________________________________
> crypto-discuss mailing list
> crypto-discuss at opensolaris.org
> http://opensolaris.org/mailman/listinfo/crypto-discuss
>
Okay, cool. Maybe I'll have a look at the RNG side if you haven't done
that yet.
As far as attach, I think the best thing is may be to do a forceattach,
or to arrange for it to be loaded by the platmod or CPU module. I've
not looked at the x86 cpu module to see how much stuff it has in it for
different CPU support, but that might be a place to start.
There may be other ways if the Padlock is accessible via other registers
in IO space, as well. I might have a look at it in a bit, if you'd like.
-- Garrett
--
Garrett D'Amore, Principal Software Engineer
Tadpole Computer / Computing Technologies Division,
General Dynamics C4 Systems
http://www.tadpolecomputer.com/
Phone: 951 325-2134 Fax: 951 325-2191
