All of that makes sense. However, with Catalina, macOSX/Darwin seems to now treat the Documents, Downloads, and Desktop directories a little differently, at least with regard to whatever xterm is doing in starting processes and setting permissions. Eterm does as well. rxvt does not. Those are the only X-Window terminal applications I have tried. Apple Terminal, and iTerm2 also do not have a problem. Any other directory in the user’s home directory also do not have problems at all, no matter what terminal program you use. Even xterm and Eterm start to behave normally if you futz around with them. Doesn’t matter whether they are started as part of the X11.app/XQuartz.app, or from a separate terminal session, like Terminal. Doesn’t happen on Mojave or earlier MacOSX releases.
These three directories are probably considered by Apple to be, for the normal user, needing more security, and there may be an obscure bug that xterm and others have triggered in Catalina. Apple has been making security related changes to the file structure since moving to APFS as the boot disk file system. It would be interesting to see if the behavior was different if the user’s home directory was located on an HFS+-formatted volume, or an NFS/SMB/Appletalk volume. Since X11 on MacOSX is now pretty much a volunteer effort, it’s not clear how much attention is being paid to something obscure like this, especially if there are alternatives and workarounds. Jonathan > On Oct 24, 2019, at 6:43 PM, JF Mezei via X11-users > <x11-users@lists.apple.com> wrote: > > ps -a -f > > bike:~ $ ps -a -f -x | grep 9780 > 501 9780 1 0 6:22PM ?? 0:00.28 /opt/X11/bin/xterm > 501 9968 9780 0 6:22PM ttys000 0:00.01 bash > 501 10057 10029 0 6:31PM ttys000 0:00.00 grep 9780 > > One would have to look at the xterm code which creates the process whose > input and output are to itself (so it can display in the window). > > In this case, the xterm was created from the X11 GUI "Applications" > menu optiosn wghere I have one to run xterm. But note that the parent > process of the created xterm is 1 and not that of the X11 app. > > Another example: > > 0 86493 86492 0 0:00.01 ttys000 0:00.02 login -pf root > 0 86494 86493 0 0:00.01 ttys000 0:00.01 -sh > 0 86503 86494 0 0:05.07 ttys000 0:45.66 xterm -e login > 0 86504 86503 0 0:01.08 ttys001 0:04.05 login > 501 86526 86504 0 0:00.00 ttys001 0:00.01 -bash > 0 86562 86526 0 0:00.00 ttys001 0:00.00 ps -a -f -x > > > In this example I am GUI logged in as root. Start a terminal.app window. > Which causes the "login -pf root" command and the "sh" commands. > I then issued a export DISPLAY="10.0.0.21:0.0" (not shown since not a > process), and xterm-e login. > > Notice the login process is created as a root process. It spanws a > supbrocess to run bash under my normal usename of 501. > > I am not sure about flag inheritance when the "login" happens to another > process. But in the second example, the bash running under 501 is not a > child of xterm, it is a child of login. while xterm is in the tree, it > is under a different username and the bash process does not inherit any > of root's powers. > > I know this doesn't answer things, but a better understanding of process > inheritance of whatecer flag Apple uses to allow/disallow access to your > onw files would point to what binary needs to be granted access. > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > X11-users mailing list (X11-users@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/x11-users/jprescott12%40icloud.com > > This email sent to jprescot...@icloud.com _______________________________________________ Do not post admin requests to the list. They will be ignored. X11-users mailing list (X11-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/x11-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
