There is a growing number of userland tools that need to know what crypto algorithms (and key lenghts etc) are available for a kernel consumer. The common case of this is the admin utility that configures a given kernel subsystem that uses crypto. The following are the
known cases for things already here or comming soon: ipsecalgs(1m), cryptoadm(1m), kssladm(1m), lofiadm(1m), ZFS.
This information is available over the private device /dev/cryptoadm and is how cryptoadm(1m) gets this. We need to make an API
version of this that can be used by others. Basically an API version of cryptoadm list -m but with some more information.
xxxxx@xxxxx.com 2005-03-07 17:50:58 GMT