Hi! We should clarify the issues: Must cipher implementations 1) expect that *in and *out may be the same buffer? 2) use no additional memory for operation after set_key() is called? Point (1) is not that terribly importatnt. It's just that such things should be defined somewhere. ad (2): I'm particularly thinking of encrypting swap here. There was a thread[1] about this about a year ago or so on lkml where it was said that it was necessary that encrypt() and decrypt() don't use additional memory for their run. However, whether this includes local variables placed on the stack I don't know. Maybe there is a limitation on the overall size of local variables so that it is not neccessay to claim a new page for the stack. Marc [1] message-id of the stating post was: <1E7F3E867C2DD3119D7F00A0C9D858639AC087@xxxxxxxxxxxxxxxxxx> -- Marc Mutz <Marc@xxxxxxxx> http://EncryptionHOWTO.sourceforge.net/ University of Bielefeld, Dep. of Mathematics / Dep. of Physics PGP-keyID's: 0xd46ce9ab (RSA), 0x7ae55b9e (DSS/DH) Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
