On Sat, 2012-02-11 at 15:20 +0100, Arthur de Jong wrote: > The communication protocol that is in use between the NSS and PAM > modules on one end and nslcd on the other end uses host byte order to > transfer integer values. This will cause issues when the NSS or PAM > module uses a different endianness than nslcd.
Upstream release 0.9.0 has switched to using network byte order always. This is a backwards incompatible change. While previously it wasn't a problem for an older NSS module to communicate with a newer nslcd with a switch to 0.9 this is no longer the case. We should probably figure out how to handle the upgrade (I recall libc doing something similar). It may be a while until a 0.9 version is uploaded to Debian because the branch is in development and experimental is currently used for keeping the 0.8 up-to-date. -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong --
signature.asc
Description: This is a digitally signed message part
