You are not logged in.
Hey everyone,
So, I'm really new to Arch, like, seriously new. I managed to get Arch LXQT installed with LUKS full disk encryption, which felt like a huge win, honestly.
After that, I decided I wanted to dual boot with Windows. I used GParted to create another partition for Windows, installed it, and now the GRUB menu lets me choose between Arch (which
is set as the default) and Windows. That part seems to be working fine.
But here's where I'm getting really worried. I use my Windows machine for... stuff. Let's just say I have a lot of "security software" installed. Like, a lot. We're talking
Vanguard, Faceit anti-cheat, Easy Anti-Cheat... basically everything that tries to dig into the kernel.
My question is, and I'm really hoping someone can explain this to me, how separated am I *actually* when I boot into Arch? I'm thinking about it and these anti-cheats are 'kernel
level'. Does that mean they can somehow still "see" or interact with my Arch system even though it's on a different partition and encrypted?
I'm especially worried about them potentially trying to read data from my encrypted partition, or even just knowing I'm running a different OS. Is the LUKS encryption enough to
protect me from that kind of thing?
I've been reading about virtualization and stuff, but I'm not sure if that's relevant here. I just want to know if booting into Arch gives me a genuinely clean environment, or if
those Windows kernel-level things are still lurking somewhere.
Any help or explanation would be greatly appreciated. I'm kind of panicking a little bit, to be honest.
Thanks in advance!
Offline
Windows kernels have no support for linux filesystem / encryption .
In order to acces them you need to use linux tools through WSL2 or install special software like https://github.com/AlexSSD7/linsk
or even just knowing I'm running a different OS
All partitions on the drive are visible to the windows kernel, but why would those tools care what other OSes you have installed when they are inactive ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
One thing about windows update is it likes to create extra partitions on the fly and renumber partitions accordingly.
If your arch setup is dependent on partition number, eg. /dev/sdaX, and windows renumbers it, then there's a chance it will cause trouble with your arch installation. That's why it is recommended to use UUIDs instead.
DISCLAIMER: I have not used windows actively for a very long time. My limited exposure to windows is through helping friends and relatives with their windows problems, so take my post with a grain of salt.
Last edited by kermit63 (2025-03-19 17:50:38)
Never argue with an idiot, they will drag you down to their level and then beat you with experience.
It is better to light a candle than curse the darkness.
A journey of a thousand miles begins with a single step.
Offline