Ye no. If i made malware for windows that goes over all reported drives wine will just happily translate that. Hell, by default wine will map root as z: so no, wine/proton will not help.
Even wannacry was able to cause some damage to linux if ran through wine
Thanks!
That’s very useful to know - I’d have assumed it can only see it’s own files within the wineprefix folder.
It looks like trying Steam within flatpak, and limiting the flatpak’s access might offer some protection.
Or maybe getting stem to run as a different user.
My uneducated guess is that it would run inside the prefix but would have troubles with basic Windows dependencies not availiable/running, prefix’s folder structure being cut down to the most basic components and barebones, and that nothing actually runs like in Windows but is rather translated from Linux commands to Windows one and back? Meaning there’s no processes or services like in a VM, no way to run cmd or powershell scripts, nothing to steal without leaving containment? Am I wrong somewhere?
I recall there was a wave of dread about Proton leaving host system easily accessible and not implementing any security measures as they are out of scope, but if we assume it’s a virus targeting Windows, I’m half sure it would have troubles doing anything the usual way.
Hey PieFed user, posting a 5-minute meme video where the guy struggles to make a custom virus do something through Proton isn’t the own you think it is. It literally corroborates my point. Windows viruses and malware will not work through Proton.
laughs in proton
Proton does not protect you from harm. It’s not a sandbox.
No but it also doesn’t have windows on the other side, someone would have to target a proton setup to get much of anything.
Ye no. If i made malware for windows that goes over all reported drives wine will just happily translate that. Hell, by default wine will map root as z: so no, wine/proton will not help.
Even wannacry was able to cause some damage to linux if ran through wine
Thanks! That’s very useful to know - I’d have assumed it can only see it’s own files within the wineprefix folder.
It looks like trying Steam within flatpak, and limiting the flatpak’s access might offer some protection. Or maybe getting stem to run as a different user.
Why wouldn’t they? Linux is gaining market share.
Yeah, it’s slowly gaining market share, but it’s still a minuscule size of the user base
what about bazzite set to immutable?
That does not stop things from stealing your data.
Would that even help? Windows malware can run on Linux precisely thanks to Wine and Proton.
You don’t actually believe this, right?
My uneducated guess is that it would run inside the prefix but would have troubles with basic Windows dependencies not availiable/running, prefix’s folder structure being cut down to the most basic components and barebones, and that nothing actually runs like in Windows but is rather translated from Linux commands to Windows one and back? Meaning there’s no processes or services like in a VM, no way to run cmd or powershell scripts, nothing to steal without leaving containment? Am I wrong somewhere?
I recall there was a wave of dread about Proton leaving host system easily accessible and not implementing any security measures as they are out of scope, but if we assume it’s a virus targeting Windows, I’m half sure it would have troubles doing anything the usual way.
https://www.youtube.com/watch?v=d3fSnHTJdR0
Hey PieFed user, posting a 5-minute meme video where the guy struggles to make a custom virus do something through Proton isn’t the own you think it is. It literally corroborates my point. Windows viruses and malware will not work through Proton.