this post was submitted on 29 May 2026
48 points (94.4% liked)
Technology
84996 readers
3492 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That doesn't really seem likely to happen on its own. I'm pretty sure that most IoT devices phone home and upgrade themselves (which, frankly, I'd be maybe more-concerned about as a vector than a lack of updates, since anyone can buy a defunct IoT maker and thus get control of all those devices, or penetrate the IoT maker's network) and I imagine that most people have no idea when a device has last been updated.
You can maybe have some sort of network protocol where devices can report their last update. That'd maybe permit for auditing that, if you had a device that would tell a user about an outdated device, which isn't really the case today. Also kind of hard to tell an end user what a device at IP address X is. If they're on the same Ethernet segment, maybe could try to identify it by OUI on the Ethernet MAC address, I guess, but that's not going to give you a convenient helpful-to-most-end-users product ID for a lot of devices. So if your audit program sees a device on the network that doesn't implement the "last updated" protocol, it may have a hard time identifying it to you in human terms.