cylenet is an experiment, in which I build my own internet-like thing. It (currently) has two primary features:
- WiNS, AKA Winners Name Service, a DNS-like service that expects hostnames and responds with IP addresses.
- CTP, AKA Cyle's Transfer Protocol, an HTTP-like service that expects requests for files and responds with the contents of those files.
Both are meant to be top-to-bottom SSL-encrypted.
Because why not.
- node.js 7.x or later (at least, that's what I built it with)
Right now it's all very, very simple. It's currently configured to work on your own computer only (all localhost pretty much). And these instructions are written assuming you're on a Mac.
First of all, clone this repository somewhere on your computer.
Open three Terminal windows. Using one of them, you need to make some self-signed SSL certificates:
cylenetfolder you cloned.
openssl genrsa -out cylenet.key.pem 2048
- Next, run
openssl req -new -key cylenet.key.pem -out cylenet.csr.pem
- Next, run
openssl x509 -req -in cylenet.csr.pem -signkey cylenet.key.pem -out cylenet.crt.pem
Yes, you just made a self-signed certificate, which isn't great for "verified" authorized encrypted traffic, but for now it'll have to do until I come with a cylenet SSL alternative.
Now that you have your cert set up, here's what you do with the project to test this out and see it work:
- in one Terminal window, go to the
WiNS-SSLfolder, and run
- in another Terminal window, go to the
CTP-SSLfolder, and run
- in the final Terminal window, go to the
CTP-SSLfolder, and run
node client.js "cyle.lol"
That final step does the following...
- uses my WiNS-SSL module to translate the desired server hostname "cyle.lol" to the IP "127.0.0.1"
- sends the request
req cyle.lol/to the CTP server at that IP.
- renders out the response, which should be a simple text file, in Markdown format, from the "ctproot" folder.
There are two CyleNet GUI browsers included here, but they're still in development. There's one
browser-old which is
node-webkit based. There's a newer one that actually works and it's Electron based.
To use the new one, make sure you're running your WiNS and CTP services locally. It mainly only works in local mode right now.
- Go to the
browser-electronfolder in this repo.
npm installto install local dependencies.
npm startto open the browser.
It's very simple right now... there's a window to manage which WiNS servers you're using, but only the first one in the list is currently used. You can navigate anywhere you'd like using the address bar. If the response is in Markdown, it'll be rendered as markdown in the main browser window. If there's an error of some kind, it'll be shown.
- WiNS-SSL runs on port 21335 by default
- CTP-SSL runs on port 21337 by default
- all of this is still TCP-based... not sure how I feel about that part yet, if I want to dive deeper
- "real" TLS certificates still rely on old ideas, kind of, which I don't want, so I may accept the reality of self-signed certs
- WiNS and CTP are standard specifications much like DNS and HTTP, and I've started documenting them in the
ctprootis the folder the CTP server uses as a base for requests. A "lol" file is the default "index" file equivalent.
- Loading/progress indicator in browser UI.
- Update browser to support multiple WiNS servers; add UI to show attempts and which one ended up working.
- Add to demo WiNS client support for following "try" responses.
- Update browser to use "try" WiNS responses.
- Add in some kind of memcache-based rate limiting to CTP and WiNS ?
- Make the GUI browser run a WiNS and CTP server, or make it a separate bundle.
- Add some kind of wildcard functionality to WiNS records? as in
* try 192.168.1.1as a fallback at the end of a file?
- Add some kind of client-side caching of WiNS records? if so, add a TTL to the server and client...?
- Need to compress CTP traffic with gzip or something.
- Update WiNS-SSL to use the text file format described in the spec
- Update WiNS-SSL to send back
- Update the GUI browser, add some kind of way to manage what WiNS servers you trust