Chrome's geolocation fails daily due to API limit

Re:Chrome's geolocation fails daily due to API limit by wehere1 on Tuesday August 08, 2017 @09:45PM (#14964849)

you posted this in the chromium thread too and ... it's not relevant

[ Parent | on HN ]

Re:Chrome's geolocation fails daily due to API limit by berg43w2t3t on Wednesday August 09, 2017 @12:53AM (#14965644)

I think it might be relevant, this seems to indicate that google is hardcoding their API keys in the shipped chrome binaries. These exceeded, and broke functionality in the app. This seems like a bad security practice and it is very relevant to call it out here.

[ Parent | on HN ]

Re:Chrome's geolocation fails daily due to API limit by NateyJay on Wednesday August 09, 2017 @01:16AM (#14965734)

There's really no practical alternative but to ship binaries with baked in API keys.

Maybe you dynamically provision API keys, but the binary needs a baked in permission to access that API to start with...

[ Parent | on HN ]

Re:Chrome's geolocation fails daily due to API limit by captn3m0 on Wednesday August 09, 2017 @01:37AM (#14965820)

so every release goes out with its own API key?

[ Parent | on HN ]

Re:Chrome's geolocation fails daily due to API limit by dbbk on Wednesday August 09, 2017 @06:50AM (#14967308)

Well, they're obviously going to have to hardcode something into the binary, I think you're imagining an issue that doesn't exist.

[ Parent | on HN ]