[Bug 210118] Samba `fruit:encoding = native` results in File Not Found
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Jun 7 19:00:38 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210118
Bug ID: 210118
Summary: Samba `fruit:encoding = native` results in File Not
Found
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: freebsd-ports-bugs at FreeBSD.org
Reporter: freebsd at cod3r.com
First discovered on FreeNAS 9.10 and reproduced on FreeBSD 10.3 with Samba
4.3.8. Tested on Ubuntu 14.04 with Samba 4.3.9 and it does not exhibit this
problem:
Using Samba with `vfs objects = fruit` and `fruit:encoding = native` allows Mac
clients to see files with illegal characters as far as SMB is concerned. For
example, a file with a `:` character in it is normally mangled to an 8.3 over
SMB, but the above options allow Mac clients to see the original filename.
However, any attempt to access such a file or directory results in a File Not
Found kind of error on the client. Testing the same smb.conf file on a Ubuntu
linux 14.04 system resulted in the files being visible with the original
filenames as well as normal access to these files.
Steps to reproduce:
Install Samba and put the following in smb4.conf:
vfs objects = catia fruit
fruit:encoding = native
On the server in the share:
echo "This is a test" > "A name with a : in it.txt"
On the mac client, connect to the share and cd to it:
more "A name with a : in it.txt"
You will see `A\ name\ with\ a\ :\ in\ it.txt: No such file or directory`
On the mac client:
touch "Another name with a : in it.txt"
echo "This is a test" > "A Third name with a : in it.txt"
Notice that in both cases the file creation succeeds and the file with the
correct name is visible both on the client and server, but the client still
cannot read it. In the last case, the file's contents are visible on the
server.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list