Gatekeeper code signing is broken #423
Comments
|
This is normal, if you haven't adjusted security settings. Go to the "Security and Privacy" panel in System Preferences, in the general tab, set "Allow apps downloaded from:" to Anywhere. |
|
Thanks, but I’m afraid this is not great advice for most users. :) But yeah, since code signing is broken for nvALT at the moment, right-clicking the .app and choosing “Open” does the trick (and circumvents Gatekeeper for just this one app). |
|
Ah, that's what you were after! I follow now. |
|
You’re right, I should change the title to reflect that this issue is about Gatekeeper being broken (and that I’m not looking for a workaround). |
frankrausch
changed the title
|
Yeah, I'm still wracking my brain to figure out why this happens. The
app is codesigned with a wildcard developer ID that I use successfully
with other distributions, and the binary passes `codesign` validation. I
think one of the bundled binaries may be causing this.
…-Brett
On 4 Jan 2017, at 10:19, Frank Rausch wrote:
Thanks, but I’m afraid this is not great advice for most users. :)
The system setting should never be changed to allow launching unsigned
apps globally.
But yeah, since code signing is broken for nvALT at the moment,
right-clicking the .app and choosing “Open” does the trick (and
circumvents Gatekeeper for just this one app).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#423 (comment)
|
|
@ttscoff Here's the likely issue:
Specifically, there's broken symlinks in Sparkle: P.S. You might want to update to a newer version of Sparkle. |
|
Ok, I found those symbolic links and removed, checked the built product
for any other broken links, and ran spctl again, still rejected (but
without any helpful error message). Any other thoughts?
…-Brett
On 19 Jan 2017, at 19:11, Kent Sutherland wrote:
@ttscoff Here's the likely issue:
`spctl --verbose=4 --assess --type execute nvALT.app`:
`/Applications/nvALT.app/: rejected (invalid destination for symbolic
link in bundle)`
Specifically, there's broken symlinks in Sparkle:
```
Sparkle.framework//Versions/A/Resources:
lrwxr-xr-x 1 kent admin 84 Nov 1 12:44 fr_CA.lproj ->
/Users/andym/Development/Build
Products/Release/Sparkle.framework/Resources/fr.lproj
Sparkle.framework//Versions/A/Resources/fr.lproj:
lrwxr-xr-x 1 kent admin 84 Nov 1 12:44 fr.lproj ->
/Users/andym/Development/Build
Products/Release/Sparkle.framework/Resources/fr.lproj
```
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#423 (comment)
|
|
You can give codesign a shot and see if it comes up with anything:
With the broken symlinks I couldn't get it to run cleanly (presumably it was choking on them), but maybe that'll turn something up. |
|
Woohoo, I got it! I'll put an update out shortly.
-=
…On 19 Jan 2017, at 19:11, Kent Sutherland wrote:
@ttscoff Here's the likely issue:
`spctl --verbose=4 --assess --type execute nvALT.app`:
`/Applications/nvALT.app/: rejected (invalid destination for symbolic
link in bundle)`
Specifically, there's broken symlinks in Sparkle:
```
Sparkle.framework//Versions/A/Resources:
lrwxr-xr-x 1 kent admin 84 Nov 1 12:44 fr_CA.lproj ->
/Users/andym/Development/Build
Products/Release/Sparkle.framework/Resources/fr.lproj
Sparkle.framework//Versions/A/Resources/fr.lproj:
lrwxr-xr-x 1 kent admin 84 Nov 1 12:44 fr.lproj ->
/Users/andym/Development/Build
Products/Release/Sparkle.framework/Resources/fr.lproj
```
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#423 (comment)
|
I get this message for v2.2.7 (125) on two different computers (one on El Cap 10.11.6, one on Sierra 10.12.1):
.dmgfrom http://brettterpstra.com/2016/11/14/nvalt-2-dot-2-7-everythingll-be-fine//ApplicationsfolderThe text was updated successfully, but these errors were encountered: