C'mon, I doubt these guys are that sophisticated. They're not going to buy specialized hardware to scan for this stuff, nor develop anything to fancy when their biggest concern are the Kazaa customers who leave their machines online all day, uploading gigabytes of data.
I'll guess port # range,probably mixed in with some bandwidth use thresholds before throttling. On 9/19/07 5:04 PM, "Michael Rogers" <[EMAIL PROTECTED]> wrote: > Charles Iliya Krempeaux wrote: >> Maybe people should be hiding things out in the open. Like, make it >> look like normal (unencrypted) HTTP, SMTP, or POP3 traffic (or something >> pretty common like those)... and hide the data in the data stream. > > It would be interesting to know how they're detecting encrypted traffic > - measuring redundancy, as in the recent Skype paper, or just throttling > anything that's not a recognised plaintext protocol? If the former, how > much redundancy do you have to add to get round the filter? If the > latter, can you just tack "GET / HTTP/1.0" to the beginning of every > connection? > > Cheers, > Michael > _______________________________________________ > p2p-hackers mailing list > [email protected] > http://lists.zooko.com/mailman/listinfo/p2p-hackers > -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech [EMAIL PROTECTED] _______________________________________________ p2p-hackers mailing list [email protected] http://lists.zooko.com/mailman/listinfo/p2p-hackers
