mirror of
https://github.com/LBRYFoundation/LBRY-Vault.git
synced 2025-08-27 07:23:25 +00:00
194bf84418
sudo is needed to rm FRESH_CLONE as docker is running as sudo. the proper fix would be to have docker not run as sudo...
100 lines
3.7 KiB
Markdown
100 lines
3.7 KiB
Markdown
Windows binaries
|
|
================
|
|
|
|
✓ _These binaries should be reproducible, meaning you should be able to generate
|
|
binaries that match the official releases._
|
|
|
|
This assumes an Ubuntu (x86_64) host, but it should not be too hard to adapt to another
|
|
similar system. The docker commands should be executed in the project's root
|
|
folder.
|
|
|
|
1. Install Docker
|
|
|
|
```
|
|
$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
|
|
$ sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
|
|
$ sudo apt-get update
|
|
$ sudo apt-get install -y docker-ce
|
|
```
|
|
|
|
2. Build image
|
|
|
|
```
|
|
$ sudo docker build -t electrum-wine-builder-img contrib/build-wine
|
|
```
|
|
|
|
Note: see [this](https://stackoverflow.com/a/40516974/7499128) if having dns problems
|
|
|
|
3. Build Windows binaries
|
|
|
|
It's recommended to build from a fresh clone
|
|
(but you can skip this if reproducibility is not necessary).
|
|
|
|
```
|
|
$ FRESH_CLONE=contrib/build-wine/fresh_clone && \
|
|
sudo rm -rf $FRESH_CLONE && \
|
|
mkdir -p $FRESH_CLONE && \
|
|
cd $FRESH_CLONE && \
|
|
git clone https://github.com/spesmilo/electrum.git && \
|
|
cd electrum
|
|
```
|
|
|
|
And then build from this directory:
|
|
```
|
|
$ git checkout $REV
|
|
$ sudo docker run -it \
|
|
--name electrum-wine-builder-cont \
|
|
-v $PWD:/opt/wine64/drive_c/electrum \
|
|
--rm \
|
|
--workdir /opt/wine64/drive_c/electrum/contrib/build-wine \
|
|
electrum-wine-builder-img \
|
|
./build.sh
|
|
```
|
|
4. The generated binaries are in `./contrib/build-wine/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.
|