Cannot authenticate after upgrade 9.1 to 9.2

[Olivier Nicole]

Thank you Shane,

>> login: in try_dlopen(): /usr/lib/pam_skey.so: Shared object
>> "libskey.so.2" not found login: in openpam_load_module(): no
>> pam_skey.so found
>
> That would indicate that pam_skey.so wants to open libskey.so which
> doesn't exist. I don't see either of those files on 8.4,9.2,10.0 or
> current. The only reference to pam_skey I see in the svn logs was 13
> years ago when updating to openssh 2.3.0.
>
> make delete-old will remove these old libs, maybe you hadn't done that
> in a while, or it just missed one.

I think I missed one... ten years ago.

> I would say you can safely remove /usr/lib/pam_skey.so
> You may want to make sure that it isn't listed in any pam config files
>
> /etc/pam.d/*
> /etc/pam.conf

/etc/pam.conf should not exist anymore, mine was dated back 2004. I
removed it et voila.

BR,

Olivier

> /usr/local/etc/pam.d/*
> /usr/local/etc/pam.conf
>
> Given that you can't authenticate you would need to do this in single
> user mode.
>
>> The account on that server do not use PAM, they are plain old
>> /etc/passwd account, that have been working that way for ages (the
>> machine has been updated since version 4 or 5 I guess).
>
> Actually PAM provides a common authentication framework that is used in
> many places. Standard unix authentication works through pam_unix.so
>
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"