You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For this extension, limited mode should be fine. We should probably block sshfs.configs and sshfs.configpaths from being read from untrusted workspaces, using the restrictedConfigurations field mentioned in the issue above.
Should double-check the extension for places where workspace trust might be an issue, but as far as I know, the only workspace "resources" the extension uses are the aforementioned settings. One edge case might be where the User Settings' sshfs.configpaths might have relative paths, which might thus reference the workspace folder. Actually unsure whether relative paths would be relative to the workspace folder, to wherever VS Code got opened or to the installation directory of VS Code.
The text was updated successfully, but these errors were encountered:
Went with full support. Originally planned on going with limited support, which would disable config scanning for workspace folders, but that feature has already been disabled due to complexities in the past.
Information: microsoft/vscode#120251
For this extension,
limited
mode should be fine. We should probably blocksshfs.configs
andsshfs.configpaths
from being read from untrusted workspaces, using therestrictedConfigurations
field mentioned in the issue above.Should double-check the extension for places where workspace trust might be an issue, but as far as I know, the only workspace "resources" the extension uses are the aforementioned settings. One edge case might be where the User Settings'
sshfs.configpaths
might have relative paths, which might thus reference the workspace folder. Actually unsure whether relative paths would be relative to the workspace folder, to wherever VS Code got opened or to the installation directory of VS Code.The text was updated successfully, but these errors were encountered: