Re: UTF8

[der Mouse <mouse%Rodents.Montreal.QC.CA@localhost>]

> Certainly I don't know anyone who thinks of their username or
> password as being an octet string.

Neither do I, usually.  But I know that it _is_ an octet string to the
OS, fundamentally, and if I have trouble logging in, I take that into
account.

> However, it sure looks to me like we have "rough consensus" that
> these things are in fact character strings, not octet strings, and
> that the SSH protocol should behave accordingly.

"In fact"?  Humans think of them as character strings (mostly, at
least).  OSes, at least the ones in question, treat them as opaque
octet strings.  Which is the "fact"?  When it comes to actually
successfully logging in, I would say the octet string is the fact: it
doesn't matter whether the characters you type are the ones you think
of your username or password as containing, if the resulting octet
string doesn't match.

What I think we do have consensus on, even if only consensus by apathy,
is that this issue can be ignored; I appear to be the only person the
least bit concerned about it.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse%rodents.montreal.qc.ca@localhost
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B