search for: contence

...T installed > > apart from the uid boundary interval in /etc/pam-d i left the files in > this directory as they were created by authconfig. I did not copy > anything from other systems. > > ldapsearch can read the user information. The user can again login, no > matter of the contence of the ldap's host attribute. > > I feel a bit embarrassed now. but ... does anybody have another idea? > > With kind regards, ulrich > > > > > >

On 05/09/2015 01:24 PM, Jonathan Billings wrote: > Is it normal to have pam_unix and pam_sss twice for each each section? No. See my previous message. I think it's the result of copying portions of SuSE configurations.

when I try to do a: $smbclient '\\smdlinux\tmp' I get this result. Any ideas? load_client_codepage: filename /etc/codepages/codepage.850 does not exist. Added interface ip=10.10.19.1 bcast=10.10.19.255 nmask=255.255.255.0 Session request failed (0,0) with myname=SMDLINUX destname=10.10.19.1 Unspecified error 0x0 Your server software is being unfriendly Thanks in advance, Scott

...iases: files nisplus nscd is NOT installed apart from the uid boundary interval in /etc/pam-d i left the files in this directory as they were created by authconfig. I did not copy anything from other systems. ldapsearch can read the user information. The user can again login, no matter of the contence of the ldap's host attribute. I feel a bit embarrassed now. but ... does anybody have another idea? With kind regards, ulrich

...nstalled > > apart from the uid boundary interval in /etc/pam-d i left the files in > this directory as they were created by authconfig. I did not copy > anything from other systems. > > ldapsearch can read the user information. The user can again login, no > matter of the contence of the ldap's host attribute. > > I feel a bit embarrassed now. but ... does anybody have another idea? > > With kind regards, ulrich > > > > > > _______________________________________________ CentOS mailing list CentOS at centos.org http://lists.centos.or...

...esults ] So, maybe it is a pam problem. Comparing the pam.d of my opensuse boxes with my centos box i see common-* files which are inluced, e.g. in the sshd file. They do not exist in centos. Instead i have there the system-auth where the common files should be combined. Fiddling around with the contence of my opensuse commen-* in my centos box's system-auth i did not get further. I have installed on centos: fprintd-pam-0.5.0-4.0.el7_0.x86_64 pam-1.1.8-12.el7.x86_64 gnome-keyring-pam-3.8.2-10.el7.x86_64 pam_krb5-2.4.8-4.el7.x86_64 Are you sure i do not need nss-pam-ldapd? Googling around i h...

Thanks a lot for the explanation. I have confused some things while crawling through the manuals. Now i have removed the 'ldap' from the /etc/nsswitch.conf. Now it looks like this: passwd: files sss shadow: files sss group: files sss hosts: files dns bootparams: nisplus [NOTFOUND=return] files ethers: files netmasks: files networks: files protocols: files rpc: