“Inkscape.app” can’t be opened because it is from an unidentified developer.

Bug #1363305 reported by Tim on 2014-08-29
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Inkscape
Undecided
Unassigned

Bug Description

The user must trust ALL applications from any developer, is it possible to get and make a signed installer?

Tim (timbeaudet) on 2014-08-29
information type: Private Security → Public
su_v (suv-lp) wrote :

On 2014-08-30 01:36 , Tim wrote:
> The user must trust ALL applications from any developer

This is not true, please read the related Inkscape FAQ (including the links there to the official Apple kb article) how to bypass it for individual apps (without lowering security system-wide):

http://inkscape.org/en/learn/faq/#Apple.27s_new_GateKeeper_security_feature_may_prevent_Inkscape_from_opening

> is it possible to get and make a signed installer?

Currently not (being able to sign applications for GateKeeper requires a Mac Developer Program membership which costs 99$ per year; none of the Inkscape developers nor of those producing OS X packages has such a paid membership).

tags: added: osx packaging
EmanueleSabetta (fmuaddib) wrote :

Many people are not technically wise enough to bypass the gatekeeper. I've seen it myself. Code Signing is a good thing for security, but Apple should really make digital signatures free for open source software. Meanwhile the inkscape team could rise the 99$ through an annual donation campaign via PayPal or something. I'm pretty sure that many developers working with Inkscape as professionals, like me, would be more than willingly to contribute some dollars each year to ensure a proper digital signature to Inkscape.

EmanueleSabetta (fmuaddib) wrote :

To understand the security risks, consider the following scenario: An user downloads the Inkscape package file from an unknown web site (very common). What he doesn't know is that the package is not the original Inkscape package, but it is infected with a trojan or contains malicious code. The user try to install the package on his Mac, but the Mac gatekeeper (wisely) prevents him from running the application because it is not signed. He searches on google and find the official FAQ on Inkscape.org website explaining how to bypass the gatekeeper check. He follows the instructions and install the malicious package in his system, with sore consequences.
Now you can see why a certified digital signature is a good security measure for apps. And this is why rising the 99$ with a donation campaign would be a good thing for Inkscape.

Liam P. White (liampwhite) wrote :

> Many people are not technically wise enough to bypass the gatekeeper.

I'd suggest that everyone read the FAQ /before/ attempting to use the program. The solutions to common problems there are more than enough to get you started, and if the material provided on how to allow Inkscape.app through Gatekeeper is too complex to understand (a few clicks), maybe this program isn't for you.

********

> An user downloads the Inkscape package file from an unknown web site (very common)

How common are we talking about here?

> What he doesn't know is that the package is not the original Inkscape package, but it is infected with a trojan or contains malicious code. The user try to install the package on his Mac, but the Mac gatekeeper (wisely) prevents him from running the application because it is not signed.

Just because an application has a code signature does not imply that it is not malware -- in fact, digitally signed OS X malware has occured before «http://nakedsecurity.sophos.com/2014/01/21/data-stealing-malware-targets-mac-users-in-undelivered-courier-item-attack/» and it will appear again.

> He searches on google and find the official FAQ on Inkscape.org website explaining how to bypass the gatekeeper check. He follows the instructions and install the malicious package in his system, with sore consequences.

In a system with proper permissions enforcement, and assuming no exploits in the OS itself were used in the creation of such an application, the amount of damage any such bundle could do to a system would be severely limited -- this does not necessarily protect against the application stealing data or attempting to cause physical (heat) damage to the machine

While I agree that a signed bundle would be nice to have, keep in mind that a code signature in no way guarantees the safety or reliability of an application bundle.

Bryce Harrington (bryce) wrote :

Aside from the questionable security of it that Liam describes, the $99/yr seems extortive to me, particularly given that we're a non-profit organization run entirely by volunteers. However, despite all that Emanuele's suggestion to raise it via a fundraiser seems a good idea - the users who will benefit from this can cover the costs of it and gain a smoother installation experience. But I think we'd want to raise enough to cover, say, 3 years at a minimum (plus assorted tithes and fees), so we'd need to target, say, $350 as a minimum.

If someone would like to take charge of organizing this fundraiser, please contact me or the Inkscape Board for guidance.

Qantas94Heavy (qantas94heavy) wrote :

We are tracking the progress of releasing a signed native macOS app here: https://gitlab.com/inkscape/inkscape/issues/84

Please follow there for any further progress. Thank you!

Changed in inkscape:
status: New → Invalid
tags: added: bug-migration
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.