Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp2729314pxb; Mon, 31 Jan 2022 03:04:58 -0800 (PST) X-Google-Smtp-Source: ABdhPJw3znyK8B6U+m5XjILyce83E+s7OsmpwV6TB+EUecYmdujMQwI5Huvb0weXdyhFeJrGRZD7 X-Received: by 2002:a17:902:da81:: with SMTP id j1mr20918233plx.14.1643627098558; Mon, 31 Jan 2022 03:04:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643627098; cv=none; d=google.com; s=arc-20160816; b=B9X0/kcF80fYQwF3X2yRyPc5+zAyP0aq653YY/dZYwkg7W4gSsl4VM0QW3Ta4XNu+k LcYca0Rwox8PBxMYFQM2d0ii0jxFpumTBj0sECkCmjtSCJxuudDgokQCByv8b6HzhBxd PqOYGc+GStRuBO6mN1lEm2GQmfJBZft+BvV6T6177wa6YqmsTlPz7e34Sm6Z8gp0ZmWO JvBNZJFfoHwSsYRBkCmz9e3lIDoUtuBfHW2d/nohGFRXml70Wf7Vr/X70okqFGO1mtpb 4c/Xj3I3Czotd51U1SxluxLCHAcEANh0bCqSB4nPaDm8PjsdUDzAjikDOaVlOKwEwhUh uTiQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=gT9SInkkMwHDdS/o+TmNDLEffI0M2Tk/s675iCqlZek=; b=ji7epp4NCeoSxQH/GznQIAwnfW3MuJk5l+3I3zrL3DvHRY1jO3JPXXEd1hiwuEINYP cCIumG9FVKAeZS/fp0SYZNcUiswKLoFh+OwIKN8ysxfD51EYvctntREY2Y2dMEg7sV+K 23di7OMOOiJ68rX+hVgqVQCrHiPmsLv6IIh3a4kZPfesYr0MKxzCjqRw2htq+nNBQnxq +TnTbopjSx1d3fIimVmFknKySktHrT+Qzc7hYFONEuhChpY4dkopwBNf9KnILEeiltKC ku5nik/Ejfr39ocdrO2N/wQxVzk4xtE61vfREljxsDtgSiRRxFt/xfB8+BEt6LfwZJN+ oo2g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=YPIdONdo; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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. [23.128.96.18]) by mx.google.com with ESMTP id b67si8697975pga.458.2022.01.31.03.04.48; Mon, 31 Jan 2022 03:04:58 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=YPIdONdo; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S245025AbiA1Nus (ORCPT + 99 others); Fri, 28 Jan 2022 08:50:48 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34168 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243502AbiA1Nur (ORCPT ); Fri, 28 Jan 2022 08:50:47 -0500 Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 282EBC061714; Fri, 28 Jan 2022 05:50:47 -0800 (PST) Received: by mail-yb1-xb2d.google.com with SMTP id k17so18628233ybk.6; Fri, 28 Jan 2022 05:50:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gT9SInkkMwHDdS/o+TmNDLEffI0M2Tk/s675iCqlZek=; b=YPIdONdoZg8MPE+7BhlEvuGFlqPxTzPXwKeF/HyUK97158V6MrxT8AHpTOJAvDV8K/ H7EugRXfDypqWr94IAOlUh0EWnoa+XbefqYbFHATzRrA9beo8c8OhBx58XpTDdGY8Mzv WRERccwDsbzrZOKm8vWARwW+5iiP4s3agkJbUQw7Ryz9uPQXDNpZDE2A2b+QyX55Q1T9 QIVTLa1i27QNiHE4D850NjSSTCxJp5NwmNav9hdluxltzCfw/8+W2qQZ0Zd1NHYm3Swp Ay2L5HYNUtoKxVXHIVCP4Y8FFZRLpLULHns7JiT++PG740pF+W3ukCYXSmJ2K7zL8WqM OoRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gT9SInkkMwHDdS/o+TmNDLEffI0M2Tk/s675iCqlZek=; b=A1wxHmfAAJaVey0yCBQ95fSOEtPTyih8OJFgQtvmjSCHW/GgSbVLmKeZpopl+uEY/+ wZLaaNxjnc3SxQ7scZ4olPPQ7Q6aWs2xMYf39rtnE5SlG/x5yRE5c8U+mFly/UU+RahX S9KjhKDzy4emaQCUzfQPqXmvcrTQGQp8AwT8h8WDsZ3XrrvovpOAXCK9KklwTK53mRft 9sTn57lvF1af5oSiRCKK4G57iti4tMXvd1JpW7xrWdCWjxFwUsPzClf/KiaXeXmEaoXc zgG//hgyXEt+7TpeGg3Rl1OfaZeblBBtF+JqeUU3Vl+qjfYmk0EdrMAf9DKCsdkKGX9C 5cEQ== X-Gm-Message-State: AOAM531rNY11uABI3o+4El8SkAKoUQKLX7iegoWOcjAVKk5UUX0FhxeD FO62U0McV88GWmSxDyuf8wTZWfl9/DxORMfd8PI= X-Received: by 2002:a25:2ac3:: with SMTP id q186mr13076468ybq.272.1643377846206; Fri, 28 Jan 2022 05:50:46 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: ronnie sahlberg Date: Fri, 28 Jan 2022 23:50:34 +1000 Message-ID: Subject: Re: Possible regression: unable to mount CIFS 1.0 shares from older machines since 76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c To: Thorsten Leemhuis Cc: Davyd McColl , Steve French , CIFS , LKML Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 28, 2022 at 11:30 PM Thorsten Leemhuis wrote: > > Hi, this is your Linux kernel regression tracker speaking. > > Top-posting for once, to make this easy accessible to everyone. > > Davyd, Ronnie, and/or Steve: What the status here? It seems after some > productive debugging back and forth it seems everyone forgot about this. > Or was progress made somewhere and I just missed it? I tried but can not find a system old enough to reproduce. Remember, this is an authentication mechanism that Microsoft begged people to stop using and migrate away from over 20 years ago. Win2k works just fine, as does samba3.0. I have no idea if Samba 2.0 works with current cifs.ko but then again I seriously doubt you can even get samba 2.0 to even compile on a modern machine as so many APIs have changed or just gone away since the late 90s. I tried, but there is just so much time you can spend on something that was declared obsolete 20 years ago. > > Ciao, Thorsten > > #regzbot poke > > > On 12.01.22 06:49, Davyd McColl wrote: > > Hi Ronnie > > > > The regular fstab line for this mount is: > > > > //mede8er/mede8er /mnt/mede8er-smb cifs > > noauto,guest,users,uid=daf,gid=daf,iocharset=utf8,vers=1.0,nobrl,sec=none > > 0 0 > > > > Altering the end of the options from "sec=none" to > > "username=guest,sec=ntlmssp" or "guest,sec=ntlmssp" results in failure > > to mount > > (tested on my patched kernel, which still supports the original fstab > > line), with dmesg containing: > > > > [45753.525219] CIFS: VFS: Use of the less secure dialect vers=1.0 is > > not recommended unless required for acc > > ess to very old servers > > [45753.525222] CIFS: Attempting to mount \\mede8er\mede8er > > [45756.861351] CIFS: VFS: Unable to select appropriate authentication method! > > [45756.861361] CIFS: VFS: \\mede8er Send error in SessSetup = -22 > > [45756.861395] CIFS: VFS: cifs_mount failed w/return code = -22 > > > > There is no way that I know of to set up users for smb auth on this > > device - it only supports guest connections. > > > > -d > > > > > > On Wed, 12 Jan 2022 at 04:32, ronnie sahlberg wrote: > >> > >> Thanks for the network traces. > >> > >> In the traces, both win11 and linux are not using even NTLM but the > >> even older "share password" authentication mode where you specify a > >> password for the share in the TreeConnect command. > >> That is something I think we should not support at all. > >> > >> What is the exact mount command line you use? > >> Can you try mounting the share using a username and ntlmssp ? > >> I.e. username=your-user,sec=ntlmssp on the mount command > >> > >> regards > >> ronnie sahlberg > >> > >> On Wed, Jan 12, 2022 at 6:57 AM Davyd McColl wrote: > >>> > >>> Hi Steve > >>> > >>> As requested, wireshark captures to the device in question, as well as > >>> the fstab entry I have for the device: > >>> - win11, browsing with explorer > >>> - win11, net use > >>> - unpatched linux 5.16.0 attempt to mount > >>> - patched linux 5.16.0 successful mount > >>> - fstab entry - note that I have to specify samba version 1.0 as the > >>> default has changed and the mount fails otherwise. Explicitly > >>> specifying 2.0 errors and suggests that I should select a different > >>> version. > >>> > >>> -d > >>> > >>> On Tue, 11 Jan 2022 at 00:13, Steve French wrote: > >>>> > >>>> I would be surprised if Windows 11 still negotiates (with default > >>>> registry settings) SMB1 much less NTLMv1 in SMB1, but I have not tried > >>>> Windows 11 with an NTLMv1 only server (they are hard to find - I may > >>>> have an original NT4 and an NT3.5 CD somewhere - might be possible to > >>>> install a VM with NT3.5 but that is really really old and not sure I > >>>> can find those CDs). > >>>> > >>>> Is it possible to send me the wireshark trace (or other network trace) > >>>> of the failing mount from Linux and also the one with the succeeding > >>>> NET USE from Windows 11 to the same server? > >>>> > >>>> Hopefully it is something unrelated to NTLMv1, there has been a LOT of > >>>> pushback across the world, across products in making sure no one uses > >>>> SMB1 anymore. See e.g. > >>>> https://techcommunity.microsoft.com/t5/storage-at-microsoft/stop-using-smb1/ba-p/425858 > >>>> and https://twitter.com/nerdpyle/status/776900804712148993 > >>>> > >>>> On Mon, Jan 10, 2022 at 2:30 PM Davyd McColl wrote: > >>>>> > >>>>> I don't understand. I tracked down the exact commit where the issue > >>>>> occurs with a 2 hour git bisect. This was after first confirming that > >>>>> my older 5.14 kernel did not display the symptoms. I can still connect > >>>>> to the share via windows 11 explorer. I don't know what else I need to > >>>>> do here to show where the issue was introduced? > >>>>> > >>>>> Apologies for bouncing mails - literally no email client I have seems > >>>>> to be capable of plaintext emails, so every time I forget, I have to > >>>>> find a browser with the gmail web interface to reply. > >>>>> > >>>>> -d > >>>>> > >>>>> On Mon, 10 Jan 2022 at 19:31, Steve French wrote: > >>>>>> > >>>>>> I want to make sure that we don't have an unrelated regression > >>>>>> involved here since NTLMv2 replaced NTLMv1 over 20 years ago (googling > >>>>>> this e.g. I see "NTLMv2, introduced in Windows NT 4.0 SP4 and natively > >>>>>> supported in Windows 2000") and should be the default for Windows > >>>>>> NT4, Windows 2000 etc. as well as any version of Samba from the last > >>>>>> 15 years+. I have significant concerns with adding mechanisms that > >>>>>> were asked to be disabled ~19 years ago e.g. see > >>>>>> https://support.microsoft.com/en-us/topic/security-guidance-for-ntlmv1-and-lm-network-authentication-da2168b6-4a31-0088-fb03-f081acde6e73 > >>>>>> due to security concerns. > >>>>>> > >>>>>> Can we double check that there are not other issues involved in your example? > >>>>>> > >>>>>> The concerns about NTLMv1 security concerns (and why it should never > >>>>>> be used) are very persuasive e.g. many articles like > >>>>>> https://miriamxyra.com/2017/11/08/stop-using-lan-manager-and-ntlmv1/ > >>>>>> > >>>>>> On Mon, Jan 10, 2022 at 7:48 AM Davyd McColl wrote: > >>>>>>> > >>>>>>> Good day > >>>>>>> > >>>>>>> I'm following advice from the thread at > >>>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=215375 as to how to report > >>>>>>> this, so please bear with me and redirect me as necessary. > >>>>>>> > >>>>>>> Since commit 76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c, I'm unable to > >>>>>>> mount a CIFS 1.0 share ( from a media player: mede8er med600x3d, which > >>>>>>> runs some older linux). Apparently I'm not the only one, according to > >>>>>>> that thread, though the other affected party there is windows-based. > >>>>>>> > >>>>>>> I first logged this in the Gentoo bugtracker > >>>>>>> (https://bugs.gentoo.org/821895) and a reversion patch is available > >>>>>>> there for the time being. > >>>>>>> > >>>>>>> I understand that some of the encryption methods upon which the > >>>>>>> original feature relied are to be removed and, as such, the ability to > >>>>>>> mount these older shares was removed. This is sure to affect anyone > >>>>>>> running older Windows virtual machines (or older, internally-visible > >>>>>>> windows hosts) in addition to anyone attempting to connect to shares > >>>>>>> from esoteric devices like mine. > >>>>>>> > >>>>>>> Whilst I understand the desire to clean up code and remove dead > >>>>>>> branches, I'd really appreciate it if this particular feature remains > >>>>>>> available either by kernel configuration (which suits me fine, but is > >>>>>>> likely to be a hassle for anyone running a binary distribution) or via > >>>>>>> boot parameters. In the mean-time, I'm updating my own sync software > >>>>>>> to support this older device because if I can't sync media to the > >>>>>>> player, the device is not very useful to me. > >>>>>>> > >>>>>>> Thanks > >>>>>>> -d > >>>>>> > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> Thanks, > >>>>>> > >>>>>> Steve > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > >>>>> If you say that getting the money is the most important thing > >>>>> You will spend your life completely wasting your time > >>>>> You will be doing things you don't like doing > >>>>> In order to go on living > >>>>> That is, to go on doing things you don't like doing > >>>>> > >>>>> Which is stupid. > >>>>> > >>>>> - Alan Watts > >>>>> https://www.youtube.com/watch?v=-gXTZM_uPMY > >>>>> > >>>>> Quidquid latine dictum sit, altum sonatur. > >>>> > >>>> > >>>> > >>>> -- > >>>> Thanks, > >>>> > >>>> Steve > >>> > >>> > >>> > >>> -- > >>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > >>> If you say that getting the money is the most important thing > >>> You will spend your life completely wasting your time > >>> You will be doing things you don't like doing > >>> In order to go on living > >>> That is, to go on doing things you don't like doing > >>> > >>> Which is stupid. > >>> > >>> - Alan Watts > >>> https://www.youtube.com/watch?v=-gXTZM_uPMY > >>> > >>> Quidquid latine dictum sit, altum sonatur. > > > > > > >