From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: "Dan McGregor" <danismostlikely@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
Daniel McGregor <daniel.mcgregor@vecima.com>
Subject: Re: [OE-core] [PATCH v7 3/3] nfs-utils: Configure nfsv4 ID mapping & Kerberos
Date: Mon, 08 Apr 2024 14:51:12 +0200 [thread overview]
Message-ID: <lybk6krpa7.fsf@ensc-pc.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <20240402002058.3910908-3-danismostlikely@gmail.com> (Dan McGregor's message of "Mon, 1 Apr 2024 18:20:56 -0600")
"Dan McGregor" <danismostlikely@gmail.com> writes:
> Add support for the nfsv4 user ID mapping daemon, configured with
> a sensible default, and add a packageconfig for Kerberos support.
>
> This is reasonably tested in production in our environment, but only
> systemd support. There'll be some more work to do to get GSSAPI and
> NFS idmapd support integreated into that.
Just for interest: how do you solve GSSAPI? I made it work for me, put
it requires ugly changes (e.g. see [1])
There is an early dependency loop in libtirpc -> python -> kerberos ->
openssl -> python. I solved it by
- creating a throw-away krb5-initial package [2]; installs libraries in
/opt/krb5 and is used only at a few places.
- splitting libtirpc; this required to touch only a few other packages
some weeks/months ago. But now, [file-rdeps] error is triggered and
every
Both is ugly....
Enrico
Footnotes:
[1] https://gitlab.com/ensc-groups/bpi-router/de.ensc.bpi-router/-/tree/nanbield-next/meta-core/recipes-extended/libtirpc?ref_type=heads
(there exists a newer version but I do have not pushed it yet...)
[2] https://gitlab.com/ensc-groups/bpi-router/de.ensc.bpi-router/-/tree/nanbield-next/meta-core/recipes-connectivity/krb5?ref_type=heads
next prev parent reply other threads:[~2024-04-08 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 0:20 [PATCH v7 1/3] nfs-utils: clean up startup Dan McGregor
2024-04-02 0:20 ` [PATCH v7 2/3] nfs-utils: Use upstream systemd service files Dan McGregor
2024-04-07 20:35 ` [OE-core] " Alexandre Belloni
2024-04-02 0:20 ` [PATCH v7 3/3] nfs-utils: Configure nfsv4 ID mapping & Kerberos Dan McGregor
2024-04-08 12:51 ` Enrico Scholz [this message]
2024-04-08 17:00 ` [OE-core] " Dan McGregor
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=lybk6krpa7.fsf@ensc-pc.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=daniel.mcgregor@vecima.com \
--cc=danismostlikely@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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