Closed RihanArfan closed 2 years ago
Looks like a cgo bug in https://github.com/flynn/hid/blob/master/hid_windows.go I'll try to repro this on a Windows box.
@LeCodeCo how did you run the tsh binary? Under the Linux subsystem or MinGW?
@LeCodeCo how did you run the tsh binary? Under the Linux subsystem or MinGW?
Downloaded it, opened PowerShell and ran .\tsh.exe. Guessing that'd be MinGW.
Cool, I'm able to reproduce it in powershell. At first, the MFA prompt just hangs, not responding to u2f taps. When I cancel it and try again, it hangs for a bit but then unblocks with the above panic.
Since the problem is in a dependency, I don't have a quick way to fix it right now. Need to make a minimal repro snippet and submit a report to the dependency maintainers.
Closing as U2F is no longer supported in Teleport.
Description
What happened: I am trying to add a U2F MFA device from
tsh
.What you expected to happen: I expect the key to be added without errors.
Reproduction Steps
As minimally and precisely as possible, describe step-by-step how to reproduce the problem.
Server Details
teleport version
): Teleport v6.0.2 git:v6.0.2-0-g1cb1420b7 go1.15.5/etc/os-release
): Ubuntu 20.04.2Client Details
tsh version
): Teleport v6.0.2 git:v6.0.2-0-g1cb1420b7 go1.15.5Debug Logs
While running with debug mode, the only concerning thing I see is
ERRO [CLIENT] [KEY AGENT] Unable to connect to SSH agent on socket: "". client\api.go:2449
after I enter the device name.