Closed Bug 524537 Opened 16 years ago Closed 16 years ago

Whitelist new add-ons domain

Categories

(Toolkit :: Add-ons Manager, defect)

Product:
Toolkit
Component:
Add-ons Manager
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
blocking1.9.1 --- -

People

(Reporter: samuel.sidler+old, Assigned: mossop)

Details

We need to whitelist a new domain for add-ons. Justin will probably tell you what that domain is when he knows. This needs to block 1.9.2, 1.9.1.5, 1.9.0.16, and 1.8.1.24. (yay) I'm guessing we need to update Thunderbird as well (maybe? I don't know how add-ons work there)... Probably should tell SeaMonkey too.
Flags: wanted1.9.0.x+
Flags: wanted1.8.1.x+
Flags: blocking1.9.2?
Flags: blocking1.9.0.16+
Flags: blocking1.8.1.next+
blocking1.9.1: --- → .5+
Hrm, why?
Lots of detail here!
Let's assume the total lack on information in this bug means it's somehow sensitive, and hide the bug so maybe we can get filled in. If this was filed by some random user it'd be in INCOMPLETE-ville by now.
Group: mozilla-confidential
Turns out that there's no actual need to do this, false alarm.
Status: NEW → RESOLVED
Closed: 16 years ago
Flags: wanted1.9.0.x-
Flags: wanted1.9.0.x+
Flags: wanted1.8.1.x-
Flags: wanted1.8.1.x+
Flags: blocking1.9.2?
Flags: blocking1.9.2-
Flags: blocking1.9.0.16-
Flags: blocking1.9.0.16+
Flags: blocking1.8.1.next-
Flags: blocking1.8.1.next+
Resolution: --- → INVALID
blocking1.9.1: .5+ → -
Group: mozilla-confidential
The code changes that this would have required in XPInstall would still be a good idea, but I guess a fresh start would be a better idea
You need to log in before you can comment on or make changes to this bug.