Samba permissions

[epitaxial]

Hello all, I am having an issue with Samba (3.6.15) and OpenBSD 5.6. I can see the files from my Windows 7 box but they all appear as 0 bytes and cannot be opened. Here is my smb.conf

#============= Global Settings =======================#

[global]
   host msdfs = no
   mangled names = no
   bind interfaces only = yes
   deadtime = 15
   default case = lower
   disable netbios = yes
   dns proxy = no
   domain master = no
   encrypt passwords = true
   guest ok = yes
   guest only = no
   interfaces = em0
   invalid users = nobody root
   load printers = no
   max connections = 10
   netbios name = openbsd
   preferred master = yes
   preserve case = no
   printable = no
   security = user
   server string = Samba Share
   socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536
   strict sync = no
   sync always = no
   syslog = 1
   syslog only = yes
   workgroup = WORKGROUP

#============ Share Definitions =======================#
[Video]
   path = /home/video
   read-only = no
   public = yes

The local OpenBSD account has no problems reading the files so that leads me to believe it is a samba issue. Any ideas?

[epitaxial]

The option "mangled names = no" causes this problem. Commenting that out gives me random gibberish in 8.3 filename format but they CAN be opened. Changing to yes fixes the filenames but they become inaccessible.

OK it has something to do with this

vfs objects = catia
catia:mappings = 0x22:0xa8,0x2a:0xa4,0x2f:0xf8,0x3a:0xf7,0x3c:0xab,0x3e:0xbb,0x3f:0xbf,0x5c:0xff,0x7c:0xa6,0x20:0xb1

My filenames have spaces and colons in them which apparently Samba can't handle anymore. I never had to deal with this in the past. Why is it an issue now?

[hanzer]

Originally Posted by epitaxial

The option "mangled names = no" causes this problem. Commenting that out gives me random gibberish in 8.3 filename format but they CAN be opened. Changing to yes fixes the filenames but they become inaccessible.

My filenames have spaces and colons in them which apparently Samba can't handle anymore. I never had to deal with this in the past. Why is it an issue now?

See Name Mangling and Case (about half way down the page).

Replacing the colon in the filename with an underscore might be done with something like:

mangled map = (: _)

[hanzer]

Originally Posted by hanzer

mangled map = (: _)

Wait, this approach is old and doesn't seem to exist in Samba version 3.6.15. Ignore me.