With ZFS 2.0.0 upstream ships a pam module, which uses an users login password to optionally decrypt their home dataset.
Debian upstream ships the config in a separate package, which seems cleaner than adding it to zfsutil-linux. This patchset adapts the commit to our repo. While at it I noticed that our debian/copyright file got a bit out-of-sync with debian's and pulled their version in (additionally adding Proxmox for the files in debian/*) Thanks to Fabian for catching this and pointing me in the right direction! Stoiko Ivanov (2): buildsys: make libpam-zfs a separate package update debian/copyright debian/control | 14 + debian/copyright | 840 +++++++++++----------------------- debian/libpam-zfs.install | 2 + debian/libpam-zfs.postinst | 6 + debian/libpam-zfs.prerm | 8 + debian/zfsutils-linux.install | 2 - 6 files changed, 301 insertions(+), 571 deletions(-) create mode 100644 debian/libpam-zfs.install create mode 100644 debian/libpam-zfs.postinst create mode 100644 debian/libpam-zfs.prerm -- 2.20.1 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
