Hi,
We'll be looking into the configurations soon. Thanks for the advice!
Today we handed in our project report on QUIC + TOR, which concluded our
semester-long project as well as our journey as undergrads here at CMU. I
just want to thank everyone who helped us during this time, since I've
asked
Sorry for the spam, but I have a critical typo on the previous message.
Instead of "with 11 nodes (2 relays) and 2 clients who have path
restriction." I meant 11 nodes (2 authorities) and 2 clients.
On Sun, May 8, 2016 at 1:52 AM, Xiaofan Li wrote:
> Tim,
>
> I'm not su
iguration issue? Or are you
saying it's a configuration issue with my underlying network topology?
The only thing different in the torrc files for the chutney run and the
Emulab run is "Sandbox 1" and "RunAsDaemon 1" but I don't think they cause
any issue?
Thanks
Thanks for the replies!
1. About the name:
Thanks for the headsup! We'll definitely pay attention to the trademark
rules when we publish our results. We are not planning to roll out our own
version of Tor. I think our most important goal is probably: demonstrate a
possibility of UDP-based protocol
Hi all,
We've finished building TOR on QUIC and everything works fine with chutney.
However, we have an issue with the node availability when we test on real
networks. We need this to work in order to evaluate the effect of HOL
blocking with QuicTor vs. Tor.
Specifically:
1. When using our Qui
>
> Tim:
Thank you for your understanding!
Our Tor baseline version is* Tor 0.2.8.0-alpha-dev* at commit hash:
42dea56363c24960e85344749644f6502f625463
(on Jan 26, 2016).
I also included a sample torrc file used by a relay. Hope it's useful.
>
I generally use a fresh directory with chutney every t
ject.org/pipermail/tor-commits/2013-March/053977.html>)?
*Why are these routers being excluded? *
Please let me know if you want more specific information on those issues.
Thank you!
Li.
On Sun, Apr 24, 2016 at 11:33 PM, Tim Wilson-Brown - teor <
teor2...@gmail.com> wrote:
>
> &g
Hi Tim and everyone on tor-dev,
Our QUIC + TOR project has almost been fully implemented. We are debugging
the last few bits of bugs. Update:
1. *We've now able to build many complete circuits with QUIC as its
underlying protocol. *
2. We have not debugged the actual communication part y
ere.
> All of these questions could benefit from the wider Tor developer
> community.
> When I know I can't fully answer a question, I'll say so below.
>
> Please feel free to forward my response to tor-dev.
>
> > On 5 Apr 2016, at 05:38, Xiaofan Li wrote:
> >
> >
k, such as encrypting twice unnecessarily (once
for QUIC's TLS and once for TOR). So, we are exploring the possibility of
turning off this feature in QUIC. What do you think of this problem? Are we
on the right track?
Thank you!
Li.
On Tue, Feb 16, 2016 at 8:29 PM, Tim Wilson-Brown - teor
Hi everyone:
I'm new to Tor dev community and my name is Xiaofan Li, currently a senior
at Carnegie Mellon University studying ECE and CS. My friend Kevin Ku and I
are taking a graduate class <http://www.cs.cmu.edu/%7Esrini/15-744/S16/> on
computer networks and we decided to
11 matches
Mail list logo
