Search results for

“codesign”

3,223 results found

Post

Replies

Boosts

Views

Activity

Code Signing -- errSecInternalComponent, unable to build self-signed root for signer "Developer ID Application..."
I am a developer on a project at work. I recently got a new laptop; however, since then I have been unable to build/deploy our application. I received a copy of the Developer ID Application certificate and Developer ID Installer certificate from a fellow developer. Note, everything works on their machine with these certificates. I have gone through the steps documented here https://developer.apple.com/forums/thread/712005 When I run security find-identity -p codesigning, I have two certificates that show up. one for my User and one for the Developer ID Application that my colleague gave me. Both show up as matching and valid identities. When I try to codesign MyTrue, as documented in the link above, using Apple Development works; however, the Developer ID Application identity does not. I get a errSecInternalComponent error. ahenderson@ahendersonmacbook [17:29:23] [~/Downloads] -> % codesign -s Apple Development -f MyTrue -vvv MyTrue: replacing existing signature MyTrue: signed Ma
3
0
996
Nov ’24
Does the Team ID on Apple Developer Portal need to match the one on Keychain?
Hello, I was trying to solve the error Command CodeSign failed with a nonzero exit code that occurs when I try to archive and publish my app. I realized the Team IDs on the Portal (To right corner next to my name eg Pete Park - ABC1D2E334) and my Mac Keychain Acces (eg Pete Park - XYZ9W8V776) do not match. The number on KeyChain Access, is that's a Team ID. (clueless self learner here) If yes, do they need to match? Any suggestion for the CodeSign error? Is errSecInternalComponent the error? Sorry if these questions are obvious or stupid. Thanks so much for any advice.
1
0
1.1k
Oct ’24
Gatekeeper refuses to start application from downloaded DMG
Hello, I have an application which uses a helper[1] to download[2] files. When files download is a DMG and user mounts the image to run the application from this DMG it doesn't pass Gatekeeper. It presents the Application XYZ.app can't be opened.. Same file downloaded via Safari shows a different dialog, the XYZ.app is an app downloaded from the internet. Are you sure you want to open it? In the system log I see this line: exec of /Volumes/SampleApp/SampleApp.app/Contents/MacOS/SampleApp denied since it was quarantined by Downloadx20Helper and created without user consent, qtn-flags was 0x00000187 The application is running sandboxed and hardened, the main application has com.apple.security.files.downloads.read-write entitlement. Everything is signed by DeveloperID and passes all checks[3]. I tried to check the responsible process[4] of the helper. Then trivial stuff like download folder access in System Settings/Privacy & Security/Files & Folders. Everything seems to be fine. For what it worths the v
13
0
1.6k
Oct ’24
Outgoing SSL connections fail on macOS 15, work fine on earlier versions
The OpenSSL library interface to Allegro Common Lisp system stopped working with macOS 15.x (15.0.1 and 15.1). We have tried many versions of OpenSSL. 1.1.1t (which we built ourselves), 3.0.x, 3.3.x, 3.4.0. All work fine on macOS 14 and earlier. All fail on macOS 15. What is bizarre about the failure: we can load the SSL libraries fine, but when we try to make an outgoing connection it fails (with varying errors). Also, trying to use lldb to debug just hangs, once we step into the SSL libraries. More specifically, using Homebrew OpenSSL 3.0.15 gives an exception that we see in lldb, but we cannot step into SSL_ctrl(), which is in libssl.3.dylib, provided by Homebrew. We have also tried a version of OpenSSL 1.1.1t that we built ourselves (and codesigned and is included in the notarized app), and it fails with a SEGV, rather than the error below, which is using 3.0.15: What started this were errors using the OpenSSL libraries. Here's the use case: cl-user(2): (net.aserve.client:do-http-request https://
23
0
1.7k
Oct ’24
Reply to "How to" for dext distribution
I thought an example of the command line output might be useful, so here is the output of my specific test app: Command: codesign -dvvv --ent :- HIDKeyboardApp.app Entitlement block at end of output: .... com.apple.application-identifierVKPFXJZWAV.com.appledts.kevine.KeyboardAppcom.apple.developer.system-extension.installcom.apple.developer.team-identifierVKPFXJZWAVcom.apple.security.app-sandboxcom.apple.security.files.user-selected.read-only Command: security cms -D -i HIDKeyboardApp.app/Contents/embedded.provisionprofile Entitlement block at end of output: .... Entitlements com.apple.developer.system-extension.install com.apple.application-identifier VKPFXJZWAV.com.appledts.kevine.KeyboardApp keychain-access-groups VKPFXJZWAV.* com.apple.developer.team-identifier VKPFXJZWAV ExpirationDate 2042-10-07T18:15:36Z Name Mac Team Direct Provisioning Profile: com.appledts.kevine.KeyboardApp ProvisionsAllDevices TeamIdentifier VKPFXJZWAV TeamName Kevin Elliott TimeToLive 6570 UUID 339032ce-3f1c-4b56
Oct ’24
Reply to "How to" for dext distribution
Stepping back for a moment, I think it's important to understand what's actually going on here. The starting point here is that there are two sets of data at work here: (1) Your Xcode project has a set of data about your app, particularly the entitlement list, which are embedded in the codes signature of your app. That data can actually be viewed with the command: codesign -dvvv --ent :- (2) The developer portal has a set of data about apps bundle ID, particularly the entitlement list, which is used to generate a provisioning profile which will be embedded inside your apps bundle. That data can actually be viewed with one of the following commands*: *iOS and macOS use slightly different names and locations, a fact which is annoying when you jump back and forth between platforms. I wrote a script years ago which simply tried all 4 possibilities and am now working hard to not remember which is which. security cms -D -i /embedded.mobileprovision security cms -D -i /embedded.provisionprofile security cm
Oct ’24
Reply to App Groups and macOS 15
Thanks for confirming that. I would expect this to work. When you use an iOS-style app group ID in a Mac Catalyst app, Xcode generates a provisioning profile to authorise that use. So this use falls under case D in App Groups: macOS vs iOS: Fight!. Consider this tiny test app I just created: % codesign -d --entitlements - Debug-maccatalyst/Test766580.app Executable=/Users/quinn/Library/Developer/Xcode/DerivedData/Test766580-beavevigoaauqrfhkfssttblupau/Build/Products/Debug-maccatalyst/Test766580.app/Contents/MacOS/Test766580 [Dict] … [Key] com.apple.security.application-groups [Value] [Array] [String] group.eskimo1.test [Key] com.apple.security.get-task-allow [Value] [Bool] true … % security cms -D -i Debug-maccatalyst/Test766580.app/Contents/embedded.provisionprofile | plutil -p - { … Entitlements => { … com.apple.security.application-groups => [ 0 => group.eskimo1.test ] … } … } Note the presence of com.apple.security.get-task-allow, showing that this is a development build. And that group
Topic: Code Signing SubTopic: Entitlements Tags:
Oct ’24
Reply to "How to" for dext distribution
Thank you both for the responses. We have accomplished the Team Agent request for entitlements for PCI DriverKit - it looks like I am able to perform all other tasks necessary at my admin level on the developer portal. Following ssmith_c's advice, I was able to build, sign, notarize, and deploy a dext within a hosting application, the added export and manual selection seemed to be the difference I needed. However, I'm still encountering some issues with Xcode 15.2 when trying to make a distributable application that works with the dext (#3 of the software types listed above). One worked, and one seemed to not work. The not working one is crashing based on: Exception Type: EXC_CRASH (SIGKILL (Code Signature Invalid)) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: CODESIGNING 1 Taskgated Invalid Signature Using codesign to inspect the signature, it seems ok, but I likely am just not seeing the issue: daniek3@MacBook-Pro Project % codesign -dv --verbose=3 A
Oct ’24
"Command CodeSign failed with a nonzero exit code" after enrollment to a development team
Hi all, I have two apple accounts. Stupidly my project is written in Account A and my paid developer account is Account B. When I tried to archive and publish under Account A, it says Team XXX (Personal Team) is not enrolled in the Apple Developer Program. But when I add a team to Account B, Command CodeSign failed with a nonzero exit code. I know it is not the code itself because it runs fine when I use Account A. Just couldn't publish. Any advice? Many many thanks
Topic: Code Signing SubTopic: General
1
0
432
Oct ’24
Reply to Notarization succeeds, but gatekeeper check still fails, with QtWebEngine
I dig into the issue, hence I have 2 executable files in the app under xxx.app/Contents/MacOS: M and N, M is in the Info.plist and is the CFBundleExecutable file, after signed the M with codesign, returns with this: signed app bundle with Mach-O thin (arm64) [CFBundleIdentifier]; otherwise, the N signed with codesign in the same way, returned with this: signed Mach-O thin (arm64) [N]. And I installed the APP on my machine, when I clicked the M executable file, seems it passed the gatekeeper, but I clicked the N, seems the gatekeeper check fails. I am not sure it's the reason.
Topic: Code Signing SubTopic: Notarization Tags:
Oct ’24
Command CodeSign failed with a nonzero exit code
I have not been able to open any of my apps since I uploaded my latest update midOctober 2023. Previously I have tried everything on forums from removing derived data, adding new options in build folder and more. Since then I have wasted hours trying to open any app from my iCloud / hard disk and I wonder if part of the problem is caused by backing up to iCloud, as I can open from an external hard disk. It takes almost as long to upload from hard disk than cloud so whole thing annoying, does this add clues to this frustrating problem ? Also when I opened one of my apps it had made hundreds of unassigned assets that all had to be removed individually. I have no idea how to continue with my work I have three other apps in progress, but am halted at present but such a stupid small detail. // here is full commet /Users/ruwickigmail.com/Desktop/0-APPS-2023/InstaAnimates/InstaAnimates.xcodeproj: warning: Unable to find a target which creates the host product for value of $(TEST_HOST) '/Users/ruwickigmail.com/Deskto
1
0
758
Oct ’24
Notarization succeeds, but gatekeeper check still fails, with QtWebEngine
I am packaging an app with QtWebEngine in it, after codesign the app and the QtWebEngine Framework, the app can run properly. The codesign result is: valid on disk staisfies its Designated requirements Then I notarized and stapled the dmg file, after the dmg installed on Mac, gatekeeper still failed the check. Here is the result for spctl: spctl -a -t open -vvv --context context:primary-signatue Remote Graphics Workstation_.dmg Remote Graphics Workstation_.dmg: rejected source=Insufficient Context Need help to identify the codesign process and the root cause why gatekeeper fail here, thanks.
3
0
772
Oct ’24
Reply to Issues with Embedding Python Interpreter in MacOS App Distributed via TestFlight
Hello, I still get some errors: Process tccd Prompting policy for hardened runtime; service: kTCCServiceAppleEvents requires entitlement com.apple.security.automation.apple-events but it is missing for accessing={TCCDProcess: identifier=com.sampleApp.app, pid=72680, auid=502, euid=502, binary_path=[PATH_TO_APP]]}, requesting={TCCDProcess: identifier=com.apple.appleeventsd, pid=831, auid=55, euid=55, binary_path=/System/Library/CoreServices/appleeventsd}, Process python3.11 flock failed to lock list file (): errno = 35 Basically the changes I made are: Used the code from 'Running a Child Process with Standard Input and Output', it works great, thanks! Made a Run script to sign the executable: codesign -s - -i com.sampleApp.app.Python -o runtime --entitlements $ENTITLEMENTS_PATH -f $BINARY_PATH And then created a copy build phase to place the executable in Executables destination. Code sign on copy is selected. (Verified that it is placed in MacOS folder, and correctly signed.) These are the Entitlemen
Topic: Code Signing SubTopic: Entitlements Tags:
Oct ’24
Issue codesign on VS Code and XCode
Hello, I'm starting to develop a new app with Flutter on VS Code. I. struggle to start because I face constantly this error : Error (Xcode): Target debug_unpack_ios failed: Exception: Failed to codesign /Users/Nylan1/Desktop/Thoughts./Flutter Application/app_v0/app_v0/build/ios/Debug-iphonesimulator/Flutter.framework/Flutter with identity -. Can someone pleas help me to solve that ? I've checked on Xcode and the macOS signing certificate is on Development but the IOS one is not working.
0
0
547
Oct ’24
Code Signing -- errSecInternalComponent, unable to build self-signed root for signer "Developer ID Application..."
I am a developer on a project at work. I recently got a new laptop; however, since then I have been unable to build/deploy our application. I received a copy of the Developer ID Application certificate and Developer ID Installer certificate from a fellow developer. Note, everything works on their machine with these certificates. I have gone through the steps documented here https://developer.apple.com/forums/thread/712005 When I run security find-identity -p codesigning, I have two certificates that show up. one for my User and one for the Developer ID Application that my colleague gave me. Both show up as matching and valid identities. When I try to codesign MyTrue, as documented in the link above, using Apple Development works; however, the Developer ID Application identity does not. I get a errSecInternalComponent error. ahenderson@ahendersonmacbook [17:29:23] [~/Downloads] -> % codesign -s Apple Development -f MyTrue -vvv MyTrue: replacing existing signature MyTrue: signed Ma
Replies
3
Boosts
0
Views
996
Activity
Nov ’24
Does the Team ID on Apple Developer Portal need to match the one on Keychain?
Hello, I was trying to solve the error Command CodeSign failed with a nonzero exit code that occurs when I try to archive and publish my app. I realized the Team IDs on the Portal (To right corner next to my name eg Pete Park - ABC1D2E334) and my Mac Keychain Acces (eg Pete Park - XYZ9W8V776) do not match. The number on KeyChain Access, is that's a Team ID. (clueless self learner here) If yes, do they need to match? Any suggestion for the CodeSign error? Is errSecInternalComponent the error? Sorry if these questions are obvious or stupid. Thanks so much for any advice.
Replies
1
Boosts
0
Views
1.1k
Activity
Oct ’24
Gatekeeper refuses to start application from downloaded DMG
Hello, I have an application which uses a helper[1] to download[2] files. When files download is a DMG and user mounts the image to run the application from this DMG it doesn't pass Gatekeeper. It presents the Application XYZ.app can't be opened.. Same file downloaded via Safari shows a different dialog, the XYZ.app is an app downloaded from the internet. Are you sure you want to open it? In the system log I see this line: exec of /Volumes/SampleApp/SampleApp.app/Contents/MacOS/SampleApp denied since it was quarantined by Downloadx20Helper and created without user consent, qtn-flags was 0x00000187 The application is running sandboxed and hardened, the main application has com.apple.security.files.downloads.read-write entitlement. Everything is signed by DeveloperID and passes all checks[3]. I tried to check the responsible process[4] of the helper. Then trivial stuff like download folder access in System Settings/Privacy & Security/Files & Folders. Everything seems to be fine. For what it worths the v
Replies
13
Boosts
0
Views
1.6k
Activity
Oct ’24
Outgoing SSL connections fail on macOS 15, work fine on earlier versions
The OpenSSL library interface to Allegro Common Lisp system stopped working with macOS 15.x (15.0.1 and 15.1). We have tried many versions of OpenSSL. 1.1.1t (which we built ourselves), 3.0.x, 3.3.x, 3.4.0. All work fine on macOS 14 and earlier. All fail on macOS 15. What is bizarre about the failure: we can load the SSL libraries fine, but when we try to make an outgoing connection it fails (with varying errors). Also, trying to use lldb to debug just hangs, once we step into the SSL libraries. More specifically, using Homebrew OpenSSL 3.0.15 gives an exception that we see in lldb, but we cannot step into SSL_ctrl(), which is in libssl.3.dylib, provided by Homebrew. We have also tried a version of OpenSSL 1.1.1t that we built ourselves (and codesigned and is included in the notarized app), and it fails with a SEGV, rather than the error below, which is using 3.0.15: What started this were errors using the OpenSSL libraries. Here's the use case: cl-user(2): (net.aserve.client:do-http-request https://
Replies
23
Boosts
0
Views
1.7k
Activity
Oct ’24
Reply to "How to" for dext distribution
I thought an example of the command line output might be useful, so here is the output of my specific test app: Command: codesign -dvvv --ent :- HIDKeyboardApp.app Entitlement block at end of output: .... com.apple.application-identifierVKPFXJZWAV.com.appledts.kevine.KeyboardAppcom.apple.developer.system-extension.installcom.apple.developer.team-identifierVKPFXJZWAVcom.apple.security.app-sandboxcom.apple.security.files.user-selected.read-only Command: security cms -D -i HIDKeyboardApp.app/Contents/embedded.provisionprofile Entitlement block at end of output: .... Entitlements com.apple.developer.system-extension.install com.apple.application-identifier VKPFXJZWAV.com.appledts.kevine.KeyboardApp keychain-access-groups VKPFXJZWAV.* com.apple.developer.team-identifier VKPFXJZWAV ExpirationDate 2042-10-07T18:15:36Z Name Mac Team Direct Provisioning Profile: com.appledts.kevine.KeyboardApp ProvisionsAllDevices TeamIdentifier VKPFXJZWAV TeamName Kevin Elliott TimeToLive 6570 UUID 339032ce-3f1c-4b56
Replies
Boosts
Views
Activity
Oct ’24
Reply to "How to" for dext distribution
Stepping back for a moment, I think it's important to understand what's actually going on here. The starting point here is that there are two sets of data at work here: (1) Your Xcode project has a set of data about your app, particularly the entitlement list, which are embedded in the codes signature of your app. That data can actually be viewed with the command: codesign -dvvv --ent :- (2) The developer portal has a set of data about apps bundle ID, particularly the entitlement list, which is used to generate a provisioning profile which will be embedded inside your apps bundle. That data can actually be viewed with one of the following commands*: *iOS and macOS use slightly different names and locations, a fact which is annoying when you jump back and forth between platforms. I wrote a script years ago which simply tried all 4 possibilities and am now working hard to not remember which is which. security cms -D -i /embedded.mobileprovision security cms -D -i /embedded.provisionprofile security cm
Replies
Boosts
Views
Activity
Oct ’24
Reply to App Groups and macOS 15
Thanks for confirming that. I would expect this to work. When you use an iOS-style app group ID in a Mac Catalyst app, Xcode generates a provisioning profile to authorise that use. So this use falls under case D in App Groups: macOS vs iOS: Fight!. Consider this tiny test app I just created: % codesign -d --entitlements - Debug-maccatalyst/Test766580.app Executable=/Users/quinn/Library/Developer/Xcode/DerivedData/Test766580-beavevigoaauqrfhkfssttblupau/Build/Products/Debug-maccatalyst/Test766580.app/Contents/MacOS/Test766580 [Dict] … [Key] com.apple.security.application-groups [Value] [Array] [String] group.eskimo1.test [Key] com.apple.security.get-task-allow [Value] [Bool] true … % security cms -D -i Debug-maccatalyst/Test766580.app/Contents/embedded.provisionprofile | plutil -p - { … Entitlements => { … com.apple.security.application-groups => [ 0 => group.eskimo1.test ] … } … } Note the presence of com.apple.security.get-task-allow, showing that this is a development build. And that group
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
Oct ’24
Reply to "How to" for dext distribution
Thank you both for the responses. We have accomplished the Team Agent request for entitlements for PCI DriverKit - it looks like I am able to perform all other tasks necessary at my admin level on the developer portal. Following ssmith_c's advice, I was able to build, sign, notarize, and deploy a dext within a hosting application, the added export and manual selection seemed to be the difference I needed. However, I'm still encountering some issues with Xcode 15.2 when trying to make a distributable application that works with the dext (#3 of the software types listed above). One worked, and one seemed to not work. The not working one is crashing based on: Exception Type: EXC_CRASH (SIGKILL (Code Signature Invalid)) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: CODESIGNING 1 Taskgated Invalid Signature Using codesign to inspect the signature, it seems ok, but I likely am just not seeing the issue: daniek3@MacBook-Pro Project % codesign -dv --verbose=3 A
Replies
Boosts
Views
Activity
Oct ’24
"Command CodeSign failed with a nonzero exit code" after enrollment to a development team
Hi all, I have two apple accounts. Stupidly my project is written in Account A and my paid developer account is Account B. When I tried to archive and publish under Account A, it says Team XXX (Personal Team) is not enrolled in the Apple Developer Program. But when I add a team to Account B, Command CodeSign failed with a nonzero exit code. I know it is not the code itself because it runs fine when I use Account A. Just couldn't publish. Any advice? Many many thanks
Topic: Code Signing SubTopic: General
Replies
1
Boosts
0
Views
432
Activity
Oct ’24
Reply to Notarization succeeds, but gatekeeper check still fails, with QtWebEngine
I dig into the issue, hence I have 2 executable files in the app under xxx.app/Contents/MacOS: M and N, M is in the Info.plist and is the CFBundleExecutable file, after signed the M with codesign, returns with this: signed app bundle with Mach-O thin (arm64) [CFBundleIdentifier]; otherwise, the N signed with codesign in the same way, returned with this: signed Mach-O thin (arm64) [N]. And I installed the APP on my machine, when I clicked the M executable file, seems it passed the gatekeeper, but I clicked the N, seems the gatekeeper check fails. I am not sure it's the reason.
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Oct ’24
Command CodeSign failed with a nonzero exit code
I have not been able to open any of my apps since I uploaded my latest update midOctober 2023. Previously I have tried everything on forums from removing derived data, adding new options in build folder and more. Since then I have wasted hours trying to open any app from my iCloud / hard disk and I wonder if part of the problem is caused by backing up to iCloud, as I can open from an external hard disk. It takes almost as long to upload from hard disk than cloud so whole thing annoying, does this add clues to this frustrating problem ? Also when I opened one of my apps it had made hundreds of unassigned assets that all had to be removed individually. I have no idea how to continue with my work I have three other apps in progress, but am halted at present but such a stupid small detail. // here is full commet /Users/ruwickigmail.com/Desktop/0-APPS-2023/InstaAnimates/InstaAnimates.xcodeproj: warning: Unable to find a target which creates the host product for value of $(TEST_HOST) '/Users/ruwickigmail.com/Deskto
Replies
1
Boosts
0
Views
758
Activity
Oct ’24
Notarization succeeds, but gatekeeper check still fails, with QtWebEngine
I am packaging an app with QtWebEngine in it, after codesign the app and the QtWebEngine Framework, the app can run properly. The codesign result is: valid on disk staisfies its Designated requirements Then I notarized and stapled the dmg file, after the dmg installed on Mac, gatekeeper still failed the check. Here is the result for spctl: spctl -a -t open -vvv --context context:primary-signatue Remote Graphics Workstation_.dmg Remote Graphics Workstation_.dmg: rejected source=Insufficient Context Need help to identify the codesign process and the root cause why gatekeeper fail here, thanks.
Replies
3
Boosts
0
Views
772
Activity
Oct ’24
Reply to Issues with Embedding Python Interpreter in MacOS App Distributed via TestFlight
Hello, I still get some errors: Process tccd Prompting policy for hardened runtime; service: kTCCServiceAppleEvents requires entitlement com.apple.security.automation.apple-events but it is missing for accessing={TCCDProcess: identifier=com.sampleApp.app, pid=72680, auid=502, euid=502, binary_path=[PATH_TO_APP]]}, requesting={TCCDProcess: identifier=com.apple.appleeventsd, pid=831, auid=55, euid=55, binary_path=/System/Library/CoreServices/appleeventsd}, Process python3.11 flock failed to lock list file (): errno = 35 Basically the changes I made are: Used the code from 'Running a Child Process with Standard Input and Output', it works great, thanks! Made a Run script to sign the executable: codesign -s - -i com.sampleApp.app.Python -o runtime --entitlements $ENTITLEMENTS_PATH -f $BINARY_PATH And then created a copy build phase to place the executable in Executables destination. Code sign on copy is selected. (Verified that it is placed in MacOS folder, and correctly signed.) These are the Entitlemen
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
Oct ’24
Issue codesign on VS Code and XCode
Hello, I'm starting to develop a new app with Flutter on VS Code. I. struggle to start because I face constantly this error : Error (Xcode): Target debug_unpack_ios failed: Exception: Failed to codesign /Users/Nylan1/Desktop/Thoughts./Flutter Application/app_v0/app_v0/build/ios/Debug-iphonesimulator/Flutter.framework/Flutter with identity -. Can someone pleas help me to solve that ? I've checked on Xcode and the macOS signing certificate is on Development but the IOS one is not working.
Replies
0
Boosts
0
Views
547
Activity
Oct ’24
Reply to Issues with Invalid Binary Signatures During macOS Notarization of Electron App
Faced same issue the --deep signing may not do what is expected. I found that --deep flag is depreciated and seems latest https://keith.github.io/xcode-man-pages/codesign.1.html#deep Looking forward to hear something from Apple about it.
Replies
Boosts
Views
Activity
Oct ’24