samba.git/source4/libnet, branch v3-5-test Unnamed repository; edit this file 'description' to name the repository. Fix typo. 2009-10-19T07:49:07+00:00 Karolin Seeger kseeger@samba.org 2009-10-19T07:47:33+00:00 cf0617b40ba2affa4f2135cc44741afa71b967e3 privilage -> privilege Karolin (cherry picked from commit fa08d0b44bf80f6caaeb004a0f27d8346c2820e2) 
privilage -> privilege

Karolin
(cherry picked from commit fa08d0b44bf80f6caaeb004a0f27d8346c2820e2)
s4-libnet: fixed debug formatting 2009-09-28T00:25:31+00:00 Andrew Tridgell tridge@samba.org 2009-09-26T03:47:06+00:00 808585b4fe312aac953f1647a9c7f08b412b915b 






s4-libnet: allow the functional level of becomeDC to be specified
2009-09-24T17:34:53+00:00

Andrew Tridgell
tridge@samba.org

2009-09-23T21:53:28+00:00

a9188f7e10dffc9ad7c30b0b51a45d21b633417d

Use
   ads:functional level = 4
for DS_DC_FUNCTION_2008_R2

See libds/common/flags.h





Use
   ads:functional level = 4
for DS_DC_FUNCTION_2008_R2

See libds/common/flags.h







s4-libnet: avoid a steal with references error
2009-09-24T17:33:36+00:00

Andrew Tridgell
tridge@samba.org

2009-09-24T17:33:36+00:00

3cd0f9e264b0ebb92d5fe8086ee2d146f3e3d02d












s4:libnet_become_dc - bump down the level requested by abartlet
2009-09-21T09:59:07+00:00

Matthias Dieter Wallnöfer
mwallnoefer@yahoo.de

2009-09-21T09:59:07+00:00

32f4afd617944153ce17ea9b4cfe23fb29fcbc68












s4:provision Use code to store domain join in 'net join' as well
2009-09-20T23:29:38+00:00

Andrew Bartlett
abartlet@samba.org

2009-09-20T23:27:24+00:00

bfddb6816f50f629d29e476327a921212fd63a2d

This ensures we only have one codepath to store the secret, and
therefore that we have a single choke point for setting the
saltPrincipal, which we were previously skipping.

Andrew Bartlett





This ensures we only have one codepath to store the secret, and
therefore that we have a single choke point for setting the
saltPrincipal, which we were previously skipping.

Andrew Bartlett







s4-resolve: fixed a crash bug on timeout
2009-09-19T15:23:03+00:00

Andrew Tridgell
tridge@samba.org

2009-09-19T15:23:03+00:00

92786aebf1b8aa17612ebaf5dd0ee8cd4abf9616

We were creating the name resolution context as a child of lp_ctx,
which meant when we gave up on a connection the timer on name
resolution kept running, and when it timed out the callback crashed as
the socket was already removed.





We were creating the name resolution context as a child of lp_ctx,
which meant when we gave up on a connection the timer on name
resolution kept running, and when it timed out the callback crashed as
the socket was already removed.







s4:libnet_become_dc - Fix some uninitialised variables
2009-09-17T16:27:31+00:00

Matthias Dieter Wallnöfer
mwallnoefer@yahoo.de

2009-09-17T16:05:58+00:00

4445cdfad229607d380442118bcf9c5949cb15b8












s4/domain behaviour flags: Fix them up in various locations
2009-09-17T10:40:33+00:00

Matthias Dieter Wallnöfer
mwallnoefer@yahoo.de

2009-09-13T10:37:41+00:00

0c202e403f72ccb1c7081197e83094498fa390b0

Additional notes:
- Bump the level to Windows Server 2008 R2 (we should support always the latest
  version - if we provision ourself)
- In "descriptor.c" the check for the "domainFunctionality" level shouldn't be
  needed: ACL owner groups (not owner user) are supported since Windows 2000
  Server (first AD edition)
  - I took the argument from: http://support.microsoft.com/kb/329194





Additional notes:
- Bump the level to Windows Server 2008 R2 (we should support always the latest
  version - if we provision ourself)
- In "descriptor.c" the check for the "domainFunctionality" level shouldn't be
  needed: ACL owner groups (not owner user) are supported since Windows 2000
  Server (first AD edition)
  - I took the argument from: http://support.microsoft.com/kb/329194







s4-repl: don't do double replication
2009-09-16T01:45:43+00:00

Andrew Tridgell
tridge@samba.org

2009-09-15T21:06:07+00:00

458dda1f15db3db674cf8846b3c08340378a29a8

When we replicate from a remote DC, we need to note the new uSN that
the local changes have resulted in, and modify the uSN that the notify
task uses to determine if it should send a ReplicaSync message back to
the remote DC. Otherwise we end up always triggering a ReplicaSync
every time we replicate from another DC





When we replicate from a remote DC, we need to note the new uSN that
the local changes have resulted in, and modify the uSN that the notify
task uses to determine if it should send a ReplicaSync message back to
the remote DC. Otherwise we end up always triggering a ReplicaSync
every time we replicate from another DC