• 0 Posts
  • 94 Comments
Joined 11 months ago
cake
Cake day: August 16th, 2023

help-circle


  • The presence of OPs device on our network would be ringing about a dozen alarms and we’d already have it quarantined with his account disabled because we would assume it’s been compromised. I’d then enjoy sitting in the meeting with OP and his boss as he has to explain to them why I disabled their access to all company technology and OP has to turn in his reports in a 3 ring binder.

    That would be interesting.

    Out of curiosity - what would you do if you detect Steam installed on corporate laptop? Would be interesting to hear your verdict. 😅


  • There are more:

    1. Unable to completelly disable IPv6.
    2. On fresh WSL2 install, the DNS is somehow broken (on corporate laptop). Had to update /etc/wsl.conf and /etc/reaolv.conf to fix it.
    3. WSL2 ignores global proxy settings. Kind of expected, because Linux does not really support autoconf URL.
    4. Already mentioned - unable to port-forward UDP ports from Windows.

    I think that’s the most significant ones.

    Also there are few nice features to know:

    1. “explorer.exe .” opens windows explorer from WSL2 in a given path.
    2. Windows drives are accessible via “/mnt/”.


  • zikk_transport2@lemmy.dbzer0.comOPtoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    10 months ago

    Actually it’s quite good. Recently they added SystemD services support, so all those guides “for Ubuntu” work totally okay in WSL2.

    Well, take the step back - Microsoft implementing WSL2 shows that Microsoft agrees that Linux shell environment is better that Windows PowerShell environment.

    But the way they implemented and this mind-blowing TCP-only port forwarding feature shows that they did a crappy job…