After performing the upgrade I can't login via ssh and local password change attempts fail. I can log in locally as root and a normal user. When I do this and try to change passwords this is the result:

[root@tiger]# passwd
Changing password for user root.
passwd: Module is unknown

For each remote ssh login attempt I see these entries in /var/log/secure:

Nov 28 21:33:10 localhost passwd: PAM unable to dlopen(/lib/security/pam_stack.so)
Nov 28 21:33:10 localhost passwd: PAM [error: /lib/security/pam_stack.so: cannot open shared object file: No such file or directory]
Nov 28 21:33:10 localhost passwd: PAM adding faulty module: /lib/security/pam_stack.so

I cannot stress enough that ALL I did was upgrade Fed6 to Fed8 using the DVD from the Fed site. The Fed6 system used yum to regularly update itself, actually a daily cron calling "yum update all" in case thats relevant.

Was there something else I should have done? Should I have actually done the Fed6->Fed7->Fed8 route instead? I see an old entry for this message here:http://www.linuxquestions.org/questi...194/page2.html
but cracklib is present and libxcrypt is unknown to yum. Thanks.

Apparantly it also jhappened when you go from Fc6->Fc7:
http://forums.fedoraforum.org/archiv.../t-159050.html

Does anyone know of whatever package/rpm I could try removing & reinstalling (if that might help) please?

http://www.redhat.com/archives/rhl-d.../msg00050.html

Ok, although it seems like pulling teeth right now I think I'm getting somewhere. Not content with breaking upgrades by renaming all /hda/ refs to /sda/ and not telling future installers about it, it seems my crime of upgrading Fed1 -> Fed2 ... -> Fed6 -> Fed 8 ENTIRELY USING THE UPGRADE CD IN EVERY CASE must now be punished by me not being able to log on because of another deprecation. Don't get me wrong, these are a necessary evils for the system to evolve, but what is not forgivable is the failure of the upgrades to handle it properly!

Ok rant over. I'm still stitting at a bust system.
Must I either source pam_stack.so elsewhere, copy it to the required location and hope that fixes it (living with the deprecation) or is there another task I should perform to get the security system to stop looking for this deprecated file please? Thanks.