4 ms·
Ah yes, a new take on the botnet-as-a-service genre. Running untrusted code, even inside a container, is a terrible idea. Container escapes get discovered all
by jeroenhd 5y ago
Ah yes, a new take on the botnet-as-a-service genre.
Running untrusted code, even inside a container, is a terrible idea. Container escapes get discovered all the time and even without them you could get yourself in serious trouble with the police by just letting random people use your network. Sure, you'll be able to defend yourself in court, but nobody has time to go to court over this stuff.
If you run this inside a VM with a PCIe paasthrough and all network traffic tunneled through some kind of VPN then maybe it's worth the effort, but I just wouldn't risk it.
- winrid 5y agogood luck getting your hardware after it was confiscated, too.
- cinntaile 5y agoWhy bother though, the number of machines you can hack is very limited.
- judge2020 5y agoThe threat is using your IP address to do illegal stuff (read: serve/proxy CSAM).
- jeroenhd 5y agoThese decides have their performance and internet connection uplink listed, which make for very interesting targets. Yes, a hundred shitty smart scales are a nice target, but they're underpowered for more involved attacks. With a fiber uplink, a decent CPU and plenty of disk space advertised, this service can be very attractive, especially since you only need to pay for a minute to escape the boundaries of the container runtime if there's an exploit. Also, it doesn't matter that there's only a few computers if you're using other people's computers to break the law.
- deleted 5y ago[deleted]
- aaron695 5y ago