Ventura (13.5.2) has NO file security at all

The problem is almost entirely solved.

I upgraded to macOS Sonoma hoping what happened to user Test would not come back AND that Sono as real USER wouldn’t experienced those most frustrating false error messages telling him he’s not the owner of his own files… even if this occurs in ±1% of the cases.

In the INFO window of Shakti I made sure I deleted all groups I could. I made sure Sono is the owner (or at least is listed first) and “Everyone” with “NO ACCESS”.

Then I applied it to all encloses items and… it worked. OUFTI (this is French mening “At last it worked, so I’m relieved and let it finally go”).

The first enclosed screenshot was of course not owned by Sono, as it was taken by test and indicated HE, (i.e. test) was the owner of that file.

Should I have added the INFO view when logged in by sono? Here it is:

As you can see sono is mentioned twice.

Q1. Any idea how to get rid of this anomaly? I tried to delete one but it didn’t work (no for the second one and not for the first one).

BUT!!! When I updated the rtfd file of this issue, I got another error:

The document “Ventura has NO file security at all… by default.rtfd” is on a volume that does not support permanent version storage.

Q2. Will this never stops?

Here the INFO about ext. HD Shakti:

By miracle the updates (of file “Ventura has NO file security at all… by default.rtfd”) WERE saved, so I didn’t most anything (to be complete: juste before; the file itself closed without allowing me to make a duplicate).

for etresoft: Thank you for your time and concerns. Let me reassure you: my organisation is extremely simple and SOLID.

So:

I have one internal SSD with ALL applications and SYSTEM stuff. and ONE “System Admin user”, called “Mackie”, whose only purpose is when need to ADD a new application or update/upgrade the system.

I have one external SSD with ALL data files and ONE USER called “Sono” who formatted that disk. And which more than 200 000 files (two hundredth thousands, that’s, I think, “200,000” for US Americans) and many thousand of folders all bearing a clear, unambiguous name. I only use LIST view, and each folder, depending on its use, is shown sorted by 7 COLOR LABELS, MOD. DATE and/or ITS NAME.

In other words, I’m using Sono ±99,97% of the time.

As for another vaste list of reasons I don’t use Time Machine but have several other external devices where I put backups on.

The only reason to have a TEST user was to find out about the inconsistency of the default file security which I now know, has its reason.

The fact that (1) BY DEFAULT all disks are NOT private and (2) do NOT have an owner and (3) that you have to MANUALLY indicate which is the owner, (4) to propagate it to its content and (5) to give NO ACCESS to everyone else, is, in my view, a severe security leak. But hey: who am I?

Thus, dear, etresoft, don’t worry, as I DO NOT want to share files amongst users, as I have no need for it.

I know my way of working if different from most users, and I take full responsibility of it.

And please, dont’t ask me why. It’s just far too complicated (and extremely long) to justify.

BUT, and now comes the delicate part, do not tell me that IT IS NORMAL that Sono as the OWNER of the whole disk and CREATOR af each and very file irregularly receive errors (which I call LIES, how would YOU call them?) telling him HE IS NOT THE OWNER or telling him the VOLUME DOES NOT SUPPORT PERMANENT VERSION STORAGE, which is disregarded some seconds (or minutes) later!

Since I’m using Sonoma, I receive other strange error messages… upon each start up:

• The application Finder can't be opened.

• The application “Firefox.app” can’t be opened.

Doesn’t this make you wonder if they ever tested it?!??

(I’ve lost the “The application Finder can't be opened” error message)

I was spammed several times each and every day, by messages telling me an update will be performed later that day… which never occurred despite the fact I didn’t shut down for more that a week, you may understand why I finally wanted to do it manually.

[having endured the worst system degradation starting in ±2018 (where I kept El Capitan for another bunch of extremely good reasons) up to March 2023, by NOT upgrading, I nowadays don’t wait too long before upgrading]

So let’s close this issue, unless you know why macOS becomes less and less consistant?

(I’ve now the INSIDE MACINTOSH era, where EVERYTHING WAS CONSISTENT, EASY AND USERFRIENDLY. It degraded around mid-2010 and I can give some hard examples)

Have a nice day…

At first I thought: "YES THAT'S IT", because the check box (at the end of the INFO panel was indeed crossed). But when I uncrossed it. Nothing changed. I logged in into TEST and he still could do all changes.

But, as paradoxal as it can be, SONO, the owner of a simple text file couldn't make any changes in an open text file. He needed to make a copy and save it on the desktop.

He get’s: You don’t own the file “…rtfd” and don’t have permission to write to it.

I.e. the word upside down (but this time worse). + the situation has become WORSE.

Sono created the ext. HD “Shakti”, so why is is marked System?

AND, BELIEVE IT OR NOT: THE ONWER OF THIS VERY TEXT FILE HAS BECOME “TEST”!!!!!!!!!!!!!!!!!!!!!!!!

The more I try to solve it the worse it gets!!!

! ! ! H E L P ! ! !

for Barney-15E: I’m not familiar with Terminal and think it should only be used by very experimented users WHICH I AM NOT.

It’s already enormous difficult making an REBOOT or AUTOMATIC SHUTDOWN.

Note1: i’ve no idea what is a “POSIX owner”. And I already told, I only have 3 users mackie, sono and test (see further).

Note2: The last time I had to use ACL’s was before 1997. It was when everybody was connected to 1 single Digital mainframe via… terminal.

Note3: aren’t you confounding with another issue?

Note4: The issues I’m encouter should be reported to APPLE and I do not intent to complicate my work with cryptic manipulations, î’ve no knowledge about.