I never authorized an integration that scans my secrets(github.com)
239 points by trvrprkr 9 days ago | 221 comments
tl;dr: A Home Assistant user discovered that the Supervisor automatically checks configured passwords against Have I Been Pwned without explicit opt-in, and filed an issue requesting it be opt-in. Maintainer Frenck initially dismissed the complaint—noting the check uses k-anonymity (only a 5-char SHA-1 prefix leaves the system)—before locking the thread, then later apologized and clarified it can be disabled via `ha security options --pwned=false`, promising to update the docs.
HN Discussion:
  • ↑Any data transmission to third parties, however safe, requires explicit opt-in consent
  • ↑Maintainer acknowledges dismissiveness, apologizes, and clarifies the opt-out mechanism exists
  • ↑This incident reflects a broader pattern of toxic developer behavior in the project
  • ↑k-anonymity schemes actually leak meaningful signal to attackers, so the 'mathematically safe' defense is weak
  • ↓Decisive maintainers rejecting entitled user complaints is defensible and produces better software