You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, Fedora installs root partition and swap partition. Both are encrypted and have the same passphrase in slot 0.
ykfde.conf asks me to choose one. It's not at all obvious if it's possible to configure multiple devices.
After configuring one (I started with swap device only, now switched to root, but behavior seems consistent, regardless), boot process asks for ykfde passphrase (2nd factor) and proceeds.. until system asks me for a password for the other partition.
At this point, I have the default Fedora LUKS key in slot 0 of both, slot 1 used/reserved for ykfde, and had now set slot 2 to different passphrases for the partitions: "asdf" for root and "qwer" for swap.
May not quite be a solution, but, why not switch to using a dynamic key for swap, rather than persistent? As swap itself is not persistent, this shouldn't impact you, and it does resolve your issue.
By default, Fedora installs root partition and swap partition. Both are encrypted and have the same passphrase in slot 0.
ykfde.conf asks me to choose one. It's not at all obvious if it's possible to configure multiple devices.
After configuring one (I started with swap device only, now switched to root, but behavior seems consistent, regardless), boot process asks for ykfde passphrase (2nd factor) and proceeds.. until system asks me for a password for the other partition.
At this point, I have the default Fedora LUKS key in slot 0 of both, slot 1 used/reserved for ykfde, and had now set slot 2 to different passphrases for the partitions: "asdf" for root and "qwer" for swap.
Current sequence of boot events:
...
...so ykfde failed to unlock? ...oops :(
Note: using https://copr.fedorainfracloud.org/coprs/bpereto/ykfde/packages/ which seems to be a repackage of this repo. Can compile from source if necessary.
The text was updated successfully, but these errors were encountered: