Garrett D'Amore wrote:
Actually, it sounds like this particular kind of functionality is useful enough that it should be part of the DDI. There are functions like this (for example CRC functionality required for calculating hashes used in many ethernet MAC chips, SHA1 that is used in various places, etc.) that should really be part of a common DDI. They could be kept in separate modules, so that they don't increase the size of kernel/unix.
We already have Kernel modules for MD5/SHA1/SHA256-512 that are directly callable software or you can go through the crypto framework. The direct interfaces are Consolidation Private but given I've made all of libmd Committed we should probably just make the same commitment to the kernel ones (after all the API and implementation are identical just compiled as a lib an kernel module).
Currently the Crypto Framework is not part of the DDI but we hope that it will become so at some point, both the API and the SPI.
Advert: There will soon be a separate mailing list and project page for the crypto framework - we are just putting the initial content up.
-- Darren J Moffat _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
