dm-crypt using kthread
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 6 lines · Christophe Saout
Am Mo, den 16.02.2004 schrieb Grzegorz Kulewski um 03:07:
Quoted 4 lines
Quoted 4 lines
Is there more documentation that this? I'd imagine a lot of crypto-loop users wouldn't have a clue how to get started on dm-crypt, especially if they have not used device mapper before.
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
And how do they migrate existing encrypted filesytems?
And is the format considered "stable"?
(= if I will create fs on it, will I have problems with future kernels?)Yes. The cryptoloop compatible format will stay this way. The format (basically the cipher used and the iv generation mode) can be specified.
"Can be specified" = not stable, and likely means you cannot use old file systems.
-Andi