codesign

hello Eskimo, By now I build out of Xcode successfully, and code sign by command, but still failed. SampleEndpointApp Info.plist: CFBundleDevelopmentRegion $(DEVELOPMENT_LANGUAGE) CFBundleExecutable $(EXECUTABLE_NAME) CFBundleIconFile CFBundleIdentifier $(PRODUCT_BUNDLE_IDENTIFIER) CFBundleInfoDictionaryVersion 6.0 CFBundleName $(PRODUCT_NAME) CFBundlePackageType $(PRODUCT_BUNDLE_PACKAGE_TYPE) CFBundleShortVersionString 1.0 CFBundleVersion 1 LSMinimumSystemVersion $(MACOSX_DEPLOYMENT_TARGET) NSHumanReadableCopyright Copyright © 2020 Apple. All rights reserved. NSMainStoryboardFile Main NSPrincipalClass NSApplication NSSupportsAutomaticTermination NSSupportsSuddenTermination Extention Info.plist: CFBundleDevelopmentRegion $(DEVELOPMENT_LANGUAGE) CFBundleDisplayName Extension CFBundleExecutable $(EXECUTABLE_NAME) CFBundleIdentifier $(PRODUCT_BUNDLE_IDENTIFIER) CFBundleInfoDictionaryVersion 6.0 CFBundleName $(PRODUCT_NAME) CFBundlePackageType $(PRODUCT_BUNDLE_PACKAGE_TYPE) CFBundleShortVersionString

First, I referred the Configure the Sample Code Project section in the README.md and configured the sample code project to build with automatic signing. I could run the app and activate the dext successfully and made sure the app could communicate with the dext. Great! That's how development signing is intended to work. Next, I tried the manual signing. I followed steps described in the Configure the Sample Code Project section carefully. Manually code-signing for what purpose/environment? If you're trying to manually sign for development, my advice is don't bother. While it is technically possible, it's a pain to set up, will break frequently, and doesn't provide any real benefit. If you're signing for any other environment, including: I would also like to know detailed steps to publicly distribute my dext and app using our Developer ID Application Certificate My description of the basic flow is here. In a different thread, I also posted a detailed write up on how the different configuration points relate an

codesign -d --entitlements :- /Applications/SampleEndpointApp.app Executable=/Applications/SampleEndpointApp.app/Contents/MacOS/SampleEndpointApp warning: Specifying ':' in the path is deprecated and will not work in a future release com.apple.application-identifierRKJVFVKFG3.com.example.apple-samplecode.SampleEndpointAppRKJVFVKFG3com.apple.developer.system-extension.installcom.apple.developer.team-identifierRKJVFVKFG3com.apple.security.files.user-selected.read-onlycom.apple.security.get-task-allow codesign -d --entitlements :- /Applications/SampleEndpointApp.app/Contents/Library/SystemExtensions/com.example.apple-samplecode.SampleEndpointAppRKJVFVKFG3.Extension.systemextension Executable=/Applications/SampleEndpointApp.app/Contents/Library/SystemExtensions/com.example.apple-samplecode.SampleEndpointAppRKJVFVKFG3.Extension.systemextension/Contents/MacOS/com.example.apple-samplecode.SampleEndpointAppRKJVFVKFG3.Extension warning: Specifying ':' in the path is deprecated and will not work in a

Yes, I'm trying to run Monitoring System Events with Endpoint Security sample code. By now, I disabled automatic signing in Xcode and use my private profile generated by apple site, build successfully. I read through this post and deleted both entitlements files of app and extension, codesign them. Then got error like this: Failed to install the extension ❌ Invalid extension configuration in Info.plist and/or entitlements: does not appear to belong to any extension categories.

Thank for those UUIDs. I asked the notary team for a copy of those submissions, so I could see exactly what the submitted zip archives look like, and that revealed a clear problem. Consider this file listing of your notarytool submission: % unzip -t ok-035482f3-855c-455f-bd60-6be63ceefd61.zip Archive: ok-035482f3-855c-455f-bd60-6be63ceefd61.zip … testing: Wwwwwwww.app/Contents/MacOS/graphviz/bin/gvmap.sh OK testing: __MACOSX/Wwwwwwww.app/Contents/MacOS/graphviz/bin/._gvmap.sh OK … No errors detected in compressed data of ok-035482f3-855c-455f-bd60-6be63ceefd61.zip. Note I’ve redacted stuff using my ‘patented’ ‘first letter’ algorithm [1]. First up, the __MACOSX indicates that you’ve sequestered Mac metadata. That doesn’t make sense in this context. I explain why in Extended Attributes and Zip Archives. However, the real issue is that you have Mac metadata at all! Unpacking the archive I see this: % xattr Wwwwwwww.app/Contents/MacOS/graphviz/bin/gvmap.sh com.apple.cs.CodeDirectory com.apple.cs.CodeRequirements

security -v import bundle.p12 -k login.keychain -T /usr/bin/codesign -P https://1drv.ms/u/c/de13bcdacf228c88/ER4DNppbQQRMlY4tzawZ1s8BNLNcbEnuf54lLUOL1oD-Dg

Any updates on the bug ? Same issue. Sequoia 15.4.1 (24E263) OpenSSL 3.4.0 Steps for repoducing: Create .p12 without password openssl genpkey -algorithm RSA -out private_key.pem openssl req -new -key private_key.pem -out csr.pem openssl x509 -req -days 365 -in csr.pem -signkey private_key.pem -out certificate.pem openssl pkcs12 -export -out bundle.p12 -inkey private_key.pem -in certificate.pem Import .p12 to a keychain import bundle.p12 -k login.keychain -T /usr/bin/codesign -P And voila you've got the bug: security: SecKeychainItemImport: MAC verification failed during PKCS12 import (wrong password?)

It’s really hard to read your post. Please take a look at Quinn’s Top Ten DevForums Tips, which has lots of suggestions for how to work effectively on the forums. Anyway, what I can see is this: [quote='784184021, BenAuerDev, /thread/784184, /profile/BenAuerDev'] Are there known issues with signing Flutter plugin frameworks for notarization? [/quote] I think you might have more luck asking that via the support channel for the third-party tool you’re using. However, my experience is that third-party tooling tends to bend the bundle placement rules outlined in Placing Content in a Bundle, and that causes all sorts of weird problems. [quote='784184021, BenAuerDev, /thread/784184, /profile/BenAuerDev'] Using both codesign --deep [/quote] I strongly recommend against using --deep when signing code. See --deep Considered Harmful. As to what you should do, you can find my general advice in: Creating distribution-signed code for macOS Packaging Mac software for distribution Beyond that, it’s hard to offer sp

I’ve not looked into the installer package side of this in depth but, in general, the transition from SHA1 to SHA256 is driven by the deployment target. If your product supports old releases, the system has to include both hashes to ensure compatibility with those systems. Now, with codesign I’m familiar with how that’s controlled, that is, via various Mach-O load commands. You can dump these using vtool. For installer packages, the productbuild man page described how you set the minimum supported OS version. Are you doing that? And just for testing, try setting it way up, to something silly like macOS 15. If that works, you can then step it back to determine the inflexion point. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com