handsomeransoms | 12 years ago | on: Help EFF test Privacy Badger, our new browser extension for privacy
handsomeransoms's comments
handsomeransoms | 12 years ago | on: Help EFF test Privacy Badger, our new browser extension for privacy
That's awesome! At Mozilla we've been daydreaming about incorporating something like that into the product. Especially with the proliferation of both in-browser content policies (CSP, Mixed Content blocking, etc.) and out-of-browser content policies (addons like Privacy Badger, ABP, Ghostery, etc.) it's almost impossible to understand the root cause of what's breaking a page, especially if you're not a technical user.
> but also making it work efficiently (wrote custom ABP engine from scratch which doesn't suffer the real one's abuse of memory/CPU)
For the Firefox version of Privacy Badger, we also eschewed the ABP engine in favor of something we wrote ourselves. Don't get me wrong, ABP is a great tool and we learned a lot from its code - but we wanted something as lean and performant as possible. I'd be interested to see the approach you took!
> only one extension is allowed to modify the HTTP headers
> it will break any previously installed extension
That sounds like a shortcoming in Chrome's Extension API. Firefox is somewhat better in that we do not restrict addons based on the behavior of other addons, so multiple addons are allowed to modify a request's headers. Unfortunately, the order in which the request is passed from handler to handler is not guaranteed, so in practice this may not end up being so useful.
We're trying to improve this situation by rewriting the Gecko Content Policy API [0], but that's a large project with no clear deadline.
[0] https://groups.google.com/forum/#!msg/mozilla.dev.platform/v...
Generally I think your addon and Privacy Badger are targeted at different audiences and have different use cases. It is too bad they are incompatible with each other - I, for one, would like to have both installed. Perhaps we can resolve this by talking to the Chrome devs about their Extension API?
- One of the Privacy Badger devs
handsomeransoms | 12 years ago | on: Help EFF test Privacy Badger, our new browser extension for privacy
- One of the Privacy Badger devs
handsomeransoms | 12 years ago | on: Chrome: From NSS to OpenSSL
[0] https://wiki.mozilla.org/SecurityEngineering/mozpkix-testing... [1] https://wiki.mozilla.org/SecurityEngineering/mozpkix-testing...
handsomeransoms | 12 years ago | on: Chrome: From NSS to OpenSSL
Of course, it is open source, so patches are always welcome. (Firefox dev here)
handsomeransoms | 12 years ago | on: Heartbleed should bleed X.509 to death
Pinning directly in the app puts trust in the developers of the app instead, which is indirect and prone to lag. It is also generally fragile (have to issue app updates for cert revocations) and can be hard to scale. How many secure sites does your app need to connect to? Is it flexible, unknown? How are you, the app developer, going to validate those certs beyond relying on the CA PKI? (and then you're back to square one).
handsomeransoms | 12 years ago | on: Neel Mehta donates Heartbleed bounty to Freedom of the Press Foundation
https://pressfreedomfoundation.org/
Huge thanks to Neel, whose donation pushed us over the edge to meet our goal!
(Full disclosure: I work for the Freedom of the Press Foundation)
handsomeransoms | 12 years ago | on: Firefox 28 Release Notes
handsomeransoms | 12 years ago | on: Npm's Self-Signed Certificate is No More
Because then you're susceptible to remote MITM? VPNs are useful but do not replace end-to-end encryption.
handsomeransoms | 12 years ago | on: On the Timing of iOS’s SSL Vulnerability and Apple’s ‘Addition’ to NSA’s PRISM
handsomeransoms | 12 years ago | on: Firefox 27 Released
For page load lag, addons like ABP are often especially bad because they're running the URI of each request against a bunch of regex filters to determine if the load should be allowed to begin.
handsomeransoms | 12 years ago | on: Firefox 27 Released
Does this mean that we can use Task.js in ordinary web pages now?
handsomeransoms | 12 years ago | on: Edward Snowden nominated for Nobel peace prize
I'll let you fill in the comparisons to widespread sexism, racism, and homophobia for yourself. Go back to the leaders of the American civil rights movement and tell them to let things "percolate through society" so they can know "where to draw reasonable lines".
[0] http://www.t-vox.org/index.php?title=Cisgender_privilege
handsomeransoms | 12 years ago | on: The New Aaron Swartz Documentary at Sundance
This contrived conclusion mars an otherwise sensitive synopsis of the film, and through that, Aaron's life. The drive to reform CFAA continues. Strides are being made for open access to research [0], the cause that lead to Aaron's conviction. The Strongbox/Deaddrop project is being actively developed and deployed to protect journalist-source communication and empower whistleblowers all over the world. [1]
The fight is not over - it has only just begun.
[0] http://www.washingtonpost.com/blogs/the-switch/wp/2014/01/17... [1] https://github.com/freedomofpress/securedrop
handsomeransoms | 12 years ago | on: Asm.js AOT compilation and startup performance
It is actually quite different, read: http://static.googleusercontent.com/media/research.google.co...
There are fact several layers of sandboxing, which dramatically limit both the ability to create exploits, and the damage that a successful exploit can cause.
To be clear: I work for Mozilla, and I think Asm.js is a great project with a lot of potential for developers and the web; however, Google did a lot of innovative work to have a great security foundation for NaCL, which was not a real goal for NaCL AIUI.
> a "beta product" shows that it's not 100% safe
There is no correlation here.
> in the context of an interpreted, thoroughly tested JS engine, which is very much more secure.
> but since JS engines are heavily optimized, it makes the security problem disappear completely because JS is an old language, so all security problems are already known.
The continuing drive for JS performance has lead to new avenues for serious exploits, some of which are poorly understand are only have been partially mitigated by widely used engines. For just one example, see http://www.matasano.com/research/Attacking_Clientside_JIT_Co...
> The fact android uses java for its app is another demonstration of the easiest path to security.
I lol'ed.
handsomeransoms | 12 years ago | on: How's my SSL?
handsomeransoms | 12 years ago | on: Firefox 26 is released
handsomeransoms | 12 years ago | on: The Mozilla Developer Network has a New Face
handsomeransoms | 12 years ago | on: Multiprocess Firefox
handsomeransoms | 12 years ago | on: Scientist-developed malware covertly jumps air gaps using inaudible sound