forked from EFForg/https-everywhere
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathChangelog
More file actions
131 lines (120 loc) · 5.19 KB
/
Changelog
File metadata and controls
131 lines (120 loc) · 5.19 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
0.9.7:
* Support firefox 5 and 6 betas
* Numerous improvements and fixes to Google and GoogleServices support
* Fixes to AmazonAWS
* Secure j.mp via bit.ly
* Fix gentoo bugs
0.9.6:
* Support firefox 4.0.1
* Unbreak recaptcha
* Disable google.com/jsapi (which was breaking some embedded maps, though
that bug *might* have been fixed)
0.9.5:
* WashingtonPost is broken and seems to be staying that way; disable it :(
* Replace "Enable All" with "Reset Defaults"
* Fixes & Improvements to WordPress + Mozilla
0.9.4:
* Significant performance improvements
* Disable Cisco by default
* Fixes & improvements to: NYTimes, WashingtonPost, Cisco, WordPress
* Support Google Code
* Disable Google Custom Search Engines (they don't work)
* Support global installation for OS distributions (thanks dm0)
0.9.2:
* Fix a bug in our redirection loop detection that was causing touble with
some parts of NYTimes, Facebook, and other sites
0.9.1:
* Unbreak the "all x news articles" links in Google News
* Exclude nytimes.com/roomfordebate, since it's broken in https.
0.9.0:
* This is our "Firesheep" release. It has numerous anti-firesheep
improvements!
* Split the stricter parts of the Facebook rule into a "Facebook+" rule.
It's what's required to protect Facebook from Firesheep and similar cookie
theft attacks, but it may break apps, because apps.facebook.com currently
has the wrong cert.
* Allow rulesets to specify that the secure flag should be set on some
cookies even if the site operator failed to do so
* Ship rules for:
- Amazon S3 (AWS)
- Github
- Bit.ly
- Dropbox
- Evernote
- Cisco
* Extensive improvements (including secure cookies) in the Twitter and
Facebook rules
* Support for full Live / Hotmail encryption
* Significant performance optimisation decreases CPU load
Fixes:
https://trac.torproject.org/projects/tor/ticket/1656
https://trac.torproject.org/projects/tor/ticket/2194
* Rearrange our Channel Replacement code!
Fixes https://trac.torproject.org/projects/tor/ticket/1684
https://bugzilla.mozilla.org/show_bug.cgi?id=548102
Thanks to Giorgio Maone and Boris Zbarsky!
* Add scrollbars if there are a lot of rules present in the Preferences
dialog (may still be somewhat buggy...)
* Optimise GoogleServices.xml and support Google code search
* Patch for future compatiability with Request Policy:
https://trac.torproject.org/projects/tor/ticket/1574
* Support for the Firefox 4 API
* The Amazon rule was causing a lot of glitches; it is now off by default
* Control log verbosity with an about:config variable
* Numerous minor rule improvements
0.2.2:
* Fix a glitch in the Content Policy path that may or may not have been
responsible for these bugs:
https://trac.torproject.org/projects/tor/ticket/1700
https://trac.torproject.org/projects/tor/ticket/1672
https://trac.torproject.org/projects/tor/ticket/1673
The patch breaks toolbar search suggestions. And who knows what else?
* Don't send some country homepages to https://www.google.com/webhp?hl= ;
use https://encrypted.google.com instead
* Cleanup and refactor the URI replacement and rewriting code. Should
hopefully fix https://trac.torproject.org/projects/tor/ticket/1649
* Add a Google APIs rule
* Remove some Extremely Nasty code that would delete malformed rulesets (!)
(it was pasted from Torbutton's cookie handling logic...)
* Add code.google.com to Google Services
* The client=firefox* workaround is no longer necessary once we're sending
non-US users to encrypted.google.com rather than www.google.com
* Better coverage for GMX, Google services, Twitter
* Scroogle homepage in HTTPS
* Add rules for
- Mail.com logins
- Microsoft (limited coverage)
* Fix a nasty Google/Wikipedia bug within 0.2.2.development.{1,2}
0.2.1:
* Although google said https://www.google.com would continue to work, that
wasn't absolutely true.
* The new encyrpted.google.com seems to require queries to be #q=thing
rather than search?q=thing, at least some of the time. So let's do that.
0.2.0:
* Work around the fact that Google does not allow client=firefox* HTTPS
searches from outside the US, by rewriting those URIs
* Add rules for:
- Amazon
- GMX
- Live.com (Hotmail logins)
- Meebo
- the Netherlands Government
- Wordpress.com
- Zoho
* Remove the assumption that non-US searches would always start with an hl=
language parameter
* Handle searches to the google.com/firefox script better
* Remove accidental duplicates of a couple of rules!
* Bump maxVersion into the future so we're compatible with Firefox alphas
* Fix more legacy eff.org bugs
0.1.2:
* Apparently, we are not actually compatible with Firefox 2.0.0.x, so don't
install with it!
* Further generalisation of Wikimedia rules
* Fix bugs in the handling of obscure parts of eff.org and torproject.org
* A bug in a user rules file should produce an error, rather than causing all
rules to fail to load
0.1.1:
* Generalise the Wikipedia rules to other Wikimedia services
* In preferences window, add a link to instructions for writing one's own
rules