Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As a root I can chown a dir say /rock to ramu:ramu.
I smbmounted a windows dir onto this.
Now /rock permissions are set to root:root.
I issues chown command to set it to another user say, ramu.
It appears that the command worked, [no warnings given]
But " ls -l " shows root:root for /rock.
Now user ramu is unable to creat any file under the smbmounted /rock.
I don't believe smbmounted fs's support changing owning users or groups. The problem is some smbmounted shares could be filesystems that don't have those permissions. I believe the owning user/group is automatically set to the user/group that mounts the fs. This is the same behavior you'd see if you mounted a local fat32 disk.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.