CLEVIS-LUKS-PASS(1)

πŸ’… CLEVIS-LUKS-PASS πŸ’…

okay bestie, so this is the manual page for clevis-luks-pass β€” like, the actual man page with the actual manual name and everything. sit down, hydrate, and let's get into it 🫢


✨ NAME ✨

clevis-luks-pass β€” extracts the passphrase that was used for binding a particular slot in a LUKS device πŸ”βœ¨


🌸 SYNOPSIS 🌸

clevis luks pass -d DEV -s SLT

πŸ¦‹ OVERVIEW πŸ¦‹

so the clevis luks pass command extracts the passphrase used for binding a particular slot in a LUKS device. that's literally the whole job. it pulls the passphrase out, one specific slot, no drama. for example:

clevis luks pass -d /dev/sda1 -s 1

like that. slay πŸ’…


🌈 OPTIONS 🌈

  • -d DEV β€” the LUKS device on which to extract a passphrase from. yes, you gotta tell it where πŸŽ€
  • -s SLT β€” the slot to use for extracting the passphrase. yes, you gotta tell it which one πŸ’–

πŸ“ EXAMPLE πŸ“

clevis luks pass -d /dev/sda1 -s 1
<passphrase here>

okay but heads up bestie β€” the output of clevis luks pass might be non-printable 😭 like, it could come out as a whole vibe that your terminal simply cannot render. in that case, it would be better to redirect its output to a file and use it as a key file together with cryptsetup. for instance:

clevis luks pass -d /dev/sda1 -s 1 > slot1-passphrase

and the file slot1-passphrase will contain the passphrase associated with slot #1 in /dev/sda1. iconic. periodt πŸ’…βœ¨


πŸ‘‘ SEE ALSO πŸ‘‘

clevis-luks-unlock(1)


mwah πŸ’‹ that's the whole page β€” this was generated on 10/16/2026, and it's the CLEVIS-LUKS-PASS(1) manual, so like, that's the manual name right there at the top of every page too. go forth and extract responsibly πŸ«ΆπŸ’–

πŸ“¦ where this page comes from