public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Tom Weber <pve@junkyard.4t2.com>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] How to secure the PBS Encryption Key
Date: Mon, 1 Nov 2021 14:58:53 +0100	[thread overview]
Message-ID: <31206b58-3a29-ef80-3534-13c556918832@4t2.com> (raw)

Hello,

in
https://forum.proxmox.com/threads/cant-set-an-symlink-in-etc-pve-for-zfs-encryption.96934/
fireon describes his problem securing the PBS encryption key.

I think his solution is only a workaround.

Suppose I encrypt local VM/Data storage on a node (without the / beeing 
unencrypted for ease of booting/remote management), I end up with a PBS 
Encryption Key lying around in clear that anyone who can get hands on the 
machine can get.

Now all it needs is access to a remote PBS with the synced encrypted Backups 
to get all the protected data that was in the VMs/CTs lying on encrypted 
storage of the orignal node.

This is probably not a Problem of PVE or PBS on their own. But in 
combination I think it's a weakness. "Stealing" hardware should not give you 
such cleartext keys.

Any idea how to circumvent this? My first idea was the same direction as 
fireon's by symlinking the key from some secure space - but this obviously 
doesn't work.

Some way to manually unlock the key after booting the node or maybe an area 
(folder) in /etc/pve/ that'd need unlocking for storing such information - 
though that's probably quite some development effort?

Best,
   Tom





                 reply	other threads:[~2021-11-01 14:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=31206b58-3a29-ef80-3534-13c556918832@4t2.com \
    --to=pve@junkyard.4t2.com \
    --cc=pve-user@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal