Post
Topic
Board Economics
Re: Bitcoin adoption slowing; Coinbase + Bitpay is enough to make Bitcoin a fiat
by
AnonyMint
on 12/07/2014, 00:02:28 UTC
Saw that Monero is partnering with I2P:

https://geti2p.net/en/blog/post/2014/05/25/Monero-partnership

Either the Monero developers don't intend to provide anonymity against the NSA or don't understand that (especially low-latency) Chaum mix-nets are not immune to timing analysis by a global adversary such as the NSA, GCHQ, and other national security agencies:

https://geti2p.net/en/comparison/tor

Quote
The I2P/Tor outproxy functionality does have a few substantial weaknesses against certain attackers - once the communication leaves the mixnet, global passive adversaries can more easily mount traffic analysis. In addition, the outproxies have access to the cleartext of the data transferred in both directions, and outproxies are prone to abuse,

Here are more citations:

https://tails.boum.org/doc/about/warning/index.en.html#index4h1

Quote
Confirmation attacks

The Tor design doesn't try to protect against an attacker who can see or measure both traffic going into the Tor network and also traffic coming out of the Tor network. That's because if you can see both flows, some simple statistics let you decide whether they match up.

That could also be the case if your ISP (or your local network administrator) and the ISP of the destination server (or the destination server itself) cooperate to attack you.

Tor tries to protect against traffic analysis, where an attacker tries to learn whom to investigate, but Tor can't protect against traffic confirmation (also known as end-to-end correlation), where an attacker tries to confirm an hypothesis by monitoring the right locations in the network and then doing the math.

Quoted from Tor Project: "One cell is enough to break Tor's anonymity".

Also the weaknesses you listed are not complete. Every low-latency Chaum mixnet (i.e. Tor, I2P, Anonymox, etc) is subject to timing attacks due to a global adversary (e.g. national security agencies) that can monitor most or all of the encrypted (even if they can't decrypt it) traffic passing in and out of the proxy servers.

http://en.wikipedia.org/w/index.php?title=Onion_routing&oldid=592703635#Weaknesses
https://tails.boum.org/doc/about/warning/index.en.html#index4h1
https://tails.boum.org/doc/about/warning/index.en.html#index7h1
http://en.wikipedia.org/wiki/Tor_%28anonymity_network%29#Exit_node_eavesdropping

Quote from: Dan Egerstad, a Swedish security consultant
If you actually look in to where these Tor nodes are hosted and how big they are, some of these nodes cost thousands of dollars each month just to host because they're using lots of bandwidth, they're heavy-duty servers and so on. Who would pay for this and be anonymous?


Note the NSA is sharing data with relevant authorities in each country in the G20 to help them hunt down the wealth:

Since the Knowledge Age is rising [3], socialism is peaking into an economic collapse soon (maybe to rise even higher in future), thus we headed into a crazy period where the governments will try to fund the $150227 trillion global debt bubble [4] by hunting down all private capital (G20 announced a database for this today, NSA will contribute and note this is the bankster business model for them to own everything), then as Bitcoin is taken over top-down then the alternative coin with the above features will take over and become the surviving private sector...


Good to see the I2P developers updated their website about timing analysis after I gave them the heads up (about such vulnerability of low-latency mix-nets) nearly a year ago quoted as follows.

Apologies if this has already been asked upthead. I didn't have time to read the entire thread.

Does Anoncoin not view high-latency for I2P as critically urgent as I do?

https://bitcointalk.org/index.php?topic=273197.msg2950363#msg2950363
https://bitcointalk.org/index.php?topic=276849.msg2955966#msg2955966
https://bitcointalk.org/index.php?topic=273197.msg2950849#msg2950849

I2P doesn't plan on implementing until version 3.0? When is that ETA?