diff options
author | Stefan Metzmacher <metze@samba.org> | 2007-02-23 11:00:20 +0000 |
---|---|---|
committer | Gerald (Jerry) Carter <jerry@samba.org> | 2007-10-10 14:48:48 -0500 |
commit | 1b17d9a587bf3600d449c2481fe1191793479e32 (patch) | |
tree | 56b754f86be6e0facbabc8e41f6fdf1c8232fac9 /BUGS.txt | |
parent | deea9258536b15d5212db4a72b07fe747442b8f1 (diff) | |
download | samba-1b17d9a587bf3600d449c2481fe1191793479e32.tar.gz samba-1b17d9a587bf3600d449c2481fe1191793479e32.tar.bz2 samba-1b17d9a587bf3600d449c2481fe1191793479e32.zip |
r21515: add some more PFC_FLAGS from the DCERPC spec, and fix some names
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)
Diffstat (limited to 'BUGS.txt')
0 files changed, 0 insertions, 0 deletions