I am not sure if this is a complete explanation of the notarization requirement. Isn’t this either disable-able or bypassable with admin rights to the machine,

I am not sure if this is a complete explanation of the notarization requirement. Isn’t this either disable-able or bypassable with admin rights to the machine, similar to existing Gatekeeper? I assume Homebrew, MacPorts, and others will continue to work, just as Gatekeeper does not block them today. According to https://eclecticlight.co/2019/06/07/notarization-in-mojave-and-catalina/ https://eclecticlight.co/2019/06/07/notarization-in-mojave-a... “ If you build your own apps, using Automator, AppleScript, another scripting system or even Xcode, you don’t need to acquire a developer ID, code signing certificate, and start notarizing them unless you provide them to others via the Internet. Catalina still runs apps which haven’t been notarized or even signed, including those built after 1 June 2019. But you may find them more complex to run, and they don’t of course benefit from any of new security protection unless they’re signed and hardened. Apple has, though, announced that it intends that a future version of macOS (possibly 10.16) will not run unsigned code so readily. How that will affect those who build their own apps isn’t yet clear. Let’s get notarization sorted first.” Therefore, I assume right-clicking the app and choosing “Open” will still be available to bypass the first-run check for a downloaded software, as it is today.