Files and Folders access??

https://dev.iachieved.it/iachievedit/macos-10-15-catalina-adds-additional-filesystem-restrictions/
 
<https://dev.iachieved.it/iachievedit/macos-10-15-catalina-adds-additional-filesystem-restrictions/>

I am NOT a Catalina user.



Regards
--------------------------------------------------
Peter Collinson

> On 17 Oct 2019, at 23:52, JF Mezei via X11-users <[email protected]> 
> wrote:
> 
> Some time ago, in a newsgroud discussion, there was a discussion about
> file access for line commands. I don't recall the specifics because
> discussion quickly turned to insults,  but there are some under-the-hood
> inheritances.
> 
> I am sticking to High Sierra, so not affected by this.
> 
> There is a process inheritance issue.
> 
> The "ls" (or any other) command is a subprocess created by bash (or
> whatever shell you use such as sh).
> 
> But how bash/sh is created is not so clear.
> 
> Consider this:
> 
> from terminal.app window under GUI user ABC, you can issue the command:
> xterm -e login &
> 
> an xterm window is created (assume under user ABC) with the login
> process. That login process then creates a bash (or sh) process under
> the user DEF. Does that process inherit any special attributes from ABC?
> 
> It isn't clear to me whom bash/ls inherit any special file access flags
> from (since not clear to me at what level OS-X implemented these
> restrictions).
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> X11-users mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription: 
> https://lists.apple.com/mailman/options/x11-users/pc%40hillside.co.uk
> 
> This email sent to [email protected]
> 

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription: 
https://lists.apple.com/mailman/options/x11-users/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to