[Tilesathome] Switching T at H server to t at hngo NOW!

[Robert (Jamie) Munro]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Henry Loenwind wrote:
| spaetz wrote:
|
|>> My password was containing some specials characters. I changed it into a
|>> more simple one and it's now pretty good.
|> Really? Can you mail me privately what chars that would have been? I
pass on the password to the OSM server as is, so I don't know what could
have been causing this. I will try to check this with more complicated
passwords. It probably needs some HTML encoding or something...
|
| I'd say that's an encoding issue. When reading the authentication.conf,
| the tah client has no way of telling in which encoding the text editor
| saved the file. It now sends the string unchanged to the server, which
| again has no way of knowing the encoding...
|
| The only workaround I can imagine (apart from making users use a
| specific encoding when editing the conf file---not possible) would be to
| try to recode the password if it fails to validate and contains
| non-ASCII characters. (Ok, that would fail for EBCDIC encoded passwords,
| but who manages to run the client on an EBCDIC platform also can
| properly encode the conf file, I'd guess...)
|
| I could code a loop over, say, the Top100 encodings in the client, but I
| don't think hammering the server after a failed login that way would be
| wise. Any better ideas?

Personally, my rule is unless there is a good reason not to, always
assume UTF-8. The most obvious good reason not to would be if it didn't
validate.

Robert (Jamie) Munro
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkh/1WwACgkQz+aYVHdncI2rZgCeMN3oxUDeKFjU5ueUEE2645xU
5CEAoLXrJqRMPtKMVRAwASxJkuQjBOXu
=AZAP
-----END PGP SIGNATURE-----