codesign

Application with multiple executables appears signed but triggers firewall warning

喜你入骨 提交于 2019-12-06 01:34:21
I'm working on a QT app for OS X that uses multiple executables. We sign the .app by signing each executable within the .app, then signing the whole .app with the "-f" option. This is the procedure Apple recommended when we contacted them. However, each time our app starts, the user is prompted with a warning that our application wants to connect to the internet. This warning is repeated every time the application is restarted, even if the user chooses to grant it access. Any suggestions for where our process could be going wrong would be useful. For what it's worth, all executables and the

Resign iOS Application .iPA file without changing BundleId

爷,独闯天下 提交于 2019-12-04 21:48:53
background: we are getting iOS apps ( .ipa ) from external developers ( their apps may be submitted in the appstore ), and they want submit their apps in our internal store just by sending their .ipa to us we are installing apps using ota, by sending plist to our endusers, itms-services://?action=download-manifest&url=[PLIST_URL] i was using some GUI signing tools such as iResign, iOS App Resigner and AppResigner, injecting custom entitlements, injection App Transport Security into info.plist. and when i tried to install apps which are signed by these tools, install popup is shown correctly,

codesigned kext But why not load in Yosemite(10.10)

谁说胖子不能爱 提交于 2019-12-04 19:16:25
问题 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

App dies on startup but not crash report

£可爱£侵袭症+ 提交于 2019-12-04 18:56:28
问题 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

Codesign only succeeds after other xcode iphone project is successfully signed

不羁岁月 提交于 2019-12-04 09:00:47
I have a weird issue. Codesign refuses to sign this big project I have, project A, but does signs the other, project B. However, when I have signed project B, it also can sign project A all of a sudden. I am 100% certain I didn't change anything else. The steps I took were: Try to build, sign A - fails on signing Try to build, sign B - succeeds Try to build, sign A - succeeds Transcript: CodeSign build/Debug-iphoneos/CPPlayer.app cd /Users/nick/CPPlayer setenv CODESIGN_ALLOCATE /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/codesign_allocate setenv PATH "/Developer/Platforms/iPhoneOS

Retrieve certificate expiration date from an .ipa file?

倖福魔咒の 提交于 2019-12-04 08:47:42
问题 I know how to view the expiration date of an .ipa file's provisioning profile (by renaming the ipa to zip, then unzip it and view the ExpirationDate key in the embedded.mobileprovisioning file). But how can I view the expiration date of the certificate itself that was used to sign the ipa? I found that you can use the codesign utility to "extract" certs: codesign --display --extract-certificates /Applications/Example.app This produces three files: codesign0, codesign1, codesign2. Not sure how

Name of Provisioning Profile used to sign an iPhone app?

我与影子孤独终老i 提交于 2019-12-04 08:21:39
问题 I wrote a script that uses xcodebuild to generate an AdHoc build of an iPhone application. I would like to edit this script to output the name of the Provisioning Profile used to sign the build. This would allow me to include the Provisioning Profile in the zip that is automatically generated. This way, I could automatically send the archive to the AdHoc testers and be sure that they have the right Provisioning Profile to install the app. Is there any way to extract the Provisioning Profile

iPhone: Compressing .app files in command line (Mac OS X) removes CodeSigning

 ̄綄美尐妖づ 提交于 2019-12-04 01:59:04
I am trying to do a simple build automation of my iPhone apps with TeamCity, but having this nagging issue.. When I manually pickup and install .app file from the build folder it works great (syncs smoothly with iTunes and I can see the app on my phone) But when I try to zip this with /bin/zip or ditto...then the zipped contents loose the CodeSigning (iTunes says that it cannot install this app because its not signed) I have tried different combinations of these.. ditto -ck --rsrc --keepParent HelloWorld.app HelloWorld.zip Any more ideas? I tried this too but still getting the same error

Segmentation fault: 11 when attempting to codesign .app

纵然是瞬间 提交于 2019-12-03 23:46:59
I haven't been able to find a definition for this error in relation to codesigning. I'm really quite stumped as of what to do. The error occurs when attempting to execute this command line: codesign -s "Developer ID Application: Name (ID)" -fv --deep Application.app/ System: XCode 6.2 on Yosemite 10.10.3 I've reinstalled XCode, still without any luck. This is for a desktop application. Apologies if this is a silly question! A solution I found on the Apple forum worked for me: first, run the following command to find your identity's hex ID: $ security find-identity -v 1)

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

时间秒杀一切 提交于 2019-12-03 17:31:00
问题 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