Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#52306 - Cryptsetup encrypts two partition when it should only encrypt one
Attached to Project:
Arch Linux
Opened by vespid (vespid) - Thursday, 29 December 2016, 17:33 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 06 January 2017, 16:43 GMT
Opened by vespid (vespid) - Thursday, 29 December 2016, 17:33 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 06 January 2017, 16:43 GMT
|
DetailsDescription:
I have encountered a bug when trying to create an encrypted boot partition for use on an EFI system. I create both necessary partitions and instruct cryptsetup to encrypt only one. Both of them end up encrypted with the same passphrase. Steps to reproduce: 1. Create a 512M EFI partition using gdisk 2. Create a 1G Linux filesystem partition using gdisk 3. Encrypt the 1G partition using cryptsetup eith a serpent-cbc-essiv:256 cipher and a tiger2 hash 4. Attempt to mount the efi partition. The filesystem type is listed as crypto_LUKS 5. Attempt to unlock the efi partition. The passphrase is the same as the one used for the partition that should be encrypted. |
This task depends upon
Comment by Doug Newgard (Scimmia) -
Saturday, 31 December 2016, 15:34 GMT
You never formatted sdb1. Was it previously encrypted?
cryptsetup_bug