[tor-dev] Next OONI weekly meetings

2014-11-19 Thread Arturo Filastò
Hello Oonitarians, Sorry for not sending this email sooner, but this week has been a bit hectic. A couple of people have said that they cannot attend the weekly meeting on thursday at 18:00, because it conflicts with another recurring appointment they have. For this reason I am going to suggest

Re: [tor-dev] Next OONI weekly meetings

2014-11-19 Thread Aaron Gibson
On 2014-11-19 11:20, Arturo Filastò wrote: Hello Oonitarians, Sorry for not sending this email sooner, but this week has been a bit hectic. A couple of people have said that they cannot attend the weekly meeting on thursday at 18:00, because it conflicts with another recurring appointment they

Re: [tor-dev] Of CA-signed certs and .onion URIs

2014-11-19 Thread grarpamp
On Wed, Nov 19, 2014 at 1:05 AM, Tom Ritter t...@ritter.vg wrote: At that point, they can tell me whatever they want Some of them will ;) So I'm not sure I understand the attacks you're talking about. this .onion SSL bypass stuff into little-t tor, I'm talking about making it a Tor Browser

Re: [tor-dev] Stormy - request for feedback

2014-11-19 Thread Patrick Schleizer
Hi! I think it's non-ideal to modify config files using cat/sed/echo. That breaks sooner or later. And if later settings are supposed to be changed in the same file, things get messy. Some suggestions... It would be better to put the config files into (debian) packages. Want to disable popcon?

Re: [tor-dev] Of CA-signed certs and .onion URIs

2014-11-19 Thread Matthew Finkel
On Tue, Nov 18, 2014 at 10:53:30PM -0500, grarpamp wrote: On Tue, Nov 18, 2014 at 12:55 PM, George Kadianakis desnac...@riseup.net wrote: plans for any Tor modifications we want to do (for example, trusting self-signed certs signed by the HS identity key seem like a generally good idea).

Re: [tor-dev] Stormy - request for feedback

2014-11-19 Thread Fabio Pietrosanti - lists
On 11/17/14 10:33 AM, Griffin Boyce wrote: Q: Can I use this right now to set up a hidden service? A: Please don't use this in production until firewall settings are in place. I would suggest to add a Tor2web policy that, looking at X-Tor2web: HTTP header, enable or disable access to the Blog