Powershell accepts input on the daemons prompt, not the clients

[ariscop]

https://youtu.be/dVPuI8HrE00

Launching powershell directly (ssh localhost powershell) has the same behavior

[quamrulmina]

Known limit now - cmd.exe shell runs but Powershell does not. Our win32 port of sshd server does not provide a console as input in pty/tty mode and powershell seems to need a console input to run in interactive mode. Notice cmd.exe shell does not have this need and so runs fine.

[quamrulmina]

"powershell -File -" invocation will make it work now as it is a known issue of powershell.

[quamrulmina]

Invoke as follows to make it work:
ssh user@domain@hostname powershell -File -

From a cmd.exe remote shell:
ssh user@domain@hostname
c:> powershell -File -

[MichaelPietroforte]

@quamrulmina This didn't work for me. When I enter powershell -File - I just receive "powershell -File" twice as output, but PowerShell commands still don't work. Only cmd.exe shell works.

[quamrulmina]

In the upcoming release it has been fixed and "ssh user@domain@hostname powershell -File -" will work. But it will work even better if you launch powershell after getting to the interactive shell, cmd.exe, in this case so that pty support like echo characters are available:
ssh user@domain@hostname
c:> powershell -File -

[manojampalam]

Fixed in latest release.

[mikemaccana]

Why is this closed? There's a workaround (powershell -File -) but obviously input should be set correctly by default.

[ariscop]

This bug was fixed, powershell's io is sent over ssh instead of using the sshd's console
On the latest release powershell is still broken, but it's a different bug

[mikemaccana]

Thanks @ariscop!