Work on adding the advanced luks article to the password article #1166
Conversation
updates to the LUKS commands.
content/password.md
Outdated
| @@ -114,7 +114,7 @@ The output may be different based on the drive setup and partition table. You ca | |||
| sudo cryptsetup luksDump /dev/sda3 | |||
| ``` | |||
|
|
|||
| Replacing '/dev/sda3' with the location of the root partition on your system. With the output of this command we can see the seven extra slots that we have for passwords to decrypt the drive. Slots 1-7 are the open ones and Slot 0 is the current one the system has set. | |||
| Replacing '/dev/sda3' with the location of the root partition on your system. With the output of this command we can see the seven extra slots that we have for passwords to decrypt the drive. On a normal install Slots 1-7 are the open, with Slot 0 as the initial pass-phrase. | |||
There was a problem hiding this comment.
This is a bit odd:
On a normal install Slots 1-7 are the open, with Slot 0 as the initial pass-phrase.
I feel like it would be like this:
On a normal install Slots 1-7 are not used and Slot 0 is used as the initial pass-phrase.
There was a problem hiding this comment.
There are several places where we assume that a pop install will be on certain devices/ partitions (nvme0n1p3 or sda3) which could cause issues. An image inline, highlighting the listed partition may help a user. More importantly, if we assume that our user is not technically inclined, parts of the article which haven't been touched cite commands using "sda3" when A) "nvme0n1p3" is probably more common now given how many major manufacturers have moved to default nvme drives, let alone our own nvme-centric offerings, and B) might cause users to hit a wall where they just type commands in character-for-character without understanding them. Admittedly, a support article will never replace someone actively engaging with the instructions... but it might still be worth considering changes to some of that verbiage as we're already looking at updating this article.
(I've yet to review the LUKS portion, but will be doing that next)
ahoneybun
force-pushed
the
update-passwords
branch
from
3daea9c
to
6580e31
Compare
This combines them fixing issue #1161