Modified code sign instructions and README.md

README.md

@@ -12,11 +12,18 @@ with Maven then [download it first](http://maven.apache.org) and follow their in
 * [Bitcoinj Enforcer Rules](https://github.com/gary-rowe/BitcoinjEnforcerRules) to prevent dependency chain attacks
 * [XChange](https://github.com/timmolter/XChange) for access to several Bitcoin exchanges
 
-#### A note on the Bitcoinj dependency
+### MultiBit contains cut down JREs so is a large clone
+
+The MultiBit installers contain cut down JREs so the project clone is quite large.
+(100 to 200 MB).
+
+### The Bitcoinj "Alice" dependency
 
 MultiBit depends on a special fork of Bitcoinj for its Bitcoin support. This is due to legacy wallet serialization issues
-and the MultiBit team are working towards a complete integration. To build MultiBit you will need to clone this fork from
-here:
+and the MultiBit team are working towards a complete integration through the MultiBit HD project.
+
+While it is possible to build MultiBit using our staging repository you may want to review the modified Bitcoinj library
+for yourself. You can clone from this fork:
 ```
 https://code.google.com/r/jimburton618-bitcoinj-coinbase-tx/source/checkout
 ```
@@ -31,7 +38,7 @@ mvn clean install
 
 ### Branching strategy
 
-This follows the  [master-develop](http://nvie.com/posts/a-successful-git-branching-model/) pattern.
+This follows the ["master-develop" or "Git flow"](http://nvie.com/posts/a-successful-git-branching-model/) pattern.
 
 There are 2 main branches: `master` and `develop`. The `master` branch is exclusively for releases, while the `develop`
 is exclusively for release candidates. The `develop` branch always has a Maven version of `develop-SNAPSHOT`.

code-sign-on-windows.md

@@ -0,0 +1,32 @@
+# How to code sign the Windows installer
+
+1) Build all the installers on your main build machine (assumed not to be a Windows machine).
+
+2) Prepare a directory on a USB drive containing:
+
+* the windows installer file e.g) `multibit-0.5.17-windows-setup.exe`
+* the encrypted private key 
+* object signing certificate PFX file.
+* (James-Burton-object-pfx.p12)) This is not under source control for security reasons.
+* Use `KSign` to do the signing so you might want a copy of the KSign installer, `ksign-installer.exe`, on your USB.
+
+3) Transfer the USB to your Windows signing machine.
+
+4) Install `KSign` if necessary.
+
+5) Start `KSign` and add the following entries:
+
+* File to sign: `multibit-0.5.17-windows-setup.exe`
+* Description: MultiBit - lightweight Bitcoin wallet
+* Enter the password to decrypt the PFX file.
+
+6) You should see a success message.
+
+7) Test the installer by double clicking on it.
+   You should see a User Account Control dialog signed by "James Burton".
+
+8) Transfer the signed installer back to your main build machine.
+
+9) Put it in the releases directory.
+
+Remember: you need to do the PGP signing and SHA256 hashes AFTER code signing)