v1.9.2
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.25.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
GitHub automatically computes SHA-256 checksums for all release assets, which you can see to the right of the asset names in the "Assets" section below. These are generated at upload time and are immutable. The build system also computes SHA-256 checksums of built executables, and these 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:
5c8f8afe0e3307cbd0442ff828fdfdf487938927069e54d7b69194d1af7ee2db npiperelay_windows_386.exe
ea8d1df3dd20c92a4b20496f048221e92468d76fed87f1c426fee99ac8e5f410 npiperelay_windows_386.zip
0be2e7df371ad7207fb9d804d302128ca35c5bd75eace8330eb2bbe294902d87 npiperelay_windows_amd64.exe
e33c7f166b633cc0019c461da43245bf74ca454bd56f5aaf09514bbadd76efb5 npiperelay_windows_amd64.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 vulnerability analysis, using Go's govulncheck and GitHub's CodeQL, 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:
- 02567b7 Bump golang.org/x/sys from 0.38.0 to 0.39.0
- 42ce80a Bump actions/checkout from 5 to 6
- a2d6af3 Bump golangci/golangci-lint-action from 8 to 9
- 60cb164 Bump golang.org/x/sys from 0.37.0 to 0.38.0
- bd85194 Bump github/codeql-action from 3 to 4
(Application executable in release assets built with Go version 1.25.5).