341293 - LinkedIn Companion uses an external updateURL

Status: RESOLVED FIXED

(addons.mozilla.org Graveyard :: Administration, defect)

Description

[:Gijs (he/him)]

As in summary.

It's also a featured extension -> severity major.

CC-ing Mossop who brought this to our attention. Assigning to shaver who said he was "on it".

Comment 1

[alanjstr]

The only way to fix this is for us to download the XPI, change the install.rdf and up the revision.

However, anyone who already has it won't automatically get notified of the change.  Did anyone try to reach out to the author?

Comment 2

[Mike Shaver (:shaver emeritus)]

Yes, I've sent mail to the author.

Comment 3

[alanjstr]

Do we plan to audit all XPIs, or is this on as needed basis.

Comment 4

[Mike Shaver (:shaver emeritus)]

As we notice them, I imagine.

If someone writes a tool that lets us notice all of them at once, that would be fine too. :)

(That discussion doesn't belong in this bug, though; mailing list or IRC or something if you want to continue it, please!)

Comment 5

[Michael Morgan [:morgamic]]

AMO BUGSPAM FOR COMPONENT MOVE AND DELETE (FILTER ME)

Comment 6

[Reed Loden [:reed]]

AMO BUGSPAM FOR QACONTACT FIX (FILTER ME)

Comment 7

[Dave Townsend [:mossop]]

Since this doesn't appear to have progressed in nearly three months, can the extension at least be removed from the recommended extensions page

Comment 8

[Cameron]

Listings didn't get deleted after all, just renamed.

Comment 9

[Mike Shaver (:shaver emeritus)]

Apologies for appearance, but there has been progress.  The next LinkedIn companion update will have the appropriate updateURL (that is: none).  I don't believe that it's in the interests of our users to force an update on the LinkedIn Companion's installed base to resolve what is a violation of the letter, but not the spirit, of our external-update policy.  I'll leave this open until the next update is pushed (I have no ETA), but I don't think further action is required at this point.

(I should add that LinkedIn and I were foiled in an attempt to resolve this more elegantly, as an update.rdf can't specify a new updateURL -- alas!)

Thanks for your diligence here; it's appreciated.

Comment 10

[Mike Shaver (:shaver emeritus)]

I finally got the account stuff sorted out, and the update pushed, so we're all good here now.  At long last!