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  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:	Thu, 03 May 2007 10:36:53 -0400
From:	simo <>
To:	Christoph Hellwig <>
Cc:	Steve French <>,,
Subject: Re: [linux-cifs-client] Re: SMB2 file system - should it be a
	distinct module

On Thu, 2007-05-03 at 15:17 +0100, Christoph Hellwig wrote:
> On Thu, May 03, 2007 at 09:21:29AM -0400, simo wrote:
> > Separate modules would mean the user have to know which protocol to
> > choose each time. And this make little sense.
> Of course it makes a lot of sense.  We don't have anyfs.ko either
> because some ubuntu users are too braindead to know what's on their
> disk.
> > You really want to auto-negotiate which protocol to use, because you
> > could have at the same time a connection to a Vista/Longhorn (SMB2)
> > machine and one to a Windows 2000 server (plain SMB) in the same domain
> > using the same credentials.
> So what?

I guess DFS referrals can work cross protocol, so if you are redirected
from a longhorn server to a windoes 2000 or a samba server you want to
be able to follow the DFS referral and not return an error.
To do that you need to have either 1 module that support both protocols
or a way from one module to call the other. Just separating the 2
without any glue will not work (or you will have to add some userspace
upcall hack to make it work).


Simo Sorce
Samba Team GPL Compliance Officer

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists