microsoft
Open sourcing P9rdr.sys and p9np.dll, which runs the “\\wsl.localhost” filesystem redirection (from Windows to Linux)
In follow-up to https://github.com/microsoft/WSL/issues/1#issuecomment-2893266627
Logs are required for review from WSL team
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1
The script will output the path of the log file once done.
If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here
Once completed please upload the output files to this Github issue.
Click here for more info on logging If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
+1. This will help to fix (I guess) the problem with wsl.localhost dissappear or stop working, I think.
#12593
+1. I don't see any way open sourcing them would leak technologies used in the Windows kernel.
+1. I don't see any way open sourcing them would leak technologies used in the Windows kernel.
Who came up with that rumor ?
There are other opensource MiniRDR-based Windows filesystem drivers like the one for VirtualBox guest FS sharing, or the Windows NFSv4.2 filesystem driver (https://github.com/kofemann/ms-nfs41-client), and both are opensource and only rely on public Windows kernel APIs.
Or short: There is no security or technical issue which prevents releasing the Microsoft Windows 9p filesystem driver...
@gisburn - I didn't know about it, and looks good, but we can't use in production:
The kernel driver ("nfs41_driver.sys") does not yet have a cryptographic signature for SecureBoot - which means it will only work if SecureBoot is turned off (otherwise $ /sbin/msnfs41client install # will FAIL!)
from https://github.com/kofemann/ms-nfs41-client?tab=readme-ov-file#known-issues
Today another developer got the error with wsl.localhost after a Windows update (WSL version: 2.5.9)
- The P9NP is still here, though. The key has not dissappeared, so it's not exactly the common #12593
- regquery
-wslview returns a slighly different error (he's running systemd): _/proc/sys/fs/binfmt_misc/WSLInterop no such file or directory
- Accessing through \wsl$ does not work.
- Accessing throug \wsl.localhost does not work.