> Encryption/decryption is transparent to the user, so the only thing
> they will need to know is their key, and how to mount a device. We do not
> encrypt the entire volume under the same key as some solutions do (this can
> not only aid in a known-plaintext attack, but it gives the users less
> options). Instead, every file is encrypted seperately under the key of the
> users choice.
Do you encrypt before the data has hit the data journal or after? Does that
work for mmap etc?
> We are also adding support for reading keys off floppies,
> cdroms, and USB keychain drives. Currently, ext3sj supports the following
> algorithms: AES, 3DES, Twofish, Serpent, RC6, RC5, RC2, Blowfish, CAST-256,
> XTea, Safer+, SHA1, SHA256, SHA384, SHA512, MD5, with more to come.
This sounds like something you might want to abstract into a generic
architecture to be shared with the loop device code, or anything which might
need encryption in the kernel. Otherwise it is a PITA to maintain.
And I thought some of those algorithms were strictly signature / hash
algorithms, but you never stop learning ;-)
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
-- Principal Squirrel SuSE Labs - Research & Development, SuSE Linux AG "If anything can go wrong, it will." "Chance favors the prepared (mind)." -- Capt. Edward A. Murphy -- Louis Pasteur - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/