From: Guillaume Le Vaillant <glv@posteo.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Unencrypted boot with encrypted root
Date: Wed, 20 May 2020 10:49:09 +0200 [thread overview]
Message-ID: <87blmjout6.fsf@yamatai> (raw)
In-Reply-To: <87eerih8pq.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> Have you tried to unlock a ZFS-encrypted home with pam_mount?
>
> I found these related links:
>
> https://blogs.oracle.com/solaris/user-home-directory-encryption-with-zfs-v2
>
> https://old.reddit.com/r/linuxquestions/comments/g7t38d/mounting_an_encrypted_zfs_home_filesystem_at_user/
>
> ZFS is not listed here:
> http://pam-mount.sourceforge.net/pam_mount.conf.5.html
No, I've never tried. In fact, I only tried ZFS once a few years ago,
and as for my use case I didn't see an advantage over BTRFS, I kept
using BTRFS.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-05-20 8:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 8:59 Unencrypted boot with encrypted root Pierre Neidhardt
2020-04-03 15:32 ` pelzflorian (Florian Pelz)
2020-04-03 15:44 ` Ellen Papsch
2020-04-03 16:13 ` Pierre Neidhardt
2020-04-03 17:16 ` Ellen Papsch
2020-04-03 19:56 ` Guillaume Le Vaillant
2020-04-04 9:02 ` Pierre Neidhardt
2020-05-17 15:39 ` Pierre Neidhardt
2020-05-20 8:49 ` Guillaume Le Vaillant [this message]
2020-05-20 9:42 ` Pierre Neidhardt
2020-04-03 19:44 ` pelzflorian (Florian Pelz)
2020-04-04 8:12 ` Ellen Papsch
2020-04-04 10:18 ` pelzflorian (Florian Pelz)
2020-04-06 12:00 ` Ellen Papsch
2020-04-07 9:46 ` Ludovic Courtès
2020-04-07 11:34 ` Ellen Papsch
2020-04-07 20:19 ` Ludovic Courtès
2020-04-08 12:37 ` Ellen Papsch
2020-04-07 15:05 ` Alex Griffin
2020-04-07 16:47 ` Vagrant Cascadian
2020-04-08 12:25 ` Ellen Papsch
2020-04-08 15:07 ` Alex Griffin
2020-04-08 16:22 ` Vagrant Cascadian
2020-04-08 7:57 ` Pierre Neidhardt
2020-04-08 12:19 ` Alex Griffin
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blmjout6.fsf@yamatai \
--to=glv@posteo.net \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).