-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Passing parameters to cryptsetup when unlocking volume #316
Comments
Hello. I don't think there is such an option. In the end, the only available options for "clevis luks unlock" are: OPTIONS When inspecting the code of the unlock command, no additional options exist: $ grep cryptsetup /usr/bin/clevis-luks-unlock | grep open Feel free to open a new enhancement issue for this option, and, if possible, submit a patch. Regarding the options, I consider cryptsetup has too many options for clevis to add a particular one for this, so, from my perspective, I guess it is better to add a generic option to clevis-luks-unlock to attach to "cryptsetup open", although it is more error prone. @sergio-correia , what's your view on this? |
Pull Request submitted. This is just a quick, minimally-tested version, so feel free to give feedback there, if I've made any egregious errors, etc. |
Because I've got the pull request in now, I'm inclined to close this, and let all discussion happen over there. That way there's only one discussion thread to worry about, instead of two. |
Is there already a mechanism when unlocking a clevis/luks volume, to pass arbitrary parameters to the underlying
cryptsetup
? My integration work with pacemaker, may require being able to pass along a--disable-locks
to the finalcryptsetup open
. If there's a way to do that already, it's not obvious to me.To be clear, I'm fine doing the work of writing and testing patches. I just didn't know if there was already a way to do it, that I was missing.
Assuming that I need to patch
clevis-luks-unlock
, is it preferable to have explicit parameters for the ones we might want to pass along (eg--disable-locks
), or would a more generic one that passes everything (eg. based on$@
inbash
), be preferable?The text was updated successfully, but these errors were encountered: