similar to: is sssd *faster* than samba4's builtin winbind?

Dear R-devel: The following code seems to allow one function to permanently modify a calling function. I did not expect this would be allowed (short of more creative gymnastics) and wonder if it is really intended. (I can see other ways to accomplish the intended task of this code [e.g. via match.call instead of substitute below] that do not trigger the problem, but I don't think that is

Every 10 minutes, my samba 4.0.9 (active directory domain controller) is logging messages like these :- 2014-01-07T14:26:09.896260+11:00 gumbo samba[5198]: /usr/sbin/samba_dnsupdate: ; Communication with 127.0.1.1#53 failed: operation canceled 2014-01-07T14:26:09.896281+11:00 gumbo samba[5198]: /usr/sbin/samba_dnsupdate: could not talk to any default name server 2014-01-07T14:26:09.917096+11:00

When I do "getent group", I want to see the group's members enumerated. With nss_ldap they are; with nss_winbind they aren't: root at gumbo:~# getent group mgmt PI\mgmt:*:1040: There *are* members there (partially redacted): root at gumbo:~# ldbsearch -Htdb:///var/lib/samba/private/sam.ldb cn=mgmt member # record 1 dn: CN=mgmt,CN=Users,REDACTED member:

My samba thinks its own groups don't exist. Background: I had a samba3 server operating as a NAS with some desktops joined to the domain. I'm migrating it to samba 4.0.9 as an AD domain. Users can log in and browse their home share -- but the other shares aren't working. They're per-project shares set up to allow that project's group access, and to forcibly make all files

http://bugzilla.mindrot.org/show_bug.cgi?id=117 ------- Additional Comments From fcusack at fcusack.com 2002-04-16 23:27 ------- sshd should definitely not be using 'NOUSER'. The correct thing is to use the username, regardless of whether (pw) exists. I can't understand why you would substitute the value 'NOUSER'. ------- You are receiving this mail because: -------

I have about 40 SCO 5.0.5 servers on which I am installing samba (I've tried 2.0.3 and 2.0.7, I'm having the same trouble with both). For my example, assume the following: NT domain: ORLANDO_ADMIN NT PDC: ORLANDO_PDC NT user: Administrator (I have tried other users as well) samba server: CLASS guest account (on UNIX server): nouser A generic Unix account exists called samba. My goal

Hello all, I have a CentOS 4.2 server that gives me these error messages in my /var/log/secure file, I realise that these are SSH attacks, but where does the extra line "Could not get shadow information for NOUSER" come from? This doesn't make any sense. I have many servers running CentOS 4.2, but don't get this error message on any others. I hate junk in my logs. Is there

Hi ! Sorry to bring back the infamous "NOUSER" in the conversation but I didn't get the workaround on that problem. Firstly, I'm using : - openssh-3.1p1-15 which is the version which comes by default with my Red Hat Linux Advanced Server release 2.1AS. - I'm using PAM, set up to use radius. Please find below the /etc/pam.d/sshd file : #%PAM-1.0 auth

http://bugzilla.mindrot.org/show_bug.cgi?id=117 ------- Additional Comments From djm at mindrot.org 2002-02-15 10:10 ------- > OpenSSH traditionally would not even start PAM, and > now starts it specifying 'NOUSER' as the login name. We have always used NOUSER, the recent patch just makes it consistent between protocols 1 and 2. > The second is to prevent username guessing

this is at the bottom of auth.c. What is it? struct passwd * fakepw(void) { static struct passwd fake; memset(&fake, 0, sizeof(fake)); fake.pw_name = "NOUSER"; fake.pw_passwd = "$2a$06$r3.juUaHZDlIbQaO2dS9FuYxL1W9M81R1Tc92PoSNmzvpEqLkLGrK"; fake.pw_gecos = "NOUSER"; fake.pw_uid = -1; fake.pw_gid = -1; fake.pw_class =

BSD/OS 4.2 comes with OpenSSH 2.1.1p4, patched to support BSDI's authentication library. However, BSDI's patches have several problems: 1. They don't run the approval phase, so they can allow users to login who aren't supposed to be able to. 2. They don't patch configure to automatically detect the BSDI auth system, so they're not ready to use in a general portable

Hi Rowland, Thanks for your response . I will check on this. Even i have tried with commenting xattr_tdb:file = /var/opt/samba/locks/xattr.tdb in smb.conf and am getting same issue . To be more specific whether you're referring ACL as Windows ACL or POSIX ACL or Extended ACL In the below command "-U%" refers to nouser and no group ? . smbclient -L localhost -U% I am able to get

I have the following as the last line of my /etc/fstab file on a computer running CentOS6.4.. UUID=3b550884-8d05-41a5-a205-17b6d7269dd1 /mnt ext3 rw,suid,dev,exec,noauto,nouser,async 0 2 The UUID refers to an ext3 partition of a removable USB drive. If the USB drive is not plugged into the computer the computer will not boot. It seems that this is the incorrect behavior since

This is true with OpenSsh 3.8p1 and OpenSsh 3.9p1. I am running on Sun Solaris servers, both Solaris 8 and Solaris 9. I send all ssh syslog messages to local3 via the sshd_config file. I periodically get in my error logs the line: Oct 4 15:29:36 wintermute sshd[14517]: [ID 800047 local3.error] error: Could not get shadow information for NOUSER I do not think this is interfering with any

Hello list, I am trying to make a very simple samba share with out any authentication which will work inside the lan only and accessible from winxp too. This is debian lenny box and samba is 2:3.2.5-4lenny7 To achieve this I have written smb.conf ( collected from testparm as ) ``````````````````````````````````` Load smb config files from /etc/samba/smb.conf Processing section

Hello, I'm trying to configure the quota-status service, but it seems I'm not successful with my director setup (2.2.9). I activate the quota-status service like this on my director server: $ cat 91-quota-status.conf ## ## Quota-Status configuration. ## # Load Module quota-status and listen on TCP/IP Port for connections. service quota-status { ? executable = quota-status -p postfix ?

I've got weird things happening with winbind authentication - sometimes it works, sometimes it doesn't. Sometimes it works for one username, and not for the other, sometimes it works for both, sometimes neither... I'm a departmental admin trying to authenticate against our central windows domain - so I've no control of the windows side. The client machine is a fresh redhat

Hi! quota-status is not supported in proxy configuration. You should use quota_warning and quota_over_flag scripts instead. Aki On 08.10.2016 03:51, Michael Kliewe wrote: > Hello, > any news on this topic? I tried it again with Dovecot 2.2.25, but it's > still not possible to run the quota-status services on the directors. > They try to access the mailbox of the user, which they

I use dovecot-0.99.11 from RHEL4. dovecot-mysql.conf: === db_host = dbhost db_port = 3306 db = db db_user = dovecot db_passwd = pass default_pass_scheme = PLAIN password_query = SELECT password FROM users WHERE username = '%u' user_query = select maildir AS home,u_id AS uid,g_id AS gid from users WHERE username = '%u' === When I try "telnet localhost 110" and enter

Hi Greg, Really, the first step to install filesystem it with support ACL. It looks at my archive: LABEL=/ / ext3 defaults,acl 1 1 LABEL=/boot /boot ext3 defaults 1 2 LABEL=/data /data ext3 defaults,acl 1 2 none /dev/pts devpts gid=5,mode=620