aboutsummaryrefslogtreecommitdiffstats
path: root/fs/cifs/smb2pdu.c
diff options
context:
space:
mode:
authorJeff Layton <jlayton@redhat.com>2013-05-26 07:01:02 -0400
committerSteve French <smfrench@gmail.com>2013-06-26 17:31:55 -0500
commit52dfb446dbc1915e1df89f8ea9cae1fee7ab3d5e (patch)
tree69ab965c02081ef4a2ac82e3958a724e4ac6baa5 /fs/cifs/smb2pdu.c
parentWhen server doesn't provide SecurityBuffer on SMB2Negotiate pick default (diff)
downloadlinux-dev-52dfb446dbc1915e1df89f8ea9cae1fee7ab3d5e.tar.xz
linux-dev-52dfb446dbc1915e1df89f8ea9cae1fee7ab3d5e.zip
cifs: try to handle the MUST SecurityFlags sanely
The cifs.ko SecurityFlags interface wins my award for worst-designed interface ever, but we're sort of stuck with it since it's documented and people do use it (even if it doesn't work correctly). Case in point -- you can specify multiple sets of "MUST" flags. It makes absolutely no sense, but you can do it. What should the effect be in such a case? No one knows or seems to have considered this so far, so let's define it now. If you try to specify multiple MUST flags, clear any other MAY or MUST bits except for the ones that involve signing. Signed-off-by: Jeff Layton <jlayton@redhat.com> Reviewed-by: Pavel Shilovsky <piastry@etersoft.ru> Signed-off-by: Steve French <smfrench@gmail.com>
Diffstat (limited to 'fs/cifs/smb2pdu.c')
0 files changed, 0 insertions, 0 deletions