Yeah, I'm worried about the day when infosec turns it's eye toward WSL. So far they have turned a blind eye, but just wait until someone cooks up an exploit targeting WSL...
Yeah, I'm worried about the day when infosec turns it's eye toward WSL. So far they have turned a blind eye, but just wait until someone cooks up an exploit targeting WSL...
In my experience they just block it in corporate environments.
They don't explicitly block it in my org, but connecting to VPN while it's running breaks the networking inside WSL.
Sometimes it is routed from the VPN, sometimes it is DNS, sometimes it just needs a restart. I'm not sure if that situation has improved. There were some workarounds at one point.
It's "just" a Hyper-V VM with some extra drivers to talk to the sibling VM. There isn't much special about it that should worry you too much.
Well, I'd like to tell security that