On 12 Jan 2014, at 02:57, nano wrote:

I haven't looked into this at all yet, thought I would share it here first. Both my exit relays [0] received these repeated warnings around the same time yesterday:

timestamp [warn] Received http status code 404 ("Not found") from server 'server1IP:port' while fetching "/tor/keys/fp-sk/A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0-A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0". timestamp [warn] Received http status code 404 ("Not found") from server 'server2IP:port' while fetching "/tor/keys/fp-sk/A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0-A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0". timestamp [warn] Received http status code 404 ("Not found") from server 'server3IP:port' while fetching "/tor/keys/fp-sk/A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0-A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0". timestamp [warn] Received http status code 404 ("Not found") from server 'server4IP:port' while fetching "/tor/keys/fp-sk/A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0-A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0".

Same here multiple times, started yesterday Jan-11 on 17:08 GMT

Jan 12 11:06:42 GMT Tor[36615]: Received http status code 404 ("Not found") from server 'xxxxxxx:443' while fetching "/tor/keys/fp-sk/E8A9C45EDE6D711294FADF8E7951F4DE6CA56B58-9732F95C0620648332899FD91C6463F827983B17". Jan 12 11:06:42 GMT Tor[36615]: Received http status code 404 ("Not found") from server 'xxxxxxx:80' while fetching "/tor/keys/fp-sk/E8A9C45EDE6D711294FADF8E7951F4DE6CA56B58-9732F95C0620648332899FD91C6463F827983B17".

Thanks,

-mateusz

nano nanotek@bsdbox.co wrote Sun, 12 Jan 2014 13:57:20 +1100:

| I haven't looked into this at all yet, thought I would share it here | first. Both my exit relays [0] received these repeated warnings around | the same time yesterday: | | timestamp [warn] Received http status code 404 ("Not found") from | server 'server1IP:port' while fetching | "/tor/keys/fp-sk/A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0-A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0". | timestamp [warn] Received http status code 404 ("Not found") from | server 'server2IP:port' while fetching | "/tor/keys/fp-sk/A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0-A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0". | timestamp [warn] Received http status code 404 ("Not found") from | server 'server3IP:port' while fetching | "/tor/keys/fp-sk/A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0-A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0". | timestamp [warn] Received http status code 404 ("Not found") from | server 'server4IP:port' while fetching | "/tor/keys/fp-sk/A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0-A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0". | | Only one timestamp and serverIP was consistent on both relays. All | fingerprints, however, were consistent on both. Hasn't appeared before | or since. Anything to worry about? Thanks.

Thanks for reporting. This happens when directory authorities switch signing keys and you shouldn't worry.

My guess is that your fingerprints read ED03BB616EB2F60BEC80151114BB25CEF515B226-B59F6E99C575113650C99F1C425BA7B20A8C071D which would be gabelmoo with a new signing key since 2014-01-11 16:26:31 (UTC).

It's actually a bit misleading that you replaced both fingerprints with the same string. If they are indeed identical, there's something to worry about.

You will see more of these in the near future as all directory authorities are switching signing keys before schedule in order to increase the key size. See https://people.torproject.org/~linus/sign2048.html for the progress on this. We hope to have moved all authority signing keys to 2048 bits within a couple of weeks.