RE: codesign vs. install_name_tool
RE: codesign vs. install_name_tool
- Subject: RE: codesign vs. install_name_tool
- From: "Dallman, John" <email@hidden>
- Date: Thu, 23 Feb 2012 18:34:55 +0000
- Thread-topic: codesign vs. install_name_tool
> This is reasonable, you can also look into using @rpath. (i.e. make your
> library's install_name relative to "@rpath", and your clients specify, at
> buildtime, the runtime search paths in which to find your library).
That's looking like the right answer, once I can go through all the cases.
> That said, if your customers are including your library inside of their
> app bundle, they can change the library however they want, and just sign
> it with their identity.
I'm wanting to avoid giving them the chance to both (a) need to break the
signature and (b) fail to re-sign the library. Murphy's Law dictates that
someone will exploit this chance if they have it.
thanks,
--
John Dallman
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden