[jcifs] ShareSecurity with OverlandStorage Server aka SnapServer
Christopher R. Hertel
crh at ubiqx.mn.org
Wed Oct 19 06:43:58 MDT 2011
Mazhar Lateef wrote:
> Hi Christopher,
> Does this mean Jcifs will not be compatible with SMB V2,
I never said that, and I don't think I said anything in my e'mail that would
Currently, however, jCIFS does not support SMB2 but that's okay because
every server of which I am aware still supports SMB1.
All I was trying to point out is that SMB/CIFS is a complex protocol and
ever server will behave a bit differently. In addition, every configuration
variation will cause a difference in behavior.
> Regarding the SnapServer, I will try to find out about the configuration
> options available, and see if there is anything that is forcing this
> behaviour of returning the Everyone Group.
Forcing or enabling.
The Windows ownership and permissions system is complicated, and also quite
different from the Unix/Posix/Linux system. A mapping has to occur in order
to ensure that permissions work as expected.
> Many Thanks for your input.
> On Tue, Oct 18, 2011 at 9:08 PM, Christopher R. Hertel <crh at ubiqx.mn.org
> <mailto:crh at ubiqx.mn.org>> wrote:
> I *believe*, but do not know for sure, that the SnapServer product
> runs Samba.
> The SMB/CIFS protocol is not the same per platform. Every
> (including different Windows versions) has variations. The protocol
> is too
> large and too complex for there to be a viable conformance test. In
> addition, the semantics of SMB/CIFS and now SMB2 are tied very
> closely to
> Windows and NTFS semantics. Any server that is not running on
> Windows must
> translate semantics between those expected by the platform and those
> expected by the protocol. It gets tricky.
> All that said... There is probably a configuration parameter on the
> SnapServer that is set in such a way that it is always returning the
> "Everyone" group. I do not know what configuration interface
> make available.
> Chris -)-----
> Mazhar Lateef wrote:
> > Hi All,
> > We are currently working with a client using an overland Storage
> > appliance aka SnapServer running Guardian OS. Jcifs seems to work ok,
> > except it does not seem to return the correct share security
> > of the Shared folder. The same application when used in a windows
> > environment works absolutely fine and returns the correct information.
> > The client's appliance is integrated with a AD and the shared
> > permissions are applied to security groups from the AD. Jcifs seems to
> > ALWAYS return the everyone group even when the share security does not
> > have everyone listed in the Allow permissions.
> > Can anyone help please? does anyone know anything about SnapServer and
> > why the share security may not be working? I would have thought
> the CIFS
> > protocol will be the same regardless of the platform.
> > Any help, guidance, pointers would be much appreciated.
> > Maz
> "Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
> Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel
> jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development,
> ubiqx Team -- http://www.ubiqx.org/ -)----- crh at ubiqx.mn.org
> <mailto:crh at ubiqx.mn.org>
> OnLineBook -- http://ubiqx.org/cifs/ -)----- crh at ubiqx.org
> <mailto:crh at ubiqx.org>
> Mazhar Lateef
> Virtualcode Solutions LTD - London
> www.virtualcode.co.uk <http://www.virtualcode.co.uk>
> Tel : +44 (0)20 3286 1246
> Fax : +44 (0)207 900 3460
"Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/ -)----- crh at ubiqx.mn.org
OnLineBook -- http://ubiqx.org/cifs/ -)----- crh at ubiqx.org
More information about the jCIFS