[Bug 762636] Re: Ubuntu installer kills LUKS partitions without warning

[Evan Peck]

*** This bug is a duplicate of bug 420080 ***
    https://bugs.launchpad.net/bugs/420080

** This bug has been marked a duplicate of bug 420080
   Configure encrypted volumes destroys existing data

** Changed in: ubiquity (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/762636

Title:
  Ubuntu installer kills LUKS partitions without warning

Status in “ubiquity” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: ubiquity

  From https://lists.ubuntu.com/archives/ubuntu-
  bugsquad/2011-April/003176.html

  The dm-crypt mailing list (archive here:
  http://dir.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt)
  has had several reports that the Ubuntu installer creates 
  new LUKS partitions (encrypted partitions) on top of exisiting
  ones without giving adequate warning and at the same time
  giving the impression that the existing LUKS partition would be
  activated. The rather clear warning and verification question 
  asked by the cryptsetup tool seems to get disabled with the
  "--batch-mode" option.

  This causes irreversible loss of all data! Nothing 
  (in the cryptographically strong sense) can be done
  to get the data back!

  Checking for an existing LUKS partition is easy,    
  it has the magic string 'L','U','K','S, 0xBA, 0xBe  
  at the beginning. It seems this is not checked for,
  or no additional warning or only inadequate additional
  warning is given if a pre-exisiting LUKS partition 
  is about to be permanently and irretrivably erased.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/762636/+subscriptions