676312ae79fb3ac01e4e066f53fc00a617efd95c
12
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
 phil
|
d0b53dcc9e |
feat(listeners): verify client connectivity and expose diagnostics
Inspect listener readiness and test exported client endpoints with isolated Mihomo clients. Preserve public addresses, ports and protocol settings, report diagnostic stages, and repair generated access SNI fields. feat(listeners): verify client connectivity and expose diagnostics Inspect listener readiness and test exported client endpoints with isolated Mihomo clients. Preserve public addresses, ports and protocol settings, report diagnostic stages, and repair generated access SNI fields. feat(listeners): verify client connectivity and expose diagnostics Inspect listener readiness and test exported client endpoints with isolated Mihomo clients. Preserve public addresses, ports and protocol settings, report diagnostic stages, and repair generated access SNI fields. feat(listeners): verify client connectivity and expose diagnostics Inspect listener readiness and test exported client endpoints with isolated Mihomo clients. Preserve public addresses, ports and protocol settings, report diagnostic stages, and repair generated access SNI fields. feat(listeners): verify client connectivity and expose diagnostics Inspect listener readiness and test exported client endpoints with isolated Mihomo clients. Preserve public addresses, ports and protocol settings, report diagnostic stages, and repair generated access SNI fields. feat(listeners): verify client connectivity and expose diagnostics Inspect listener readiness and test exported client endpoints with isolated Mihomo clients. Preserve public addresses, ports and protocol settings, report diagnostic stages, and repair generated access SNI fields. feat(listeners): verify client connectivity and expose diagnostics Inspect listener readiness and test exported client endpoints with isolated Mihomo clients. Preserve public addresses, ports and protocol settings, report diagnostic stages, and repair generated access SNI fields. feat(listeners): verify client connectivity and expose diagnostics Inspect listener readiness and test exported client endpoints with isolated Mihomo clients. Preserve public addresses, ports and protocol settings, report diagnostic stages, and repair generated access SNI fields. feat(listeners): verify client connectivity and expose diagnostics Inspect listener readiness and test exported client endpoints with isolated Mihomo clients. Preserve public addresses, ports and protocol settings, report diagnostic stages, and repair generated access SNI fields. feat(listeners): verify client connectivity and expose diagnostics Inspect listener readiness and test exported client endpoints with isolated Mihomo clients. Preserve public addresses, ports and protocol settings, report diagnostic stages, and repair generated access SNI fields. feat(listeners): verify client connectivity and expose diagnostics Inspect listener readiness and test exported client endpoints with isolated Mihomo clients. Preserve public addresses, ports and protocol settings, report diagnostic stages, and repair generated access SNI fields. feat(listeners): verify client connectivity and expose diagnostics Inspect listener readiness and test exported client endpoints with isolated Mihomo clients. Preserve public addresses, ports and protocol settings, report diagnostic stages, and repair generated access SNI fields. |
||
|
freephilx
|
2e6256fb6a |
feat(distribution): add complete installation and recovery workflows
Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs. Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands. Add release verification, lifecycle regression tests, and installation documentation. feat(distribution): add complete installation and recovery workflows Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs. Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands. Add release verification, lifecycle regression tests, and installation documentation. feat(distribution): add complete installation and recovery workflows Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs. Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands. Add release verification, lifecycle regression tests, and installation documentation. feat(distribution): add complete installation and recovery workflows Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs. Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands. Add release verification, lifecycle regression tests, and installation documentation. feat(distribution): add complete installation and recovery workflows Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs. Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands. Add release verification, lifecycle regression tests, and installation documentation. feat(distribution): add complete installation and recovery workflows Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs. Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands. Add release verification, lifecycle regression tests, and installation documentation. feat(distribution): add complete installation and recovery workflows Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs. Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands. Add release verification, lifecycle regression tests, and installation documentation. feat(distribution): add complete installation and recovery workflows Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs. Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands. Add release verification, lifecycle regression tests, and installation documentation. feat(distribution): add complete installation and recovery workflows Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs. Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands. Add release verification, lifecycle regression tests, and installation documentation. feat(distribution): add complete installation and recovery workflows Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs. Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands. Add release verification, lifecycle regression tests, and installation documentation. feat(distribution): add complete installation and recovery workflows Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs. Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands. Add release verification, lifecycle regression tests, and installation documentation. feat(distribution): add complete installation and recovery workflows Ship stable-only Linux bundles and multiarch Docker images with a pinned Mihomo core. Share secure first-run initialization across native and container installs. Validate downloads before downtime, snapshot persistent state before updates, and restore the previous installation after a failed upgrade. Add backup, restore, healthcheck, and randomized administrator reset commands. Add release verification, lifecycle regression tests, and installation documentation. |
||
|
Z User
|
a3c5c3cd0f |
docs: 迁移至 3m-ui-docs 仓库 (Docusaurus)
文档已从本仓库迁移至独立的 3m-ui-docs 仓库，基于 Docusaurus 3 构建。 变更: - 删除 docs/ 目录（全部 18 篇 wiki 文档已迁移） - README.md 顶部添加迁移指引 新文档仓库: https://github.com/kazeyukiro/3m-ui-docs GitHub Wiki 已同步清空（仅保留迁移指引首页） docs: 迁移至 3m-ui-docs 仓库 (Docusaurus) 文档已从本仓库迁移至独立的 3m-ui-docs 仓库，基于 Docusaurus 3 构建。 变更: - 删除 docs/ 目录（全部 18 篇 wiki 文档已迁移） - README.md 顶部添加迁移指引 新文档仓库: https://github.com/kazeyukiro/3m-ui-docs GitHub Wiki 已同步清空（仅保留迁移指引首页） docs: 迁移至 3m-ui-docs 仓库 (Docusaurus) 文档已从本仓库迁移至独立的 3m-ui-docs 仓库，基于 Docusaurus 3 构建。 变更: - 删除 docs/ 目录（全部 18 篇 wiki 文档已迁移） - README.md 顶部添加迁移指引 新文档仓库: https://github.com/kazeyukiro/3m-ui-docs GitHub Wiki 已同步清空（仅保留迁移指引首页） docs: 迁移至 3m-ui-docs 仓库 (Docusaurus) 文档已从本仓库迁移至独立的 3m-ui-docs 仓库，基于 Docusaurus 3 构建。 变更: - 删除 docs/ 目录（全部 18 篇 wiki 文档已迁移） - README.md 顶部添加迁移指引 新文档仓库: https://github.com/kazeyukiro/3m-ui-docs GitHub Wiki 已同步清空（仅保留迁移指引首页） docs: 迁移至 3m-ui-docs 仓库 (Docusaurus) 文档已从本仓库迁移至独立的 3m-ui-docs 仓库，基于 Docusaurus 3 构建。 变更: - 删除 docs/ 目录（全部 18 篇 wiki 文档已迁移） - README.md 顶部添加迁移指引 新文档仓库: https://github.com/kazeyukiro/3m-ui-docs GitHub Wiki 已同步清空（仅保留迁移指引首页） docs: 迁移至 3m-ui-docs 仓库 (Docusaurus) 文档已从本仓库迁移至独立的 3m-ui-docs 仓库，基于 Docusaurus 3 构建。 变更: - 删除 docs/ 目录（全部 18 篇 wiki 文档已迁移） - README.md 顶部添加迁移指引 新文档仓库: https://github.com/kazeyukiro/3m-ui-docs GitHub Wiki 已同步清空（仅保留迁移指引首页） docs: 迁移至 3m-ui-docs 仓库 (Docusaurus) 文档已从本仓库迁移至独立的 3m-ui-docs 仓库，基于 Docusaurus 3 构建。 变更: - 删除 docs/ 目录（全部 18 篇 wiki 文档已迁移） - README.md 顶部添加迁移指引 新文档仓库: https://github.com/kazeyukiro/3m-ui-docs GitHub Wiki 已同步清空（仅保留迁移指引首页） docs: 迁移至 3m-ui-docs 仓库 (Docusaurus) 文档已从本仓库迁移至独立的 3m-ui-docs 仓库，基于 Docusaurus 3 构建。 变更: - 删除 docs/ 目录（全部 18 篇 wiki 文档已迁移） - README.md 顶部添加迁移指引 新文档仓库: https://github.com/kazeyukiro/3m-ui-docs GitHub Wiki 已同步清空（仅保留迁移指引首页） docs: 迁移至 3m-ui-docs 仓库 (Docusaurus) 文档已从本仓库迁移至独立的 3m-ui-docs 仓库，基于 Docusaurus 3 构建。 变更: - 删除 docs/ 目录（全部 18 篇 wiki 文档已迁移） - README.md 顶部添加迁移指引 新文档仓库: https://github.com/kazeyukiro/3m-ui-docs GitHub Wiki 已同步清空（仅保留迁移指引首页） docs: 迁移至 3m-ui-docs 仓库 (Docusaurus) 文档已从本仓库迁移至独立的 3m-ui-docs 仓库，基于 Docusaurus 3 构建。 变更: - 删除 docs/ 目录（全部 18 篇 wiki 文档已迁移） - README.md 顶部添加迁移指引 新文档仓库: https://github.com/kazeyukiro/3m-ui-docs GitHub Wiki 已同步清空（仅保留迁移指引首页） docs: 迁移至 3m-ui-docs 仓库 (Docusaurus) 文档已从本仓库迁移至独立的 3m-ui-docs 仓库，基于 Docusaurus 3 构建。 变更: - 删除 docs/ 目录（全部 18 篇 wiki 文档已迁移） - README.md 顶部添加迁移指引 新文档仓库: https://github.com/kazeyukiro/3m-ui-docs GitHub Wiki 已同步清空（仅保留迁移指引首页） docs: 迁移至 3m-ui-docs 仓库 (Docusaurus) 文档已从本仓库迁移至独立的 3m-ui-docs 仓库，基于 Docusaurus 3 构建。 变更: - 删除 docs/ 目录（全部 18 篇 wiki 文档已迁移） - README.md 顶部添加迁移指引 新文档仓库: https://github.com/kazeyukiro/3m-ui-docs GitHub Wiki 已同步清空（仅保留迁移指引首页） |
||
|
風雪
|
1c24114581 |
docs: explain Mihomo verification behavior (THREE_M_UI_VERIFY_MIHOMO)
Add section '四、Mihomo 核心的校验（说明）' to 验证Release签名.md: - Mihomo does not publish SHA256SUMS; we use GitHub Release API digest. - Three-tier verification: default (best-effort), VERIFY_MIHOMO=1 (enforce), INSECURE=1 (skip all). - Threat model: our 3m-ui binary is fully verified end-to-end; Mihomo is independent and protected by HTTPS + ELF smoke-test. Add item #11 to 安全建议.md summarizing the Mihomo verification stance. docs: explain Mihomo verification behavior (THREE_M_UI_VERIFY_MIHOMO) Add section '四、Mihomo 核心的校验（说明）' to 验证Release签名.md: - Mihomo does not publish SHA256SUMS; we use GitHub Release API digest. - Three-tier verification: default (best-effort), VERIFY_MIHOMO=1 (enforce), INSECURE=1 (skip all). - Threat model: our 3m-ui binary is fully verified end-to-end; Mihomo is independent and protected by HTTPS + ELF smoke-test. Add item #11 to 安全建议.md summarizing the Mihomo verification stance. docs: explain Mihomo verification behavior (THREE_M_UI_VERIFY_MIHOMO) Add section '四、Mihomo 核心的校验（说明）' to 验证Release签名.md: - Mihomo does not publish SHA256SUMS; we use GitHub Release API digest. - Three-tier verification: default (best-effort), VERIFY_MIHOMO=1 (enforce), INSECURE=1 (skip all). - Threat model: our 3m-ui binary is fully verified end-to-end; Mihomo is independent and protected by HTTPS + ELF smoke-test. Add item #11 to 安全建议.md summarizing the Mihomo verification stance. docs: explain Mihomo verification behavior (THREE_M_UI_VERIFY_MIHOMO) Add section '四、Mihomo 核心的校验（说明）' to 验证Release签名.md: - Mihomo does not publish SHA256SUMS; we use GitHub Release API digest. - Three-tier verification: default (best-effort), VERIFY_MIHOMO=1 (enforce), INSECURE=1 (skip all). - Threat model: our 3m-ui binary is fully verified end-to-end; Mihomo is independent and protected by HTTPS + ELF smoke-test. Add item #11 to 安全建议.md summarizing the Mihomo verification stance. docs: explain Mihomo verification behavior (THREE_M_UI_VERIFY_MIHOMO) Add section '四、Mihomo 核心的校验（说明）' to 验证Release签名.md: - Mihomo does not publish SHA256SUMS; we use GitHub Release API digest. - Three-tier verification: default (best-effort), VERIFY_MIHOMO=1 (enforce), INSECURE=1 (skip all). - Threat model: our 3m-ui binary is fully verified end-to-end; Mihomo is independent and protected by HTTPS + ELF smoke-test. Add item #11 to 安全建议.md summarizing the Mihomo verification stance. docs: explain Mihomo verification behavior (THREE_M_UI_VERIFY_MIHOMO) Add section '四、Mihomo 核心的校验（说明）' to 验证Release签名.md: - Mihomo does not publish SHA256SUMS; we use GitHub Release API digest. - Three-tier verification: default (best-effort), VERIFY_MIHOMO=1 (enforce), INSECURE=1 (skip all). - Threat model: our 3m-ui binary is fully verified end-to-end; Mihomo is independent and protected by HTTPS + ELF smoke-test. Add item #11 to 安全建议.md summarizing the Mihomo verification stance. docs: explain Mihomo verification behavior (THREE_M_UI_VERIFY_MIHOMO) Add section '四、Mihomo 核心的校验（说明）' to 验证Release签名.md: - Mihomo does not publish SHA256SUMS; we use GitHub Release API digest. - Three-tier verification: default (best-effort), VERIFY_MIHOMO=1 (enforce), INSECURE=1 (skip all). - Threat model: our 3m-ui binary is fully verified end-to-end; Mihomo is independent and protected by HTTPS + ELF smoke-test. Add item #11 to 安全建议.md summarizing the Mihomo verification stance. docs: explain Mihomo verification behavior (THREE_M_UI_VERIFY_MIHOMO) Add section '四、Mihomo 核心的校验（说明）' to 验证Release签名.md: - Mihomo does not publish SHA256SUMS; we use GitHub Release API digest. - Three-tier verification: default (best-effort), VERIFY_MIHOMO=1 (enforce), INSECURE=1 (skip all). - Threat model: our 3m-ui binary is fully verified end-to-end; Mihomo is independent and protected by HTTPS + ELF smoke-test. Add item #11 to 安全建议.md summarizing the Mihomo verification stance. docs: explain Mihomo verification behavior (THREE_M_UI_VERIFY_MIHOMO) Add section '四、Mihomo 核心的校验（说明）' to 验证Release签名.md: - Mihomo does not publish SHA256SUMS; we use GitHub Release API digest. - Three-tier verification: default (best-effort), VERIFY_MIHOMO=1 (enforce), INSECURE=1 (skip all). - Threat model: our 3m-ui binary is fully verified end-to-end; Mihomo is independent and protected by HTTPS + ELF smoke-test. Add item #11 to 安全建议.md summarizing the Mihomo verification stance. docs: explain Mihomo verification behavior (THREE_M_UI_VERIFY_MIHOMO) Add section '四、Mihomo 核心的校验（说明）' to 验证Release签名.md: - Mihomo does not publish SHA256SUMS; we use GitHub Release API digest. - Three-tier verification: default (best-effort), VERIFY_MIHOMO=1 (enforce), INSECURE=1 (skip all). - Threat model: our 3m-ui binary is fully verified end-to-end; Mihomo is independent and protected by HTTPS + ELF smoke-test. Add item #11 to 安全建议.md summarizing the Mihomo verification stance. docs: explain Mihomo verification behavior (THREE_M_UI_VERIFY_MIHOMO) Add section '四、Mihomo 核心的校验（说明）' to 验证Release签名.md: - Mihomo does not publish SHA256SUMS; we use GitHub Release API digest. - Three-tier verification: default (best-effort), VERIFY_MIHOMO=1 (enforce), INSECURE=1 (skip all). - Threat model: our 3m-ui binary is fully verified end-to-end; Mihomo is independent and protected by HTTPS + ELF smoke-test. Add item #11 to 安全建议.md summarizing the Mihomo verification stance. docs: explain Mihomo verification behavior (THREE_M_UI_VERIFY_MIHOMO) Add section '四、Mihomo 核心的校验（说明）' to 验证Release签名.md: - Mihomo does not publish SHA256SUMS; we use GitHub Release API digest. - Three-tier verification: default (best-effort), VERIFY_MIHOMO=1 (enforce), INSECURE=1 (skip all). - Threat model: our 3m-ui binary is fully verified end-to-end; Mihomo is independent and protected by HTTPS + ELF smoke-test. Add item #11 to 安全建议.md summarizing the Mihomo verification stance. |
||
|
風雪
|
b81f91cb58 |
docs: add Release signature verification guide
Add a new wiki page 验证Release签名.md covering: - Asset inventory (binaries, scripts, SHA256SUMS, cosign .pem/.sig) - Layer 1: integrity verification via SHA256SUMS (default, fail-closed) - Layer 2: authenticity verification via cosign keyless OIDC (opt-in) - Three verification modes: installer auto, manual, end-to-end example - v1.0.0 back-fill note (uses refs/heads/main identity) - FAQ (legacy releases, THREE_M_UI_INSECURE, keyless model, cosign trust) Cross-reference from: - 安装与升级.md: new '验证安装包签名（推荐）' section with cosign install + THREE_M_UI_VERIFY_COSIGN=1 usage for both install and update. - 安全建议.md: new item #10 '供应链验证' summarizing the two layers and warning against THREE_M_UI_INSECURE=1. - _Sidebar.md: add 验证Release签名 entry above 安全建议. docs: add Release signature verification guide Add a new wiki page 验证Release签名.md covering: - Asset inventory (binaries, scripts, SHA256SUMS, cosign .pem/.sig) - Layer 1: integrity verification via SHA256SUMS (default, fail-closed) - Layer 2: authenticity verification via cosign keyless OIDC (opt-in) - Three verification modes: installer auto, manual, end-to-end example - v1.0.0 back-fill note (uses refs/heads/main identity) - FAQ (legacy releases, THREE_M_UI_INSECURE, keyless model, cosign trust) Cross-reference from: - 安装与升级.md: new '验证安装包签名（推荐）' section with cosign install + THREE_M_UI_VERIFY_COSIGN=1 usage for both install and update. - 安全建议.md: new item #10 '供应链验证' summarizing the two layers and warning against THREE_M_UI_INSECURE=1. - _Sidebar.md: add 验证Release签名 entry above 安全建议. docs: add Release signature verification guide Add a new wiki page 验证Release签名.md covering: - Asset inventory (binaries, scripts, SHA256SUMS, cosign .pem/.sig) - Layer 1: integrity verification via SHA256SUMS (default, fail-closed) - Layer 2: authenticity verification via cosign keyless OIDC (opt-in) - Three verification modes: installer auto, manual, end-to-end example - v1.0.0 back-fill note (uses refs/heads/main identity) - FAQ (legacy releases, THREE_M_UI_INSECURE, keyless model, cosign trust) Cross-reference from: - 安装与升级.md: new '验证安装包签名（推荐）' section with cosign install + THREE_M_UI_VERIFY_COSIGN=1 usage for both install and update. - 安全建议.md: new item #10 '供应链验证' summarizing the two layers and warning against THREE_M_UI_INSECURE=1. - _Sidebar.md: add 验证Release签名 entry above 安全建议. docs: add Release signature verification guide Add a new wiki page 验证Release签名.md covering: - Asset inventory (binaries, scripts, SHA256SUMS, cosign .pem/.sig) - Layer 1: integrity verification via SHA256SUMS (default, fail-closed) - Layer 2: authenticity verification via cosign keyless OIDC (opt-in) - Three verification modes: installer auto, manual, end-to-end example - v1.0.0 back-fill note (uses refs/heads/main identity) - FAQ (legacy releases, THREE_M_UI_INSECURE, keyless model, cosign trust) Cross-reference from: - 安装与升级.md: new '验证安装包签名（推荐）' section with cosign install + THREE_M_UI_VERIFY_COSIGN=1 usage for both install and update. - 安全建议.md: new item #10 '供应链验证' summarizing the two layers and warning against THREE_M_UI_INSECURE=1. - _Sidebar.md: add 验证Release签名 entry above 安全建议. docs: add Release signature verification guide Add a new wiki page 验证Release签名.md covering: - Asset inventory (binaries, scripts, SHA256SUMS, cosign .pem/.sig) - Layer 1: integrity verification via SHA256SUMS (default, fail-closed) - Layer 2: authenticity verification via cosign keyless OIDC (opt-in) - Three verification modes: installer auto, manual, end-to-end example - v1.0.0 back-fill note (uses refs/heads/main identity) - FAQ (legacy releases, THREE_M_UI_INSECURE, keyless model, cosign trust) Cross-reference from: - 安装与升级.md: new '验证安装包签名（推荐）' section with cosign install + THREE_M_UI_VERIFY_COSIGN=1 usage for both install and update. - 安全建议.md: new item #10 '供应链验证' summarizing the two layers and warning against THREE_M_UI_INSECURE=1. - _Sidebar.md: add 验证Release签名 entry above 安全建议. docs: add Release signature verification guide Add a new wiki page 验证Release签名.md covering: - Asset inventory (binaries, scripts, SHA256SUMS, cosign .pem/.sig) - Layer 1: integrity verification via SHA256SUMS (default, fail-closed) - Layer 2: authenticity verification via cosign keyless OIDC (opt-in) - Three verification modes: installer auto, manual, end-to-end example - v1.0.0 back-fill note (uses refs/heads/main identity) - FAQ (legacy releases, THREE_M_UI_INSECURE, keyless model, cosign trust) Cross-reference from: - 安装与升级.md: new '验证安装包签名（推荐）' section with cosign install + THREE_M_UI_VERIFY_COSIGN=1 usage for both install and update. - 安全建议.md: new item #10 '供应链验证' summarizing the two layers and warning against THREE_M_UI_INSECURE=1. - _Sidebar.md: add 验证Release签名 entry above 安全建议. docs: add Release signature verification guide Add a new wiki page 验证Release签名.md covering: - Asset inventory (binaries, scripts, SHA256SUMS, cosign .pem/.sig) - Layer 1: integrity verification via SHA256SUMS (default, fail-closed) - Layer 2: authenticity verification via cosign keyless OIDC (opt-in) - Three verification modes: installer auto, manual, end-to-end example - v1.0.0 back-fill note (uses refs/heads/main identity) - FAQ (legacy releases, THREE_M_UI_INSECURE, keyless model, cosign trust) Cross-reference from: - 安装与升级.md: new '验证安装包签名（推荐）' section with cosign install + THREE_M_UI_VERIFY_COSIGN=1 usage for both install and update. - 安全建议.md: new item #10 '供应链验证' summarizing the two layers and warning against THREE_M_UI_INSECURE=1. - _Sidebar.md: add 验证Release签名 entry above 安全建议. docs: add Release signature verification guide Add a new wiki page 验证Release签名.md covering: - Asset inventory (binaries, scripts, SHA256SUMS, cosign .pem/.sig) - Layer 1: integrity verification via SHA256SUMS (default, fail-closed) - Layer 2: authenticity verification via cosign keyless OIDC (opt-in) - Three verification modes: installer auto, manual, end-to-end example - v1.0.0 back-fill note (uses refs/heads/main identity) - FAQ (legacy releases, THREE_M_UI_INSECURE, keyless model, cosign trust) Cross-reference from: - 安装与升级.md: new '验证安装包签名（推荐）' section with cosign install + THREE_M_UI_VERIFY_COSIGN=1 usage for both install and update. - 安全建议.md: new item #10 '供应链验证' summarizing the two layers and warning against THREE_M_UI_INSECURE=1. - _Sidebar.md: add 验证Release签名 entry above 安全建议. docs: add Release signature verification guide Add a new wiki page 验证Release签名.md covering: - Asset inventory (binaries, scripts, SHA256SUMS, cosign .pem/.sig) - Layer 1: integrity verification via SHA256SUMS (default, fail-closed) - Layer 2: authenticity verification via cosign keyless OIDC (opt-in) - Three verification modes: installer auto, manual, end-to-end example - v1.0.0 back-fill note (uses refs/heads/main identity) - FAQ (legacy releases, THREE_M_UI_INSECURE, keyless model, cosign trust) Cross-reference from: - 安装与升级.md: new '验证安装包签名（推荐）' section with cosign install + THREE_M_UI_VERIFY_COSIGN=1 usage for both install and update. - 安全建议.md: new item #10 '供应链验证' summarizing the two layers and warning against THREE_M_UI_INSECURE=1. - _Sidebar.md: add 验证Release签名 entry above 安全建议. docs: add Release signature verification guide Add a new wiki page 验证Release签名.md covering: - Asset inventory (binaries, scripts, SHA256SUMS, cosign .pem/.sig) - Layer 1: integrity verification via SHA256SUMS (default, fail-closed) - Layer 2: authenticity verification via cosign keyless OIDC (opt-in) - Three verification modes: installer auto, manual, end-to-end example - v1.0.0 back-fill note (uses refs/heads/main identity) - FAQ (legacy releases, THREE_M_UI_INSECURE, keyless model, cosign trust) Cross-reference from: - 安装与升级.md: new '验证安装包签名（推荐）' section with cosign install + THREE_M_UI_VERIFY_COSIGN=1 usage for both install and update. - 安全建议.md: new item #10 '供应链验证' summarizing the two layers and warning against THREE_M_UI_INSECURE=1. - _Sidebar.md: add 验证Release签名 entry above 安全建议. docs: add Release signature verification guide Add a new wiki page 验证Release签名.md covering: - Asset inventory (binaries, scripts, SHA256SUMS, cosign .pem/.sig) - Layer 1: integrity verification via SHA256SUMS (default, fail-closed) - Layer 2: authenticity verification via cosign keyless OIDC (opt-in) - Three verification modes: installer auto, manual, end-to-end example - v1.0.0 back-fill note (uses refs/heads/main identity) - FAQ (legacy releases, THREE_M_UI_INSECURE, keyless model, cosign trust) Cross-reference from: - 安装与升级.md: new '验证安装包签名（推荐）' section with cosign install + THREE_M_UI_VERIFY_COSIGN=1 usage for both install and update. - 安全建议.md: new item #10 '供应链验证' summarizing the two layers and warning against THREE_M_UI_INSECURE=1. - _Sidebar.md: add 验证Release签名 entry above 安全建议. docs: add Release signature verification guide Add a new wiki page 验证Release签名.md covering: - Asset inventory (binaries, scripts, SHA256SUMS, cosign .pem/.sig) - Layer 1: integrity verification via SHA256SUMS (default, fail-closed) - Layer 2: authenticity verification via cosign keyless OIDC (opt-in) - Three verification modes: installer auto, manual, end-to-end example - v1.0.0 back-fill note (uses refs/heads/main identity) - FAQ (legacy releases, THREE_M_UI_INSECURE, keyless model, cosign trust) Cross-reference from: - 安装与升级.md: new '验证安装包签名（推荐）' section with cosign install + THREE_M_UI_VERIFY_COSIGN=1 usage for both install and update. - 安全建议.md: new item #10 '供应链验证' summarizing the two layers and warning against THREE_M_UI_INSECURE=1. - _Sidebar.md: add 验证Release签名 entry above 安全建议. |
||
|
風雪
|
7dca023678 | docs: NAT and custom panel port guide | ||
|
風雪
|
e930d6905e | docs: NAT and custom panel port guide | ||
|
風雪
|
149dab30b1 | docs: NAT and custom panel port guide | ||
|
風雪
|
1e2ab3488f | docs: NAT and custom panel port guide | ||
|
風雪
|
f60c3b218f | docs: NAT and custom panel port guide | ||
|
風雪
|
5b3836f9ae | docs: NAT and custom panel port guide | ||
|
風雪
|
7dae775208 | docs: add complete user guide under docs/wiki |