Workspace Trust in VS Code
code.visualstudio.com
Workspace Trust in VS Code
1–10 of 25 posts
Re: Workspace Trust in VS Code
#2I prefer zero trust.
Re: Workspace Trust in VS Code
#3Re: Workspace Trust in VS Code
#4Total anecdata but I don't appreciate the nag screen every time I've opened repos that I have either authored or contributed heavily to... I default to "yes I accept in this directory and all directories" which seems very sketchy in general, but is the easiest for me to get my work done.
It's pretty annoying. I'm a developer, I know what I'm doing. I don't need to be asked whether I trust a Python notebook or not.
Re: Workspace Trust in VS Code
#5Total anecdata but I don't appreciate the nag screen every time I've opened repos that I have either authored or contributed heavily to... I default to "yes I accept in this directory and all directories" which seems very sketchy in general, but is the easiest for me to get my work done.
This happens even in files I just created or when doing `code ~./zshrc`. It's pretty annoying. I'm a developer, I know what I'm doing. I don't need to be asked whether I trust a Python notebook or not.
famous last words
Re: Workspace Trust in VS Code
#6Despite favoring "least privilege" myself, I find the new nag screens overbearing. I think some basic UI reworking can help to alleviate that, though. It's a new feature; they'll get it right within a couple of iterations.
Re: Workspace Trust in VS Code
#7Re: Workspace Trust in VS Code
#8Re: Workspace Trust in VS Code
#9Based on the first four comments, I see some do not appreciate this unlike me, at least. Just last-night, I was forced to download a zipped folder with source code from a site I was new to. Well, I did appreciate using this new feature because I wasn't sure what I of the 'trustworthiness' of the folder.
It is the same approach to defend off phishing attacks in large corporations: shift the responsibility to the user.
In my opinion, this is just another scream for codified capabilities. Which would be a real solution and not just repeatedly a click away from disaster.
Re: Workspace Trust in VS Code
#10Based on the first four comments, I see some do not appreciate this unlike me, at least. Just last-night, I was forced to download a zipped folder with source code from a site I was new to. Well, I did appreciate using this new feature because I wasn't sure what I of the 'trustworthiness' of the folder.