Re: Upcoming MacOS 14.5 with software “notarization” requirements
richmondmathewson at gmail.com
Wed Apr 10 13:34:47 EDT 2019
I don't think it's some secret plan either, but I do think it will make
things awkward for types like me
who wish to distribute demo standalones without any "undue fuss" as I am
able to at the moment via
sites such as macUpdate and via direct download from DropBox.
The problem, and it will always be a problem, is how to balance the
requirements for system security against
I, for one, do not want people to vet my reading list before I buy books!
But, I'm an odd sort of person insofar as I won't hold it against the
producers of an operating system
if a piece of software I install on my computer hoses MY computer:
anymore than I am likely to sue
the makers of my underpants because a wasp bit my bottom when I sat on it.
I am absolutely convinced that Apple's move is a direct result of the
fact that fewer and fewer
people are prepared to accept responsibility for their actions, and are
always looking round for
someone to blame for the results of their decisions.
On 10.04.19 19:22, J. Landman Gay via use-livecode wrote:
> There's no review, it's an automated process that adds a security key
> to the files. It sounds a lot like the RSA public/private keys I added
> to my current project to verify that the files hadn't been tampered
> with. That's definitely a security thing. Gatekeeper will be updated
> to check that the keys match.
> If you plan to distribute in the App Store, the security keys must be
> in place before the app is submitted for normal review. If you will be
> distributing privately, users with newer versions of OSX may not be
> able to launch the app if is not secured. If you already have apps in
> the App Store they won't be affected.
> While I'm not happy with the general direction Apple is taking with
> OSX, their main PR lately has been how much more secure the OS is
> compared to most others. They've been caught recently with a few bad
> submissions their review missed, which may have triggered this new
> I'm not happy with this because the submission process was already bad
> enough, but I don't think it's some secret plan to take over all our
> Jacqueline Landman Gay | jacque at hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On April 10, 2019 6:15:45 AM Paul Dupuis via use-livecode
> <use-livecode at lists.runrev.com> wrote:
>> From the first link to the Apple developer site:
>> Beginning in macOS 10.14.5, all new or updated kernel extensions and all
>> software from developers new to distributing with Developer ID must be
>> notarized in order to run. In a future version of macOS, notarization
>> will be required by default for all software."
>> It seems that this is the next step in the inevitable move by Apple to
>> require all macOS applications to be sold through the Apple Store where
>> they will take their desired 30% cut from your revenue. Notarization is
>> the step that say all apps must go through Apple (automated) review. It
>> is being sold under the guise of "security" and "trust", after all, who
>> can argue with those. Notarized apps can still be sold and distributed
>> as you like, but the next step after that (with OSX 10.15 or later) will
>> surely be the move to unify OSX apps under sole Apple distributorship
>> like iOS apps.
>> Oh Joy!
>> On 4/9/2019 10:27 PM, Tariel Gogoberidze via use-livecode wrote:
>>> It seems that as of MacOS 14.5 all new and updated apps would not
>>> run without been “notarized” by Apple.
>>> Anybody on the list who “notarized” their Mac OS app or who knows
>>> what it takes ?
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>>> subscription preferences:
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the Use-livecode