Code Signature is no longer valid

[dkav]

codesign --verbose --deep-verify /Applications/QGIS*.app/
/Applications/QGIS.app/: a sealed resource is missing or invalid

[dkav]

codesign -d -vvvv /Applications/QGIS*.app/
Executable=/Applications/QGIS.app/Contents/MacOS/QGIS
Identifier=org.qgis.qgis3
Format=app bundle with Mach-O thin (x86_64)
CodeDirectory v=20200 size=3694 flags=0x0(none) hashes=110+3 location=embedded
VersionPlatform=1
VersionMin=658688
VersionSDK=658944
Hash type=sha256 size=32
CandidateCDHash sha256=d1528247c524c3ac8ea69af7f26c23b005744402
CandidateCDHashFull sha256=d1528247c524c3ac8ea69af7f26c23b0057444028b7165ddc0b9f5c74915b1e1
Hash choices=sha256
CMSDigest=d1528247c524c3ac8ea69af7f26c23b0057444028b7165ddc0b9f5c74915b1e1
CMSDigestType=2
Page size=4096
CDHash=d1528247c524c3ac8ea69af7f26c23b005744402
Signature size=9015
Authority=Developer ID Application: Open Source Geospatial Foundation (4F7N4UDA22)
Authority=Developer ID Certification Authority
Authority=Apple Root CA
Timestamp=Feb 24, 2021 at 03:51:06
Info.plist entries=19
TeamIdentifier=4F7N4UDA22
Sealed Resources version=2 rules=13 files=29342
Internal requirements count=1 size=176

[dkav]

This issue is still present in 3.32.3-Lima. Using Signet the following error is identified:

/Applications/QGIS.app/Contents/Resources/python/site-packages/cmake/data/CMake.app error -67028 bundle format unrecognized, invalid, or unsuitable

[dkav]

Here is a fuller output:

/Applications/QGIS.app/Contents/MacOS/Designer.app is signed but not Notarized.
/Applications/QGIS.app/Contents/MacOS/qgis_process.app is signed but not Notarized.
/Applications/QGIS.app/Contents/Resources/python/site-packages/cmake/data/CMake.app error -67028 bundle format unrecognized, invalid, or unsuitable
/Applications/QGIS.app/Contents/Resources/python/site-packages/cmake/data/CMake.app isn't signed or recognised.

[agiudiceandrea]

@dkav is the issue still valid?

[dkav]

@agiudiceandrea on version 3.36 the same errors are reported. So yes the issue is still valid.

[agiudiceandrea]

Maybe @jef-n knows if this is actually an issue and if it is possible to fix it.
qgis/QGIS#55663 is probably related to this issue.

[dkav]

If I remember correctly, the issue described in qgis/QGIS#55663 was what lead me to running the tests in the first place. Earlier builds did not have this problem.

[dkav]

It looks like we should wait for the outcome of qgis/QGIS-Enhancement-Proposals#270. (This supersedes the unfunded qgis/QGIS-Enhancement-Proposals#218.)