Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Pavel Shilovskiy
	<pshilov-0li6OtcxBFHby3iVrkZq2A@public.gmane.org>,
	ronnie sahlberg
	<ronniesahlberg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Thorsten Leemhuis <linux-rCxcAJFjeRkk+I/owrrOrA@public.gmane.org>,
	"linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: RFC: Revert move default dialect from CIFS to to SMB3
Date: Fri, 01 Sep 2017 07:07:43 -0400	[thread overview]
Message-ID: <1504264063.5755.5.camel@redhat.com> (raw)
In-Reply-To: <CAH2r5mv9roEvMX+C-csU=GZFM_HMbqxnHfF11NUp+2yonDVPgA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Thu, 2017-08-31 at 21:42 -0500, Steve French wrote:
> Any thoughts on this patch to add additional warnings for the user -
> logging when using default dialects (or when server returns dialect
> not supported), and noting the default dialect change?
> 
> See https://git.samba.org/?p=sfrench/cifs-2.6.git;a=commit;h=bb86f22eeddbb5879675b55168b8fa8990d74a21
> 

Breaking backward compatability sucks, but I agree that there's no real
alternative here. SMB1 is just not a safe default these days.

> On Thu, Aug 31, 2017 at 7:29 PM, Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > Yes - updating the parsing slightly and printks as suggested makes sense
> > 
> > Some additional warning messages in the userspace helper (adding Jeff
> > Layton), mount.cifs can also help.
> > 

What do you suggest here?

> > I also have an experimental set of patches to allow multi-dialect
> > negotiation with at least three of the acceptable dialects
> > (smb2.1/smb3/smb3.02) which will help, but complicate secure dialect
> > validation ("validate negotiate") but that will have to wait till next
> > release.
> > 

That seems like the best way to fix this. If you fail to negotiate any
dialect, throw a warning then.


> > On Thu, Aug 31, 2017 at 7:12 PM, Linus Torvalds
> > <torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> wrote:
> > > On Thu, Aug 31, 2017 at 2:36 PM, Thorsten Leemhuis <linux-rCxcAJFjeRkk+I/owrrOrA@public.gmane.org> 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"
> > > 
> > > Oh, looking at that version parsing code, I think we also need to fix
> > > that legacy "ver=1" thing (ver without the 's') which now silently
> > > ignores "ver=1" as being the "default", even though it's not.
> > > 
> > > I do *not* believe that "default to version 1" is acceptable.
> > > 
> > >                 Linus
> > 
> > 
> > 
> > --
> > Thanks,
> > 
> > Steve
> 
> 
> 

-- 
Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

  parent reply	other threads:[~2017-09-01 11:07 UTC|newest]

Thread overview: 16+ 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
     [not found] ` <1504213298-27431-1-git-send-email-linux-rCxcAJFjeRkk+I/owrrOrA@public.gmane.org>
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]         ` <CAH2r5msWDXzwbFPtUHCKbqHrEBTsvw5eaTayj5RkdgYCLM5nAQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-01  2:42           ` Steve French
     [not found]             ` <CAH2r5mv9roEvMX+C-csU=GZFM_HMbqxnHfF11NUp+2yonDVPgA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-01  3:06               ` ronnie sahlberg
2017-09-01 11:07               ` Jeff Layton [this message]
2017-09-02 14:25               ` Thorsten Leemhuis
2017-09-01 18:23       ` L. A. Walsh
     [not found]         ` <59A9A59E.6040205-gT3AUAsYRbTYtjvyW6yDsg@public.gmane.org>
2017-09-01 19:45           ` Linus Torvalds
2017-09-02  2:16             ` Steve French
2017-09-02  3:56               ` Linus Torvalds
     [not found]                 ` <CA+55aFwUHLxBhOh7DxtjSSnKX6KBj+k+p=_CzE8i_xgq-LNj0A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-02  5:22                   ` Andrew Bartlett
     [not found]                     ` <1504329770.3249.61.camel-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
2017-09-02 17:09                       ` Linus Torvalds
2017-09-01  0:03   ` RFC: Revert move default dialect from CIFS to to SMB3" L. A. Walsh
     [not found]     ` <59A8A3E2.40804-gT3AUAsYRbTYtjvyW6yDsg@public.gmane.org>
2017-09-01  3:11       ` Andrew Bartlett

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=1504264063.5755.5.camel@redhat.com \
    --to=jlayton-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-rCxcAJFjeRkk+I/owrrOrA@public.gmane.org \
    --cc=pshilov-0li6OtcxBFHby3iVrkZq2A@public.gmane.org \
    --cc=ronniesahlberg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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