Aquesta és una versió anterior. La versió actual és la 1.12.1. npiperelay 1.12.1 · Data de publicació:
Fitxers d’instal·lació 1.10.0
| Arquitectura | Tipus | Àmbit | Mida del fitxer | Baixa | SHA256 |
|---|---|---|---|---|---|
| 64 bits | ZIP → Portable | — | — | github.com | VirusTotal |
| 32 bits | ZIP → Portable | — | — | github.com | VirusTotal |
L’enllaç i l’SHA256 provenen del manifest comunitari del Gestor de paquets del Windows. Convé comparar el hash del fitxer baixat abans d’executar-lo.
Notes de la versió
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.26.0.
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:
51b5c26ac7ce5b494dff6b75960eb895b8bd9c5f8bb40db40e512c6f42144c5b npiperelay_windows_386.exe
dbc640749cebc2abebfd95114b22e82d4b2b6d0873875c04f526443372075f89 npiperelay_windows_386.zip
55d6900a174f91b55c7132c909af641eefdefb410cdc65f8bb0a57705d84f841 npiperelay_windows_amd64.exe
81af7bcdafc53ed80f6e8977f447e66008f3eed65a66ea55bcb83ae405087fff 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:
- 23d6c10 Fix GoReleaser deprecated properties
- d77bf2f Bump go version to build with 1.26 while still supporting 1.25
- b5beca7 Bump golang.org/x/sys from 0.40.0 to 0.41.0
(Application executable in release assets built with Go version 1.26.0).https://github.com/albertony/npiperelay/releases/tag/v1.10.0