this post was submitted on 05 Mar 2025
218 points (100.0% liked)

Hardware

1154 readers
296 users here now

All things related to technology hardware, with a focus on computing hardware.


Rules (Click to Expand):

  1. Follow the Lemmy.world Rules - https://mastodon.world/about

  2. Be kind. No bullying, harassment, racism, sexism etc. against other users.

  3. No Spam, illegal content, or NSFW content.

  4. Please stay on topic, adjacent topics (e.g. software) are fine if they are strongly relevant to technology hardware. Another example would be business news for hardware-focused companies.

  5. Please try and post original sources when possible (as opposed to summaries).

  6. If posting an archived version of the article, please include a URL link to the original article in the body of the post.


Some other hardware communities across Lemmy:

Icon by "icon lauk" under CC BY 3.0

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] wavebeam@lemmy.world 2 points 19 hours ago (1 children)

Isn’t the concern that if you infect a printer locally, you can use that to “pivot” to another device on that network that IS connected to the internet?

[–] AnarchistArtificer@slrpnk.net 1 points 17 hours ago (1 children)

I see your point, I hadn't thought about it this way. I think what you're suggesting is this:

           |                        |
           |          rest of LAN <-/
[–] wavebeam@lemmy.world 1 points 16 hours ago

I don’t really understand your snippet. But yeah i think the issue with IoT devices having connection to any other network device at all is that if they have a security hole that can be exploited through a malicious USB drive or BT or any other compromised device it can connect to, that it can act maliciously in a number of ways. The only true security for devices that can’t get patched is a complete air gap for any connected devices.