prototype/proof-of-concept to implement Proposition 279 w/o changing Tor (Namecoin fork, you should probably be using upstream instead)
Switch branches/tags
Nothing to show
Clone or download
Pull request Compare This branch is 4 commits behind meejah:master.
Latest commit 5ed4abe Jun 22, 2017
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
LICENSE add license (unlicense) Jun 17, 2017
README.md mention banana Apr 9, 2017
ns_always_txtorcon.py genesis Apr 8, 2017
ns_petname.py Remove TLD restrictions. Jun 20, 2017
poc.py Fix issue introduced in 9be1ef4 that caused a new service to be spawn… Jun 22, 2017

README.md

Proposal 279

This is an implmentation of the "Tor side" of Proposal 279 ("naming layer api") so that actual naming plugins can be tested/prototyped "now" without changing Tor.

Using This

It will currently connect to a system tor on localhost:9051 or you can change this to 9151 (in poc.py) to react a Tor Browser Bundle instance.

This actually works and launches two example services, reached via: ..onion where the two services are .pet.onion for the ns_petname.py lookup (so try, e.g., "http://scihub.pet.onion" in TBB).

The other one is .demo.onion and will always remap to txtorcon's documentation hidden-service. So .demo.onion will redirect you to txtorcon's documentation.

Naming Implementations