PrivSec-dev/privsec.dev
1
0
Fork 0
mirror of https://github.com/PrivSec-dev/privsec.dev synced 2025-02-20 18:31:35 -05:00
Code

Grammar Fixes

Browse Source 
Signed-off-by: Tommy <contact@tommytran.io>
This commit is contained in:
Tommy 2023-03-11 14:52:08 -05:00 committed by GitHub
parent bad3161754
commit cbd8fa913d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/posts/linux/Using Native ZFS Encryption with Proxmox.md
View File

@ -68,10 +68,10 @@ zfs destroy -r rpool/data
# Create a new encryption key # Create a new encryption key
dd if=/dev/urandom bs=32 count=1 of=/.data.key dd if=/dev/urandom bs=32 count=1 of=/.data.key
# Setting the approprieate permission # Set the approprieate permission
chmod 400 /.data.key chmod 400 /.data.key
# Making the key immutable # Make the key immutable
chattr +i /.data.key chattr +i /.data.key
# Create a new dataset with encryption enabled # Create a new dataset with encryption enabled
@ -138,4 +138,4 @@ update-initramfs -u
You should now be able to ssh into your dropbear upon reboot. Use `zfsunlock` to unlock the `rpool/ROOT` dataset :) You should now be able to ssh into your dropbear upon reboot. Use `zfsunlock` to unlock the `rpool/ROOT` dataset :)
![Dropbear with Proxmox ZFS](/images/dropbear-proxmox-zfs.png) ![Dropbear with Proxmox ZFS](/images/dropbear-proxmox-zfs.png)