From: Eric Abreu <abreuer1521@gmail.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Where is ZFS encryption key in Proxmox 7.1
Date: Tue, 30 Nov 2021 12:17:05 -0500 [thread overview]
Message-ID: <CACEJK8N20D2tw+-fkL6rGSVk35y4oAqfj_BrSPcrLhE_7UKdFA@mail.gmail.com> (raw)
In-Reply-To: <5a879cf8-ed5a-783a-29a7-6d175b2605f7@proxmox.com>
Hi Thomas,
Thanks for the quick response. I'm going to repeat the steps to create the
ZFS pool from the web interface and paste them here. I'm pretty sure I did
everything from the dashboard and the encryption was enabled by default.
I'll keep you posted. Thanks again for your help.
On Tue, Nov 30, 2021 at 3:37 AM Thomas Lamprecht <t.lamprecht@proxmox.com>
wrote:
> Hi,
>
> On 30.11.21 04:36, Eric Abreu wrote:
> > I have created a ZFS pool from Proxmox 7.1 web interface with 2 SSDs in
> > RAID 1. I noticed that everything works fine after I created the pool,
> and
> > ZFS at REST encryption was also enabled. After rebooting the server it
> did
> > not ask for a passphrase so my guess is that Proxmox is getting the key
> > from somewhere in the file system. Anyone could help me find out where?
>
> Well, how did you enable ZFS at rest encryption? As that is something that
> won't
> be done automatically, and the local-storage web-interface/api currently
> does not
> allow to configure that either.
>
> cheers,
> Thomas
>
>
next prev parent reply other threads:[~2021-11-30 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 3:36 Eric Abreu
2021-11-30 8:37 ` Thomas Lamprecht
2021-11-30 17:17 ` Eric Abreu [this message]
2021-12-01 0:31 ` Eric Abreu
2021-12-01 2:58 ` Adam Thompson
2021-12-01 3:39 ` Eric Abreu
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=CACEJK8N20D2tw+-fkL6rGSVk35y4oAqfj_BrSPcrLhE_7UKdFA@mail.gmail.com \
--to=abreuer1521@gmail.com \
--cc=pve-user@lists.proxmox.com \
--cc=t.lamprecht@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.