You are not logged in.
Hi there,
I recently updated samba to version 3.4.6-1 and now the symlinks that are placed in my shares won't work
anymore. I tried putting follow symlinks = yes and wide links = yes in smb.conf but when I click on a folder that's actually a symlink in windows I get: Drive:\Folder is not accessible Access is denied.
I know that symlink behaviour was changed in samba due to possible security problems. But security is not an
issue for me, so how can I get the old behaviour back?
Thanks for any help.
Last edited by Orim (2013-08-12 21:57:54)
Offline
Hello, I got exactly the same issue than you after upgrading samba-and smbclient from 3.4.5-1.1 to 3.4.6-1: symlinks in a share don't work anymore.
Downgrading samba and smbclient on the server reverted successfully to the previous behaviour, I'll guess I'll wait for a fix or more info from the samba team.
Cheers,
Offline
I think you also need to set "wide links = yes"
See here for info :
http://www.samba.org/samba/news/symlink_attack.html
EDIT
Doh !!! I missed that you already set both. I haven't been using symlinks in any shares, so haven't seen the issue. Maybe I'll play around later today + see what breaks.
EDIT 2
I got it working with the following...
In the Global section of smb.conf you need the following :
unix extensions = no
If you omit it, but enable wide links, you should see something like the following in the logs :
Share 'tmp' has wide links and unix extensions enabled. These parameters are incompatible. Wide links will be disabled for this share.
The "wide links" and "follow symlinks" are Share options, so should not be in the Global section, but in any Share definitions where you want to enable the functionality.
Disclaimer - I didn't only minimal testing just to "make it work", so I don't know what other impact this will have...
Last edited by dschrute (2010-02-28 14:50:22)
Offline
I got it working with the following...
In the Global section of smb.conf you need the following :unix extensions = no
Great, thank you very much. Now it works again.
Can someone maybe clarify what other effects setting unix extensions to no could have?
Thanks...
Offline
unix extensions (G)
This boolean parameter controls whether Samba implements the CIFS UNIX
extensions, as defined by HP. These extensions enable Samba to better serve
UNIX CIFS clients by supporting features such as symbolic links, hard links,
etc... These extensions require a similarly enabled client, and are of no
current use to Windows clients.
Note if this parameter is turned on, the wide links parameter will
automatically be disabled.
See the parameter allow insecure wide links if you wish to change this
coupling between the two parameters.
Default: unix extensions = yes
Offline
jiehanzheng, Your post is relevant to the thread, so I will leave the thread open -- but -- be advised that this thread is a bit stale ( 3 1/2 years stale )
Don't be surprised if you don't receive a reply and, please, be aware of our policy
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Wow, 3.5 years later and I'm actually still running the same arch installation...awesome
jiehanzheng did not write any question but an answer to mine. Thanks, I guess.
I've marked the question as solved.
Offline