separate Unix domain sockets for NSS and PAM
[Date Prev][Date Next] [Thread Prev][Thread Next]separate Unix domain sockets for NSS and PAM
- From: Michael Ströder <michael [at] stroeder.com>
- To: nss-pam-ldapd-users [at] lists.arthurdejong.org
- Subject: separate Unix domain sockets for NSS and PAM
- Date: Wed, 18 Sep 2019 18:46:05 +0200
HI!I'm using nss-pam-ldapd's PAM and NSS frontend modules for sending NSS and PAM requests to my own custom demon implemented with Python.
Now for various reasons I'm trying to isolate things a bit more. E.g. in my setup I'd like to have separate NSS and PAM services listening on separate sockets.
Disclaimer: I'm not a C programmer.Diving into the code I've first started to tweak configure.ac (see attached patch). But then I got stuck a bit. It seems I would have to modify some macros etc.
Before I start developing a patch: Would that be a feature accepted into upstream? Ciao, Michael.
Attachment:
0001-new-autoconf-options-with-nss-socket-and-with-pam-so.patch
Description: Text Data
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
- separate Unix domain sockets for NSS and PAM, Michael Ströder
- Re: separate Unix domain sockets for NSS and PAM, Arthur de Jong
- Prev by Date: Re: nslcd.conf - ldap_result() failed: No such object: cdcLdapSearch :System error (cdcRC=28)
- Next by Date: Re: separate Unix domain sockets for NSS and PAM
- Previous by thread: Re: nslcd.conf - ldap_result() failed: No such object: cdcLdapSearch :System error (cdcRC=28)
- Next by thread: Re: separate Unix domain sockets for NSS and PAM