History

root 240dc888ec Add script to strip signature from signed binary		7 years ago
..
README.md	Add script to strip signature from signed binary	7 years ago
build-electrum-git.sh	win builds: call 'git describe' before we add unstaged files to the repo	7 years ago
build-secp256k1.sh	wine build: towards deterministic libsecp - strip debug symbols	7 years ago
build.sh	build and include libsecp256k1 in windows binaries	7 years ago
deterministic.spec	fix revealer for linux distributables; and small clean-up	7 years ago
electrum.nsi	Fix typos	7 years ago
prepare-wine.sh	build and include libsecp256k1 in windows binaries	7 years ago
sign.sh	Add script to check and sign executables	7 years ago
unsign.sh	Add script to strip signature from signed binary	7 years ago

README.md

Windows Binary Builds

These scripts can be used for cross-compilation of Windows Electrum executables from Linux/Wine. Produced binaries are deterministic, so you should be able to generate binaries that match the official releases.

Usage:

Install the following dependencies:

dirmngr
gpg
7Zip
Wine (>= v2)
(and, for building libsecp256k1)
- mingw-w64
- autotools-dev
- autoconf
- libtool

For example:

$ sudo apt-get install wine-development dirmngr gnupg2 p7zip-full
$ sudo apt-get install mingw-w64 autotools-dev autoconf libtool

The binaries are also built by Travis CI, so if you are having problems, that script might help.

Make sure /opt is writable by the current user.
Run build.sh.
The generated binaries are in ./dist.

Code Signing

Electrum Windows builds are signed with a Microsoft Authenticode™ code signing certificate in addition to the GPG-based signatures.

The advantage of using Authenticode is that Electrum users won't receive a Windows SmartScreen warning when starting it.

The release signing procedure involves a signer (the holder of the certificate/key) and one or multiple trusted verifiers:

Signer	Verifier
Build .exe files using `build.sh`
	Build .exe files using `build.sh`
	Sign .exe files using `gpg -b`
	Send signatures to signer
Place signatures as `$filename.$builder.asc` in `./dist`
Run `./sign.sh`

sign.sh will check if the signatures match the signer's files. This ensures that the signer's build environment is not compromised and that the binaries can be reproduced by anyone.

Verify Integrity of signed binary

Every user can verify that the official binary was created from the source code in this repository. To do so, the Authenticode signature needs to be stripped since the signature is not reproducible.

This procedure removes the differences between the signed and unsigned binary:

Remove the signature from the signed binary using osslsigncode or signtool.
Set the COFF image checksum for the signed binary to 0x0. This is necessary because pyinstaller doesn't generate a checksum.
Append null bytes to the unsigned binary until the byte count is a multiple of 8.

The script unsign.sh performs these steps.