codesign

How to codesign and enable the hardened runtime for a 3rd-party CLI on Xcode?

家住魔仙堡 提交于 2019-12-03 14:25:55
My project needs the Ghostscript to do lots of tasks, so I have added the gs CLI tool into my project resource. However when I tried to notarize the project application, Xcode shows me this: I assume that might because the ghostscript portable CLI is a 3rd-party program from the internet and which doesn't have a codesign, also it has not been enabled the hardened runtime. On the latest MacOS Mojave I have to notarize applications to avoid the gatekeeper shows warnings during the user opens the DMG file. But it seems the notarizing is hard to pass if the application contains a 3rd-party CLI. Is

Codesign check fails Xcode 4

给你一囗甜甜゛ 提交于 2019-12-03 13:08:24
问题 I just created all new dev and deployment certs and I'm getting this weird error when I try to validate the application in the archive manager: error: Codesign check fails : /var/folders/w_/dvqfkh916k12c5hn639qvvqw0000gn/T/oqhxIfU87c/Payload/TestUpload.app: valid on disk /var/folders/w_/dvqfkh916k12c5hn639qvvqw0000gn/T/oqhxIfU87c/Payload/TestUpload.app: satisfies its Designated Requirement test-requirement: code failed to satisfy specified code requirement(s) I've looked all over to see how

codesigned kext But why not load in Yosemite(10.10)

 ̄綄美尐妖づ 提交于 2019-12-03 12:36:35
I had a code signing on kext in Yosemite. But kextload is failed. It was version2 codesign. codesign --verify is true. But kextload is failed. Why not load in Yosemite? Here is my log. I have checked with codesign -dvvv ./myKext.kext And It's all right. codesign -dvvv ./myKext.kext returned following: Executable=/Path/to/myKext Identifier=com.myKext.kext.Firewall Format=bundle with Mach-O thin (x86_64) CodeDirectory v=20100 size=317 flags=0x0(none) hashes=9+3 location=embedded Hash type=sha1 size=20 CDHash=d0ff68bd8b49c650f45349c2d1570d45a8c1f148 Signature size=8544 Authority=Developer ID

Codesign failed on 10.12 Sierra

本秂侑毒 提交于 2019-12-03 12:31:58
问题 Just installed 10.12 and Xcode 8 codesign command fails even from terminal with A cryptographic verification failure has occurred. and no further details. Any solutions? 回答1: This Chinese website helps me to solve that issue. Launch "Keychain Access", go to "Preferences..." and click "Reset My Default Keychain". After that I was finally able to build my projects. 来源: https://stackoverflow.com/questions/37801465/codesign-failed-on-10-12-sierra

App dies on startup but not crash report

妖精的绣舞 提交于 2019-12-03 12:28:54
I've given an ad hoc version of my app to some users. Two of them have the app die on start up while one user has no issues. I can also install the ad hoc without issue...but that is always the case for me. One user sent the info below from the Xcode Organizer Console. They didn't find any crash logs. I don't know what to make of the info below. The one thing that stands out is "Permission denied". I place the provisioning and myapp.app files in a dropbox folder. The user then retrieves the files from the same location. I've run codesign against the .app file in the dropbox and get valid

Xcode does not see my developer certificate in Code Signing Identity

一曲冷凌霜 提交于 2019-12-03 11:08:05
I renewed my IOS Developer Certificate, i deleted old ones from keychains and clicked on my certificate. Everything looks normal in keychains, i have distribution,developer, WWDC certificates in there.Every profile look valid with green marks Under Teams and Provisioning Profiles section in Organizer but in Xcode under Code Signing Identity there is no profile currently match developer profile under Automatic Profile Selector(Recommended). What can i do about it? thanks in advance. First of all check in Xcode -> Preferences -> Account that you have your new profile in the list, refresh the

Remove private key from Mac OS X keychain using Terminal

流过昼夜 提交于 2019-12-03 07:34:58
问题 I've imported a developer identity (certificate + private key) for iOS development to a keychain using the "security" Terminal application with the command security import identity.p12 -k <keychain> -P <passphrase> This imports both items included in the p12 file, certificate and private key, into the given keychain. I forgot to specify -T /usr/bin/codesign , however, which adds the codesign application to the access list of the private key. I've tried to add the codesign app to the access

Xcode Build Error Jenkins: Your session has expired. Please log in

Deadly 提交于 2019-12-03 06:32:41
I'm trying to build my application using jenkins pipeline using shell command. Below is the command i'm using to build the app. sh 'xcodebuild -workspace projectname.xcworkspace - allowProvisioningUpdates -scheme projectname_UAT -sdk iphoneos - configuration Debug clean build' Below is the error i'm getting i console. note: Using new build system note: Planning build 2018-10-11 11:19:36.638 xcodebuild[92399:5181481] DVTPortal: Service '' encountered an unexpected result code from the portal ('1100') 2018-10-11 11:19:36.638 xcodebuild[92399:5181481] DVTPortal: Error: Error Domain

How does Apple's codesign utility decide which SHA algorithm(s) to sign a shared library with?

社会主义新天地 提交于 2019-12-03 05:41:35
First, a little background: I'm investigating why my company's MacOS/X application (which by all accounts appears to be correctly signed; it runs fine under MacOS/X 10.11.x and 10.12.x; Gatekeeper is fine with it on all MacOS versions; "spctl --assess", and "codesign -vvvv" all say it satisfies its requirement on all OS versions) nevertheless won't launch under OS/X 10.10.x -- under 10.10.x when I try to launch it, I get a Crash Report where dyld complains that some of the libraries aren't signed correctly: Dyld Error Message: Library not loaded: @executable_path/../Frameworks/libcrypto.1.0.0

Codesign wants to access key “access” in your keychain, I put in my login password but keeps asking me

好久不见. 提交于 2019-12-03 01:36:15
问题 I'm trying to learn to load apps on my iPhone from Xcode. When I do I keep getting "Codesign wants to access key "access" in your keychain, I put I my login password but it keeps popping up over and over. I've tried my computer login so many times, apple account password, and many others. 回答1: Had the same issue. It was fixed after I entered my mac user password and hit Always Allow . 回答2: Solve this problem by doing this. Enter your Mac Login Password and Choose "Always Allow" One or More