You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
This release fixes a race condition that effects the setting of global variables. See #12268
Tor Browser is not effected. Anyone using storage.sync will be effected by this change. Anyone who has previously changed a global variable (counter, addon on/off state, http nowhere toggle) will now see this change persisting across restarts.
I have running duplicate-whitelist-cleanup.sh and ruleset-coverage-whitelist-cleanup.sh in my normal release checklist. I don't have hsts-prune in this checklist, as this takes a significant amount of time and slows down the release process. It's also fine to run this perennially, not tightly bound to the release cycle. That being said, I can run it now.
Chrome has not yet removed any domains from the preload list for failing to keep up the requirements after submission, but there are plans to do so in the future.
This indicates that they are starting to remove domains from the list according to the preload requirements.
Luckily, in 8bda7ce there were only removals and nothing was re-added. This tends to confirm the intended functionality of the hsts-prune script not to remove domains that do not strictly comply to the preload requirements.
Activity
gloomy-ghost commentedon Aug 31, 2017
Hainish commentedon Aug 31, 2017
I have running
duplicate-whitelist-cleanup.shandruleset-coverage-whitelist-cleanup.shin my normal release checklist. I don't havehsts-prunein this checklist, as this takes a significant amount of time and slows down the release process. It's also fine to run this perennially, not tightly bound to the release cycle. That being said, I can run it now.Hainish commentedon Aug 31, 2017
Preloaded domains removed in 13c2034
cschanaj commentedon Aug 31, 2017
I'd like to note that hsts-prune is still pointing to the discontinued Firefox Aurora release, see #12139
Hainish commentedon Aug 31, 2017
8bda7ce incorporates a reversion and re-run of the
hsts-pruneutility.Earlier this month, https://hstspreload.org/ removed the language:
This indicates that they are starting to remove domains from the list according to the preload requirements.
Luckily, in 8bda7ce there were only removals and nothing was re-added. This tends to confirm the intended functionality of the
hsts-prunescript not to remove domains that do not strictly comply to the preload requirements.[-]Release 2017.8.30 forthcoming[/-][+]Release 2017.8.31 forthcoming[/+]Hainish commentedon Aug 31, 2017
Finished