Hello everyone, my employer wants to have a lightweight, zero-copy user space interface to the Crypto-API and I *think* I'm on the right way to realising this.
What I've got so far is just a proof-of-concept, tested only with cbc(aes), merely as generic as I'd like it to be, but with zero-copy of the actual data buffers (which reside in user space) and asynchronous operation. You can check it out via git://nwl.cc/~n0-1/kcrypto.git or simply have a look at http://nwl.cc/cgi-bin/git/gitweb.cgi?p=kcrypto.git;a=summary. If you do so, you may in return flame me as much as you like to. :) I know that it's far from being ready for use as the sole crypto API user space interface, but I'm convinced as well that it will never be unless someone with Crypto-API skills points out at least the very basic design flaws I've already created. As this is not yet being used in production (of course), I'm totally open to changes. So taking this as start of a collaborative project would be perfect for me, too. Greetings (and sorry for yet another interface approach), Phil -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
