this post was submitted on 23 Sep 2024
1343 points (97.3% liked)
People Twitter
5283 readers
2417 users here now
People tweeting stuff. We allow tweets from anyone.
RULES:
- Mark NSFW content.
- No doxxing people.
- Must be a tweet or similar
- No bullying or international politcs
- Be excellent to each other.
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
Last I checked the only fully open stuff is one manufacturer's IBM power 9 workstation and several Chromebooks
Is it better in embedded stuff? Last openWRT device I ran needed a closed binary for network
There's still some various binaries. E.g. the expressif sdk generated code. However, it's far harder to sneak something nasty into it.
Codespace is at an extreme premium on microcontrollers. Kb, and even bytes matter. A big, complex bit of malware would take significant space, likely enough to be noticed quickly.
As for smaller, simpler malware, this is a possibility. However, due to their nature, microcontrollers get a lot more scrutiny of their outputs. Random data dumps to an unexpected external address would be caught VERY quickly.
This is compounded by the fact that it's not uncommon, at least in larger installs, to segregate IoT devices from the main network. It stops them cluttering it up, and slowing it down. This makes it easy to firewall off the network from the Internet. They can talk to each other, and the central coordinator, but only the coordinator can see the internet, unless explicitly allowed.
If my network were compromised via my smarthome setup, my first suspects would be the debian PC running home assistant, or my ubiquiti router. I've at least reduced my target area to business grade networking kit and a single Linux server. I'm not an impossible target, but far from a soft one.