Fix released in 3.0.0.
** Changed in: apparmor
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575438
Title:
usr.sbin.nscd needs r/w access to nslcd
An update to the "ldapclient" abstraction has been merged upstream:
https://gitlab.com/apparmor/apparmor/merge_requests/153/diffs?commit_id=ac1d0545f458b11728f2bcb4a7de0567538fa94a
** Changed in: apparmor
Status: New => Fix Committed
** Changed in: apparmor (Ubuntu)
Status: New =>
I think you're right that adding the nslcd socket to the
abstractions/nameservice probably makes sense; I didn't see anything in
the nslcd manpages that suggested nscd was the only way to use the
module.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Tags added: aa-policy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575438
Title:
usr.sbin.nscd needs r/w access to nslcd socket
To manage notifications about this bug go to:
Minor addendum: It's conceivable that the new line should go into
rather than just the nscd profile. I do see
that the nscd socket is already mentioned there.
I don't know if/why anything else would need access to the nslcd socket,
but that may be a valid use case for other folks.
--
You
** Also affects: apparmor
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575438
Title:
usr.sbin.nscd needs r/w access to nslcd socket
To manage
