they are using VERY old Thinkpads, and they have some (looks like 30 years old) servers in the back of their IT department, but we as students are not allowed to see them
reworded it
well, we are not allowed to exactly go so in deep of their "IT room" to see their servers but form my observations they hvae few very old thinkpads and their servers look 10-20 years old.
I've just been using Openbox since it's lightweight in comparison to the DEs I'd tried.
You're not using any DE with it, just straight up Openbox? What kind of specs does your machine have?
i5 + 16GB of RAM + Intel HD graphics. Performance-wise, the DEs I tried were fine, but they drained my laptop's battery pretty fast.
Which DEs did you try? I've never considered the battery aspect of a DE. Did you try XFCE and LXDE?
Cinnamon, GNOME, MATE and LXDE. LXDE was fine but I didn't like the file manager that it came with and how some programs here and there would open that one by default even if I had another one installed and set up so it was supposed to be used by default.
That's odd. LXDE itself shouldn't, I don't think, come with a file manager. Was it just that you installed Lubuntu and whichever other distros came with those DEs preinstalled?
I might actually have been thinking of what happened with MATE, my memory kinda sucks. If it did come with a file manager, then I probably didn't bother to think of trying to remove it at all since the other DEs I've used rely somewhat on the file managers that they come with.
did you try Enlightenment? did you try Mate 1.18?
did you try GNOME on Wayland? it is supposed to perform better than normal x11 in performance & power aspects.
Nope, I only tried what was the latest release of MATE at the time (which was a few months ago).
Actually, no, that's not how it'd work. Only the Wine prefix would be affected provided it'd even run. In this case it'd be "/root/.wine/dosdevices/c:@/Users/<username>" since in your scenario it was ran with sudo, but that's not necessary to execute malware. Anyway, no harm done whatsoever.
this askubuntu post contradicts what you stated...
He had those affected folders symlinked to his Wineprefix. Pretty easy to avoid.
Windows malware can't because it treats the prefix as a Windows drive. It doesn't know it's being ran with Wine.
wait, but i thought this malware affected all drives connected, and the "/" is available as a drive, right?
No. The malware can't see anything above the emulated C: drive. Like I said, it doesn't know it's being ran through Wine. Wineprefixes are essentially sandboxes, and you can even have more than one with different architectures and Windows versions setup at the same time.wait, but i thought this malware affected all drives connected, and the "/" is available as a drive, right?
WINEARCH=win32 WINEPREFEX=$HOME/.wine32 winecfg
