A very fussy case of "XXXX will damage your computer"
I am attempting to run a Rust script in Terminal. When I issue the cargo command, I get the dreaded message:
I have used both malwarebytes and etrecheck to look for malware - all clean. Then I read and followed directions from John Galt's excellent article:
About those "<app> will damage your… - Apple Community
My LaunchAgents/LaunchDaemons folders look pretty clean (see below), but I'm still getting the error.
Seems like others were getting the error when their computer would start up, or otherwise frequently, whereas I'm getting it only when I attempt to run a Rust program. I used an old git branch for the same Rust call and the error still appears, so I don't think it has anything to do with the script itself. (But I could be wrong of course!)
A colleague using the same tools with the same OS (Sonoma) is getting the same error...
Does anyone have any suggestions?
MacBook Pro 13″, macOS 10.13