search for: machinex

I run samba-3 as PDC for a small domain with 4 clients. User A should be allowed to login on all client machines, while logins for the privileged user B should be restricted to 2 machines for security reasons. Any ideas how to manage that? Suggestions for further reading would be highly appreciated? Hans Musil

...pam_succeed_if(sshd:auth): error retrieving information about user should_work May 31 08:12:01 happytobehere sshd[12713]: pam_unix(sshd:auth): check pass; user unknown May 31 08:12:01 happytobehere sshd[12713]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=machineX.foo.org May 31 08:12:01 happytobehere sshd[12713]: pam_succeed_if(sshd:auth): error retrieving information about user should_work May 31 08:12:03 happytobehere sshd[12713]: Failed password for invalid user should_work from www.xxx.yyy.zzz port 51602 ssh2 May 31 08:12:06 happytobehere sshd[12716]: R...

Hello All, I'm trying to set up linux ssh/shell authentication on a CentOS_6.2 server running smbd version 3.5.10-114 using winbind/smb/pam. We've done this successfully using the tdb backend but wanted users to get the same UID/GID on every machine. Switched to rid for the backend but users still got a foreign number for UID and their default group was always Domain Users. So I'm

Dear Community, I recently started thinking about how to make a project like CentOS more transparent and open (especially for new contributors). The http://wiki.centos.org/Team page (which Dag created about a year ago) lists about 20 (more or less active) members, divided into core and community contributors. I personally do not like that kind of distinction. Of course there should be something