Remove plaintext audit dataset keys from model-owner CLI output

Offen
  • Stimmt etwas nicht?
#328 5 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@0xzoz arbeitet bereits daran.

Seit 12.11.2026.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
58/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
python
Bereich
cli, security

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Python
Sterne
4
Forks
7
Ø Merge
5 T. 15 Std.
Gemergte PRs (30 T.)
43

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus InfiniteZeroFoundation/DevNet

Alle Issues in InfiniteZeroFoundation/DevNet

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.