search for: 10500

...+"domain admins" create mask = 0640 directory mask = 0750 oplocks = Yes On my workstation, logged with root user, I do : "mount -t cifs -o user=administrator //filserv/Admins foo" the mount works. I do an 'ls -l foo' : total 4 drwxr-x--- 5 10500 50512 0 ao?t 12 14:32 . drwx------ 5 root root 4096 ao?t 4 09:18 .. drwxr-x--- 4 10500 50512 0 ao?t 12 14:33 Linux drwxr-x--- 6 10500 50512 0 ao?t 7 17:27 Windows Where 10500 is the UID of user administrator and 50512 is the GID of group "Domain Admins". I enter into &...

...machine: root at storiq-111:~# pidstat -p 11694 2 20 Linux 4.4.78-storiq64-opteron (storiq-111) 10/08/2017 _x86_64_ (32 CPU) 16:30:12 UID PID %usr %system %guest %CPU CPU Command 16:30:14 0 11694 0,00 0,00 0,00 0,00 8 smbd 16:30:16 10500 11694 48,00 8,00 0,00 56,00 8 smbd 16:30:18 10500 11694 54,00 13,00 0,00 67,00 8 smbd 16:30:20 10500 11694 54,00 12,00 0,00 66,00 8 smbd 16:30:22 10500 11694 61,50 11,50 0,00 73,00 8 smbd 16:30:24 10500 11694...

...            pam_permit.so     On Begin feb 2018, i disabled an account in the AD. Just checked again and yes its still set to "Account disabled"  Today i noticed the following.    From my SFTP server log.  and this should not be possible. 2018-04-25 07:00:05 [27504][username][1.2.3.4][10500]Start download file '/folder1/file1.csv' 2018-04-25 07:00:05 [27504][username][1.2.3.4][10500]End download file '/folder1/file1.csv' (82 bytes) : 100% 2018-04-25 07:00:05 [27504][username][1.2.3.4][10500]Start download file '/folder1/file1.csv' 2018-04-25 07:00:06 [27504][us...

...riq-111:~# pidstat -p 11694 2 20 > Linux 4.4.78-storiq64-opteron (storiq-111) 10/08/2017 > _x86_64_ (32 CPU) > > 16:30:12 UID PID %usr %system %guest %CPU CPU > Command 16:30:14 0 11694 0,00 0,00 0,00 > 0,00 8 smbd 16:30:16 10500 11694 48,00 8,00 > 0,00 56,00 8 smbd 16:30:18 10500 11694 54,00 > 13,00 0,00 67,00 8 smbd 16:30:20 10500 11694 > 54,00 12,00 0,00 66,00 8 smbd 16:30:22 10500 > 11694 61,50 11,50 0,00 73,00 8 smbd 16:30:24 > 10500...

...:auth): internal module error (retval = > PAM_MAXTRIES(11), user = 'username') > > The above seems to show that pam_krb5, pam_unix and > pam_winbind are rejecting the user > > Apr 25 07:00:04 hostname1 sshd[27490]: Accepted password for > username from 1.2.3.4 port 10500 ssh2 > Apr 25 07:00:04 hostname1 sshd[27490]: > pam_unix(sshd:session): session opened for user username by (uid=0) > Apr 25 07:00:04 hostname1 systemd-logind[25400]: New session > 4873 of user username. > Apr 25 07:00:04 hostname1 systemd: > pam_unix(systemd-user:session): ses...

[I was overlooked on the CC. Hopefully this message does not create a new bug report.] > Prof Brian Ripley wrote: > I would say this was user error (insisting on editing non-existent > rownames), although the argument is documented. You could argue that > there are implicit rownames, but they would be 1, 2 ... not row1, row2 > .... And rownames(mat) is NULL. > > For an

...t; Have you given Administrator a uidNumber attribute ? > > If it is a Unix domain member, are you using a username map in smb.conf > > Rowland It 's on a samb4/cups domain member (not a DC) The administrator user is the one of the domain, not a local user: id administrator uid=10500(administrator) gid=10513(domain users) groups=10513(domain users),10500(administrator),10518(schema admins),10572(denied rodc password replication group),10519(enterprise admins),10520(group policy creator owners),10512(domain admins),70002(BUILTIN+users),70001(BUILTIN+administrators),744000513...

...; SeDiskOperatorPrivilege OR net -S ADserver -U support rpc rights grant 'domain\Administrator' SeDiskOperatorPrivilege I am trying to grant the above privilege because managing samba shares through mmc from remote windows system is failing with: _srvsvc_NetShareSetInfo: uid 10500 doesn't have the SeDiskOperatorPrivilege privilege needed to modify share myshare Uid 10500 is 'domain\Administrator' account I can send the relevant smb.conf and any additional traces I need to capture. Can anyone provide ideas on what could be going wrong? The above featu...

...9;root'. When you do something on Windows as 'Administrator' is done on Unix as 'root'. I would never use 'Administrator' directly on Unix and here is why: I use the 'rid' idmap backend and if I run 'getent passwd administrator', I get: administrator:*:10500:10513::/home/administrator:/bin/bash As you can see 'Administrator' has the ID '10500', which makes it a normal Unix user with no special powers. However, from Windows via Samba, the 'Administrator' ID is set to '0' by the user map and I hope you realise what other...

...dir testdir rowland at devstation:~$ sudo chown Administrator testdir rowland at devstation:~$ ls -ld testdir drwxrwx---+ 2 administrator domain users 4096 Feb 13 11:00 testdir If I then use the '-n' switch to 'ls', I get this: rowland at devstation:~$ ls -nd testdir drwxrwx---+ 2 10500 10513 4096 Feb 13 11:00 testdir Which clearly shows that the numeric ID for Administrator is '10500' and makes 'Administrator' into just another Unix user. What could be happening here is that you are seeing Administrator owning the share on a Windows machine and the user.map is...

...gt; > you have in smb.conf: > > username map = /etc/samba/user.map > > with the corresponding user.map > > !root = TESTING\Administrator TESTING\administrator > > you also posted: > > [root at centos7member ~]# getent passwd administrator > administrator:*:10500:10513:Administrator:/home/administrator:/sbin/bash > > You are mapping Administrator to root, but have also given Administrator a > uidNumber attribute (10500) > > I would suggest that you remove the uidNumber attribute (and any other > rfc2307 attributes) from Administrators AD o...

...Windows as 'Administrator' is done on Unix as > 'root'. > > I would never use 'Administrator' directly on Unix and here is why: > > I use the 'rid' idmap backend and if I run 'getent passwd > administrator', I get: > > administrator:*:10500:10513::/home/administrator:/bin/bash > > As you can see 'Administrator' has the ID '10500', which makes it a > normal Unix user with no special powers. However, from Windows via > Samba, the 'Administrator' ID is set to '0' by the user map and I hope >...

...one on Unix as > > 'root'. > > > > I would never use 'Administrator' directly on Unix and here is why: > > > > I use the 'rid' idmap backend and if I run 'getent passwd > > administrator', I get: > > > > administrator:*:10500:10513::/home/administrator:/bin/bash > > > > As you can see 'Administrator' has the ID '10500', which makes it a > > normal Unix user with no special powers. However, from Windows via > > Samba, the 'Administrator' ID is set to '0' by the user...

...n. I have got a problem that the "username map" entry in smb.conf does not seem to have any effect at all. In the mapping file there is a mapping from Administrator to root. But when I run id Administrator I do not get the mapping to root. The result of the id command looks like: uid=10500(administrator) gid=10513(domain_users) groups=10513(domain_users), 10500(administrator), 10512(domain_admins), 10572(denied_rodc_password_replication_group), 10518(schema_admins),10519(enterprise_admins), 10520(group_policy_creator_owners), 3001(BUILTIN\users),3000(BUILTIN\administrators) and...

...$ sudo chown Administrator testdir > rowland at devstation:~$ ls -ld testdir > drwxrwx---+ 2 administrator domain users 4096 Feb 13 11:00 testdir > > If I then use the '-n' switch to 'ls', I get this: > > rowland at devstation:~$ ls -nd testdir > drwxrwx---+ 2 10500 10513 4096 Feb 13 11:00 testdir > > Which clearly shows that the numeric ID for Administrator is '10500' and > makes 'Administrator' into just another Unix user. > > What could be happening here is that you are seeing Administrator owning > the share on a Windo...

Ben, Thanks for the bug report. I am off two minds about it as discussed below. But as it does indeed create a crash / segfault, I am passing this on to the R bug tracker. A suggested two-line patch is below; I tested the patch against a 'vanilla' 2.6.1 source tree. On 6 December 2007 at 19:32, Ben Goodrich wrote: | -----BEGIN PGP SIGNED MESSAGE----- | Hash: SHA1 | | Package:

...#39;. > > > > > > I would never use 'Administrator' directly on Unix and here is why: > > > > > > I use the 'rid' idmap backend and if I run 'getent passwd > > > administrator', I get: > > > > > > administrator:*:10500:10513::/home/administrator:/bin/bash > > > > > > As you can see 'Administrator' has the ID '10500', which makes it a > > > normal Unix user with no special powers. However, from Windows via > > > Samba, the 'Administrator' ID is set to ...

I would say this was user error (insisting on editing non-existent rownames), although the argument is documented. You could argue that there are implicit rownames, but they would be 1, 2 ... not row1, row2 .... And rownames(mat) is NULL. For an interactive function the best solution seems to be to throw an error when the user asks for the impossible. I'll fix it for 2.7.0: it

...>> >> > -- >> >> > To unsubscribe from this list go to the following URL and read >> >> > the instructions: https://lists.samba.org/mailman/options/samba >> >> >> >> getent passwd Administrator >> >> administrator:*:10500:10513::/home/administrator:/bin/bash >> >> >> >> smb.conf already contains user.map >> >> >> > >> > >> > The fact that 'Administrator' has an ID that isn't '0' means that, >> > to Linux, Administrator is...

...configured or a std template? OK, I missed this before: you have in smb.conf: username map = /etc/samba/user.map with the corresponding user.map !root = TESTING\Administrator TESTING\administrator you also posted: [root at centos7member ~]# getent passwd administrator administrator:*:10500:10513:Administrator:/home/administrator:/sbin/bash You are mapping Administrator to root, but have also given Administrator a uidNumber attribute (10500) I would suggest that you remove the uidNumber attribute (and any other rfc2307 attributes) from Administrators AD object and depend on the m...