lukechilds
/
electrum
mirror of https://github.com/lukechilds/electrum.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
9253 Commits
21 Branches
132 Tags
52 MiB
 
 
 
 
Tree: 7e0b470ca2
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7e0b470ca2'
${ noResults }
electrum/contrib/build-wine
Filip Gospodinov 5fde89b689
Dockerfile: don't suppress error message (#4509) 		6 years ago
..
docker Dockerfile: don't suppress error message (#4509) 6 years ago
README.md winbuilds: update README. Do not sign in unsign.sh 6 years ago
build-electrum-git.sh docker windows build: fix missing translations 6 years ago
build-secp256k1.sh wine build: towards deterministic libsecp - strip debug symbols 6 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 6 years ago
electrum.nsi Fix typos 7 years ago
prepare-wine.sh wine build: try multiple keyservers as in tianon/gosu#35 6 years ago
sign.sh sign.sh: rm signed dir 6 years ago
unsign.sh sign.sh: rm signed dir 6 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:

  1. 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.

  1. Make sure /opt is writable by the current user.
  2. Run build.sh.
  3. 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
Sign .exe with ./sign.sh
Upload signed files to download server
Build .exe files using build.sh
Compare files using unsign.sh
Sign .exe file using gpg -b

| Signer and verifiers: | Upload signatures to 'electrum-signatures' repo, as $version/$filename.$builder.asc |

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:

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

The script unsign.sh performs these steps.