bouine

Repository on GitHub, which uses git. git is distributed.

bouine supports secure protocols for all network communications, with insecure protocols disabled by default:

• Data plane: HTTP/1.1 and HTTP/2 over TLS (HTTPS). Minimum TLS version is 1.2 ( tls.Config{MinVersion: tls.VersionTLS12} in listener.go:143 ), configurable to 1.3. Plaintext HTTP (h2c) is available only via explicit configuration for in-mesh traffic; the default Helm chart enables TLS.
• Cluster (peer-to-peer): mTLS required for all gossip and peer-fetch traffic. Separate CA from the data plane. No plaintext cluster communication is supported.
• Origin (upstream): TLS verification enabled by default ( insecure_skip_verify refused in release builds). Optional mTLS for client cert authentication.
• Admin API: Separate port, bearer token or mTLS authentication. The Helm chart binds it to cluster-internal only by default (not exposed to the Internet).
• Insecure protocols disabled by default: SSLv3 and earlier are not supported (Go's crypto/tls minimum is TLS 1.0, but bouine sets the minimum to 1.2). FTP, telnet, SSHv1 are not used. insecure_skip_verify is refused in release builds. The admin API rejects insecure HTTP for write methods.

bouine requires at least TLS 1.2 on all TLS surfaces.

The HTTPS listener sets tls.Config{MinVersion: tls.VersionTLS12} by default ( internal/server/listener.go:143 ). The minimum version is configurable via tls.min_version in the config ( internal/config/config.go:101 ), but the default and minimum supported value is 1.2. Cluster mTLS and origin TLS also inherit Go's secure defaults with TLS 1.2 as the floor. The test utility (internal/testutil/tlsutil/tlsutil.go:92 ) explicitly asserts MinVersion >= tls.VersionTLS12 .

Multiple dynamic analysis tools are applied:

• Go race detector ( -race ) — runs on every CI push and pre-commit, detecting data races at runtime
• Fuzz testing — 4 fuzz targets ( FuzzPathTraversal , FuzzParseRequestLine , FuzzParseHeaders , FuzzSmugglingDetected ) with committed corpora in testdata/fuzz/
• Integration tests — 3-node in-process cluster tests for all consistency modes ( make integration )
• Chaos tests — peer kill, origin flap, slow origin, rolling restart, concurrent purge ( make chaos )
• Load testing — k6 load tests running nightly with regression gates ( loadtest-nightly.yml )

The project uses Go's test framework with assertions enabled during dynamic analysis:

• -race flag enabled in all CI and pre-commit test runs (detects data races, a form of runtime assertion not enabled in production builds)
• Testify require + assert — used throughout all test suites with strict assertions
• Fuzz testing — 4 fuzz targets with corpus seeds, runtime assertions on parser/smuggling detection
• Benchmark allocation gates — allocs/op == 0 assertions on hit path, enforced in CI
• Conformance score gate — runtime assertion that score ≥ 339, fails CI if regressed
• Chaos tests — runtime assertions on cluster convergence, peer fetch, origin flap behavior

None of these assertions run in production builds ( go build without test flags).