[Savannah-hackers] Re: lshd crashed on subversions.gnu.org

[Niels M�ller]

Loic Dachary <address@hidden> writes:

> lshd crashed at 04:33 and was restarted at 05:50.
> 
> Jun 23 04:30:04 subversions lshd[386]: Unregistered child 10353 died with 
> exit status 0.
> Jun 23 04:33:17 subversions lshd[386]: Unhandled exception of type 0x1000: 
> Invalid utf8 in password.

Thanks for the bug report. I think that information should be enough
to reproduce and track down the bug. I'm assuming you're running
version 1.2.2?

If you can get that information, it would be interesting to know (i)
what the user's password (or some other password provoking the bug)
was, (ii) which client was used and how it utf8-encoded the password,
and (iii) which character set/encoding is used for non-asciii
passwords (i.e. the strings that are passed to crypt(3) locally).

There are three alternative modes of operation that are more-or-less
implemented in current versions of lsh:

  CHARSET_UTF8: Utf-8 is the "native" character set of the system;
                user names and passwords are encoded using utf-8.
                Normalization is currently unspecified, but it has to
                be specified for this to work reliably.

  CHARSET_LATIN1: iso-8859-1 is the "native" character set. User names
                  and passwords are strings of 8-bit latin1
                  characters.

  CHARSET_USASCII: Only 7-bit USASCII can appear in usernames and
                   passwords.

Current versions have the CHARSET_LATIN1 mode hardcoded at startup,
but it should be configured via LC_CTYPE or something like that. The
conversion from utf8 to latin1 doesn't currently respect unicode
equivalence.

/Niels