Ticket #184 (new defect)
Access problems with symbolic link
| Reported by: | anonymous | Owned by: | alamaison |
|---|---|---|---|
| Priority: | critical (affects core workflow) | Milestone: | 0.7.x Bug sprint |
| Component: | authentication | Version: | 0.6.3 |
| Keywords: | Cc: | p.seitz@ks-ingenieurconsult.de |
Description
I've installed latest version of swish (0.6.3) on Windows XP Professional, Version 2002 SP3.
I have a linux user (and his own group) test who is member of (linux) group exchange.
His home directory is /home/test with the following information:
drwxr-xr-x 21 root root 528 2012-05-29 16:00 home
drwxr-x--x 3 test test 96 2012-05-29 16:03 test
I have created an exchange directory as followed:
/home/exchange/project
with the following rights:
drwxr-xr-x 21 root root 528 2012-05-29 16:00 home
drwxrwxr-x 3 root exchange 72 2012-05-29 15:28 exchange
drwxrwxr-x 2 root project 72 2012-05-29 17:49 project
-rw-rwxr-- 1 test2 project 12 2012-05-29 17:50 file_for_test.txt
In the test user directory, I've created a symbolic link as followed
ln -s /home/exchange/project projectdir
and I have changed the ownership as followed
chown test.project -h projectdir
which results in:
lrwxrwxrwx 1 test project 21 2012-05-29 16:03 projectdir -> /home/exchange/project/
When I connect with swish to /home/test , I can access my files in my home directory without problems. Download it, modify it, store locally and finally upload the modified file.
When I try to acess the exchange directory with swish through the projectdir link, I cannot access the project directory. The error message tells:
Failed obening remote file: FX_NO_SUCH_FILE
HRESULT: E_FAIL
So it seems to be a right problem.
I've then tried to connect to the directory with WinSCP v4.0.7 (Build 370) and user test and I could access the "file_for_test.txt" without problems. I also could upload a modified copy (resulting in some errors setting the permissions, but that is another story).
So for me it seems to be that swish has problems with the rights when following a symbolic link.
Can someone please confirm?
Is there a fix possible or should I try to do a hardlink?
Thanks
Peter Seitz
