Sigil-2.3.0 Released - Page 2

KevinH · Today, 07:09 PM

Okay, I tested using a Sigil.dmg and when downloaded from github to my Mac it sure enough had the com.apple.quarantine attribute set.

kbhend@MacBook-Pro Desktop % ls -a@l *.dmg
-rw-r--r--@ 1 kbhend staff 198173869 16 Aug 19:04 Sigil.dmg
com.apple.macl 72
com.apple.metadata:kMDItemDownloadedDate 53
com.apple.metadata:kMDItemWhereFroms 684
com.apple.quarantine 57

but worse yet, after double clicking it and copying the Sigil.app out of it, it too was marked with com.apple.quarantine and it generated that horrid error message even though it was properly signed and notarized.

So using dmg is not going to work either unless I can somehow sign and notarize an entire dmg.

Not something I want to do.

DiapDealer · Today, 07:21 PM

Is Apple really so petty that they would add the quarantine attribute to anything downloaded from Github?!

KevinH · Today, 07:49 PM

Quote:

Originally Posted by DiapDealer

Is Apple really so petty that they would add the quarantine attribute to anything downloaded from Github?!

Yes but they are equally petty about all non-Apple external sources!

Only using curl to move the file results in a download that does not have com.apple.quarantine set.

I tried recursively trying to use xattr -d but they add it to every single file, symbolic link, directory, socket, special character block, etc. It is a real pisser to remove. Your only real chance to remove it is *before* trying to unpack the archive.

This really stinks. Why does it matter that you downloaded an archive or app from github (or anyplace) as long as the application itself inside the archive is fully signed and notarized?

Apple is truly becoming a real bastard using Fear, Uncertainty, and Doubt (FUD) to drive developers to its Mac App store.

KevinH · Today, 08:34 PM

I have been reading up on this, and Apple's GateKeeper (which is what com.apple.quarantine turns on) now requires that there be no "dangling rpaths" in any place in your app but that means when macdeployqt moves the Qt frameworks in it can not just add new rpaths, it must remove the old rpaths otherwise they are considered "dangling".

Worse yet that must be true for every executable and every shared library in your app.

This is going to take lots of work to check for dangling rpaths as neither their signing process or notarization checks for that.

ARRRRGGGGGGGHHHHHHH!

Today, 07:09 PM	#16
KevinH Sigil Developer Posts: 7,937 Karma: 5449552 Join Date: Nov 2009 Device: many	Okay, I tested using a Sigil.dmg and when downloaded from github to my Mac it sure enough had the com.apple.quarantine attribute set. kbhend@MacBook-Pro Desktop % ls -a@l .dmg -rw-r--r--@ 1 kbhend staff 198173869 16 Aug 19:04 Sigil.dmg com.apple.macl 72 com.apple.metadata:kMDItemDownloadedDate 53 com.apple.metadata:kMDItemWhereFroms 684 com.apple.quarantine 57 but worse yet, after double clicking it and copying the Sigil.app out of it, it too was marked with com.apple.quarantine and it generated that horrid error message even though it was properly signed and notarized. So using dmg is not going to work either unless I can somehow sign and notarize an entire dmg. Not something I want to do. Last edited by KevinH; Today at 07:41 PM.*

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Sigil-1.5.1 Released	DiapDealer	Sigil	27	04-15-2021 10:27 AM
Sigil-1.2.0 Released	DiapDealer	Sigil	77	07-16-2020 12:55 PM
Sigil-0.9.7 Released	DiapDealer	Sigil	90	11-10-2016 01:30 PM
Sigil-0.9.6 Released	DiapDealer	Sigil	69	10-29-2016 10:35 AM
Sigil-0.8.900 released for testing - Wait for Sigil-0.8.901	KevinH	Sigil	106	10-04-2015 10:41 AM

Today, 07:21 PM	#17
DiapDealer Grand Sorcerer Posts: 27,773 Karma: 198099188 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Is Apple really so petty that they would add the quarantine attribute to anything downloaded from Github?!

Today, 08:34 PM	#19
KevinH Sigil Developer Posts: 7,937 Karma: 5449552 Join Date: Nov 2009 Device: many	I have been reading up on this, and Apple's GateKeeper (which is what com.apple.quarantine turns on) now requires that there be no "dangling rpaths" in any place in your app but that means when macdeployqt moves the Qt frameworks in it can not just add new rpaths, it must remove the old rpaths otherwise they are considered "dangling". Worse yet that must be true for every executable and every shared library in your app. This is going to take lots of work to check for dangling rpaths as neither their signing process or notarization checks for that. ARRRRGGGGGGGHHHHHHH!