Iperf3 static binaries linux - windows - docker via reusable workflows.

[userdocs]

https://github.com/userdocs/iperf3-static

I have updated this project to be a pretty complete solution to providing builds with a verifiable chain of custody. It does these main things.

Builds:

• Linux fully static muls based binaries and creates a proper multiarch docker for amd64 arm32v6 arm32v7 arm64v8 i386 ppc64le riscv64 s390x
  • Docker images - https://github.com/userdocs/iperf3-static/pkgs/container/iperf3-static
• Windows staticish cygwin based exes with and without openssl. See note
• Macos amd64 macos-13 intel and macos-14 arm64 staticish binaries linked with openssl. See note

Windows and macos tested to work - https://github.com/userdocs/iperf3-static/actions/runs/11410638485

Note

Windows and MacOS binaries are not fully static in terms of their dependency and cygwin1.dll (Windows) libSystem.B.dylib (MasOS).
They are statically linked with libcrypo.a libssl.a (openssl) and iperf3.a (iperf3) so there should be no other system dependency required to run them on the target hosts.

On Windows openssl is built from Github source to get static libs and on MacOS we get them from the brew cellar installation of openssl@3

Releases

https://github.com/userdocs/iperf3-static/releases/tag/3.17.1%2B

Workflows

A dynamic reusable workflow setup to automate new builds via a schedule, set defaults via hardcoded settings and to also be able to configure the workflow on demand to build what you need.

Easily build via custom sources for patches and branches to test stuff.

Features

Using GitHub actions and workflows, binaries are verified using GitHub attestation and VirusTotal scanning, at build time, so that you can be certain the release assets you are using were transparently built from the source code.

Using artifact attestations to establish provenance for builds

https://docs.github.com/en/actions/security-for-github-actions/using-artifact-attestations/using-artifact-attestations-to-establish-provenance-for-builds

Virus total scanning

https://github.com/marketplace/actions/virustotal-github-action

Conclusion

This is the most complete third party build solution for iperf3.

All binaries are attested and virus scanned during the build process so there is full chain of custody.

It can be forked and used on demand. Only needs the virus total api key as a secret.