Re: Signed Extensions
Daniel Veditz <[email protected]>
| Newsgroups | gmane.comp.mozilla.devel.seamonkey |
|---|---|
| Message-ID | <CADYDTCA9OaSZQTcgZWJj0+8GE72OJS_PNiNDAtU=cCcZTxnsug@mail.gmail.com> |
Why would we update the maxVersion or anything else? We're signing the archive, not modifying it any more than necessary. If the existing maxVersion works then it will still work; if the existing maxVersion doesn't work then the author should already have plans to update it and it will get re-signed when that happens. I don't understand your comment about the filenames. None of the add-ons I have installed have versions as part of the name. How many people are actually reaching into our CDN and using the internal filename? In any case the signed/not-signed versions were not intended to be different in any meaningful way and only have a different version as a hack to trigger an update. You'd have better luck reaching the AMO developers in an addons-related forum rather than here. I'm guessing the damage is done and it's not worth re-generating all the signed files to fix it at this point, and for future add-on updates it won't be an issue since there will only ever be the signed version. -Dan Veditz