News for hackers. Stuff that matters.

A comment on iOS Static Libraries Are, Like, Really Bad. Parent comment

Re:iOS Static Libraries Are, Like, Really Bad by quesera on Sunday January 12, 2014 @07:14PM (#7048086)
The code signature is on the multiple architecture binary, thereby including any statically linked object files, right?

If Apple were to add dynamic libs, they would presumably be separate binary files, with their own signatures. This could raise the concern noted by 0x0.

[ Parent | on HN ]
Re:iOS Static Libraries Are, Like, Really Bad by teacup50 on Sunday January 12, 2014 @08:04PM (#7048243)
> If Apple were to add dynamic libs, they would presumably be separate binary files, with their own signatures.

No. That's not how it works on Mac OS X today, where bundled shared libraries are supported.

[ Parent | on HN ]
Re:iOS Static Libraries Are, Like, Really Bad by quesera on Friday January 17, 2014 @09:51AM (#7076004)
That's right, thanks.

Separate binary files have individual hashes, which are included in the package manifest file. The manifest is then signed, so a single signature covers all hashed files in the manifest.

Curiously though, in all of the MAS apps I've checked, bundled dylibs are explicitly not hashed in the manifest. This is the developers choice, but perhaps a default?

[ Parent | on HN ]