Bug 461264 - mkinitrd does not follow /etc/crypttab
mkinitrd does not follow /etc/crypttab
Product: Fedora
Classification: Fedora
Component: mkinitrd (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Peter Jones
Fedora Extras Quality Assurance
: Triaged
Depends On:
Blocks: F10Target
  Show dependency treegraph
Reported: 2008-09-05 08:36 EDT by Gabriel VLASIU
Modified: 2009-12-18 01:21 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 01:21:57 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gabriel VLASIU 2008-09-05 08:36:42 EDT
Description of problem:
mkinitrd does not care about custom parameters specified in /etc/crypttab

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

How reproducible:

Steps to Reproduce:
1. swapoff -a

2. cryptsetup remove luks-sda5 (sda5 is swap partition)

3. add to /etc/cryptab:
   luks-sda5 /dev/sda5 /dev/urandom  swap,size=256,cipher=aes-cbc-essiv:sha256

4. mkinitrd -f /boot/initrd-`uname -r`.img `uname -r`

5. reboot

6 . cryptsetup status luks-sda5
/dev/mapper/luks-sda5 is active:
cipher:  aes-cbc-essiv:sha256
keysize: 256 bits
device:  /dev/sda5
offset:  0
sectors size:    4192902
sectors mode:    read/write

7. swapon -s
Filename                                Type            Size    Used    Priority
/dev/mapper/luks-sda5                   partition       2096440 0       -1

8. mkinitrd -f /boot/initrd-`uname -r`.img `uname -r`

9. reboot

Actual results:

# cryptsetup status luks-sda5
/dev/mapper/luks-sda5 is active:
  cipher:  aes-cbc-essiv:sha256
  keysize: 128 bits
  device:  /dev/sda5
  offset:  1032 sectors
  size:    4191870 sectors
  mode:    read/write

Expected results:

# cryptsetup status luks-sda5
/dev/mapper/luks-sda5 is active:
  cipher:  aes-cbc-essiv:sha256
  keysize: 256 bits
  device:  /dev/sda5
  offset:  0 sectors
  size:    4192902 sectors
  mode:    read/write

Additional info:
Comment 1 Bug Zapper 2008-11-25 21:58:13 EST
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
Comment 2 Bug Zapper 2009-11-18 03:21:39 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 3 Bug Zapper 2009-12-18 01:21:57 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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