| 1 |
nss-pam-ldapd (0.9.0-1) experimental; urgency=low |
| 2 |
|
| 3 |
The 0.9 release changes the communication protocol used between the NSS |
| 4 |
and PAM modules on one end and the nslcd process on the other end. |
| 5 |
|
| 6 |
This means that after the upgrade, if the new nslcd is running, processes |
| 7 |
that have the old NSS or PAM module already loaded will be unable to |
| 8 |
perform queries. |
| 9 |
|
| 10 |
For example, if a screensaver that was running before the upgrade has |
| 11 |
locked the screen during the upgrade, the user will no longer be able to |
| 12 |
unlock the screen. |
| 13 |
|
| 14 |
-- Arthur de Jong <[email protected]> Sat, 06 Apr 2013 15:00:00 +0200 |
| 15 |
|
| 16 |
nss-pam-ldapd (0.7.0) unstable; urgency=low |
| 17 |
|
| 18 |
The package has been split into libnss-ldapd which contains the the NSS |
| 19 |
module, libpam-ldapd which contains the PAM module and nslcd which |
| 20 |
includes the daemon that performs the LDAP operations. |
| 21 |
|
| 22 |
The configuration file has been changed to /etc/nslcd.conf to reflect this |
| 23 |
new organisation of packages (upgrades should create this file based on |
| 24 |
any existing /etc/nss-ldapd.conf file). |
| 25 |
|
| 26 |
-- Arthur de Jong <[email protected]> Tue, 01 Sep 2009 17:00:00 +0200 |