Serene wrote:
Q: Why is it called Snowflake?
There's a bunch of "ICE" negotiation happening for WebRTC, and it also
involves a great abundance of ephemeral and short-lived (and special!)
volunteer proxies...
Anyhow, if Snowflake seems like it would be useful / desired here, it
would be awesome
Orbot update with new built-in bridges (currently using the TBB default
list, randomly shuffled!) and some other small fixes for the user
interface, reproducible builds, and VPN feature.
- Original message -
From: Nathan of Guardian
To:
On Mon, Jan 25, 2016 at 02:34:42PM -0800, Serene wrote:
> Snowflake is a webrtc pluggable transport inspired by flashproxy.
> (https://gitweb.torproject.org/pluggable-transports/snowflake.git)
> Arlo, David, and I have made lots of progress on it lately, and it now
> appears to have reached
Hello all,
I just tagged obfs4proxy-0.0.6. There aren't many significant changes,
and the internal changes primarily affect the client side
initialization, so those of you that are perfectly content with
obfs4proxy-0.0.5 can continue to use the existing version without issue.
Tarball/Signature:
On Mon, Jan 25, 2016, at 09:38 AM, Yawning Angel wrote:
>benefit is that it is a lot easier to package than meek-client + the
>external helper, and this can probably save binary size on things
>like Android.
Yes, I've been waiting for this. It is especially useful since we will
be
> What are your plans for getting https://github.com/keroserene/go-webrtc
> to build completely in a deterministic manner?
Just opened an issue, so that's about as far as we are
in the planning stages.
https://github.com/keroserene/go-webrtc/issues/29
> The several hours isn't
> per platform
Hi all,
Snowflake is a webrtc pluggable transport inspired by flashproxy.
(https://gitweb.torproject.org/pluggable-transports/snowflake.git)
Arlo, David, and I have made lots of progress on it lately, and it now
appears to have reached minimum viability.
The following should result in a 100%
On Mon, Jan 25, 2016 at 2:53 PM, Yawning Angel wrote:
> What are your plans for getting https://github.com/keroserene/go-webrtc
> to build completely in a deterministic manner? The several hours isn't
> per platform right? (The "easy way" is not going to cut it for
>
On Mon, 25 Jan 2016 14:34:42 -0800
Serene wrote:
> Anyhow, if Snowflake seems like it would be useful / desired here, it
> would be awesome if we had more help getting it stable, polished,
> audited, deployable, etc...
Neat. Yes, this will be useful.
What are your plans
On Mon, 25 Jan 2016 15:32:55 -0800
Serene wrote:
[snip]
> > What are your plans for actually getting the server side to scale
> > well? Since you're using cgo you will run into Really Interesting
> > behavior wrt OS threads as you try to increase concurrency.
>
> Right
> On 26 Jan 2016, at 09:34, Serene wrote:
>
> Hi all,
>
> Snowflake is a webrtc pluggable transport inspired by flashproxy.
> (https://gitweb.torproject.org/pluggable-transports/snowflake.git)
> Arlo, David, and I have made lots of progress on it lately, and it now
>
> I get about this far on OS X, I'm behind a NAT:
>
> Jan 26 12:25:50.063 [notice] Tor v0.2.7.6 running on Darwin with Libevent
> 2.0.22-stable, OpenSSL 1.0.2e and Zlib 1.2.8.
> …
> Jan 26 12:25:50.071 [notice] Opening Socks listener on 127.0.0.1:9050
> Jan 26 12:25:50.000 [notice] Parsing
> On 26 Jan 2016, at 12:47, Arlo Breault wrote:
>
>
>> I get about this far on OS X, I'm behind a NAT:
>>
>> Jan 26 12:25:50.063 [notice] Tor v0.2.7.6 running on Darwin with Libevent
>> 2.0.22-stable, OpenSSL 1.0.2e and Zlib 1.2.8.
>> …
>> Jan 26 12:25:50.071 [notice]
On 18 Jan (07:13:36), Tim Wilson-Brown - teor wrote:
>
> > On 15 Jan 2016, at 03:31, David Goulet wrote:
> >
> >> Friday January 29: 8:30 am eastern (1330 UTC)
> >>
> >> Prop#252: Single Onion Services [DRAFT]
> >> Prop#260: Rendezvous Single Onion Services [DRAFT]
14 matches
Mail list logo