Re: fixes for getpeercred.c
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
Re: fixes for getpeercred.c
- From: Brett Lymn <blymn [at] internode.on.net>
- To: Arthur de Jong <arthur [at] arthurdejong.org>
- Cc: nss-pam-ldapd-users [at] lists.arthurdejong.org
- Subject: Re: fixes for getpeercred.c
- Date: Mon, 26 Jun 2023 16:38:58 +0930
On Sun, Jun 25, 2023 at 11:00:30AM +0200, Arthur de Jong wrote:
> On Fri, 2023-06-23 at 07:52 +0930, Brett Lymn wrote:
> > On Sat, Jun 17, 2023 at 10:25:11PM +0200, Arthur de Jong wrote:
> >
> > Thanks. There are a few more changes before we can compile cleanly
> > on NetbSD, I have a proposal in to import the FreeBSD nss compat
> > headers so we should just be able to use the FreeBSD style compat
> > layer.
>
> You might also be interested in
> https://github.com/arthurdejong/nss-pam-ldapd/pull/36
>
Yes, I am aware of those changes too, they are patches that are used in
the WIP (work in progress) pkgsrc nss-pam-ldapd package that they want
to upstream, hence the pull request :)
> >
> > On another topic, can I gently prod about the change proposal I
> > posted a while ago? I am happy to do the work but it is important to
> > me that the changes are incorportated into this project.
>
> You mean per search-DN configuration? For attribute mapping you could
> already use the "${attr1:-$attr2}" syntax for alternatives but not all
> attributes can use these kind of expressions because they are used in
> search filters. I'm guessing that could become pretty complex quite
> quickly. I would personally see if something like that could be solved
> in an LDAP proxy. I'm not against integrating such a change but since I
> have limited time available I can't guarantee that such a change can be
> integrated quickly.
>
Yes I mean the per search-DN configuration. Rather than hijack this
thread I will start a new one.
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"