Bug#762297: [pkg-cryptsetup-devel] Bug#762297: cryptsetup: fails to create tmp filesystem due to false positive from blkid

2014-10-07 Thread Zygo Blaxell
On Tue, Oct 07, 2014 at 07:24:37PM +0200, Jonas Meurer wrote: > Am 02.10.2014 um 16:43 schrieb Zygo Blaxell: > > 1. Create an encrypted tmpfs header. A simple static header (or a > > stripped down LUKS header) can be unambiguously recognized by blkid or > > even cryptdisks itself[...] > > Mh, in

Bug#762297: [pkg-cryptsetup-devel] Bug#762297: cryptsetup: fails to create tmp filesystem due to false positive from blkid

2014-10-07 Thread Jonas Meurer
Hey Zygo, thanks for your feedback. See my comments inline below. Am 02.10.2014 um 16:43 schrieb Zygo Blaxell: >> Unfortunately, no better solution than un_blkid is known to me to >> prevent serious data loss in case of device rearrangement or >> missconfiguration with plain dm-crypt devices and

Bug#762297: [pkg-cryptsetup-devel] Bug#762297: cryptsetup: fails to create tmp filesystem due to false positive from blkid

2014-10-02 Thread Zygo Blaxell
On Thu, Oct 02, 2014 at 01:16:16PM +0200, Jonas Meurer wrote: > Am 20.09.2014 um 22:07 schrieb Zygo Blaxell: > > un_blkid is not a suitable precheck for plain dm-crypt 'tmp' or 'swap' > > devices due to the potential for false positives from previous runs > > on the same device. > > That's really

Bug#762297: [pkg-cryptsetup-devel] Bug#762297: cryptsetup: fails to create tmp filesystem due to false positive from blkid

2014-10-02 Thread Jonas Meurer
severity 762297 minor tag 762297 wontfix thanks Hi Zygo, thanks for your bugreport. Am 20.09.2014 um 22:07 schrieb Zygo Blaxell: > un_blkid is not a suitable precheck for plain dm-crypt 'tmp' or 'swap' > devices due to the potential for false positives from previous runs > on the same device. T

Bug#762297: cryptsetup: fails to create tmp filesystem due to false positive from blkid

2014-09-20 Thread Zygo Blaxell
Package: cryptsetup Version: 2:1.6.6-1 Severity: normal un_blkid is not a suitable precheck for plain dm-crypt 'tmp' or 'swap' devices due to the potential for false positives from previous runs on the same device. This bug potentially leads to information disclosure in some configurations. I ha