Want Public Folder READ ONLY for Guests Read/Write for Users

Zitat von SpiritualMadMan

My Users Group I trust to add files and edit stuff in the public folder.

But, not everyone in the family or Guests can be trusted to do so.

If we're talking about a Samba share (SMB) accessible on your network, there are two ways to do what you want:

You have a shared folder with permissions. Note that Samba (SMB) CAN NOT override file folder permissions to allow more access. Samba can further restrict, but it can not override, granting a permission that does not exist in the following.

Shared Folder permissions for a Music Share:
In the following, the users group can edit the share. (This is any user added to the server.) They can add files, delete, etc.
"Others" which is the equivalent of an SMB "Guest" has read only.
 

________________________________________________________________________________________________________

If you have "Others" (or the SMB equivalent of "Guests") set to Read/Write/Execute, in essence, everyone would have write access) The following will still provide the protection you're looking for.

As I said before, Samba can restrict further but can not override. In the following, the Samba share (which is layered onto the shared folder) is set to read only. Read only applies to all.

Now, for the final note:
Even with write access at the Shared folder level, you can set the top level SMB share as "Read Only". When Samba is set to "read only", the following statement in extra options will allow members of the users group to "write" anyway. It's called a "write list". It can be done for a single user as well, in this form -> write list = username
In this way, an exception for a group or a user can be made to the Global "read only" setting above.

So here are the minimum settings for what you want:
Shared Folder:

users must have Read/Write
others must have Read

SMB share
Public: Guests allowed

The above would be enough.
_________________________________________________

(Setting Read Only in the SMB share, then overriding "read only" for your users group only with a write list, would only be necessary "if" your shared folder has "others" with full permissions of Read/Write. This particular SMB setting would prevent guests from writing to the share.)
_________________________________________________

**A more inclusive document regarding shared folder permissions and SMB shares can be found -> here .**

Zitat von SpiritualMadMan

Honest IO will take a Linux course as soon as possible...

For now I quit

Oh no! Don’t quit for now. This IS your Linux course. Besides, most of your questions have to do with settings in the OMV GUI. Look at what a great explanation you got from crashtest above, which will benefit others who read this thread. The little tidbit about using write list=@users in the extra options of your SMB settings was something that I didn’t know. The explanation of the relationship between shares permissions and SMB permissions is a little nugget of gold, not found anywhere in the complete & updated manual. There is so much to learn from the ongoing threads in this forum. Never quit.

Sometimes Google is your friend, but not always. My biggest problem with Google is sometimes I can’t figure out how to phrase a search in order to get the desired search results. In this age of lockdown and masks it’s refreshing to interact with a real person.

Zitat von CrashTestDumie

OMG! Nearly 2 weeks of research, and finally I found an answer to my issue! Thank you so much crashtest

If you need more help, I wrote a document that might be useful, -> here.

Look through the doc. It explains some of the pit-falls.

First, I'd recommend creating a new thread for this issue, to get the attention of people experienced with SQL. This question is out of the scope of Linux file permissions. SQL DB permissions, users, DB backup, etc., are different topics altogether.

In the new thread, you might want to mention "where" the SQLite server process is running. (Is it on OMV or on a Laptop Client?) What your SQL server is doing would be useful information as well (the back end for what?).
______________________________________________________________

While I'm not an SQL expert:
SQL files (actually databases) are created by the SQL server process. The server expects to maintain exclusive control of the DB file while the server is running. Usually, when the server is active, it holds its DB files in a continually open state. You can do a simple file copy of the DB file but there's a chance that the copy may be corrupted, if the server writes to the DB while you're backing it up. To do a proper DB backup, the server should be commanded to quiet down - to not write to the DB during the backup. While it may be possible to run a command line or script a "stop the server" or a "detach database" command, Free File Sync does not appear to be capable of doing that by default.