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
Remote OS Version: Linux 3.10.0-693.2.2.el7.x86_64
Remote Extension/Connection Type: SSH
Steps to Reproduce:
Install SeKey, a tool that stores SSH keys on the Secure Enclave on Touch ID-equipped Macs. Configure public key authentication to a remote SSH server using a key stored on the Secure Enclave.
Use Visual Studio Code to connect to the Remote SSH server.
During "Confirming is reachable" phase, authenticate via Touch ID. (Awesome that it works with no change on the VS Code side!)
Authenticate via Touch ID again, during "Initializing VS Code Server" phase.
Authenticate via Touch ID again, during "Waiting for port forwarding" phase.
Click "Open Folder" in the file navigator and enter a path to open.
Authenticate via Touch ID two more times...
Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered:
rgov
changed the title
Many TouchID prompts when using SeKey
Many Touch ID prompts when using SeKey and an SSH server
Jul 1, 2019
Steps to Reproduce:
Install SeKey, a tool that stores SSH keys on the Secure Enclave on Touch ID-equipped Macs. Configure public key authentication to a remote SSH server using a key stored on the Secure Enclave.
Use Visual Studio Code to connect to the Remote SSH server.
During "Confirming is reachable" phase, authenticate via Touch ID. (Awesome that it works with no change on the VS Code side!)
Authenticate via Touch ID again, during "Initializing VS Code Server" phase.
Authenticate via Touch ID again, during "Waiting for port forwarding" phase.
Click "Open Folder" in the file navigator and enter a path to open.
Authenticate via Touch ID two more times...
Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: