Set up a framework to fully man-in-the-middle my own browsers’ networking and see what they’re up to beyond just looking at their DNS queries and encrypted tcp packets. We force the browser to trust our mitmproxy cacert so we can peek inside cleartext traffic and made it conveniently reproducible and extensible.
It has containers for official Firefox, its Debian version, and some other FF derivatives that market a focus on privacy or security. Might add a few more of those or do the chromium family later - if you read the thing and want more then please let us know what you want to see under the lens in a future update!
Tests were run against a basic protocol for each of them and results are aggregated at the end of the post.
Posting with ambition that this can trigger some follow-ups sharing derived or similar things. Maybe someone could make a viral blog post by doing some deeper tests and making their results digestible ;)
In case you want to try this for yourself, adding container and running test for Waterfox should be about same as for Floorp that I wrote about here. Then you can really see what’s going on and reason about the difference when you see the URLs and stuff.
BTW the purpose of the report section here isn’t “look at my numbers and take my word for it” but “here’s some examples of things we can look at with this”. Please keep in mind both the Limitations section and that it’s intended as showing one way to easily and independently compare browsers yourself. Just reproducing the examples shown and then scrolling through the
.harfiles JSON is a great start. Of course, me and I assume others would be very happy if you want to share anything that comes out of that so that we can bring people up together. I’m sure there’s a lot more useful insights to derive even with a small and scoped testing protocol like the one in article and wouldn’t mind input of any nuggets other people come up with :)