I have a few questions about the shims used by WSL Comfort (pbcopy, pbpaste, open, etc.):
-
Are these shims intended to provide any kind of isolation or restricted access to Windows executables, or are they only convenience wrappers?
-
If they are only convenience wrappers, what is the recommended way to create custom shims for additional Windows functionality? Is there an intended pattern or extension point for adding custom shims to WSL Comfort?
-
Do these shims work when the following WSL interop settings are used?
[interop]
enabled=false
appendWindowsPath=false
In particular, I'm interested in whether a shim could provide access to a specific Windows executable while preventing general access to Windows executables and the Windows PATH.
I have a few questions about the shims used by WSL Comfort (
pbcopy,pbpaste,open, etc.):Are these shims intended to provide any kind of isolation or restricted access to Windows executables, or are they only convenience wrappers?
If they are only convenience wrappers, what is the recommended way to create custom shims for additional Windows functionality? Is there an intended pattern or extension point for adding custom shims to WSL Comfort?
Do these shims work when the following WSL interop settings are used?
In particular, I'm interested in whether a shim could provide access to a specific Windows executable while preventing general access to Windows executables and the Windows PATH.