> See Documentation/DocBook/crypto-API.tmpl in the cryptodev-2.6 tree. > There you will find tons of documentation (which will be merged during > 3.19-rc1) Yes, I've been reading that. It certainly helps a great deal, but still leaves me with some significant questions. I started researching the crypto layer when I proposed using Dan Bernstein's SipHash elsewhere in the kernel and someone asked for a crypto API wrapper for it. That seemed a simple enough request to me, but it's been a deeper rabbit hole than I expected. I started reading the code to another keyed hash, michael_mic, as a model, but I'm stil trying to understand the intended difference between "struct crypto_shash" and "struct shash_desc", and in particular why both have a copy of the key. The SHASH API documentation at https://git.kernel.org/cgit/linux/kernel/git/herbert/cryptodev-2.6.git/tree/include/crypto/hash.h isn't particularly enlightening. If the crypto_shash were entirely read-only and the shash_desc were the entire volatile state, that would make sense, but as it is I'm confused about the design intent. (On a related point, the general lack of const declarations throughout the crypto layer has been a source of frustration.) The other big issue I'm struggling with is how to get the tcrypt.ko module to print "ansi_cprng has passed its tests." All it has produced for me so far is a few kilobytes of dmesg spam about ciphers which aren't even configured in my kernel. After a few hours of trying to figure out what the alg and type parameters do, I gave up and cut and pasted the tests into prng_mod_init(). -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
