Skip to content
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

Use key-file specified in crypttab #1187

Open
debnath-d opened this issue Sep 18, 2023 · 0 comments
Open

Use key-file specified in crypttab #1187

debnath-d opened this issue Sep 18, 2023 · 0 comments

Comments

@debnath-d
Copy link

From crypttab's manpage:

Each line is in the form

    volume-name encrypted-device key-file options

...

 3. The third field specifies an absolute path to a file with the
    encryption key. Optionally, the path may be followed by ":"
    and an /etc/fstab style device specification (e.g. starting
    with "LABEL=" or similar); in which case the path is taken
    relative to the specified device's file system root. If the
    field is not present or is "none" or "-", a key file named
    after the volume to unlock (i.e. the first column of the
    line), suffixed with .key is automatically loaded from the
    /etc/cryptsetup-keys.d/ and /run/cryptsetup-keys.d/
    directories, if present. Otherwise, the password has to be
    manually entered during system boot. For swap encryption,
    /dev/urandom may be used as key file, resulting in a
    randomized key.   

Currently, udiskctl unlock does not use the key-file specified either in /etc/crypttab or automatically from /etc/cryptsetup-keys.d/ if not specified in /etc/crypttab.

It would be great if the key-file (either specified in /etc/crypttab or located in /etc/cryptsetup-keys.d/) could be used automatically by udiskctl to unlock the encrypted device without needing to use the --key-file option or without prompting the user for a passphrase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants