Tor does not have a single threat model. It provides a various degrees of protection against different adversaries: local observers, malicious node operators, observers of the underlying Internet, etc. That said, the usual stated adversary in security analyses is one that owns a fraction c/n of the relays, as well as some clients and destinations. With all ...
The recommended way to browse the web through Tor is to use the Tor Browser Bundle. Using any other browser will make you different from the common anonymity set of Tor users.
Changing the configuration of the Tor Browser is not recommended exactly for the same reason: it is likely to make the browser behave differently from everyone else's.
Tails include ...
Tor and I2P have a number of similarities. Tor however has a big benefit when you are leaving the Tor network. I2P's exit system is basically a really limited set of proxies, which makes attacking you by analyzing the traffic at the exit easier. It's a game of numbers. There are very few exit nodes (they call them outproxies sometimes) compared to Tor.
You can use several I2P eepsites from the 'normal' internet and so also through Tor. Several people run so-called inproxies. There are/were:
At the moment only the last works. Just append .us (or .in, .to when the other two are back online) to the I2P url. So if you want to reach zzz's eepsite enter http://zzz.i2p....
Visit "Hidden Services Manager" from your "Router Console" homepage or directly (with defaults):
Configured by default are:
I2P HTTPS Proxy Port 4445
Description: HTTPS proxy for browsing eepsites and the web
I2P HTTP Proxy Port 4444
Description: HTTP proxy for ...
Instead of using a socks server with a routing feature, you could always use some intelligent proxy selection in firefox itself.
Using the FoxyProxy addon, you can say "Use proxy for URLs matching http://*.i2p.; use proxy for everything else".
[Ceterum censeo: using normal Firefox instead of the TBB is probably not very safe.]
If you're using good code that doesn't 1. give away your personal information and 2. doesn't try to steal your visitor's personal information, then there's nothing wrong with it.
If you're not a web developer and you want to use some ...
So, you have a checklist to verify:
First, you need to check allowed clients list.
Second - IP binding in the proxy service, it should be explicitly 127.0.0.1, it can be 0.0.0.0 - and in I2P it used to cause some glitches.
Third - check the logs, a false.i2p can be not working, there're other proxies in I2P, try them too. If it is a remote problem - it will ...
I think (maybe) it means they don't use standard Internet protocols to provide the same Internet services.
For example, when you go to https://tor.stackexchange.com/, your browser sends a DNS request to your default DNS server, sends a TCP SYN packet (make a connection) to the address it resolves to, and sends a HTTP request over the connection. When you go ...
See I2P's comparison page.
Packet switched instead of circuit switched
implicit transparent load balancing of messages across multiple peers, rather than a single path
resilience vs. failures by running multiple tunnels in parallel, plus rotating tunnels
scale each client's connections at O(1) instead of O(N) (Alice has e.g. 2 inbound tunnels that are used ...
The pro's of i2p is that in the tunnel-model it's possible to make a "garlic routing", but they're not implemented it yet in full scale. it will make possible to transmit multiple tunnel's packets in one "package". And I2P uses local site-naming directories rather one distributed one in Tor. Basically - except a tech deep-sea details - there's the main ...
Answering in the context of the edit (accessing clearnet):
Tor is better than I2P for accessing clearnet, because that is what it was originally designed for. Exit nodes are a fundamental part of the Tor architecture, whereas I2P was designed for in-net communication (there is no difference between a client and server at the network level). In I2P, we call "...
There are a lot of questions here.
It's up to you to decide which you prefer. This is a Tor related stackexchange so even if "better" was quantifiable, it would be biased. Tor is not I2P, and vis versa. It looks like I2P has the difference in their design here. Good luck.
TAILS did this for a while until a vulnerability in I2P was found that compromised ...
You can make the settings in about:config. Just enter it into the address bar and read+confirm the warning. When the config page is open, search for network.proxy. You'll see network.proxy.socks_port set to 9150. You can double-click on network.proxy.http_port and set it to 4444. You should also make some settings for other proxies.
When you're changed the ...