https://github.com/willscott/oneswarmdirectoryserver

Directory Server to support OneSwarm clients in finding Exit Nodes.
https://github.com/willscott/oneswarmdirectoryserver

Last synced: about 1 year ago
JSON representation

Directory Server to support OneSwarm clients in finding Exit Nodes.

• Host: GitHub
• URL: https://github.com/willscott/oneswarmdirectoryserver
• Owner: willscott
• Created: 2012-08-13T23:15:07.000Z (almost 14 years ago)
• Default Branch: master
• Last Pushed: 2012-09-13T17:59:20.000Z (over 13 years ago)
• Last Synced: 2025-02-06T10:31:21.739Z (over 1 year ago)
• Language: Java
• Size: 4.14 MB
• Stars: 1
• Watchers: 4
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

          
OneSwarm Directory Service

======

Usage

------

Run the java code (The main entry point is in OSDirectoryServer).

If it is the first time, the server will generate a signing key,

and will sign all listings with that key.  The key pair will be stored

in the file "key.store", and the public certification will be stored

in "directory.cert".  Clients should be given the certificate to

validate the authenticity of responses they receive from the directory.

If the file "knownPartners.txt" is present, it will be used to

allow multiple instances of the service to coordinate as a single entity.

The file should contain one entry per line of the address (host:port) of

the other instances.  When updates are given an instance, it will

relay those state changes to the other instances.

Inprogress:

------

 * Updates should be encrypted with the public key, so that an attacker

   gaining access of the directory server can't see payloads.

 * Syncronization between instances should be bundled, to lower load.

 * Additional verification of registrations should occur:

    * Limit registrations allowed to each IP.

    * Ensure a service is running at the requested service.

    * Ensure the asserted bandwidth / location / policy are reasonable.