kajer (@[email protected])
infosec.exchange
So, uh, @[email protected] has been sending partial hashes of any password it can find up to `Have I Been Pwned` for 5+ years. Only recently did they fix the display / warning to actually do something and alert on API hits. This ""feature"" is on by default, and requires console/CLI commands to disable. @[email protected] - Do better. This should be an integration like the default weather app. This should be entirely optional by users and not hidden away in the python sub-basements of the HA backrooms. disable with `ha security options --pwned=false` in a console https://github.com/home-assistant/home-assistant.io/issues/49314

Heads up, if you use home assistant, any credentials in your config have been hoovered up without your knowledge

  • frongt@lemmy.zipEnglish
    0·
    3 days ago

    No, your credentials have not been “hoovered up”. A hash is not reversible, and a partial hash would match far too many potential passwords to be any more accurate than random guesses.

    Still, uploading any data, especially identifying data, should absolutely not be enabled by default.

      • socphoenix@lemmy.worldEnglish
        0·
        3 days ago

        This is such a nothing burger, they’re using those first five to get partial matches then doing the actual checks locally on the hash…

        To be transparent: this check isn't new, it has been part of the Supervisor for years. It checks app options that are marked as passwords. A recent release fixed the warning that surfaces it, which is why you're seeing it now. Privacy was a design requirement for this feature from the start, which is why your secrets never leave your system. The Supervisor hashes them locally and sends only the first 5 characters of the SHA-1 hash to Have I Been Pwned. HIBP returns every hash starting with that prefix, and the matching happens on your own instance. You can see exactly what it does here: https://github.com/home-assistant/supervisor/blob/main/supervisor/utils/pwned.py. You are right that our documentation should have explained this, including how to turn it off. We'll get that page updated. ../Frenck

    • StarkZarn@infosec.pubOPEnglish
      0·
      3 days ago

      They have been hoovered up, by home assistant. I made no claim, nor did the source, that clear-text credentials were shipped anywhere.

      This is meant to drive awareness on a transparency and dev issue, not an overt compromise. My language was maybe a bit too inflammatory though, I suppose.

      • AvocadoSandwich@eviltoast.orgEnglish
        0·
        3 days ago

        So for as far as I understand it:

        Yes, this is a big issue on the developers part as this should not have happened without consent.

        No, this is not a direct security breach for every and all home assistant users. You do not need to immediately change all your passwords (due to it being partial hashes)

        Did I understand correctly? I’m not that deep into how all this works as I am mostly a enthusiast user without a lot of computer science knowledge

        • curbstickle@anarchist.nexusMEnglish
          0·
          3 days ago

          No to both.

          Its a long-standing and documented feature. Included in that documentation is how to turn it off, which was added a few years back iirc.

          Its brought up every once in a while by people.who don’t understand cryptographic hashes or the hibp tools. Usually with a bunch of posts about how passwords are being leaked (they aren’t).

      • Saiwal@utsukta.org
        0·
        3 days ago

        yes, the phrasing makes it sound like a major security breach. not your fault though, we’ve been conditioned to click bait for years now.