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

How to test luks setup with --vm-test #575

Open
haraldh opened this issue Mar 20, 2024 · 5 comments
Open

How to test luks setup with --vm-test #575

haraldh opened this issue Mar 20, 2024 · 5 comments

Comments

@haraldh
Copy link

haraldh commented Mar 20, 2024

Is there any trick how I can test a luks setup with --vm-test. Doing so always fails to unlock the luks device in the booted_machine stage of course, because the key files are missing.

@Mic92
Copy link
Member

Mic92 commented Mar 20, 2024

There is no trick as of today. Those VMs also run in a nix-build, which would require adding secrets. Maybe there could be a way to allow stub secrets for testing.

@haraldh
Copy link
Author

haraldh commented Mar 20, 2024

Thanks for the quick answer! Yeah, stub secrets would be great!

@Mic92
Copy link
Member

Mic92 commented Mar 20, 2024

@Lassulus could we recursively override all existing cryptsetup keys with fake keys? Same for zfs.

@Mic92
Copy link
Member

Mic92 commented Mar 20, 2024

Not sure how could provide these keys at boot time...

@haraldh
Copy link
Author

haraldh commented Mar 20, 2024

maybe https://systemd.io/CREDENTIALS/

VMs can be passed credentials via SMBIOS OEM strings (example qemu command line switch -smbios type=11,value=io.systemd.credential:foo=bar

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

No branches or pull requests

2 participants