Re:Notarizing Your Mac Software for macOS Catalina
by ridgeguy on Monday October 07, 2019 @09:23AM
(#21180463)
>"right click > open" brings up an admin challenge/authentication if executed by a non-admin user.
[ Parent
| on HN ]
Re:Notarizing Your Mac Software for macOS Catalina
by Wowfunhappy on Monday October 07, 2019 @09:47AM
(#21180696)
Don't know if it still works, but I used to get around this on school computers by loading the app binary (SomeApp.app/Contents/macOS/SomeApp) in the Terminal.
Gatekeeper really isn't a stringent measure, it just protects people who don't know what they're doing.
Re:Notarizing Your Mac Software for macOS Catalina
by e12e on Monday October 07, 2019 @02:33PM
(#21184352)
Interesting. So it's not implemented as a check on fork()/exec() for example? (checking an xattr shouldn't be too onerous to do practically. Not sure I think it's a good idea. Then again, we've had the "exec" bit for many decades...).
Ed: seems there is a more general check now - but limited to checking against known "malware" - not "whitelist" (motorized) https://news.ycombinator.com/item?id=21180317
Re:Notarizing Your Mac Software for macOS Catalina
by Communitivity on Monday October 07, 2019 @09:54AM
(#21180773)
I still use this trick sometimes, because it's a way to get stdout logging output you might not otherwise see. Sometimes it leads to a quick pinpoint of your issue.
Re:Notarizing Your Mac Software for macOS Catalina
by Wowfunhappy on Monday October 07, 2019 @10:16AM
(#21181045)
Oh, I do that too. Completely different purpose though.