Closed Bug 266546 Opened 20 years ago Closed 20 years ago

Extension Update gets wrong version of "disable targets for download"

Categories

(Toolkit :: Application Update, defect)

defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: tonglebeak, Assigned: bugs)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1

When the update searches for an update to "Disable Targets for Download", it
says it finds one, version .7. However, when it downloads and installs, it spits
out an error saying along the lines of "Disable targets for download 0.5 cannot
be installed because it's incompatible."

Reproducible: Always
Steps to Reproduce:
1.If 0.5 is already installed, run the update for the extension.
2.Select 0.7 as the version to update to.
3.

Actual Results:  
Firefox says 0.5 can't be installed.

Expected Results:  
Downloaded and installed 0.7, like it says it would do.

I believe that this can also be a security flaw, because if Firefox is
downloading the wrong file for this, who knows what else it could potentially
download for other things.
Does clearing the cache fix it?
Summary: Update incorrectly gets "disable targets for download" extension → Extension Update gets wrong version of "disable targets for download"
Nope
Wolf, is this another result of the update.mozilla.org bug with updates that use
the same filename?
This seems to have been fixed...
WFM per comment 4. This doesn't rate the confidential flag unless it
demonstrates a way to purposefully hack the system to force the wrong downloads
on people. If it's something only someone who could change the extension can do,
then they could just do evil things silently in the extension code itself.
Group: security
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.