Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
metze
|
|
Even if signing is mandatory.
With NTLMSSP this happens for the session setup:
request1 => BSRSPYL
response1 => BSRSPYL
request2 => BSRSPYL
response2 => <SIGNATURE>
and with krb5:
request1 => BSRSPYL
response1 => <SIGNATURE>
metze
|
|
metze
|
|
the _recv functions
metze
|
|
Guenther
|
|
|
|
Pinched from b53e6387e30010509034835acf88b91b380ff44a by metze.
Andrew Bartlett
(This used to be commit d55602e23e7947462cb402b20b2d354b96aa7ba3)
|
|
We now reuse ignored values for the ntvfs backend private flags.
metze
(This used to be commit 14eda93aeface307e1ffd1ea012d8f236fa78290)
|
|
Also in particular the 'sync' flags (which Samba has traditionally
ignored).
Thanks to Olivier Salamin <olivier.salamin@gmail.com> for pointing out
more flags that needed to be handled.
Andrew Bartlett
(This used to be commit 370bb39cd79fe49efd36a1ceb3e896d386e6d3ce)
|
|
The MS-SMB document explains that some of these options should be
ignored. The test proves it.
/* Must be ignored by the server, per MS-SMB 2.2.8 */
/* Must be ignored by the server, per MS-SMB 2.2.8 */
If we implement HSM in samba4 (likely) we should honour this bit.
/* Don't pull this file off tape in a HSM system */
Andrew Bartlett
(This used to be commit 502739ff90d56d2c9aabe8e224317f6ceb175c17)
|
|
metze
(This used to be commit d235ce673705641e06b4ad5f5679e146b59a19e1)
|
|
metze
(This used to be commit a6aa055097313975299f214d8ebe8d45aa51d10a)
|
|
metze
(This used to be commit 48ccb51caf7976ec07c8a9bfc1afd3076bf4ee22)
|
|
metze
(This used to be commit e1d81388fcabba9a947ed0be9ccae875e2b19135)
|
|
metze
(This used to be commit ec67c61b6a82e4f39a15f37a98ae3fe93bb81316)
|
|
metze
(This used to be commit 5bf136e233e26b4372155f494bae5118ef777a76)
|
|
The recv helper will be called when a response comes
and the recv helper can decide to let the request
on the SMBCLI_REQUEST_RECV when more reponse packets
are expected. It's up to the helper function
to keep a reference to the in buffers, each incoming
response overwrites req->in.
metze
(This used to be commit 6d84af89ba96627abe142ba7080c24ae2421ed6c)
|
|
metze
(This used to be commit a65599cc83a12ec61e5a6ba6ad9628619a0dc8a3)
|
|
(This used to be commit 388f4fde3655146bf57b4c51c59c39f475aa7fe8)
|
|
(This used to be commit f84620324a8cebcd2fd19388d910928ca1ad1334)
|
|
(This used to be commit 4eb49335d5f0319f9aa47ded5215a2977d3336bf)
|
|
library
(This used to be commit 597b38e97b01d2137e6ac96ca07cd56fadb2c09e)
|
|
(This used to be commit 318038d6f670efffa96d8b0db63f46b3752e1cd3)
|
|
(This used to be commit 2633bc749792c224acc73a2e4ca723404331c19c)
|
|
(This used to be commit a7b5689a73adde59de28770aa3949660441291ea)
|
|
(This used to be commit af31030e0b78b6b220740529901ec8d2d9f5a3fe)
|
|
(This used to be commit 198ed9336756f973cebd7cc3df7f51e2c4575205)
|
|
(This used to be commit a7be5ba22e0cf2c61501f5a05e64673f31ba145c)
|
|
(This used to be commit c52fe1fe1c77636d87355d3c4baa66e052fe9008)
|
|
- SMB2 locking is different in several ways from SMB locking. To fix
it properly we will need a new generic mapping structure for
locking, but for now do a best effort mapping
- added locking to gentest_smb2
(This used to be commit ea6d9cf602302adafe0f9d5f5f90a9b26d1ead6f)
|
|
(This used to be commit b7560afd4bab984c0083e9687b69bc42970ad932)
|
|
This protocol feild isn't used by servers (apparently), so we might be
able to get rid of it.
Andrew Bartlett
(This used to be commit 58935acc7c8e97323d5d5979234ef26ef8a100a4)
|
|
the code.
Make sure we pass around the event_context where we need it instead.
All test but a few python ones fail. Jelmer promised to fix them.
(This used to be commit 3045d391626fba169aa26be52174883e18d323e9)
|
|
metze
(This used to be commit 5ffea702c3a1c92a797afab1a3cadf2f2a18729f)
|
|
The approach I have used is as set out in
https://www.securecoding.cert.org/confluence/display/seccode/ARR38-C.+Do+not+add+or+subtract+an+integer+to+a+pointer+if+the+resulting+value+does+not+refer+to+an+element+within+the+array
(This used to be commit 92d5fb531db39be655f0cbd2d75b5f675a0a4cfa)
|
|
This also fixes the alignment from 8 to 4 byte bounderies.
metze
(This used to be commit e0a0d8e36acd735b587cd7870625af52c5dc3431)
|
|
(This used to be commit 9b686c138037f613da15168d0722786e00f023e5)
|
|
(This used to be commit 47ffbbf67435904754469544390b67d34c958343)
|
|
metze
Signed-off-by: Stefan Metzmacher <metze@samba.org>
(This used to be commit bfe773a620640fa46efe008f38144f5452350825)
|
|
But the keep the default to always send it
when the server supports it too.
metze
(This used to be commit 33caaef2e46557525a8ffb79d6dd0db46a079529)
|
|
(This used to be commit a16c9a2129ce92e7e1a613b2badd168e42ead436)
|
|
(This used to be commit f4b31ad76771d674ec85cd155b023eed377e6eb4)
|
|
(This used to be commit 5de88728ac5c567d3711d1ac6862bbdaced84b75)
|
|
(This used to be commit 47d05ecf6fef66c90994f666b8c63e2e7b5a6cd8)
|
|
this.
(This used to be commit 3c9973b695a0b5c30d3a5bfabecf62dd1a25ebc1)
|
|
We now define a separate info level RAW_SFILEINFO_RENAME_INFORMATION_SMB2
and set that level when handling SMB2 packets. This makes the parsers clearer.
(This used to be commit f6cdf3f1177f63d80be757f007eb15380839b4f5)
|
|
We needed a flag in bufinfo to mark packets as SMB2, as it seems that
SMB2 uses a different format for the RenameInformation buffer than SMB
does
Also handle the fact that SMB2 clients give the full path to the
target file in the rename, not a relative path
(This used to be commit 52d7972d95ddc19d22a4187b4d4428a6c3ed32d5)
|