CLEVIS-LUKS-EDIT(1)

✨ CLEVIS-LUKS-EDIT ✨

okay bestie, gather round, because we're talking about clevis-luks-edit — it's a clevis command, it lives in section 1 of your manual pages, and it's literally the glow-up button for your LUKS bindings 💅

🎀 NAME 🎀

clevis-luks-edit — edit a binding from a clevis-bound slot in a LUKS device. that's it, that's the whole job, and she does it beautifully ✨

---

🦋 SYNOPSIS 🦋

clevis luks edit [-f] -d DEV -s SLT [-c CONFIG]

---

🌸 OVERVIEW 🌸

so the clevis luks edit command edits clevis bindings from a LUKS device. iconic behaviour, no cap. for example:

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

like… look at her go 🫶

---

💖 OPTIONS 💖

• -d DEV — the LUKS device whose clevis-bound pins you wanna edit. this is the "which one" of it all.
• -s SLT — the slot to use when editing the clevis binding. pick your slot, queen 👑
• -f — go ahead and do the edit anyway, even if the config didn't change. sometimes you just need to re-slay for no reason and that's valid.
• -c CONFIG — the updated config you wanna use. this is your "here's the new version, bestie" flag.

---

🔥 EXAMPLES 🔥

okay so let's actually do this. first, we peek at what's bound:

clevis luks list -d /dev/sda1
1: tang '{"url":"addr"}'

see that? like the example above shows, /dev/sda1 has one slot bound, and in this case it's bound to a tang pin. adorable. love that for her 🌈

now we can edit this binding by running:

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

this is gonna open a text editor — the one set in the $EDITOR environment variable, or vi as a fallback (yes, vi, the og) — with the current configuration of this binding all ready for you to edit. in this case, you should be looking at:

{
    "url": "addr"
}

once you're in the editor, you can edit the pin configuration. for tang, you could edit the url, for instance. after you finish the change, save the file and exit. the updated configuration gets validated for JSON, and if there are no errors, you'll be shown the updated configuration and prompted whether to proceed. vibe check time ✨

if you proceed, the binding gets updated. and ngl, you may be required to provide a valid LUKS passphrase for the device. so have that ready, bestie 🔑

second example time! we're updating the same device and the same slot, but this time we're handing over the updated configuration too:

clevis luks edit -d /dev/sda1 -s 1 -c '{"url":"new-addr-here"}'

in this case, the binding update happens in non-interactive mode — no editor, no prompts, just straight to business 😌. note that it may also be required to provide a LUKS passphrase for the device here. same energy, same passphrase requirement, fr fr.

---

👑 SEE ALSO 👑

clevis-luks-list(1)

---

⚠️ heads up bestie: providing a LUKS passphrase may be required in both the interactive and the non-interactive flow. don't get caught out there 🙈

---

and that's the whole page, periodt 💜 this was CLEVIS-LUKS-EDIT(1), dated 10/16/2026 — she ate and left no crumbs, bye bestie 🎀✨