Bug 291270 - Samba shared folders through Dolphin fail to be accessed due to access restrictions
Summary: Samba shared folders through Dolphin fail to be accessed due to access restri...
Status: RESOLVED NOT A BUG
Alias: None
Product: kio
Classification: Unmaintained
Component: smb (show other bugs)
Version: 4.7
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-11 13:58 UTC by freeseek
Modified: 2018-01-24 17:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description freeseek 2012-01-11 13:58:01 UTC
Version:           1.7 (using KDE 4.7.3) 
OS:                Linux

I have tried to share a directory using Samba through Dolphin (e.g. /home/user/public), but when I tried to access it through Dolphin (e.g. smb://localhost/public/) I got an error saying that the shared directory doesn't exist, though I could see among the shared directories (e.g. smb://localhost/). By inquiring in the logs (/var/log/samba/) I found the error:
[xxxx/xx/xx xx:xx:xx.xxxxxx,  0] smbd/service.c:988(make_connection_snum)
  canonicalize_connect_path failed for service ssl, path /home/user/public
I eventually understood that what was going on is that, by default, the /home/user directory was not accessible (permission 700). Changing permission (to 755) fixed the issue and the directory was now accessible. Nevertheless, this is a bug, as Dolphin should have checked on this when sharing the folder. I am not sure why the permission was by default so restrictive in Ubuntu 11.10, but it might relate to the fact that my home directory is encrypted.

Reproducible: Always

Steps to Reproduce:
chmod 700 /home/user
Share the directory /home/user/public
Try to access smb://localhost/public

Actual Results:  
Directory doesn't exist

Expected Results:  
Show content of public directory

This bug should be easy to fix. At least, a proper message should be given to the user so that he knows how to fix the problem
Comment 1 Nate Graham 2017-12-12 22:38:09 UTC
Why would you access the a local path using the smb:/ protocol? Why not just visit /home/user/public if you're already on the machine?