decred/decred-release

Decred binary releases.

decred-release

Overview

This repository contains the decred installers and the installer manifests.

For the binary archives, binary manifests and release notes please go to decred-binaries.

Verifying dcrinstall

For your security, we recommend that you verify binaries before running them. Each release contains a manifest file with SHA-256 hashes for each released binary. To ensure your downloads are authentic, you should verify that the manifest file is signed by [email protected], and that your hashed binary matches the manifest.

Detailed instructions can be found in the Decred Documentation: Verifying Binaries. New users should start there.

If you've already done this before and you still have the Decred Release keys on your GnuPG keyring, the following shorthand instructions are provided as a quick refresher:

1. Download:

   • The zip/tarball for your specific OS / architecture
   • The file manifest and hashes, ending in -manifest.txt
   • The signature for the manifest, ending in -manifest.txt.asc

2. Verify that the manifest was directly signed by the Decred project:

   $ gpg --verify dcrinstall-v1.5.1-manifest.txt.asc
   

   Example output:

   gpg: assuming signed data in 'dcrinstall-v1.5.1-manifest.txt'
   gpg: Signature made 01/29/20 15:17:45 Eastern Standard Time
   gpg:                using RSA key F516ADB7A069852C7C28A02D6D897EDF518A031D
   gpg: Good signature from "Decred Release <[email protected]>" [unknown]
   gpg: WARNING: This key is not certified with a trusted signature!
   gpg:          There is no indication that the signature belongs to the owner.
   Primary key fingerprint: FD13 B683 5E24 8FAF 4BD1  838D 6DF6 34AA 7608 AF04
      Subkey fingerprint: F516 ADB7 A069 852C 7C28  A02D 6D89 7EDF 518A 031D
   

   If you see Good signature from "Decred Release <[email protected]>", then you're successful! You can trust that the manifest.txt came directly from the Decred project.

3. Verify that the hash of your downloaded zip/tarball matches the manifest hash:

   • Windows:

     • If you have 7-Zip installed, simply open up Windows Explorer, right click on the file, mouseover CRC SHA, then click SHA-256.

     • $ certutil -hashfile <your file> SHA256

   • macOS

     • $ shasum -a 256 <your file>

   • Linux

     • $ sha256sum <your file>

   Example output:

   9c346bbdb5dbd9671f2ef6731f52c228f5972000960be8dfdc9346f52bab48b2 *dcrinstall-linux-amd64-v1.5.1
   

If your output hash matches the hash from the manifest, you're done! The binary for your platform is now verified and you can be confident it was generated by the Decred Project. It's safe to install the software.

decred-release's Issues

Add promptsecret to install

Once decred/dcrd#649 and decred/decred-binaries#35 are done, dcrinstall should install the new tool.

dcrinstall missing linux-arm

dcrinstall for linux-arm is missing although dcrinstall linux-arm64 is present. The lack of a 32 bit version will exclude the raspberry pi community as Raspbian (the default linux that ships with Raspberry) remains (and will be for the near future) a 32 bit system.

dcrinstall 1.4 did not have this issue.

dcrinstall not working on OS X

Logs shows:
02:08:31.173 user: Current not implemented on darwin/amd64

Googling fot it i found that this is caused by cross compiling: golang/go#6376 (comment)

So dcrinstall for OSX (darwin) should be compiled under OSX, or avoid using user.Current().

dcrinstall-linux-arm-v1.5.0-rc1

Installer fails on freshly installed Raspbian.

decred@raspberrypi:~$ ./dcrinstall-linux-arm-v1.5.0-rc1
21:51:22.971 temporary directory: /tmp/decred002506178
21:51:22.971 downloading manifest: https://github.com/decred/decred-binaries/releases/download/v1.5.0-rc1/decred-v1.5.0-rc1-manifest.txt
21:51:24.716 downloading manifest signatures: https://github.com/decred/decred-binaries/releases/download/v1.5.0-rc1/decred-v1.5.0-rc1-manifest.txt.asc
21:51:26.351 downloading package: https://github.com/decred/decred-binaries/releases/download/v1.5.0-rc1/
21:51:26.767 HTTP error: 404 Not Found
=== dcrinstall complete Monday, 11-Nov-19 21:51:26 GMT ===

dcrinstall on freebsd/amd64 11

On a fresh FreeBSD 11 (zfs) install dcrinstall exits without downloading/installing if run without CLI args:

$ ./dcrinstall-freebsd-amd64-v0.8.2 -verbose
01:43:23.726 exit status 1
=== dcrinstall complete Saturday, 15-Apr-17 01:43:23 UTC ===

$ cat decred/dcrinstaller.log 
01:43:23.726 exit status 1
=== dcrinstall complete Saturday, 15-Apr-17 01:43:23 UTC ===

$ uname -a
FreeBSD freebsd-1gb-fra1-01 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed Feb 22 06:12:04 UTC 2017     [email protected]:/usr/obj/usr/src/sys/GENERIC  amd64

-downloadonly works:

$ ./dcrinstall-freebsd-amd64-v0.8.2 -downloadonly
=== dcrinstall run Saturday, 15-Apr-17 01:45:25 UTC ===
01:45:25.671 temporary directory: /tmp/decred788493824
01:45:25.671 downloading manifest: https://github.com/decred/decred-binaries/releases/download/v0.8.2/manifest-v0.8.2.txt
01:45:27.379 downloading manifest signatures: https://github.com/decred/decred-binaries/releases/download/v0.8.2/manifest-v0.8.2.txt.asc
01:45:28.294 downloading package: https://github.com/decred/decred-binaries/releases/download/v0.8.2/decred-freebsd-amd64-v0.8.2.tar.gz
01:46:00.619 verifying manifest: manifest-v0.8.2.txt OK
01:46:00.640 verifying package: decred-freebsd-amd64-v0.8.2.tar.gz OK
=== dcrinstall complete Saturday, 15-Apr-17 01:46:00 UTC ===

-skip errors out also:

$ ./dcrinstall-freebsd-amd64-v0.8.2 -skip -path /tmp/decred788493824/
01:47:07.154 exit status 1
=== dcrinstall complete Saturday, 15-Apr-17 01:47:07 UTC ===

dcrinstall-freebsd-386-v0.8.2 behaves the same way.

Validate dcrinstall on all OS'

Validate dcrinstall upgrades on the following platforms:

• Linux
• Bitrig
• Windows
• OSX

Validate dcrinstall clean install on the following platforms:

• Linux
• Bitrig
• Windows
• OSX

Remove reference to wiki

Old wiki is going away, don't link to it.

Validate dcrinstall on all OS'

Validate dcrinstall upgrades on the following platforms:

• Linux
• Bitrig
• Windows
• OSX

Validate dcrinstall clean install on the following platforms:

• Linux
• Bitrig
• Windows
• OSX

Remove requires on dcrwallet main module

Packages from the dcrwallet main module are not intended nor versioned for import usage by other Go code and these packages should be avoided. This includes the usage of both the loader and prompt packages.

solaris/illumos

Once decred/dcrwallet#557 goes in this one needs a glide update to get it:

jcv@triforce dcrinstall $ GOOS=solaris GOARCH=amd64 go build
# github.com/decred/decred-release/vendor/github.com/decred/dcrwallet/internal/prompt
../../vendor/github.com/decred/dcrwallet/internal/prompt/prompt.go:54: undefined: terminal.ReadPassword
../../vendor/github.com/decred/dcrwallet/internal/prompt/prompt.go:123: undefined: terminal.ReadPassword
../../vendor/github.com/decred/dcrwallet/internal/prompt/prompt.go:138: undefined: terminal.ReadPassword

Match dcrd -V behavior

see decred/dcrd#583

ambiguous folder name

Similar to closed issue #13, uncompressing the archive
decred-v0.1.2-linux-amd64-20160503-01.tar.gz
just gives you a directory just called
~/linux-amd64/
Better would be any of these
decred-v0.1.2-linux-amd64-20160503-01
decred-v0.1.2-linux-amd64
decred-v0.1.2-linux
decred-v0.1.2
decred

Verification of bins and sourcecode

I don't know if its the correct place for that issue but a slack user was asking about the verification process. His question was about the verification of the binary and the verification of the toolchain binaries that got installed by dcrinstall.

His main request was to be able to verify the sourcecode. Is there a chance we can enable users to verify sourcecode?

Additionaly i will open an issue on dcrdocs as we came to the conclusion that it would make sense to give guides for system hardening in the documentation.

dcrinstall upgrade from 0.8.2 to 1.0.0 fails

Upgrading from 0.8.2 to 1.0.0 fails:

=== dcrinstall run Thursday, 27-Apr-17 15:07:45 CDT ===
15:07:45.891 temporary directory: /tmp/decred686538944
15:07:45.891 downloading manifest: https://github.com/decred/decred-binaries/releases/download/v1.0.0/manifest-v1.0.0.txt
15:07:46.252 downloading manifest signatures: https://github.com/decred/decred-binaries/releases/download/v1.0.0/manifest-v1.0.0.txt.asc
15:07:46.703 downloading package: https://github.com/decred/decred-binaries/releases/download/v1.0.0/decred-linux-amd64-v1.0.0.tar.gz
15:07:51.341 verifying manifest: manifest-v1.0.0.txt OK
15:07:51.348 verifying package: decred-linux-amd64-v1.0.0.tar.gz OK
15:07:51.428 extracting: decred-linux-amd64-v1.0.0.tar.gz -> /home/xxx/decred
15:07:52.049 checking: /home/xxx/decred/decred-linux-amd64-v1.0.0/dcrctl OK
15:07:52.050 checking: /home/xxx/decred/decred-linux-amd64-v1.0.0/dcrd OK
15:07:52.051 checking: /home/xxx/decred/decred-linux-amd64-v1.0.0/dcrwallet OK
15:07:52.053 checking: /home/xxx/decred/decred-linux-amd64-v1.0.0/promptsecret OK
15:07:52.054 current version: /home/xxx/decred/dcrctl dcrctl version 0.8.2-beta
15:07:52.141 current version: /home/xxx/decred/dcrd dcrd version 0.8.2-beta
15:07:52.179 current version: /home/xxx/decred/dcrwallet dcrwallet version 0.8.2-beta
15:07:52.222 current version: /home/xxx/decred/promptsecret NOT INSTALLED
15:07:52.224 --- Unknown state, manual intervention ---required
15:07:52.224 dcrctl.conf dcrd.conf already exists
=== dcrinstall complete Thursday, 27-Apr-17 15:07:52 CDT ===

Make proxy persistent for all daemons.

When the user uses the HTTP_PROXY environment variable to install the various daemons we should assume that all daemons should be proxied as well. Add the proxy to bitcoind/dcrd/dexc config files.

Validate v1.0.3

Validate dcrinstall upgrades on the following platforms:

• Linux
• Windows
• OSX

Validate dcrinstall clean install on the following platforms:

• Linux
• Windows
• OSX

Please comment with what you tested. Multiple linuxes are always welcome.

Decredliton 1.4.0

Hello, help please, please, five days can not install the wallet, my version 1.3 worked well, wanted to update, see what happened, I ask You to help. Thanks.
[ERR] DCRD: metadata claims file 5, offset 482740795, but block data is at file 0, offset 0
2019-03-30 13:00:20.359 [INF] DCRD: Shutdown complete

internal/process/warning.js:18 (node:14716) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

Add LICENSE file

https://help.github.com/articles/open-source-licensing/#what-happens-if-i-dont-choose-a-license

warnings about sample-dcrd.conf and promptsecret

dcrd.conf is now generated on first run and sample-dcrd.conf was removed.

Also, the installer would falsely print that promptsecret is not installed because it does not support the --version flag.

signature mismatch

Hi

I'm installing the dcrd using the dcrdinstall and there is an issue with signature.

So the steps are:

$ wget https://github.com/decred/decred-release/releases/download/v1.1.0/dcrinstall-linux-amd64-v1.1.0

$ wget https://github.com/decred/decred-release/releases/download/v1.1.0/manifest-dcrinstall-v1.1.0.txt.asc

$ wget https://github.com/decred/decred-release/releases/download/v1.1.0/manifest-dcrinstall-v1.1.0.txt

$ sha256sum dcrinstall-linux-amd64-v1.1.0

35a35a7726a984c11c42d34fe3474852e60679bc0adc2bc416cc468b027c9d7f  dcrinstall-linux-amd64-v1.1.0

$  gpg --keyserver pgp.mit.edu --recv-keys 0x6D897EDF518A031D

gpg: requesting key 518A031D from hkp server pgp.mit.edu
gpg: key 7608AF04: "Decred Release <[email protected]>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

and finally

gpg --verify manifest-dcrinstall-v1.1.0.txt.asc

gpg: assuming signed data in 'manifest-dcrinstall-v1.1.0.txt'
gpg: Signature made Fri 22 Sep 2017 07:48:47 PM UTC using RSA key ID 518A031D
gpg: Good signature from "Decred Release <[email protected]>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: FD13 B683 5E24 8FAF 4BD1  838D 6DF6 34AA 7608 AF04
     Subkey fingerprint: F516 ADB7 A069 852C 7C28  A02D 6D89 7EDF 518A 031D

So first the issue with the This key is not certified with a trusted signature!
Second is how do I check the signature against the SHA256 above?

Unable to set up dcrinstall-linux-arm-v1.2.0 on Raspberry pi 3 (Raspbian)

Hello,

Please bear with me as I am very new to this process.

I am currently trying to set up dcrinstall-linux-arm-v1.2.0 on Raspberry pi 3 (Raspbian).

When I try and make this file executable on the terminal program, by running
cd ~/Downloads/, then:
chmod u+x dcrinstall-linux-arm-v1.2.0

I get an error saying
"chmod: cannot access 'dcrinstall-linux-arm-v1.2.0': No such file or directory

What am I missing?

dcrinstall ignore argument -path

execute dcrinstall -path /home/foo/download_path , dcrinstall output log:

11:10:24.932 temporary directory: /tmp/decred155921598
11:10:24.932 downloading manifest: https://github.com/decred/decred-binaries/releases/download/v1.5.0/decred-v1.5.0-manifest.txt

temporary directory: /tmp/decred155921598
ignore argument -path

have project name in the file name

instead of
linux-amd64-20160318-01.tar.gz
have
decred-v0.1.0-linux-amd64-20160318-01.tar.gz
or even just
decred-v0.1.0-linux-amd64.tar.gz

dcrinstall incorrectly checks process environment variables for running processes

$ ./dcrinstall-openbsd-amd64-v1.5.1                                                                                          
=== dcrinstall run Saturday, 15-Feb-20 14:26:50 EST ===
14:26:50.821 dcrwallet is still running
=== dcrinstall complete Saturday, 15-Feb-20 14:26:50 EST ===

dcrwallet is not running, and does not appear anywhere in ps auxww output.

Tested with the released v1.5.1 binary, as well as building dcrinstall from source.

Implement downloadonly flag

Track #64 and #48

error when run ./dcrinstall-linux-amd64-v1.1.2

root@ubuntu:/home/snack/gocode/src/github.com/decred# ./dcrinstall-linux-amd64-v1.1.2
=== dcrinstall run Sunday, 04-Mar-18 05:56:59 PST ===
05:56:59.783 temporary directory: /tmp/decred895285910
05:56:59.784 downloading manifest: https://github.com/decred/decred-binaries/releases/download/v1.1.2/manifest-v1.1.2.txt
05:57:24.310 Get https://github-production-release-asset-2e65be.s3.amazonaws.com/61043514/98b6d46e-e0e9-11e7-852f-1b6405de37e1?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20180304%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20180304T135703Z&X-Amz-Expires=300&X-Amz-Signature=cb1accfe96bd1542792833827d1195121d1f3e9b881a8cba086e91f5c13b0d19&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dmanifest-v1.1.2.txt&response-content-type=application%2Foctet-stream: dial tcp 52.216.128.107:443: getsockopt: connection refused
=== dcrinstall complete Sunday, 04-Mar-18 05:57:24 PST ===

I have done the verification of dcrinstall.

Validate 0.8.0 release

Validate dcrinstall upgrades on the following platforms:

• Linux
• Bitrig
• Windows
• OSX

Validate dcrinstall clean install on the following platforms:

• Linux
• Bitrig
• Windows
• OSX

Automatic Wallet Creation Conditional

Currently, if none of the .conf files exist AND a wallet.db doesn't already exist, then --create is started. Why not only check for ../dcrwallet/mainnet/wallet.db?

Verify all OS'

Verify that dcrinstall works on thre following OS':

• OpenBSD/Bitrig
• Linux
• OSX
• Windows

Make sure dcrd, dcrctl, dcrwallet and dcrticketbuyer work. Click on check box once verified.

Additionally check:

• Windows gominer
• Linux gominer

-net testnet creates wallet for old testnet, not testnet2

On linux, amd64 (ubuntu 14.04), when running dcrinstall-linux-amd64-v1.0.1 with option -net testnet, the wallet.db is created inside folder ~/.dcrwallet/testnet, instead of ~/.dcrwallet/testnet2. Then when i try to run the wallet it displays the error message:
The wallet does not exist. Run with the --create option to initialize and create it.

missing sample-dcrctl.conf file

dcrinstall version 1.5.0+dev

when run dcrinstall in VPS first time,

dcrinstall print log:open /home/foo/decred/decred-linux-amd64-v1.5.0-rc1/sample-dcrctl.conf: no such file or directory

Asst trans

v1.4.0-rc3

RPCS: Configuration: No payment addresses specified via --miningaddr

when i use yiimp pool connect dcrdwallet, dcrd make error: RPCS: Configuration: No payment addresses specified via --miningaddr
Has the dcrdwallet version changed ? or command "getwork" changed ? thanks for your answer

dcrinstall: Avoid unnecessary redownloads

Currently when dcrinstall is re-run using a different random temporary directory, all archives to be installed must be redownloaded. It would be optimal if an old archive could be found on disk, checked against the manifest, and avoid redownloading it if it matches, or avoid downloading when the extracted archive directory already exists.

sample-dcrd.conf needs to be generated

It was removed as a standalone file so now it needs to be generated.

A problem with dcrinstall-linux-arm64-v1.1.2

I've Downloaded dcrinstall-linux-arm64-v1.1.2, verified the manifest and the sha256sum.
Then i made it an executable and ran ./dcrinstall-linux-arm64-v1.1.2
which gave me the following error message:

bash: ./dcrinstall-linux-arm64-v1.1.2: cannot execute binary file: Exec format error

when i ran sudo ./dcrinstall-linux-arm64-v1.1.2 the error message ran:

./dcrinstall-linux-arm64-v1.1.2: 1: ./dcrinstall-linux-arm64-v1.1.2: Syntax error: ")" unexpected

I'm doing this an a Raspberry pi 3.

When i proceeded by trying to install the 32-bit version, it worked flawlessly

Request: Add VERSION file

It would be nice to have a VERSION file in the release master branch that includes the current releases info. I was thinking a json file that includes version, date and build number something like:

{
"decred": {
"version": "0.1.2",
"build": "01",
"date": "2016-05-03"
},
"paymetheus": {
"version": "0.0.8"
},
"miners": {
"version": "0.1.0"
}
}

This would provide all the info needed to create automated tools to check for and update the different software being released.

Validate upgrade from prior version.

Validate dcrinstall upgrades on the following platforms:

• Linux
• Windows
• OSX

Validate dcrinstall clean install on the following platforms:

• Linux
• Windows
• OSX

glide.lock is not up to date with the latest release

proxy support

Someone in #decred was asking for this.

Test plan

Currently, on a new release I open up issues in 3 repos (decred/decred-release, decred/Paymetheus, and decred/decrediton) with some details for testing.

What we should do is write up a test plan for each relevant part (cli, Paymetheus, decrediton, copay) that a tester can run through before each release. It would be great to really script it, but for first step just a list of things for a user to do would be great.

What I envision is something like this for the tester to fill in:

---

CLI testing

User: jcv
OS: Debian testing
Date: 08/01/2017

Fresh install

• run dcrinstall
• test something
• test something else

Upgrade

• install previous version
• run dcrinstall
• test this
• test that

---

And so on (with a separate plan for the the guis and maybe webwallet or any other parts we want).

This would greatly help catch bugs before release.

Need Chinese LANG

I Need support Chinese language in wallet.

Unable to connect the dcrd's RPC server form another machine

hi,
I have used two methods to connect the RPC server:
1.edit the dcrd.conf , use the RPC user and password; add RPC port 0.0.0.0:9109
2.start dcrd with the RPC info, like
./dcrd --rpcuser=xxxxx --rpcpass=xxxxx --rpclisten=0.0.0.0:9109

I can't use dcr mining pool to connect it form another machine .
I am sure that port is Available。

Thanks for your help！

OSX

I assume dcrinstall-darwin-amd64-v0.5.1 is for OSX but I cannot open or run that.

Unable to connect the dcrdRPC server from another machine .

hi,
I have used two methods to connect the RPC server

dcrticketbuyer missing from darwin release?

I've downloaded and installed, but I'm left without the dcrticketbuyer binary. Is that now available in a separate package?

± % ./dcrinstall-darwin-386-v0.8.2                                                         !4444
=== dcrinstall run Thursday, 16-Mar-17 14:11:18 CET ===
14:11:18.417 temporary directory: /var/folders/pq/q7pxn3ts67782l3pyfsdgqv00000gn/T/decred086065813
14:11:18.418 downloading manifest: https://github.com/decred/decred-binaries/releases/download/v0.8.2/manifest-v0.8.2.txt
14:11:24.767 downloading manifest signatures: https://github.com/decred/decred-binaries/releases/download/v0.8.2/manifest-v0.8.2.txt.asc
14:11:26.788 downloading package: https://github.com/decred/decred-binaries/releases/download/v0.8.2/decred-darwin-386-v0.8.2.tar.gz
14:11:57.289 verifying manifest: manifest-v0.8.2.txt OK
14:11:57.304 verifying package: decred-darwin-386-v0.8.2.tar.gz OK
14:11:57.422 extracting: decred-darwin-386-v0.8.2.tar.gz -> /Users/dan/decred
14:11:58.110 checking: /Users/dan/decred/decred-darwin-386-v0.8.2/dcrctl OK
14:11:58.112 checking: /Users/dan/decred/decred-darwin-386-v0.8.2/dcrd OK
14:11:58.114 checking: /Users/dan/decred/decred-darwin-386-v0.8.2/dcrwallet OK
14:11:58.117 current version: /Users/dan/decred/dcrctl dcrctl version 0.8.2-beta
14:11:58.202 current version: /Users/dan/decred/dcrd dcrd version 0.8.2-beta
14:11:58.293 current version: /Users/dan/decred/dcrwallet dcrwallet version 0.8.2-beta
14:11:58.405 --- Performing upgrade ---
14:11:58.405 installing: /Users/dan/decred/decred-darwin-386-v0.8.2/dcrctl -> /Users/dan/decred
14:11:58.438 installing: /Users/dan/decred/decred-darwin-386-v0.8.2/dcrd -> /Users/dan/decred
14:11:58.493 installing: /Users/dan/decred/decred-darwin-386-v0.8.2/dcrwallet -> /Users/dan/decred
=== dcrinstall complete Thursday, 16-Mar-17 14:11:58 CET ===

~/decred

total 96376
-rwxrwxr-x  1 dan  staff    10M Feb 15 20:54 dcrctl
-rwxrwxr-x  1 dan  staff    17M Feb 15 20:54 dcrd
-rw-r--r--@ 1 dan  staff    52B Mar 16 09:24 dcrd.conf
-rw-------  1 dan  staff   4.0K Mar 16 14:11 dcrinstaller.log
-rwxrwxr-x  1 dan  staff    20M Feb 15 20:54 dcrwallet
-rw-r--r--@ 1 dan  staff   164B Mar 16 13:45 dcrwallet.conf
drwxrwxr-x  8 dan  staff   272B Feb 15 20:54 decred-darwin-386-v0.8.2

dcrinstall fails because promptsecret has no config

function "exists" checks if all the binaries have configs or none has, but there is no config for "promptsecret", so it always fails on updates.

Remove standalone ticketbuyer

Standalone ticketbuyer has been superseded by builtin buyer in wallet. No need to install.

Please sign macOS binaries

Affected version 1.4.0.

Currently there is a "unidentified developer" warning. This is an unacceptable shortcoming for applications that involve physical health or monetary value.

validate v1.0.5

Need fresh install and upgrade

• windows
• linux
• osx