[GNUnet-developers] Resisting anti-P2P software systems

[Alexander Winston]

As some of you have may have read on CNET News.com a la Slashdot, the
Motion Picture Association of America has been testing its "Automated
Copyright Notice System" for several months now. The full story is
available at <http://news.com.com/2100-1027_3-5194341.html>. One college
has already set up a similar system and different college's system was
scheduled to go live yesterday.

The University of Florida's program is named ICARUS, which is an acronym
standing for "Integrated Computer Application for Recognizing User
Services." According to its FAQ at
<http://www.lists.ufl.edu/cgi-bin/wa?A2=ind03&L=icarus-updates-l&P=168>,
"ICARUS will likely be released under a GPL or BSD-style license" in the
spring of 2004. However, there has been no more news in this area, so I
am unsure whether we will be able to get a peek anytime soon. More
information about the system can be found at
<http://www.networkcomputing.com/showitem.jhtml?docid=1503f1>,
<http://www.networkcomputing.com/showitem.jhtml?docid=1503f2>, and
<http://www.wired.com/news/digiwood/0,1412,60613,00.html>.

Little information has been released regarding the system expected to
debut yesterday at the University of California, Los Angeles.

Because we lack detailed knowledge of these systems' innards, we can
only assume that they all function in the same basic manner as ICARUS.
This would mean that they have the ability to scan ports and monitor all
of the data that are transmitted back and forth from the computers.

I know that Christian Grothoff has suggested the use of port knocking;
this would possibly be an effective defense against the systems' port
scanning. I am curious to know how development of this is going, if at
all.

What do we have already or what can we write to project against complete
traffic sniffing?

signature.asc
Description: This is a digitally signed message part