1 files changed, 50 insertions, 0 deletions
diff --git a/scripts/regeng-api.lisp b/scripts/regeng-api.lisp
index 58e14bcf..4b719caa 100644
--- a/scripts/regeng-api.lisp
+++ b/scripts/regeng-api.lisp
@@ -4,3 +4,53 @@
 ;;;
 ;;; This file is psuedocode, I just wanted to take advantage of
 ;;; emacs's built-in support for languages with reasonable syntax.
+
+
+
+;;; Protocol operations between registration engine and signing engine.
+;;; This assumes the model in which the signing engine stores nothing
+;;; but keypairs and takes orders from the registration engine on what
+;;; to sign; this still needs to be checked by competent paranoids.
+
+;; Create a keypair.  :length is the number of bits for the key
+;; (default 2048?).  :handle is optional, and is here to allow forward
+;; references within a sneakernet queue.
+
+(create-keypair :cust-id 42
+		:length 2048
+		:handle customer-42s-new-keypair)
+
+=> (public-key handle)
+
+;; Destroy a keypair.
+
+(destroy-keypair :cust-id 42
+		 :public-key public-key)
+
+;; List existing keypairs
+
+(list-keypairs :cust-id 42)
+
+=> (public-key public-key ...)
+
+;; Sign something.  Will probably need to break this down into
+;; separate signing calls for each kind of thing to be signed, but
+;; most likely they will all look pretty much alike.  One of
+;; :key-to-use or :key-handle must be specified.
+
+(sign-thing :cust-id		42
+	    :what-to-sign	blob
+	    :how-to-sign	'rsa/sha256
+	    :key-to-use		public-key
+	    :key-handle		handle-for-public-key)
+
+=> (signed-thing)
+
+;; Do we need a verify operation here that can take a handle so we can
+;; verify things that were signed by keys that don't exist yet at the
+;; time we're queuing up the sneakernet channel?  Hope not, sounds
+;; complicated.  Punt for now.
+
+
+
+;;; Protocol operations between IR back-end and registration engine.