Tried latest Windows client against our demo system, hanged when connecting to the agent. It seems like the thinlinc-login output was intermixed with the COMMAND_EXITSTATUS, see attached log.
Created attachment 432 [details]
Created attachment 433 [details]
tlclient.log when it works
Note that for the successful case, there's no output from thinlinc-login at all.
First test to see how common this is. Test on several windows machines, and possibly against different servers.
Nightly build of the client needs to be used.
Have attempted to reproduce this on Windows 7 and the XP machine in the lab - could not reproduce. Perhaps we should test again quickly on Peter's laptop before closing.
More testing on my laptop, with build 3459. Seems to be rare. I tried 20 logins against different servers, sometimes reconnect, sometimes new session. In some cases, doing a file transfer against the same server. The result is:
No output from thinlinc-login: 12
Only HELLO: 1
Everything from thinlinc-login (ie unsupported service): 7
Intermixed, ie this bug: 0
IOW, we can probably pretend this bug does not exist right now.
Created attachment 442 [details]
tlclient.log when using smart card login
Unfortunately, this bug happened again today, when using smart card auth against the demo system.
Will look at this whilst doing bug 3183.
This could in theory happen with OpenSSH as well. Seeing if things can be improved.
Fixed in r26792.
Tester could verify this with a malicious thinlinc-login that omits the last \n.
Tried but failed to reproduce the problem with the 4.0 client; does not happen neither with my laptop against the demo system, neither with a malicious thinlinc-login. Anyway, the latest nightly build works fine as well, so assuming we do not see this elsewhere this test period, I'd say this problem is gone.