Received: by 10.223.185.116 with SMTP id b49csp7849970wrg; Thu, 1 Mar 2018 12:13:59 -0800 (PST) X-Google-Smtp-Source: AG47ELu2XJ5fKYmurY7l66qloe2sq882VTFAuXLFf22uxPFKWmUYA8Fool9ON2PcPkP5TuaxwdQs X-Received: by 10.101.91.133 with SMTP id i5mr2463736pgr.20.1519935239426; Thu, 01 Mar 2018 12:13:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519935239; cv=none; d=google.com; s=arc-20160816; b=Hd0GA9HEEuFAMhdWZ2nfKfoo+hLrBXzNtd/EwTHD58WVhXwUwDwZB9I2o1hlirvGOD VBIVUPUrELpDqfmR1bTWkvBqDkKb19oxwVMOsymbnb7MpoGiil6A9LgpuI2uc83C5WMo 28vkCvE38D5Okp3cIP3yBQfhhl3yS6IGEV/8NumMQ1FsbhxJzc2kg4BxexJqLv0JLShB x4ancksIbpw3ZCGVN2UGyyXVRlWMYlUzbNlM4Lp5LcS58+WeHKrMuO3vVlADDTkIlSsM F9troSijCNPZKyhI2VT3DvFf0QyCIGEIZMxDIanKvcAsu3zLqZOfyt223Pdp30ShCbS6 YmtQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=FXag8wYTWFlGF4d0w2XRH8RY95Zv9r1fsUmYZxXnLj0=; b=UlPIh3+DYtbFs2Z671CXnL4kwnQxpy5VN6UKdvjAx3tPE693RfeC/X10ZIIOoVTyKh c3ZUjeDy91koDZjykrZ/gRaiY4F7CTgsqsYMeFuVv+2KQuhEg58wr0dwC8QEZ/BNC3T/ 9v9LXcgipqNyOla+zzHRDjULsjjTzVWZHg2VpZ19kBBwWdRRNfBfbHZZZXiLirsj7mNU kBKfU6OeIrGyrC56BPKvBnWz8+7j6b9LlvyktPc6ydNAVcWIZUO7O4X6oEKMR9ap1ahg g82ePFNyJhOGm3hXXQRjATWYRvCKyGqu6wE0D0GY+qteXoOCQMqM1QjxzcaMC8GfLaTN Vabw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=pvlaL1le; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q1-v6si3481711plb.764.2018.03.01.12.13.44; Thu, 01 Mar 2018 12:13:59 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=pvlaL1le; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161519AbeCAUMw (ORCPT + 99 others); Thu, 1 Mar 2018 15:12:52 -0500 Received: from mail-pf0-f193.google.com ([209.85.192.193]:41090 "EHLO mail-pf0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161448AbeCAUMt (ORCPT ); Thu, 1 Mar 2018 15:12:49 -0500 Received: by mail-pf0-f193.google.com with SMTP id f80so2943680pfa.8; Thu, 01 Mar 2018 12:12:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=FXag8wYTWFlGF4d0w2XRH8RY95Zv9r1fsUmYZxXnLj0=; b=pvlaL1le1vlVkOZB6SCrXvio2BxBstUYNlll1MlLDXxlgjkgZsieo2pF+c1W4Em3Xr vCCKp/UXtzN2XShe/DNZrkQb5dVxCFuPieiBkJiw9BKgorRVcJWP78if62djHjLt7uLP VlEoU2F6ugePBcFy0kGQEQqpdC7yl5FA0sXYni6cp3oin9onlau0fO+8pmZFIYmhX6Y6 S5q/aPDGx2yYh/QHzEvlLbtj9jjbR3/Tfxc+ss5rbxv7ro3jiOddIrFq+0A/9QStyXMU AgxO7yogJJz2wQeJeKIER2XJe2jV4aDhmA6ROcNgDvZ1k/4Y3qY/KkYu89LJM1tJpTGN jM/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=FXag8wYTWFlGF4d0w2XRH8RY95Zv9r1fsUmYZxXnLj0=; b=TGOGpzYu/rlyV2vPH6WQkfEmxusfRLqFNsR99Y1DYOHJPkbpl7fEW2SZQQdr8ahD6I I/JWyXjwFnzytYfdRLqUt8V/ts8fr3ARxu+C8HRZgbpoAPsC7UC4oE2S2aEGlHzIvrJk YLUYzbusn5wFpTLrHjM+UVE0Vs7NCSnfzs9UXMk7fFE8bnkkO5fnhm1OYNkHspv2twUZ gZ1ns8+vP1zcFqi/8NzPFfE+XKErX9Lj9ktDwi+GIVLQ5wAqVEDZ3d+0Pz8AK+BNKSI9 GD8VyYKqBaAfE09YcKPKwjazo/MH2TDJTaqutym11Ipxd5Vdj2szBV/2WHEq3ayhgfWH YDZw== X-Gm-Message-State: APf1xPCV5SnvPnmacaO0WN1i3ElA5xvf5LtpSfAG42UbKKo4e06f8gAz hA2Pn0+Xwq4hmPZqiqUDNjvziTaQskdknF9TN8M= X-Received: by 10.98.225.2 with SMTP id q2mr3107151pfh.23.1519935168954; Thu, 01 Mar 2018 12:12:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.171.78 with HTTP; Thu, 1 Mar 2018 12:12:28 -0800 (PST) In-Reply-To: References: <20171031095530.520746935@linuxfoundation.org> <20171031095531.633196173@linuxfoundation.org> <97340c9a-0ea2-0d3d-cf26-58c799d76cae@mageia.org> <20171101151803.GB31285@kroah.com> <4ba67095-4075-688f-d3fb-157847aee4d9@csail.mit.edu> <28ffc363-5140-5685-d288-6e3dc07c6369@csail.mit.edu> <20180227085428.GA16879@kroah.com> <20180227124050.GB31888@kroah.com> <6bca5a97-f581-86b8-12ad-77147619d519@csail.mit.edu> From: Steve French Date: Thu, 1 Mar 2018 14:12:28 -0600 Message-ID: Subject: Re: [PATCH 4.13 28/43] SMB3: Validate negotiate request must always be signed To: "Srivatsa S. Bhat" Cc: Greg Kroah-Hartman , Thomas Backlund , =?UTF-8?Q?Aur=C3=A9lien_Aptel?= , LKML , Stable , Ronnie Sahlberg , Pavel Shilovskiy , CIFS Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org So far I haven't been able to reproduce this on the current 4.9 stable tree with vers=3.0 or with default (vers=1.0 for these older kernels). On Tue, Feb 27, 2018 at 11:56 AM, Steve French wrote: > This shouldn't be too hard to figure out if willing to backport a > slightly larger set of fixes to the older stable, but I don't have a > system running 4.9 stable. > > Is this the correct stable tree branch? > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/log/?h=linux-4.9.y > > On Tue, Feb 27, 2018 at 11:45 AM, Srivatsa S. Bhat > wrote: >> On 2/27/18 4:40 AM, Greg Kroah-Hartman wrote: >>> On Tue, Feb 27, 2018 at 01:22:31AM -0800, Srivatsa S. Bhat wrote: >>>> On 2/27/18 12:54 AM, Greg Kroah-Hartman wrote: >>>>> On Mon, Feb 26, 2018 at 07:44:28PM -0800, Srivatsa S. Bhat wrote: >>>>>> On 1/3/18 6:15 PM, Srivatsa S. Bhat wrote: >>>>>>> On 11/1/17 8:18 AM, Greg Kroah-Hartman wrote: >>>>>>>> On Tue, Oct 31, 2017 at 03:02:11PM +0200, Thomas Backlund wrote: >>>>>>>>> Den 31.10.2017 kl. 11:55, skrev Greg Kroah-Hartman: >>>>>>>>>> 4.13-stable review patch. If anyone has any objections, please let me know. >>>>>>>>>> >>>>>>>>>> ------------------ >>>>>>>>>> >>>>>>>>>> From: Steve French >>>>>>>>>> >>>>>>>>>> commit 4587eee04e2ac7ac3ac9fa2bc164fb6e548f99cd upstream. >>>>>>>>>> >>>>>>>>>> According to MS-SMB2 3.2.55 validate_negotiate request must >>>>>>>>>> always be signed. Some Windows can fail the request if you send it unsigned >>>>>>>>>> >>>>>>>>>> See kernel bugzilla bug 197311 >>>>>>>>>> >>>>>>>>>> Acked-by: Ronnie Sahlberg >>>>>>>>>> Signed-off-by: Steve French >>>>>>>>>> Signed-off-by: Greg Kroah-Hartman >>>>>>>>>> >>>>>>>>>> --- >>>>>>>>>> fs/cifs/smb2pdu.c | 3 +++ >>>>>>>>>> 1 file changed, 3 insertions(+) >>>>>>>>>> >>>>>>>>>> --- a/fs/cifs/smb2pdu.c >>>>>>>>>> +++ b/fs/cifs/smb2pdu.c >>>>>>>>>> @@ -1963,6 +1963,9 @@ SMB2_ioctl(const unsigned int xid, struc >>>>>>>>>> } else >>>>>>>>>> iov[0].iov_len = get_rfc1002_length(req) + 4; >>>>>>>>>> + /* validate negotiate request must be signed - see MS-SMB2 3.2.5.5 */ >>>>>>>>>> + if (opcode == FSCTL_VALIDATE_NEGOTIATE_INFO) >>>>>>>>>> + req->hdr.sync_hdr.Flags |= SMB2_FLAGS_SIGNED; >>>>>>>>>> rc = SendReceive2(xid, ses, iov, n_iov, &resp_buftype, flags, &rsp_iov); >>>>>>>>>> cifs_small_buf_release(req); >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> This one needs to be backported to all stable kernels as the commit that >>>>>>>>> introduced the regression: >>>>>>>>> ' >>>>>>>>> 0603c96f3af50e2f9299fa410c224ab1d465e0f9 >>>>>>>>> SMB: Validate negotiate (to protect against downgrade) even if signing off >>>>>>>>> >>>>>>>>> is backported in stable trees as of: 4.9.53, 4.4.90, 3.18.73 >>>>>>>> >>>>>>>> Oh wait, it breaks the builds on older kernels, that's why I didn't >>>>>>>> apply it :) >>>>>>>> >>>>>>>> Can you provide me with a working backport? >>>>>>>> >>>>>>> >>>>>>> Hi Steve, >>>>>>> >>>>>>> Is there a version of this fix available for stable kernels? >>>>>>> >>>>>> >>>>>> Hi Greg, >>>>>> >>>>>> Mounting SMB3 shares continues to fail for me on 4.4.118 and 4.9.84 >>>>>> due to the issues that I have described in detail on this mail thread. >>>>>> >>>>>> Since there is no apparent fix for this bug on stable kernels, could >>>>>> you please consider reverting the original commit that caused this >>>>>> regression? >>>>>> >>>>>> That commit was intended to enhance security, which is probably why it >>>>>> was backported to stable kernels in the first place; but instead it >>>>>> ends up breaking basic functionality itself (mounting). So in the >>>>>> absence of a proper fix, I don't see much of an option but to revert >>>>>> that commit. >>>>>> >>>>>> So, please consider reverting the following: >>>>>> >>>>>> commit 02ef29f9cbb616bf419 "SMB: Validate negotiate (to protect >>>>>> against downgrade) even if signing off" on 4.4.118 >>>>>> >>>>>> commit 0e1b85a41a25ac888fb "SMB: Validate negotiate (to protect >>>>>> against downgrade) even if signing off" on 4.9.84 >>>>>> >>>>>> They correspond to commit 0603c96f3af50e2f9299fa410c224ab1d465e0f9 >>>>>> upstream. Both these patches should revert cleanly. >>>>> >>>>> Do you still have this same problem on 4.14 and 4.15? If so, the issue >>>>> needs to get fixed there, not papered-over by reverting these old >>>>> changes, as you will hit the issue again in the future when you update >>>>> to a newer kernel version. >>>>> >>>> >>>> 4.14 and 4.15 work great! (I had mentioned this is in my original bug >>>> report but forgot to summarize it here, sorry). >>> >>> >>> Then what is the bugfix that should be applied here in order to keep >>> things working with these patches applied? >>> >> >> That would be the one mentioned in the subject line of this thread :) >> However, a working backport of that fix is not available for 4.4 and >> 4.9, hence the trouble. >> >> It looks like we are reconstructing elements of this email thread all >> over again, so let me quickly summarize the status so far: >> >> In 4.14/4.15/mainline, >> - commit 0603c96f3af50e2f9 (SMB: Validate negotiate (to protect against >> downgrade) even if signing off) caused mount regression with SMB v3. >> >> - commit 4587eee04e2ac7ac3 (SMB3: Validate negotiate request must >> always be signed) fixed the issue. >> >> - [ There was a lot of code churn in the CIFS/SMB codebase between >> these two commits in mainline. ] >> >> In this email thread, you backported the fix to stable 4.13. Thomas >> noticed that the problematic commit had also made it to stable series >> such as 4.4 and 4.9, and requested a backport of the fix to those >> trees as well. However, a straight-forward backport of the fix to 4.4 >> and 4.9 breaks the build, so no fix was available for those kernels. >> >> I investigated this and tried to produce a working backport of the fix >> to 4.4 and 4.9, but didn't succeed, despite trying several variations >> as well as suggestions from Aurelien [1][2]. So, given that there is >> still no known fix for the mount regression on 4.4 and 4.9 stable >> series at this point, I decided to request a revert of the problematic >> commit that caused the regression in those kernels. >> >> [1]. https://lkml.org/lkml/2018/1/3/892 >> [2]. https://lkml.org/lkml/2018/1/29/1009 >> >> Regards, >> Srivatsa > > > > -- > Thanks, > > Steve -- Thanks, Steve