Hornet
March 18th, 2005, 01:52 AM
Which is safer MUTE or ANts?
MUTE security has been cracked by GWREN not due to coding error but due to a design flaw.
It is very complicated so let me simplify:
MUTE uses a counter(UC) to ensure that all queries get a reasonable number of results.
Searches continue until a set number of results generated then the search stops.
It's the search stopping at a SET LEVEL (UC) that causes the problem.
MUTE stops search by sending search from ONE node to another node in CHAIN of random length.
In other words when stopping it does NOT send search to ALL neighbours, each node sends to ONE neighbour so forming a CHAIN.
A CHAIN is used rather than sending to all neighbours (FLOOD) because, "probabilistic limiting schemes do not work for branching message paths, they do work for non-branching paths (chains)"[Jason Rohrer].
In other words CANNOT use random number to stop a FLOOD search.
The random length of CHAIN stops a hacker TRICKING a node to stop search by telling it set number(UC) of results(false stop message) already reached.
The node instead continues after search set number of results(UC) reached by sending search along a node chain of random length.
So hacker cannot stop search and find searchers identity by sending false stop message. The search instead continues for a random few more hops along CHAIN.
The CRACK is the HACKER only needs to use ONE other ZOMBIE nodes after sending false stop search message to surround hacked node becasue it is in a CHAIN (chain only has two neighbours). Once surronded identity of hacked node is then easily found.
I did say it was complicated.
see:
http://mute-net.sourceforge.net/utilityCounters.shtml
http://antsp2p.sourceforge.net/muteCracked.pdf
http://sourceforge.net/mailarchive/message.php?msg_id=11194284
http://sourceforge.net/mailarchive/message.php?msg_id=11195245
MUTE developers response has so far been to say that they use random FLOOD to stop searches although as quoted above Jason Rohrer who wrote MUTE says this DOES NOT WORK!
I do not know if ANts has the same problem.
Gwren has not posted any documentation about how the current version of ANts works.
However, as far as I know ANts does not use stop messages in the form of TTL or UC to stop searches so ANts is SAFE.
Also, MUTE maybe safe IF IT DOES NOT WORK AS STATED ON ITS WEBSITE. In other words if its publish documentation is out of date and they have ceased using stop messages for searches.
Hornet :ass :ass :ass
MUTE security has been cracked by GWREN not due to coding error but due to a design flaw.
It is very complicated so let me simplify:
MUTE uses a counter(UC) to ensure that all queries get a reasonable number of results.
Searches continue until a set number of results generated then the search stops.
It's the search stopping at a SET LEVEL (UC) that causes the problem.
MUTE stops search by sending search from ONE node to another node in CHAIN of random length.
In other words when stopping it does NOT send search to ALL neighbours, each node sends to ONE neighbour so forming a CHAIN.
A CHAIN is used rather than sending to all neighbours (FLOOD) because, "probabilistic limiting schemes do not work for branching message paths, they do work for non-branching paths (chains)"[Jason Rohrer].
In other words CANNOT use random number to stop a FLOOD search.
The random length of CHAIN stops a hacker TRICKING a node to stop search by telling it set number(UC) of results(false stop message) already reached.
The node instead continues after search set number of results(UC) reached by sending search along a node chain of random length.
So hacker cannot stop search and find searchers identity by sending false stop message. The search instead continues for a random few more hops along CHAIN.
The CRACK is the HACKER only needs to use ONE other ZOMBIE nodes after sending false stop search message to surround hacked node becasue it is in a CHAIN (chain only has two neighbours). Once surronded identity of hacked node is then easily found.
I did say it was complicated.
see:
http://mute-net.sourceforge.net/utilityCounters.shtml
http://antsp2p.sourceforge.net/muteCracked.pdf
http://sourceforge.net/mailarchive/message.php?msg_id=11194284
http://sourceforge.net/mailarchive/message.php?msg_id=11195245
MUTE developers response has so far been to say that they use random FLOOD to stop searches although as quoted above Jason Rohrer who wrote MUTE says this DOES NOT WORK!
I do not know if ANts has the same problem.
Gwren has not posted any documentation about how the current version of ANts works.
However, as far as I know ANts does not use stop messages in the form of TTL or UC to stop searches so ANts is SAFE.
Also, MUTE maybe safe IF IT DOES NOT WORK AS STATED ON ITS WEBSITE. In other words if its publish documentation is out of date and they have ceased using stop messages for searches.
Hornet :ass :ass :ass