Interesting, I wasn't aware of the upstream module. I'd say that's
preferable to the one I wrote.
I think you would need to wire that into the 'modules' directory under
libpam. I can look into doing that.
On 9/5/21 11:27 AM, Greg wrote:
>
>
> On September 5, 2021 4:54:26 PM GMT+03:00, Eric
On September 5, 2021 4:54:26 PM GMT+03:00, Eric McCorkle
wrote:
>All,
>
>This patch creates a new PAM module that will load a ZFS key upon a
>successful login: https://reviews.freebsd.org/D31844. It will use the
>user's auth token as the key argument to loading a ZFS encryption key on
>a
On 2021 M09 5, Sun 15:52:50 EEST David Wolfskill wrote:
> Sorry I hadn't noticed this yesterday (so I could have repported it
> then), but after updating the "head" slice of my laptopp from:
>
> FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #340
> main-n249128-a0c64a443e4c: Fri
In message <2838567.hhqauc6...@sigill.theweb.org.ua>, "Oleg V. Nauman"
writes:
> On 2021 M09 5, Sun 15:52:50 EEST David Wolfskill wrote:
> > Sorry I hadn't noticed this yesterday (so I could have repported it
> > then), but after updating the "head" slice of my laptopp from:
> >
> > FreeBSD
All,
This patch creates a new PAM module that will load a ZFS key upon a
successful login: https://reviews.freebsd.org/D31844. It will use the
user's auth token as the key argument to loading a ZFS encryption key on
a user-specific ZFS data set.
This is the other side of my changeset to have
Sorry I hadn't noticed this yesterday (so I could have repported it
then), but after updating the "head" slice of my laptopp from:
FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #340
main-n249128-a0c64a443e4c: Fri Sep 3 04:06:12 PDT 2021
On 05/09/2021 13:52, David Wolfskill wrote:
… from:
FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #340
main-n249128-a0c64a443e4c: Fri Sep 3 04:06:12 PDT
2021r...@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY
amd64 1400032 1400032
to:
FreeBSD
On Sun, Sep 05, 2021 at 02:22:58PM +0100, Graham Perrin wrote:
>
> > … I note that the subject update also included updates to
> > contrib/wpa/wpa_supplicant, as well as some files in sys/net80211,
> > but I have not started chasing that down. …
>
> Can you share relevant lines from your
