Age | Commit message (Collapse) | Author | Files | Lines |
|
checksum over the remaining bytes
metze
(This used to be commit c9fe6a867c7e23a60e0f9200b04c31e48ccc11a2)
|
|
I wonder what the first 4 bytes are, but the last 16 bytes of the 20 bytes
are the rid crypted hash. The lmhash and the history fields are not verified
yet. But I get the administrators nthash in plain.
metze
(This used to be commit 7726d4a0272b29a4eade26c9ae3d929df50897da)
|
|
(This used to be commit 025597a3593d9dede93180d284beda256caf9483)
|
|
- merge ctdb_get_num_nodes() from bzr tree
(This used to be commit 3df7527aedeba7ce2f4a6ca2d3b7167f58c6b68a)
|
|
Andrew Bartlett
(This used to be commit 9e15a51579157405b2013b9b948d279fefd0eda6)
|
|
(This used to be commit 84c15158b986ef9e82f46d6c01d5cbf04300cda5)
|
|
* Add tests for wireshark dissector generator
* Add tests for the header code
* Some cleanups
* Fix handling of elements without [in] or [out]
(This used to be commit 1aecba7100685ed291ea13b0ae47fb0cf9e6a6c8)
|
|
successful!!!!!!!!!!!!!!!!!!!!!!!!!!
we now support the session depended password attribute encryption
used in DsGetNCChanges()
the static encryption (something like sam_rid_crypt() is assumed for some attributes
and the format of the attribute values isn't known yet, but some contain
some unicode strings...
metze
(This used to be commit daee739ebba38e54fbdbd7e53d16fd30bc0dd54e)
|
|
I was wondering why I got allways 4 times the same decrypted buffer...
metze
(This used to be commit ba168479d5c5710de4252d9b8970ab41b7979411)
|
|
to solve the drsuapi password encryption automaticly.
metze
(This used to be commit 7b331b95bf43384e571ecc88ac827f46acd8c20c)
|
|
metze
(This used to be commit 65a55c8fdecbc212ba2fc2a01c580f30dcc7b54a)
|
|
nthash
values for each drsuapi connection in RPC-DSSYNC
metze
(This used to be commit df74c4a88108bd4387d9be4f64619c46c23493e6)
|
|
metze
(This used to be commit 29c44957a0ea16af3e5e3717d2cb0c9180d394c2)
|
|
requests.
(This used to be commit 6a2ba01f155266add71319c1dbc3442eb0c2c751)
|
|
should now work on a real cluster, and not just a localhost simulator
(This used to be commit f05072ad74fb08fd906bc500c5e89930bcc3387f)
|
|
advantage of the ctdb messaging layer for their own data
(This used to be commit b288ba05e5dc2aa5c8cd26eaee1c41b12e4996da)
|
|
handling messages to remote nodes. Implemented dummy functions in the
'local' cluster backend for the messaging hooks, and modified the
messaging layer to check if the destination is remote and redirect
messages via the cluster layer
(This used to be commit 4474552e8fb73efebef32ad8480d7fe9a1e379ef)
|
|
* Pidl will now warn when trying to use pointers as integers in expressions.
* "subcontext()" is now marked as deprecated. The alternatives,
transmit_as() / represent_as() should be available soon.
* More tests.
* Remove some unused code in smbtorture.
(This used to be commit 37c0da541e3962164d5af3e3c9560803a733f3b7)
|
|
across the connections
(This used to be commit 01ef699981f3bcbbbdd4a47d9b85324aec783451)
|
|
a SMBexit
(This used to be commit 753a85eff6a19af2c7b0884f705e9f66b5f605fe)
|
|
a nested ntvfs call. The req structure can go away while processing a
ntvfs request
(This used to be commit f62b3c505f71f37a86a76d152d643926e19eb148)
|
|
codes for "Invalid argument". This change should help track that down
(This used to be commit 608aac7804754fed1c68b847676d7a71a586e4bb)
|
|
event context is created. This allows the LOCAL-EVENT test to pass on
systems with have libaio but not the necessary kernel patches
(This used to be commit 2ff8abf0022824e6ae93019ee1b3391e651a8ee7)
|
|
return. Having a lowercase macro that returns from a function is
probably a bad idea - it looks too much like a C function but doesn't
behave like one.
(This used to be commit e680656419f00fd8b4ddb996fd247bada0f0a51d)
|
|
please test patches, even if they look trivial!
(This used to be commit 8134a628f06f0df2ee94612854e0fb3e2efc2eb8)
|
|
- changed the setup array in nttrans to be a uint8 array, instead of a
uint16 array. This makes it clearer that it is the job of the caller
to do any byte swapping within that data
(This used to be commit fa3c9b29ae1c7c6a9bc97484cc386aeec9b5d266)
|
|
Trivial patch from "Lunar Child <luch@etersoft.ru>"
(This used to be commit 1b75a9ff2d7f91f13fbdfd136b40eca14867bf6f)
|
|
Please check!
For code symmetry reasons, trans2 might also see this fix, but this is left to
the interested reader :-)
Volker
(This used to be commit f2d364ebe69fc5d624e456cc7d941071811a5567)
|
|
Andrew Bartlett
(This used to be commit c3977b4bae1e1b5e4ff4a64c7146534536685e91)
|
|
(This used to be commit 38b688fd15a9103e5ef5c86e01b594169d6b6b9c)
|
|
Fix the join code to know that the ldb layer handles the keytab update.
Andrew Bartlett
(This used to be commit d3fbc089f4161ae71b21077d50130fdabd8b2d77)
|
|
matching va_end() for each va_copy(). This doesn't matter for most
architectures, but there could be some obscure ones where it does
matter.
some of this should be ported to Samba3
(This used to be commit 21eb316473486cb6b73bb3ff9c5f3a44ecd57e4a)
|
|
complex once we have code for changing the number of nodes)
- fixed a ctdb/tcp bug in the handling of multiple packets waiting on
a socket
(This used to be commit faf9a1146cb5f33228a11e01b66cb3cbe18bd05d)
|
|
(This used to be commit 2d6e082e813e18dcd43bc8d9a8f445f77e0a8452)
|
|
If this happens:
- two sockets are readable, and select/epoll/aio returns both of
them
- read event on socket1 is called
- inside that read event an event_loop_once is called, this returns that
socket2 is readable
- read event on socket2 is called
- event_loop_once returns
- top level event handler then calls read event on socket2 (as it
still has that listed as readable)
- read handler for socket2 returns zero byte read, which is
interpreted as end of file
- socket is incorrectly closed
this happened with ctdb, but it could happen anywhere (just
rarely). The fix is trivial - ensure we break out of the event loop
when we have been called recursively.
(This used to be commit e042002bb5ee8974220e1ade56b64389571f75a6)
|
|
metze
(This used to be commit 1f8a037ac4f592d29f7d66e1f924efe1c5d8c2b0)
|
|
(This used to be commit 3f41a4b014a47b3c751066f5d1bef7f76f4be831)
|
|
locks retry immediately when another blocking lock is removed.
(This used to be commit 169920a5341392e84d5b5fb5f39c2b9d5243bb3b)
|
|
early byte range lock retries (ie. PENDING locks in brlock)
(This used to be commit 09237e3acf524f7e772acce2e652ef30b8ba4d65)
|
|
them as a hook on ldb modify, via a module.
This should allow the secrets.ldb to be edited by the admin, and to
have things update in the on-disk keytab just as an in-memory keytab
would.
This isn't really a dsdb plugin, but I don't have any other good ideas
about where to put it.
Andrew Bartlett
(This used to be commit 6ce557a1aff4754d2622be8f1c6695d9ee788d54)
|
|
(This used to be commit 966c30ca591c410a4a229396c7919fe8f98bd066)
|
|
acceptable.
In Samba3 with inotify we have the problem that the MODIFIED action is sent
second. I think this could also happen in Samba4, depending on the order when
the different sockets (unix domain dgram / inotify) are looked at by the
events system.
This patch accepts the NEW/OLD/MODIFIED entries in any order.
Comments welcome!
Volker
(This used to be commit 72a7771b757c3aca637eb632abebab60bdd2da9f)
|
|
Volker
(This used to be commit c9886ce63b8cc085e0032ad2f6193c547336856d)
|
|
(This used to be commit 3548b1f683a7f5ccc6563de7e099d3a5a86ed39c)
|
|
metze
(This used to be commit dfbdb958419a041c1aff039810f7e9cb4320ec2c)
|
|
HKEY_LOCAL_MACHINE\System\CurrentControlset\Services\WINS\Parameters\Randomize1CList
nbtd:wins_randomize1Clist=yes
nbtd:wins_randomize1Clist_mask=255.255.0.0
metze
(This used to be commit eee635ab4d7ae8ffd8962b3d4518a7e6b5a90f97)
|
|
metze
(This used to be commit 1c942b7d8ffb97b70f17fd901033f54771274b96)
|
|
current code in Samba 3 is already generated using this pidl patch.
(This used to be commit 30a06273d28fb59c6f20154f97c67f4c0a63dee9)
|
|
metze
(This used to be commit e788709835fa13b512fbf38951c9d0ca9bc3df18)
|
|
Andrew Bartlett
(This used to be commit 1c466c6d6f02bf76f7f68e7dcd3d9a4c2a63179a)
|