Age | Commit message (Collapse) | Author | Files | Lines |
|
first dialect
- allow override of SMB2 port in client code
|
|
don't handle SEC_FLAG_MAXIMUM_ALLOWED
|
|
|
|
|
|
SMB2 returns NOT_SUPPORTED to some more NTCREATE_OPTIONS.
metze
(This used to be commit 3ea08d430370717463ffab44fed9c42db1002d97)
|
|
metze
(This used to be commit fe74faf13dc64eaa58d757de156aedcb24abed1f)
|
|
metze
(This used to be commit 1380fb954a7d9d4b543c4650a060fef9f357af7b)
|
|
metze
(This used to be commit 3f6cbece4a199a42ad6583ea4bd4302629399625)
|
|
To make that work (as a client) with aes128 and aes256 krb5 keys
we need to use gsskrb5_get_subkey().
metze
(This used to be commit 0c6d988f2083067e1ac7b07a492f88cefd3ba906)
|
|
metze
(This used to be commit 8bc12dc77a59e792830d96e84a4e8d1b2c651505)
|
|
metze
(This used to be commit 35ee165b146b9157b0cff49e1139a0cb37d98926)
|
|
Thanks to Metze for spotting this
(This used to be commit e9fd9b821c04d1cb7b574f539dd8169611e662aa)
|
|
(This used to be commit 8e919dcb0826a5b25d037ee6144af5f7cb21f3ae)
|
|
next version)
(This used to be commit 436cb17b869e2d6cc57936ccc5e81680fb992341)
|
|
This doessn't work against Windows yet, and I've submitted a WSPP
request for clarification of the docs to try and find out
why. Meanwhile this is no worse than what we had, as it only gets used
when the server demands signing, and we didn't work then anyway.
(This used to be commit b788096add3586d7277efcd3bf5ca7f3a604cb7a)
|
|
(This used to be commit ddd0bb32510d615c7b943fb4ce4c9c275b98ab89)
|
|
(This used to be commit 5754cc13514a0f5fe4c47ce53521c256c9d96487)
|
|
(This used to be commit a6cc89fffe8c149b540f2125cea57f31331d5460)
|
|
(This used to be commit f5985a0490e4105a9b0208f6b7b19e635db324f9)
|
|
library
(This used to be commit 597b38e97b01d2137e6ac96ca07cd56fadb2c09e)
|
|
(This used to be commit 88a2c7b2f44f160836e477e460812df557204f51)
|
|
row will fail
(This used to be commit 3b811a52fe9a8356337ad149d01a3498c09d900a)
|
|
- go back to 4 byte alignment until I work out the rules that Vista
wants more exactly
- add the zero sized EA handling for SMB2 more generically
(This used to be commit 326b69bc8064cbea357864cecd6bd27b50c57184)
|
|
(This used to be commit af31030e0b78b6b220740529901ec8d2d9f5a3fe)
|
|
(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 d4f41db964ce82c8889017d0f932d60100b3cd32)
|
|
(This used to be commit 6a3b1cd6698faa460c6258bb41b4936e363f4387)
|
|
(This used to be commit 7989ca861dcc700b52be3a47ea5ae8b03fbb9330)
|
|
(This used to be commit 733937e87a1adcc19492ea2bd138e705701901b6)
|
|
(This used to be commit a63f458462d207d215a6e4ef8e480b0c8daedf6a)
|
|
(This used to be commit a6b52119940a900fb0de3864b8bca94e2965cc24)
|
|
middle.
(This used to be commit f4a77b96f9c17d853348b70794026e5b9e384942)
|
|
(This used to be commit c41bd3005f5f0b9cfd3709fc9217b4a401d265b4)
|
|
(This used to be commit 67290e0ad69df2f2fe651249c6550b8e32dd641b)
|
|
(This used to be commit b7560afd4bab984c0083e9687b69bc42970ad932)
|
|
metze
(This used to be commit 58189b87eade62b717c2c17c679e482786bf2098)
|
|
metze
(This used to be commit 7f545dbbf0186fe552e4c49a3f618862cb4771e7)
|
|
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)
|
|
With this smbtorture works against longhorn beta3 again,
hopefully it still works with new versions...
metze
(This used to be commit 874924a85a862e38b7d1a6199276e998cf3697d8)
|
|
(This used to be commit 92856d5054106894b65cd1a1b5119c0facfc4cff)
|
|
(This used to be commit 9b686c138037f613da15168d0722786e00f023e5)
|
|
(This used to be commit 47ffbbf67435904754469544390b67d34c958343)
|
|
(This used to be commit 66d0502228b31533b5d93731128a681992c22eda)
|
|
SMB2. Thanks to Metze for spotting this.
(This used to be commit fbcf3e65b9284e5d1862c98706d7f148a36afe47)
|
|
- Updated getinfo structures and field names
- also updated the protocol revision number handling to reflect
new docs
(This used to be commit 3aaa2e86d94675c6c68d66d75292c3e34bfbc81b)
|
|
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)
|
|
This converts our SMB and SMB2 code to use a common structure "struct
request_bufinfo" for information on the buffer bounds of a packet,
alignment information and string handling. This allows us to use a
common backend for SMB and SMB2 code, while still using all the same
string and blob handling functions.
Up to now we had been passing a NULL req handle into these common
routines from the SMB2 side of the server, which meant that we failed
any operation which did a bounds checked string extraction (such as a
RenameInformation setinfo call, which is what Vista uses for renaming
files)
There is still some more work to be done on this - for example we can
now remove many of the SMB2 specific buffer handling functions that we
had, and use the SMB ones.
(This used to be commit ca6d9be6cb6a403a81b18fa6e9a6a0518d7f0f68)
|