| Anonymous | Login | 2024-04-19 10:59 MDT |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0007711 | ClearOS | app-samba-directory - Samba Directory | public | 2016-03-14 19:54 | 2016-04-05 09:45 | ||||
| Reporter | user2 | ||||||||
| Assigned To | user2 | ||||||||
| Priority | normal | Severity | major | Reproducibility | have not tried | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 7.2.0 | ||||||||
| Target Version | 7.2.0 Updates | Fixed in Version | 7.2.0 Updates | ||||||
| Summary | 0007711: Samba Directory "administrator" account 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. However, since ClearOS 7.2 (or earlier?), the Samba Directory provisioning seems to fail due to this uid-ness. Instead of running scripts with UID=0/root, the system is using UID=0/administrator. Here's an example of a sudoers error in the /var/log/system log file: Mar 14 11:52:04 localhost engine: exception: error: /usr/clearos/apps/base/libraries/Shell.php (207): administrator is not in the sudoers file. This incident will be reported. Can we prevent the Samba 4 Directory behavior? Are we missing a step somewhere? | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
||||||
|
||||||
 Relationships |
|
Notes |
|
|
(0002821) bchambers (administrator) 2016-03-15 03:27 |
Relevant??? "The problem is that there are two ways to use the windows user 'Administrator' on a Unix machine, you can map 'Administrator' to the Unix user 'root' via a line in smb.conf and a mapping file, this is the easiest way. You can also give the 'Administrator' user a uidNumber, this turns it into a normal Unix user and further setup is required to allow this user to work as the root user, something that in essence gives you two 'root' users and is probably not a good idea. I will think how to edit the page, I do not think giving a uidNumber to 'Administrator' is a good idea and probably the wiki shouldn't show it. Rowland" Ref: https://groups.google.com/forum/#!topic/linux.samba/8y7TdrinYzg [^] |
|
(0002861) dloper (administrator) 2016-03-15 11:42 |
Something to try...map it to root: https://lists.samba.org/archive/samba/2013-May/173658.html [^] |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2016-03-14 19:54 | user2 | New Issue | |
| 2016-03-14 19:58 | user2 | Status | new => acknowledged |
| 2016-03-15 03:27 | bchambers | Note Added: 0002821 | |
| 2016-03-15 11:42 | dloper | Note Added: 0002861 | |
| 2016-03-29 13:31 | user2 | Status | acknowledged => resolved |
| 2016-03-29 13:31 | user2 | Fixed in Version | => 7.2.0 Updates |
| 2016-03-29 13:31 | user2 | Resolution | open => fixed |
| 2016-03-29 13:31 | user2 | Assigned To | => user2 |
| 2016-04-04 18:55 | user2 | Status | resolved => closed |
| 2016-04-05 09:45 | user2 | Issue cloned: 0007991 | |
| 2016-04-05 09:45 | user2 | Relationship added | related to 0007991 |
|
Issue History |