Thx for picking up my query. Results are: 1. cron: in pam_vprompt(): no conversation function (many, many entries - I should have thought to look here first)
2. File: /usr/lib/libpam.so String dump of section '.comment': [ 0] GCC: (NetBSD nb4 20200810) 7.5.0 File: /usr/lib/libpam.so.4 String dump of section '.comment': [ 0] GCC: (NetBSD nb4 20200810) 7.5.0 File: /usr/lib/libpam.so.4.0 String dump of section '.comment': [ 0] GCC: (NetBSD nb2 20150115) 4.8.4 File: /usr/lib/libpam.so.4.1 String dump of section '.comment': [ 0] GCC: (NetBSD nb4 20200810) 7.5.0 3. String dump of section '.comment': [ 0] GCC: (NetBSD nb4 20200810) 7.5.0 4. /usr/lib/security/pam_rootok.so.4: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, for NetBSD 9.2, not stripped 5. -r--r--r-- 1 root wheel 8184 May 12 2021 /usr/lib/security/pam_rootok.so.4 Kind regards, -- Steve Blinkhorn <st...@prd.co.uk> You wrote: > > On Tue, 15 Nov 2022, Steve Blinkhorn wrote: > > > the cron/rsyncd.conf etc. config in place. I checked that everything > > ran normally back in July, but now I find /var/log/cron is full of > > lines like this: > > > > Nov 14 22:02:00 trafalgar cron[3913]: (CRON) pam_authenticate failed > > (System error) > > > > PAM System errors should've been logged. What's the output of these: > > ``` > $ fgrep cron /var/log/messages > $ readelf -p .comment /usr/sbin/cron /usr/lib/libpam.so* > $ readelf -p .comment /usr/lib/security/pam_rootok.so.4 > $ file /usr/lib/security/pam_rootok.so.4 > $ ls -l /usr/lib/security/pam_rootok.so.4 > ``` > > -RVP > >
