Please be respectful of this website as you'll find you can edit transactions that others have listed. This is to allow people to collaboratively add their combined expenses with all the complications that cavers bring to anything. However, it could be abused. Please don't. The admins can see records of who changed what and when.
BoC was originally designed for expedition use, where expenses are distributed by number of nights/car-passengers/beers. Being online helps accounting transparency, allows real-time review of creditors/debtors, and, if input permissions are devolved, reduces the burden on the treasurer. Due to its expedition origins it correctly handles exchange rates changing over time.
Please read how these expenses records are also kept manually on paper in the Bier and Sesh books in the potato hut.
-
Bank of Expo (and the same software running as Bank of CUCC for ordinary caving trips) was written by Stuart Bennett in Cambridge. He says:
"BoC is a multi-user auditable online share-based accounting system. The `share-based' part is probably its distinguishing feature: absolute amounts are split evenly across the slates of implicated users and/or ring-fenced cost-pools. Transactions are automatically double-entry, and as real-world transactions are made against a real bank account, the
@@ -20,10 +20,9 @@
The split mechanism transparently underlies everything, but for user-friendliness there are various handy web-forms provided which generate the split tables (`Transaction Groups'). These range from a simple person-to-person swap, to a customizable `Event' with costs for various items being automatically squirrelled away into pre-set cost-pools."
-
Now read the online documentation at https://github.com/malc0/BoC which has a link to a demonstration system that you can play with (CUCC meets 2014-15).
+
Now read the the documentation (PDF) (for the version running on the expo server).
-
-Here is the the original documentation (PDF). It's a bit out of date: the instructions online largely replace Chapter 2.
+
Source and docs for the upstream version are online at https://github.com/malc0/BoC which has a link to a demonstration system that you can play with (CUCC meets 2014-15).
diff --git a/handbook/bocdoc.pdf b/handbook/boc.pdf
similarity index 73%
rename from handbook/bocdoc.pdf
rename to handbook/boc.pdf
index 0a6279b5c..5edec354e 100644
Binary files a/handbook/bocdoc.pdf and b/handbook/boc.pdf differ
diff --git a/handbook/computing/keyexchange.html b/handbook/computing/keyexchange.html
index c805d8595..e8f6fe7dd 100644
--- a/handbook/computing/keyexchange.html
+++ b/handbook/computing/keyexchange.html
@@ -2,7 +2,7 @@
-Handbook placeholder page
+Key-Pair Setup (Expo handbook)
@@ -20,7 +20,7 @@
A public key file looks like this: ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEApc9+PAMrDtWa8D8/ZneLP2X9UOYmTITAhTd2DRs8SE+NDgis5pYo/Xhtbrg86ePMAC2YM5xAkYx3jNA/VZ/PkB3gTzYJW3T/zTH+cc7YeWhy9l1zIMaYqeyvw7FxeSBaR4XoLPVtVUlai8DUDiWAEm7VvOKj1n68z1LxVh1MZXLm7btckf6fske2YU9UpjqT++AURQvFheRJ4la7KBJ7LXZ3A/TQ7HQaTpqmcQKCiRj/yZ5FNHxBk0M+ShbHUtz1GhXRCMJ3LZHaw24OJyVJ8YNzBiStBb1qcWCXX7HR9CUNhz7tA5HZyc1lau/1vwk8MSe93lyyLntzJKkqmkW/cQ== wookey@khi.e. a long string of characters with 'ssh-rsa' at the start and a 'user'@'machine' ID at the end.
+
A public key file looks like this: ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEApc9+PAMrDtWa8D8/ZneLP2X9UOYmTITAhTd2DRs8SE+NDgis5pYo/Xhtbrg86ePMAC2YM5xAkYx3jNA/VZ/PkB3gTzYJW3T/zTH+cc7YeWhy9l1zIMaYqeyvw7FxeSBaR4XoLPVtVUlai8DUDiWAEm7VvOKj1n68z1LxVh1MZXLm7btckf6fske2YU9UpjqT++AURQvFheRJ4la7KBJ7LXZ3A/TQ7HQaTpqmcQKCiRj/yZ5FNHxBk0M+ShbHUtz1GhXRCMJ3LZHaw24OJyVJ8YNzBiStBb1qcWCXX7HR9CUNhz7tA5HZyc1lau/1vwk8MSe93lyyLntzJKkqmkW/cQ== wookey@khi.e. a long string of characters with 'ssh-rsa' at the start and an ID at the end (often 'user'@'machine').
Windows
On a Windows machine use
@@ -28,8 +28,11 @@
Follow the Puttygen instructions, but the really short version is:
Run PuTTYgen
Click on 'Generate'. Follow the instructions. Don't bother adding a passphrase.
-
Save the key
-
Copy all of the public key out of the window and paste that into the email. Make sure not to miss part or add newlines or otherwise mess with it.
+
Type your name in the 'Key comment' field. (just so we know who's key it is)
+
Save the private key (this will create a .ppk file that you will need later)
+
Don't save the public key - instead copy all of the text from the 'Public key for pasting
++into OPENSSH authorized_keys file' field, and paste that into the email. Make sure not to miss part or add newlines or otherwise mess with it.
+
Run Pageant (it will have been installed in your Start menu, otherwise find it it "C:\Program Files\PuTTY\pageant.exe"). Click the "Add Key" button. Select the .ppk file in the pop-up file list. You only need to do this once.
Linux
@@ -39,7 +42,6 @@
If not, run ssh-keygen. It may ask about passwords: you can add a password for extra
security, but a passwordless key is fine, and more convenient.
That will create a file: .ssh/id_rsa.pub in your home directory. Email that file to one of the admins listed above.
-
Run Pageant (it will have been installed in your Start menu, otherwise find it it "C:\Program Files\PuTTY\pageant.exe"). Click the "Add Key" button. Select the .ppk file in the pop-up file list. You only need to do this once.
@@ -62,7 +64,7 @@
Your second machine
-
OK, you have an uploaded and usable key and you can ssh into the expo server. Now you want to set up a key for another machine such as your phone. You don't need a nerd admin now, you can do this yourself. But be extremely careful to follow this exactly. If you innocently rename the files to something that appears more sensible it won't work.
+
OK, you have an uploaded and usable key and you can ssh into the expo server. If you want to connect from another machine (e.g. your phone) it's better to make another key than try to re-use the first one. You don't need a nerd admin now, you can do this yourself. But be extremely careful to follow this exactly. If you innocently rename the files to something that appears more sensible it won't work.
On your new machine, generate a key-pair. Since you are probably using a different operating system on your second machine, read the instructions above for the relevant OS. Yes you will be generating a new key. Do not re-use the key you had already.
This time though, you will want to be sure that the key has a meaningful label. On Linux this means something like this:
@@ -73,7 +75,7 @@ If you accepted the defaults, the public key will be called expo.survex.com/home/expo/.ssh/keys/
Now login to the expo server on your first machine and do these commands:
-Be extremely careful to type ">>" and not ">" in the fourth line below otherwise you will delete everything.
+Be extremely careful to type ">>" and not ">" in the fourth line below otherwise you will delete everyone's logins.
$ ssh expo@expo.survex.com
expo@expo:~$ cd .ssh
expo@expo:~$ cp -p authorized_keys authorized_keys.backup