Home

Welcome to the reticle wiki!

The reason the documentation is limited is a much simpler reason, namely that I've been excessively busy and haven't had time to get it all online yet. So, sorry for that.

OK, very very very brief intro, better docs coming soon, but if you're having trouble getting started:

The F-BOMBs are running SSH, login pi, password raspberry, from the start. They also run the full Reticle stack, including CouchDB, Nginx to act as an SSL-verifying proxy to Couch, and Tor exposing Nginx as a hidden service. Couch locally is indeed 50121, so you can connect to that (through, e.g., a reverse SSH tunnel---or you could change couch.ini to make Couch listen on more than 127.0.0.1).

They won't be running at the start, though, because they don't have a TLS key in place. To add one, do the following:

1. ssh pi@<ip addr> # The password is raspberry
2. cd /tmp/crypt/util/crypto
3. ./genkeys.sh 1
4. cd /tmp/crypt/certs
5. cp ../util/crypto/reticleCA/certs/ca.pem .
6. cp ../util/crypto/nodeCerts/node_0001.key my.key
7. cp ../util/crypto/nodeCerts/node_0001.pem my.pem

This will generate a key and insert it into the proper place for Nginx and Couch to find it. If you'd like to use this node as the prime (command-inserting) node, also run cp ../util/crypto/reticleCA/certs/ca.key . to copy the signing key into place.

The restore image for the SD card is in the Releases section: https://github.com/ussjoin/reticle/releases . https://github.com/ussjoin/reticle/wiki/Restoring-the-Reticle-Image-from-an-SD-Card has how to burn it to an SD card.

If you set up a wireless AP with SSID Private and password 12345abcde (can be changed in portalsmash/networks.yaml in order to connect to your own wireless AP) and with Internet access, since it uses Tor, the F-BOMB will connect to it. Due to a weird way the Debian image deals with incoming requests (which in this case acts like a really useful firewall, but I can't claim credit), you need to connect to the F-BOMB via SSH within about 60 seconds of the F-BOMB's connecting to the network, or you won't get an ARP response. You can also (once you get the MAC from your access point) just set up a static ARP entry, which solves the problem generally.

Look through the code, especially the util folder (and the example missions inside); util will help you generate a CA and per-node certificates, and install missions and new versions of client.rb to the Reticle network.

And if you have questions, feel free to add them to the Wiki and we'll make a FAQ.