documenting like this is also really good for future reference
Comment on Absolute disaster, RAT backdoored through WINE. Assistance with Docker
TropicalDingdong@lemmy.world 1 day agoYeah. As an aside, including heat you’ve written here, it would be good for you to document what went wrong, how you identified things going wrong, and how you ultimately resolved it, so we can all learn and maybe get something from this other than the pain you are experiencing.
Homelabbing is a command we really only have each other
Jumuta@sh.itjust.works 1 day ago
ushjftye@programming.dev 1 day ago
I didn’t own the network, that was the problem. My distro has security updates still, everything comes from repositories. I didn’t containerise everything. That was my fault. WINE had network access and filesystem access and it wasn’t in a container, and the password to the router was plain text. Absolutely chilling, finding the root /run/. 128TB man. I use clamav and it identified winexpiro hidden in a .DLL called .BRM. Supposedly for Windows 6. WINE is just a compatability layer, so you can push any .DLL into it. This is why I NEED to learn commandline docker, because it’s just not fucking safe. I don’t know whose machine it got to first, but once you’re connected to a machine as admin that’s connected to a router as admin. Like Fuck me.