Ralf S.Engelschall
2004-05-18 17:28:11 UTC
Looks like modification of the /etc/pam.conf file on Solaris might be
incorrect.
Putting sshd in debug mode, I get a dlopen failed when trying to login.
Looks like this is because the sshd entries all need to be of the form
/usr/lib/security/$ISA/....
Rather than
/usr/lib/security/...
So that the 64bit libraries will get called (if in 64bit mode). It's
probably minor and hasn't showed up because openpkg compiles everything in
32-bit. Reason I noticed is that my non-openpkg version of OpenSSH which I
compiled 64bit stopped working.
Yes, this is still not correct, I think. But for OpenPKG 1.1 we already haveincorrect.
Putting sshd in debug mode, I get a dlopen failed when trying to login.
Looks like this is because the sshd entries all need to be of the form
/usr/lib/security/$ISA/....
Rather than
/usr/lib/security/...
So that the 64bit libraries will get called (if in 64bit mode). It's
probably minor and hasn't showed up because openpkg compiles everything in
32-bit. Reason I noticed is that my non-openpkg version of OpenSSH which I
compiled 64bit stopped working.
to find a better solution to the PAM situation. We plan to create a "pam"
package which does all the fiddling with /etc/pam.conf and /etc/pam.d/ and
all other modules which require PAM depend on this single "pam" module. This
way we do not have to maintain PAM stuff in every package like "openssh".
Thenway we do not have to maintain PAM stuff in every package like "openssh".
we also should use the $ISA in this new "pam" package.
This is now fixed in OpenPKG-CURRENT (and this way in the forthcomingOpenPKG 1.1) by the introduction of the new "pam" package and by making
PAM support optionally, too.
Ralf S. Engelschall
***@engelschall.com
www.engelschall.com