Re: [arch-general] [arch-dev-public] [signoff] cryptsetup 1.4.0-1
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 crypted partition and after re-configuring it using the newer cryptsetup) Is this to be worried about? Geert -- geert.hendrickx.be :: geert@hendrickx.be :: PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
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 size: 2097152 sectors
(both on the existing crypted partition and after re-configuring it using the newer cryptsetup)
Is this to be worried about?
Geert
For what it's worth, this still seems to work here using LUKS. [bo@archawesome backups (master) Mon 10:39 ]$ sudo cryptsetup status encrypted-backup Password: /dev/mapper/encrypted-backup is active and is in use. type: LUKS1 cipher: aes-xts-plain keysize: 512 bits device: /dev/sdc offset: 4096 sectors size: 976769072 sectors mode: read/write [bo@archawesome backups (master) Mon 13:01 ]$ pacman -Qi cryptsetup Name : cryptsetup Version : 1.4.0-1 Regards, Bjørn Øivind Bjørnsen
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 offset: 0 sectors size: 2097152 sectors
(both on the existing crypted partition and after re-configuring it using the newer cryptsetup)
Is this to be worried about?
I can't reproduce this here: /dev/mapper/pv is active and is in use. type: LUKS1 cipher: aes-xts-plain keysize: 384 bits device: /dev/sda2 offset: 3016 sectors size: 625034984 sectors mode: read/write Your output seems wrong, but if everything works, I wouldn't worry. Can anyone else see this?
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 - keysize: 256 bits + keysize: 0 bits device: /dev/xvda1 offset: 0 sectors size: 2097152 sectors
(both on the existing crypted partition and after re-configuring it using the newer cryptsetup)
Is this to be worried about?
I can't reproduce this here:
/dev/mapper/pv is active and is in use. type: LUKS1 cipher: aes-xts-plain keysize: 384 bits device: /dev/sda2 offset: 3016 sectors size: 625034984 sectors mode: read/write
Your output seems wrong, but if everything works, I wouldn't worry. Can anyone else see this?
I can reproduce this on three different systems, two (similar) i686 VPS'es, and my x86_64 desktop PC, all with cryptsetup 1.4.0-1. Geert -- geert.hendrickx.be :: geert@hendrickx.be :: PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
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 :: geert@hendrickx.be :: PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
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=665#
Not sure if I wanna rebuild for that, this is a minor problem.
participants (3)
-
Bjørn Øivind Bjørnsen
-
Geert Hendrickx
-
Thomas Bächler