cascreation.blogg.se - Visual studio code github login keeps popping up

However, once I removed VSCode from having access to the entry to see the repeated dialogs appearing, they started to appear.It's always fun when Visual Studio (ie can't recite the alphabet backwards: The code below builds just fine when running through the compiler, but Visual Studio displays Intellisense errors in the Error Window and in the code with underlined squiggles: I was NOT prompted with a dialog to grant access to the keychain simply because the application was the first to store the password. As a preparation I deleted any VSCode related entry of the macOS keychain and then started VSCode to sign-in to GH.

While attempting to verify this fix for our upcoming recovery release, I have a better understanding now why this issue is present now and was not there before.

The polling for the keychain will be addressed in Multiple access to keychain in a single session #107480 and that should make things better and you might not have to provide Always Allow.

You can also delete the particular keychain entity that is trying to be accessed if you no longer use that extension.

Provide Always Allow to prevent from repeated prompts.

So please make sure you have done one of these, I certainly agree its an annoyance but thats how it works today.

There is nothing the app can do here to prevent the prompt from showing up. Since there is now a change of application executable that is trying to access the keychain, the prompt is shown. As mentioned earlier keychain access control list is based on the bundle identifier, and the bundle identifier for these helper executables are different from the main application executable. In 1.50 we moved the keytar module from the renderer process to the main process in an effort towards sandboxing #92164. You can check for the different policies applied to each of these process. For ex: gpu helper will depend on a different set of system libraries than the renderer helper or restrict the system calls that can be made directly from the renderer. This comes from the multi-process architecture of chromium where each of these helper executables are responsible for different components as rendering, running utility process etc and the advantage in that allows for applying different profiles of the OS sandboxing. MacOS manages the access control list for a keychain item based on the bundle identifier of the application trying to access it.īefore 1.50 this module was present inside each window and on macOS the windows are spawned by an executable called Code Helper (Renderer) which is different from the main application executable.

VSCode uses a native module called keytar to manage passwords across different OS, so any extension that saves an authentication talks to this module for interaction with the keychain. I will expand on and why this ought to happen.