aboutsummaryrefslogtreecommitdiff
path: root/scripts/regeng-api
diff options
context:
space:
mode:
authorRob Austein <sra@hactrn.net>2007-03-22 09:31:16 +0000
committerRob Austein <sra@hactrn.net>2007-03-22 09:31:16 +0000
commitaae9220ad200be379c147cc05733be1a09e2ccda (patch)
tree7d0895a042bf3aa31112a6265db85d8e1829525f /scripts/regeng-api
parentb7198e941eaa86f115ddd7890c78a55983184e9f (diff)
*** empty log message ***
svn path=/scripts/regeng-api; revision=521
Diffstat (limited to 'scripts/regeng-api')
-rw-r--r--scripts/regeng-api6
1 files changed, 6 insertions, 0 deletions
diff --git a/scripts/regeng-api b/scripts/regeng-api
index 8a2463b0..24e5ae25 100644
--- a/scripts/regeng-api
+++ b/scripts/regeng-api
@@ -55,6 +55,12 @@
;;; internal name for the CA, whatever. This hack may require finding
;;; out the parent's publication URI (which we might get from the
;;; parent's cert or not to be decided later), sort this out later.
+;;;
+;;; If there is any preliminary negotation with publisher before
+;;; publication, it is all hypothetical and assumes that proof will be
+;;; given with actual publication request. Thing that needs to be
+;;; proven is that publication client A is not stepping on publication
+;;; client B even when B is A's parent.