On Mon, 2007-07-02 at 10:19 -0700, Jeremy Allison wrote:
> On Mon, Jul 02, 2007 at 05:09:54PM +0000, simo wrote:
> > The biggest problem is leaking streams from one user to another:
> > userA delete fileA with streamA
> > userB create fileB
> > accidentally fileB inode == fileA
> > userB has streamA data in fileB
> That's not an in Samba issue - on delete
> of fileA we also delete the stream directory
> containing the inode name. Could be a problem
> with UNIX tool access though. We need a generation
> count or something similar....
Yes I was point out the problem of manipulating files from the user
side, not the samba side.
Keeping the same ACL on the streams that you have on the original files
may mitigate the problem a lot though.
Samba Team GPL Compliance Officer
email: [email protected]