I moved from Ventura to Sonoma yesterday and have been having problems with my wheels coming 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 some of these scripts. Many of these run on files that are on external drives. Every time I run one of these scripts through cron, I get a flurry of popup windows for each program in the script asking if it's ok for this program or that program to access the external drive. They all become new items on my “Full Disk Access” list. Currently, I have 42 entries in this list. This code has been in use for literally decades and worked fine before Sonoma.
Now, setting aside how annoyingly stupid this is, is there a way to cover all the code I've written that gets run in a shell script via cron to allow access to an external drive? The list has both csh and tcsh shells, cron is on this list, python3 is on this list, and yet all code that gets run from one of these scripts apparently needs to be on the list. Is this even a reality these days, when we take three steps of precaution against every possible source of security problems?