Bug 3513 - Mageia 2 Alpha 1 can't installed with encrypted filesystems: cryptsetup missing
Summary: Mageia 2 Alpha 1 can't installed with encrypted filesystems: cryptsetup missing
Status: RESOLVED DUPLICATE of bug 3749
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-28 00:47 CET by Jim Darby
Modified: 2011-12-20 18:21 CET (History)
2 users (show)

See Also:
Source RPM: installer
CVE:
Status comment:


Attachments

Description Jim Darby 2011-11-28 00:47:28 CET
Description of problem:Mageia 2 alpha 1 can't install with encrypted partitions

It would appear that Mageia 2 alpha 1 can't install on encrypted partitions.

The reason for this is that the cryptsetup utility is missing (it even pops up a window to say this).

Yes, this is a minor problem at this time but it should be fixed so that it's not forgotten later on.


Version-Release number of selected component (if applicable):

Mageia 2 alpha 1


How reproducible:

Every time.


Steps to Reproduce:
1. Run installer
2. Create an encrypted partition to install on
3. It fails and tells you that it was because cryptsetup was installed.


Additional notes:

The rules for when you should be permitted to encrypted filesystems are easy to get wrong (c.f. Mandriva 2011).

Essentially they are:
 * Everything can be encrypted
 * Except /
    * UNLESS /boot exists, which can never be encrypted.

The above was added to make sure we don't fall into that trap once cryptsetup is available in the installer.
Jim Darby 2011-11-28 00:48:00 CET

CC: (none) => uberscubajim

Thierry Vignaud 2011-11-28 10:02:43 CET

CC: (none) => pterjan

Comment 1 Jim Darby 2011-12-20 18:21:49 CET
Let's avoid too many bugs about essentially the same thing. As this one is inactive it's a good candidate to mark as a duplicate of an open one that's being work on.

*** This bug has been marked as a duplicate of bug 3749 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE


Note You need to log in before you can comment on or make changes to this bug.