Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1274360 - Laptop attempts boot w/ wrong LUKS password/fails
Summary: Laptop attempts boot w/ wrong LUKS password/fails
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-22 14:54 UTC by mulhern
Modified: 2020-12-15 07:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:38:02 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description mulhern 2015-10-22 14:54:40 UTC
Description of problem:

If I type the wrong password a few too many times laptop will actually start booting, making me think I've typed the correct password. But, it will turn out to have been the wrong password after all, the encrypted volumes will not be available, and the result is a drop to the dracut shell.

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

My laptop has RHEL7.1 CSB. Not easy to get a whole lot of version info from
dracut shell.

How reproducible:

It seems that maybe all I have to do is type the wrong password enough times (3), so always.

Steps to Reproduce:
1. Apparently, just enter an incorrect LUKS password thrice.
2.
3.

Actual results:

Attempt and failure to boot.

Expected results:

Same.

Additional info:

Better if it didn't attempt to boot, with wrong passphrase.

Comment 4 RHEL Program Management 2020-12-15 07:38:02 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


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