This will be more of a bug report, since I eventually achieved a successful registration and login. Though I think it may be useful to share what I learned along the way. I am doing this from a Mac Pro, late 2013 model, running OS X 10.9.5. EchoHam reports its version as 1.10 (840).
My first attempts to
register (I am not logged in at this point, the system does not know my password yet!) involved a 16-character password that ended in a double-quote ("). The rest of the password did contain both capital and lowercase letters, numbers, and other punctuation symbols, but no whitespace. The login process would simply hang until the client complained that it was not able to connect. After I removed the double-quote things appeared to work normally.
To me this suggests:
- The double-quote character is not welcome in passwords. Are there other unwelcome characters?
- EchoHam does not handle 16-character passwords correctly, but shorter passwords are fine.
- Whatever network protocol EchoLink uses for login does not properly handle passwords longer than a certain length. This would be a server bug, not a client bug.
- Some combination of the above.
Are there other reports of problems around password length, or specific password content?
I also discovered other authentication-related problems while attempting to debug this. I would prefer to report them privately to a responsible party. I can PGP encrypt if desired.
