Question about 2 warn messages

Tue Feb 27 06:37:23 UTC 2007

On Wed, Feb 14, 2007 at 02:29:25PM +0100, webwill33 at web.de wrote:
> I found these two warn messages in my router log. Is it something i should be worried about?
> 
> [warn] tor_gzip_uncompress(): Gzip decompression returned an error: incorrect data check
> 
> [warn] connection_dir_client_reached_eof(): Received http status code 403 ("Forbidden") from server '8.7.49.192:80' while fetching "/tor/server/d/83CC8C7D61175920964FBDB6515487545BACBFDC+DDADE5501F74B0C96A34181605EDCF48175EE76A+056DC7137558DED0285428B916D25789916BEAC8+5BA3A08EF28E895ECAE3239416AE8057E74509DF+B04F20279621FF2AC70EBDE2A7FBC9D3EA11D9FF+872E65EFD99F18F85BD565A231349E64AAAEC6EB+766606E134D139BA34ADE97037098DECB418AC70+588F785F8E811DB3318CF3F62052F78B59795F5F+8CCAE7A822114D0175E25926484EAB637A1540D5+EEAD5D7D16C7C8C5B4E2D9FDAEF5CD4F471F5B85+FA0DC02D08E6925346BBA464BC55F933862506C9+5CAC59A09099CDCB790C9788C509C859932B10F6+F2C12554F48C325E59BE9F7922F28963D2897741+456FD0105074C73052650AB70C67416C047BE838+8246C3C0B000FF5685F034837D18D29779FF2FEA+A94404181BFC8777031CA55D90DC4F9FD21D4F55+0EDA652B35ECF33C03813F5682CA3EDC1BCB73EA+E04F1BAEEA83C7D1BF49BB7350E7AD265AE5631F+A309DC7612DB0E8917946F68336B057FCD591502+A25F06C0E3E6C08A4DB5309AAE6BDBBE6CEBBC2B+89BC553D60A98F1DDDE82758E64DF3087033AB84+EF0CA1DC68AB27337C1BDD3316475343EF7941FA+0A6F2723DF66590E3B50E73BDB011D99F5C71E9A+19FAEA3510E6696E591D6307C5265E6C511012AD+CD451FE13C053BBE1D4E7032C8611071B62955AF+B3F670FF8C864EB8DCD17806050AED9ADC36FB89+1B0709B2B9E1F77FCFBC61A169EC8B43C6F37F1B+F91642EB81EFFA32C8DF843D659CE7E40ADB6F01+6F8020926BE8DBEB8D7AA8DA347F6C88B7912676.z". I'll try again soon.

These are fine, as long as Tor is working for you. They happen because
somebody is advertising an open DirPort somewhere, but actually they're
running some other software at that address and port. In this case it's
probably some sort of web cache or web server. Eventually I'd like to
stop mentioning these to users (there's not much they can do, after all),
but at the same time if *all* your directory requests are showing these
errors, then it's a good hint that maybe your local http connections
are being intercepted and blocked. For example, this happens on hotel
or airport wireless networks.

I'll add a todo item to try to be smarter about when we can be quiet
and when we should tell the user -- for example, if Tor has already
bootstrapped and we hit just one bad dirport, it's not worth mentioning.

Thanks,
--Roger