Workspace Trust has undergone major adjustments. VisualStudioCode 1.5.8 released

Hello.
I'm Mandai, in charge of Wild on the development team.
Visual Studio Code (VSCode) recently released version 1.58 of Visual Studio Code (VSCode), which suddenly started asking "Do you trust the creator of the files in this folder?" with the last version update.
It's been a while, but I would like to introduce the main update contents of 1.58 from the release notes.

Workspace Trust has been adjusted after all

As expected, you can now adjust the behavior to display the "Do you trust the creator of the files in this folder?" message that I introduced at the beginning.

What is this anyway? For those who are interested, Visual Studio Code Workspace Trust security , which has detailed information, but the developers of VSCode believe that "we believe it is important that developers can safely browse code," They believe that this is playing a role in reducing our security risks.
However, I don't want to see this dialog every time I open a new project! It's easy to imagine that there are a certain number of people like that, so I created an adjustment item! That's the form.

By the way, it seems that you can read and write code without any problems even if you open it in restricted mode, but the following restrictions apply.

• Execute the task (can no longer be executed)
• Executing debugging (debugging cannot be started)
• Some workspace settings are disabled
• Some extensions are disabled

If you want to clone unknown open source code from github, I think opening it in restricted mode will reduce the risk.

If you search for "trust" from the settings screen, several items will appear, so let's take a look.

 

Banner

This setting allows you to control the display of the dialog for selecting whether to enter restricted mode.

• The default is untilDismissed, so if you choose whether to trust it or not, the dialog will not be displayed from now on.
• Select always to display the dialog every time if you select don't trust
• If you select never the dialog will not be displayed

The dialog will no longer appear, but the functionality will remain enabled.

 

Empty Window

Set whether to enable Workspace Trust for empty windows that are not workspaces.
By enabling this option and using it in conjunction with Untrusted Files (described below), you can treat the workspace as a trusted workspace without displaying a dialog in an empty window.

 

Enabled

Enable/disable Workspace Trust functionality.
A reboot is required for changes to take effect.

 

Startup Prompt

Adjust when the Workspace Trust dialog is displayed at startup.

 

always

Displays a confirmation dialog every time you open an untrusted workspace.

 

once

The dialog will be displayed only the first time, and will not be displayed from the second time onwards.

 

never

No dialog will be displayed.

 

Untrusted Files

It's a bit complicated, but you can set the behavior when opening a file outside the workspace (this is an untrusted file) on a trusted workspace.
The default is "prompt" which opens the Workspace Trust dialog, "open" which opens without displaying the dialog, and "newWindow" which opens the file in a new window.

 

Support Untrusted Workspace

Control extensions in untrusted workspaces.
This option requires editing settings.json directly and describes the settings to enable for each extension depending on whether the workspace is trusted.
Depending on the number of extensions you have installed, it may require a fair amount of work, so you may be disappointed.

"eamodio.gitlens": { "supported": true "version": "11.6.0" },

 

The above JSON is an excerpt from settings.json, but the settings for one extension are objects that take two values ​​with the extension's Unique Identifier as the key.
supported is how to launch it in an untrusted workspace; if true it will be enabled unconditionally, if false it will be disabled.
There is also a value limited, which means that the extension itself is enabled, but the extension's functions that require trust (such as file execution) are hidden depending on the extension of the target file. .

 

What are transient workspaces?

The unfamiliar word "transient" came up, and it seems that Transient workspaces is also a type of workspace.
There seem to be two differences from a normal workspace.

• Do not reopen workspace when restarting or reloading VSCode
• Workspaces marked as Transient workspaces do not appear in recent items

Although it is used locally, I thought it would be possible to treat it like a private tab in a browser, where embarrassing workspaces will not appear in the history if someone sees them.

 

The day has come when you can treat the terminal as an editor.

You can now move the terminal to the editor area, giving you more freedom in creating layouts.
Until now, the terminal was only able to make adjustments within the panel, such as maximizing the panel or splitting the layout, but now it has expanded to the editor area.

To do this, right-click the open terminal from the right side of the terminal panel and select Move into Editor Area, or drag and drop it to the editor.
The layout of the moved terminal feels the same as a normal editor, and the inside of the terminal feels the same as the previous terminal, so it feels natural to use.

You can display multiple terminals side by side as an editor, but be careful not to make mistakes.

 

Scrollbar size can now be adjusted

This is a setting that I thought was not possible before, but now you can make adjustments such as making the scroll bar thicker or thinner.

I tried adjusting it a bit, but if I made it too thick, the display area would be narrowed, and if I made it too thin, it would be stressful to use the mouse.
In the end, I thought the default was better.

 

You can now display formulas in Markdown preview

KaTeX formulas written in Markdown are now previewed correctly.

 

summary

In this article, I regret not being able to introduce Workspace Trust in detail when it was introduced in the previous version update, but since various adjustments were made, I thought it was a good idea to introduce it as well. I thought.
I wondered what security meant when I was reading the editor, but the more I looked at how it was introduced, the more I realized that we're now in an era where malicious programs can not only be accessed by clicking on suspicious links, but can also be found on github. I was acutely aware of this.

I've spent a lot of space on Workspace Trust, but from a server-side engineer's perspective, it's important to note that the terminal can now be treated as an editor.
The fact that it has been made into an editor means that it will soon be possible to make it floating...maybe.

lastly

I have opened the system development service site "SEKARAKU Lab" to which I belong.
Beyond is a one-stop service for everything from server design and construction to operation, so if you have any trouble with server-side development, please feel free to contact us.
SEKARAKU Lab: [https://sekarakulab.beyondjapan.com/](https://sekarakulab.beyondjapan.com/)

That's it.