I moved from Ventura to Sonoma yesterday and have been dealing with wheels falling off ever since. I run a lot of my own software, written in Fortran and C and run in python and csh/tcsh scripts. I use cron to run several of these scripts. Many of these run on files located on an external drive. Whenever I run one of these scripts in cron I get a flurry of pop-up windows asking if it's ok for this or that program to access an external drive, one for each program in the script. All of these then end up as a new item in the "Full Disk Access" list. There are now 42 entries in this list. These codes have been used literally for decades and were working just fine pre-Sonoma.
Now, aside from how annoyingly stupid this all is, is there a way to cover ALL code I write myself which runs in shell scripts via cron to allow access to external drives rather than needing to get each and every one in this verdammte list? I have both csh and tcsh shells in this list, I have cron in this list, and I have python3 in this list, and yet still every piece of code that is run from one of these scripts apparently has to be on the list. Is that just the way it is in these days of three levels of prophylactics over every possible source of a security problem?
Now, aside from how annoyingly stupid this all is, is there a way to cover ALL code I write myself which runs in shell scripts via cron to allow access to external drives rather than needing to get each and every one in this verdammte list? I have both csh and tcsh shells in this list, I have cron in this list, and I have python3 in this list, and yet still every piece of code that is run from one of these scripts apparently has to be on the list. Is that just the way it is in these days of three levels of prophylactics over every possible source of a security problem?