Skip to content

v0.1.42

Choose a tag to compare

@github-actions github-actions released this 11 Nov 17:41
· 90 commits to main since this release
d787fbe

What this is

The open build of the Crossfyre toolchain, compiled by GitHub
Actions from this tag. Engines and templates are Apache-2.0.

What this is not

This is not the binary get.crossfyre.io installs. The repo is
open-core: three things are absent from any public checkout, and
one feature that is in it is not turned on here.

not in this build effect on this build
plessor/src/authz/private.rs no BOLA/BFLA/BOPLA authorization oracle
core/src/egress/private.rs no per-node egress isolation
adaptive-private/ untuned pacing, not the shipped governor
the impersonate feature the engines use rustls, not a browser's TLS and HTTP/2 fingerprint

build.rs selects the baseline.rs stubs instead. The distributed
binary includes the real implementations and cannot be reproduced
from this source. That difference is the point of publishing this
separately rather than pretending the two are the same artifact.

This release also carries a standalone oast binary, the
out-of-band interaction server. The first-party CLI runs the same
server as crossfyre oast serve.

Platforms

archive runs on
crossfyre-toolchain-x86_64-unknown-linux-gnu.tar.gz Linux on x86-64, glibc 2.36 or later
crossfyre-toolchain-aarch64-unknown-linux-gnu.tar.gz Linux on 64-bit ARM, glibc 2.36 or later
crossfyre-toolchain-x86_64-apple-darwin.tar.gz macOS 11 or later on Intel
crossfyre-toolchain-aarch64-apple-darwin.tar.gz macOS 11 or later on Apple silicon
crossfyre-toolchain-x86_64-pc-windows-msvc.zip Windows 10 or later on x86-64

The macOS binaries are signed ad hoc, not with a Developer ID, so a
copy downloaded with a browser is quarantined and Gatekeeper refuses
to open it. Clear that once the checks below pass:
xattr -d com.apple.quarantine <file>. One fetched with curl is not
quarantined. cfx-script needs a Python; everything else starts without
one. On Linux the archive carries CPython 3.13 from python-build-standalone
in a python folder beside it, which it loads and no other, so it starts
whatever Python the host has or lacks; keep the folder beside the binary
when you move it. THIRD-PARTY-NOTICES-PYTHON.txt holds the licences of
that CPython and what it compiles in. On macOS it loads CPython 3.10 or
later from python.org's framework or Homebrew's. On Windows the zip
carries python.org's embeddable Python in a python folder beside it,
which it loads first.

Verifying it

Provenance is attested, so you do not have to take our word for where
these came from:

gh attestation verify crossfyre-toolchain-x86_64-unknown-linux-gnu.tar.gz \
  --repo clickswave/crossfyre-toolchain
sha256sum -c SHA256SUMS

On macOS, shasum -a 256 -c SHA256SUMS. In PowerShell,
(Get-FileHash crossfyre-toolchain-x86_64-pc-windows-msvc.zip).Hash
prints the sum to compare with the line in SHA256SUMS.

Or skip us entirely: clone the tag and cargo build --release.