On Tue, Mar 15, 2016 at 9:12 PM, Isabela wrote:
> Hi there,
>
> Quick reminder that tomorrow we will have prop 224 discussion:
>
> Proposal 224: Next-Generation Hidden Services in Tor
>
> Wednesday, March 16th 1500 UTC
> Must-have attendees: special, dgoulet, asn, teor
> Conflicts: (If you are not
Hi there,
Quick reminder that tomorrow we will have prop 224 discussion:
Proposal 224: Next-Generation Hidden Services in Tor
* Wednesday, March 16th 1500 UTC
* Must-have attendees: special, dgoulet, asn, teor
* Conflicts: (If you are noting a conflict, please include a big bunch
of ti
Hi Patrick -- yes, they're just WebRTC peers, which automatically and
easily traverse NATs in most cases. "Hosting a bridge" for snowflake
can be accomplished by leaving a tab open in your browser (or later
on, running an extension)
Cheers,
~serene
On Tue, Mar 15, 2016 at 2:25 PM, Patrick Schleiz
Cool!
Does the server (hosting a bridge) work also out of the box behind NAT?
Cheers,
Patrick
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Hi Martin,
> I try to configure OpenWRT in a way that it will only allow outgoing
> connections if it is Tor. Basically it is the opposite of "blacklisting
> exit relays on servers": "whitelisting (guard) relays for clients". It
> should *not* run Tor itself.
Maybe corridor would work for you: ht
Martin Kepplinger:
> I try to configure OpenWRT in a way that it will only allow outgoing
> connections if it is Tor. Basically it is the opposite of "blacklisting
> exit relays on servers": "whitelisting (guard) relays for clients". It
> should *not* run Tor itself.
I actually implemented this wh
Am 2016-03-15 um 18:10 schrieb Tom Ritter:
> On 15 March 2016 at 10:52, Martin Kepplinger wrote:
>> Hi,
>>
>> I try to configure OpenWRT in a way that it will only allow outgoing
>> connections if it is Tor. Basically it is the opposite of "blacklisting
>> exit relays on servers": "whitelisting (g
Am 2016-03-15 um 16:52 schrieb Martin Kepplinger:
> Hi,
>
> I try to configure OpenWRT in a way that it will only allow outgoing
> connections if it is Tor. Basically it is the opposite of "blacklisting
> exit relays on servers": "whitelisting (guard) relays for clients". It
> should *not* run Tor
On 15 March 2016 at 10:52, Martin Kepplinger wrote:
> Hi,
>
> I try to configure OpenWRT in a way that it will only allow outgoing
> connections if it is Tor. Basically it is the opposite of "blacklisting
> exit relays on servers": "whitelisting (guard) relays for clients". It
> should *not* run T
Hello,
I took a look at proposal 224 again, with the aim of revisiting the cell logic
and format.
Here are some matters that require discussion:
1) Should we keep backwards compability with old introduction and rendezvous
points?
Currently, proposal 224 actually tries to maintain backwards
Hi,
I try to configure OpenWRT in a way that it will only allow outgoing
connections if it is Tor. Basically it is the opposite of "blacklisting
exit relays on servers": "whitelisting (guard) relays for clients". It
should *not* run Tor itself.
A first test setup (onionoo document, ipset and ipta
Dear Marcela, Arlo
> You’re very welcome, we look forward to your application!
I have submitted my draft proposal via GSoC website. I am looking forward to
your feedback.
Thank you so much!
best,
Vu Quoc Huy
___
tor-dev mailing list
tor-dev@li
Hi Tor Community,
My name is Pierre and I'm really interested in participating in a GSoC
project this year with the Tor organization. Since I've been working on
browser fingerprinting for the past two years, I'd love to build a
Panopticlick-like website to improve the fingerprinting defenses of th
Akito Ono:
> Hi,
>
> Thanks for quick answer.
>
>> For the tests themselves there will probably mainly JavaScript used + some
> CSS/HTML.
>
> So if I understand correctly, students have a choice about sever-side
> language?
> I have developed Web application, so I'm concerned about whether I can
14 matches
Mail list logo
