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
Display of UTF-8 characters has worked for a long time in normal SSH sessions when you invoke ssh in Windows Terminal to connect to a Linux machine, including on current Windows 11 with OpenSSH_for_Windows_9.5p1.
Is the problem perhaps merely that during KbdInteractiveAuthentication that non-ASCII bytes in challenge strings are not passed through transparently, but are escaped as octal numbers with backslashes?
This seems to be an openssh-portable upstream issue, with an open PR at openssh/openssh-portable#452 and therefore may not actually be specific to OpenSSH for Windows.
It looks as if such QR codes rendered using UTF-8 block-graphic characters in PAM-based kbd-interactive dialogues only work on Ubuntu's OpenSSH fork so far, because Ubuntu had patched their own version of OpenSSH, as upstream OpenSSH so far escapes many bytes in these PAM dialogue strings via strnvis().
Summary of the new feature / enhancement
With QR functionality MS Entra ID ubuntu/authd#497 being introduced in ubuntu auth/sshd/ - please enable utf-8. I have tested with the latest https://github.com/PowerShell/Win32-OpenSSH/releases/tag/v9.5.0.0p1-Beta
ref:
Proposed technical implementation details (optional)
No response
The text was updated successfully, but these errors were encountered: