this post was submitted on 27 Jun 2024
216 points (98.6% liked)
Technology
59605 readers
3345 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
I would imagine that the devices aren't making elevenlabs requests directly, but just making requests to the rabbit backend, which forwards the responses. if I'm wrong, then that's quite impressively bad security
Then wouldn't it be just one API key to the rabbit backend instead? The researchers are suggesting it's several keys though. Or are you suggesting every device has the same key to Elvenlabs that it sends over to the rabbit backend which passes that through to the request? That's also very silly if they did that.
My understanding was that they leaked the key that the rabbit backend uses to make requests to elevenlabs, and were just too lazy to change it. I could easily be wrong though
I don't think that's the case, because otherwise how did they leak this key that the backend uses, that presumably stayed in the backend, by reverse-engineering the rabbit android application?
I think the devices all just have hardcoded keys to the APIs themselves.