Changes between Version 14 and Version 15 of CodeSigning

Timestamp:

Aug 29, 2014, 1:28:23 PM (10 years ago)

Author:

davea

Comment:

--

CodeSigning

@@ -33 +33 @@
 == Changing your code-signing key ==
 
-To change your project's code-signing key:
+You can change your project's code-signing key at any point.
+To make this invisible to users, you must do the following steps
+(otherwise users will have to detach/reattach).
 
- * Generate a new key pair (do this on an offline machine).
- * In your project's 'keys' directory, put the old public key in a file 'old_key_0'.
- * Sign the new public key with the old private key, and put the signature in 'keys/signature_0'.
- * Release new versions of all apps, signed with the new key.
+Note: the following requires that you upgrade your server software to
+trunk as of at least 29 Aug 2014.
+
+On your code-signing machine:
+
+ * Rename your current key pair to '''old_key_private_i''' and '''old_key_i''' for the next available i
+   (i.e. old_key_0, old_key_1 etc. is the history of your public keys).
+ * Generate a new key pair, say '''code_sign_private''' and '''code_sign_public'''.
+{{{
+crypt_prog -genkey 1024 code_sign_private code_sign_public
+}}}
+ * Create a "stripped" version (removing the trailing \n) of the public key:
+{{{
+head -c -1 code_sign_public > code_sign_public_stripped
+}}}
+  (this is needed because 7.0+ clients strip \n from the end of keys).
+ * For each old key i, sign both the original and stripped versions of the new public key:
+{{{
+crypt_prog -sign code_sign_public old_key_private_i > signature_i
+crypt_prog -sign code_sign_public_stripped old_key_private_i > signature_stripped_i
+}}}
+ * Put '''code_sign_public''' and (for all i) '''old_key_i''', '''signature_i''', and '''signature_stripped_i'''
+   on a USB memory stick.
+ * Sign all your app version files with the new key; put these signatures on the memory stick also.
+
+On your project server:
+
+ * Stop the project.
+ * Use update_versions to create new app versions, using the new file signatures.
+ * Copy '''code_sign_public''' and (for all i) '''old_key_i''', '''signature_i''' and '''signature_stripped_i'''
+   from the memory stick to your project's '''keys/''' directory.
+ * Start the project.
 
 You might want to do this when your project goes public,
 you've started using an offline signing machine,
 and you don't want to force existing users to detach and reattach.
-
-If you change code-signing keys frequently,
-you can keep multiple (old key, signature) pairs,
-so that client that haven't connected in a long time will update successfully.
-If a client has a signing key that's not current, the server logic is:
-
- * Scan the keys/ directory for files '''old_key_i''' for i = 0, 1, ...
- * If one of these contains the key sent by the client,
-   send the client the new key with the signature in '''signature_i'''.
-
-Note that '''signature_i''' contains a signature for the newest key,
-signed by the old key i.
-You must regenerate these when you issue a new key.