cifs: fix setting SecurityFlags to true
authorSteve French <stfrench@microsoft.com>
Tue, 9 Jul 2024 23:07:35 +0000 (18:07 -0500)
committerSteve French <stfrench@microsoft.com>
Sat, 13 Jul 2024 14:24:27 +0000 (09:24 -0500)
commitd2346e2836318a227057ed41061114cbebee5d2a
tree72b4a860f47d8c2f6e50c34aa44dd52a1c652bad
parent34afb82a3c67f869267a26f593b6f8fc6bf35905
cifs: fix setting SecurityFlags to true

If you try to set /proc/fs/cifs/SecurityFlags to 1 it
will set them to CIFSSEC_MUST_NTLMV2 which no longer is
relevant (the less secure ones like lanman have been removed
from cifs.ko) and is also missing some flags (like for
signing and encryption) and can even cause mount to fail,
so change this to set it to Kerberos in this case.

Also change the description of the SecurityFlags to remove mention
of flags which are no longer supported.

Cc: stable@vger.kernel.org
Reviewed-by: Shyam Prasad N <sprasad@microsoft.com>
Signed-off-by: Steve French <stfrench@microsoft.com>
Documentation/admin-guide/cifs/usage.rst
fs/smb/client/cifsglob.h