Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
"only for secondary phisical drives"
they will patch it out soon :)
(Thankfully) I don't have it here so can't really test the details, but my guess is that WSL2 will ensure permissions are handled properly since that's needed inside WSL2 in general too.
can it have root permissions? that would be nice way to infect Linux machines from compromised Windows OS.
In any case, 3rd-party software without admin priviledges can open and even write to EXT4 from inside Windows since before WSL even existed (eg: https://www.howtogeek.com/112888/3-ways-to-access-your-linux-partitions-from-windows/), so a windows virus in theory already could implement the same code to be able to target neighbour linux partitions from windows on its own... given how excessive the powers of a non-privililedged app on windows are, if the disk is plugged in and has no full disk encription or LUKS in place, it was vulnerable already.
WSL may put the possibility into a spotlight for malware developers, but isn't really innovating, only making it more convenient out-of-the-(sand)box
Finally, the secondary disk needs to be mounted via a command that, if I got the idea right, is ran inside WSL2 and not directly on Windows, so some extra steps would need to be taken there to make it happen without user interaction from a malicious .exe running outside it... not that I think it's impossible, just non-trivial.
Nice to know
thanks for sharing
Having access from Windows Explorer does make it a lot easier to get the WindowsNT system URI for drive access to create a drive letter.
so actually using the drive in windows software is also good to go, though not as easily accessible yet
they sure took their sweet time ;)
i have been hearing rumors about that threat for a few weeks, but havent had time to investigate the possible attack vectors.
you can use PS commandlets to map/mount a given path to a drive letter (this has been around for a while, but had some issues with permission inheritance. i am not sure if it was fixed)
did they come up with a different way?
Starting point: Linux keeps all data in text files, protected by root privileges on Linux systems and just text files if you access it from outside. some files are read-only, protected by system but will act like common files if accessed from Windows.
To execute something you just have to add malicious command/file to loading scripts, often these would be executed on boot with root privileges or as sudoer.
I take it Windows 7 has no ability to "see" ext4 drives so there's no issue to dual boot, right?
As I mentioned earlier:
In short, if the drive is plugged and data is not encrypted, it can be tampered and if it's encrypted it can only be destroyed.