Reinaldo Silva
2008-Jul-22 17:59 UTC
[Samba] Samba 3.2 PDC - Creating Zone Identifier files and not able to read/write/delete them.
Hello, I use a Suse 11.0 as a Samba 3.2 PDC. The clients run XP SP3. I have upgraded a few weeks ago from Suse 10.3 and now all files tranfer that I do - for example, downloading a file using a web browser - it leaves a trash file named "transferd-file:Zone.Identifier" or "tranferd-file:encryptable". The odd thing is that from Windows I can`t read/write/delete these files. They appear with names like "hdje2423". Any help will be apreciated. Thanks in advance. Reinaldo Silva reinaldosilva@ufmg.br reinaldo.silva@gmail.com
Jeremy Allison
2008-Jul-25 01:10 UTC
[Samba] Samba 3.2 PDC - Creating Zone Identifier files and not able to read/write/delete them.
On Tue, Jul 22, 2008 at 07:59:24PM +0200, Reinaldo Silva wrote:> Hello, > > I use a Suse 11.0 as a Samba 3.2 PDC. The clients run XP SP3. I have > upgraded a few weeks ago from Suse 10.3 and now all files tranfer that I do > - for example, downloading a file using a web browser - it leaves a trash > file named "transferd-file:Zone.Identifier" or "tranferd-file:encryptable". > > The odd thing is that from Windows I can`t read/write/delete these files. > They appear with names like "hdje2423". > > Any help will be apreciated.Looks like a bug in 3.2.0 that got missed in release. We now handle named streams in xattrs or in a database but if we're not using either of those modules we should refuse to create them (as we did in Samba 3.0.x). Try this patch, should fix it - will be in 3.2.1. (attached to this post). Either that or you can add: vfs objects = streams_xattr to the share definition and the named streams will be correctly stored in xattr's instead (so long as the filesystem supports them. Jeremy. -------------- next part -------------- diff --git a/source/smbd/open.c b/source/smbd/open.c index 0d1dd31..2184e69 100644 --- a/source/smbd/open.c +++ b/source/smbd/open.c @@ -3052,6 +3052,11 @@ NTSTATUS create_file(connection_struct *conn, ZERO_STRUCT(sbuf); goto done; } + + if (!(conn->fs_capabilities & FILE_NAMED_STREAMS)) { + status = NT_STATUS_OBJECT_PATH_NOT_FOUND; + goto fail; + } } if ((req != NULL) && (req->flags2 & FLAGS2_DFS_PATHNAMES)) {
Reinaldo Silva
2008-Jul-26 17:56 UTC
[Samba] Samba 3.2 PDC - Creating Zone Identifier files and not able to read/write/delete them.
It's ok now. Thank you very much. Reinaldo Silva reinaldosilva@ufmg.br reinaldo.silva@gmail.com On Fri, Jul 25, 2008 at 3:10 AM, Jeremy Allison <jra@samba.org> wrote:> On Tue, Jul 22, 2008 at 07:59:24PM +0200, Reinaldo Silva wrote: > > Hello, > > > > I use a Suse 11.0 as a Samba 3.2 PDC. The clients run XP SP3. I have > > upgraded a few weeks ago from Suse 10.3 and now all files tranfer that I > do > > - for example, downloading a file using a web browser - it leaves a trash > > file named "transferd-file:Zone.Identifier" or > "tranferd-file:encryptable". > > > > The odd thing is that from Windows I can`t read/write/delete these files. > > They appear with names like "hdje2423". > > > > Any help will be apreciated. > > Looks like a bug in 3.2.0 that got missed in release. > We now handle named streams in xattrs or in a database > but if we're not using either of those modules we should > refuse to create them (as we did in Samba 3.0.x). > > Try this patch, should fix it - will be in 3.2.1. > (attached to this post). > > Either that or you can add: > > vfs objects = streams_xattr > > to the share definition and the named streams will > be correctly stored in xattr's instead (so long as > the filesystem supports them. > > Jeremy. >