Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Minimize identifying metadata in local logs and third-party journal output

Aperta
  • Qualcosa non va?
#63 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
linux, shell
Ambito
observability, security

Direzione di ricerca

Start by reviewing the log calls in bin/hermeskey and the logging setup in bin/hermeskey-server.py, then read docs/TROUBLESHOOTING.md. Add tests using synthetic marker IDs, paths, and source names across normal and failure paths, including captured service journal output. Done means logs contain only allowlisted status fields, and the troubleshooting guidance accurately states what is and is not logged.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug privacy

Privacy finding (v0.6.0 / main at 12e1fb3)

The speech server sanitizes its own exceptions (#48), but the hotkey runtime log still records active/target desktop IDs, resource classes, window UUIDs, microphone source names, and runtime paths (bin/hermeskey: focus_is_safe, insert_text, record_start, and error branches). Even if no transcript or window caption is logged, these fields reveal which apps/devices a user was using and can contain user-specific path fragments. bin/hermeskey-server.py also sets root logging to INFO, allowing third-party model/downloader log messages into the user journal without a HermesKey redaction boundary. No raw transcript leak in the journal was established by this audit.

Expected

Privacy-safe diagnostics with explicit allowlisted, non-content status fields. Avoid persisting app identities, window UUIDs, device identifiers, absolute paths, third-party exception strings, request contents, audio or transcripts. Keep useful error codes and timestamps. If extra diagnostic detail is ever needed, make it opt-in, bounded, local and clearly warned before sharing.

Acceptance

  • Review all log calls and third-party logger levels; replace identifying fields with category/reason codes.
  • Test with synthetic marker desktop IDs, paths, and source names; assert none appears in runtime logs or captured service journal under normal and failure paths.
  • Align docs/TROUBLESHOOTING.md and support guidance with exactly what is and is not logged. Do not paste real user logs into this public issue.
Lingua principale
Shell
Stelle
0
Fork
0
Merge medio
27m
PR unite (30g)
21

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di graygarbage/HermesKey

Tutte le issue di graygarbage/HermesKey

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.