aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRob Austein <sra@hactrn.net>2007-11-19 16:53:17 +0000
committerRob Austein <sra@hactrn.net>2007-11-19 16:53:17 +0000
commitcf4bdfa98b8ec57fd9611df00cb52d4d0d7bb134 (patch)
treeeb870ee7bc8c599bb33e7c819f6edf54a2671a6e
parent5313b1beb56100b6fdcd1117f3918c5f94739e5c (diff)
Notes on root key
svn path=/scripts/README; revision=1329
-rw-r--r--scripts/README7
1 files changed, 5 insertions, 2 deletions
diff --git a/scripts/README b/scripts/README
index f1fa21c6..29eef8d3 100644
--- a/scripts/README
+++ b/scripts/README
@@ -198,12 +198,15 @@ Current TO DO list:
If it's not a separate daemon, will need left-right protocol support
to configure whatever it is we're going to configure, with all the
- usual private key hygiene issues. This probably implies a level of
+ usual private key hygiene issues. This might imply a level of
indirection, eg, the self-signed cert is generated in the IRBE, the
RPKI engine generates PKCS#10 for a working cert to be issued by the
self-signed cert (perhaps with RFC 3779 inheritance for everything,
to keep it small), so that the RPKI engine never needs to hold the
- private key for the root.
+ private key for the root. Or maybe the root key is no more special
+ than any of the other keys we have to protect. Or maybe it's so
+ special that we take the separate daemon approach so we can
+ sneakernet the root key. Or some combination of the above.
Deferred for the moment, not sure for how long.