HaJ3FgupAm8RrDJW3MHgT9X7Ft27eVaD
If you think for about two seconds about the national security implications about this, this is extremely, extremely bad.
You’re right, but Flock (and all of these cameras) is bad for the liberty of the people, so this is good. Any time a national security threat is found, it shakes the trust in these systems, so they’re less likely to be trusted again.
The worst thing is that this isn’t exactly new. The house heard about the vulnerabilities of this system in May.
https://www.youtube.com/watch?v=VKSjlZ6xyDo
Unfortunately, we’re in such a state of plutocracy and regulatory capture that even stating how big of a national security risk they are did not make any movement until now.
I’m going to go as a functional Flock camera for Halloween.
So you’re wearing Meta glasses?
don’t look surprised when someone in a hockey mask cuts your legs off at the knees with a chainsaw.
🎶 When you get knocked down, don’t you get up again. We’re all trying to keep you down.
damn that’s good
Why are you linking to bluesky instead of his article?
We are soon to find out if Flock blindly onboards random MAC addresses as new cameras.
If so, it seems anyone with the hardcoded key can authenticate with Flock ask if they were a new camera.
I wonder if that means you could “claim” a bunch of MAC addresses so you can block deployment of new or replacement flock cameras.
And it doesn’t have to be a camera. It can just be a random set of images.
It can be
Gasp
Can it pretend to be information about me, but then instead it’s all butt holes?
¿Porque no los dos?
Because mine is secretive 😶
OMG that user handle.
They are always very specific when saying that Flock cameras do not do face recognition. Vecause stated like this it’s true. The face recognition doesn’t happen on the camera (also not license plate reading etc.) instead photos are sent to central servers where they do the license plate reading and face recognition.
Just a random string of characters:
HaJ3FgupAm8RrDJW3MHgT9X7Ft27eVaD
Is that the token?
Ah yes, yes it is.
Get it, freedom fighters! 🤘🏼✊🏼
Keeps getting better
I wonder if this was a form of sabotage by an engineer, or regular incompetence
Hanlon’s razor:
Never attribute to malice that which is adequately explained by stupidity.
But, also, Grey’s law:
Any sufficiently advanced incompetence is indistinguishable from malice.
I’d like to live in a world in which the former is the case, but as an engineer I have seen some shit
Lmao
Quick question: what would be the correct way to handle this, security wise? How should they acquire their token if it isn’t present on-device?
I mean, each device could have its own token, but you could still sniff it, maybe? I dunno.
How should Flock have gone about this if working to their own self-interest?
One way would be to generate a unique private key on the secure element / TPM and its public key stored on the server for validation. Each API request would need to be signed with a relatively short expiration time. That way the code never contains sensitive content such as an API key, an exploited device only holds in RAM a signed certificate that is valid for a short period of time, and the certificate can be revoked/blocklisted on the server if compromised.
Ethically? Expire the token since it’s compromised, and offer to refurbish all units in the field since flock screwed up, a now all customer data could be poisoned/suspect now.
Realistically? Keep going like nothing happened an make it a customer support problem while pushing new hardened cameras that cost more. Because the product alone loudly flags Flock as a bunch of amoral greedy fuckwits.
I won’t suggest ways to actually make their product bulletproof because I care and we don’t need to make this problem worse for everyone. It is a tantilizing problem space but there are never any perfect answers in security, only relatively better/worse ones.
Oh, I don’t mean afterwards. I meant before it even happened.
y’all just givin the work away huh? don’t answer this unless you are getting paid.
O… Kay, I’m just trying to expand my knowledge about this particular case. I’m mostly a web dev but I’m trying to expand into security a little bit as well because I think that’s important for my field. It just wasn’t a part of my curriculum at uni 10–20 years ago.
i was mostly joking 🙃 sorry if it came across as rude
Unique private key per device, pre-provisioned certificate at manufacturing time, hardware-level separation of crypto operations so sensitive creds are never in memory.
It’s a bit more expensive to manufacture, in terms of BOM and logistics. And then you have a lot more complexity to your production system too.
Is it possible to have several private keys per singleton public key?
No.
