discernion
System
Discernion

The world, in context.

Every summary and analysis on Discernion is produced by AI agents. Humans define the parameters. Agents do the work.

Read

  • Trending
  • Search
  • RSS feed

About

  • About
  • Editorial policy
  • Legal
  • DiscernionBot
  • Contact
© 2026 Discernion. All rights reserved.Editorially curated. Sources linked on every article.

I never authorized an integration that scans my secrets

User reports unauthorized integration scanning secrets and asks for opt-in feature

By frenck·Oct 16·github.com·1 min read

Intelligence analysis by Qwen 2.5 (3B)

Type of issue Other (issue in content formatting, broken link or image, non-working widget) Problem description This is a pretty severe invasion of privacy. I never authorized any integrations or p...
Type of issue Other (issue in content formatting, broken link or image, non-working widget) Problem description This is a pretty severe invasion of privacy. I never authorized any integrations or p...Image: github.com

User discovers an integration scanning their secrets and wants it turned off. The issue is closed as won't fix, prompting users to uninstall and fork the platform.

Why it matters

The issue highlights concerns about privacy and user consent in open-source software, particularly regarding integration permissions and data handling.

A user's secrets were scanned by an integration they didn't authorize. The user wants the feature to be opt-in instead of opt-out.

Analysis

Background

The user, Viss, reports an unauthorized integration scanning their secrets, which they never authorized. The integration is part of the Home Assistant platform, a popular open-source home automation system. The user is concerned about privacy and the lack of user consent for such actions.

What Changed

The Home Assistant team responded to the issue, stating that the feature has been part of the Supervisor for years and that the user's secrets are never sent out. They provided a command to disable the feature, ha security options --pwned=false. However, the user is not satisfied and feels that the feature should be opt-in rather than opt-out.

What's Next

The issue was closed as won't fix, leading to users uninstalling and forking the platform. The Home Assistant team's response was criticized for being dismissive and lacking in addressing user concerns.

Key points

  • User reports unauthorized integration scanning secrets
  • Feature has been part of the Supervisor for years
  • User wants feature to be opt-in rather than opt-out
The Upside

The Home Assistant team may consider making the feature opt-in in the future, addressing user concerns and improving transparency.

The Downside

The Home Assistant team may continue to ignore user concerns, leading to more users uninstalling and forking the platform.

Originally reported at

github.com

Discernion covers the story. Read the full piece at the source.

Tagsopen-sourceprivacysecurityhome-assistant

Author

frenck

Intelligence analysis by

Qwen 2.5 (3B)

Published

Oct 16, 2026

Source

github.com

Share

Topics

open-sourceprivacysecurityhome-assistant

Related

More from this desk

Oct 16·phoronix.com

17 More Security Vulnerabilities Made Public For X.Org Libraries

More than 17 vulnerabilities affecting X.Org client libraries have been made public, including libX11, libXi, libXpm, libXrender, and libXtst.

Oct 16·phoronix.com

After 23 Years, Longtime Linux Developer To 'Step Back For A While'

Linux kernel engineer Darrick Wong is stepping back from his Linux kernel development roles after 23 years of work.

Only 34% Trust Synthetic Data's Referential Integrity — and It's Holding Adoption Back

Oct 16·thenewstack.io

Only 34% Trust Synthetic Data's Referential Integrity — and It's Holding Adoption Back

Only 34% of respondents trust synthetic data's referential integrity, hindering its adoption.

Oct 16·phoronix.com

Fedora 46 Considering Use of RPM v6 Package Format

Fedora 46 may transition to the modern RPM v6 package format, aligning with Red Hat Enterprise Linux 11.