Am 31.10.2011 13:18, schrieb Geert Hendrickx:
> Apparantly this affects only plain volumes (not luks),
> and will be fixed in 1.4.1:
>
> http://code.google.com/p/cryptsetup/issues/detail?id=115
>
> You may want to include the patch already?
> http://code.google.com/p/cryptsetup/source/detail?r=66
Apparantly this affects only plain volumes (not luks),
and will be fixed in 1.4.1:
http://code.google.com/p/cryptsetup/issues/detail?id=115
You may want to include the patch already?
http://code.google.com/p/cryptsetup/source/detail?r=665#
Geert
--
geert.hendrickx.be :: ge...@hendric
On Mon, Oct 31, 2011 at 13:11:31 +0100, Thomas Bächler wrote:
> Am 31.10.2011 12:54, schrieb Geert Hendrickx:
> > Appears to work fine, however I noticed a change in cryptsetup status
> > output:
> >
> > /dev/mapper/cryptswap is active.
> >type:PLAIN
> >cipher: aes-cbc-essiv:sha256
Am 31.10.2011 12:54, schrieb Geert Hendrickx:
> Appears to work fine, however I noticed a change in cryptsetup status output:
>
> /dev/mapper/cryptswap is active.
>type:PLAIN
>cipher: aes-cbc-essiv:sha256
> - keysize: 256 bits
> + keysize: 0 bits
>device: /dev/xvda1
>offse
On 31/10/11 12:54, Geert Hendrickx wrote:
Appears to work fine, however I noticed a change in cryptsetup status output:
/dev/mapper/cryptswap is active.
type:PLAIN
cipher: aes-cbc-essiv:sha256
- keysize: 256 bits
+ keysize: 0 bits
device: /dev/xvda1
offset: 0 sectors
Appears to work fine, however I noticed a change in cryptsetup status output:
/dev/mapper/cryptswap is active.
type:PLAIN
cipher: aes-cbc-essiv:sha256
- keysize: 256 bits
+ keysize: 0 bits
device: /dev/xvda1
offset: 0 sectors
size:2097152 sectors
(both on the existing
6 matches
Mail list logo