OK, I solved that mystery:
certificate.p12 is a (self-signed) certificate file that is used to sign the executable being built. It is already supposed to be on the developer’s (my) system and is expected, by default, by the aip (build-settings) file in the safe_vault package.
I could have edited that option out in the AdvancedInstaller gui editor and saved the amended aip file, but I felt it might be a useful learning exercise to created my own certificate, and put the path to it into the aip file.
To create a certificate.p12 file:
First install openssl: http://slproweb.com/products/Win32OpenSSL.html
Add environment variables in order to make openssl available to the compiler:
Go through steps 1 to 5 described here:
I put the file in my home folder and configured that path into the aip file.
I ran the create_installer.ps1 script again and it completed without any errors, and dutifully signing the msi (Windows installation) file!
However, running the installation file did not produce a working vault:
The installation wizard ran and completed without error, but there were problems when I tried to run the safe_vault.exe:
Files were not in the right places. (I’ll cut this explanation short though by not describing everything)
Safe_vault.exe would only run when run as administrator because there was some file it could not otherwise access.
I got the same error as when I installed safe_vault manually ( see Pre-Dev-Update Thread! Yay! :D ):
“Failed to start listening to peers.”
This is alpha software (just saying…) as stated in the source code comments. But I’m wondering if the core devs are aware of these issues and do they welcome patches, since I seem to be coming up to speed with hacking this stuff. Or do I content myself with experimenting with it on Linux?