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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
- improve verifiying a replica with a remote wins server
we now take the ownership of replica records that doesn't match
the answer from the wins owner and make the record tombstone.
this hopefully causes the original wins owner to propagate its
new record, so that it will be replicated back to us
metze
(This used to be commit 49199477f225f3d22b3c70bb4626b92ed096f310)
I would sugguest to run 'make test && make valgrind' before each commit
at this stage...
metze
(This used to be commit b7a0a778cc77f294aac589416b05dc676696d11e)
if the addresses and their owners are idetical to the old record
and we're the owner of the old record then we should just gnore the replica
metze
(This used to be commit e4f823ef038eeb74a8a6de05207f2f9aae7262a1)
after a new partner connects, try to find the partner struct on a per call
basis if it's not present on the connection yet
add some more useful debug messages
metze
(This used to be commit e57158e216e3564faa337288734d9efb30ab838d)
release notes. I will answer some questions and clarify some points
in the next commit.
Andrew Bartlett
(This used to be commit d01c4dd84895efdde6043b63dd377fe441366094)
out proto headers.
The reason this is done in this way is that the attribute must be on
the prototype, not the actual function defintion. Hence the macros
which expand to nothing in the C file, but expand to an __attribute__
in the prototype header.
Andrew Bartlett
(This used to be commit a88933668f908a398bb0d8bc7dc39c96cee40de6)
don't use the arguments, but you must connect as the right type
anyway.
Andrew Bartlett
(This used to be commit f50186e9306714b25ae8f92eff9a3e95ad706274)
our winsserver and don't defend our local name against
our own register packets...
this won gave quite confusing logmessages...
metze
(This used to be commit 31ce24d7b1d2945c45c4f5d6376d5041df8b6982)
This updates the module to handle both SID allocation and nextRid
updating while importing users. (As imported users already have a
SID, so don't go via the allocation step). We also ensure that SIDs
in the database are unquie at create time.
Furthermore, at allocation time, we double-check the SID isn't already
in use, and that we don't create a foriegnSecurityPrincipal for a
'local' sid.
Also create random samAccountName entries for users without one (we
were setting $000000-000000000000).
We may want to seperate the uniqueness code from the rest of samldb,
and into a module with the objectguid code, which needs similar
checks. These checks also need to apply to modification, or those
modifications denied outright.
Also update part of the testsuite to validate this.
Andrew Bartlett
(This used to be commit 7a9c8eee4bea88f5f0bb7c62f701476384b7dc84)
This should give better behaviour in SWAT.
Fix authentication as Samba, rather than System, users in SWAT.
Andrew Bartlett
(This used to be commit 498d72c4ad4d57d10f43ca58830d6ee8292a55f4)
- also w2k doesn't work correct with max_attrs = 0, so we should use
a high number, with this I'm getting the same results from w2k and w2k3
metze
(This used to be commit ce9f086c3c1a65bf1b4c843ec44e8817d9361182)
