MacOS Big Sur permission problem

Question

Created Jul ’20

Replies 4

Boosts 0

Views 6.7k

Participants 4

Hi!

I've just installed developer beta and realize that some files in Finder now are showing as Exec icons, regardless they are functioning properly.

Via Terminal I found there are some permissions change as was installed. I see a lot of documents have 777 level of permission.

For example I have a work One Drive folder and if I access the same file from a Windows machine there is no problem and is not identified as an exec file.

I had the same folder on Catalina and not a single file was showing as an Exec file.

Have you found similar behavior?

Boost

Answer 1

Puffincendre OP

Jul ’20

BigSur introduced a new csrutil with this: csrutil authenticated-root status

Boot in BigSur Recovery and type in the terminal csrutil authenticated-root disable, this is the "new BigSur SIP disabled" (from my current BigSur normal booting terminal)

The reboot back to your desktop and type csrutil authenticated-root status and see if you et disabled. You should now to be able to change your permission.

If not post back, I will try to see what I can do..

2

Answer 2

trancemeister75 OP

Jul ’20

Thanks!

I'm afraid I actually can change permission without problem, I'm adding a screenshot that serves as an example:

https://www.icloud.com/iclouddrive/033xm6eVigPCB98Ga2F0JQhhw#Screen_Shot_2020-07-01_at_14.30.21

Here as you can see the listed documents have the same level of permissions, but some of them are shown as exec files and the txt doc is shown properly, well this is happening across all my One Drive, NAS folders and iCloud Drive.

Basically some of them are showing properly and other ones not.

0

Answer 3

marcelkraan OP

Nov ’20

I can't add a theme file to my /usr/share/vim/vim82/

Marcels-MBP:usr root

touch test

Marcels-MBP:usr root

csrutil authenticated-root status

Authenticated Root status: disabled

Marcels-MBP:usr root

pwd

/usr

touch: test: Operation not permitted

Marcels-MBP:usr root

id

uid=0(root) gid=0(wheel) groups=0(wheel),1(daemon),2(kmem),3(sys),4(tty),5(operator),8(procview),9(procmod),12(everyone),20(staff),29(certusers),61(localaccounts),80(admin),33(appstore),98(lpadmin),100(lpoperator),204(developer),250(analyticsusers),395(com.apple.accessftp),398(com.apple.accessscreensharing),399(com.apple.accessssh),400(com.apple.accessremoteae),701(com.apple.sharepoint.group.1)

Marcels-MBP:usr root

df

Filesystem 512-blocks Used Available Capacity iused ifree %iused Mounted on
/dev/disk1s7s1 975415384 29178256 663233768 5% 563932 4876512988 0% /
devfs 379 379 0 100% 656 0 100% /dev
/dev/disk1s4 975415384 2099296 663233768 1% 3 4877076917 0% /System/Volumes/VM
/dev/disk1s2 975415384 553304 663233768 1% 815 4877076105 0% /System/Volumes/Preboot
/dev/disk1s6 975415384 5632 663233768 1% 20 4877076900 0% /System/Volumes/Update
/dev/disk1s1 975415384 235914960 663233768 27% 592697 4876484223 0% /System/Volumes/Data
/dev/disk1s5 975415384 42834640 663233768 7% 563938 4876512982 0% /Volumes/Macintosh HD
map auto_home 0 0 0 100% 0 0 100% /System/Volumes/Data/home

I really don't know how to write a file on the ***** filesystem

0

Answer 4

BlazerinEDH OP

Nov ’20

I'm just a regular guy who's old Mac Mini died and needed a replacement. Now with the new M1 and Big Sur, using Paragon's NTFS writing program for Big Sur, I am only able to write to about half of my NTFS discs. I can read slightly more than that. Others show ZERO files on the drive. I am so mad at Apple. I can't change permissions. I don't even show up in the box. Everything is grayed out. I hope somebody smart can fix these problems so I don't lose so many TBs of data. BOO!

2