Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
managing_hard_drive_encryption_on_linux [2023/09/22 09:53] ac1mdemanaging_hard_drive_encryption_on_linux [2023/10/23 14:42] (current) ac1mde
Line 12: Line 12:
 </code> </code>
  
-The encrypted partition is nvme0n1p3_crypt (//yours will likely be different!//). The device node path associated with this is /dev/nvme0n1p3. This is needed in the next command which allows you to add your own passphrase to the 'crypted partition. Using this example, the command is:+Copy the UUID it shows you and use it in this command:
  
 <code> <code>
-sudo cryptsetup luksAddKey /dev/nvme0n1p3+sudo cryptsetup luksAddKey UUID=fd11d274-d095-4a29-a5aa-9e06514a18fe
 </code> </code>
  
-//Make sure you use your own device path instead of the one in the example.//+//Make sure you use your own UUID instead of the one in the example.//
 It will ask for the currently set passphrase, and then you can enter your own that you want to use. To check you can use it, reboot the computer and enter your new passphrase when it asks to unlock the drive. It will ask for the currently set passphrase, and then you can enter your own that you want to use. To check you can use it, reboot the computer and enter your new passphrase when it asks to unlock the drive.
  
 Assuming it works, the final stage is to dispose of any hard copies you may have of the original hard-to-remember passphrase! Assuming it works, the final stage is to dispose of any hard copies you may have of the original hard-to-remember passphrase!
  
managing_hard_drive_encryption_on_linux.1695372837.txt.gz · Last modified: 2023/09/22 09:53 by ac1mde
Public Domain
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0