Hi, I've ran into an issue which only seems to affect one of my macs. It's currently running 14.2.1 but I first saw this issue in 13.6. If I download the macOS Sonoma 14.2.1 installer (via App store) onto this particular machine, it will never execute the installer. It always reports that the installer is "damaged". Of course I did reasearch this online and you get the usual unhelpful posts which just say "re download it" and of course, I wouldn't be posting here had I not tried that. This happens with any macOS installer I download using the softwareupdate --fetch-full-installer utility as well. The thing is, if I copy this .app to another (identical as far as I can tell) Mac - it will work. So far this also seems limited to macOS installers - other third party apps are fine. I'm convinced this is related to trusted execution and something has gone wrong in the environment. I've been looking at my router logs to see if any connections may have been blocked (I'm using OPNsense) and also looking to see what connections are being made via Little Snitch and so far it looks fine. Again, other machines on the network can run these just fine. I've read through eskimo's excellent guide here: https://forums.developer.apple.com/forums/thread/706442 but I was wondering if anyone can give me some pointers to narrow this down further. As it stands, I can't trust this machine for app development if I can't even get the official Apple installers to run sucessfully.

Hi, I’m developing a program which requires writing files to a volume mounted on a remote server. I've set up the volume on the server and shared a folder within there using a sharing-only account as a first test. The permissions are set to allow read and write for the sharing-only user in both the parent volume and the shared folder within it. However it will only let me access the directory over the network if I enable “Allow full disk access for all users” within the sharing settings in the server. What does this setting actually do? If I disable this option and then disable file sharing all together and then re-enable, it will switch that setting back on. It seems to tie in with the process smbd getting “full disk access” even though that process runs as root anyway. Allow full disk access for all users doesn't seem to grant my sharing-only user any more access than I’ve defined locally so I‘m really confused as to its use and why I need it for this to work. I’m on macOS Sonoma 14.4 for both systems.