Chronographs@lemmy.zip
on 06 Aug 2024 18:48
nextcollapse
TL;DR people don’t update their shit
wreckedcarzz@lemmy.world
on 06 Aug 2024 20:06
nextcollapse
surprised Pikachu face
admin@sh.itjust.works
on 06 Aug 2024 22:19
collapse
Also: vendors don’t update their shit.
jet@hackertalks.com
on 07 Aug 2024 05:56
nextcollapse
If you have a internet attached device and it isn’t getting systematic and timely updates, you have a time bomb. Doesn’t matter who made the device initially
Ubiquity has patched the issue identified in the article, people have these devices deployed and they are not patching them…
Alphane_Moon@lemmy.world
on 08 Aug 2024 05:36
nextcollapse
This is why I avoid opening up “service” devices to the broader internet.
My current work around is to access a computer with TeamViewer on a given local network and manage things from there. There are probably flaws with this approach too, but it seems like a more manageable solution than giving IoT-type devices access to the open internet.
I do wonder if protocol like Yggdrasil would be a good solution in the future.
LibreHans@lemmy.world
on 08 Aug 2024 17:00
collapse
threaded - newest
TL;DR people don’t update their shit
surprised Pikachu face
Also: vendors don’t update their shit.
If you have a internet attached device and it isn’t getting systematic and timely updates, you have a time bomb. Doesn’t matter who made the device initially
Ubiquity has patched the issue identified in the article, people have these devices deployed and they are not patching them…
This is why I avoid opening up “service” devices to the broader internet.
My current work around is to access a computer with TeamViewer on a given local network and manage things from there. There are probably flaws with this approach too, but it seems like a more manageable solution than giving IoT-type devices access to the open internet.
I do wonder if protocol like Yggdrasil would be a good solution in the future.
That’s why I have firewalls 🤷🏻♂️