Automatic pull of documentation from Wiki.

svn path=/trunk/; revision=5605

2 files changed, 15 insertions, 0 deletions

diff --git a/doc/doc.RPKI.CA.Configuration.CreatingRoot b/doc/doc.RPKI.CA.Configuration.CreatingRoot
index fbdf0bc4..b9004a4c 100644
--- a/doc/doc.RPKI.CA.Configuration.CreatingRoot
+++ b/doc/doc.RPKI.CA.Configuration.CreatingRoot
@@ -43,8 +43,13 @@ this:
 Assuming you save this configuration in a file root.conf, you can use it to
 generate a root certificate as follows:
 
+  #!/bin/sh -
+
+  # Generate the root key if it doesn't already exist.
+  test -f root.key ||
   openssl genrsa -out root.key 2048
 
+  # Generate the root certificate.
   openssl req                     \
           -new                    \
           -x509                   \
@@ -80,6 +85,16 @@ $top/rcynic:
 
   $top/rcynic/make-tal.sh  rsync://example.org/rpki/root/root.cer  root.cer
 
+Note that, like any certificate, the root.cer you just generated will expire
+eventually. Either you need to remember to regenerate it before that happens,
+or you need to set up a cron job to do that for you automatically. Running the
+above shell script (really, just the openssl req command) should suffice to
+regenerate root.cer; remember to copy the updated root.cer to the publication
+directory.
+
+Regenerating the certificate does not require regenerating the TAL unless you
+change the key or URL.
+
 ***** Converting an existing RSA key from PKCS #8 format *****
 
 If you previously generated a certificate using openssl req with the -newkey
diff --git a/doc/manual.pdf b/doc/manual.pdf
index a00153bb..9168f15d 100644
--- a/doc/manual.pdf
+++ b/doc/manual.pdf