Hi all,
I've running a CentOS 5 64bit server that hosts VMware Server and uses authentication via Samba/Winbind. The problem is that authentication in the VMware Server web interface does not work because apparently it is a 32bit application and CentOS 5 x86_64 provides only a 64bit version of the pam_winbind.so library. At least that what I conduct from the following message I get in /var/log/security:
Jan 14 18:10:45 ittvm1 vmware-authd[7946]: PAM unable to dlopen(/lib/security/pam_winbind.so)
Jan 14 18:10:45 ittvm1 vmware-authd[7946]: PAM [error: /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory]
Jan 14 18:10:45 ittvm1 vmware-authd[7946]: PAM adding faulty module: /lib/security/pam_winbind.so
And when I look into the filesystem I find a pam_winbind.so in /lib64/security and none in /lib/security. Of course the module is in the samba-common.i386 package, but since it also contains a lot of other tools and utilities I don't want to install it in addition to the 64bit version.
Any advice/hints?
Best regards, __
/homas
--
Thomas Bleier, DI Information Management Austrian Research Centers GmbH - ARC
HG Wien - FN 115980i - ATU14703506 2444 Seibersdorf, Austria
Mobile: +43 (664) 8251279 E-Mail: thomas.bleier@arcs.ac.at mailto:thomas.bleier@arcs.ac.at
Hi all,
in the meantime (thinking helps sometimes J) I found a workaround that worked for me, but I think it's a bug in the distribution (probably from upstream).
The workaround I use is to let vmware authenticate it's users via Kerberos (pam_krb5.so) instead of winbind - by using the AD Domain Controller as a KDC the user does not see any difference.
What I'm surprised is that this works J: the pam_krb5.so comes from the rpm package "pam_krb5", where I find both the i386 and the x86_64 version installed on my system, so I can use it with the VMware server applications. On the other side pam_winbind.so comes from the rpm package "samba-common", where only the x86_64 version of the package is installed and so I'm missing the 32bit version of the library.
So I would say that's a bug - but I'm not sure if it's CentOS or (which I would guess) it's the same in the upstream distribution. Could probably anybody check this? And where can I file a bug report at the upstream vendor J?
Best regards,
__
/homas Bleier
--
Thomas Bleier, DI Information Management Austrian Research Centers GmbH - ARC
HG Wien - FN 115980i - ATU14703506 2444 Seibersdorf, Austria
Mobile: +43 (664) 8251279 E-Mail: thomas.bleier@arcs.ac.at
From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Bleier Thomas Sent: Monday, January 14, 2008 6:14 PM To: CentOS mailing list Subject: [CentOS] winbind - 32bit vs 64bit
Hi all,
I've running a CentOS 5 64bit server that hosts VMware Server and uses authentication via Samba/Winbind. The problem is that authentication in the VMware Server web interface does not work because apparently it is a 32bit application and CentOS 5 x86_64 provides only a 64bit version of the pam_winbind.so library. At least that what I conduct from the following message I get in /var/log/security:
Jan 14 18:10:45 ittvm1 vmware-authd[7946]: PAM unable to dlopen(/lib/security/pam_winbind.so)
Jan 14 18:10:45 ittvm1 vmware-authd[7946]: PAM [error: /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory]
Jan 14 18:10:45 ittvm1 vmware-authd[7946]: PAM adding faulty module: /lib/security/pam_winbind.so
And when I look into the filesystem I find a pam_winbind.so in /lib64/security and none in /lib/security. Of course the module is in the samba-common.i386 package, but since it also contains a lot of other tools and utilities I don't want to install it in addition to the 64bit version.
Any advice/hints?
Best regards, __
/homas
--
Thomas Bleier, DI Information Management Austrian Research Centers GmbH - ARC
HG Wien - FN 115980i - ATU14703506 2444 Seibersdorf, Austria
Mobile: +43 (664) 8251279 E-Mail: thomas.bleier@arcs.ac.at
-
Bleier Thomas