Nah, some MCUs have low power modes.
ESP32 has 5 of them, from disabling fancy features, throttling the clock, even delegating to an ultra low power coprocessor, or just going to sleep until a pin wakes it up again. It can go from 240mA to 150uA and still process things, or sleep for only 5uA.
towerful
joined 1 year ago
Who needs a map? It's obviously "scone".
They are clearly idiots over there
Exactly.
Communities need to be more generic until a specialisation becomes too much of the content, then a specific community should be started.
I remember my boss asking me to fit his new 1TB SSD into his computer. My jaw just dropped.
Doesn't seem like that long ago, but 2019/2020 has messed with my timeline
Yup, that would be sensible security practices.
The wrench has a web UI to program it or monitor it. It also talks a few "standardised" car-manufacturer protocols for recieving and sending instructions/measurements/certifications. And it can send also send stuff to a local history server.
The majority of the CVEs seem to exist in its onboard webUI system, with a few in the manufacturing protocols.
But yes, IoT devices should be on an isolated vlan or on pvlans. That should be standard practice.
Access from wrench->server should be via a firewall that logs connections. And access from management->wrench should be via firewall with logging.
There is no reason for unauthorized people to have access to the wrenches network, and there is no need for the wrench to communicate with anything other than the local history server.
And to then certify it's tightened to spec and send that cert to a logging server, for things like aviation
God, I hope the wrench has access to less of the network than the employee.
It's an IoT device.
You never trust IoT.
It should be on an isolated vlan dedicated to the wrenches that allows it connect to its storage server, only.
Putting the wrenches on a pvlan would further limit the scope of any breaches to a single wrench.
Any access to the wrench vlan/pvlan should be from a trusted management vlan. Any traversal of the firewall for this access should be logged.
Ultimately, this is a device being used by a company that requires per-bolt certification of torque. You can bet that every part of their process has an equivalent level of scrutiny, including certification of network security/auditing.
In fact, following sensible IoT network security mitigates all of the CVEs listed - because they need the attacker to have network access.
Sure, most of the CVEs are the stupidest "my-first-web-app" level of mistakes (csrf, xss, directory traversal) and shouldn't exist. But it's still an IoT device, and should always be treated as a black box of leaky security regardless of the manufacturer.
People are actually the easiest to hack. That's why social engineering is such a huge security risk, why employees have minimum amount of access required to systems, why corporate laptops are so locked down, and why huge phishing assessments are done.
It's just that we are more accustomed to monitoring people, and it also gives a focus that everyone understands that can take the blame for mistakes.
I think most people would just use media server software like pixera, d3, touchdesigner etc to accomplish playback of video on a moving surface with feedback sensors.
It's established tech, plenty of integrations, and most companies that are able to deliver something like this aren't a linux-first type of company.
If it was for an installation, something bespoke might be made using Linux. But the cost of touchdesigner and a suitable computer are tiny compared to doing this using Linux and then supporting and documenting it (especially considering how widespread skills in touchdesigner/pixera/d3 are in the industry Vs more esoteric Linux skills)
It's worth googling "reddit /u/username" and rechecking your post history (including changing between hot/top/controversial and different time ranges) every few months.
Googling will show up a lot of the posts/comments you have missed using 3rd party deletion tools.
Reddit caches sometimes pull older content from the database or whatever, and you get "access" to it again.
And WiFi is going the opposite direction. From 802.1a/b/ax/whatever to WiFi 5, 6 etc.
(Although the MIMO chains can get a bit more complex, but still fairly simple compared to the USB bs)
Like a survivorship bias?