Ever since the switch to make extensions be read only bind-mounted files into a temporary tmpfs dir, manual addon updates appear to work, even though the updates will not actually persist.
Instead attempting to update addons should fail immediately, as the behavior is probably confusing to users.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
This fixes everything except for HTTPS-E. I'm not sure what I should do about the last case, because it's not immediately obvious to me how to override the update URL when it's set in an addon's install.rdf file.
This fixes everything except for HTTPS-E. I'm not sure what I should do about the last case, because it's not immediately obvious to me how to override the update URL when it's set in an addon's install.rdf file.
Use the version from AMO ;)
This fixes everything except for HTTPS-E. I'm not sure what I should do about the last case, because it's not immediately obvious to me how to override the update URL when it's set in an addon's install.rdf file.
Use the version from AMO ;)
In general replacing large bundle components wholesale is omething I want to avoid. I could also modify the install.rdf file, but that will cause issues with the delta updater and XPI signatures.
Ask TBB Team for that ;) (as EFF special updating sucks the same way nowadays)
I did. Among other things that Tor Browser should be doing, some dating back years.
Ultimately it's up to the Tor Browser people to change how addons are built, packaged, and shipped at this point. The sandbox doesn't auto update addons individually, and if people try to manually update them, it won't actually work regardless of what the UI says.
I'm not going to take further action here till the upstream situation changes.