Media campaign against connection data storage

[Enigma]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
 
Hi all,

The /Arbeitskreis Vorratsdatenspeicherung/ (German association against
the connection data storage directive) is setting up a campaign
against the connection data storage by calling for a web demonstration
as well as contacting the mass media to report about this EU
directive. Again it's only for German citizens and German webmasters
but since members of this mailing list said it's interesting to read
about these developments nevertheless I thought I'd notify everyone
about this campaign.
The English article can be found here:
http://www.anti1984.com/en/articles/9.html
The German article is located at:
http://www.anti1984.com/de/artikel/14.html

Speaking of German webmasters, I really wonder if not every European
webmaster should be able to participate in that and have a javascript
showing the same thing in English language? After all, all European
webmasters and citizens will be affected.
What do you think?
(I know this mailing list is mainly about Tor, so if a discussion
about this is not welcomed here let us know and we can start one in
anti1984's forum
at www.anti1984.com/forum )

Sincerely,
Enigma

- --
German Tor mailing list / surveillance and anonymity:
http://www.anti1984.com

GPG key ID: 4096R/602492EA
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iQIVAwUBRX7sr6wicbNgJJLqAQI9Hg/+PlDTdRNsgbylP7iTJLX7QrBnLhBeXP16
h6B8bQy9q8ajmamui6abRstCOGI2RKB1tchbnqjECjbOhKyc93C1yH1iag1vLn0a
GiY1cUf3gqs65hT882ciUgqNLDmxxPD41Y5WkZRhiT8rzJOtuUJ5Ln7PZdJX5J3/
4bZl6bcGQNN21JxRS6AqqP11MZ/uAYRC5tmb1PYSq5HmWXIz44/T6OgKgnsV1BDS
SX6f2MHHTGWH4Cjs4f8M4oBXyaG679gqBJumjC7RfeA5KfHuiDaFCS7v8GyOTPej
NamwpLMmdj0+JdfmCw+WDgjoPebxXwPYvwvNsSuU9PSkh68hYdyI0XWf49yhdQ8V
DnzvEou5zPRleIHh9UQidyePPmYTJcz7RqcZMGQqdDIkT3UbWdjSuvkwuXNashwn
XlVXeDtJpxHZF+lCJijUprhifoPrnQg7xeeZxw8wCWDUgZxVLIyZujhQbjnSXdgM
sQyKQXJBPc4ttgHbE57As3r3VaWaz6RzP99qQjGVX2Kk5GoKqLLXIR/U64pwbnoc
n0T6YrBWuMJw/fJvOKYVPVd8X0rJexqA6lxE3ZpJjMr4Q9v46Mm2JgQsqh8S0bj/
Mr551gCFZEjZJPGOJzd2JOqxYmQO3E6fTzp3IdETf2S1D3qQz0eDOcVDEULdqpW0
5kxZI+0PPOM=
=egag
-END PGP SIGNATURE-

Re: Tor 0.1.2.2-alpha eventdns timeouts

[Fabian Keil]

Nick Mathewson [EMAIL PROTECTED] wrote:

 On Thu, Oct 26, 2006 at 06:49:57PM +0200, Fabian Keil wrote:
  [...]
  As a result I see indeed a lot less timeout warnings,
  and the servers are declared active right away, but it
  also looks as if the number of timeouts isn't reset
  correctly:
 
 My apologies for the delay here.  Your diagnosis turned out to be
 completely correct.  I was looking for far more tricky problems, when
 the root cause turned out to be (I think) that eventdns.c never
 actually reset the timeout count.  Oops! I've checked a patch in to
 subversion as r9054; if you have a chance to see whether it fixes the
 problem for you, I'd be most grateful.

I patched Tor 0.1.2.4-alpha about half an hour ago,
so I can't be sure yet, but it looks as if the patch
causes less timeout warnings, but more Bad response 2
messages.

This is a log excerpt from vanilla Tor 0.1.2.4-alpha:

Dec 12 18:55:11.676 [warn] eventdns: Nameserver 81.169.148.34 has failed: 
request timed out.
Dec 12 17:46:01.083 [warn] eventdns: Nameserver 81.169.148.34 is back up
Dec 12 17:53:45.157 [warn] eventdns: Nameserver 81.169.148.34 has failed: 
request timed out.
Dec 12 17:53:55.158 [warn] eventdns: Nameserver 81.169.148.34 is back up
Dec 12 18:02:27.201 [warn] eventdns: Nameserver 81.169.148.34 has failed: 
request timed out.
Dec 12 18:02:37.242 [warn] eventdns: Nameserver 81.169.148.34 is back up
Dec 12 18:12:59.581 [warn] eventdns: Nameserver 81.169.148.34 has failed: 
request timed out.
Dec 12 18:13:09.582 [warn] eventdns: Nameserver 81.169.148.34 is back up
Dec 12 18:13:19.784 [warn] eventdns: Nameserver 81.169.148.34 has failed: 
request timed out.
Dec 12 18:13:29.785 [warn] eventdns: Nameserver 81.169.148.34 is back up
Dec 12 18:33:15.708 [warn] eventdns: Nameserver 81.169.148.34 has failed: 
request timed out.
Dec 12 18:33:16.746 [warn] eventdns: Nameserver 81.169.148.34 is back up
Dec 12 18:43:00.952 [warn] eventdns: Nameserver 81.169.148.34 has failed: 
request timed out.
Dec 12 18:43:02.706 [warn] eventdns: Nameserver 81.169.148.34 is back up

This is with your patch applied:

Dec 12 18:47:11.260 [notice] Self-testing indicates your DirPort is reachable 
from the outside. Excellent.
Dec 12 18:48:09.113 [notice] Performing bandwidth self-test.
Dec 12 18:55:11.676 [warn] eventdns: Nameserver 81.169.148.34 has failed: 
request timed out.
Dec 12 18:55:21.677 [warn] eventdns: Nameserver 81.169.148.34 is back up
Dec 12 18:55:37.977 [warn] eventdns: Nameserver 81.169.148.34 has failed: Bad 
response 2 (server failed)
Dec 12 18:55:47.978 [warn] eventdns: Nameserver 81.169.148.34 is back up
Dec 12 18:59:26.843 [warn] eventdns: Nameserver 81.169.148.164 has failed: Bad 
response 2 (server failed)
Dec 12 18:59:34.863 [warn] eventdns: Nameserver 81.169.148.34 has failed: Bad 
response 2 (server failed)
Dec 12 18:59:34.864 [warn] eventdns: All nameservers have failed
Dec 12 18:59:36.843 [warn] eventdns: Nameserver 81.169.148.164 is back up
Dec 12 18:59:44.864 [warn] eventdns: Nameserver 81.169.148.34 is back up

I already did get some Bad response 2 before,
so this could be a coincidence.

As I said, it's not running long enough to be sure,
but it at least looks as if there's still some problem left.

Fabian
-- 
http://www.fabiankeil.de/


signature.asc
Description: PGP signature