Note: The
ate-6.3.1544.7-web.exe installer/updater contains a further update to the SSH protocol support (in ashnet2.dll 2.3.208). Aside from updating the dependent OpenSSL and related libraries, it also closes a minor security loophole related to the all-users configurations.
The issue here (as described earlier in this thread) is that the all-user profiles are stored in an area of the Registry that is read-only to non-admin users. That works nicely in cases where an administrator sets up a profile to be shared by multiple users and you don't want one user messing up those shared settings. (They can still save the user-level customizable settings, such as initial window size and position, color palette, etc., via the File > Save menu.)
But the problem was that the SSL protocol involves comparing a fingerprint on the server with a saved copy of that fingerprint on the client, to guard against the possibility that the server has been spoofed or redirected to somewhere unexpected. In such a case, a dialog will be displayed warning the user of the change and asking them if it is ok to accept and update the fingerprint. In the previous patch (2.3.207), we allowed the non-admin user to indicate approval even though he didn't really have the privileges necessary to actually save the new fingerprint. Now, in such a case, we deny the connection.
Which makes security sense, even if it may be a slight hassle in operating environments were you don't really worry about that fingerprint changing. If that seems like a step backwards to you, the solution is simple: just check the Auto-Accept Fingerprint option in the configuration. In that case, it pays no attention to the fingerprint.