Bug 7173 - Samba server does not strictly check SMB2 open
Summary: Samba server does not strictly check SMB2 open
Status: NEW
Alias: None
Product: Samba 3.6
Classification: Unclassified
Component: SMB2 (show other bugs)
Version: unspecified
Hardware: Other Linux
: P3 normal
Target Milestone: ---
Assignee: Volker Lendecke
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-24 13:46 UTC by Steve French
Modified: 2011-07-30 09:09 UTC (History)
2 users (show)

See Also:

Attachments
mkdir fails (as expected) to win2008r2 (26.88 KB, application/octet-stream)
2010-02-24 13:50 UTC, Steve French 		no flags Details
to current samba 3 (mkdir should fail on SMB2 open) (67.74 KB, application/octet-stream)
2010-02-24 13:50 UTC, Steve French 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steve French 2010-02-24 13:46:46 UTC 
Have capture which shows SMB2 open of a file to Windows 2008 R2 fails with Invalid parameter but same works to Samba 3.  Samba server has more relaxed checks.
Comment 1 Steve French 2010-02-24 13:50:13 UTC 
Created attachment 5417 [details]
mkdir fails (as expected) to win2008r2
Comment 2 Steve French 2010-02-24 13:50:52 UTC 
Created attachment 5418 [details]
to current samba 3 (mkdir should fail on SMB2 open)
Comment 3 Karolin Seeger 2010-06-11 04:24:20 UTC 
Change components
Comment 4 Stefan Metzmacher 2011-07-30 09:09:48 UTC 
Does this still happens with 3.6.0-rc3?

STATUS_INVALID_PARAMETER is strange, I'd expect STATUS_OBJECT_NAME_INVALID
as the name starts with '\'.

[MS-SMB2] 3.3.5.9 Receiving an SMB2 CREATE Request
says:
...
If the file name length is greater than zero and the first character is a separator character, the server MUST fail the request with STATUS_OBJECT_NAME_INVALID.
...