kill security=share and security=server

[Volker Lendecke]

On Thu, Jan 27, 2011 at 09:47:53AM -0800, Jeremy Allison wrote:
> > Also, implicitly mapping sec=share to sec=user in SMB2 just
> > adds to the mess. Can we please remove that?
> 
> I don't think we can do that. It allows people to move
> to SMB2 simply by adding "max protocol = SMB2" and no
> other changes. Remember we'll probably end up making
> "max protocol = SMB2" the default, so we need to ensure
> that existing smb.conf files will upgrade and work
> without change.
> 
> What is the problem with the mapping ? We already
> had a bug report because it wasn't done completely
> (and someone using security=share wanted to test
> SMB2). I don't see why having the mapping causes a
> problem.

Ok, maybe you're right. I think it gives different semantics
though depending on which client OS you're coming from, or
what protocol the client decides to use. I would feel better
if we had max protocol = smb1 for all security=share configs.

Volker

-- 
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen