File Sharing Permissions, "Read Only" still allows writing for Guests.

Can't figure out why something so simple doesn't seem to be working.


Turned on file sharing n my laptop

Added a drive to share media

Right-click on the shared folder/drive and went to Advanced Options to allow guest users

Users Staff and Everyone is set to Read Only

Connected as guest on another mac laptop

Yet, I can still rename and add files, essentially WRITING to the drive/folder.

Why is READ ONLY not working here?


Full disk access is turned off.




Posted on Apr 20, 2025 8:55 PM

Reply
Question marked as Top-ranking reply

Posted on Apr 23, 2025 3:48 PM

I cannot access any shares with Full Disk Access Off in File Sharing. I can see the shared folders, but if I try to open them, it says the original Item cannot be found.

In earlier versions of Sequoia, that let all users access to everything. Now, it appears that Full Disk Access doesn't allow access to all items.

I turned on Guest access, but could not log in as Guest, so I'm not sure what is going on. I do not have the Guest account enabled on the server, so perhaps that is my problem with Guest.


I have noticed that even though you connect as some other user, your current logged in user also has access to the mounted share. So, if that user has more access than the user you are connecting as, you will be able to write to a location that should be read only. The only way to isolate that is to log in from an account that doesn't exist on the server, remove access to that logged in user from the share on the server.

That seems confusing, so let me clarify how I am testing this.

On the host (server) Mac I have an account with same username as the one I use on my client Mac. From the client Mac I connect to the host (automatically as my logged in user) then disconnect. I click connect as… and enter my sharing user login credentials on the host. From that mounted share, I have all the access of my logged in user, and the access of the sharing user. On the host, I then set my client login user to have read only on the shares which my sharing user had only read access. With that setup, I could not write to the share with the sharing user.

So, if you are logged into the client Mac with an account that also exists on the Host Mac, then connect as Guest, you really are also still logged into the client Mac user account. There is no way to isolate that access. If you logged in as guest from an account that has no access on the host, I would think you would see the correct sharing behavior you expect.


1 reply
Question marked as Top-ranking reply

Apr 23, 2025 3:48 PM in response to bashzer0

I cannot access any shares with Full Disk Access Off in File Sharing. I can see the shared folders, but if I try to open them, it says the original Item cannot be found.

In earlier versions of Sequoia, that let all users access to everything. Now, it appears that Full Disk Access doesn't allow access to all items.

I turned on Guest access, but could not log in as Guest, so I'm not sure what is going on. I do not have the Guest account enabled on the server, so perhaps that is my problem with Guest.


I have noticed that even though you connect as some other user, your current logged in user also has access to the mounted share. So, if that user has more access than the user you are connecting as, you will be able to write to a location that should be read only. The only way to isolate that is to log in from an account that doesn't exist on the server, remove access to that logged in user from the share on the server.

That seems confusing, so let me clarify how I am testing this.

On the host (server) Mac I have an account with same username as the one I use on my client Mac. From the client Mac I connect to the host (automatically as my logged in user) then disconnect. I click connect as… and enter my sharing user login credentials on the host. From that mounted share, I have all the access of my logged in user, and the access of the sharing user. On the host, I then set my client login user to have read only on the shares which my sharing user had only read access. With that setup, I could not write to the share with the sharing user.

So, if you are logged into the client Mac with an account that also exists on the Host Mac, then connect as Guest, you really are also still logged into the client Mac user account. There is no way to isolate that access. If you logged in as guest from an account that has no access on the host, I would think you would see the correct sharing behavior you expect.


This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

File Sharing Permissions, "Read Only" still allows writing for Guests.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.