This is the tracker for the Distributed Proxy assignment for the Datanet Networking course at the University of Copenhagen. These pages contain links to the tracker pages as well as documentation for how to interact with the tracker.

There are currently no peers in the database.

Available Peer Lists

The peer lists can be downloaded in the following formats. Please see the documentation for more info.

• YAML
• JSON
• Bencode
• XML
• Plain text
• Plain text with keys

Public Key

You can get the trackers public key in various formats (see the documentation on Public Key Formats for more info:

• PEM
• YAML
• JSON
• Benconce
• XML
• TXT

Changelog

2011-06-10

• Fixed diagram on the Security Page to show that the hash is calculated over the body and the nonce.
• Fixed text describing padding (which showed values in bits but describeded them as byts).

2011-06-08

• Add a peer list that always shows keys: peer_keys.txt

2011-05-31

• Updated the Super Peer page to indicate that one can set the Super-Via header to a value (e.g., if your http library or application of choice refuses to send empty headers
• Updated the whitelist

2011-05-24

• Fixed an issue where last_registered was not updated for clients making non-signed requests
• Updated whitelist

2011-05-17

• Fixed various errors reported by Rasmus Abrahamsen:
  • In the dictionary based peer lists (json, yaml, etc) last_registered was spelt incorrectly (as last_reqistered)
  • When registering the tracker now checks that a port value is specified and return a 400 error if not
  • Fixed an error that meant that peers registering without a public key got a 500 error
• Fixed the spelling of last_registered on the YAML, JSON, and Bencode Peer Lists and XML Peer List pages
• The dictionary based peer lists did not check to see if a peer had a public key when generating the peer lists, potentially resulting in an internal server error

2011-05-16

• Fixed the Super-Via response example on the Super Peer page
• Removed link to nonexisting page on the Responses page
• Clarification of 400 error on the Responses page

2011-05-04

• Updated the Whitelist documentation to state that a 403 should be sent as a response of a request is denied due to the whitelist.
• Updated the Whitelist documentation to state that the whitelist domains are supplied in fully qualified domain name (FQDN) form.
• Updated the whitelist entries to be in FQDN form.

2011-04-29

• The tracker has been made live