On 09.11.2015 19:37, Michael Tremer wrote:
> I wonder if you have tested this on a clean installation. Because of
> the many so-bumps, the new libraries would probably not be used in an
> upgraded system and that won't find us the bugs

Hi Michael,

You're probably right - sorry if I was a bit too fast with pushing this 
update! I'm having a tough time with a lot of work. "So much to do, but 
not much time for it..." ;-)

In in the meantime I ran a few tests, maybe this helps:

1. Installed on testmachine (an old(!) Core 92), no noticeable problems 
during/after reboot:

Deleted old pam-libraries, restarted, no noticeable problems either:

***SNIP***
...
[root(a)ipfiretest ~]# ps ax|grep pam
1527 ? Ss 0:00 /usr/sbin/saslauthd -n 2 -a pam
1528 ? S 0:00 /usr/sbin/saslauthd -n 2 -a pam
2463 pts/0 R+ 0:00 grep pam
...
***SNAP***

Started / stopped / restarted various services without problems.

2. Clean install on testmachine: (Core 96, "Development Build: 
pam/eeb83132-dirty", compiled 15.11.2015, with pam 1.2.1), no 
eye-catching events.

What else could I test?

Best,
Matthias