Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Code signing CURLHandle? #11

Open
gbrhaz opened this issue Apr 11, 2013 · 2 comments
Open

Code signing CURLHandle? #11

gbrhaz opened this issue Apr 11, 2013 · 2 comments

Comments

@gbrhaz
Copy link

gbrhaz commented Apr 11, 2013

Hey,

I was just seeing if it could be code signed, and it actually went through fine, but when I made some changes to the .pch file (commented the log #defines) it stopped working. Validation just wouldn't run. Any ideas what would be causing this?

@mikeabdullah
Copy link
Collaborator

It's not something I've really tested myself. Curious, why do you want to code sign CURLHandle? I think in general it's desirable to sign your overall app, than an individual framework.

@terrencetalbot
Copy link
Contributor

In my experience with Sandvox, Mac App Store validation required (after some point in time in the last six months) that frameworks be individually signed with at least the correct bundle identifier and your dev id. This rule also appears to include any embedded dylibs. FWIW, we started signing CURLHandle in Sandvox like this:

codesign -s DEV_ID --prefix com.karelia.CURLHandle.dylibs. --force "${PATHTOSIGN}"

and then Apple seemed happier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants