Your message dated Mon, 20 Dec 2010 16:50:38 +0100 with message-id <20101220155038.GX5063@radis.liafa.jussieu.fr> and subject line Re: Bug#607360: unblock: nss-pam-ldapd/0.7.13 has caused the Debian Bug report #607360, regarding unblock: nss-pam-ldapd/0.7.13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 607360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607360 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: nss-pam-ldapd/0.7.13
- From: Arthur de Jong <adejong@debian.org>
- Date: Fri, 17 Dec 2010 14:09:36 +0100
- Message-id: <[🔎] 1292591376.2848.5.camel@sorbet.thuis.net>
Subject: unblock: nss-pam-ldapd/0.7.13 Package: release.debian.org User: release.debian.org@packages.debian.org Usertags: freeze-exception Severity: normal Please unblock version 0.7.13 of nss-pam-ldapd. It has the following changes: * fix handling of idle_timelimit option * fix error code for problem while doing password modification The second change is rather minor but is just a one-line fix (the change in nslcd/pam.c) that should be obvious and without possible side effects. The first change is the RC one because it causes problems if the LDAP server closes the connection after a timeout. This confuses the reconnect-handling and timeout code and makes the LDAP server appear to be unavailable for some time. This is apparently common when using Microsoft Active Directory and makes it impossible to resolve user names (and anything else that comes from LDAP). A proper fix for this is in the works in the development version but that is much larger. The fix is for the workaround that is normally used for this (have the client side use a timeout). The problem was that timed out connections were never closed because the new search was started before trying to close the old connection. Some background for this problem is available here: http://lists.arthurdejong.org/nss-pam-ldapd-users/2010/msg00173.html (since this issue did not come in through the BTS it's not there) Thanks for considering. -- -- arthur - adejong@debian.org - http://people.debian.org/~adejong --Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
- To: Arthur de Jong <adejong@debian.org>, 607360-done@bugs.debian.org
- Subject: Re: Bug#607360: unblock: nss-pam-ldapd/0.7.13
- From: Julien Cristau <jcristau@debian.org>
- Date: Mon, 20 Dec 2010 16:50:38 +0100
- Message-id: <20101220155038.GX5063@radis.liafa.jussieu.fr>
- In-reply-to: <[🔎] 1292591376.2848.5.camel@sorbet.thuis.net>
- References: <[🔎] 1292591376.2848.5.camel@sorbet.thuis.net>
On Fri, Dec 17, 2010 at 14:09:36 +0100, Arthur de Jong wrote: > Subject: unblock: nss-pam-ldapd/0.7.13 > Package: release.debian.org > User: release.debian.org@packages.debian.org > Usertags: freeze-exception > Severity: normal > > Please unblock version 0.7.13 of nss-pam-ldapd. It has the following > changes: > > * fix handling of idle_timelimit option > * fix error code for problem while doing password modification > unblocked, thanks. Cheers, JulienAttachment: signature.asc
Description: Digital signature
--- End Message ---