Releases: albertony/npiperelay
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).
v1.4.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.20.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
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:
1c4a2d8ec907fb1c1bdd5b3d55976b9f640db02d58983cf50553b8b85d3c93b8 npiperelay_windows_amd64.zip
5230cc7de34b20469235521d81225478ac2a90c0cfac7381e3e04a1470d98302 npiperelay_windows_386.zip
538168f3b9410c5e1f32dcc2772822a9094520e8265c4c6b6684e3ccc2ef649a npiperelay_windows_amd64.exe
7296e9d39ba31201273deb013b12d834d59de278afaef590bdf3791befb7f08f 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.
Changelog
Commits since previous fork release:
- 027deaf Bump golang.org/x/sys from 0.5.0 to 0.6.0
(Application executable in release assets built with Go version 1.20.2).
v1.4.1
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.
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.
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.
v1.4.0
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.
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.
641ac4ded537c15d6e9fea5b8533fc6bd86978c7eedc931ee16b826cb56c3719 npiperelay_windows_amd64.zip
69a4dbba5a8561c7dc09ca6ff1217c96e3c85d808d7189d0cdf0e2a48e6b9bbb npiperelay_windows_386.exe
a560a9710411ea69a442c60d7a6c4cd77fb18adfadcd25e920a398f235621f0a npiperelay_windows_amd64.exe
f6f846c6f082d08a0e27f814ff90c5110b005ad53c9a4bf2a3315bcb011fb0c0 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.
VirusTotal scan reports for release assets:
- Asset download URLs:
- Asset files:
v1.3.4
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.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
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.
1c0a6a42b382b23b832373d9708cfbcaa1a3aa838b8a5d7a5d10b690b66abf82 npiperelay_windows_amd64.exe
3f06b7958fe5691d89f29c5cd1c580f4e2fab0ceed9c5c1dcd69f079a4bec813 npiperelay_windows_amd64.zip
433f7bd8f413d98132e167ebc4bda1c5581c444b26936a198b92016b2905a570 npiperelay_windows_386.exe
5ea47f08a57964186b8ab492f1b53ad36cd086380953a1d36ef8f28b7fd6fde5 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.
VirusTotal scan reports for release assets:
- Asset download URLs:
- Asset files:
v1.3.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.19.4.
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.
6e94702d70eef7d868b7dc036176c05f0b6a77d2f4deea194a7c70778bd5b056 npiperelay_windows_amd64.zip
b4e3e6a83a236c47696e65c1983511f6d5ca3a118b10b15821cf89e19d62bafa npiperelay_windows_amd64.exe
b82afd48089d0cef37e470e4d407e1bd2c6df2b313791da517d5f0373e0dd726 npiperelay_windows_386.zip
ce0382cd69742970f4a1632094b0c93b95a15f05cd49182da30933a13f9dcf78 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:
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:
v1.3.1
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.1.
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 the 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.
64ac64f2a79488dda89f05a6dd7568b938fe5f3b6774cbeea126eb91c82066eb npiperelay_windows_amd64.zip
740162b69042027a4ddf492fe4bdfeb4b028e03763c0d917dd6a1b8ea53e1639 npiperelay_windows_386.zip
c5d43e92733e908344b5ad9b7c7cf8d92fc8afa7196ab365e451afd515f80cef npiperelay_windows_amd64.exe
d16b21c67da350bf740fa4b9a67dae127435f830934322b462eb87c2baf7cca3 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, and it is automatically run through a long list of external 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:
- b5c82bd Add linting (code quality test) to github workflow
- 343bc5b Add template for release notes to GoReleaser, and automatically publish as draft release only
- 5ab1c76 Improved error handling
- d22b36f Improvements to the GoReleaser release notes template
- bc8d1d5 Make GoReleaser automatically include checksums of npiperelay.exe
- 3d6d132 Make GoReleaser publish raw binaries (.exe) in addition to the original archived format
- 257a982 Update sys package dependency to latest version (Sep 8, 2022)
- 88b1c28 Update vendoring (go mod vendor)
v1.3.0
Release of the forked project, containing some improvements on top of upstream release v0.1.0. See release notes for the first release, v1.0.0, for background. The only change from previous fork release (v1.2.2) to this release (v1.3.0) is update to latest version of go (v1.19.0) and latest version of the sys package dependency. Full changelog listing all commits further down.
Checksums (SHA-256):
- 386/x86/32-bit:
- npiperelay_windows_386.zip:
4452eaaa2c6fb3e6f80708c548aad8252528c16a077928396545ba3f2b1ac0cf - npiperelay.exe:
c08142275523d2a0ad7cfa6ecd82bf7b3e90d171dad9244867da4565b859e18b
- npiperelay_windows_386.zip:
- amd64/x64/64-bit:
- npiperelay_windows_amd64.zip:
82bbf942e9be9eebe01131ccd2f1732e53b91830a2f29f54eb8d0703b8e1e93b - npiperelay.exe:
157b9e2d83a5d6091f7c15eee1099fd896cb1a58b3978b3feaa5611cba85724b
- npiperelay_windows_amd64.zip:
VirusTotal scan results:
- 386/x86/32-bit:
- amd64/x64/64-bit
At the time of the release, no security vendors flag the zip download urls as malicious, but some flag the extracted executable as malicious. If this worries you, you can always check for yourself by reading through the less than 300 lines of go code, plus the single, commonly used, third party dependency, and then build from source. If your local antivirus flag the executable, you should try to report it as a false positive, e.g. for Symantec at https://symsubmit.symantec.com.
Changelog
v1.2.2
Release of the forked project, containing some improvements on top of upstream release v0.1.0. See release notes for the first release, v1.0.0, for background. The only change from previous fork release (v1.2.1) to this release (v1.2.2) is update to latest version of go (v1.18.4) and latest version of the sys package dependency. Full changelog listing all commits further down.
Checksums (SHA-256):
- 386/x86/32-bit:
- npiperelay_windows_386.zip:
c474c9f20560183714ebf134f16b2fc06cd2bb8ed2189798911442888e936634 - npiperelay.exe:
a2fb4f717a9f59c20feef2146ab000e6ae6b5a2044a4a85650ab1083847d0e18
- npiperelay_windows_386.zip:
- amd64/x64/64-bit:
- npiperelay_windows_amd64.zip:
1b78febf71ec847de70a70242c92396fb0eb380baae33ae47ef376a266a13f92 - npiperelay.exe:
f705d4d4fd22ccc70f98da9e351623129feea41a114b01af0be450ece4342be8
- npiperelay_windows_amd64.zip:
VirusTotal scan results:
- 386/x86/32-bit:
- amd64/x64/64-bit
At the time of the release, no security vendors flag the zip download urls as malicious, but some flag the extracted executable as malicious. If this worries you, you can always check for yourself by reading through the less than 300 lines of go code, plus the single, commonly used, third party dependency, and then build from source. If your local antivirus flag the executable, you should try to report it as a false positive, e.g. for Symantec at https://symsubmit.symantec.com.