ClearFoundation Tracker - ClearOS | ||||||||||
View Issue Details | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||||
0007991 | ClearOS | app-samba-directory - Samba Directory | public | 2016-04-05 09:45 | 2018-10-30 18:27 | |||||
Reporter | user2 | |||||||||
Assigned To | ||||||||||
Priority | normal | Severity | major | Reproducibility | have not tried | |||||
Status | closed | Resolution | suspended | |||||||
Platform | OS | OS Version | ||||||||
Product Version | 7.2.0 | |||||||||
Target Version | Fixed in Version | |||||||||
Summary | 0007991: Samba Directory "administrator" uid=0 is problematic | |||||||||
Description | One of the gotchas discussed during the Samba Directory beta was the unusual behavior of the Windows "Administrator" account. When the Samba 4 Directory initializes, the "administrator" account takes on a UID of 0 (?). So running as the "root" user, you see: # id uid=0(administrator) gid=0(root) groups=0(root) Wah? I'm not sure what's going on here, but it seemed to work okay during the early beta. Can we prevent the Samba 4 Directory behavior? Are we missing a step somewhere? Perhaps this: samba-tool user setParameter Administrator --uidNumber=1234 | |||||||||
Steps To Reproduce | ||||||||||
Additional Information | ||||||||||
Tags | No tags attached. | |||||||||
Relationships |
| |||||||||
Attached Files | ||||||||||
Issue History | ||||||||||
Date Modified | Username | Field | Change | |||||||
2016-04-05 09:45 | user2 | New Issue | ||||||||
2016-04-05 09:45 | user2 | Status | new => assigned | |||||||
2016-04-05 09:45 | user2 | Assigned To | => user2 | |||||||
2016-04-05 09:45 | user2 | Issue generated from: 0007711 | ||||||||
2016-04-05 09:45 | user2 | Relationship added | related to 0007711 | |||||||
2018-10-30 18:27 | user2 | Status | assigned => closed | |||||||
2018-10-30 18:27 | user2 | Assigned To | user2 => | |||||||
2018-10-30 18:27 | user2 | Resolution | open => suspended |
There are no notes attached to this issue. |