Search results for

“codesign”

3,223 results found

Post

Replies

Boosts

Views

Activity

Reply to Keychain error -34018 (errSecMissingEntitlement)
I am also strugling with this, when trying to write to the KeyChain, Simulator iPhone 6, IOS 10, Xcode 8, when unit testing..I have tried signing the Test Tarrget codesign -d --verify --force -i AXXXXXXXXXXXXXXXXXXXXXXXXXXXX43C --entitlements $SRCROOT/TheSDKTests/SDKtest.entitlements --sign AXXXXXXXXXXXXXXXXXXXXXXXXXXXX43C $CODESIGNING_FOLDER_PATHBut still I get the error : -34018
Topic: Privacy & Security SubTopic: General Tags:
Sep ’16
Can't run(debug) App on Device
I working with macos Sierra en xcode 8.0Creating an objective-c App In the simulator no problems. Running on my Ipad i get the following message:CodeSign /Users/aad/Library/Developer/Xcode/DerivedData/TestOC-dbkyvbcrpfvbgfghxadarkghjrzf/Build/Products/Debug-iphoneos/TestOC.app cd /AppStones/Projecten/IosProjecten/TestOC export CODESIGN_ALLOCATE=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate export PATH=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin Signing Identity: iPhone Developer: Aad Glasbergen (32A254WUH8)Provisioning Profile: iOS Team Provisioning Profile: * (20e5defb-711e-493f-921e-380110490e8d) /usr/bin/codesign --force --sign C2D5A6FB111CBEB2D727B45DBDE260A748C92634 --entitlements /Users/aad/Library/Developer/Xcode/DerivedData/TestOC-dbkyvbcrpfvbgfghxadarkghjrzf/Build/Intermediates/TestOC.build/Debu
1
0
1k
Oct ’16
Command /usr/bin/codesign failed with exit code 5
CodeSign /Users/ogystoev/Library/Developer/Xcode/DerivedData/APPNAME-/Build/Intermediates/ArchiveIntermediates/APPNAME/InstallationBuildProductsLocation/Applications/APPNAME.app cd /Users/ogystoev/Documents/WORK/APPNAME/ios export CODESIGN_ALLOCATE=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate export PATH=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbinSigning Identity: iPhone Developer: .....Provisioning Profile: iOS Team Provisioning Profile: ..... () /usr/bin/codesign --force --sign --entitlements /Users/ogystoev/Library/Developer/Xcode/DerivedData/APPNAME-/Build/Intermediates/ArchiveIntermediates/APPNAME/IntermediateBuildFilesPath/APPNAME.build/Release-iphoneos/APPNAME.build/APPNAME.app.xcent --timestamp=none /Users/ogystoev/Library/Developer/Xcode/DerivedData/APPNAME-/Build/Intermediates/Archive
12
0
3.3k
Oct ’16
Has anyone seen/able to fix a " /usr/bin/codesign '--force' '--sign'" issue?
Hi all!I'm using Xcode - Version 8.0 (8A218a) and sometimes it will fail during a build and will give me this error message. I've had luck cleaning the folder, trashing the derived folered, and booting. This obvisouly is not a strategy the works for me in the long term. Any ideas on how to fix this?I've also recreated this issue with Xcode - Version 8.1 beta (8T46g).error: Task failed with exit 1 signal 0 { /usr/bin/codesign '--force' '--sign' '-' '--verbose' '/Users/xxx/Library/Developer/Xcode/DerivedData/xxx-xxxxx/Build/Products/Debug-watchsimulator/TargetName Extension.appex/Frameworks/libswiftCoreGraphics.dylib' }
1
0
264
Oct ’16
Xcode 8 on 10.12 codesign segmentation fault
I have a separate script that signs my embedded frameworks.This was worked fine form 10.9 - 10.11.On 10.12 I get a segmentation fault.codesign --verbose --force --sign $IDENTITY ${FRAMEWORKS_LOCATION}/${FRAMEWORK}.framework/Versions/A18939 Segmentation fault: 11Running the command outside of Xcode produces the same result.
8
0
5.9k
Oct ’16
Reply to Enabling SIP on 3rd-party apps
Thanks Quinn. This pretty much covers the subject. The current SIP protections are based on how the code is signed, which isn’t something you can change. Is this anything like the Kernel Extension codesigning keys? Should we just request a new type of key? This won’t stop a determined attacker (ask me how I know!) How do you know? And what are the risks, and the steps an attacker could take to bypass this?
Topic: Privacy & Security SubTopic: General Tags:
Oct ’16
lldb framework error after re-signing lldb code
On a MacBook Pro, OSX El Capitan release, using lldb on the command lineSummary: Keep getting a 'cannot open client port' error when using lldb command line mode. Recreated new lldb_codesign certificate but to no avail. Still getting the error.Here are the steps I took.( all work is in a separate tree off of /Users/Jeff )1. Removed all old lldb binaries/libraries2. Removed lldb_codesign certificate3. Reboot4. Re-create new lldb_codesign cert. per instructions below5. Rebuilt lldb from source ( make -B lldb )6. Reboot7. run newly built lldb on lldb ( % ./lldb ./lldb )8. still get 'unable to open client port'Any Help on this wouild be appreciated.Updating codesign============================================- Launch /Applications/Utilities/Keychain Access.app- In Keychain Access select the login keychain in the Keychains list in the upper left hand corner of the window.- Select the following menu item: keychain Access->Certificate Assistant->Create a Certificate...- Set the following settings Name
0
0
478
Oct ’16
Reply to Enabling SIP on 3rd-party apps
Is this anything like the Kernel Extension codesigning keys?No. Last I checked, SIP only kicks in for Apple code that comes built in to the OS.How do you know?Well, I was being facetious but, sure I can answer that: a while back I built my own tool to nobble PT_DENY_ATTACH so that I could debug various plug-ins that get loaded in system components that set PT_DENY_ATTACH. And no, I won’t share (-: And what are the risks, and the steps an attacker could take to bypass this?What’s your threat model? Are you trying to protect yourself from the user themselves (like a DRM scheme)? Or trying to protect yourself from code that the user has unwittingly run?Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com
Topic: Privacy & Security SubTopic: General Tags:
Oct ’16
Device Build fail after upgrading to Xcode 8
Since upgrading to Xcode 8 I cannot run any app on my iPhone. The build fails with error:error: Task failed with exit 0 signal 11I can run the apps on the simulators, just not on a device.The full error message:Please help.Coby ReshefThe full error message:error: Task failed with exit 0 signal 11 { /usr/bin/codesign '--force' '--sign' '7F49C2A625C8976762BDEA351F8DA88E4F6FED22' '--verbose' '/Users/reshef/Library/Developer/Xcode/DerivedData/testXcode-eltpwhxdshmmlygolxcnsroevmoo/Build/Products/Debug-iphoneos/testXcode.app/Frameworks/libswiftCore.dylib'}
7
0
1.9k
Oct ’16
Developer ID signed apps cannot load external data under macOS Sierra
Hello, we currently have problems with the download versions (ZIP) of our applications under the new operating system »macOS Sierra« from Apple. It is a (non-native) video tutorial app with external data and different startfiles (certificate signed) for Mac and Windows (originally created for DVDs). Although the Mac startfile of the download version was properly signed with a valid Apple Developer ID certificate, an authorization problem now appears and the application can no longer load external data. The same application on DVD still works impeccable. My researches have shown that under macOS Sierra developer ID signed apps (outside the App Store) are not allowed to use external libraries, external code or external data:https://developer.apple.com/library/content/releasenotes/MacOSX/WhatsNewInOSX/Articles/OSXv10.html»Starting in macOS 10.12, you can not get any longer. An app distributed outside the Mac App. To provide secure execution, code your disk image is using the codesign tool, or distribute
5
0
868
Oct ’16
Reply to Command /usr/bin/codesign failed with exit code 5
The only solution I've found is to build and archive on a machine still running El Capitan. This works fine, keeping everything else the same.http://stackoverflow.com/questions/39664079/command-usr-bin-codesign-failed-with-exit-code-5What doesn't work- regenerating certificates and provisions (https://forums.developer.apple.com/thread/64677)- fixes for exit code 1- restarting xcode, rebooting, etc- deleting derived data- deleting and reinstalling certificates/keys in Keychain Access on the mac- updating to Sierra 10.12.1 developer Beta 5- updating to Sierra 10.12.1 release (Oct 24)
Oct ’16
Reply to Xcode 8 can't archive “Command /usr/bin/codesign failed with exit code 1” part 2
That's an interesting observation. I had the same issue for my unit tests after upgrade to Sierra. resource fork, Finder information, or similar detritus not allowed Command /usr/bin/codesign failed with exit code 1 In my case the xattr -rc . didn't resolve the issue.After a lot of trial and error and even more hair-pulling, I remembered that Sierra started syncing my Documents folder where I kept my projects to the iCloud, and I keep my DerivedData relative to the project path. Sure enough, when I changed that back to the default location under ~/Library/... the issue went away. When I switch it back to any directory that is synced to the iCloud the issue re-appears. It seems that something in Sierra, possibly related to the sync process, is marking files or directories with extended attributes.Hope that may help someone.
Oct ’16
Reply to SecKey API returned: -25304 libswiftAVFoundation.dylib: unknown error -1=ffffffffffffffff error: Task failed with exit 1 signal 0
The underlying problem for me was that I codesign was requesting access to the keychain and I had to approve it before it worked.Somehow this line didn't grant codesign access when the keychain was created:security import ./osx_signing.p12 -k osx_signing.keychain -P MY_SUPER_PASSWORD -T /usr/bin/codesignActually with Sierra, even doing this still causes codesign to trigger a pop-up the very first time it is run. 🙂security import ./osx_signing.p12 -k osx_signing.keychain -P MY_SUPER_PASSWORD -A
Oct ’16
Reply to Keychain error -34018 (errSecMissingEntitlement)
I am also strugling with this, when trying to write to the KeyChain, Simulator iPhone 6, IOS 10, Xcode 8, when unit testing..I have tried signing the Test Tarrget codesign -d --verify --force -i AXXXXXXXXXXXXXXXXXXXXXXXXXXXX43C --entitlements $SRCROOT/TheSDKTests/SDKtest.entitlements --sign AXXXXXXXXXXXXXXXXXXXXXXXXXXXX43C $CODESIGNING_FOLDER_PATHBut still I get the error : -34018
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Sep ’16
Reply to Xcode 8 Beta error launching simulator
Thank you very much...after being sick for a while, this solved my problem with error codesign...But I do not understand why suddenly this appears...I mean in Xcode7 the project with working correctly, but not in Xcode8... is this a bug in the new version?
Replies
Boosts
Views
Activity
Oct ’16
Can't run(debug) App on Device
I working with macos Sierra en xcode 8.0Creating an objective-c App In the simulator no problems. Running on my Ipad i get the following message:CodeSign /Users/aad/Library/Developer/Xcode/DerivedData/TestOC-dbkyvbcrpfvbgfghxadarkghjrzf/Build/Products/Debug-iphoneos/TestOC.app cd /AppStones/Projecten/IosProjecten/TestOC export CODESIGN_ALLOCATE=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate export PATH=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin Signing Identity: iPhone Developer: Aad Glasbergen (32A254WUH8)Provisioning Profile: iOS Team Provisioning Profile: * (20e5defb-711e-493f-921e-380110490e8d) /usr/bin/codesign --force --sign C2D5A6FB111CBEB2D727B45DBDE260A748C92634 --entitlements /Users/aad/Library/Developer/Xcode/DerivedData/TestOC-dbkyvbcrpfvbgfghxadarkghjrzf/Build/Intermediates/TestOC.build/Debu
Replies
1
Boosts
0
Views
1k
Activity
Oct ’16
Command /usr/bin/codesign failed with exit code 5
CodeSign /Users/ogystoev/Library/Developer/Xcode/DerivedData/APPNAME-/Build/Intermediates/ArchiveIntermediates/APPNAME/InstallationBuildProductsLocation/Applications/APPNAME.app cd /Users/ogystoev/Documents/WORK/APPNAME/ios export CODESIGN_ALLOCATE=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate export PATH=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbinSigning Identity: iPhone Developer: .....Provisioning Profile: iOS Team Provisioning Profile: ..... () /usr/bin/codesign --force --sign --entitlements /Users/ogystoev/Library/Developer/Xcode/DerivedData/APPNAME-/Build/Intermediates/ArchiveIntermediates/APPNAME/IntermediateBuildFilesPath/APPNAME.build/Release-iphoneos/APPNAME.build/APPNAME.app.xcent --timestamp=none /Users/ogystoev/Library/Developer/Xcode/DerivedData/APPNAME-/Build/Intermediates/Archive
Replies
12
Boosts
0
Views
3.3k
Activity
Oct ’16
Has anyone seen/able to fix a " /usr/bin/codesign '--force' '--sign'" issue?
Hi all!I'm using Xcode - Version 8.0 (8A218a) and sometimes it will fail during a build and will give me this error message. I've had luck cleaning the folder, trashing the derived folered, and booting. This obvisouly is not a strategy the works for me in the long term. Any ideas on how to fix this?I've also recreated this issue with Xcode - Version 8.1 beta (8T46g).error: Task failed with exit 1 signal 0 { /usr/bin/codesign '--force' '--sign' '-' '--verbose' '/Users/xxx/Library/Developer/Xcode/DerivedData/xxx-xxxxx/Build/Products/Debug-watchsimulator/TargetName Extension.appex/Frameworks/libswiftCoreGraphics.dylib' }
Replies
1
Boosts
0
Views
264
Activity
Oct ’16
Xcode 8 on 10.12 codesign segmentation fault
I have a separate script that signs my embedded frameworks.This was worked fine form 10.9 - 10.11.On 10.12 I get a segmentation fault.codesign --verbose --force --sign $IDENTITY ${FRAMEWORKS_LOCATION}/${FRAMEWORK}.framework/Versions/A18939 Segmentation fault: 11Running the command outside of Xcode produces the same result.
Replies
8
Boosts
0
Views
5.9k
Activity
Oct ’16
Reply to Enabling SIP on 3rd-party apps
Thanks Quinn. This pretty much covers the subject. The current SIP protections are based on how the code is signed, which isn’t something you can change. Is this anything like the Kernel Extension codesigning keys? Should we just request a new type of key? This won’t stop a determined attacker (ask me how I know!) How do you know? And what are the risks, and the steps an attacker could take to bypass this?
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Oct ’16
Xcode 8 throwing "Command /usr/bin/codesign failed with exit code 1" for Preview created pngs
After upgrading to Xcode 8, a couple of my apps starting throwing Command /usr/bin/codesign failed with exit code 1 errors. I narrowed it down to pngs exported from Preview. Opening and exporting them from GIMP fixed it.
Replies
0
Boosts
0
Views
385
Activity
Oct ’16
lldb framework error after re-signing lldb code
On a MacBook Pro, OSX El Capitan release, using lldb on the command lineSummary: Keep getting a 'cannot open client port' error when using lldb command line mode. Recreated new lldb_codesign certificate but to no avail. Still getting the error.Here are the steps I took.( all work is in a separate tree off of /Users/Jeff )1. Removed all old lldb binaries/libraries2. Removed lldb_codesign certificate3. Reboot4. Re-create new lldb_codesign cert. per instructions below5. Rebuilt lldb from source ( make -B lldb )6. Reboot7. run newly built lldb on lldb ( % ./lldb ./lldb )8. still get 'unable to open client port'Any Help on this wouild be appreciated.Updating codesign============================================- Launch /Applications/Utilities/Keychain Access.app- In Keychain Access select the login keychain in the Keychains list in the upper left hand corner of the window.- Select the following menu item: keychain Access->Certificate Assistant->Create a Certificate...- Set the following settings Name
Replies
0
Boosts
0
Views
478
Activity
Oct ’16
Reply to Enabling SIP on 3rd-party apps
Is this anything like the Kernel Extension codesigning keys?No. Last I checked, SIP only kicks in for Apple code that comes built in to the OS.How do you know?Well, I was being facetious but, sure I can answer that: a while back I built my own tool to nobble PT_DENY_ATTACH so that I could debug various plug-ins that get loaded in system components that set PT_DENY_ATTACH. And no, I won’t share (-: And what are the risks, and the steps an attacker could take to bypass this?What’s your threat model? Are you trying to protect yourself from the user themselves (like a DRM scheme)? Or trying to protect yourself from code that the user has unwittingly run?Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Oct ’16
Device Build fail after upgrading to Xcode 8
Since upgrading to Xcode 8 I cannot run any app on my iPhone. The build fails with error:error: Task failed with exit 0 signal 11I can run the apps on the simulators, just not on a device.The full error message:Please help.Coby ReshefThe full error message:error: Task failed with exit 0 signal 11 { /usr/bin/codesign '--force' '--sign' '7F49C2A625C8976762BDEA351F8DA88E4F6FED22' '--verbose' '/Users/reshef/Library/Developer/Xcode/DerivedData/testXcode-eltpwhxdshmmlygolxcnsroevmoo/Build/Products/Debug-iphoneos/testXcode.app/Frameworks/libswiftCore.dylib'}
Replies
7
Boosts
0
Views
1.9k
Activity
Oct ’16
Developer ID signed apps cannot load external data under macOS Sierra
Hello, we currently have problems with the download versions (ZIP) of our applications under the new operating system »macOS Sierra« from Apple. It is a (non-native) video tutorial app with external data and different startfiles (certificate signed) for Mac and Windows (originally created for DVDs). Although the Mac startfile of the download version was properly signed with a valid Apple Developer ID certificate, an authorization problem now appears and the application can no longer load external data. The same application on DVD still works impeccable. My researches have shown that under macOS Sierra developer ID signed apps (outside the App Store) are not allowed to use external libraries, external code or external data:https://developer.apple.com/library/content/releasenotes/MacOSX/WhatsNewInOSX/Articles/OSXv10.html»Starting in macOS 10.12, you can not get any longer. An app distributed outside the Mac App. To provide secure execution, code your disk image is using the codesign tool, or distribute
Replies
5
Boosts
0
Views
868
Activity
Oct ’16
Reply to Command /usr/bin/codesign failed with exit code 5
The only solution I've found is to build and archive on a machine still running El Capitan. This works fine, keeping everything else the same.http://stackoverflow.com/questions/39664079/command-usr-bin-codesign-failed-with-exit-code-5What doesn't work- regenerating certificates and provisions (https://forums.developer.apple.com/thread/64677)- fixes for exit code 1- restarting xcode, rebooting, etc- deleting derived data- deleting and reinstalling certificates/keys in Keychain Access on the mac- updating to Sierra 10.12.1 developer Beta 5- updating to Sierra 10.12.1 release (Oct 24)
Replies
Boosts
Views
Activity
Oct ’16
Reply to Xcode 8 can't archive “Command /usr/bin/codesign failed with exit code 1” part 2
That's an interesting observation. I had the same issue for my unit tests after upgrade to Sierra. resource fork, Finder information, or similar detritus not allowed Command /usr/bin/codesign failed with exit code 1 In my case the xattr -rc . didn't resolve the issue.After a lot of trial and error and even more hair-pulling, I remembered that Sierra started syncing my Documents folder where I kept my projects to the iCloud, and I keep my DerivedData relative to the project path. Sure enough, when I changed that back to the default location under ~/Library/... the issue went away. When I switch it back to any directory that is synced to the iCloud the issue re-appears. It seems that something in Sierra, possibly related to the sync process, is marking files or directories with extended attributes.Hope that may help someone.
Replies
Boosts
Views
Activity
Oct ’16
Reply to SecKey API returned: -25304 libswiftAVFoundation.dylib: unknown error -1=ffffffffffffffff error: Task failed with exit 1 signal 0
The underlying problem for me was that I codesign was requesting access to the keychain and I had to approve it before it worked.Somehow this line didn't grant codesign access when the keychain was created:security import ./osx_signing.p12 -k osx_signing.keychain -P MY_SUPER_PASSWORD -T /usr/bin/codesignActually with Sierra, even doing this still causes codesign to trigger a pop-up the very first time it is run. 🙂security import ./osx_signing.p12 -k osx_signing.keychain -P MY_SUPER_PASSWORD -A
Replies
Boosts
Views
Activity
Oct ’16