projects.samba.org

------------------- BACKGROUND INFO BEGIN -------------------

Rather than become overwhelmed with the tidal wave of information we are getting back from DSGetNCChanges(), I decided to take it one bit at a time.
These notes reference the smbtorture output found here by line number.

What i'm hoping to do here is breakdown as many of the unknown attributes as I can.
I'm starting with the root of dc=smb,dc=test (my domain name). I'm going to try and line up unknown values in my output file with what ldp.exe tells us on the domain controller.
The dc is my pdc(2k3 enterprise edition), and it is running as a mixed-mode domain (freshly loaded snapshot 8).

The first object in the list starts at line 571.

I got these results by running 'bin/smbtorture -W smbtest -U administrator%sn4ppl3sux ncacn_ip_tcp:pdc.smb.test[seal,print] RPC-DSSYNC | less -N' of revision 9723 of my branch.

------- BACKGROUND INFO END -------
------- INTERESTING INFO BEGIN -------

Line 588 represents the beginning of an DRSUAPI_ATTRIBUTE_objectClass object. objectClassId 0xA0043 on line 597 and objectClassId 0xA0042 on line 601 are returned as UNKNOWN_ENUM_VALUE.
objectClassId 0x100000 on line 605 is returned as DRSUAPI_OBJECTCLASS_top. The attribute values returned by ldp.exe for objectClass are top; domain; domainDNS;. This indicates to me
that objectClassId 0xA0043 and 0xA0042 are DRSUAPI_OBJECTCLASS_domain and DRSUAPI_OBJECTCLASS_domainDNS. But which is which? (spoiler: see entry for line 1831).

Line 606 represents the beginning of the next attribute. Line 607 shows that attid value 0x20001 is UNKNOWN_ENUM_VALUE. Line 616 shows that it has one value, a 5 (0x00000005).
ldp.exe shows that an attribute, instanceType has the value 0x5 = ( DS_INSTANCETYPE_IS_NC_HEAD|IT_WRITE );. Given that, i'm going to go with this object being instanceType, unless contiued
exploration shows that to be not so simple. :)

Line 617 - next object, attid : UNKNOWN_ENUM_VALUE (0x20002). Single valued, time : Mon Jul 18 21:41:50 2005 CST. The whenCreated attribute's value in my AD is
7/18/2005 21:41:50 Canada Central Standard Time Canada Central Standard Time; so i'm going to assume that this (attid: 0x20002) is the 'whenCreated' attribute.

Line 628 - is the start of the next object, attid : DRSUAPI_ATTRIBUTE_ntSecurityDescriptor (0x20119). It's really long, and i'm guessing that it's the auditingPolicy: ; that
ldp can't tell me anything about.

Line 1594 - attribute with UNKNOWN_ENUM_VALUE (0x90001). Single valued, Unicode string 'smb'. That lines it up with the AD name: attribute, which also has the value smb in my directory.
So, attid: 0x90001 is the 'name' attribute, or the 'dc' attribute.

Line 1605 - attribute with UNKNOWN_ENUM_VALUE (0x9001A). It's a DATA_BLOB (length=8). This could be the auditingPolicy that ldb says is a binary blob.

Line 1616 - another UNKNOWN_ENUM_VALUE (0x90027). DATA_BLOB (length=8).

Line 1627 - UNKNOWN_ENUM_VALUE (0x9003C). DATA_BLOB (length=8).

Line 1638 - UNKNOWN_ENUM_VALUE (0x9003D). DATA_BLOB (length=8).

Line 1649 - UNKNOWN_ENUM_VALUE (0x90049). DATA_BLOB (length=4).

Line 1660 - UNKNOWN_ENUM_VALUE (0x9004A). DATA_BLOB (length=8).

Line 1671 - UNKNOWN_ENUM_VALUE (0x9004E). DATA_BLOB (length=8).

Line 1682 - UNKNOWN_ENUM_VALUE (0x9004F). DATA_BLOB (length=4).

Line 1693 - UNKNOWN_ENUM_VALUE (0x90051). DATA_BLOB (length=8).

Line 1704 - UNKNOWN_ENUM_VALUE (0x90058). DATA_BLOB (length=4).

Line 1715 - UNKNOWN_ENUM_VALUE (0x9005D). DATA_BLOB (length=4).

Line 1726 - UNKNOWN_ENUM_VALUE (0x9005F). DATA_BLOB (length=4).

Line 1737 - DRSUAPI_ATTRIBUTE_objectSid (0x90092). Unsurprisingly, ldb also tells me that my objectSid: is S-1-5-21-96697697-2244252087-1111806455.

Line 1748 - UNKNOWN_ENUM_VALUE (0x90097). num_values returns 0, values = NULL. The only attribute value ldp.exe tells me that is anything like that is
creationTime: : cannot format time field;

Line 1754 - UNKNOWN_ENUM_VALUE (0x9009B). DATA_BLOB (length=4).

Line 1765 - UNKNOWN_ENUM_VALUE (0x9009E). num_values = 0, values = NULL.

Line 1771 - UNKNOWN_ENUM_VALUE (0x900CA). DATA_BLOB (length=2).

Line 1782 - UNKNOWN_ENUM_VALUE (0x90165). DATA_BLOB (length=4).

Line 1793 - UNKNOWN_ENUM_VALUE (0x90170). DATA_BLOB (length=138).

Line 1793 - UNKNOWN_ENUM_VALUE (0x90170). DATA_BLOB (length=138).

Line 1804 - UNKNOWN_ENUM_VALUE (0x90171). single valued dn_string.
1817 guid : d38ff38a-4c36-4394-a80b-eeb21661964d
1818 sid : S-0-0
1819 dn : 'CN=NTDS Settings,CN=PDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=smb,DC=test'
This appears to match up with the fSMORoleOwner attribute in my AD.

Line 1820 - DRSUAPI_ATTRIBUTE_systemFlags. value = 0x8c000000 (2348810240).

Line 1831 - UNKNOWN_ENUM_VALUE (0x9026A). 11 element array of drsuapi_DsAttributeValueCtrDNString. dn for each element:
'CN=Users,DC=smb,DC=test'
'CN=Computers,DC=smb,DC=test'
'OU=Domain Controllers,DC=smb,DC=test'
'CN=System,DC=smb,DC=test'
'CN=LostAndFound,DC=smb,DC=test'
'CN=Infrastructure,DC=smb,DC=test'
'CN=Deleted Objects,DC=smb,DC=test'
'CN=ForeignSecurityPrincipals,DC=smb,DC=test'
'CN=Program Data,DC=smb,DC=test'
'CN=Microsoft,CN=Program Data,DC=smb,DC=test'
'CN=NTDS Quotas,DC=smb,DC=test'
This indicates to me that attribute id 0x9026A is attribute name wellKnownObjects.
As an interesting side note, it looks like ldb.exe and smbtorture print the order of the elements in an array in opposite order from each other.
If we hypothesize that the order an array is printed is a standard, we can determine the unknown objectClassId's (way, way back to line 588) as follows:
Ldp.exe returned the values in the following order: top; domain; domainDNS;
smbtorture returned the values in the following order: 0xA0043, 0xA0042, 0x10000 (DRSUAPI_OBJECTCLASS_top).
If my hypothesis is correct, which is supported by the prior knowledge that 0x10000 is top, 0xA0042 is DRSUAPI_OBJECTCLASS_domain, and 0xA0043 is DRSUAPI_OBJECTCLASS_domainDNS.
Score one for the scientific method!
This doesn't confirm/prove anything, however. But I think it makes sense. We should be able to get more information to test the theory with from the next object we reach.

Line 1937 - DRSUAPI_ATTRIBUTE_objectCategory (0x9030E). value = 'CN=Domain-DNS,CN=Schema,CN=Configuration,DC=smb,DC=test'

Line 1953 - UNKNOWN_ENUM_VALUE (0x90364). DATA_BLOB (length=4).

Line 1964 - UNKNOWN_ENUM_VALUE (0x9037B). Unicode string, value '[LDAP://CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=smb,DC=test;0]'
That matches the value for the gPLink attribute in my AD. So, attribute name gPLink should match attid 0x9037B.

Line 1975 - UNKNOWN_ENUM_VALUE (0x90583). DATA_BLOB (length=4).

Line 1986 - DRSUAPI_ATTRIBUTE_msDS_Behavior_Version (0x905B3). Value 0.

Line 1997 - UNKNOWN_ENUM_VALUE (0x906FC). DATA_BLOB (length=4).

Line 2008 - UNKNOWN_ENUM_VALUE (0x906FD). DATA_BLOB (length=4).

Line 2019 - UNKNOWN_ENUM_VALUE (0x906FE). DATA_BLOB (length=4).

Line 2032 - 2210 - meta data.

This is the end of the first object.

What did we match that we didn't know before?
DRSUAPI_OBJECTCLASS_domain (0xA0042)
DRSUAPI_OBJECTCLASS_domainDNS (0xA0043)
wellKnownObjects (0x9026A)
fSMORoleOwner (0x90171)
name or dc (0x90001)
whenCreated (0x20002)
instanceType (0x20001)
gPLink (0x9037B)

(I added all of these to source/librpc/idl/drsuapi.idl, except for 0x90001 - yet)

What was returned by ldb that we didn't match?
distinguishedName:
whenChanged:
subRefs:
uSNCreated:
repsFrom:
uSNChanged:
objectGUID:
replUpToDateVector:
creationTime:
forceLogoff:
lockoutDuration:
lockOutObservationWindow:
lockoutThreshold:
maxPwdAge:
minPwdAge:
minPwdLength:
modifiedCountAtLastProm:
nextRid:
pwdProperties:
pwdHistoryLength:
serverState:
uASCompat:
modifiedCount:
auditingPolicy:
nTMixedDomain:
rIDManagerReference:
isCriticalSystemObject:
masteredBy:
ms-DS-MachineAccountQuota:
msDS-PerUserTrustQuota:
msDS-AllUsersTrustQuota:
msDS-PerUserTrustTombstonesQuota:
msDs-masteredBy:
name: or dc:

There are more attributes for this object returned by ldp.exe that we aren't resolving, than there are UNKNOWN_ENUM_VALUE's returned by smbtorture.

Line 2211 - Second object starts.

Line 2220 - dn of this object is 'CN=LostAndFound,DC=smb,DC=test'.

That's enough for now though.

So far what I have come up with is a number of classes that are used to
deal with the "most common parameters" that Samba configuration
file deals with. Now for a server configuration I have distributed those
parameter bulk into approx 20 classes.

a) Basic class :
It covers the Basic parameters in the Server , Fileshare and Printshare
configurations
and includes parameters like

comment, path, netbiosname , workgroup , server string, etc

b) Tuning class:
it covers the methods to fine tune the Share and Server configurations .
includes parameters like

max smbd connections , keepalive, socket options, max open files,
maxconnections , write cache size, strict allocation ,
strict sync , minprint space

c) Browse class:

browseable , OS level , preferred master , local master, browse list , enhanced
browsing

d) Protocol Class:

Protocol , smb ports, max protocol, min protocol , nt pipe support , disable
netbios, time server, nt acl support, client signing , name resolve order
,

e) FilenameHandling Class :

case sensitive, preserve case, short preserve case, mangle case , hide
dot files,
delete veto, hide files, veto files, map system , map hidden , map archive,
mangled map

f) Locking class :

blocking locks , locking , oplocks , posix locking , strict locking ,
share modes , fake oplocks

g) printing class :

printing , cups options, lpq command, lppause command .....
printcap name , load printers , delete printed command , addprinter command
,
max reported print job , printable , printer name ....

h) Logon class :
add user script , delete user script , logon script , logon drive , logon
path , logon home
domain logons , shutdown script

i) WINS class :
dns proxy , wins proxy , wins server, wins support , wins hook

j) LogFile class :
includes parameters related to the log files LDAP class :

k) Security class :
includes parameters that handle the server and share security .

server security

security , auth methods, encrypt passwords , null passwords, password
server, smbpsswd file
username level , unix passwd sync, root dir , guest account , private dir
, username map

share security

force user , force group , inherit permissions , guest only , only user
, writable
username , invalid users, valid users, admin users , read list , security
mask , directory
mask , create mask ......

l) Miscellaneous class :

remaining but frequent parameters ..

follow symlinks , wide links , postexec , root preexec , root postexec
, delete readonly ,
dos file mode , fstyps , volume , dont descend ......

Now based upon these classes there would be three MAIN classes
a) ServerClass
b) FileShareClass
c) PrintShareClass

The Objects Distribution for classes ...

ServerClass (class)
Basic
Security
Tuning
Locking
Protocol
Printing
FilenameHandling
Logon Options
Browse
WINS LDAP
winbind
Miscellaneous

FileShareClass (class)
Basic
Security
Protocol
Tuning
FilenameHandling
Browse
Locking
Miscellaneous

PrintShareClass (class)
Basic
Security
Tuning
Browsing
Miscellaneous
Printing Options

UserAccountsClass (class)

At present I am dealing with the functions for Each of the Main Classes
designed so far ..
What would a test file look like ??

Functions For the Server class

def CommitChanges(self):
def AddShare(self, ShareObject):
def RefreshServer(self):
def ListOptionsInShare(self , shareName):
def PrintServerInfo(self):
def ListShares(self):
def RemoveShare(self, delShareName ):
def SetOptionValuePairInService(self, ServiceName, Option , Value):
def Version(self):
def PrintConfigFile(self):
def TestServerConfiguration(self):
def RevokeUserRight(self):
def AddUser(self):
def RemoveUser(self):
def CreatePath(self):
def CheckIfPathExist(self):
def CommentOptionValuePair(self):
def UncommentOptionValuePair(self):
def SetServerType(self, serverType):

test.py

import sys
from ServerClass import Server

from FileShareClass import FileShare

if _name_ == "_main_":
s = Server("/home/amit/test/smb.conf")
s.Basic.Workgroup(" workgroupnamE ")
s.Basic.NetBIOSname(" my computer ")
s.Security.EncryptPasswords("yes")

s.FilenameHandling.HideDotFiles("yes","comment here")

S.Browse.Browseable("yes")
s.CommitChanges()

s1 = FileShare("mama")
s1.Basic.Path("/home/amit")
s1.Basic.Comment(" comment for the share name")
s1.Security.ReadOnly("yes")
s1.Security.Writable("yes")

s.AddShare(s1)

print "done"

Amit Regmi 2nd August 2005

Classes and Methods implemented so far

filename:Server.py

(class) Server

commitChanges
ListShares,
AddShare,
RemoveShare,
setServerName,
setWorkgroupName,
setOptionValuePairInService,
setServerType,
ListOptionsInShare,
printServerInfo

filename: FileAndPrintService.py

(class) SetSharePermissions

addOptionValuePair,
setGuestOk,
setBrowseable,
setSearchPath

(class) FileService(SetSharePermissions)

setReadOnly,
setWritable,
setCreateMask,
setDirectoryMask

(class) PrintService(SetSharePermissions)

setPrintable,
allowGuestToPrint

filename: Accounts.py

(class) User
setUserPassword

(class) UnixUser(User)
(class WindowsUser(User)
(class) SambaUser(User)

(class) UserAccounts
listUnixUserAccounts
listSambaUserAccounts
checkAccountInSmbPasswd
addUnixAccount
addSambaAccount
delSambaAccount
changeSmbPasswd
enableSMBaccount
disableSMBaccount
addWindowsAccount

Amit Regmi 29th July 2005

Automatic Breakage Emails

An email that automatically emails a committer when something breaks would be nice.

As tridge said:

add a system to the build farm where we email the committers of
the broken patches when a host starts failing.

There is some subtlety to (2). We'd need to use the oldrevs logic to
work out which commits are candidates for having broken the
build. This is bound to generate some false positives, but I think we
can live with those.

Anyone feel up to the challenge of doing this?

Vance

Python framework for samba management:

So far what has been done is the design of several classes which include a smb.conf parser (by Jerry).
I have worked out 2 files
a) make_smb_conf.py
Here we have a Server class and we decide what server we are to implement. Depending on option we generate a smb.conf file from scratch.
b) smb_tools.py
Here we have methods that help us
- send message to machines on the network
- Check the available accounts in the samba database
- check the available unix user accounts
- add/modify/delete the user accounts (samba)
- refreshing the server
Observation is root acess is required to run many of the management tools.
So, I believe superusers are the people who would be most benifited in using the framework for the management of samba.

Amit Regmi

Sorting the Recent Build tables

I just added basic support to sort the table on Recent Builds, but it isn't anywhere near what I'd like.

Ideally, I'd like to see a method you could call that looks like: $table = new Table(columns=>[ qw/Age Revision Tree Platform Host Compiler Status/], sorters=>[ "age", "revision" ]); $table->add_row(util::dhm_time($age), $rev, $tree, $hosts{$host}, $host, $compiler, $status); $table->output();

Vance

Print Migrator support now working in 3.0.20pre2

This was really a lot of work. More so than I anticipated (spanned 4 months). What we got out of it was the \svcctl pipe, the regfio library, write support on the winreg pipe including security checks, more privilege checks, and a talk at the upcoming CIFS Conference. I'll post a link to the slides here once they are done.

Overall the printmig.exe work has spawned many other ideas such as the task scheduler work and the remote smb.conf registry interface.

jerry

My new testing strategy

After the pain of getting printmig.exe to work against Samba, I've decided to just grab every unsupported tool from the resource kit and start poking at Samba. My theory is that the reason these are unsupported tools is that they do really horrible things. And doing really horrible things means using interfaces and rpcs that one would never suspect.

So while usrmgr.exe doesn't really fall in the unsupported category. it does fall into the "poke at the server until everything works" category. There are a few known issues currently, mostly dealing with managing domain trusts. I've already decoded the rpc structures in rpc_lsa.h, but have not implemented the server code to do anything yet.

jerry

First thoughts on implementing the Task Scheduler

After the initial query to the Samba ml, I did some more research about how the task schedule actually works. It's actually much different than I expected. I guess since the scheduler icon was controlled by winreg queries, I thought the jobs would be stored in the registry as well. The registry paths are used to detect the presence of the task scheduling agent on the remote host. The actual jobs are simply stored as files.

So I think this might map onto cron directories pretty well. For example, it I run a job as jerry, then the job script would be stored in ~jerry/cron and a crontab entry would be made in /var/spool/cron/jerry. The interface with crontab needs a little more thought. The other detail is to figure out the file format used to present the job properties dialog to Windows. This is probably already decoded somewhere (similar to *lnk files or something).

Jonathan Johnson sent me some more information:

"FYI/FWIW, on my Windows XP machine, the jobs in the local task scheduler are binary files located in the hidden folder %SYSTEMROOT%\Tasks\ with a filename extension of .job.

This folder is one of those "special" folders that Windows Explorer displays differently. You can't copy files into or out of this folder using Explorer, nor can you view any files other than .job files. To copy into, out of, or list the contents of this folder, you're pretty much stuck with a command shell.

To display the properties of a scheduled task, the library mstask.dll is used. Some of the relevant registry keys (an incomplete list) used are:

HKEY_CLASSES_ROOT\.job
HKEY_CLASSES_ROOT\JobObject (Note, there are several other similarly named keys)
HKEY_CLASSES_ROOT\CLSID\{148BD520-A2AB-11CE-B11F-00AA00530503}
HKEY_CLASSES_ROOT\CLSID\{148BD52A-A2AB-11CE-B11F-00AA00530503}

Also, you may find the command line interface to the task scheduler, schtasks.exe, useful. Documentation can be found here."

jerry

Registry futures in Samba 3.0:

I posted a few links to some ideas for making better use of the Registry API eariler today.

jerry