-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry everyone for the long pause.
I wrote down a proposal (and some code) to address issues raised by
Mike and George:
https://securehomes.esat.kuleuven.be/~gacar/summer_2014.pdf
Looking for your comments and critics...
On 03/21/2014 11:39 PM, Pete
On 19/04/14 00:07, Michael Wolf wrote:
> I think I can make some improvements to the consensus-health page
> (mostly removing redundant formatting code in the HTML), but I can't
> seem to find the git repo for the project listed at
> https://gitweb.torproject.org/
>
> Could someone point me in the
I think I can make some improvements to the consensus-health page
(mostly removing redundant formatting code in the HTML), but I can't
seem to find the git repo for the project listed at
https://gitweb.torproject.org/
Could someone point me in the right direction?
I another pertinent question wou
There are a lot of components that make up the meek transport. There is
the client and server, and then there is the middle part that runs on
App Engine, and the browser extension that ensures we are speaking HTTPS
the right way. I'm working towards deploying the transport, and to that
end I'd like
A while back I wrote about a pluggable transport called meek that routes
your traffic through a third-party web service in a way that should be
difficult to block. There are now experimental bundles featuring this
transport, ready for somewhat wider testing. Please try:
https://people.torproject.o
On Fri, Apr 18, 2014 at 2:29 PM, Sebastian Hahn wrote:
>
> On 18 Apr 2014, at 19:52, Nick Mathewson wrote:
>> Imo we _should_ check through the code for things related to the Named
>> flag, though, back through 0.2.3 or maybe 0.2.2. Reasons:
>>
>> * Private networks never worked very well with
On 18 Apr 2014, at 19:52, Nick Mathewson wrote:
> Imo we _should_ check through the code for things related to the Named
> flag, though, back through 0.2.3 or maybe 0.2.2. Reasons:
>
> * Private networks never worked very well with older tors.
> * Maybe there's some piece of obscure functiona
On Thu, Apr 10, 2014 at 3:45 AM, Sebastian Hahn wrote:
> 2. Design
>
>None. Tor clients already support consensuses without Named flags,
>and testing in private Tor networks has never revealed any issues in
>this regard.
Imo we _should_ check through the code for things related to th
On 18 Apr 2014, at 15:02, Karsten Loesing wrote:
> If I understand the proposal correctly, operators will still be able to
> name their relay or bridge, and people can still find it in Atlas or
> Globe by this nickname. If so, great!
Yes, this is in no way related to the nickname field.
>> T
Hey all,
Got a report from a friend* who noticed that twitch.tv stops letting
him watch broadcasts while flashproxy is in an active state. He uses
Cupcake, which shows flashproxy's status in the icon bar, and he only
has an issue when the cupcake icon has a mustache.
Has anyone noticed
On 10/04/14 09:45, Sebastian Hahn wrote:
> Filename: xxx-kill-named-flag.txt
>
> Title: Stop assigning (and eventually supporting) the Named flag
> Authors: Sebastian Hahnn
> Created: 10 April 2014
> Target: 0.2.5
> Status: Draft
>
11 matches
Mail list logo
