You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/posts/linux/Using Native ZFS Encryption with Proxmox.md
+12-7Lines changed: 12 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ Load in the `zfs` kernel module:
25
25
modprobe zfs
26
26
```
27
27
28
-
Next, follow [this gist](https://gist.github.com/yvesh/ae77a68414484c8c79da03c4a4f6fd55) to encrypt the dataset. You do not need to use any sort of live USB or rescue mode, as the initramfs has all what we need. In case it gets moved or deleted, I will copy and paste it here:
28
+
Next, follow [this gist](https://gist.github.com/yvesh/ae77a68414484c8c79da03c4a4f6fd55) to encrypt the dataset. You do not need to use any sort of live USB or rescue mode, as the initramfs has all what we need. In case it gets moved or deleted, I will copy and paste it here (we will make a few changes to better suite our purposes as well):
Next, we need to encrypt the `rpool/data` dataset. This is where Proxmox stores virtual machine disks.
69
72
70
-
Note that the encryption key will be stored inside of the `rpool/ROOT` dataset. Since `rpool/ROOT` is already encrypted, we can safely store it there. The key also has to be exactly 32 bytes.
71
-
72
73
73
74
```bash
74
75
# Destroy the original dataset
75
76
zfs destroy -r rpool/data
77
+
```
76
78
77
-
# Create a new encryption key
78
-
dd if=/dev/random bs=32 count=1 of=/.data.key
79
+
Create a diceware passphrase, and save it to `/.data.key`. Then, continue with:
0 commit comments