]> asedeno.scripts.mit.edu Git - PuTTY.git/commit
On Windows, MessageBoxIndirect() was sometimes failing to pop up the host key
authorJacob Nevins <jacobn@chiark.greenend.org.uk>
Sun, 20 Feb 2005 23:00:17 +0000 (23:00 +0000)
committerJacob Nevins <jacobn@chiark.greenend.org.uk>
Sun, 20 Feb 2005 23:00:17 +0000 (23:00 +0000)
commit651cedc7fbb52e09b6d302919c6b4372486641ed
tree385d5fcfd86ef8ccf5476f847893eab00432e823
parent140688e77fc22bed828feb2bf2f93a84e7b82cc9
On Windows, MessageBoxIndirect() was sometimes failing to pop up the host key
dialog and returning an unexpected value (0), causing everything to silently
behave as if the user had said "allow this connection but don't store host
key"!

Initialising (MSGBOXPARAMS).hInstance seems to have cured this (although the
MSDN docs seemed to indicate it wouldn't be used) -- if so, it's been broken
since r5309 on 2004-02-15 -- but since this was something of a Heisenbug, and
the behaviour was so catastrophic when MessageBoxIndirect() behaved oddly, I've
rearranged the code to default to cancelling, and added an assertion for
visibility.

(Windows PuTTY still seems to be broken wrt servers that send NEWKEYS while
we're waiting for the user, which happens to include the "SSH-2.0-2.4.1 SSH
Secure Shell OpenVMS V1.0" I'm testing against. I don't know why. The above bug
may also have been limited to this circumstance.)

[originally from svn r5370]
[r5309 == 99122767f528fa86e6e33c1bc594af2c0dcb884b]
windows/windlg.c