Age | Commit message (Collapse) | Author | Files | Lines |
|
metze
(from samba4wins tree 74232901d1e7ea9ebcb3bd8d584dda36fac37223)
|
|
metze
(from samba4wins tree 8eb30add7c95672a85b4084b4a3dbfa78db820c4)
|
|
metze
(from samba4wins tree 7a1d4fac9d77440c2c463bfdb2a5671e4817cfdf)
|
|
metze
(from samba4wins tree b411e60e1536668e11bc5d8eaa389071b25077bf)
|
|
metze
(from samba4wins tree 405cbb74b7191e744178894a5e0ac4abcac2a4fe)
|
|
If the client gets a WACK response, the server
sends a timeout to the client. Possible
values are between 9 and 105 seconds.
Because w2k3 servers have a bug and always return
a value of 5 seconds, we need a workarround.
Always using a fixed value of 30 seconds is bad
as we could timeout to early.
Now we use the value from the server if it's in the
valid range and otherwise we use the upper limit
of the valid range (105s).
metze
(from samba4wins tree 40ef7739f4141598a6392c203e4a2d52d972fe06)
|
|
metze
(from samba4wins tree 24eb7577414c8584b97f43c850d738d3dbb30777)
|
|
metze
(from samba4wins tree 7862deca8555f960a5ef65e6315ce94af5023a2a)
|
|
metze
(from samba4wins tree de7225658493006c19d139ac77ac1b1ffab01d25)
|
|
metze
(from samba4wins tree 5e101475d5ed62060c991ea71c943e76b862aeef)
|
|
This fixes the following bug:
While we reply with a WACK response to a client.
Instead of waiting for the final reply some
windows client just resends the request using
the same name_trn_id in the nbt_name_packet.
We handled this as a new request and send a
WACK response (and the challenges) again.
Then the first request gets its final success
response, but the when we try to send the success
for the "second" request we notice that
the record was changed in between and we return
an error.
Windows 2003 (and I assume all other versions as well)
detect the packet is just a resent of a currently pending
request and ignores it.
So we now keep a list of all pending WINS name register
requests which result in a WACK response. On each incoming
name register request we search through the list to find
duplicate requests and ignore them. In theory we should
do that for all requests, but name register requests
are the only requests we response async and only
if we have to go via the WACK code path.
metze
(from samba4wins tree 382e7d384b70d03e9f81c7bb353afaed288d80f0)
|
|
metze
(from samba4wins tree e99531aae325e4443fcb917a75dfe4a86b892583)
|
|
metze
(partly from samba4wins tree 447e7f9532131117e896712db9def321c96718eb)
|
|
This reverts commit ee7c2170a79f1ca9e2ad1a209d342d8fd287ec8d.
A much more correct fix will come soon.
(40ef7739f4141598a6392c203e4a2d52d972fe06 from the samba4wins tree)
metze
|
|
each time)
This makes the code more clear.
metze
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The user session key is also available in rpccli->auth->user_session_key
Guenther, please check!
Thanks,
Volker
|
|
|
|
This streamlines setting up a multi-step async request a bit
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also move the transport switch to this routine
|
|
|
|
|
|
|
|
Type-casting does not the right thing if used the way it used to be. The
function arguments have not been uint32_t's, but the type cast made the calling
routine believe so. Not good...
The assignment xxx=account_policy_temp does however type-convert properly,
potentially cutting off the top-bits.
|
|
|
|
|
|
This eliminates a warning in pidl generated code, while preserving
cross-platform idl compatibility.
|
|
- Most of the time, we can determine from the file system we're connecting to
whether it supports case sensitivity. In those cases, we now set the
internal case sensitivity flag automatically. For those cases where the
request to retrieve file system attributes fails, we'll use the
user-specified option value.
Derrell
|
|
|
|
- Since the revamp of libsmbclient, there has still been an external
declaration for smbc_urlencode and smbc_urldecode in libsmbclient.h, yet
those functions were renamed and made private. The two choices were to
remove the function names from libsmbclient.h or to make them public
again. The reported requested that they be public. This commit makes it so.
Derrell
|
|
*** THIS COMMIT CAUSES A CHANGE OF DEFAULT BEHAVIOR IN libsmbclient!!! ***
- libsmbclient now calls cli_set_case_sensitive() for a new CLI. By default,
it requests case-sensitive, but the old behavior of case-insensitive can be
requested with smbc_setOptionCaseSensitive(context, False);
The change of behavior is considered a bug fix, as it was previously
possible to accidentally overwrite a file that had the same case-insensitive
name but a different case-sensitive name as a previously-existing file,
while creating a new file.
Derrell
|