I agree Bob. But there really does need to be a basis of trust or you’re asking for trouble. I did that once and very much regretted it - downloaded a demo installer for an app I was interested in. What I got was a trojan horse that attempted to divert my internet connection in an ploy to send me to a PayPal phishing site. Fortunately I caught it in time and learned my lesson. Certainly code signing isn’t fool proof but it could be easier!
> On Dec 11, 2018, at 2:30 PM, Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Agreed, but for a local deployment, like the company I work for, I should > never be forced to sign my apps. That would be onerous in my opinion. > > Bob S > > >> On Dec 11, 2018, at 14:26 , Knapp Martin via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> I think on Sierra and older there was a 3rd option in the security section >> to choose from “Anywhere” but that is gone in High Sierra and Mojave. There >> is a trick to get around this, outlined here: >> https://www.macworld.co.uk/how-to/mac-software/mac-app-unidentified-developer-3669596/ >> >> But you can’t really seriously (in my opinion) distribute apps this way. >> Code signing is a hassle but it’s only going to get worse. > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
