Remove plaintext audit dataset keys from model-owner CLI output

未关闭
  • 哪里不对？
#328 5 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@0xzoz 已经在做这个了。

开始于 2026年11月12日。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
58/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
python
领域
cli, security

调研方向

Start with the logging call in dincli/cli/modelownerd/auditor_batches.py lines 309–311 and the returned object in cache_model_1/services/modelowner.py lines 247–263. Review adjacent audit and dispute paths for similar logging, then capture success, retry, and failure CLI output with synthetic key bytes. Done means logs retain batch counts and public CIDs without exposing keys, while encryption and decryption still work.

由索引模型根据 Issue 内容生成。

描述

Approved

Observed against ed175d0deceddfa2e63175ec7752c800b31c1fbf during the November 10 Fashion-MNIST local test investigation. The subsequent full round with three notebooks and a Raspberry Pi used recorded workarounds; its success does not establish that this upstream defect is fixed. Related: #276 and #40.

Problem and evidence

create-testdataset prints the complete audit_testDataCIDs result. The reference service includes K, the raw 32-byte AES key, in each item. Consequently normal CLI output includes the decryption keys as well as ciphertext CIDs.

Our experiment removed this output before collecting shareable evidence. An additional focused reproduction used synthetic key bytes and the same Rich logging call: the key was present in captured output. No real key is needed in an issue or regression test.

Someone with access to such logs and the ciphertext can decrypt the batch without the intended auditor-specific key delivery. This is a log-access exposure, not evidence that an unauthenticated remote user can obtain the logs. Our dataset was public Fashion-MNIST; we did not demonstrate a leak of a private production dataset.

Proposed scope

Replace the raw object dump with an allowlisted summary such as batch count, batch index and public CID. Keep K available internally for encryption, but exclude it from normal/debug output and exception diagnostics. Review the adjacent audit/dispute paths for the same logging pattern.

Acceptance criteria
  • Success, retry and failure output do not contain a synthetic key in bytes, hex or base64 form.
  • Batch counts/CIDs remain available for diagnosis.
  • Auditor key encryption and dataset decryption still work.
  • Tests capture CLI output, rather than merely checking that one print statement was deleted.
Full-round test report

See Discussion #331 — Fashion-MNIST with three notebooks and a Raspberry Pi for the setup diagram, completed protocol roles, results and experiment adaptations.

主要语言
Python
星标
4
派生
7
平均合并
5 天 15 小时
30 天内合并 PR
43

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

InfiniteZeroFoundation/DevNet 的其他 Issue

查看 InfiniteZeroFoundation/DevNet 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。