v1.4.3
This is a release of my forked project, from branch fork. See below for full changelog, listing all commits since previous fork release. The primary asset of the release is a direct download link for a ready-to-use build of the application's single executable, as well as an alternative .zip archive containing the same executable. It is built with Go version 1.20.5.
About this fork
This release is from my fork of jstarks/npiperelay, adding some smaller improvements on top of upstream release v0.1.0. The changes are conservative; primary concern is to keep the code updated and secure, considering upstream has not been updated since this first release back in mid 2020. See previous release notes for fork releases starting with v1.0.0 to learn about all changes.
Checksums
The SHA-256 checksums of the binary release assets are published as text file asset npiperelay_checksums.txt
. Note that the .zip asset for the amd64 (x64/64-bit) and 386 (x86/32-bit) architectures both contain a single executable with name npiperelay.exe
, and it is identical to the .exe asset with same name as the .zip asset, i.e. npiperelay_windows_386.exe
and npiperelay_windows_amd64.exe
, and should therefore have the same checksum.
These are the SHA-256 checksums of all binary release assets, as published in npiperelay_checksums.txt
:
30008d126c92fd22c25887a8a44ee86f76bfa2308570da199b4e2c60eaecb875 npiperelay_windows_amd64.zip
7f45dd065ecaced0e4c79f24bc7d95ed0155f72ecc480174b6ece66886ac798b npiperelay_windows_amd64.exe
85396b217dfbaed96293270d5b9137040bbb6f2da0f6d8e311e41749663d025e npiperelay_windows_386.exe
dd5417a63aed2945d642163ce13ddbe94c42a149fe3b8a808bfb11fbe4c21bcd npiperelay_windows_386.zip
Antivirus
If your local antivirus treats the downloaded archive or executable as suspicious or malicious, you should try to report it as a false positive, e.g. to Symantec on symsubmit.symantec.com (select "Clean software incorrectly detected"). At the time of the release, no security vendors on VirusTotal flagged the asset download urls as malicious, but some very few (well below 10%) did flag the zip archive and executable files themselves (see report for each of the assets in expandable section below). The implementation is less than 300 lines of go code, plus a single, commonly used, third party dependency. The source code is automatically run through a vulnerability analysis, using govulncheck, and a long list of code quality checks (linters), using golangci-lint (see .golangci.yml for the complete list). If you do worry, you are free to analyse the code yourself, and you can also build the executable locally from source.
Changelog
Commits since previous fork release:
- f06828c Disable caching of go modules and build output in setup-go
- b893a6b Bump golang.org/x/sys from 0.6.0 to 0.8.0
- fd97558 Bump actions/setup-go from 3 to 4
- 635d4f9 Run checkout before setup go in github workflow to support caching
- 43327f7 Increase timeout of linting in github workflow
(Application executable in release assets built with Go version 1.20.5).