> Date: Mon, 4 May 2015 16:07:20 -0400
> From: CJ Ess
>
> Thanks for going into so much detail, you've given me a lot to think about.
> The real solution is probably the one that nobody wants to take on - having
> an application HTTP port that could take direct input from HTTP aware stuff
> and
Thanks for going into so much detail, you've given me a lot to think about.
The real solution is probably the one that nobody wants to take on - having
an application HTTP port that could take direct input from HTTP aware stuff
and utilize a richer set of information then SOCKS allows for. I've spe
> Date: Sun, 3 May 2015 12:34:51 -0400
> From: CJ Ess
>
> On Sun, May 3, 2015 at 11:06 AM, teor wrote:
>
>>> Date: Sun, 3 May 2015 02:50:46 -0400
>>> From: CJ Ess
>>>
>>> So I'm doing a bit of an experiment, the idea being that if you have a
>>> group of tor users sharing common infrastructu
So underlying idea in this case is to pass thru the proxy credentials from
the browser, so they don't have to be had coded in plain text in the tor
config - you exit the browser and the credential goes away (or maybe its
encrypted in the browser password manager), if you change your password you
do
> Date: Sun, 3 May 2015 02:50:46 -0400
> From: CJ Ess
>
> So I'm doing a bit of an experiment, the idea being that if you have a
> group of tor users sharing common infrastructure then its a slightly
> different situation then one lone user, and you wantto emphasize that
> resources should not b
So I'm doing a bit of an experiment, the idea being that if you have a
group of tor users sharing common infrastructure then its a slightly
different situation then one lone user, and you wantto emphasize that
resources should not be shared, caching should be minimal and
non-persistent, you need to
