From: "L. A. Walsh" <linux-cifs@tlinx.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thorsten Leemhuis <linux@leemhuis.info>,
Steve French <smfrench@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>,
Pavel Shilovsky <pshilov@microsoft.com>
Subject: Re: RFC: Revert move default dialect from CIFS to to SMB3
Date: Fri, 01 Sep 2017 11:23:26 -0700 [thread overview]
Message-ID: <59A9A59E.6040205@tlinx.org> (raw)
In-Reply-To: <CA+55aFwUdX3wNYCuWjUTLQGPMCw3peeKeSBfwXb+HuV36OwE+g@mail.gmail.com>
Linus Torvalds wrote:
> On Thu, Aug 31, 2017 at 2:36 PM, Thorsten Leemhuis <linux@leemhuis.info> wrote:
>
>> Lo! To give a bit more background to this (the mail I reply to was the
>> first I sent with git send-email and I missed some details): Maybe I'm
>> over stretching my abilities/position as regression tracker with this
>> RFC for a revert, but I hope it at least triggers a discussion if such a
>> revert should be done or not.
>>
>
> I don't think that a revert is appropriate.
>
> But perhaps just a single printk() or something if the user does *not*
> specify the version explicitly? Just saying something like
>
> We used to default to 1.0, we now default to 3.0, if you want old
> defaults, use "vers=1.0"
>
----
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 do *not* believe that "default to version 1" is acceptable.
>
---
But does it have to jump to 3? I.e. Why not go a more middle
route of 2.1 -- as it is still security-supported by MS. Ideally
MS would find some bug in 2.1 and allow 3.x to be an upgrade to Win7,
but until then...
Linda
next prev parent reply other threads:[~2017-09-01 18:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 21:01 RFC: Revert move default dialect from CIFS to to SMB3" Thorsten Leemhuis
2017-08-31 21:36 ` RFC: Revert move default dialect from CIFS to to SMB3 Thorsten Leemhuis
2017-09-01 0:12 ` Linus Torvalds
2017-09-01 0:29 ` Steve French
[not found] ` <CAH2r5mv9roEvMX+C-csU=GZFM_HMbqxnHfF11NUp+2yonDVPgA@mail.gmail.com>
2017-09-02 14:25 ` Thorsten Leemhuis
2017-09-01 18:23 ` L. A. Walsh [this message]
2017-09-01 19:45 ` Linus Torvalds
2017-09-02 2:16 ` Steve French
2017-09-02 3:56 ` Linus Torvalds
2017-09-02 5:22 ` Andrew Bartlett
2017-09-02 17:09 ` Linus Torvalds
2017-09-01 0:04 ` RFC: Revert move default dialect from CIFS to to SMB3" L. A. Walsh
2017-09-01 0:41 ` Steve French
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59A9A59E.6040205@tlinx.org \
--to=linux-cifs@tlinx.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=pshilov@microsoft.com \
--cc=smfrench@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox