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.
Rather short notice, however this release will be somewhat minor but please put comment any extra needed checks, call outs, or notes that may be needed.
Release Notes (incomplete):
Change "Block all unencrypted requests" language to "Encrypt all sites eligible"
Amend check_rules.py fetch test to disable rules only if all rules are problematic,
and comment rules out if other rules are functional in the set
Updating this, since EFF is about to go on holiday, we decided to postpone the release until after we get back so there will be full support in case an issue occurs.
This update reverted my EASE setting. That could be very problematic in some threat models. I could swear there was an issue for this but I can't find it anymore. Anyone remembers this?
Looks like an oversight on my part led to the "EASE" language not making it into this release. Merging #17156 into master and scheduling another release for this month soon.
This update reverted my EASE setting. That could be very problematic in some threat models. I could swear there was an issue for this but I can't find it anymore. Anyone remembers this?'
@Bisaloo Do you think the issue was resolved and returned? Or was this an issue that was closed? I'll search around for it in the meantime.
I'm not sure. I don't know if it was open of closed and I'm even starting to wonder if I'm not mixing things up with similar but different issues 😕 . I'll keep looking.
Activity
[-]Release 2018.12.19 forthcoming[/-][+]Release 2018.1.03 forthcoming[/+]zoracon commentedon Dec 19, 2018
Updating this, since EFF is about to go on holiday, we decided to postpone the release until after we get back so there will be full support in case an issue occurs.
cschanaj commentedon Dec 23, 2018
I believe the upcoming version should be
2019.1.3😄cschanaj commentedon Dec 31, 2018
It seems that the PR labeller is crashed, #17197 and #17199 should be marked as top-1k.
Bisaloo commentedon Dec 31, 2018
Sorry, I guess that's me again. It happens every time I submit a HSTS-prune PR
[-]Release 2018.1.03 forthcoming[/-][+]Release 2018.1.8 forthcoming[/+]zoracon commentedon Jan 2, 2019
Due to some scheduling conflicts we are pushing the release to Monday since a Friday release is not ideal for obvious reasons. Bear with us!
J0WI commentedon Jan 5, 2019
#16595 fixes #15862, would be great to get some feedback there. But this could also be served in a ruleset update and does not block a new release.
Bisaloo commentedon Jan 7, 2019
If the release happens today, the date should be 2019.1.7 😉
[-]Release 2018.1.8 forthcoming[/-][+]Release 2019.1.7 forthcoming[/+]Bisaloo commentedon Jan 8, 2019
This update reverted my EASE setting. That could be very problematic in some threat models. I could swear there was an issue for this but I can't find it anymore. Anyone remembers this?
zoracon commentedon Jan 8, 2019
Looks like an oversight on my part led to the "EASE" language not making it into this release. Merging #17156 into master and scheduling another release for this month soon.
@Bisaloo Do you think the issue was resolved and returned? Or was this an issue that was closed? I'll search around for it in the meantime.
Bisaloo commentedon Jan 9, 2019
I'm not sure. I don't know if it was open of closed and I'm even starting to wonder if I'm not mixing things up with similar but different issues 😕 . I'll keep looking.