bug with pam-auth-update ?

Path	csiph.com!feeder.erje.net!2.eu.feeder.erje.net!border1.nntp.ams1.giganews.com!nntp.giganews.com!feeds.phibee-telecom.net!news.panservice.it!bofh.it!news.nic.it!robomod
From	Jean-Louis Mas <Jean-Louis.Mas@imag.fr>
Newsgroups	linux.debian.user
Subject	bug with pam-auth-update ?
Date	Fri, 08 Apr 2016 10:20:02 +0200
Message-ID	<rlzO2-Ty-31@gated-at.bofh.it> (permalink)
X-Mailbox-Line	From debian-user-request@lists.debian.org Fri Apr 8 08:18:44 2016
Old-Return-Path	<Jean-Louis.Mas@imag.fr>
X-Amavis-Spam-Status	No, score=-4.616 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SARE_ADLTOBFU=0.68] autolearn=no autolearn_force=no
X-Policyd-Weight	using cached result; rate: -8.1
X-Enigmail-Draft-Status	N1110
User-Agent	Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version	1.0
Content-Type	text/plain; charset=utf-8
Content-Transfer-Encoding	7bit
X-Greylist	Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (mx2.imag.fr [129.88.30.17]); Fri, 08 Apr 2016 10:18:26 +0200 (CEST)
X-Imag-Mailscanner-Information	Please contact MI2S MIM for more information
X-Mailscanner-ID	u388IP5Q004063
X-Imag-Mailscanner	Found to be clean
X-Imag-Mailscanner-From	jean-louis.mas@imag.fr
Mailscanner-Null-Check	1460708306.21193@VAxH8YHcm5VEkPbmW7osBw
X-Mailing-List	<debian-user@lists.debian.org> archive/latest/706016
List-ID	<debian-user.lists.debian.org>
List-URL	<https://lists.debian.org/debian-user/>
List-Archive	https://lists.debian.org/msgid-search/57076952.8060606@imag.fr
Approved	robomod@news.nic.it
Lines	76
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Fri, 8 Apr 2016 10:18:26 +0200
X-Original-Message-ID	<57076952.8060606@imag.fr>
Xref	csiph.com linux.debian.user:166525

Show key headers only | View raw

No luck with the french debian list, so I try here

We have some servers running Debian Jessie 8.4 amd64
We update them via a cron script and as you see it, pam-auth-update
freeze our cron update


'ps -efH' extract

root      22723  21862  3 avril03 ?      01:08:58               apt-get
-y -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confold
dist-upgrade
root      38647  22723  0 avril03 pts/2  00:00:00
/usr/bin/dpkg --force-confdef --force-confold --status-fd 32 --configure
libc-dev-bin:amd64 linux-libc-dev:amd64 libc6-dev:amd64
initramfs-tools:all linux-image-3.16.0-4-amd64:amd64
libpam-systemd:amd64 libpcrecpp0:amd64 libpcre3-dev:amd64
libapt-inst1.5:amd64 libcairo2:amd64 libglib2.0-0:amd64
libcairo-gobject2:amd64 libcairo-script-interpreter2:amd64
libglib2.0-bin:amd64 libglib2.0-dev:amd64 libcairo2-dev:amd64
libgif4:amd64 librsvg2-2:amd64 librsvg2-common:amd64
libgtk2.0-common:all libgtk2.0-0:amd64 gir1.2-gtk-2.0:amd64
libgtk2.0-dev:amd64 libgtk2.0-bin:amd64 libgudev-1.0-0:amd64
libnettle4:amd64 libhogweed2:amd64 libsndfile1:amd64 libsvn1:amd64
subversion:amd64 nslcd:amd64 libnss-ldapd:amd64 libpam-ldapd:amd64
apt-utils:amd64 locales:all libruby:all libsane-common:all
linux-compiler-gcc-4.8-x86:amd64 linux-headers-3.16.0-4-common:amd64
linux-headers-3.16.0-4-amd64:amd64 linux-source-3.16:all ruby:all
nslcd-utils:all
root      42111  38647  0 avril03 pts/2  00:00:00
/bin/sh /var/lib/dpkg/info/libpam-systemd:amd64.postinst configure
215-17+deb8u3
root      42112  42111  0 avril03 pts/2  00:00:00
/usr/bin/perl -w /usr/share/debconf/frontend /usr/sbin/pam-auth-update
--package
root      42122  42112  0 avril03 pts/2  00:00:00
/usr/bin/perl -w /usr/sbin/pam-auth-update --package


What happen here, as the copy/paste above is a bit messy, is a perl
script calling :

/usr/sbin/pam-auth-update --package

freezing our update if we don't manually answer.

But man pam-auth-update says :

"Selection of profiles is done using the standard debconf interface.
The profile selection question will be asked at `medium' priority when
packages are added or removed, so no user interaction is required by
default.  Users may invoke pam-auth-update  directly  to  change their
authentication configuration.

OPTIONS
       --package
              Indicate that the caller is a package maintainer script;
lowers the priority of debconf questions to `medium' so that the user is
not prompted by default."


It don't seems to work the intended way. We use custom etc/pam.d/*
files, with a different umask in mkhomedir, pam_access and pam_ldap,
nothing to special here.

Is this a pam-auth-update, debconf or systemd bug ?
Is our apt-get script with Dpkg options wrong ?

If you have already faced this  kind of problems, I would be happy to
heard about it.
In case this would not be the normal operation of pam-auth-update,
I would open a bug on the subject.

thanks
-- 
Jean Louis Mas

Back to linux.debian.user | Previous | Next | Find similar | Unroll thread

Thread

bug with pam-auth-update ? Jean-Louis Mas <Jean-Louis.Mas@imag.fr> - 2016-04-08 10:20 +0200

csiph-web