[Adium-devl] Keychain Issues
ofri.wolfus at gmail.com
Wed Apr 16 12:51:50 UTC 2008
The first section in that page says "Depending on the situation,
codesign may add to your Mach-O executable file, add extended
attributes to it, or create new files in your bundle's Contents
directory. None of your other files is modified."
So apparently, it either stores the signature in the executable itself
or in its extended attributes. Is it just me or extended attributes
really feel too fragile?
On 16/04/2008, at 15:31, Peter Hosey wrote:
> On Apr 16, 2008, at 04:43:10, Ofri Wolfus wrote:
>> That's really interesting as Apple's documentation explicitly says
>> each architecture in a universal binary is signed independently and
>> that doing UB tricks on such executable shouldn't break its
> Our CodeResources file (it's just a plist) lists only one signature
> for the AdiumAppleScriptRunner, so that's probably it.
> What I find interesting is that it *doesn't* contain a signature for
> Contents/MacOS/Adium. Is the signature stored in the executable?
> Adium-devl mailing list
> Adium-devl at adiumx.com
More information about the Adium-devl