Bug#726448: closed by Christian Perrier <bubulle@debian.org> (Bug#726448: fixed in partman-crypto 66)

[Thiemo Nagel <thiemo.nagel@gmail.com>]

Dear Christian,

thank you for uploading my patches!

> Changes:
>  partman-crypto (66) unstable; urgency=low
>  .
>    [ Thiemo Nagel ]
>    * Use the same security setting for wiping existing volumes
>      than previous settings, when the volume was already encrypted.
>      Closes: #726448

I'm sorry, but I believe that this does not describe the nature of the
changes very well. It is not about wiping existing volumes but about
wiping the device (with random data) on which a new crypto volume is
to be created as to obscure future write patterns to the new crypto
volume. (I don't want to exclude that it might affect the wiping of
existing volumes, but I believe that this is irrelevant.)

I'd rather suggest something along the lines of:

"Protect meta-information (including eg. the amount of free space)
with the same crypto algorithm and the same key size as are used for
the volume's content."

Cheers,
Thiemo