On Sunday 02 November 2014 00:47:40 coderman wrote:
> even a simple one time, "You are about to route your traffic over the
> Tor network. Turn off your torrents and don't upgrade poorly written
> applications".
>
> the zero guidance to unsuspecting is what i am most concerned about;
> even basic
On Mon, Nov 3, 2014 at 3:05 PM, Mike Perry wrote:
> Cyrus Katrak:
> > https://github.com/kr36/seaturtle
> >
> > At a high level:
> > - Process per tab security model, with each tab owning it's own in-memory
> > state (cache, cookies, local storage, hsts db etc...).
>
> We've been going for URL ba
No, currently I am not using any Isolation flags. I assume this means all
tabs are sharing the same stream. I could trivially use something like
IsolateDestAddr, but I assume what you are suggesting is to have one Tor
SOCKS port per tab?
On Mon, Nov 3, 2014 at 11:12 AM, coderman wrote:
> On 11/3
Thanks, I've been looking for something like this.
On Mon, Nov 3, 2014 at 5:07 PM, Tom Ritter wrote:
> On 3 November 2014 17:05, Mike Perry wrote:
> > I also have an OpenWRT configuration I can give you to monitor for proxy
> > leaks on an upstream router, but you need to be able to configure T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/03/2014 04:06 PM, l.m wrote:
>
> So I can laugh at you when your buyers realize how
> stupid they were for not reading the Tor manual.
>
> [snip]
>
> Who the hell
> wants anonymity and actually trusts their networking equipment?
>
*** Every
On Tuesday 04 November 2014 07:26:09 mic...@michaelblizek.twilightparadox.com
wrote:
> This would require IsolateDestAddr. This might have a serious impact on
> performance and load (I cannot tell you how much).
I have now enabled IsolateDestAddr and I think that will remain enabled. It's
too i
