diff options
Diffstat (limited to 'doc/26.RPKI.CA.UI.md')
| -rw-r--r-- | doc/26.RPKI.CA.UI.md | 26 |
1 files changed, 17 insertions, 9 deletions
diff --git a/doc/26.RPKI.CA.UI.md b/doc/26.RPKI.CA.UI.md index fe64aa1f..8f05a518 100644 --- a/doc/26.RPKI.CA.UI.md +++ b/doc/26.RPKI.CA.UI.md @@ -9,12 +9,12 @@ no existing back end with a fairly large programming project. The user interface tools attempt to fill that gap. Together with irdbd, these tools consitute the "IR back-end" (IRBE) programs. -rpkic is a command line interface to the the IRBE. The web interface is a -Django-based graphical user interface to the IRBE. The two user interfaces are -built on top of the same libraries, and can be used fairly interchangeably. -Most users will probably prefer the GUI, but the command line interface may be -useful for scripted control, for testing, or for environments where running a -web server is not practical. +[rpkic][1] is a command line interface to the the IRBE. The [web interface][2] +is a Django-based graphical user interface to the IRBE. The two user +interfaces are built on top of the same libraries, and can be used fairly +interchangeably. Most users will probably prefer the GUI, but the command line +interface may be useful for scripted control, for testing, or for environments +where running a web server is not practical. A large registry which already has its own back-end system might want to roll their own replacement for the entire IRBE package. The tools are designed to @@ -49,7 +49,7 @@ While the specific commands one uses differ depending on whether you are using the command line tool or the GUI, the basic operations during setup phase are the same: - 1. If you haven't already done so, install the software, create the rpki.conf for your installation, and set up the MySQL database. + 1. If you haven't already done so, [install the software][3], create the [rpki.conf][4] for your installation, and [set up the MySQL database][5]. 2. If you haven't already done so, create the initial BPKI database for your installation by running the "rpkic initialize" command. This will also create a BPKI identity for the handle specified in your rpki.conf file. BPKI initialization is tied to creation of the initial BPKI identity for historical reasons. These operations probably ought to be handled by separate commands, and may be in the future. 3. If you haven't already done so, start the servers, using the `rpki-start-servers` script. 4. Send a copy of the XML identity file written out by "rpkic initialize" to each of your parents, somehow (email, USB stick, carrier pigeon, we don't care). The XML identity file will have a filename like ./${handle}.identity.xml where "." is the directory in which you ran rpkic and ${handle} is the handle set in your rpki.conf file or selected with rpkic's `select_identity` command. This XML identity file tells each of your parents what you call yourself, and supplies each parent with a trust anchor for your resource-holding BPKI. @@ -94,6 +94,14 @@ just the URI of the directory on its command line: If you need to examine RPKI objects in detail, you have a few options: - * The RPKI utilities include several programs for dumping RPKI-specific objects in text form. + * The [RPKI utilities][6] include several programs for dumping RPKI-specific objects in text form. * The OpenSSL command line program can also be useful for examining and manipulating certificates and CMS messages, although the syntax of some of the commands can be a bit obscure. - * Peter Gutmann's excellent [dumpasn1](http://www.cs.auckland.ac.nz/~pgut001/dumpasn1.c) program may be useful if you are desperate enough that you need to examine raw ASN.1 objects. + * Peter Gutmann's excellent [dumpasn1][7] program may be useful if you are desperate enough that you need to examine raw ASN.1 objects. + +[1]: 26.RPKI.CA.UI.md.rpkic +[2]: 28.RPKI.CA.UI.GUI.md +[3]: 01.RPKI.Installation.md +[4]: 12.RPKI.CA.Configuration.md +[5]: 24.RPKI.CA.MySQLSetup.md +[6]: 36.RPKI.Utils.md +[7]: http://www.cs.auckland.ac.nz/~pgut001/dumpasn1.c |