Bug#1061701: nss-pam-ldapd: install PAM and NSS modules into /usr

On Sun, 2024-01-28 at 20:44 +0100, Michael Biebl wrote: > We want to finalize the /usr-merge via DEP17 by moving all files to > /usr. nss-pam-ldapd installs files into /lib; these should be moved > into the respective canonical locations in /usr/. > > Please find a patch attached. It has been

Bug#1035572: geany crashes often when clicking to switch focus

Package: geany Followup-For: Bug #1035572 On Fri, 2023-05-05 at 18:27 +0200, Arthur de Jong wrote: > Geany crashes for me on a regular basis. After some experimenting > I've found a way to reproduce this: > > - start geany > - from a new terminal open a not-yet-existing file: &

Bug#1035572: geany crashes often when clicking to switch focus

Package: geany Version: 1.38-1+b1 Severity: important Geany crashes for me on a regular basis. After some experimenting I've found a way to reproduce this: - start geany - from a new terminal open a not-yet-existing file: geany /tmp/some-file.txt - click a bit between geany and the terminal

Bug#1033919: svn2cl: svn2cl --html fails due to usrmerge

On Mon, 2023-04-03 at 23:39 +0200, H.-Dirk Schmitt wrote: > The `--html` option fails on bookworm, > > Due to the usrmerge the script is now invoked as `/bin/svn2cl`. > This leads to an error in the determination of the  snv2cl.xss file. Thanks for pointing this out (on my system I still had

Bug#1033919: svn2cl: svn2cl --html fails due to usrmerge

On Mon, 2023-04-03 at 23:39 +0200, H.-Dirk Schmitt wrote: > The `--html` option fails on bookworm, > > Due to the usrmerge the script is now invoked as `/bin/svn2cl`. > This leads to an error in the determination of the  snv2cl.xss file. Thanks for pointing this out (on my system I still had

Bug#1031979: libnss-ldapd: Entries for passwd and shadow are cleared on upgrade when system locale is sv_SE.UTF-8

On Sun, 2023-02-26 at 10:50 +0100, Arne Nordmark wrote: > The search for enabled services in /etc/nsswitch.conf breaks when > using the Swedish locale. > > LANG=C sed -n > 's/^[[:space:]]*\([a-z]*\)[[:space:]]*:.*[[:space:]]ldap\([[:space:]].*\)\?/\1/p' > /etc/nsswitch.conf | xargs > > gives

Bug#1030597: /usr/share/doc/lsb-base/README.Debian: file points to itself for more information

Package: lsb-base Version: 11.5 Severity: minor File: /usr/share/doc/lsb-base/README.Debian Ony my system /usr/share/doc/lsb-base/README.Debian contains: ... * The "lsb-base" package includes a number of functions used by init.d scripts in some LSB packages. For documentation of

Bug#1023460: in debian/nslcd.config, guess_ldap_uri returns the IP address instead of the name of the server

On Fri, 2022-11-04 at 11:00 -0400, Marvin Renich wrote: > When nslcd is installed [...] guess_ldap_uri tries to find an > appropriate ldap server using some heuristics.  If it finds a host > [...] it returns the IP address of the host rather than the name. The original reason for this was that if

Bug#1022311: python-stdnum: FTBFS: AssertionError: Failed doctest test for test_no_fodselsnummer.doctest

On Sun, 2022-10-23 at 14:50 +0200, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. A fix has just been uploaded and is part of version 1.18-1. If this ever needs to be backported for some reason the fix is trivial:

Bug#1018584: python-stdnum: build-depends on python3-nose or uses it for autopkgtest

Control: tags -1 + upstream pending On Sun, 2022-08-28 at 21:51 +0300, Dmitry Shachn > Your package still uses nose [1], which is an obsolete testing > framework for Python, dead and unmaintained since 2015 [2][3]. The upstream repo switched from nose to pytest:

Bug#989409: nss-pam-ldapd's autopkgtest fails with OpenLDAP 2.5

On Fri, 2022-02-18 at 19:11 -0800, Ryan Tandy wrote: > I removed "pwdMustChange: TRUE" from the policy and then the tests > passed. Not sure if this is the correct fix, but at least I don't > currently see anything in test_pamcmds.expect that would be expecting > a forced reset? Applying this

Bug#900253: nslcd: disabling ppolicy breaks authentication

On Sat, 2022-01-08 at 20:19 +0100, Nicolas Peugnet wrote: > I just ran into this bug. If I understand correctly it should have > been fixed by this commit: > > which is in Debian since version

Bug#1002047: reportbug: nslcd silently modifies /etc/nslcd.conf on upgrade, breaking authentication

Control: tags -1 + pending On Mon, 2021-12-20 at 22:03 +0100, Thomas Fargeix wrote: > The postinst script of nslcd silently modifies the configuration file > /etc/nslcd.conf on package upgrades. It rewrites or adds settings > without notification to the administrator. Thanks for this report. >

Bug#819961: nslcd: package upgrade fails in postinst due to uncommon characters in bindpw config parameter

Control: tags -1 + pending On Mon, 2021-12-20 at 21:07 +0100, Thomas Fargeix wrote: > /var/lib/dpkg/info/nslcd.postinst chocked on a randomly generated > password during my dist-upgrade from Buster to Bullseye, interrupting > and blocking the dist-upgrade and leaving the system in an unstable >

Bug#989409: nss-pam-ldapd's autopkgtest fails with OpenLDAP 2.5

Control: tags -1 + patch Hi Ryan, On Fri, 2021-06-04 at 11:19 -0700, Ryan Tandy wrote: > Hi. The attached patch updates the test slapd config to support > OpenLDAP 2.5 in addition to 2.4. Thanks for the patch. I've applied it in the upstream repo and I plan to make a new release soon. >

Bug#939259: webcheck: Python2 removal in sid/bullseye

On Mon, 2020-07-27 at 00:42 -0400, Sandro Tosi wrote: > 9 months have passed and i dont see any progress on this porting to > python3: last commits on https://arthurdejong.org/git/webcheck are > from 2013 (!) > > Are you still interested in this program (which you wrote)? should we > just remove

Bug#699114: O: libnss-ldap -- NSS module for using LDAP as a naming

On Tue, 2020-07-07 at 22:04 +0200, Chris Hofstaedtler wrote: > Do any of you think the situation has changed since 2013? > > Personally I would not want to have once popular NSS and PAM > libraries in the next stable release, if upstream has vanished a long > time ago. Looking at the popcon

Bug#958092: virtualenv: PIP fails with No module named 'pip._vendor.six'

Package: virtualenv Version: 20.0.17-1 Severity: important Creating a virtualenv no longer works: $ mkdir /tmp/a $ cd /tmp/a $ virtualenv venv created virtual environment CPython3.8.2.final.0-64 in 443ms creator CPython3Posix(dest=/tmp/a/venv, clear=False, global=False) seeder

Bug#953026: python-stdnum fails to validate new Dutch BTW/VAT number format

Control: fixed -1 python-stdnum/1.13-1 Control: forwarded -1 https://github.com/arthurdejong/python-stdnum/issues/182 Control: tags -1 + fixed-upstream On Tue, 2020-03-03 at 14:57 +0100, Harald Welte wrote: > The problem is that from January 1st, Dutch BTW (VAT) numbers can > have two valid

Bug#951536: Debian Bug Tracking System

On Mon, 2020-02-17 at 21:57 +0100, Ingo wrote: > On first login after boot up on the linux console with a local user I > have to wait one minute to get a shell prompt. After first login I > can logoff and login as usual without delay. This is weird. I suspect this is related to the mechanism that

Bug#939259: webcheck: Python2 removal in sid/bullseye

On Mon, 2019-09-02 at 15:09 +0200, Stefano Rivera wrote: > Your package either build-depends, depends on Python2, or uses > Python2 in the autopkg tests. Please stop using Python2, and fix > this issue by one of the following actions. > > - Convert your Package to Python3. I would like to do

Bug#900253: nslcd: disabling ppolicy breaks authentication

On Sun, 2019-09-22 at 01:01 +0900, Marc Dequènes wrote: > As I can see this part of the code did not change in 0.9.10. Hi Marc, Sorry for not responding sooner. There are two nslcd implementations: nslcd and pynslcd. The pynslcd implementation is more experimental and does not handle

Bug#923784: update-ca-certificates: corrupts ca-certificates.crt on full root file system

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Control: tags + patch I have created a merge request in Salsa for this: https://salsa.debian.org/debian/ca-certificates/merge_requests/2 - -- - -- arthur - adej...@debian.org - http://people.debian.org/~adejong -- -BEGIN PGP SIGNATURE-

Bug#923784: update-ca-certificates: corrupts ca-certificates.crt on full root file system

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: ca-certificates Version: 20161130+nmu1+deb9u1 Severity: normal File: /usr/sbin/update-ca-certificates If the root file system is full update-ca-certificates will corrupt the /etc/ssl/certs/ca-certificates.crt file. The script will

Bug#916789: nslcd: Proposal Of Systemd NSLCD

Control: merge 916789 892730 On Tue, 2018-12-18 at 17:25 +0100, Kevin Ariza wrote: > I have one proposal to solve the problem for add systemd .service > file, which is the following: > > [Unit] > Description=NSLCD Systemd Unit Debian > After=multi-user.target > > [Service] >

Bug#877002: nslcd installation broken: missing ca-certificates.crt

On Wed, 2019-01-16 at 15:43 -0800, Sunil Mohan Adapa wrote: > It would be nice to have fix for this in time for buster. Please > consider uploading the proposed fix. I've comitted a fix and will upload soon. Thanks for the patch and chasing me (I've been quite busy recently). Thanks, -- --

Bug#903840: nslcd unattentded upgrade fails/hangs at unter URI path

On Sun, 2018-07-15 at 09:48 -0700, Matt Weatherford wrote: > I went to upgrade my debian 9 system today and got a prompt at the > nslcd upgrade to enter the uri path. I entered this and the upgrade > hung. I am running upgrades over ssh sessions in non-interactive > mode and wonder if there is

Bug#872798: nslcd: can be killed by the OOM Killer, DoS

On Tue, 2017-08-22 at 00:52 +0200, Vincent Lefevre wrote: > Control: severity -1 normal > > (fixing the typo in the Control line) Thanks, I somehow never get these right ;) > Perhaps not unique to nslcd, but the consequences are the worst when > nslcd is killed: one can no longer access to the

Bug#872798: nslcd: can be killed by the OOM Killer, DoS

Control: sevirity -1 normal On Mon, 2017-08-21 at 13:17 +0200, Vincent Lefevre wrote: > Severity: grave > Justification: causes non-serious data loss and DoS from an end user. The severity is a bit questionable and, at the very least not a flaw in or unique to nslcd. Any local user that does not

Bug#863964: systemd does not restart nslcd after a segfault

On Sat, 2017-06-03 at 14:12 +, Sergio Gelato wrote: > I've now successfully tested the fix from #827444 on both jessie and > stretch. > > Specifically, I created > /etc/systemd/system/nslcd.service.d/forking.conf with the following > contents: > > [Service] > Type=forking >

Bug#861212: nslcd: certificate authentication fails with Unknown authentication method: SASL(-4)

On Thu, 2017-05-04 at 23:01 -0700, Matt Weatherford wrote: > Update:  I logged this bug further down the stack, as it was also  > affecting the "ldap-utils" package (ldapsearch and ldapwhoami also) > > I got some feedback that led us to determine that our LDAP server on  > CentOS was offering up

Bug#861212: nslcd: certificate authentication fails with Unknown authentication method: SASL(-4)

On Thu, 2017-04-27 at 20:25 -0700, Matt Weatherford wrote: > Im sure you have many, many other projects going but I am motivated > to solve this problem - is there anything else I can try on my > side?  I've sent you nslcd debug info ...  anything else I can do? Sorry for not replying sooner.

Bug#861212: nslcd: certificate authentication fails with Unknown authentication method: SASL(-4)

On Tue, 2017-04-25 at 16:53 -0700, Matt Weatherford wrote: > debian 7 install works fine with certificate auth. > Debian 9 install with same config files appears to not work and > throws these erros: > > Apr 25 16:41:08 nori nslcd[1376]: [52255a] failed to > bind to LDAP server

Bug#859432: nss-pam-ldapd shouldn't disable PIE

Control: tags -1 + pending On Mon, 2017-04-03 at 16:10 +0300, Adrian Bunk wrote: > With gcc in stretch defaulting to PIE, hardening=+all,-pie changed > semantics from "enable hardening but not PIE" to "enable all > hardening and explicitely disable the default PIE". > The latter is usually not

Bug#859452: libpam-ldapd: mixing with libnss-ldap does not work

On Mon, 2017-04-03 at 19:52 +0200, Laurent Bonnaud wrote: >  - libpam-ldapd + libnss-ldap  -> fails This works for me. Note that for this to work you have to include ldap in the shadow map in nsswitch.conf because otherwise pam_unix rejects the login. You should also be able to map the

Bug#858883: nslcd : missing symbols : _nss_ldap_version and _nss_ldap_enablelookups

On Mon, 2017-04-03 at 19:02 +0200, Laurent Bonnaud wrote: > This system had libnss-ldap installed, indeed.  I purged this > package, installed libnss-ldapd instead, but I still get the > warnings: Are you sure, can you run? dpkg -S /lib/x86_64-linux-gnu/libnss_ldap.so.2 dpkg --get-selections |

Bug#858826: nslcd: confusing error messages during package installation

Control: tags -1 + pending On Mon, 2017-03-27 at 12:41 +0200, Laurent Bonnaud wrote: > below is a full log of this package's installation.  What I found > confusing is: > >  - the error message > Warning: The home dir /var/run/nslcd/ you specified can't be > accessed: No such file or directory >

Bug#858608: spotweb: Wrong mysql-client dependency

Package: spotweb Version: 20130826+dfsg3-4 Severity: important    Dear Maintainer, The mysql-client dependency in spotweb is wrong which results in forcing the installation of MariaDB over an existing MySQL installation. The dependency on default-mysql-client should be default-mysql-client

Bug#851134: Info received (Bug#851134: nslcd crashes when losing contact with its server)

Control: severity -1 important On Tue, 2017-02-07 at 12:42 -0500, James Valleroy wrote: > Any update on this bug? Is it possible the severity could be lowered > until the analysis is complete? > > I have some packages (plinth, freedombox-setup) that depend on nslcd, > so I'm hoping that it won't

Bug#851134: Info received (Bug#851134: nslcd crashes when losing contact with its server)

On Mon, 23 Jan 2017, Elizabeth Myers wrote: I can't reproduce it with nslcd -d. It happens reliably outside of it though. I will try to get a core dump. You probably want to avoid adding the core file to the bug report since it will probably contain your client's private SSL key. If you

Bug#851134: nslcd crashes when losing contact with its server

Hi Elizabeth, I have been trying to reproduce this (nslcd 0.9.7-1, slapd 2.4.40+dfsg- 1+deb8u2). I have not been able to reproduce this when not using SSL and the following nslcd.conf also works without problems for me: uid nslcd gid nslcd uri ldaps://192.168.12.1/ base dc=thuis,dc=net

Bug#851564: nslcd fails to start: postinst sets tls_cacertdir wrong

end ca-certificate which is needed due to adding tls_cacertfile by default (see #750949) and the checking of tls_cacertfile in 0.9.7 (closes: #836720) + * fix parsing of nslcd.conf tls_cacert option in package configuration +(closes: #851564) - -- Arthur de Jong <adej...@debian.

Bug#851564: nslcd fails to start: postinst sets tls_cacertdir wrong

Hi, On Mon, 2017-01-16 at 11:52 +0100, Thomas Wallrafen wrote: > The aforementioned setting is probably added to the file via the > postinstall script of the nslcd package.  If one removes the line > tls_cacertfile dir /etc/ssl/certs from the file /etc/nslcd.conf and > runs > # dpkg --configrue

Bug#851134: nslcd crashes when losing contact with its server

On Thu, 2017-01-12 at 04:16 -0600, Elizabeth Myers wrote: > When restarting the OpenLDAP server, nslcd often crashes on multiple > servers with the following messages logged (I know they're not > helpful but it's what I have at the moment): > > nslcd[14819]: segfault at 0 ip 7fdc51502ce4 sp

Bug#777125: sysvinit-utils: service cmd with systemd shows, but did not stop duplicate instances of nslcd

Control: tags -1 + moreinfo On Thu, 2015-02-05 at 11:15 +0100, Hermann Lauer wrote: > during some "service {start,stop,restart,status} nslcd" usage > there are for unknown reasons two instances of nslcd running: Given that this is a 0.9.4 version of nslcd, there was a fix in 0.9.6-4 (bug

Bug#845443: jessie-pu: package nss-pam-ldapd/0.9.4-3+deb8u2

On Wed, 2016-11-23 at 14:19 +0100, Salvatore Bonaccorso wrote: > nss-pam-ldapd's nslcd under the conditions as described in #814881 > might fail to restart. nslcd restart which is stop+start with > systemd, is racy, and might lead to nslcd not running after a > restart. Ferenc has posted his

Bug#754248: [Python-modules-team] Bug#754248: python-virtualenv: Error when attempting to create a python2.6 virtualenv

On Mon, 2016-11-14 at 10:28 -0500, Barry Warsaw wrote: > On Nov 13, 2016, at 10:14 PM, Arthur de Jong wrote: > > I just ran into this today and I can confirm that the above fix > > allows me to move forward with a Python 2.6 virtualenv. Can you fix > > this for unstable?

Bug#754248: python-virtualenv: Error when attempting to create a python2.6 virtualenv

On Thu, 2015-01-08 at 06:08 +0200, Stefano Rivera wrote: > Hi John (2015.01.08_05:24:06_+0200) > > ++'/usr/share/python-wheels/{0}-*.whl'.format(project)) > > -+'/usr/share/python-wheels/{}-*.whl'.format(project)) > > That's simple enough that it is reasonable to apply.

Bug#717235: proftpd requests the whole passwd database at each login

On Tue, 2016-09-20 at 14:37 +0200, Hilmar Preuße wrote: > > An alternative is to do setpwent()/getpwent()/setpwent() which should > abort the started search without wasting too much time trying to > search LDAP entries in our environment. > > > ...and this is exactly what has been implemented

Bug#836720: nslcd should recommend ca-certificates

Control: tags -1 + pending On Mon, 2016-09-05 at 05:21 +, Mathias Gibbens wrote: > During installation nslcd failed to start, and I saw this error in > the log: > > > connection daemon: nslcdnslcd: /etc/nslcd.conf:28: tls_cacertfile: > > error accessing /etc/ssl/certs/ca-certificates.crt: No

Bug#825244: nslcd: Allow arbitrary maps via getent.ldap(1)

Hi, On Tue, 2016-05-24 at 20:43 -0400, Daniel Richard G. wrote: > I want to have an autofs mount for these so that they are accessible, > but I need to query a "unixHomeDirectory" attribute in LDAP (homedirs > are spread across multiple servers so I can't just construct a path > from the

Bug#825153: nslcd: Numerous '

On Tue, 2016-05-24 at 19:01 -0400, Daniel Richard G. wrote: > After picking through the backtrace, I've found exactly what is > generating the request. Below, I've copied the entire shell function > in question (from /usr/share/bash-completion/bash_completion), and > have marked the offending

Bug#825153: nslcd: Numerous '

On Tue, 2016-05-24 at 16:24 -0400, Daniel Richard G. wrote: > > No, I'm pretty sure it is some sort of lookup that is meant to > > return nu users at all or a misconfiguration somewhere. > > If I can find what is doing this, should the behavior be > considered a bug? At the very least it is

Bug#825153: nslcd: Numerous '

On Tue, 2016-05-24 at 03:27 -0400, Daniel Richard G. wrote: > I am seeing relatively frequent entries of this form in syslog: > > May 24 03:04:23 darkstar nslcd[1187]: [3c9869] request denied by > validnames option > > While I am uncertain as to what causes this, at one point it appeared >

Bug#820025: python-pskc-doc: missing Breaks+Replaces: python-pskc (<< 0.4)

On Mon, 2016-04-04 at 22:35 +0200, Andreas Beckmann wrote: > during a test with piuparts I noticed your package fails to upgrade > from 'testing'. > It installed fine in 'testing', then the upgrade to 'sid' fails > because it tries to overwrite other packages files without declaring > a

Bug#814881: nslcd is stopped after service restart

Control: tags -1 + pending On Tue, 2016-02-16 at 10:09 +0100, Michael Braun wrote: > After installing some unrelated program using apt-get, it was > discovered that nslcd needs a restart und I was promted to restart it > (among other services). Were you using needrestart for this? I've had

Bug#794686: nslcd start script does not report starting failure

On Thu, 2016-02-11 at 14:13 +0300, Nikolay Shaplov wrote: > This bug was not fixed for debian jessie, as I can see...  > And I think it should be fixed in all supported distributives, as it > can cause problems. Thanks for reminding me. I uploaded a new version for jessie yesterday. -- --

Bug#785053: jessie-pu: package nss-pam-ldapd/0.9.4-3+deb8u1

On Fri, 2016-01-01 at 17:16 +, Adam D. Barratt wrote: > Apologies for the repeated delay. :-| Please go ahead. Just when I wanted to wrap this up, another important bug popped up with a trivial fix :) The bug is #811476 which has a trivial fix that has been in testing for a long time and

Bug#811476: libnss-ldapd: getent hosts crashes with nss-ldapd and mixed IPv4/IPv6 reading

Control: tags -1 + patch fixed-upstream Control: fixed -1 nss-pam-ldapd/0.9.5-1 On Tue, 2016-01-19 at 10:55 +0100, Simon Bin wrote: > The version 0.9.4 of libnss-ldapd contains a flaw that makes the > `getent hosts` command and similar name resolution crash when the > LDAP directory contains

Bug#803316: python-stdnum: new feature eu.vat.check_vies does not work

Control: tags -1 + fixed-upstream Control: tags -1 + pending On Wed, 2015-10-28 at 18:19 +0100, Lionel Elie Mamane wrote: > >>> stdnum.eu.vat.check_vies_approx('BE555445','BE87785') > Traceback (most recent call last): >   File "", line 1, in >   File

Bug#737079: nscd crashes on netgroup lookups

On Thu, 2015-10-15 at 00:29 -0400, Carlos O'Donell wrote: > The upstream glibc community has been working hard to rectify these > issues, and Red Hat in particular spent a lot of time making the > netgroup caching as bullet-proof as possible. If you have real bugs, > please file them upstream and

Bug#737079: nscd crashes on netgroup lookups

On Wed, 2015-10-14 at 07:56 +, Mike Gabriel wrote: > The Debian Edu team heavily relies on NIS netgroups coming from > LDAP. So any help with this in Debian jessie is highly appreciated!!! The last time I looked at nscd code I was not very happy ;) Also, nscd has a long history of instability

Bug#801217: modplugtools: Please reference shuf instead of randomize-lines

On Thu, 2015-10-08 at 09:24 +0200, gurkan wrote: > Here? > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799414 > Either wrong bug number, or I look at the wrong place? Sorry, indeed wrong bug number, please see #801171:   https://bugs.debian.org/801171 Thanks, -- -- arthur -

Bug#801171: Please remove this package

Control: reassign -1 ftp.debian.org Control: retitle -1 RM: randomize-lines -- ROM; deprecated, replaced by shuf On Wed, 2015-10-07 at 09:19 +0200, martin f krafft wrote: > Since this is deprecated and the shuf coreutil replaces it > adequately, please reassign this bug to ftp.debian.org and

Bug#801217: modplugtools: Please reference shuf instead of randomize-lines

:12.0 +0200 @@ -1,3 +1,10 @@ +modplugtools (0.5.3-1.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Replace randomize-lines with shuf from coreutils. + + -- Arthur de Jong <adej...@debian.org> Wed, 07 Oct 2015 16:22:35 +0200 + modplugtools (0.5.3-1.1) unstable; urgency=low

Bug#798942: Does not fail over to another server when server is unwilling to perform

On Mon, 2015-09-14 at 12:41 +0200, Bernhard Schmidt wrote: > Due to a local configuration error we had a new slapd deployed on a > server that requires authentication (our normal servers don't, yet). > nslcd tried to connect to the server (which was unwilling to perform) > but did not fail over

Bug#799414: nss-pam-ldapd: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

Control: tags -1 + pending On Fri, 2015-09-18 at 20:50 -0300, Adriano Rafael Gomes wrote: > Please, Could you update the Brazilian Portuguese Translation? > > Attached you will find the file pt_BR.po. It is UTF-8 encoded and it > is tested with msgfmt and podebconf-display-po. Thanks for the

Bug#785053: jessie-pu: package nss-pam-ldapd/0.9.4-3+deb8u1

in signal +handling during start-up (closes: #759544) + * ensure proper return code of init script (closes: #794686) + * fix-ppolicy-expiration-warnings.patch: fix password policy expiration +warnings (closes: #794068) + + -- Arthur de Jong adej...@debian.org Sun, 30 Aug 2015 13:00:00 +0200

Bug#794068: AW: Bug#794068: libpam-ldapd: unable to login when ldap-server sends password expiration warning

On Mon, 2015-08-17 at 09:06 +, Uibel, Joerg wrote: Thank you for the upstream fix. While I realize that you prefer to get a whole new upstream release into jessie, I wonder if there's any reason not to backport the relevant changes [1-3] to the nss-pam -ldapd_0.9.4-3 source? I rebuilt

Bug#794068: libpam-ldapd: unable to login when ldap-server sends password expiration warning

Control: tags -1 + fixed-upstream On Thu, 2015-07-30 at 09:22 +, Uibel, Joerg wrote: I'm using the OpenLDAP password policy overlay on my ldap-servers to implement password expiration. The attribute pwdExpireWarning is set to 10 days. Unfortunately it doesn't only print a warning to the

Bug#794686: nslcd start script does not report starting failure

Control: tags -1 + pending On Wed, 2015-08-05 at 20:02 +0300, Nikolay Shaplov wrote: Package: nslcd Version: 0.9.4-3 Severity: serious Justification: fails to build from source Justification is not right but the init script return code is not according to policy so I'll leave it at serious.

Bug#792871: python-daemon: signal_map handling wrong

-unicode 'termniate' string is passed via the signal_map argument to the DaemonContext constructor. The reason this appears to work in the tests is due to from __future__ import unicode_literals Author: Arthur de Jong adej...@debian.org --- a/daemon/daemon.py +++ b/daemon/daemon.py @@ -483,7 +483,7

Bug#783644: python-stdnum: new feature: EU VAT VIES check _with_ proof (certificate)

Control: tags -1 + pending On Tue, 2015-04-28 at 23:02 +0200, Lionel Elie Mamane wrote: I'm not eager for a single function to return differently structured data depending on an argument that does not look like it should influence this part of the structure. Having two functions emphasises

Bug#788084: python-stdnum: Please use a maintained soap library instead of deprecated python-suds.

Control: forcemerge 774948 788084 Control: tags 774948 + fixed-upstream Control: tags 774948 + pending your package is listed as a Reverse Depend of the python-suds package, which is now deprecated due to long time missing upstream maintenance as well as missing compatibility for Python3

Bug#789616: [Evolution] Bug#789616: evolution-plugins: Face header too long

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=751462 On Wed, 2015-06-24 at 13:32 +0200, Emilio Pozuelo Monfort wrote: Thanks for the patch. Can you please send it upstream and let us know the bug url? Sure. I put the relevant details and patch here:

Bug#789616: evolution-plugins: Face header too long

Control: reassign -1 evolution-data-server 3.16.3-1 Control: tags -1 + patch On Mon, 2015-06-22 at 21:31 +0200, Arthur de Jong wrote: which means the first line ends up as 1003 characters. While this technically may be a bug in that software it is probably much easier to work around

Bug#789616: evolution-plugins: Face header too long

On Mon, 2015-06-22 at 19:55 +0200, Arthur de Jong wrote: When using the face plugin to configuring an image, a Face header is added to outgoing email. For common sizes of images this results in lines that are too long. RFC 2822 section 2.1.1 specifies the maximum line length to be 998

Bug#789616: evolution-plugins: Face header too long

Package: evolution-plugins Version: 3.16.3-1 Severity: important When using the face plugin to configuring an image, a Face header is added to outgoing email. For common sizes of images this results in lines that are too long. RFC 2822 section 2.1.1 specifies the maximum line length to be 998.

Bug#785053: jessie-pu: package nss-pam-ldapd/0.9.4-3

On Thu, 2015-06-04 at 21:04 +0200, Arthur de Jong wrote: On Mon, 2015-05-11 at 23:12 +0200, Arthur de Jong wrote: I would like to fix #759544 in jessie. Just to clarify, #759544 seems to affect people who use systemd and network-manager together with nslcd. The bug is a race condition

Bug#780320: nslcd group queries not working in jessie

On Fri, 2015-05-22 at 21:44 +0200, Torsten Landschoff wrote: Any hint how this can be fixed? I'd be up to patch the source and build a new package for our local systems. Could you provide the relevant bits of nslcd.conf (leave out any passwords) and output from nslcd -d when the error occurs?

Bug#759544: please fix in jessie

On Sun, 10 May 2015, Meik Hellmund wrote: Please provide a patched version of nslcd for jessie-updates. I just upgraded a larger installation of Debian servers and desktop clients to jessie and was bitten by this bug. Progress on getting this fixed in jessie can be tracked at

Bug#785053: jessie-pu: package nss-pam-ldapd/0.9.4-3

Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu I would like to fix #759544 in jessie. There is a fix already in 0.9.5-2 in testing and unstable (avoid-signal-race.patch as seen in the package). I see a couple of ways to solve

Bug#783644: python-stdnum: new feature: EU VAT VIES check _with_ proof (certificate)

On Tue, 2015-04-28 at 19:09 +0200, Lionel Elie Mamane wrote: Please add a new function to stdnum.eu.vat so that when one does a VIES VAT number check, one gets a proof (certificate) that one did the check, as defence against the VAT administration later putting this in doubt. This certificate

Bug#640774: Stopping nslcd no longer

On Fri, 2015-04-17 at 19:28 +0200, أحمد المحمودي wrote: Please find /etc/pam.d/common-auth attached. I have been playing around with pam_ccreds and I think the bug is in that package or a configuration mix-up. Anyway, if I disable shadow lookups via ldap in /etc/nsswitch.conf I got it to work,

Bug#774948: python3-stdnum: stdnum.eu.vat.check_vies needs suds

Control: severity -1 normal Control: tags -1 + help On Fri, 2015-01-09 at 12:40 +0100, Lionel Elie Mamane wrote: ImportError: No module named 'suds' An Internet search suggests suds itself is not available for Python3, but there seems to be several forks that are. A while back I did some

Bug#782652: nslcd: Does not start at boot when uri set to DNS

On Wed, 2015-04-15 at 18:36 +0200, أحمد المحمودي wrote: This bug might be related to #626603 It could be related. In general, if nslcd is started before DNS is available, it can have issues with lookups. The DNS option for uri makes this especially problematic because a DNS lookup is performed

Bug#705568: libpam-ldapd: LDAP Authentication failure with cached credentials

On Wed, 2015-04-15 at 19:13 +0200, أحمد المحمودي wrote: In 0.9.4-3 revision, Account-Type is Primary, so I applied your changes for the Account: entry, yet neither local nor LDAP users can login (even if LDAP server is reachable), and I found the following in /var/log/auth.log: Apr 15

Bug#640774: Stopping nslcd no longer

On Wed, 2015-04-15 at 19:07 +0200, أحمد المحمودي wrote: I am experiencing the issue of login failure with cached credentials, yet stopping nslcd no longer helps, rather I get this in /var/log/auth.log: Apr 15 18:19:42 myhostname login[13342]: pam_ldap(login:auth): error opening connection to

Bug#759544: nslcd: fails 'sometimes' to start at boot (systemd?)

Control: found -1 nss-pam-ldapd/0.9.1-1 Control: tags + pending On Mon, 2015-04-13 at 15:36 +0200, Bernhard Schmidt wrote: I still think it is caused by a race between the ifupdown trigger and nslcd startup. Thanks for prodding me about this. I've spent some more time trying to track this down

Bug#782554: libpam-ldapd: pam-configs/ldap should consult /etc/login.defs for UID_MIN setting

On Tue, 2015-04-14 at 15:28 +0930, Phil Nitschke wrote: We inherited a legacy system where user's UIDs are less than 1000. We set the UID_MIN value in /etc/login.defs, but whenever libpam-ldapd is updated, it specifies minimum_uid=1000 and users cannot log in. I also manage a legacy system

Bug#780320: nslcd: Fails to return group names

On Wed, 2015-03-11 at 19:27 -0600, Daniel Fussell wrote: Running nslcd on sid generally works, but is not able to get group names from ldap, reporting the following errors when requesting information on a user with the id command: nslcd: [9478fe] DEBUG: connection from pid=2735 uid=2345

Bug#780284: nss-pam-ldapd: Descriptions do not explain why to use this over lib{pam, nss}-ldap

is a fresh implementation written by Arthur de Jong, which doesn't install TLS and LDAP libraries into every single running program twb Instead [it] loads a shim that talks over a socket to nslcd, a dedicated daemon. He thinks maybe you meant to be modest in your descriptions, but IMO

Bug#759544: nslcd: fails 'sometimes' to start at boot (systemd?)

On Wed, 2015-03-04 at 16:59 +0100, Rike-Benjamin Schuppner wrote: On Sun, 04 Jan 2015 00:42:42 +0100 Bernhard Schmidt be...@birkenwald.de wrote: This sounds like http://arthurdejong.org/git/nss-pam-ldapd/commit/?id=1d3b19b1ecd3b10f36e8925e8a752a28e3e74b56 could help here. Unfortunately I

Bug#759544: Bug#772342: debian-edu-config: mounting homedirs via NFS doesn't work reliably

tags 759544 + help thanks On Wed, 2014-12-10 at 22:32 +0100, Holger Levsen wrote: Raising the severity of 759544 as 20% failure rate surely has a major impact on the usuability of the package... Please see 772342 to learn how 759544 affects debian-edu-config. Any help in tracking this down

Bug#759544: nslcd: fails 'sometimes' to start at boot (systemd?)

On Fri, 2014-08-29 at 17:22 +0200, Andreas B. Mundt wrote: Hm. Any other hints how to pin down the issue? Sorry to not get back to you sooner. Can you try these patches: http://arthurdejong.org/git/nss-pam-ldapd/commit/?id=a726d291b0f6794abec0a0192cf2b2a742648e4a

Bug#760287: please set nslcd as preferred provider of nslcd-2

Control: tags -1 + pending On Tue, 2014-09-02 at 08:13 -0700, Ryan Tandy wrote: With two providers of nslcd-2 and no preferred one declared, apt-get (at least on two systems of mine) chooses pynslcd instead of nslcd. Please consider changing the nslcd-2 dependency to 'nslcd | nslcd-2', at

Bug#759540: pynslcd immediately exits / fails to run

On Thu, 2014-08-28 at 11:47 +0200, Andreas B. Mundt wrote: pynslcd fail to start here on debian-lan. I attach the debug log. This problem does not happen with nslcd, where things work. Thanks for reporting this. I've seen some issues in pynslcd in combination with SSL/TLS. Sadly error messages

Bug#759544: nslcd: fails 'sometimes' to start at boot (systemd?)

On Thu, 2014-08-28 at 12:34 +0200, Andreas B. Mundt wrote: another issue I just observed: nslcd 'sometimes', perhaps 1 of 5 reboots, fails to start/run at boot. systemctl status tells me in these cases: root@workstation00:~# systemctl status nslcd -l nslcd.service - LSB: LDAP connection

Bug#758693: Updated Norwegian Bokmål debconf translation (nb.po)

Control: tags -1 + pending On Wed, 2014-08-20 at 09:47 +0200, Petter Reinholdtsen wrote: Hi. Here is an updated debconf translation for Norwegian Bokmål (nb.po). Thanks for the updated translation, it will be in the next upload. Btw, the file you sent was encoded using ISO-8859-1 while the po

Bug#643948:

On Mon, 2014-07-21 at 17:38 -0700, Peter Mairhofer wrote: I have the same issue. It happens rarely but that's the bigger issue: NSS/LDAP is the most critical service because without, all services and even login is broken. I have not seen the issue myself for a long time. But from my logs it

  1   2   3   4   5   6   7   8   >