Notes on Using Non-ASCII Characters in User Names or Passwords

SSH Connection

RFC 4252 specifies that both the user name and password are transmitted in UTF-8 in the SSH protocol.
Tera Term sends user names and passwords containing non-ASCII characters in UTF-8.
However, if the SSH server does not correctly handle UTF-8, SSH authentication may fail.
Furthermore, depending on the implementation of processing related to SSH authentication (such as PAM, SSSD, or LDAP), passwords may be handled using a locale-dependent character encoding.
In such cases, a password containing non-ASCII characters may not be interpreted correctly.

Telnet Connection

The Telnet protocol is fundamentally based on ASCII, and the use of non-ASCII characters in user names or passwords is not assumed.
When Tera Term sends user names or passwords containing non-ASCII characters, they are encoded according to the configured transmit character encoding.
If the Telnet server uses a different character encoding, authentication may fail.