3 ms·
There are a bunch of things I don't understand in the patches. I wish they'd link to a bugtracker or something. (Incidentally, Chrome/Chromium has a public bugt
by geofft 12y ago
There are a bunch of things I don't understand in the patches. I wish they'd link to a bugtracker or something. (Incidentally, Chrome/Chromium has a public bugtracker: Iridium seems to have a Trac that nobody used apart from creating two tickets.)
* Enabling Do-Not-Track by default: https://git.iridiumbrowser.de/cgit.cgi/iridium-browser/commit/?id=9db15d3834683bcb621c263e9aef49ba17f413a2 https://git.iridiumbrowser.de/cgit.cgi/iridium-browser/commi...
This is widely considered to be a questionable plan, and violates the Internet-Draft (section 6.3: "It MUST NOT transmit OPT-IN without explicit user consent."). Are they asserting that merely having Iridium over Chromium is explicit user consent?
* Disabling hyperlink auditing: https://git.iridiumbrowser.de/cgit.cgi/iridium-browser/commit/?id=411e31b4bcefdff1e93704c5c4ff76572d0c2596 https://git.iridiumbrowser.de/cgit.cgi/iridium-browser/commi...
As the HTML spec (https://html.spec.whatwg.org/multipage/semantics.html#hyperlink-auditing https://html.spec.whatwg.org/multipage/semantics.html#hyperl...) points out, the behavior of hyperlink auditing in terms of privacy impact is already achievable in several ways, like server-side redirects, JavaScript, etc. The goal with the feature was to make performance and user experience better, while not changing the privacy standard. Is it being changed in Iridium for privacy reasons or for other reasons?
* Increasing the default client certificate (?) length to 2048 bits from 1024 bits: https://git.iridiumbrowser.de/cgit.cgi/iridium-browser/commit/?id=4b16cfc4abc4482a0b4ccf9321c547685f26c927 https://git.iridiumbrowser.de/cgit.cgi/iridium-browser/commi...
Given how much Google's been yelling about 1024-bit server certs, this seems like an obvious thing to change upstream. Has it been submitted / is there a reason they haven't changed it in Chromium?
* Disabling globally-installed NPAPI plugins on OS X, but still allowing those installed in your homedir: https://git.iridiumbrowser.de/cgit.cgi/iridium-browser/commit/?id=fd5b986d422963f5466c94ab0bae012c9e059902 https://git.iridiumbrowser.de/cgit.cgi/iridium-browser/commi...
Why? (There's probably a reason, I just have no idea what it might be.)
* Emptying the list of CAs allowed to sign EV certs: https://git.iridiumbrowser.de/cgit.cgi/iridium-browser/commit/?id=2b97ce66913b9e6e1c03214132e9432e75fc21ea https://git.iridiumbrowser.de/cgit.cgi/iridium-browser/commi...
Why? As far as I can tell, the only effect is that EV certs will show up as normal certs (green lock, instead of bar showing the organization name). What does this have to do with improving security or privacy?