Re: UTF8

[nisse%lysator.liu.se@localhost (Niels Möller)]

markus%gyger.org@localhost (Markus Gyger) writes:

> Niels Moeller writes:
> > Please leave the file system issues out of it for now. What's of
> > primary importantance are the core drafts, and those deal with
> > usernames and passwords in utf8 form, *not* file names.
> 
> Are there any directions on what encoding SSH_MSG_CHANNEL_REQUEST
> with the "exec" request type should use for the command string
> (for "subsystem" it is specified but there sems to be no info
> for "exec" in connect-23)?

I've never thought about the encoding issues for this string before.
It's not specified. Note that also the channel data is often text, and
its encoding is also not specified at all by the ssh protocols. In
practice,

  * You have to guess what character system is used by the default
    session.

  * This will probably be a pain if local and remote systems use
    different character sets (say latin-1/utf8).

  * It's easier to let the client environment adapt to the server
    environment conventions than vice versa.

But for now, users have to ensure manually that they are using the
same character set locally and remotely. If you e.g. want to login to
a server that lives in utf8-land, and your local environment doesn't
use utf8, then you'd better use some local terminal emulator that
understands utf8.

Regards,
/Niels