-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 GDR!:
On 07.10.2013 21:11, dardok wrote:
I guess that you misunderstood the concept of obfsproxy. It is useful to obfuscate the communication between a client within a censorship zone and a tor bridge. The obfsproxy doesn't emulate a HTTP protocol communication, instead it is designed to look random (and the packets are encypted). So if you try to run this service over the HTTP port 80 and the packets are random and not looking like a HTTP communication, it will be more suspicious than running this service over any other port.
Thank you. I understood the concept but not the implementation.
"For example, there MIGHT be a HTTP transport which transforms Tor traffic to look like regular HTTP traffic."
I missed the "MIGHT" part. Too bad this doesn't exist.
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
There is a pluggable transport protocol that aims to mimic a cover protocol such HTTP. Its name is Stegotorus but I believe that still is not full developed. If you want more info you can read this: - - http://www.owlfolio.org/media/2010/05/stegotorus.pdf - - https://gitweb.torproject.org/stegotorus.git -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJSUx7rAAoJEFz9RJtDk2+MW2cH/2OVQ9XtY02cZO+wZEtYF31k 0pGL2poRRfTjQGBbR3KxVIoJvffAx8sixMR6nZ/Zfqu0wr4OvhofIVfXQgVwqevS XcI5aJEgQV13u8frdER3PG3/IrDtYcPpTR0irVoAZJKwKKp+7TTe7/kcU9WB+hGD rH8bklY+pr0uWJjvymb7zG5iZ1fnutU7Da1Nc9679n4YA7Go/B5N3hdLCV6/WwQn i3vQavXMOjdSwN+kWlwbPhb9EhXmxyQonIJBgsi3PjADfvV36h9MsxixDo5ZSq/f Sz8TdaNfx5ye+4zwQQZR32W+W6HfNqN2/Fyiuqw+Ggw54OUMhbOfPDE8R4de9+E= =1mgs -----END PGP SIGNATURE-----