search for: lmde5

Displaying 9 results from an estimated 9 matches for "lmde5".

Did you mean: lmde
2023 May 14
1
samba users at boot, the same local and samba user bug has gone
...quot; on a user that exists locally and in the > domain I get the list of groups of both local + domain concatenated as > one long list. > > Would it be viewed as two separate users that would not happen. > > - Kees. > OK, I should have posted that as well: adminuser at lmde5:~$ id unixuser uid=1001(unixuser) gid=1001(unixuser) groups=1001(unixuser),13105(unixuser),10513(domain users),3001(BUILTIN\users) adminuser at lmde5:~$ id SAMDOM\\unixuser uid=13105(unixuser) gid=10513(domain users) groups=10513(domain users),13105(unixuser),3001(BUILTIN\users) Still think th...
2023 May 14
1
samba users at boot, the same local and samba user bug has gone
...>> domain I get the list of groups of both local + domain concatenated >> as one long list. >> >> Would it be viewed as two separate users that would not happen. >> >> - Kees. > >> > > OK, I should have posted that as well: > > adminuser at lmde5:~$ id unixuser > uid=1001(unixuser) gid=1001(unixuser) > groups=1001(unixuser),13105(unixuser),10513(domain > users),3001(BUILTIN\users) > > adminuser at lmde5:~$ id SAMDOM\\unixuser > uid=13105(unixuser) gid=10513(domain users) groups=10513(domain > users),13105(unixuser),3...
2023 May 14
1
samba users at boot, the same local and samba user bug has gone
...both local + domain concatenated >>> as one long list. >>> >>> Would it be viewed as two separate users that would not happen. >>> >>> - Kees. >> >>> >> >> OK, I should have posted that as well: >> >> adminuser at lmde5:~$ id unixuser >> uid=1001(unixuser) gid=1001(unixuser) >> groups=1001(unixuser),13105(unixuser),10513(domain >> users),3001(BUILTIN\users) >> >> adminuser at lmde5:~$ id SAMDOM\\unixuser >> uid=13105(unixuser) gid=10513(domain users) groups=10513(domain >&...
2023 May 14
1
samba users at boot, the same local and samba user bug has gone
...gt;> as one long list. >>>> >>>> Would it be viewed as two separate users that would not happen. >>>> >>>> - Kees. >>> >>>> >>> >>> OK, I should have posted that as well: >>> >>> adminuser at lmde5:~$ id unixuser >>> uid=1001(unixuser) gid=1001(unixuser) >>> groups=1001(unixuser),13105(unixuser),10513(domain >>> users),3001(BUILTIN\users) >>> >>> adminuser at lmde5:~$ id SAMDOM\\unixuser >>> uid=13105(unixuser) gid=10513(domain users) gr...
2023 May 14
2
samba users at boot, the same local and samba user bug has gone
...ba will create SID's 'S-1-2-*' for local users, but they are not true Windows SID's. If you create a local user on a domain joined machine and then create a domain user (on a DC) with the same name and then use getent on the joined machine, you will get this output: adminuser at lmde5:~$ getent passwd unixuser unixuser:x:1001:1001:,,,:/home/unixuser:/bin/bash adminuser at lmde5:~$ getent passwd SAMDOM\\unixuser SAMDOM\unixuser:*:13105:10513::/home/unixuser:/bin/bash You have to use the username in the form 'DOMAIN\\username' to get the domain users output, otherwise yo...
2023 May 14
2
samba users at boot, the same local and samba user bug has gone
...;S-1-2-*' for > local users, but they are not true Windows SID's. > > If you create a local user on a domain joined machine and then create > a domain user (on a DC) with the same name and then use getent on the > joined machine, you will get this output: > adminuser at lmde5:~$ getent passwd unixuser > unixuser:x:1001:1001:,,,:/home/unixuser:/bin/bash > adminuser at lmde5:~$ getent passwd SAMDOM\\unixuser > SAMDOM\unixuser:*:13105:10513::/home/unixuser:/bin/bash > > You have to use the username in the form 'DOMAIN\\username' to get the > doma...
2023 May 14
1
samba users at boot, the same local and samba user bug has gone
...t;> >>>>> Would it be viewed as two separate users that would not happen. >>>>> >>>>> - Kees. >>>> >>>>> >>>> >>>> OK, I should have posted that as well: >>>> >>>> adminuser at lmde5:~$ id unixuser >>>> uid=1001(unixuser) gid=1001(unixuser) >>>> groups=1001(unixuser),13105(unixuser),10513(domain >>>> users),3001(BUILTIN\users) >>>> >>>> adminuser at lmde5:~$ id SAMDOM\\unixuser >>>> uid=13105(unixuser) gi...
2023 May 14
2
samba users at boot, the same local and samba user bug has gone
Hi! We faced another issue with not having samba (ad-dc) users in local /etc/password: this way, we can't easily have services run as users this way, since winbindd is started later than most services are (and it requires working network). Also, user-defined cron @reboot jobs aren't being run, for the same reason: cron is stared before winbindd on most systems. This is quite difficult to
2023 May 15
1
samba users at boot, the same local and samba user bug has gone
...d it be viewed as two separate users that would not happen. >>>>>> >>>>>> - Kees. >>>>> >>>>>> >>>>> >>>>> OK, I should have posted that as well: >>>>> >>>>> adminuser at lmde5:~$ id unixuser >>>>> uid=1001(unixuser) gid=1001(unixuser) >>>>> groups=1001(unixuser),13105(unixuser),10513(domain >>>>> users),3001(BUILTIN\users) >>>>> >>>>> adminuser at lmde5:~$ id SAMDOM\\unixuser >>>>&gt...