This bug was fixed in the package nss-pam-ldapd - 0.9.12-1
---------------
nss-pam-ldapd (0.9.12-1) unstable; urgency=medium
[ Arthur de Jong ]
* New upstream release:
- allow explicitly configuring an empty search base (for LDAP servers
that support that)
- support LDAP attributes with minus characters in attribute mapping
expressions
- add tls_reqsan, tls_crlfile and tls_crlcheck options (thanks
Sebastien Blavier)
- support generating ldaps:// URIs from DNS SRV records for port 389 by
using DNSLDAPS in the uri option
- prefer the first URI listed in nslcd.conf after reconnecting after
idle_timelimit
- fix handling of pam_authc_ppolicy no
- fix debug logging of ldap timeout values
- documentation improvements (thanks Filip Dvorak and Benedict Reuschling)
- add pam_authc_ppolicy support to pynslcd
- fix Python 3 compatibility in chsh.ldap
- fix for running pynslcd without the uid option
- partial support for running tests with slapd 2.5 (thanks Ryan Tandy)
* Switch to using /run/nslcd (fixes lintian warnings)
* Update debian/upstream/metadata
* Drop lintian override
* Use debhelper-compat instead of debian/compat
* Update debhelper compatibility level to 13
* Specify Rules-Requires-Root: no
* Update debian/watch version
* Upgrade to standards-version 4.6.0 (no changes needed)
* Include more output on test suite failure
* Add lintian override for pam_ldap(8) manual page warning
* Run tests with netbase installed for /etc/services and /etc/protocols
[ Sergio Durigan Junior ]
* Support networkd-dispatcher notifications
- d/nslcd.if-up: Adjust script to make it compatible with
networkd-dispatcher
- d/nslcd.links: Install the proper nslcd script inside the
/usr/lib/networkd-dispatcher/routable.d/ directory (LP: #1718227)
-- Arthur de Jong <adej...@debian.org> Sat, 20 Nov 2021 16:10:03 +0100
** Changed in: nss-pam-ldapd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to mythtv in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
Invalid
Status in ethtool package in Ubuntu:
Triaged
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
Fix Released
Status in ntp package in Ubuntu:
Won't Fix
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
Fix Released
Status in openvpn package in Ubuntu:
Confirmed
Status in openvswitch package in Ubuntu:
Triaged
Status in postfix package in Ubuntu:
Fix Released
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~mythbuntu-bugs
Post to : mythbuntu-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mythbuntu-bugs
More help : https://help.launchpad.net/ListHelp
