Mercurial > hg > anonet-resdb

annotate README.txt @ 1248:95b01f0aed0d draft

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
copied structure.txt to root dir as README.txt
author Passive <passive@21.50.0.1>
date Sun, 08 Dec 2019 01:14:48 -0600
parents
children
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
1248
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
1 --- ResDB structure (As written by Sarah.ano 10/March/2014)
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
2 When I 'joined' anonet I was told to update the resdb.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
3 This in itself isnt all that hard to do if someone helps you.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
4 But when that isnt the case youre kind of stuck.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
5 There isnt a helpful README that says exactly what to do, or even what is necesary.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
6 As of writing, there isnt anything on the anonet wiki about it either.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
7 Maybe this can be that README?
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
8
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
9 -- ResDB in a nutshell
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
10 ResDB is where people write down what they own.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
11 If its not in the ResDB, people wont know its yours.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
12 Things like tinydns use the db/dom directory to find relevant DNS servers.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
13 Chakra in #anonet uses all information to answer requests. (try @asowner <num>)
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
14
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
15 -- A smallish disclaimer
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
16 Do not blindly run anything you find in ResDB.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
17 Someone could have edited, well, anything, to include a rm -rf / (or worse)
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
18 Everything is written in human readable languages. So just cat the scripts and read them.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
19 You might even learn something.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
20
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
21 -- What are all these things?
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
22 Short explanation on what everything in resdb is.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
23 doc/ Where people put documentation. A bit sparse. Also where this file should be.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
24 db/ Ill get to that later. Its the important bit.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
25 contrib/ Full of a lot of misc things that people found useful enough to include. Most of it is not documented. Run with care.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
26 scripts/ Mostly scripts directly related to working with ResDB. Again, run with care.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
27
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
28 The executables are related to running your own git and serving your modified ResDB.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
29 ./configure will configure git commit relevant stuff, and also configure gitd.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
30 ./gitd will run the git server. Optimally you would use this to serve your modified ResDB to others. Once someone else has it, it will usually spread fast.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
31 ./git-commit will commit whatever canges you made. You should always do this when done fucking with resdb. People cant pull uncommited changes.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
32
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
33 Once you want to announce your changes, just go to #anonet and tell people to pull from git://<yourgitdip>/
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
34 Note that many people set up a proper git server to serve ResDB and other things. The included gitd is a bootstrap and potential hazard. (Since future commits might put bad things in there.)
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
35
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
36 -- DB Structure
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
37 - db/as/
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
38 Every claimed AS has a directory here. Inside is a single file called 'owner'.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
39 That file simply contains the handle of whoever owns that AS.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
40 To add yourself, either create these things manually or use a script. (scripts/add_as)
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
41
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
42 - db/dom/
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
43 Inside is a directory for each TLD in use. In each TLD directory are domain names.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
44 Each domain name directory contains another 'owner' file, and a ns directory.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
45 The ns directory should contain a file named 'a.ns.<domain>.<tld>' or something similar.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
46 In that file should be a valid anonet ip to a DNS server. This DNS server will be asked about your domain and is required.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
47 There is also a script for this (scripts/add_dom), but take care to give a valid ns as argument too or your domain will be broken.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
48
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
49 - db/ip and db/ip6
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
50 Nested directories for each byte of an IP. At the end of that chain is, again, an owner file and a cidr file.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
51 Doing this manually might cause confusion, headaches and sudden death.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
52 Id recommend using a script. (scripts/add_ip)
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
53
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
54 - db/usr
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
55 Kind of freeform. A directory for every handle that cares to add itself.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
56 Inside, you can put pretty much whatever information you want.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
57 An adress to your git server, contact information. The filenames should be short and descriptive.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
58 Just check a few folders yourself and youll get the idea. Maybe find something useful.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
59
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
60 -- So what do?
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
61 Well, if you are reading this, I assume you are already peered. So you should know your information.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
62 So go and add it to the relevant places as explained.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
63 If you are still confused (as you should be) head to #anonet and seek help. You should say Hi anyway.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
64 Help on other related things (like tinydns) can be found on the wiki or asked for.
95b01f0aed0d copied structure.txt to root dir as README.txt
Passive <passive@21.50.0.1>
parents:
diff changeset
65 If something doesnt work, fuck around with it untill it does.