Subject: nss-pam-ldapd: problem with mixed endian multiarch Source: nss-pam-ldapd Version: 0.8.4 Severity: important User: multiarch-de...@lists.alioth.debian.org Usertags: multiarch Tags: help
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. Ideally, the protocol should be updated to always use network byte order. This is however a backwards incompatible change and may need careful consideration during upgrades. For example, running processes may have an older version of the NSS module loaded and will no longer be able to find users unless nslcd accepts both the old and new protocol. Updating the protocol does also offer some room to make other improvements (for example to the PAM part of the protocol). Advice on how to handle this is more than welcome. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong --
signature.asc
Description: This is a digitally signed message part
