[lkml]   [2017]   [Sep]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: RFC: Revert move default dialect from CIFS to to SMB3
On Fri, Sep 1, 2017 at 2:45 PM, Linus Torvalds
<> wrote:
> On Fri, Sep 1, 2017 at 11:23 AM, L. A. Walsh <> wrote:
>> Why be incompatible with the majority of Windows installations?
>> I.e. If you really want to up security from 1.0 (not adverse to that),
>> then why not go to 2.1 as used by Win7? Win7 is still in support
>> from MS -- and they haven't indicated a need to upgrade to 3.x for
>> security reasons. 3.x may have new security features, no argument, but
>> that doesn't mean 2.1, is insecure.
> I'm certainly ok with changing the default to 2.1 if that helps people.
> Is that actually likely to help the people who now see problems with
> the existing 3.0 default?
> I don't know the exact security issue details with cifs, but I _think_
> it was explicitly _only_ smb-1.0, right?

The default was SMB1 (CIFS) and was recently changed to SMB3.
The dialect still can be overridden by specifying "vers=1.0" or "vers=2.1"
etc. on mount.

We just put together a patch to better explain the default changes
(with additional warning messages) as suggested.

SMB3 is significantly better than SMB2.1 (supporting encrypted shares
and sessions for example, and requiring support for "secure negotiate")
and some servers require SMB3 minimum as a result, but it was agreed
at the last test event to eventually support multi-dialect negotiation (for
which SMB2.1 e.g. Windows 7, would be the oldest and least secure
dialect we would support) but in this interim stage we had to pick one,
and the improvements in SMB3 (over SMB2.1) tipped the balance.

In 4.14 we will likely have the ability to more securely do multi-dialect
negotiation, and this issue of SMB2.1 vs. SMB3 will be moot as the
server will choose its most recent dialect.



 \ /
  Last update: 2017-09-02 04:17    [W:0.067 / U:11.436 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site