Closed Bug 759318 Opened 13 years ago Closed 13 years ago

stop excluding distribution/, extensions/, and mozilla.cfg from OS X signature

Categories

(Release Engineering :: Release Automation: Other, defect)

defect
Not set
normal

Tracking

(firefox14 disabled, firefox15 disabled, firefox-esr10 wontfix)

RESOLVED FIXED
Tracking Status
firefox14 --- disabled
firefox15 --- disabled
firefox-esr10 --- wontfix

People

(Reporter: bhearsum, Assigned: bhearsum)

References

Details

Attachments

(2 files)

I spoke with Kev about whether or not we want to do bug 758188. As part of that, he pointed out that having distribution/, extensions/, and mozilla.cfg excluded from the signature allows for behavioral modification of Firefox without invalidating the signature. For example, a bad guy could add malware or other such things, repack it, and distribute it. The signature would still be "Mozilla Corporation". We need to lock this down. Kev doesn't think it needs to block 13.0 since 10.8 hasn't shipped yet, but we should look at doing this soon. Doing this means that our partner repacks (the ones run with release automation) and BYOB builds will need to resign the .app as part of their process.
Concur, per comment #0.
Let's let the security team weigh in on this topic. See my comment in https://bugzilla.mozilla.org/show_bug.cgi?id=758188#c8.
My initial patch doesn't seem to be working as I would expect....the CodeResources file I used no longer excludes distribution et. al, and the partner repack scripts do send a new thing to the signing server to be resigned, and CodeResources gets modified....but distribution/distribution.ini don't end up being in it. I wonder if codesign only re-checksums existing files in the CodeResources file when it resigns a file, rather than gathering a new set of files. I don't think this will make it for 13.0 final.
Attached patch dmg sign mac partner builds (deleted) — Splinter Review
(In reply to Ben Hearsum [:bhearsum] from comment #5) > My initial patch doesn't seem to be working as I would expect....the > CodeResources file I used no longer excludes distribution et. al, and the > partner repack scripts do send a new thing to the signing server to be > resigned, and CodeResources gets modified....but > distribution/distribution.ini don't end up being in it. I wonder if codesign > only re-checksums existing files in the CodeResources file when it resigns a > file, rather than gathering a new set of files. Oops, turns out that I was comparing an en-US vanilla vs. a localized repack which explains why CodeResources differed. Found a quick fix for that.
Attachment #628352 - Flags: review?(rail)
Attachment #627942 - Flags: review?(ted.mielczarek)
Attachment #628352 - Flags: review?(rail) → review+
We need to port this to Thunderbird too.
Comment on attachment 627942 [details] [diff] [review] stop excluding things that can modify behaviour Review of attachment 627942 [details] [diff] [review]: ----------------------------------------------------------------- ::: browser/app/macbuild/Contents/_CodeSignature/CodeResources @@ -22,5 @@ > - <key>omit</key> > - <true/> > - <key>weight</key> > - <real>10</real> > - </dict> Curious, is this going to break BYOB? Do we have to re-sign BYOB builds then?
Attachment #627942 - Flags: review?(ted.mielczarek) → review+
(In reply to Ted Mielczarek [:ted] from comment #8) > Comment on attachment 627942 [details] [diff] [review] > stop excluding things that can modify behaviour > > Review of attachment 627942 [details] [diff] [review]: > ----------------------------------------------------------------- > > ::: browser/app/macbuild/Contents/_CodeSignature/CodeResources > @@ -22,5 @@ > > - <key>omit</key> > > - <true/> > > - <key>weight</key> > > - <real>10</real> > > - </dict> > > Curious, is this going to break BYOB? Do we have to re-sign BYOB builds then? Now that you mention it, it probably will. We do have a bug on file for getting mac signing machines for BYOB, but no progress there yet: bug 563798.
Comment on attachment 627942 [details] [diff] [review] stop excluding things that can modify behaviour http://hg.mozilla.org/mozilla-central/rev/708f3d693a84
Attachment #627942 - Flags: checked-in+
Attachment #628352 - Flags: checked-in+
Landed cleanly.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment on attachment 627942 [details] [diff] [review] stop excluding things that can modify behaviour This patch increases the number of files included in the signature of Firefox. I believe it's important to get on Aurora, Beta, and ESR so that we can make sure nobody can effect behaviour in these builds without breaking the signature.
Attachment #627942 - Flags: approval-mozilla-esr10?
Attachment #627942 - Flags: approval-mozilla-beta?
Attachment #627942 - Flags: approval-mozilla-aurora?
Comment on attachment 627942 [details] [diff] [review] stop excluding things that can modify behaviour Approving for Aurora and Beta, but let's see if this is needed for the ESR.
Attachment #627942 - Flags: approval-mozilla-beta?
Attachment #627942 - Flags: approval-mozilla-beta+
Attachment #627942 - Flags: approval-mozilla-aurora?
Attachment #627942 - Flags: approval-mozilla-aurora+
We backed out the distribution/ part of the CodeResources patch in bug 770996, because it completely broken partial updates for partner builds.
Comment on attachment 627942 [details] [diff] [review] stop excluding things that can modify behaviour Waiting for ESR17 to roll this out.
Attachment #627942 - Flags: approval-mozilla-esr10? → approval-mozilla-esr10-
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: