On Sun, Nov 25, 2012 at 07:54:51PM -0500, Nick Mathewson wrote:
> [tl;dr: We should make client-side DNS cacheing off by default.]
Be careful -- we seem to rely on the client-side dns cache to let us
move on to a new circuit if the current circuit's exit policy doesn't
like the stream.
See in con
On Mon, 26 Nov 2012 at 17:40, leez wrote:
> The lost document was actually this one:
> https://www.eff.org/document/dc-circuit-opinion-granting-verizons-motion-quash
>
> I've added a redirect from the broken link, so either will get you
> there now.
Thanks for fixing this!
Christian.
--
BOFH ex
This works just like OutboundBindAddress, but instead of excluding
connections to loopback addresses, it affects only connections to
loopback addresses.
The whitespace in this commit is a bit nutty, in order to put whitespace
changes into a separate commit.
---
doc/tor.1.txt | 11
---
src/or/config.c | 88 +--
src/or/connection.c | 60 +--
2 files changed, 73 insertions(+), 75 deletions(-)
diff --git a/src/or/config.c b/src/or/config.c
index 03e07f9..12f4f79 100644
--- a/src/or/config.c
On Mon, 26 Nov 2012 12:05:59 -0800 (PST)
Christian Kujau wrote:
> the Tor DMCA response[0] has a link inside for the RIAA v. Verizon
> case:
>
>https://www.eff.org/legal/cases/RIAA_v_Verizon/opinion-20031219.pdf
>
> But this document is no longer available at this address, thus
> producing a
Hi,
the Tor DMCA response[0] has a link inside for the RIAA v. Verizon case:
https://www.eff.org/legal/cases/RIAA_v_Verizon/opinion-20031219.pdf
But this document is no longer available at this address, thus producing a
404. @EFF Webmaster, could you please fix this or provide the new addres
