L5Wall 0.2.1

L5Wall 0.2.1

发布日期：2026-11-03

L5Wall 0.2.1 是 0.2.0 的生命周期修复版本。它是 HighWall 仓库中的 TLS 会话层子项目，拥有独立版本号、测试矩阵、威胁模型、部署说明和发布流。

修复

• 监听器不再把瞬时 accept 错误当作退出信号。EINTR、ECONNABORTED、Windows socket reset、EMFILE/ENFILE 和缓冲区/内存耗尽会记录告警并按 50 ms 至 1 s 指数退避重试，成功后退避复位。
• 不可恢复的 accept 错误现在显式抛出 L5ProxyError，不再静默返回后被进程管理器的重启策略掩盖。
• 收到 SIGTERM 后停止接受新连接，在 shutdown_timeout 内排空在途连接，超时才强制关闭；默认时限为 8 秒。
• 新增连接风暴、瞬时/致命故障注入、在途请求排空和排空超时回归测试。

状态

• 覆盖等级：C1，不完整。
• 成熟度：Alpha，未经独立第三方安全审计，非生产就绪。
• 运行时只依赖 Python 3.10+ 标准库。

它已经能终止 TLS、执行 SNI/ALPN 白名单、最低 TLS 版本、mTLS、SNI/Host 一致性和有界 H1 转发；没有标准 JA3/JA4、0-RTT 策略、QUIC、H2/H3 检查或握手前 TCP 预算。不要把它描述成完整 L5/L7 防护。

发布产物

• l5wall-0.2.1-py3-none-any.whl
• l5wall-0.2.1.tar.gz
• SHA256SUMS
• ghcr.io/fallen-leaves089/l5wall:0.2.1（linux/amd64、linux/arm64）

镜像带 cosign keyless 签名、GitHub provenance 和 SBOM attestation。安装前请校验 SHA256SUMS。

安装

python3 -m venv /opt/l5wall
/opt/l5wall/bin/pip install --no-cache-dir ./l5wall-0.2.1-py3-none-any.whl
/opt/l5wall/bin/l5wall --version

完整部署步骤见 DEPLOYMENT.md。

边界

• serve 只允许回环监听和回环上游；容器部署需要 host network 或共享网络命名空间。
• 不转发原始客户端 IP；不要在其后启用按 IP 封禁、来源 ACL 或依赖真实来源的限速。
• 只接受 http/1.1 ALPN；H2/H3 不会被降级伪装成已检查。
• L5Wall 之前不能有终止 TLS 的代理，否则真实客户端握手信息已经丢失。

验证

• 42 项标准库 unittest 通过，包括监听故障注入、连接风暴、优雅排空和排空超时。
• ruff、mypy、l5wall check 通过。
• wheel/sdist 构建和安装自检通过；发布包不包含测试证书、私钥或测试目录。
• 证书、SPDX 许可证和 NOTICE 均随包分发。

许可

Apache-2.0。见 LICENSE 和 NOTICE。

---

L5Wall 0.2.1

Release date: 2026-11-03

L5Wall 0.2.1 is a lifecycle-reliability patch release for 0.2.0. It is the TLS session-layer subproject in the HighWall repository, with its own version, test matrix, threat model, deployment guide, and release workflow.

Fixes

• The listener no longer treats transient accept failures as an exit signal. EINTR, ECONNABORTED, Windows socket resets, EMFILE/ENFILE, and buffer or memory exhaustion are logged and retried with exponential backoff from 50 ms to 1 s; the backoff resets after a successful accept.
• Fatal accept failures now raise L5ProxyError explicitly instead of returning silently and being masked by a supervisor restart policy.
• On SIGTERM, the listener stops accepting new work, drains in-flight connections for up to shutdown_timeout, and only then force-closes the remainder. The default is 8 seconds.
• Regression coverage now includes connection storms, transient and fatal fault injection, in-flight draining, and drain-deadline expiry.

Status

• Coverage: C1, incomplete.
• Maturity: Alpha, not independently audited, not production-ready.
• Runtime dependency: Python 3.10+ standard library only.

It terminates TLS, enforces SNI/ALPN allowlists, minimum TLS versions, mTLS, SNI/Host consistency, and bounded HTTP/1.1 forwarding. It does not implement standard JA3/JA4, 0-RTT policy, QUIC, H2/H3 inspection, or a pre-handshake TCP budget. Do not describe it as complete L5/L7 protection.

Artifacts

• l5wall-0.2.1-py3-none-any.whl
• l5wall-0.2.1.tar.gz
• SHA256SUMS
• ghcr.io/fallen-leaves089/l5wall:0.2.1 (linux/amd64, linux/arm64)

The image is signed with cosign keyless signing and carries GitHub provenance and SBOM attestations. Verify SHA256SUMS before installation.

Install

python3 -m venv /opt/l5wall
/opt/l5wall/bin/pip install --no-cache-dir ./l5wall-0.2.1-py3-none-any.whl
/opt/l5wall/bin/l5wall --version

See DEPLOYMENT.md for the full deployment procedure.

Boundaries

• serve only permits loopback listeners and loopback upstreams. Container deployment requires host networking or a shared network namespace.
• The original client IP is not forwarded. Do not enable per-IP bans, source ACLs, or source-based rate limits behind this bridge.
• Only http/1.1 ALPN is accepted. H2/H3 is never downgraded and presented as inspected.
• A TLS-terminating proxy must not sit in front of L5Wall; the real client handshake metadata would already be lost.

Verification

• 42 standard-library unittest cases pass, including listener fault injection, connection storms, graceful draining, and drain-deadline expiry.
• ruff, mypy, and l5wall check pass.
• Wheel/sdist build and installation smoke checks pass; release artifacts contain no test certificates, private keys, or test directories.
• Certificates, SPDX license metadata, and NOTICE are included.

License

Apache-2.0. See LICENSE and NOTICE.

Image digest: sha256:6dbb372aa40e2fda8cd70738862279ffa17e6761a4d0cf9d5aef529becd434b7

L4Wall 0.1.0

L4Wall 0.1.0

发布日期：2026-11-03

L4Wall 是 HighWall 仓库中的独立 TCP L4 防护网关，负责连接级准入、并发与速率限制、超时、字节上限、行为评分、封禁和审计。0.1.0 现在以独立标签和独立 GitHub Release 发布，不再依附 HighWall 主版本包。

发布性质

• 本发布完整复用 v0.11.0 官方 Release 中的 L4Wall 0.1.0 wheel 和 sdist，没有重新构建，也没有修改包内容。
• 发布标签指向 v0.11.0 对应源码提交 18e9f7e79870681b915fe85fb051a6a06b2378d2；发布资产沿用该 Release 的官方 L4Wall 附件，不来自当前 main。
• main 上的后续 L4Wall 改动不属于本发布，包括之后加入的 PROXY v2 发送能力等。
• 历史 sdist 保留了当时打包的 tests/ 和 l4wall.egg-info；本次为了保持字节一致而没有清理。新的 l4wall-v* 发布流会对未来构建执行测试、缓存、密钥和许可证检查。
• 历史资产没有 GitHub artifact attestation；本发布只声明其 SHA-256 与 v0.11.0 官方资产记录一致，不声称存在构建 provenance。

发布产物

• l4wall-0.1.0-py3-none-any.whl
• l4wall-0.1.0.tar.gz
• SHA256SUMS（只包含上面两个 L4Wall 文件）

SHA-256：

7bbbb9ad244ea5df911c697545e35089a15d3aa470fd4a497709d5d8df9b98bc  l4wall-0.1.0-py3-none-any.whl
5c5759e2a1f694b5296128622bbc3d31551097988cb1d85adaa1d8af46698dcf  l4wall-0.1.0.tar.gz

独立发布的标准下载位置是本 Release 的 Assets；旧版 v0.11.0 页面仅保留原始 L4Wall 附件以兼容旧链接。L4Wall 不提供 GHCR 镜像、PyPI 包或其他额外下载渠道，也不把 HighWall、L5Wall 或原生核心二进制打进 L4Wall 包。

状态

• 版本：0.1.0
• 成熟度：Alpha / MVP
• 运行时：Python 3.10+，只依赖标准库
• 覆盖：TCP 连接级防护；没有 TLS/HTTP 内容检查
• 审计与生产准入：未经过独立第三方安全审计，不是生产就绪产品

v0.11.0 的历史验证记录为 65 项 L4Wall 测试通过。本次独立发布额外复核资产哈希、干净虚拟环境安装、CLI 版本和初始化配置检查。

安装

先下载本 Release 的三个附件并校验：

sha256sum -c SHA256SUMS
python3 -m venv /opt/l4wall
/opt/l4wall/bin/pip install --no-cache-dir ./l4wall-0.1.0-py3-none-any.whl
/opt/l4wall/bin/l4wall --version
/opt/l4wall/bin/l4wall init --path ./config.json
/opt/l4wall/bin/l4wall check --config ./config.json

生产前请阅读 L4Wall README、部署基线 和 威胁模型。

边界

• 不处理带宽型 DDoS、SYN flood、UDP、QUIC/HTTP3 或运营商侧拥塞。
• 不解析 HTTP，不做认证、授权、WAF、DLP、TLS 终止或 JA3/JA4。
• 只保护显式配置的 listener；直连 HighWall 或上游仍会绕过 L4Wall，必须用监听地址和网络 ACL 收紧。
• 共享封禁在 0.1.0 中只有读取端；自动发布、Controller、多节点冲突合并和 HA 尚未实现。
• 不适用于已失陷主机；攻击者若能修改配置、审计或进程内存，L4 边界已经失效。

许可

Apache-2.0。许可证与 NOTICE 见仓库根目录；未来独立构建也会随 wheel/sdist 分发对应文件。

---

L4Wall 0.1.0

Release date: 2026-11-03

L4Wall is the standalone TCP L4 protection gateway in the HighWall repository. It provides connection admission, concurrency and rate limits, timeouts, byte caps, behavioral scoring, bans, and audit records. Version 0.1.0 is now published under its own tag and GitHub Release instead of being bundled into a HighWall release.

Release provenance

• This release reuses the exact L4Wall 0.1.0 wheel and sdist from the official v0.11.0 release. The packages were not rebuilt or modified.
• The release tag points to the v0.11.0 source commit 18e9f7e79870681b915fe85fb051a6a06b2378d2; the assets are the official L4Wall attachments from that release, not a build of the current main branch.
• Later L4Wall changes on main are not part of this release, including the subsequent PROXY v2 sender support.
• The historical sdist retains the tests/ and l4wall.egg-info entries from its original build. They were left unchanged to preserve byte-for-byte compatibility. Future l4wall-v* releases will run test, cache, secret, and license checks.
• The historical assets have no GitHub artifact attestation. This release only states that their SHA-256 digests match the official v0.11.0 asset records; it does not claim build provenance.

Artifacts

• l4wall-0.1.0-py3-none-any.whl
• l4wall-0.1.0.tar.gz
• SHA256SUMS (these two L4Wall files only)

SHA-256:

7bbbb9ad244ea5df911c697545e35089a15d3aa470fd4a497709d5d8df9b98bc  l4wall-0.1.0-py3-none-any.whl
5c5759e2a1f694b5296128622bbc3d31551097988cb1d85adaa1d8af46698dcf  l4wall-0.1.0.tar.gz

The canonical download location for this standalone release is the Assets section of this release. The historical v0.11.0 page retains the original L4Wall attachments only for old links. L4Wall has no GHCR image, PyPI package, or other download channel, and its packages do not contain HighWall, L5Wall, or native-core binaries.

Status

• Version: 0.1.0
• Maturity: Alpha / MVP
• Runtime: Python 3.10+, standard library only
• Coverage: connection-level TCP protection; no TLS or HTTP payload inspection
• Audit and production readiness: not independently audited and not production-ready

The historical v0.11.0 verification record reports 65 passing L4Wall tests. This standalone publication additionally checks artifact hashes, clean virtual-environment installation, the CLI version, and a generated configuration.

Install

Download all three assets, verify them, and install the wheel:

sha256sum -c SHA256SUMS
python3 -m venv /opt/l4wall
/opt/l4wall/bin/pip install --no-cache-dir ./l4wall-0.1.0-py3-none-any.whl
/opt/l4wall/bin/l4wall --version
/opt/l4wall/bin/l4wall init --path ./config.json
/opt/l4wall/bin/l4wall check --config ./config.json

Read the L4Wall README, deployment baseline, and threat model before deployment.

Boundaries

• It does not handle bandwidth DDoS, SYN floods, UDP, QUIC/HTTP3, or carrier-side congestion.
• It does not parse HTTP or provide authentication, authorization, WAF, DLP, TLS termination, or JA3/JA4.
• It protects only explicitly configured listeners. Direct access to HighWall or an upstream bypasses L4Wall; listener addresses and network ACLs must close those paths.
• Shared bans in 0.1.0 are reader-only. Automatic publishing, a controller, conflict merging, and HA are not implemented.
• It cannot protect an already compromised host. If an attacker can modify configuration, audit state, or process memory, the L4 boundary has already failed.

License

Apache-2.0. See the repository root for the license and NOTICE; future standalone builds will also include both files in the wheel and sdist.

HighWall 0.12.0 (Alpha)

HighWall 0.12.0 Alpha 预发布

English | 简体中文

状态：GitHub pre-release（Alpha）。这是可供评审和验证的预发布，不是生产发布，不附带生产支持承诺。最新稳定版仍是 0.11.0，本次发布不会移动 latest。

本版本包含

• 精确客户端 IP + 请求形状的执法键；/24、/64 只用于关联，不自动扩大封禁。
• highwall ops preview 只读 Safe Ops 预演；R2/R3 默认拒绝，没有执行入口。
• highwall capabilities --json 描述 Python H1 基线的 C0-C4 等级；原生核心能力单独按 H1/H2/H3 声明。
• 独立 subprojects/l5wall 0.2.0：TLS 终止、SNI/ALPN/mTLS 策略、握手超时、回环 H1 桥接、SNI/Host 一致性、请求头/连接/字节上限。L5Wall 继续作为独立服务发布，不并入 Python wheel。
• 阶段 1 的 l5wall serve 只允许回环监听和回环上游，只接受 http/1.1 ALPN；H2/H3 不会被伪装成已检查。
• 回环桥接不传递原始客户端 IP；不能在其后启用按 IP 封禁、来源 ACL 或依赖真实来源的限速。
• L4Wall 可选 send_proxy_v2，支持向上游发送标准 PROXY v2 TCP header；原生核心可要求 PROXY v2，并只信任显式配置的代理网段。
• Rust 原生 B+D-4 核心：TLS/QUIC、H1/H2/H3 严格解析、H1 WebSocket、H2/H3 gRPC、压缩/trailers、有界正文 WAF/DLP、精确 IP 封禁、mTLS/CRL、QUIC Retry、默认禁 0-RTT/迁移和 QUIC 客户端网络 ACL。
• TCP 和 UDP 是两条入口：H1/H2 可经 L4Wall 和 PROXY v2；H3 当前直达原生 QUIC listener，不经过 L4Wall。
• Python 镜像保持 Python-only；原生核心使用独立 Dockerfile.native，以非 root 运行，不把 Rust 依赖塞入 Python wheel 或镜像。

发布资产

GitHub Release 预期包含：

• highwall-0.12.0-py3-none-any.whl 与 highwall-0.12.0.tar.gz。
• Linux x86_64 原生二进制 highwall-native-core-0.12.0-linux-x86_64。
• Windows x86_64 原生二进制 highwall-native-core-0.12.0-windows-x86_64.exe。
• 原生核心示例配置 highwall-native-config-0.12.0.example.json。
• 覆盖上述资产的 SHA256SUMS。

发布工作流会为资产生成 GitHub build provenance attestation。容器工作流另外发布 Python-only 镜像 ghcr.io/fallen-leaves089/highwall:0.12.0（linux/amd64、linux/arm64），带 OCI provenance、SBOM 和 cosign 签名；它不是完整 B+D-4 镜像。Dockerfile.native 本轮未作为公开 GHCR 镜像发布，原生路径以 Release 中的独立二进制为准。

验证

• 根 Python：384 项测试通过；coverage --branch 总覆盖率 81%，高于项目 80% 门槛；原生真实串联默认跳过，显式开启后单独通过。
• L4Wall：71 项测试通过，包括 PROXY v2 编码和上游首包。
• L5Wall：36 项测试通过；含真实回环 TLS→HighWall 串联、未知 ALPN、SNI/Host 不一致、异常 framing、超大请求头、转发字节上限，以及跨平台许可证一致性检查。
• 原生核心：cargo test --all-targets --locked 144 项通过；cargo fmt --all -- --check、cargo clippy --all-targets --locked -- -D warnings 和锁定依赖的 release 构建通过。
• ruff、mypy（30 个根源文件）、compileall、解析器 fuzz（2000 轮、8000 次检查）、示例/严格配置检查和 highwall diff 通过。
• DSH 首轮独立验收：0 Critical、0 High、3 Medium、8 Low、3 信息项。r5 定向复测为 0 Critical、0 High：8 个指定项中 7 项定向关闭（HWA-01/02/03/07/08/09/10）；HWA-11 在 r6 窄范围独立复测中关闭。HWA-04/05/06 由维护者 r7 以仓库内可重复测试复核通过，见 REGRESSION-R7-20261102.md；r7 不是 DSH 独立验收，不能把这三个编号写成 DSH 已独立复测。
• 维护者 R7 定向结果：HWA-04 的三个重复伪头部拒绝均为 H3_MESSAGE_ERROR 270、上游零命中；HWA-05 的四个 HEAD 路由均为 200、正确 Content-Length、0 B 正文、每个上游命中 1；HWA-06 在 8192 B 为 200/上游命中 1，在 8193 B 为 413 HW-NATIVE-PROTOCOL-001/上游命中 0。
• 发布标签工作流会在 Python 3.10–3.14 上重复根测试，并在 Linux/Windows 原生 runner 上重复静态检查和测试。本地结果不能替代该远程结果；正式发布前以 Release/Container 工作流状态为准。

部署边界

• H1/H2/H3 仍只声明 C3，不声明 C4。C4 所需的完整流式背压饱和、QPACK 阻塞、真实 WebSocket 端到端和更完整的 slow-flow 覆盖仍未关闭。
• H3/UDP 绕过 L4Wall；应用层 QUIC ACL 不能替代主机防火墙或安全组。部署必须另设 UDP 来源限制、速率限制和入口 ACL。
• 被封禁来源仍可能先完成 TLS/QUIC 握手，再收到 HTTP 403。当前结论只证明应用层拒绝，不证明握手前零成本。
• 原生封禁是进程内状态，带 TTL 和容量上限；重启清空，单写者持久状态服务尚未接入。
• 运行中进程映像没有独立 attestation；DSH 的 runtime_process_image_evidence=false / process_image_independent_attestation=false 仍然成立。Release 资产 attestation 只证明构建产物来源，不证明某个运行进程就是该产物。
• Docker/HAProxy 真实边缘、standard 容器拓扑、原生镜像公开分发、真实多节点状态服务和审计写失败拓扑未在本轮验收。Docker 是可选打包/部署层，不阻塞原生可执行文件路径。
• 本轮未修改主机防火墙规则；Windows 自动规则可能绑定二进制绝对路径，部署必须显式创建并复验 TCP/UDP Allow 规则。
• 本项目尚未完成独立第三方安全审计；DSH 结果是本轮安全验证输入，不等于外部审计证书或生产准入。

发布门槛与回滚

不得把本版本标记为生产发布，也不得把 C3 写成 C4 或完整防护。DSH 对生产发布的 no-push 建议保持不变；本次只发布 Alpha 预发布和脱敏、可复现的验证记录。

回滚策略：生产环境继续使用并固定 0.11.0 及对应摘要；不要依赖 latest。若需要评估 0.12.0，使用 Release 中的固定版本资产并先核对 SHA256SUMS 与 build provenance，再在隔离环境完成入口、真实来源、H3/UDP 网络层封堵和回滚演练。

---

HighWall 0.12.0 Alpha Pre-release

简体中文 | English

Status: GitHub pre-release (Alpha). This is a reviewable and testable pre-release, not a production release, and it carries no production support commitment. The latest stable version remains 0.11.0; this release does not move latest.

Included

• Exact client-IP plus request-shape enforcement keys; /24 and /64 are correlation-only and do not automatically widen bans.
• Read-only highwall ops preview; R2/R3 remain denied by default and no executor exists.
• highwall capabilities --json for the Python H1 baseline with explicit C0-C4 levels; native-core coverage is declared separately for H1/H2/H3.
• Standalone subprojects/l5wall 0.2.0: TLS termination, SNI/ALPN/mTLS policy, handshake timeout, loopback HTTP/1.1 bridge, SNI/Host consistency, and request-head/connection/byte bounds. L5Wall remains a standalone service release and is not folded into the Python wheel.
• The phase-1 l5wall serve path accepts loopback listeners and upstreams only and accepts only the http/1.1 ALPN. H2/H3 are not presented as inspected.
• The loopback bridge does not preserve the original client IP; do not enable per-IP bans, source ACLs, or source-dependent rate limits behind it.
• Optional L4Wall send_proxy_v2 emits a standard PROXY v2 TCP header upstream; the native core can require PROXY v2 and trust only explicitly configured proxy networks.
• Rust native B+D-4 core: TLS/QUIC, strict H1/H2/H3 parsing, H1 WebSocket, H2/H3 gRPC, compression/trailers, bounded-body WAF/DLP, exact-IP bans, mTLS/CRL, QUIC Retry, 0-RTT and migration disabled by default, and a QUIC client-network ACL.
• TCP and UDP are separate ingress paths: H1/H2 can pass through L4Wall and PROXY v2; H3 currently reaches the native QUIC listener directly without L4Wall.
• The Python image remains Python-only. The native core has a separate Dockerfile.native, runs as non-root, and does not pull Rust dependencies into the Python wheel or image.

Release assets

The GitHub Release is expected to contain:

• highwall-0.12.0-py3-none-any.whl and highwall-0.12.0.tar.gz.
• Linux x86_64 native binary highwall-native-core-0.12.0-linux-x86_64.
• Windows x86_64 native binary highwall-native-core-0.12.0-windows-x86_64.exe.
• Native example configuration highwall-native-config-0.12.0.example.json.
• A SHA256SUMS file covering those assets.

The release workflow creates GitHub build provenance attestations for the assets. A separate container workflow publishes the Python-only image ghcr.io/fallen-leaves089/highwall:0.12.0 for linux/amd64 and linux/arm64 with OCI provenance, SBOM, and a cosign signature; it is not a full B+D-4 image. Dockerfile.native is not published as a public GHCR image in this release; use the standalone binary from the Release for the native path.

Verification

• Root Python suite: 384 tests passed; coverage --branch reported 81% total coverage, above the project's 80% gate. The native real-chain test is skipped by default and passes separately when explicitly enabled.
• L4Wall: 71 tests passed, including PROXY v2 encoding and upstream first bytes.
• L5Wall: 36 tests passed, including a real loopback TLS-to-HighWall chain, unknown ALPN, SNI/Host mismatch, malformed framing, oversized request heads, relay byte limits, and a cross-platform license consistency check.
• Native core: all 144 cargo test --all-targets --locked cases passed; cargo fmt --all -- --check, cargo clippy --all-targets --locked -- -D warnings, and the locked release build passed.
• ruff, mypy (30 root source files), compileall, parser fuzzing (2,000 iterations and 8,000 checks), example and strict configuration checks, and highwall diff passed.
• DSH first independent acceptance: 0 Critical, 0 High, 3 Medium, 8 Low, and 3 informational findings. The r5 directed retest found 0 Critical and 0 High: seven of eight scoped items closed (HWA-01/02/03/07/08/09/10); HWA-11 closed in the narrow r6 independent retest. HWA-04/05/06 were repeated by the maintainer's r7 repository tests, documented in REGRESSION-R7-20261102.md. The r7 run is not DSH independent acceptance and must not be described as a DSH independent retest of those three items.
• Maintainer r7 directed results: all three HWA-04 duplicate-pseudo-header cases returned H3_MESSAGE_ERROR 270 with zero upstream hits; all four HWA-05 HEAD routes returned 200 with the correct Content-Length, a 0-byte body, and one upstream hit each; HWA-06 returned 200 with one upstream hit at 8192 bytes and 413 HW-NATIVE-PROTOCOL-001 with zero upstream hits at 8193 bytes.
• The release-tag workflow repeats the root tests on Python 3.10-3.14 and repeats static analysis and tests on Linux and Windows native runners. Local results do not replace those remote results; check the Release and Container workflow runs before treating the pre-release as published.

Deployment boundaries

• H1/H2/H3 remain declared at C3, not C4. Complete streaming backpressure saturation, QPACK blocking, real end-to-end WebSocket coverage, and broader slow-flow coverage remain incomplete.
• H3/UDP bypasses L4Wall. An application-level QUIC ACL does not replace a host firewall or security group. Deployments must add separate UDP source restrictions, rate limits, and ingress ACLs.
• A banned source can still complete a TLS/QUIC handshake before receiving HTTP 403. The current result proves application-layer rejection, not zero-cost pre-handshake blocking.
• Native bans are process-local with TTL and capacity bounds; they are lost on restart and not yet backed by a single-writer persistent state service.
• There is no independent attestation of the running process image; DSH's runtime_process_image_evidence=false / process_image_independent_attestation=false still applies. Release asset attestation proves build provenance, not that a particular running process is that build.
• The real Docker/HAProxy edge, the standard container topology, public distribution of the native image, a real multi-node state service, and audit-write-failure topology were not validated in this round. Docker remains an optional packaging/deployment layer and does not block the native executable path.
• Host firewall rules were not modified in this environment. Windows automatic rule...

L5Wall 0.2.0

L5Wall 0.2.0

发布日期：2026-11-02

L5Wall 0.2.0 是 L5Wall 作为独立服务发布的第一个版本。它是 HighWall 仓库中的 TLS 会话层子项目，拥有独立版本号、测试矩阵、威胁模型、部署说明和发布产物。

状态

• 覆盖等级：C1，不完整。
• 成熟度：Alpha，未经独立第三方安全审计，非生产就绪。
• 运行时只依赖 Python 3.10+ 标准库。

它已经能终止 TLS、执行 SNI/ALPN 白名单、最低 TLS 版本、mTLS、SNI/Host 一致性和有界 H1 转发；没有标准 JA3/JA4、0-RTT 策略、QUIC、H2/H3 检查或握手前 TCP 预算。不要把它描述成完整 L5/L7 防护。

发布产物

• l5wall-0.2.0-py3-none-any.whl
• l5wall-0.2.0.tar.gz
• SHA256SUMS
• ghcr.io/fallen-leaves089/l5wall:0.2.0（linux/amd64、linux/arm64）

镜像带 cosign keyless 签名、GitHub provenance 和 SBOM attestation。安装前请校验 SHA256SUMS。

安装

python3 -m venv /opt/l5wall
/opt/l5wall/bin/pip install --no-cache-dir ./l5wall-0.2.0-py3-none-any.whl
/opt/l5wall/bin/l5wall --version

完整部署步骤见 DEPLOYMENT.md。

边界

• serve 只允许回环监听和回环上游；容器部署需要 host network 或共享网络命名空间。
• 不转发原始客户端 IP；不要在其后启用按 IP 封禁、来源 ACL 或依赖真实来源的限速。
• 只接受 http/1.1 ALPN；H2/H3 不会被降级伪装成已检查。
• L5Wall 之前不能有终止 TLS 的代理，否则真实客户端握手信息已经丢失。

验证

• 36 项标准库 unittest 通过。
• ruff、mypy、l5wall check 通过。
• wheel/sdist 构建和安装自检通过；发布包不包含测试证书、私钥或测试目录。
• 证书、SPDX 许可证和 NOTICE 均随包分发。

许可

Apache-2.0。见 LICENSE 和 NOTICE。

---

L5Wall 0.2.0

Release date: 2026-11-02

L5Wall 0.2.0 is the first standalone service release of L5Wall, the TLS session-layer subproject in the HighWall repository. It has its own version, test matrix, threat model, deployment guide, and release artifacts.

Status

• Coverage: C1, incomplete.
• Maturity: Alpha, not independently audited, not production-ready.
• Runtime dependency: Python 3.10+ standard library only.

It terminates TLS, enforces SNI/ALPN allowlists, minimum TLS versions, mTLS, SNI/Host consistency, and bounded HTTP/1.1 forwarding. It does not implement standard JA3/JA4, 0-RTT policy, QUIC, H2/H3 inspection, or a pre-handshake TCP budget. Do not describe it as complete L5/L7 protection.

Artifacts

• l5wall-0.2.0-py3-none-any.whl
• l5wall-0.2.0.tar.gz
• SHA256SUMS
• ghcr.io/fallen-leaves089/l5wall:0.2.0 (linux/amd64, linux/arm64)

The image is signed with cosign keyless signing and carries GitHub provenance and SBOM attestations. Verify SHA256SUMS before installation.

Install

python3 -m venv /opt/l5wall
/opt/l5wall/bin/pip install --no-cache-dir ./l5wall-0.2.0-py3-none-any.whl
/opt/l5wall/bin/l5wall --version

See DEPLOYMENT.md for the full deployment procedure.

Boundaries

• serve only permits loopback listeners and loopback upstreams. Container deployment requires host networking or a shared network namespace.
• The original client IP is not forwarded. Do not enable per-IP bans, source ACLs, or source-based rate limits behind this bridge.
• Only http/1.1 ALPN is accepted. H2/H3 is never downgraded and presented as inspected.
• A TLS-terminating proxy must not sit in front of L5Wall; the real client handshake metadata would already be lost.

Verification

• 36 standard-library unittest cases pass.
• ruff, mypy, and l5wall check pass.
• Wheel/sdist build and installation smoke checks pass; release artifacts contain no test certificates, private keys, or test directories.
• Certificates, SPDX license metadata, and NOTICE are included.

License

Apache-2.0. See LICENSE and NOTICE.

Image digest: sha256:f87eb6704b368cf959d17c525070c4f94de4dcb5e8f1435214ed5ab7a81172bf

HighWall v0.11.0 + L4Wall 0.1.0

HighWall v0.11.0 + L4Wall 0.1.0

L4Wall 独立发布（2026-11-03）：L4Wall 0.1.0 已在 l4wall-v0.1.0 单独发布。本页原有 L4Wall wheel/sdist 为兼容旧链接保留，字节未变；新下载请优先使用独立 Release。该调整不改变 HighWall 0.11.0 的代码或附件。

Standalone L4Wall release (2026-11-03): L4Wall 0.1.0 is now published separately at l4wall-v0.1.0. The L4Wall wheel and sdist on this page remain unchanged for link compatibility. Prefer the standalone release for new downloads. This update does not change the HighWall 0.11.0 code or assets.
English release notes | 简体中文

发布日期：2026-10-30

概览

v0.11.0 把仓库从单一 HTTP/1.1 防护网关扩展为可组合的两层防护基线：

• L4Wall 0.1.0：失败关闭的 TCP 连接级网关，负责准入、并发/速率限制、超时、字节上限、行为评分、封禁和审计。
• HighWall 0.11.0：继续负责 HTTP/1.1 的 Host/方法/路径策略、WAF、DLP、响应完整性、L7 限速和蜜罐。
• 复合部署：提供 lite 串联形态和 standard 边缘代理骨架；两者都不把“部署了组件”等同于“已经覆盖所有入口”。

新增

L4Wall 子项目

• 连接级来源白名单和默认拒绝。
• 单 IP 并发上限、新建连接速率和连接突发控制。
• 首字节、空闲、总连接时长和单方向字节上限。
• 多 listener 扇出、短连接、零字节探测、拒绝风暴和固定节奏等行为信号。
• 两阶段评分、限时遏制、确认封禁和 offenders.json 持久化。
• JSONL 审计、回环管理面、健康检查和 Prometheus 文本指标。
• 可选私网 Redis 共享封禁读取端：版本化 JSON、严格字段校验、容量限制、TTL 截断、本地优先和故障隔离。

复合部署与攻防验收

• scripts/attack_range.py：本机回环靶场，覆盖 L4Wall -> HighWall -> 模拟上游的 28 项矩阵；支持独立 WSL 攻击实例和常驻模式。
• deploy/standard/：HAProxy、Compose、TLS 变体、上游回声服务和旁路验收脚本。
• docs/STACK.md：信任边界、真实客户端 IP、直连封堵、封禁同步、故障策略和验收清单。
• docs/ATTACK_TESTING.md：自动化矩阵、实机结果、已修复问题和未验证项。

修复与加固

• 全局在途请求超限时，503 响应现在带 Retry-After: 1 和 X-Request-ID；审计同步记录 request_id、HW-SERVER-1001、status=503、detail=inflight_limit 和真实响应字节数。
• l4wall inspect 不再输出密码或管理令牌的环境变量名，并增加脱敏回归测试。
• 靶场把 L4 单方向字节上限调整到 2 MiB，使 HighWall 的 413 在临界区间可观测。
• 发布包补充 subprojects/，sdist 不会再漏掉 L4Wall 源码。

验证

• HighWall 全量：354 项测试通过。
• L4Wall：65 项测试通过。
• 跨层攻防：26 项端到端测试通过。
• ruff、mypy、compileall、配置检查和干净虚拟环境安装通过。
• PR CI：Ubuntu/Windows x Python 3.10/3.11/3.12、CodeQL、静态分析全部通过。
• 实机矩阵：28/28 通过，0 失败；2 项已知边界风险已记录，未计作通过项。
• 40 并发复测：31 个 200、1 个可追溯 503、8 个无 HTTP 响应；L4 侧 32 个允许、8 个 ip_capacity 拒绝。
• 审计对账：在途请求允许/拒绝记录的 request_id 与客户端 X-Request-ID 32/32 对齐。
• 字节边界：1,048,491 字节返回 200，1,048,577 字节返回 413（HW-PROTO-1106）。

下载

下载文件在 v0.11.0 Release 的 Assets 区域。下载后先用 SHA256SUMS 校验，再安装：

python -m pip install highwall-0.11.0-py3-none-any.whl
python -m pip install l4wall-0.1.0-py3-none-any.whl

容器镜像

v0.11.0 标签会触发多架构镜像构建并发布到 GHCR：

docker pull ghcr.io/fallen-leaves089/highwall:0.11.0

• Digest（linux/amd64 + linux/arm64 OCI index）：sha256:efedb3b9cca32a65f086c1a2ba89ae3c268a45e7a94a4158acfa5e8cda6c2dfc
• GHCR：ghcr.io/fallen-leaves089/highwall:0.11.0
• 构建工作流：https://github.com/Fallen-leaves089/highwall/actions/runs/41005104183
• SBOM、GitHub provenance attestation 和 cosign keyless 签名步骤均成功。

兼容性

• HighWall 的 HTTP/1.1 配置 schema 未破坏性变更；v0.10.0 配置可继续使用。
• L4Wall 是独立进程和独立 0.1.0 包，不要求 HighWall 进程内加载。
• lite 形态下 HighWall 看到的来源是 L4Wall 地址；需要真实客户端归属时使用 standard 骨架。

边界与未覆盖项

• HighWall 0.11.0 和 L4Wall 0.1.0 都是 alpha 阶段，未经过独立第三方安全审计。
• L4Wall 不处理带宽型 DDoS、SYN flood、UDP、QUIC/HTTP3，也不替代应用认证、授权或主机 EDR。
• standard 骨架当前只保证入口、真实 IP、网络闭环、L7 防护和验收；L4Wall Controller、动态封禁下发和多节点 HA 仍是后续里程碑。
• 共享封禁目前只有读取端，自动发布、冲突合并和 Controller 尚未实现。
• Docker/HAProxy 的完整容器拓扑仍需在目标环境执行联调；本地回环通过不等于生产拓扑通过。
• 直连 HighWall 或上游会绕过 L4 ACL；必须用网络 ACL 和监听地址保证攻击者不可达。
• 本版本不声称“绝对无漏”。未验证项和残余风险以 docs/ATTACK_TESTING.md 与 docs/STACK.md 为准。

---

English

Release date: 2026-10-30

Overview

v0.11.0 expands the repository from a single HTTP/1.1 gateway into a composable two-layer defense baseline:

• L4Wall 0.1.0: a fail-closed TCP connection-level gateway for admission, concurrency and rate limits, timeouts, byte caps, behavior scoring, bans, and audit.
• HighWall 0.11.0: continues to handle HTTP/1.1 Host/method/path policy, WAF, DLP, response integrity, L7 rate limits, and honeypots.
• Composite deployment: provides the lite chain and a standard edge-proxy skeleton. Neither treats “components deployed” as “all ingress covered.”

Added

L4Wall subproject

• Connection-level source allowlists and default deny.
• Per-IP concurrency caps, new-connection rates, and burst control.
• First-byte, idle, total-duration, and per-direction byte limits.
• Behavior signals for multi-listener fan-out, short connections, zero-byte probes, rejection storms, and regular timing.
• Two-stage scoring, timed containment, confirmed bans, and offenders.json persistence.
• JSONL audit, a loopback admin plane, health checks, and Prometheus text metrics.
• An optional private-network Redis shared-ban reader with versioned JSON, strict validation, capacity limits, TTL clamping, local-first merge, and failure isolation.

Composite deployment and attack validation

• scripts/attack_range.py: a local loopback range with a 28-item matrix across L4Wall -> HighWall -> a stub upstream; supports an isolated WSL attacker instance and a long-running mode.
• deploy/standard/: HAProxy, Compose, a TLS variant, an upstream echo service, and a bypass verification script.
• docs/STACK.md: trust boundaries, trusted client IPs, direct-access blocking, ban synchronization, failure policy, and an acceptance checklist.
• docs/ATTACK_TESTING.md: the automated matrix, live results, fixed issues, and unverified items.

Fixes and hardening

• When the global in-flight limit is exceeded, the 503 response now includes Retry-After: 1 and X-Request-ID; the audit record includes request_id, HW-SERVER-1001, status=503, detail=inflight_limit, and the real response byte count.
• l4wall inspect no longer prints password or admin-token environment variable names, with a redaction regression test.
• The range raises the L4 per-direction byte cap to 2 MiB so the HighWall 413 boundary is observable.
• Release packaging includes subprojects/, so the sdist no longer omits L4Wall sources.

Verification

• HighWall: 354 tests passed.
• L4Wall: 65 tests passed.
• Cross-layer attack/defense: 26 end-to-end tests passed.
• ruff, mypy, compileall, configuration checks, and installation in a clean virtual environment passed.
• PR CI: Ubuntu and Windows on Python 3.10/3.11/3.12, CodeQL, and static analysis all passed.
• Live matrix: 28/28 passed, 0 failed; 2 known boundary risks are recorded separately and are not counted as passes.
• 40-connection retest: 31 200 responses, 1 traceable 503, and 8 connections without an HTTP response; L4 admitted 32 and rejected 8 with ip_capacity.
• Audit correlation: request IDs for allowed and blocked in-flight requests matched the client X-Request-ID in 32/32 cases.
• Byte boundary: 1,048,491 bytes returned 200; 1,048,577 bytes returned 413 (HW-PROTO-1106).

Downloads

The files are in the Assets section of the v0.11.0 release. Verify them against SHA256SUMS before installation:

python -m pip install highwall-0.11.0-py3-none-any.whl
python -m pip install l4wall-0.1.0-py3-none-any.whl

Container image

The v0.11.0 tag builds a multi-architecture image and publishes it to GHCR:

docker pull ghcr.io/fallen-leaves089/highwall:0.11.0

• Digest (linux/amd64 + linux/arm64 OCI index): sha256:efedb3b9cca32a65f086c1a2ba89ae3c268a45e7a94a4158acfa5e8cda6c2dfc
• Build workflow: https://github.com/Fallen-leaves089/highwall/actions/runs/41005104183
• The image includes an SBOM, a GitHub provenance attestation, and a cosign keyless signature. Pin an immutable version in production instead of relying on latest.

Compatibility

• The HighWall HTTP/1.1 configuration schema has no breaking changes; v0.10.0 configurations remain usable.
• L4Wall is a separate process and a separate 0.1.0 package; HighWall does not load it in-process.
• In the lite topology, HighWall sees L4Wall as its peer address. Use the standard skeleton when real client identity is required.

Boundaries and unverified items

• HighWall 0.11.0 and L4Wall 0.1.0 are alpha releases and have not received an independent third-party security audit.
• L4Wall does not handle bandwidth DDoS, SYN floods, UDP, or QUIC/HTTP3, and does not replace application authentication, authorization, or host EDR.
• The standard skeleton currently covers ingress, trusted client IPs, network closure, L7 protection, and acceptance checks. The L4Wall Controller, dynamic ban publishing, and multi-node HA remain future milestones.
• Shared bans currently have a reader only. Automatic publishing, conflict merging, and the Controller are not implemented.
• The full Docker/HAProxy container topology still needs integration testing in the target environment; loopback success does not prove production-topology success.
• Direct access to HighWall or the upstream bypasses the L4 ACL; network ACLs and listener addresses must make those paths unreachable to attackers.
• This release does not claim “no bypasses.” See docs/ATTACK_TESTING.md and docs/STACK.md for unverified items and residual risk.

HighWall v0.10.0

HighWall v0.10.0

本版本聚焦“可预演、可审计、可回滚的变更”，并补齐发布与供应链检查。

新增

• highwall diff：比较默认值展开后的生效配置，区分可热加载、必须重启和安全降级；退出码 4 默认阻止削弱 WAF、DLP、限流、ACL、只读或完整性控制的变更。
• 配置审计：highwall check 增加来源 ACL、Origin/OPTIONS 预检、只读路由等提示。
• 解析器 fuzz 与代理性能基线脚本。
• agent_mode 一键切换：默认 score，企业可改为 block 或 throttle。
• CI 静态检查、类型检查、覆盖率门槛，以及 CodeQL 与 Dependabot。
• 发布镜像构建、SBOM、GitHub provenance attestation 与 cosign 签名。

修复与加固

• 405 响应补齐 Allow：代理级、路由级、管理面和 /reload 分别返回实际允许的方法。
• 收紧查询参数与 JSON body 中的路径穿越识别，包括多重编码。
• 补全热加载字段与配置报告。
• 其余变更见提交历史与 README。

下载

• highwall-0.10.0-py3-none-any.whl
• highwall-0.10.0.tar.gz
• SHA256SUMS

python -m pip install highwall-0.10.0-py3-none-any.whl

容器镜像：

docker pull ghcr.io/fallen-leaves089/highwall:0.10.0

验证

• 326 项测试、106 个 subtests 通过（Ubuntu/Windows × Python 3.10/3.11/3.12）。
• ruff、mypy、highwall check --strict、git diff --check 通过。
• Release 资产可用 SHA256SUMS 校验。
• 镜像 0.10.0 已完成 cosign keyless 签名与验证（digest sha256:80b54132cef0c3cf373b30a77e0248f02f48b6498ac923c80f66d9d2128a1248）。

安全演练

三轮授权隔离演练的脱敏记录见 docs/SECURITY-DRILLS.md。记录省略靶场地址、凭据、flag、规则编号、精确阈值和可复用载荷。

边界

HighWall 仍是 0.10.0，尚未经过独立第三方安全审计；WAF、DLP、评分和蜜罐是启发式控制，不是认证边界。生产使用前请阅读 README、docs/THREAT_MODEL.md 与 docs/DEPLOYMENT.md。

HighWall v0.9.0

HighWall v0.9.0

本版本聚焦“可安全变更”：在不停机、不混合新旧配置的前提下完成配置和证书切换。

新增

• 原子配置重载：先加载、校验并构建新运行时与 TLS 上下文；失败保留当前配置继续服务。
• TLS 证书热轮换：替换证书/私钥文件或路径后，通过 POST /reload 让新握手使用新证书。
• 优雅排空停机：SIGINT/SIGTERM/SIGBREAK 后停止接收新连接，等待在途请求，超时后关闭剩余连接。
• 新增 server.shutdown_timeout，默认 30 秒，可配置 0–300 秒。
• 管理面新增受 Bearer token 保护的 POST /reload；/healthz 返回 config_generation。
• 新增 config_reloads_total、config_reload_failures_total、drain_rejections_total 和 config_generation 指标。
• POSIX 支持 SIGHUP 触发重载。

安全与并发

• 在途请求固定使用取得时的运行时和上游快照。
• 旧运行时在请求结束后释放；未变化的限速、封禁、威胁状态、指标、告警发送器按配置安全复用。
• 修复连接准入期间的 IP 配额释放竞态。
• 上游目标变化时重置熔断状态，避免把旧上游的失败状态带到新目标。
• 监听地址/端口、max_connections、max_inflight_requests、TLS 启用状态和管理面监听仍需滚动重启。

验证

• 284 项测试通过：Ubuntu/Windows × Python 3.10/3.11/3.12。
• compileall、示例配置校验、git diff --check 通过。
• 构建 highwall-0.9.0-py3-none-any.whl 并确认包含 highwall/control.py。

完整说明见 README 和 docs/DEPLOYMENT.md。

HighWall v0.8.1

Added

• Multi-signal attacker fingerprints, persistent marks, two-stage containment, L7 DDoS alerts, and asynchronous webhooks.

Fixed

• Slow responses now honor the configured tarpit_hold_seconds, including the final response-body chunk. A 2-second smoke test measured 2.015 seconds.

Changed

• Expanded the Chinese and English threat-protection documentation, DDoS on-call checklist, webhook example, rollout configuration, troubleshooting, and module smoke commands.
• All version references are synchronized to 0.8.1.

This patch release supersedes the v0.8.0 tag, which predates the documentation and slow-response timing fixes.

Container image: ghcr.io/fallen-leaves089/highwall:0.8.1

HighWall v0.7.1

Fixed\n\n- The single-machine demo now verifies the repository boundary before cleaning runtime data.\n\n### Changed\n\n- All version references are synchronized to 0.7.1.\n\nContainer image: ghcr.io/fallen-leaves089/highwall:0.7.1

HighWall v0.7.0

HighWall v0.7.0

HighWall 是失败关闭的 HTTP/1.1 应用层反向代理与防护网关。本版本提供首个正式 GitHub Release、Python 分发包和 GHCR 多架构容器镜像。

发布内容

• Python wheel：highwall-0.7.0-py3-none-any.whl
• Python 源码包：highwall-0.7.0.tar.gz
• 容器镜像：ghcr.io/fallen-leaves089/highwall:0.7.0（另提供 0.7、latest 和提交哈希标签）
• 平台：linux/amd64、linux/arm64
• 镜像包含 SBOM 和最大级别 provenance；以 UID 10001 非 root 运行，不内置配置，缺少配置文件时失败关闭。

python -m pip install highwall-0.7.0-py3-none-any.whl
docker pull ghcr.io/fallen-leaves089/highwall:0.7.0

主要能力

• 严格的 HTTP/1.x 解析、Host/方法/路径三层默认拒绝，以及请求走私面收敛。
• 路径规范化、WAF、响应 DLP、安全头、请求与响应硬限制。
• 路由级只读策略、方法白名单、CIDR 限制、并发槽位和令牌桶限速。
• 精确路径蜜罐、首击封禁、有界延迟、上游熔断和响应完整性钉扎。
• 结构化脱敏审计、回环管理面、TLS HSTS、配置生成/检查与 Windows 快速部署。

验证

• Python 3.10、3.11、3.12 在 Ubuntu 与 Windows 上共 6 组 CI 全部通过。
• 本地完整测试：248 项通过。
• wheel 隔离安装后 highwall --version 与 highwall check -c config.example.json 通过。
• wheel 26 个文件、源码包 69 个文件，均不含字节码或缓存。

校验和

15516cf2dec4f286c923cc30fda02e603d352d322e32164f44e0ee4adbebb448  highwall-0.7.0-py3-none-any.whl
91446b5550759245270a5bbb22435866fd4fe46c9777d3d215a76ef8be44df3f  highwall-0.7.0.tar.gz

边界声明 / Scope

HighWall 是 L7 入口防护组件，不是“绝对高防”。它不能替代用户认证、密钥管理、主机权限隔离、EDR、备份、磁盘/回环保护和网络层隔离，也尚未完成独立第三方安全审计。生产部署前请阅读 SECURITY.md 和 威胁模型。

HighWall is a fail-closed L7 entry gateway, not an "absolute defense" product. It does not replace authentication, secret management, host privilege isolation, EDR, backups, loopback/disk protection, or network segmentation, and it has not completed an independent third-party audit. See the English README and security policy in the repository for deployment boundaries.

许可证

Apache License 2.0。当前版本为 Alpha，接口和配置可能继续演进。