IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
using the pattern in the clilsa code, it didn't fill in the p->binding
structure. This affects nearly all users of dcerpc_pipe_open_smb(), so
the simplest fix is to ensure that dcerpc_pipe_open_smb() initialises
the binding if its not already there.
- re-enable the RAW-ACLS test
(This used to be commit d8875c286d2be49c01703d8fd58bbc1842054bd9)
Stop passing the VM config file path to wintest_2k3_dc.sh on the command line as it is now properly passed through the environment.
Windows tests, including the DC tests found in test_w2k3.sh should work properly with 'make wintest' and a configured VMware environment.
These tests are executed on build-farm host bnhtest.
(This used to be commit 7496a28b4388535a426ca753bc9000670f6e42e1)
I'm only fixing the bug I introduced here,
not the rest of the mess in the pipe handling,
as we don't fill in pipe->binding and pipe->conn->binding_str
consistant...
metze
(This used to be commit cec74f352822a767770e9e00e87a94d0e37d80c9)
generate a random buffer explicit to make valgrind happy
found by valgrind in the build-farm on fort, there are some more places
like this...
metze
(This used to be commit 2654f595cae046924be33a3f8f758a20565156ee)
- use the PFC_CONC_MPX flag for the 3rd connection
- to DsGetNCChanges requests on the 3rd connection with the bind handle
from the 2nd connection to match w2k3
metze
(This used to be commit 5071af332c2c079fd94c577e58ee6e8ccf157ffa)
also make it possible to pass and get the assoc_group_id for
a pipe.
also make it possible to pass the DCERPC_PFC_FLAG_CONC_MPX flag
in bind requests. From the spec it triggers support for
concurrent multiplexing on a single connection.
w2k3 uses the assoc_group_id feature when it becomes a domain controller
of an existing domain. Know the ugly part, with this it's possible to
use a policy handle from one connection on a different one...
typically the DsBind() call is on the 1st connection while DsGetNCChanges()
call using the first connections bind handle are on the 2nd connection.
The second connection also has the DCERPC_PFC_FLAG_CONC_MPX flag attached,
but that doesn't seem to be related to the cross connection handle usage
Can anyone think of a nice way to implement the assoc_group_id stuff in our server?
metze
(This used to be commit 2d8c85397d9027485ed6dbdcca87cc1ec84c7b76)
--option="become dc:smbtorture dc=mydcname"
--option="become dc:do not unjoin=yes"
joins as mydcname and creates mydcname_*.ldb files under lp_private_dir()
metze
(This used to be commit 22bc6d541e9de2dc494cda154d6fabbc3c907da8)
re-provision (as is required for the TEST_LDAP=yes version of make
test).
Andrew Bartlett
(This used to be commit ea4c2ea22fb3975d80130f52edecaf6d1790adde)
- fill in our on bind_info struct correctly
- remember the local and remote DsBindInfo28 struct
- remember the remote bind_buid
w2k3 now tries replicate using DsGetNCChanges() from us,
after the NET-API-BECOME-DC test created the domain controller
and replicated all data.
(But we still give a DCERPC fault in DsGetNCChanges()...)
metze
(This used to be commit 33550c063d4e206fce63fdd99dc93a56995db580)
with this you can join a domain as dc for testing:-)
You still need to setup some dns entries...
and add the ldap/.... servicePrincipalName's
abartlet: it's wrong to include ldap/ in the list of host=, we should change this...
metze
(This used to be commit 12f610d747fe827ed402984fa63680b576ed7b03)
'phantom_root' flag in the search_options control
- Add in support for LDB controls to the js layer
- Test the behaviour
- Implement support for the 'phantom_root' flag in the partitions module
- Make the LDAP server set the 'phantom_root' flag in the search_options control
- This replaces the global_catalog flag passed down as an opaque pointer
- Rework the string-format control parsing function into
ldb_parse_control_strings(), returning errors by ldb_errorstring()
method, rather than with printf to stderr
- Rework some of the ldb_control handling logic
Andrew Bartlett
(This used to be commit 2b3df7f38d7790358dbb4de1b8609bf794a351fb)
Restructure existing tests to work with the recent build farm changes.
Added windows DC testing to 'make wintest'.
Some improvements and generalization to the way errors are handled.
(This used to be commit de9687404e802d7e7629c9d03f496d3c5bd30397)
This patch changes the function name and signature that pidl generate
a call for when dissecting a policy handle to a new, more
PIDL-friendly function.
It also stores the procedure name in a new pinfo-> field so that
helpers that want to know the procedure name can finbd out easily.
The new PIDL helper function for policy handles use this new field and will show
OpenHKU(<...>)
opened in frame X
closed in frame Y
for the policy handle.
(This used to be commit 0c4fb484f0e515eb4055c58cd73ca798a8c46d69)
wintest_2k3_dc.sh is a new script which will run a group of tests against a Windows 2003 DC.
The group of tests to run should be passed in on the command line.
These tests were taken from the source/script/tests/test_win2k3.sh script.
tests_win2k3_dc.sh is a new script intended to be called by 'make wintest_dc' (patch to source/main.mk forthcoming).
This is intended to provide the basis for Windows 2003 DC testing in the build farm.
In order to use these tests, you should have a DC setup as a VM in VMware server.
This process is not automated yet, but can be done by following a few steps:
1. Prepare a Windows 2003 VM in VMware Server by downloading and extracting:
svn://svn.samba.org/home/svn/samba/branches/SOC/bnh/vm_setup.tar.gz
and following the instructions in the README file.
2. Copying the following file onto the filesystem of the VM configured in step 1:
svn://svn.samba.org/home/svn/samba/branches/SOC/bnh/dcpromo_2k3dc_newdomain.answerfile.txt
and use it to promote the VM.
For example: "dcpromo /answer:<path to answerfile>"
3. On the system you are testing from, set the environment variable WINTESTCONF, and SRCDIR.
WINTESTCONF should point to the path of a test_win.conf file modified for your environment.
There's a default copy in source/script/tests/win/test_win.conf.
SRCDIR should point to the base of your Samba 4 source tree.
At that point, you should be able to run wintest_2k3_dc.sh by passing a group of tests at the command line.
For example: source/script/tests/win/wintest_2k3_dc.sh RPC-DRSUAPI
Sorry for the long-winded commit message!
(This used to be commit a0d1c690de2e58eddf5517eb974e09c2bba23605)
Made the restore_snapshot() routine in wintest_functions.sh more robust.
This change would have broken the existing windows tests, if they weren't already broken.
Will fix those once the windows DC tests are committed and working in the build farm.
(This used to be commit 76c6c5b8de58618ac013f5b26a6aafc98e15f57c)
isn't updated by originating changes, and that there's no entry for the local
dsa invocation_id
metze
(This used to be commit a9b757dddc496b705d04ee73f52b7f4f16e972e9)
