• fubarx@lemmy.ml
    link
    fedilink
    English
    arrow-up
    33
    arrow-down
    1
    ·
    5 months ago

    Many years ago, folks figured out how to crack firmware and find embedded keys. Since then, there have been many technological advances, like secure enclaves, private/public key workflows, attestation systems, etc. to avoid this exact thing.

    Hopefully, the Rabbit folks spec’d a hardware TPM or secure-enclave as part of their design, otherwise no amount of firmware updating or key rotation will help.

    There’s a well-established industry of Android crackers and this sort of beating will keep happening until morale improves.

  • LainTrain@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    13
    ·
    5 months ago

    What I don’t understand is why the TTS key could even delete voices or read past responses from other devices, ideally each device should have its own properly scoped API key that only lets it access the immediately necessary functionality and no more.