IMPORTANT: Cryptoloop has been marked deprecated in the latest 2.6 kernel.
This means that it will no longer be maintained actively. The successor to
Cryptoloop will be [http://www.saout.de/misc/dm-crypt/(...)] dm-crypt. Dm-crypt is
available in the main kernel since 2.6.4. Cryptoloop will still be available
in the main kernel for a long time, but dm-crypt will be the method of choice
for disk encryption in the future. Dm-crypt is based on the device mapper and
offers pretty much the same functionality as Cryptoloop. It is still very new
and there are no easy-to-use userspace tools available yet. Dm-crypt is
considered to be much cleaner code than Cryptoloop, but there are some
important differences. For example, creating an ecrypted filesystem within a
file will still require to go through a loop device, but this support is
still in development.
# cryptoloop est mort
Posté par 007 . En réponse au journal CryptoFS ?. Évalué à 3.
http://www.ibiblio.org/pub/Linux/docs/HOWTO/Cryptoloop-HOWTO(...)
IMPORTANT: Cryptoloop has been marked deprecated in the latest 2.6 kernel.
This means that it will no longer be maintained actively. The successor to
Cryptoloop will be [http://www.saout.de/misc/dm-crypt/(...)] dm-crypt. Dm-crypt is
available in the main kernel since 2.6.4. Cryptoloop will still be available
in the main kernel for a long time, but dm-crypt will be the method of choice
for disk encryption in the future. Dm-crypt is based on the device mapper and
offers pretty much the same functionality as Cryptoloop. It is still very new
and there are no easy-to-use userspace tools available yet. Dm-crypt is
considered to be much cleaner code than Cryptoloop, but there are some
important differences. For example, creating an ecrypted filesystem within a
file will still require to go through a loop device, but this support is
still in development.