Hacker News

Not exactly what you have asked for, but ESP32 based M5Stack and Seeed Xiao modules might fit the bill. They are not so expensive, are Linux-free, and there's no report so far of secret ping home features in the SDK.

You can get close.... I guess...

Some cameras do support thingino, so you can override their firmware. Then there's this: https://openipc.org/supported-hardware/featured

There is also https://thingino.com/ which has a clear set of supported cameras. The installation is straight forward if you choose a cam with SD-Card flashing support. I upgraded two of the Sonoff Slim Gen2 without any issues.

Seems like the shop is broken?

> Stránka nenalezena

> There's been a glitch...

> We're not quite sure what went wrong. You can go back, or try looking on our homepage.

ESP32-CAM

I wish... The best I've found is https://openipc.org/ which is a very manufacturer unsupported way of reflashing certain chips with open-source firmware. It seems very fiddly as only certain SoCs are supported and good luck finding out if a specific Chinese camera has one.

Thank you. Ordered one to play around and see if this is a viable alternative.

I do know of at least one company who has black-holed the entire DoD ip space and are using it for internal space, which is why I gave a speculation warning... it's really strange regardless.

> Note to self: never buy a Korean security product.

The Canadian Navy very recently made a major choice and agreed with you

https://www.google.com/search?client=firefox-b-d&q=hanwha+oc...

just buy stuff you can put your own firmware/os on because it's either just the worst security in the world (aka anything not from china) or, well... china.

and while i currently don't hate china as much as i do US rn (because canadian; sorry) i can also say -- due to being an aforementioned leaflandian -- that due to very personal experience i have zero faith in anything from china that has the ability to connect to any type of network :')

And so yeah at this point if I can't at the very least get a whatever-wrt firmware (preferably a proper linux distro nowadays; not to say the *-wrt firmwares aren't a real OS but, y'know) on the device i just avoid them entirely since, well... it's all i can do at this point because even if there were baked in hardware-based backdoors i as an individual can't do much more than that.

The DoWD owns such a large chunk of the IP space, it can very easily be a coincidence

Or Korean IoT products. The ones I was working on had insane approach to security.

As if domestic products aren't a hot mess of security issues and sloppy engineering. Lol

Note to self: never buy any Korean hardware or software product.

/S

> Department of War

n.b., it's the Department of Defense, just like the Kennedy Center doesn't have Trump's name attached, and the large body of water by Texas is the Gulf of Mexico.

As they say: in IoT the S stands for security.

There’s some irony to security not being a priority for security cameras. Different kind of security I know, but still.

How can there be a baseline check when you operate by getting the most inexperienced cheapest person possible to do the work?

Especially these days there’s really no excuse

Add a skill to your repo that does some basic checks at least, not that hard

how did "same MAC" lead to "access to everything"?

Was the website's security based on MAC, which presumably is supplied by the client? If so, I guess.. typical IoT.

The CSS selector they used (`a[href*="://"]::after`) is meant to only target only external links, but assumes any internal links will be using relative paths like `href="/about"`. The problem is that this site uses absolute URLs (`href="https://hhh.hn/about"`) for its nav links, so every link ends up with an icon.

You could fix this by adding an exception to the CSS rule so it skips links starting with your site's name:

  a[href*="://"]:not([href^="https://hhh.hn"])::after

will fix it tomorrow

And it's worth considering that obfuscation only ever worked against casuals for whom tedious was a bridge too far. Nation state actors and criminal hacker groups, on the other hand, consider the tedious entirely worth it.

On the bright side, even a small local LLM can easily improve garbage code like that.

There's a lot of public keys that don't give you any special access, unless the dev is really bad.

Anyone who cares about security will be using App Attest or the Google store equivalent.

Another rule of thumb - i know it's not always the best since some products are really nice aesthetically - is to buy only local smart stuff, for example, zigbee/zwave.

In many cases it is bad to publish this info because they might come after you. There used to be a company who shielded the “researcher” from the legal consequences, can’t remember the name though.

Everything can be controlled without a proprietary app. Hope you reverse engineer the protocol and publish how to do it.

Have you actually tried to do anything with them though? The keys are in there, but may not grant you any real extra access beyond what your user is actually allowed to do via the app.

Who hurt you? It's his own blog. Let him write the way he wants.

No, if you read the article the author was downloading firmware from their website and still found the token.

Abusing IP ranges which were assigned to an organization but aren't actually used on the public Internet as private addresses is pretty common. Sure, it's bad practice, but not a big deal.

Oh I thought exactly the opposite!

I feel like every security blog (or even just tech blog) I've read recently has had paragraphs and paragraphs of largely LLM generated explainer waffle. This felt refreshingly focused and to the point.

i’m not a mastermind, and I agree it could be more accessible. I treat this blog as somewhere to just dump my thoughts as unfiltered as I can while still being useful or entertaining, maybe for some other posts I will go more into depth

Seemed perfectly reasonable to me. Not everything has to be written for a target audience that includes you, besides you were able to look up what you needed it seems. Another tactic is to feed the article to your favorite LLM and interrogate it about what you don't understand.