-
Notifications
You must be signed in to change notification settings - Fork 27.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSH_ASKPASS handler breaks 2FA login #160673
Comments
@muendelezaji, could you please try the following workaround to unblock you:
|
@lszomoru That has worked, back to the old behaviour for now. Thanks. |
@muendelezaji, thank you very much for confirming the workaround. |
@lszomoru Great, thank you for that. Worth mentioning that when changing the settings, I noticed another config - |
This should be fixed in the latest Insiders (2022-09-16). |
@muendelezaji can you verify whether this is working for you on VS Code Insiders? |
@connor4312 I can confirm it does work on Insiders, even with the default setting ( |
Does this issue occur when all extensions are disabled? Yes
Version: 1.72.0-insider
Commit: 5cecbf4
Date: 2022-09-09T16:24:20.520Z
Electron: 19.0.12
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Darwin x64 21.6.0
Sandboxed: Yes
Steps to Reproduce:
Expected:
A prompt should appear in the terminal for the 2FA code to be entered. This was the previous behaviour.
Actual:
VSCode takes over and shows a popup asking "Are you sure you want to continue connecting?". The terminal prompt isn't shown, making it impossible to log into the server.
Additional details:
The changes potentially responsible appear to be from #159573 (Git - implement SSH_ASKPASS handler).
The popup only seems to handle SSH fingerprint prompts, and thus makes some assumptions about the nature of the text. This leads to extracting incorrect values for
host
andfingerprint
. Below are screenshots from 3 scenarios:Note that for (2) and (3) the
host
andfingerprint
could be anything, depending on the actual prompt text.The text was updated successfully, but these errors were encountered: