[tor-talk] Blocked HTTPS

Veggie Monster vmonmoonshine at gmail.com
Sun May 6 11:54:23 UTC 2012


> and there is also a proposal with the changes to be
> made [1]. Unfortunately, the implementation of the proposal
> hasn't started yet.

Why doesn't the proposal suggest doing it in "seemingly" natural way,
i.e., to add the possibility to specify proxy for the transport. Why
does tor need to be aware of this extra proxy at all? isn't this the
way that all other application works? e.g.:

Firefox->privoxy->tor->socks->...

so let have
Tor->transport->http-proxy->...

I'm sure Nick has thought about it, but I just want to know the reason.

vmon


More information about the tor-talk mailing list