JA3Proxy: download ældre versioner

Highlights
- Serve HTTP, HTTPS, and SOCKS5 clients on the same listen address. SOCKS5 TLS streams use the MITM/uTLS path, while non-TLS streams are forwarded as plain TCP.
- Select outbound uTLS fingerprints globally or by upstream host with the new fingerprint catalog, hot-reloadable configuration, and --tls-profile-file routes.
- Monitor active and recent traffic with the optional --tui dashboard, structured log levels, and opt-in payload dumping.
- Reorganize runtime code into focused internal packages and expand unit and end-to-end coverage.
- Build Linux, Windows, and macOS archives for AMD64 and ARM64 with SHA-256 checksums. Stable releases also publish multi-platform GHCR images with SBOM and provenance attestations.
Breaking CLI changes
The runtime flags have been renamed:
- -addr and -port → --listen
- -cert and -key → --ca-cert and --ca-key
- -client, -version, and -fingerprint → --tls-fingerprint
- -fingerprint-config → --tls-fingerprint-file
- -upstream-tls-config → --tls-profile-file
- -upstream → --upstream-proxy
- -list-fingerprints → --list-tls-fingerprints
- -debug → --log-level debug; use --dump-traffic to log payload data
Go 1.26.5 or newer is required when building from source.
Full Changelog: https://github.com/LyleMi/ja3proxy/compare/v0.5.1...v0.6.0

What's Changed
Features
- Added hot-reloadable TLS fingerprint configuration via -fingerprint-config.
- Supports loading client and version from a JSON file.
- New HTTPS CONNECT connections use the latest loaded fingerprint.
- Existing tunnels continue using the fingerprint they were opened with.
- Fixed CONNECT response handling for clients such as ffprobe.
- Aligned ALPN behavior between client-side and upstream TLS connections.
- Avoided mutating Go's default HTTP transport.
- Passed HTTP transport traffic through the configured upstream dialer.
Improvements
- Added SOCKS5 upstream proxy handling improvements.
- Moved CLI source into cmd/ja3proxy.
- Changed default generated CA paths to:
- credentials/cert.pem
- credentials/key.pem
- Updated Docker runtime paths and Docker context ignores.
- Updated Makefile output paths so release binaries are written under bin/.
- Expanded README with usage, Docker, certificate, fingerprint, and development docs.
Testing
- Added end-to-end proxy tests.
- Added JA3 fingerprint verification coverage.
- Added unit tests for proxy handlers, MITM CONNECT flow, upstream dialer construction, custom TLS wrapping, certificate handling, debug writer behavior, and
edge cases.
Dependencies and CI
- Updated github.com/refraction-networking/utls from v1.6.7 to v1.8.2.
- Updated github.com/cloudflare/cfssl from v1.6.4 to v1.6.5.
- Updated golang.org/x/net from v0.23.0 to v0.38.0.
- Updated GitHub Actions dependencies:
- actions/checkout to v6
- actions/setup-go to v6
- docker-build-push action to v7
- Added Dependabot configuration for Go modules and GitHub Actions.
Upgrade Notes
The default certificate files are now stored under credentials/ instead of the repository root. If you previously relied on cert.pem and key.pem in the
current directory, either move them to credentials/cert.pem and credentials/key.pem, or pass explicit paths with -cert and -key.
Full Changelog
https://github.com/LyleMi/ja3proxy/compare/v0.4...v0.5.1

What's Changed
- Added newer version of dependencies (e.g. utls) for new browsers compatibility by @antoniolch in https://github.com/LyleMi/ja3proxy/pull/17
New Contributors
- @antoniolch made their first contribution in https://github.com/LyleMi/ja3proxy/pull/17
Full Changelog: https://github.com/LyleMi/ja3proxy/compare/v0.3...v0.4

What's Changed
- Load certificate at startup by @rosahaj in #9
- fix: reply with sni-specific certs by @rosahaj in #11
- fix: stop goroutine leaks by ensuring both goroutines exit properly by @huboh in #14
New Contributors
- @huboh made their first contribution in #14
Full Changelog: https://github.com/LyleMi/ja3proxy/compare/v0.2...v0.3