On Tue, 2002-03-05 at 16:43, Jari Ruusu wrote: > Because cryptoapi works with very limited set of kernels, and with none of > the ultra stable kernels. Loop-AES works with all maintained stable kernels, > including distro vendor kernels. Meaning that if you use cryptoapi, HVR > chooses your kernel for you. If you use loop-AES, crypto adapts to _your_ > choice of kernel. That is a big difference. ...and with loop-aes, you choose the set of ciphers your users use... ;-) btw, you should have mentioned also that loop-aes is only about the loop block device... while cryptoapi is a _generic_ api, of which the cryptoloop is only one of the possible kernel space applications... > Another disadvantage that cryptoapi loop has, is the cryptoapi bloat that > makes it slower than loop-AES. Loop-AES does not use cryptoapi, and that is > a feature. btw, I wondering, whether we have any objective measurements of the overhead involved wrt using the additional abstraction layer w/ cryptoapi... regards, -- Herbert Valerio Riedel / Phone: (EUROPE) +43-1-58801-18840 Email: hvr@hvrlab.org / Finger hvr@gnu.org for GnuPG Public Key GnuPG Key Fingerprint: 7BB9 2D6C D485 CE64 4748 5F65 4981 E064 883F 4142
Attachment:
signature.asc
Description: This is a digitally signed message part
