bin/85796: pam doesn't work correctly after Upgrade RELENG_4-2005-09-05

[michael.schuh at gmail.com]

>Number:         85796
>Category:       bin
>Synopsis:       pam doesn't work correctly after Upgrade RELENG_4-2005-09-05
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Sep 06 13:50:17 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Michael Schuh
>Release:        FreeBSD 4.11-STABLE i386
>Organization:
my-next-home.de
>Environment:
System: FreeBSD mc.my-next-home.de 4.11-STABLE FreeBSD 4.11-STABLE #17: Mon Sep 5 14:59:16 CEST 2005 root at mc.my-next-home.de:/usr/obj/usr/src/sys/MYGENERIC i386

>Description:
After an typically update at 2005-09-05 (ISO-format) with make update under
/usr/src via cvsup and the following steps:
make buildworld kernel
mergemaster -p
make installworld
mergemaster
<REBOOT>
portupgrade -ar

Pam fails to work correctly. To check if pam works i use nomally 
pamtester (security/pamtester) from ports with an dump service that are not
really connected. Pamtester aborts with signal 10 and core dump. Same behavior is shown if i would use the pam-pgsql and also with saslauthd.

After a check in /usr/lib i can see that the pam-modules and the Libraryobject-archive
was changed, but the libpam.so.1 wasn't changed.
an Installation from new libpam.so.1 by hand, ldconfig and reuild of the required
software doesn't help to getting pam work.
after unpacking and replacing the libs and modules from the backup,
all does work correctly.

>How-To-Repeat:
update an older FreeBSD4 RELENG_4 machine with actually state and use the pamtester with pam-pgsql-module, with steps described above.
>Fix:
see above

>Release-Note:
>Audit-Trail:
>Unformatted: