On Wed, 18 May 2016 16:10:19 -0400, Boruch wrote in message
<20160518201019.GA1448@???>:

> On 2016-05-18 21:27, Arnt Karlsen wrote:
> > On Wed, 18 May 2016 13:05:31 -0400, Boruch wrote in message
> > > Sounds to me like an issue with 'pam', and that you're fix will
> > > be in /etc/pam.d.
> > > ...
> > ....
> > ..thanks, I'll try this next if the pam diagnosis fails.
>
> Glad to be of help. Let us know how it worked out.

..all joy now (except I'm a wee bit delayed getting my tax forms
out the door), I did try whitelist myself but no joy there, so I
went with the nice reicpe in:
484 zcat /usr/share/doc/libpam-abl/NEWS.Debian.gz
485 cat /usr/share/doc/libpam-abl/README.Debian
488 aptitude purge libpam-abl
490 dpkg -P libpam-abl

"The pam-abl's libdb databases (/var/lib/abl) are not removed
automatically when the package is removed. In order to remove it
compeltely use purge: apt-get purge libpam-abl.

If pam_abl tool is not able to read the backend database ( usually after
Berkeley DB update on the host ) just delete the database:
rm -f /var/lib/abl/*
"

..thanks, everyone. :o)

--
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.