“codesign”

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. Here's the link Thanks. I downloaded that and extracted your app: % xar -xf PATHmanager.pkg % cpio -i < com.chipcastle.pathmanager.pkg/Payload 58111 blocks I then dumped its code signature: % codesign -d -vvv --entitlements - PATHmanager.app Executable=/Users/quinn/Desktop/test/PATHmanager.app/Contents/MacOS/PATHmanager Identifier=com.chipcastle.pathmanager Format=app bundle with Mach-O thin (arm64) CodeDirectory v=20500 size=223078 flags=0x10000(runtime) hashes=6964+3 location=embedded Hash type=sha256 size=32 CandidateCDHash sha256=ed5d7d18f524cae6db2b57b2682ebfa61572510b CandidateCDHashFull sha256=ed5d7d18f524cae6db2b57b2682ebfa61572510b56d6a26c037c8cc003f1f1d3 Hash choices=sha256 CMSDigest=ed5d7d18f524cae6db2b57b2682ebfa61572510b56d6a26c037c8cc003f1f1d3 CMSDigestType=2 CDHash=ed5d7d18f524cae6db2b57b2682ebfa61572510b Signature size=9115 Authority=Apple Distribution: Chip

/usr/libexec/PlistBuddy -c Add :com.apple.security.get-task-allow bool true /tmp/my-app-debug-entitlements.plist /usr/libexec/PlistBuddy -c Add :com.apple.security.cs.disable-library-validation bool true /tmp/my-app-debug-entitlements.plist codesign --timestamp --options runtime --sign Developer ID Application: *** (***) --entitlements /tmp/my-app-debug-entitlements.plist --force /path/to/my-debug-binary I had no problems with the notarization process of the binary I signed this way. As you said, I will not distribute my application in this way. I will only distribute this binary to users I want to debug. Thanks.

I suspect that the sysextd crash is a known issue that seems to be caused by a race condition in the code (r. 99777199). The nesessionmanager crash is more likely to be caused by the properties in your sysex. The crashing thread looks like this: 5 Foundation 0x191f5c120 -[NSString initWithFormat:] + 52 6 nesessionmanager 0x100138ac0 -[NESMProviderManager createSystemExtensionErrorWithCode:extensionInfo:] + 440 7 nesessionmanager 0x100139558 -[NESMProviderManager createLaunchdPlistEntriesFromExtensionBundle:extensionInfo:error:] + 2464 8 nesessionmanager 0x1001399d8 __84-[NESMProviderManager listener:validateExtension:atTemporaryBundleURL:replyHandler:]_block_invoke + 212 NE is trying to validate your sysex, that’s failed, and it’s crashed trying to generate the error O-: Both of these are obviously bugs in our OS — these subsystems should fail rather than crash — and I encourage you to file bug reports about them. Include a sysdiagnose log and a copy of your built app (the broken one, not the fixed one). Plea

Gosh, there are two separate issues tangled up here: Code signing Override TLS server trust evaluation IMO they are completely separable. Let me start with code signing. If you distribute your product widely, it must be signed: If you’re targeting the Mac App Store, you can only submit a signed app. If you’re distributing directly, you product must be signed and notarised to pass Gatekeeper. If you’re not using Xcode then see the following docs for specific advice on how to sign your product: Creating distribution-signed code for macOS Packaging Mac software for distribution Regarding TLS server trust evaluation, that’s not really related to your code signing. You wrote: [quote='777675021, Atanu, /thread/777675, /profile/Atanu'] Upon investigating this online, we got to know there has to be codesigning (both app bundle and the dmg file ) along with notarization of the .dmg file in order to access keychain of [macOS] [/quote] That’s not entirely correct. It’s true the signing your app and your disk im

I raise this question again. Earlier you suggested: The easiest way to do this is use Xcode’s import/export feature. Launch Xcode, choose Xcode > Settings, select Accounts, select the account in question, then choose Export Apple ID and Code Signing Assets from the action (…) menu. In Xcode 16 I cannot find any import/export commands to move existing codesign certificates/keys to my second Mac. Probably it will easier to create a NEW individual codesign certificate for EVERY Mac I use?

Ok, I had to get some support from the tebako folks before I could reply. Here's the output of the codesign --verify -vvv PATHmanager.app command you suggested: Extract pkg contents /tmp λ xar -xf ~/code/ruby/PATHmanager.pkg Verify Bill of Materials /tmp λ lsbom com.chipcastle.pathmanager.pkg/Bom . 0 0/0 ./PATHmanager.app 40755 0/0 ./PATHmanager.app/Contents 40755 0/0 ./PATHmanager.app/Contents/Frameworks 40755 0/0 ./PATHmanager.app/Contents/Frameworks/libui.dylib 100644 0/0 925632 3337342204 ./PATHmanager.app/Contents/Info.plist 100644 0/0 1415 1981579098 ./PATHmanager.app/Contents/MacOS 40755 0/0 ./PATHmanager.app/Contents/MacOS/._PATHmanager 100755 0/0 0 0 ./PATHmanager.app/Contents/MacOS/PATHmanager 100755 0/0 30036560 1901427662 ./PATHmanager.app/Contents/PkgInfo 100644 0/0 8 742937289 ./PATHmanager.app/Contents/Resources 40755 0/0 ./PATHmanager.app/Contents/Resources/AppIcon.icns 100644 0/0 56310 2265036908 ./PATHmanager.app/Contents/_CodeSignature 40755 0/0 ./PATHmanager.app/Contents/_CodeSign

Sure. But at some point these things stop being technical questions and instead become a reflection of your policy. I agree/understand regarding the policy. I framed the question oddly, but I was really asking if that policy made sense (i.e., was there some other approach to do what I'm saying or is there anything unforseen that I'd encounter). I've already implemented it though and it seems to work out fine, so we'll stick with it. Yes. That is, in fact, the whole reason for a DR, in that it’s a cryptographically sound way for the code to identify itself, such that the system knows that version N+1 of your app is the ‘same code’ as version N. Ok, that's great. My concern was that what constitutes a DR (as emitted by codesign) could change in the future, and that same code meant the exact code the DR was computed for at the time it was run. This is obviously not the case since it is only reliant on certificate OIDs and such (so I'd assume if the signing certificate changes that would be the only thin

I have found that you can also check whether your app executable contains the aps-environment string. For example: grep -n -a aps-environment Payload/MyApp.app/MyApp It did not contain the string before the fix and it did after. This is probably similar to codesign -d --entitlements :- Payload/MyApp.app

Thank you @benjfromlondon for showing me the way! I had the same issue while building using the Xcode@5 in Azure Pipelines although the project was otherwise configured as it should and as many StackOverflow threads indicated it should. I will add below more information about how I fixed the issue and troubleshooting. The fix The Xcode@5 Azure Pipelines task does not sign the archive by default: # Signing & provisioning #signingOption: 'nosign' # 'nosign' | 'default' | 'manual' | 'auto'. Signing style. Default: nosign. #signingIdentity: # string. Optional. Use when signingOption = manual. Signing identity. So I added the following to my Yaml pipeline: (signingOption, signingIdentity and provisioningProfileName) - task: Xcode@5 displayName: 'Build IPA' inputs: actions: 'clean build' configuration: 'Release' sdk: 'iphoneos' xcWorkspacePath: 'ios/MyApp.xcworkspace' workingDirectory: '$(Build.SourcesDirectory)' scheme: 'MyApp' packageApp: true signingOption: 'manual' signingIdentity: 'iPhone Distribution' pr