linux-kernel - Re: [2.6.27 patch] the scheduled smbfs removal

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] [day] [month] [year] [list]

Date:	Tue, 20 May 2008 04:40:58 +0200
From:	Günter Kukkukk <linux@...kukk.com>
To:	Harvey Harrison <harvey.harrison@...il.com>
Cc:	Steve French <smfrench@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Adrian Bunk <bunk@...nel.org>, linux-kernel@...r.kernel.org,
	samba-technical@...ts.samba.org, linux-cifs-client@...ts.samba.org
Subject: Re: [2.6.27 patch] the scheduled smbfs removal

Am Dienstag, 20. Mai 2008 schrieb Harvey Harrison:
> On Mon, 2008-05-19 at 19:00 -0500, Steve French wrote:
> > Harvey Harrison <harvey.harrison@...il.com> wrote on 05/19/2008 
> > Note that some of the backlevel server support issues aren't handled
> > by smbfs either (and are hard due to protocol limitations). Guenter
> > Kukkukk had been tracking some of the issues with better backlevel
> > support (mostly for OS/2 and Win9x servers) so he might have more
> > information, but the obvious holes that come to mind are:
> > 
> > a) utimes to backlevel (lanman) servers
> > b) For some pre-Unicode servers it would help to be able to change the
> > code page used when translating readdir responses - so that we can
> > convert the server's readdir results from the old DBCS code pages to
> > UTF-8.
> > c) optionally zeroing pages on the client to work around the few buggy
> > old servers which don't zero on expanding file size remotely.
> > d) support for ancient dos ("core smb") servers
> > 
> > There are also a few places where Jeff Layton noticed the cifs code
> > would always try the more recent smb command (which fails) and only
> > then issue the backlevel SMB command (in a few of the places, it would
> > be safe to "remember" the "operation not supported" answer or
> > equivalent so we don't have to first try a command which will always
> > fail).
> 
> So it's generally people talking to older (or very old) servers that
> would be affected by this?  What options would they have if smbfs were
> removed?  Is there an alternative to smbfs that would work?  FUSE client?
> 
> (Not affected personally, just curious what the alternatives are where
> cifs won't do it)
> 
> Harvey
> 
> 
> 

dropping smbfs in 2.6.27 will conflict with
  - legacy servers like
       - win9x/me
       - OS/2
       - even todays sold "samba NAS boxes (2.x.x)" (!!!)
       - other old legacy servers like MSDOS/IBMDOS

Cifs vfs - the successor of smbfs - was _initially_
designed to only support the "NT LM 0.12" and "POSIX 2"
SMB/CIFS network dialects - NO legacy support at all.

I really can't talk about "FUSE client" - the burden
is on cifs vfs ... to also support legacy servers.

Steve French has already mentioned "some 
not implemented legacy features".

What is not working today in cifs vfs (regarding legacy servers):
  - stat()
  - utimes()
  - ....

There might be more glitches ...

Cheers, Günter

Btw - work is done to solve the outstanding problems
--
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/