linux-kernel - Re: [2.6 patch] remove smbfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 30 Jan 2008 19:30:55 -0600
From:	"Steve French" <smfrench@...il.com>
To:	"Jeff Layton" <jlayton@...hat.com>
Cc:	"Adrian Bunk" <bunk@...nel.org>,
	"Guenter Kukkukk" <linux@...kukk.com>,
	samba-technical@...ts.samba.org, linux-kernel@...r.kernel.org,
	sfrench@...ba.org
Subject: Re: [2.6 patch] remove smbfs

On Jan 30, 2008 7:13 PM, Jeff Layton <jlayton@...hat.com> wrote:
> On Thu, 31 Jan 2008 02:47:17 +0200
> > > > > > In addition, cifs cannot completely replace smbfs atm.
> > > > > > Even todays sold NAS-boxes (often running anchient
> > > > > > samba-2.x.x) work only with smbfs on the client side.
I am not convinced that this (mounting to older servers) would be a
problem with the proper mount options but it is more intuitive for
smbfs for some of the lanman servers.   I do want to make sure that we
don't make it too easy to mount with insecure lanman (ie due to
downgrade attacks) without the user at least doing that (specify weak
lanman security explicitly).  Today the user has to explicitly specify
sec=lanman which is confusing but at least makes explicit the weaker
security.

There are four common issues with mounting to these very old servers:
1) remembering to mount specifying lanman security (sec=lanman)
2) remembering to specify the netbios name of the server on mount
(which is often not be the same as its tcp name) - we can make this
easier in mount.cifs though
3) some missing function (mostly relating to converting unix time to
DOS time for set time functions, although the other way around works)
4) working around various server bugs (a surprising number of these)

> > > > > It would be ideal if someone were to report these problems as
> > > > > bugs. I remember some of those in the past, but haven't heard
> > > > > of any cases of that sort of thing for some time. When I have,
> > > > > Steve has generally been very good about tracking down the
> > > > > cause and fixing it.
> > > >
> > > > More exactly, one of the main advantages of removing redundant
> > > > code like smbfs is that people are finally forced to report their
> > > > bugs.




-- 
Thanks,

Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/