Software: Apache/2.0.54 (Fedora). PHP/5.0.4 uname -a: Linux mina-info.me 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11 22:57:02 EDT 2006 i686 uid=48(apache) gid=48(apache) groups=48(apache) Safe-mode: OFF (not secure) /usr/share/doc/samba-3.0.23a/htmldocs/Samba3-HOWTO/ drwxr-xr-x |
Viewing file: Select action/file-type: Table of Contents The administration of Windows user, group, and machine accounts in the Samba domain-controlled network necessitates interfacing between the MS Windows networking environment and the UNIX operating system environment. The right (permission) to add machines to the Windows security domain can be assigned (set) to non-administrative users both in Windows NT4 domains and Active Directory domains. The addition of Windows NT4/2kX/XPPro machines to the domain necessitates the creation of a machine account for each machine added. The machine account is a necessity that is used to validate that the machine can be trusted to permit user logons.
Machine accounts are analogous to user accounts, and thus in implementing them on a UNIX machine that is
hosting Samba (i.e., on which Samba is running), it is necessary to create a special type of user account.
Machine accounts differ from normal user accounts in that the account name (login ID) is terminated with a
NoteMachine (computer) accounts are used in the Windows NT OS family to store security credentials for domain member servers and workstations. When the domain member starts up, it goes through a validation process that includes an exchange of credentials with a domain controller. If the domain member fails to authenticate using the credentials known for it by domain controllers, the machine will be refused all access by domain users. The computer account is essential to the way that MS Windows secures authentication.
The creation of UNIX system accounts has traditionally been the sole right of
the system administrator, better known as the
All versions of Samba call system interface scripts that permit CIFS function
calls that are used to manage users, groups, and machine accounts
in the UNIX environment. All versions of Samba up to and including version 3.0.10
required the use of a Windows administrator account that unambiguously maps to
the UNIX
Samba 3.0.11 introduced support for the Windows privilege model. This model
allows certain rights to be assigned to a user or group SID. In order to enable
this feature, enable privileges = yes
must be defined in the Currently, the rights supported in Samba-3 are listed in ???. The remainder of this chapter explains how to manage and use these privileges on Samba servers. Table 15.1. Current Privilege Capabilities
There are two primary means of managing the rights assigned to users and groups on a Samba server. The NT4 User Manager for Domains may be used from any Windows NT4, 2000, or XP Professional domain member client to connect to a Samba domain controller and view/modify the rights assignments. This application, however, appears to have bugs when run on a client running Windows 2000 or later; therefore, Samba provides a command-line utility for performing the necessary administrative actions. The net rpc rights utility in Samba 3.0.11 has three new subcommands:
NoteYou must be connected as a member of the Domain Admins group to be able to grant or revoke privileges assigned to an account. This capability is inherent to the Domain Admins group and is not configurable. There are no default rights and privileges, except the ability for a member of the Domain Admins group to assign them. This means that all administrative rights and privileges (other than the ability to assign them) must be explicitly assigned, even for the Domain Admins group.
By default, no privileges are initially assigned to any account because certain actions will be performed as
root once smbd determines that a user has the necessary rights. For example, when joining a client to a
Windows domain, Access as the root user (UID=0) bypasses all privilege checks. The privileges that have been implemented in Samba-3.0.11 are shown below. It is possible, and likely, that additional privileges may be implemented in later releases of Samba. It is also likely that any privileges currently implemented but not used may be removed from future releases as a housekeeping matter, so it is important that the successful as well as unsuccessful use of these facilities should be reported on the Samba mailing lists.
For reference purposes, a Windows NT4 Primary Domain Controller reports support for the following privileges: SeCreateTokenPrivilege Create a token object SeAssignPrimaryTokenPrivilege Replace a process level token SeLockMemoryPrivilege Lock pages in memory SeIncreaseQuotaPrivilege Increase quotas SeMachineAccountPrivilege Add workstations to domain SeTcbPrivilege Act as part of the operating system SeSecurityPrivilege Manage auditing and security log SeTakeOwnershipPrivilege Take ownership of files or other objects SeLoadDriverPrivilege Load and unload device drivers SeSystemProfilePrivilege Profile system performance SeSystemtimePrivilege Change the system time SeProfileSingleProcessPrivilege Profile single process SeIncreaseBasePriorityPrivilege Increase scheduling priority SeCreatePagefilePrivilege Create a pagefile SeCreatePermanentPrivilege Create permanent shared objects SeBackupPrivilege Back up files and directories SeRestorePrivilege Restore files and directories SeShutdownPrivilege Shut down the system SeDebugPrivilege Debug programs SeAuditPrivilege Generate security audits SeSystemEnvironmentPrivilege Modify firmware environment values SeChangeNotifyPrivilege Bypass traverse checking SeRemoteShutdownPrivilege Force shutdown from a remote system And Windows 200x/XP Domain Controllers and workstations reports to support the following privileges: SeCreateTokenPrivilege Create a token object SeAssignPrimaryTokenPrivilege Replace a process level token SeLockMemoryPrivilege Lock pages in memory SeIncreaseQuotaPrivilege Increase quotas SeMachineAccountPrivilege Add workstations to domain SeTcbPrivilege Act as part of the operating system SeSecurityPrivilege Manage auditing and security log SeTakeOwnershipPrivilege Take ownership of files or other objects SeLoadDriverPrivilege Load and unload device drivers SeSystemProfilePrivilege Profile system performance SeSystemtimePrivilege Change the system time SeProfileSingleProcessPrivilege Profile single process SeIncreaseBasePriorityPrivilege Increase scheduling priority SeCreatePagefilePrivilege Create a pagefile SeCreatePermanentPrivilege Create permanent shared objects SeBackupPrivilege Back up files and directories SeRestorePrivilege Restore files and directories SeShutdownPrivilege Shut down the system SeDebugPrivilege Debug programs SeAuditPrivilege Generate security audits SeSystemEnvironmentPrivilege Modify firmware environment values SeChangeNotifyPrivilege Bypass traverse checking SeRemoteShutdownPrivilege Force shutdown from a remote system SeUndockPrivilege Remove computer from docking station SeSyncAgentPrivilege Synchronize directory service data SeEnableDelegationPrivilege Enable computer and user accounts to be trusted for delegation SeManageVolumePrivilege Perform volume maintenance tasks SeImpersonatePrivilege Impersonate a client after authentication SeCreateGlobalPrivilege Create global objects The Samba Team is implementing only those privileges that are logical and useful in the UNIX/Linux environment. Many of the Windows 200X/XP privileges have no direct equivalence in UNIX. Please note that every Windows NT4 and later server requires a domain Administrator account. Samba versions commencing with 3.0.11 permit Administrative duties to be performed via assigned rights and privileges (see User Rights and Privileges). An account in the server's passdb backend can be set to the well-known RID of the default administrator account. To obtain the domain SID on a Samba domain controller, run the following command:
You may assign the domain administrator RID to an account using the pdbedit command as shown here:
NoteThe RID 500 is the well known standard value of the default Administrator account. It is the RID that confers the rights and privileges that the Administrator account has on a Windows machine or domain. Under UNIX/Linux the equivalent is UID=0 (the root account). Releases of Samba version 3.0.11 and later make it possible to operate without an Administrator account provided equivalent rights and privileges have been established for a Windows user or a Windows group account.
When a Windows NT4 (or later) client joins a domain, the domain global
This is often not the most desirable solution because it means that the user will have administrative
rights and privileges on domain servers also. The See Nested Group Support for an example of how to add domain users and groups to a local group that is on a Windows workstation. The use of the net command permits this to be done from the Samba server.
Another way this can be done is to log onto the Windows workstation as the user
where |
:: Command execute :: | |
--[ c99shell v. 1.0 pre-release build #16 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0034 ]-- |