Sorry to revive an old bug, but I've recently run into this problem. Using the following in smb.conf, when I create a file as a remote user, the Owner's permissions are always set to executable on files (rwxrw-rw-), whereas they should be rw-rw-rw-.
[DnD Public]
path = "/mnt/PERSONAL/Dane/RPGs/DnD Public"
comment = Players can put stuff in here
writeable = yes
guest ok = yes
guest only = yes
force create mode = 0666
force directory mode = 0777
I've tried it with "force user = dane" in there (since that's my local login, which is set-up in samba's database), but keep getting the same result. Since this is a security problem, depending on the context, and since there's already a patch released upstream, at the link above, I was hoping this could get fixed in a security release sometime soon. (The patch was posted to that page in 2006--if this is, indeed, the same bug.)
I might end up patching and compiling Samba, myself, but I'd really rather not dump a pile of "make install" into my filesystem tree (and that wouldn't fix the bug in the repository, besides).
Sorry to revive an old bug, but I've recently run into this problem. Using the following in smb.conf, when I create a file as a remote user, the Owner's permissions are always set to executable on files (rwxrw-rw-), whereas they should be rw-rw-rw-.
[DnD Public] Dane/RPGs/ DnD Public"
path = "/mnt/PERSONAL/
comment = Players can put stuff in here
writeable = yes
guest ok = yes
guest only = yes
force create mode = 0666
force directory mode = 0777
I've tried it with "force user = dane" in there (since that's my local login, which is set-up in samba's database), but keep getting the same result. Since this is a security problem, depending on the context, and since there's already a patch released upstream, at the link above, I was hoping this could get fixed in a security release sometime soon. (The patch was posted to that page in 2006--if this is, indeed, the same bug.)
I might end up patching and compiling Samba, myself, but I'd really rather not dump a pile of "make install" into my filesystem tree (and that wouldn't fix the bug in the repository, besides).
Thanks for reading.