The difference is that you need way more interaction. Expose a webserver on the internet and check how many requests you get from just bots.
You can control what you navigate and how to interact with the outside world, but you can’t control how the outside world will interact with your services.
Don’t expose anything from your local network to the internet (unless you want multiple new sysadmins in your house). Try tailscale instead.
WannaCry targeted hospitals, businesses and similar machines.
WannaCry targeted everything with SMB exposed, blindly.
Also, you should read more about security through obscurity, the fact that “no one will target you because you are a low-value target” is a false sense of security.
I believe the risk of running outdated software is super inflated and mediatic, 99% of people would be absolutely fine running a version of Android from 3 years ago or Windows 8.
That’s the same thing people running windows XP on internet were thinking in 2017.
Then WannaCry arrived and they got their data encrypted :)
Perhaps images, video, font etc. rendering could be compromised?
Yes, it already happen in the past. Also the Wi-Fi and Bluetooth stack got exploited, like multiple kernel drivers.
But it shouldn’t be a matter of “in the past was X exploited?” but more on having a correct security posture.
Honestly if you are arguing about wasting a “perfectly working phone” you should blame it on the vendor, especially Android devices vendors have this let’s say “defect” of dropping the support after 4/5 years.
Also not going to talk about custom ROMs (with the super rare exclusion of some) managed by god knows who, without any security team behind.
Since even the NFC and Cellular Network stack got vulnerabilities the only way you would consider an old phone “safe” to use is just turning it into the equivalent of a local ARM server.
Also pretty fun seeing the replies in the original post talking about how Google Play store shouldn’t have malware on it.
I was thinking about that just today, I have something like 30+ services running on a single compose file and maintenance is slowly becoming hard. Probably moving to multiple compose file.
Because I wanted to try if others URI schemas were supported instead of http / https. file:// was a valid one. Don’t worry, the day an attempt of data exfil will happen, you will not see it though your console logs.
Is this, by any chance, originated from the sub called ignore me?
In that case is probably my bad because is set as the image of the channel. I was playing with lemmy in the previous version and forgot about it, sorry.
I created that channel to investigate why the lemmy instance was hanging every time there was a symbol in the URL, added that URI as icon for fun and forgot about it.
That alert appears because your browser is trying to load an image with that path, nothing dangerous or remotely exploitable, don’t worry.
Edit: I removed it so you shouldn’t see the alert anymore.
P.S. no, it’s not trying to steal anything, it’s your browser trying to load that file as an image but instead of being let’s say this url: https://beehaw.org/pictrs/image/c0e83ceb-b7e5-41b4-9b76-bfd152dd8d00.png (this sub icon) , it’s this one file:///etc/passwd so you browser is doing the request to your own file.
Don’t worry, nothing got compromised.
Why Russia thinks they cooperated with Apple when the agencies can just buy 0days from the resellers?
A raspberry with Adguard + unbound, a zimaboard with truenas scale running the -arr suite, nextcloud, homeassistan, homarr, headscale and caddy 2x2TB nvme and 3x 4tb HDD I recently got a new PC and I think I will convert it to being part of the homelab, it has a ryzen 7 3xxx and a 2070 super.