The Differences Between Onion Routing and Mix Networks
https://ritter.vg/blog-mix_and_onion_networks.html
On Wed, Jan 20, 2016 at 5:42 AM, Virgil Griffith wrote:
> I understand that the original Tor model is to set low-latency and
> low-jitter as a constraint as to permit things like interactiv
On Wed, 20 Jan 2016 08:15:48 +
David Stainton wrote:
> The Differences Between Onion Routing and Mix Networks
> https://ritter.vg/blog-mix_and_onion_networks.html
Not implemented yet in tor (see prop 254), but this is the current state
of the art in link padding as a traffic analysis defense.
Hi,
>
> grarpamp:
> Higher latency, in and of itself, does not
> provide any resistance to traffic
> analysis.
>
Increase one-way and it will become unusable; nothing to see here.
Wordlife,
Spencer
___
tor-dev mailing list
tor-dev@lists.torprojec
Hi,
>
> Yawning Angel:
> the art [of] link padding
>
I remember this:
eecs.harvard.edu/~htk/publication/2005-jit-cheng-kung-tan.pdf
Wordlife,
Spencer
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman
Hi,
Yawning Angel:
You can with the control port. Moving it to a first class feature
would be a terrible idea for anyone that isn't a researcher
Says a researcher (:
Wordlife,
Spencer
___
tor-dev mailing list
tor-dev@lists.torproject.org
https
Hi,
Lunar:
Proposals are all kept in the “torspec” Git repository [and] in Nick
Thanks for taking the time to share this!!
Wordlife,
Spencer
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/list
While discussing proposal 247 with George yesterday, we realized that we
still get security benefit from additional ephemeral hops beyond the
vanguards themselves.
Recall the high-level 247 path design is:
C - L - M - S -- S - M - L - H
Where:
C = Client
L = Long lived Layer1 guard
M = M
Mike Perry writes:
> While discussing proposal 247 with George yesterday, we realized that we
> still get security benefit from additional ephemeral hops beyond the
> vanguards themselves.
>
> Recall the high-level 247 path design is:
>
> C - L - M - S -- S - M - L - H
>
> Where:
> C = Client
George Kadianakis:
> Mike Perry writes:
>
> > While discussing proposal 247 with George yesterday, we realized that we
> > still get security benefit from additional ephemeral hops beyond the
> > vanguards themselves.
> >
> > Recall the high-level 247 path design is:
> >
> > C - L - M - S -- S