From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: developer not verified error
Date: Tue, 19 Nov 2019 10:06:41 +0100 [thread overview]
Message-ID: <FFB7EC85-5805-4955-97B8-0AD824B126D9@elvenkind.com> (raw)
In-Reply-To: <CAFMOkGVt2BOfEi4sVV_ekLpFUJbHChnPFWSXGjDo6_PMN=ECBQ@mail.gmail.com>
> On 18 Nov 2019, at 22:25, Alan Bowen <bowenalan03@gmail.com> wrote:
>
> This seems to be a problem peculiar to Catalina (macOS 10.15.1). There is a fix, as Otared and Glen have indicated.
>
> go to Apple menu -> Preferences -> Security & Privacy
> on the Security & Privacy, login, choose the tab General
> there choose, towards the bottom of that pane, under « Allow apps downloaded from: »
> choose the radio button App Store and identified developers
> click the button «allow anyway»
There is a easier / safer way: open de folder with ‘mtxrun’ in it using Finder. Then select
‘Open’ from the popup menu on the mtxrun executable. That will give you dialog with that
’This app was downloaded …’ error, but now with an extra ‘Open’ button on it. Click that,
and it will start mtxrun once. Running mtxrun itself this ways is pointless, but it makes
Apple start to remember that *you* trust this mtxrun binary, and from now on it can be
used normally.
On packaged distributed Apps you download from the web, you can also hold down CTRL while
opening the App so you don’t have to do the Finder step, but I am not certain that works with
command-line binaries (and cannot test any more since I already did the ‘fix’ above).
It is a bit tedious, but sort of I see Apple’s point. Making it harder to run downloaded
unsigned executables is probably a good thing.
Best wishes,
Taco
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-11-19 9:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 21:36 Alan Bowen
2019-11-16 9:02 ` Hans Hagen
2019-11-16 10:32 ` Otared Kavian
2019-11-16 16:09 ` Mojca Miklavec
2019-11-18 21:32 ` Henri Menke
2019-11-19 8:57 ` Hans Hagen
2019-11-16 22:27 ` Glen Helman
2019-11-17 16:30 ` Keith McKay
2019-11-18 21:25 ` Alan Bowen
2019-11-19 9:06 ` Taco Hoekwater [this message]
2019-11-19 9:41 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FFB7EC85-5805-4955-97B8-0AD824B126D9@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).