On Sun, May 05, 2013 at 10:44:01PM +0300, Kostas Jakeliunas wrote:
> Also, 'Format-Transforming Encryption' looks
> interesting, but I take it not much in terms of implementation beyond a
> research paper [2] (which looks interesting).
>
> [2]https://eprint.iacr.org/2012/494
I haven't tried it ye
(Sorry, last email for now --) I see that "StegoTorus is an Obfsproxy fork
that extends it to a) split Tor streams across multiple connections to
avoid packet size signatures, and b) embed the traffic flows in traces that
look like html, javascript, or pdf." However, its public repo seems to
haven'
> If we had a PT that encapsulated obfs3 inside
the body of http then this may work.
I'm probably missing some previous discussions which might have covered it,
but: have there been any attempts to produce a pluggable transport which
would emulate http? Basically, have the transport use http heade
> have there been any attempts to produce a pluggable transport which would
emulate http?
(Ah, I suppose there've been quite a bit of discussion indeed. (
https://trac.torproject.org/projects/tor/ticket/8676, etc.))
On Sun, May 5, 2013 at 9:58 PM, Kostas Jakeliunas wrote:
> > If we had a PT that
On Sun, May 05, 2013 at 04:18:56PM +0300, George Kadianakis wrote:
> tor-admin writes:
>
> > On Sunday 05 May 2013 14:50:51 George Kadianakis wrote:
> >> It would be interesting to learn which ports they currently whitelist,
> >> except from the usual HTTP/HTTPS.
> >>
> >> I also wonder if they
tor-admin writes:
> On Sunday 05 May 2013 14:50:51 George Kadianakis wrote:
>> It would be interesting to learn which ports they currently whitelist,
>> except from the usual HTTP/HTTPS.
>>
>> I also wonder if they just block based on TCP port, or whether they
>> also have DPI heuristics.
>>
>>
On Sunday 05 May 2013 14:50:51 George Kadianakis wrote:
> It would be interesting to learn which ports they currently whitelist,
> except from the usual HTTP/HTTPS.
>
> I also wonder if they just block based on TCP port, or whether they
> also have DPI heuristics.
>
> On the Tor side, it seems li
Nima writes:
> George Kadianakis:
>> Nima writes:
>>
>>> Iran is actively dropping connections to *any* unknown port right after
>>> *60secs*.
>>> Pluggable Transport successfully connects to Tor network, Although it
>>> can not make a circuit in many ISPs including "Mobin".
>>
>> Ugh. This su
George Kadianakis:
> Nima writes:
>
>> Iran is actively dropping connections to *any* unknown port right after
>> *60secs*.
>> Pluggable Transport successfully connects to Tor network, Although it
>> can not make a circuit in many ISPs including "Mobin".
>
> Ugh. This sucks.
>
> What do you mea
Nima writes:
> Iran is actively dropping connections to *any* unknown port right after
> *60secs*.
> Pluggable Transport successfully connects to Tor network, Although it
> can not make a circuit in many ISPs including "Mobin".
Ugh. This sucks.
What do you mean by "unknown port"? Which ports do
Iran is actively dropping connections to *any* unknown port right after
*60secs*.
Pluggable Transport successfully connects to Tor network, Although it
can not make a circuit in many ISPs including "Mobin".
--
Nima
0x1C92A77B
"I disapprove of what you say, but I will defend to the death your rig
11 matches
Mail list logo