Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cryptsetup: Treat key file errors as a failed password attempt #11805

Merged
merged 1 commit into from Feb 26, 2019

Conversation

refi64
Copy link
Contributor

@refi64 refi64 commented Feb 23, 2019

6f177c7 caused key file errors to immediately fail, which would make it hard to correct an issue due to e.g. a crypttab typo or a damaged key file.

Closes #11723.

@poettering poettering added reviewed/needs-rework 🔨 PR has been reviewed and needs another round of reworks cryptsetup labels Feb 25, 2019
6f177c7 caused key file errors to immediately fail, which would make it hard to correct an issue due to e.g. a crypttab typo or a damaged key file.

Closes systemd#11723.
@refi64
Copy link
Contributor Author

refi64 commented Feb 25, 2019

@poettering Done.

@poettering
Copy link
Member

lgtm! thanks!

@poettering poettering added good-to-merge/waiting-for-ci 👍 PR is good to merge, but CI hasn't passed at time of review. Please merge if you see CI has passed and removed reviewed/needs-rework 🔨 PR has been reviewed and needs another round of reworks labels Feb 25, 2019
@yuwata yuwata merged commit c20db38 into systemd:master Feb 26, 2019
@blackjackshellac
Copy link

This was driving me nuts in Fedora 30. As a workaround, you can change the /etc filesystem luks password to "none" in /etc/crypttab (assuming luks-key files are under /etc). Something like,

luks-abcde UUID=abcde none luks

@keszybz keszybz removed the good-to-merge/waiting-for-ci 👍 PR is good to merge, but CI hasn't passed at time of review. Please merge if you see CI has passed label Nov 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

v241 has issues with /home encrypted
6 participants