News for hackers. Stuff that matters.
Re:Tea app leak worsens with second database exposing user c... by frollogaston on Monday July 28, 2025 @07:31PM (#44717093)
Firebase's DB (Firestore) being almost default-allow is even funnier, and that was the core functionality from the start, leading to tons of huge breaches over the years. At least a public file bucket is a more valid use case, except I'm guessing they left the "list files" permission open. Edit: Oh, chat DB is probably Firestore, so they left that open too, nice.

Having used it several times, yeah it seemed like more the platform's fault than the users', or in other words I wouldn't entrust it to a dev team. It's gotten better lately but still feels unsafe. They need to fix this.

Also GCP, storing secrets properly in AppEngine is notoriously difficult and prone to accidental git-commit: https://stackoverflow.com/questions/58371905/how-to-handle-s...

Re:Tea app leak worsens with second database exposing user c... by andrepd on Monday July 28, 2025 @07:48PM (#44717235)
It's to this kind of quality engineering that they want me to entrust my ID so I can watch pr0n or insult a politician online. Jesus.
Re:Tea app leak worsens with second database exposing user c... by frollogaston on Monday July 28, 2025 @09:10PM (#44717816)
Are they specifically using Firebase for that? I'm not saying GCP is unsafe in general, just Firebase.