PowerShell / PowerShell/Win32-OpenSSH
RequestTTY doesn't seem to help with 2FA
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest version
- Search the existing issues.
Steps to reproduce
I'm having an issue with 2FA. I'm tunneling through an intermediate server with "RequestTTY Yes" in my client configuration file. But at the 2FA step, when prompted with multiple options, I don't see the input I provide. I can log in, but I would expect my commands to be displayed as it happens when I log in from a Linux machine.
Expected behavior
I can log in, but I would expect my commands to be displayed as it happens when I log in from a Linux machine.
Actual behavior
Obscured input
Error details
No response
Environment data
Is it an expected behaviour? What is the workaround?
Version
OpenSSH_for_Windows_9.5p1, LibreSSL 3.8.2
Visuals
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue using OpenSSH_for_Windows_9.5p1 with RequestTTY Yes while tunneling through an intermediate server and reaching a 2FA prompt with multiple options. Compare the obscured input with login behavior from a Linux machine; done means determining whether this is expected and documenting a confirmed workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- authentication, cli, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100