v1.3.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.19.2.
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
Below are the SHA-256 checksums of release assets, the same that you can find in 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 same checksums.
1b0095ca75e17ba6a12b19fd7227598b46c3b19a19eaa621f8d378c703ba1467 npiperelay_windows_386.zip
22f2d64ce31be0661f3a82285ef572fa41868adb2a3a93795cbc75a7abcf287c npiperelay_windows_amd64.exe
d07255bf758bcc6743dac58e265fbdd2b8e1e8da12b5c965803ff916eec815d9 npiperelay_windows_amd64.zip
e5aaa4adcb858763745b356d9f69390426fa38aff509dc9afc5afde8367217f0 npiperelay_windows_386.exe
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.
VirusTotal scan reports for release assets:
- Asset download URLs:
- Asset files:
Changelog
Commits since previous fork release: