Question on streams dir structure creation.

Jeremy Allison jra at
Thu Oct 20 23:08:23 UTC 2016

On Thu, Oct 20, 2016 at 06:44:22PM +0000, Hemanth Thummala wrote:
> Jeremy,
> On 10/19/16, 4:55 PM, "Jeremy Allison" <jra at> wrote:
> >Are you setting the 'veto files = .streams' so the
> >clients can't get to the stored streams ? If so,
> >then I think you can probably open up the permissions
> >here as SMB clients just can't get to or see these
> >files.
> >
> Our “veto files” config is empty. As mentioned earlier, these streams directory components are created in the logged in user context. At this state this user becomes the owner and any other user has read only unix permissions. I still don’t get how other users can get access on these streams directory component to create new file-id streams directory if they don’t have wide open unix permissions. Also wondering how this issue could be specific to our stack. 
> Yes. We have made changes to open up the permissions. Its all looking good now. Thanks for the help!

Oh it's not specific to your stack. I just thought it would
be safer if the .streams directory was vetoed so SMB clients
never see it (it shouldn't really exist for them).

More information about the samba-technical mailing list