On Thu, Jul 31, 2003 at 02:39:45PM +1000, James Morris wrote: > > Moving to the slightly more ontopic stuff for lk@xxxx: Is access to > > the cryptoapi algorithms exposed to userspace yet? > No, there is no point (apart from testing) unless the kernel API is > providing access to crypto hardware. Even if we don't have the drivers yet, the sooner it's available and in use the better, then we can always drop in hardware support later. (Still, I'm not volunteering for either job so I won't complain, just wondering if it had been done) > > Thirdly, has the encryption setup changed again since 2.4.x with hvr's > > testing cryptoapi stuff? I have a filesystem encrypted with 256 bits > > serpent, yet it won't decrypt using 2.6.0-test2 and util-linux 2.12. > The kerneli serpent implementation is incorrect (it's reversed, a common > implementation problem with this algorithm). Owch. But I assume this didn't sneak in since the testing cryptoAPI patches? Or have the algorithms been redone? > > Lastly: Why the move from a /proc/crypto directory containing files > > for all the algorithms to one monolithic /proc/crypto file? Isn't the > > former a lot nicer from the userspace programmer's point of view? > Possibly, although it's probably too late to change now for 2.6. But why was it ever changed to on big file in the first place? -- Frank v Waveren Fingerprint: 21A7 C7F3 fvw@[var.cx|stack.nl|chello.nl] ICQ#10074100 1FF3 47FF 545C CB53 Public key: hkp://wwwkeys.pgp.net/fvw@xxxxxx 7BD9 09C0 3AC1 6DF2 - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
