-
Notifications
You must be signed in to change notification settings - Fork 16
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
Native encryption #66
Comments
omv-luks-start is not part of the official plugin. Is a fork I did and I haven’t push any changes or committed back to the original plugin. Something similar can be achieved if you want that on zfs but just set it manually. The creation of that fork of the luks plugin is based on this. |
I managed to achieve desired behavior using a simple systemd service and
#!/bin/bash
function wait_unlocked() {
while zfs list -H -o keystatus | grep -q 'unavailable'; do
sleep 3
done
}
function unlock(){
while zfs list -H -o keystatus | grep -q 'unavailable'; do
pass=$(systemd-ask-password "Enter ZFS passphrase:" --timeout=0)
datasets=`zfs list -H -o name,keystatus | grep 'unavailable' | awk '{print $1}'`
for ds in $datasets; do
echo -e "$pass" | zfs load-key $ds
done
done
}
if [ "$1" = "-s" ]; then
#run as systemd service
unlock &
wait_unlocked
else
unlock
echo 'Unlocked successfully!'
fi
Once the service is enabled ( |
This would be a really useful feature to have, without it I'm not sure I can use OMV because I like having my data encrypted by default and having to SSH into my headless server anytime it reboots is a pretty bad UX. |
Any option one could run something like that from out of the Web-UI? |
Would it be possible to add a decryption support similar to how omv-luks-start works? So that the system does not try to boot, until encrypted zfs datasets are decrypted (e.g. via ssh)?
The text was updated successfully, but these errors were encountered: