/

I2P Browser Configurations and their Attackability

This information was never very complete, and it is currently out-of-date. I am working on updating it to reflect the current set of recommendations.

Testing the attackability and fingerprintability of various browsers in an i2p context, and where possible, reducing it via whatever available configuration.

Semi-Official Firefox Browser Profile

I2P in Private Browsing Mode Firefox Extension

These 2 screenshots are from the same Firefox at the same time. As you can see, the fingerprints differ and obuscation measures have been taken.

firefox scrot firefox scrot

Deliberately misconfigured Firefox(HTTPS leak)

Minimal correct configuration for Firefox

lynx

lynx scrot

elinks

elinks scrot

ungoogled-chromium incognito mode

I2P Browsing Persona + I2P Proxifier Plugin on Chromium

Get the source code:
Show license
MIT License

Copyright (c) 2018 idk

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
Hide license
I2P