mode ever failed to do this, and only Plink actually had a problem
with it, so this didn't become obvious for a while. rlogin mode is
fixed, and all implementations of from_backend() now contain an
assertion so that we should spot errors of this type more quickly in
future.
[originally from svn r1571]
even on systems where the version number check thinks we should be
expecting a dynamically registered message number. I have a
suspicion the version check isn't accurate in all circumstances; and
in any case, in a situation like this where Windows might send you
either of two things, it's better to be ready to deal with both than
to try and second-guess which one you'll get.
[originally from svn r1549]
than a future prospect. I'm going to move the beta-0-52 tag on this
file, but that won't affect release binaries that have already been
built.
[originally from svn r1547]
winnet.c. The result was that complete failures to make an SSH
connection (connection refused, for example) were causing a hang
instead of a proper error report.
[originally from svn r1539]
renames header files and symbols etc. Now if I could only _find_ my
copy of MSVC4 we might even be able to build Win32s binaries...
[originally from svn r1532]
of scp.c, psftp.c and plink.c into it. Additionally, add `batch
mode', in which all the interactive prompts (bad host key, log file
exists, insecure cipher, password prompt) are disabled and safe
responses are assumed. (The idea being that if you run PSCP, for
example, in a cron job then you'd probably rather it failed and
exited instead of leaving the cron job wedged while it waits for
user input that will never arrive.)
[originally from svn r1525]
keys before _every_ other authentication; so if you tried a local
pubkey _and_ a password, for example, you'd also try Pageant twice.
Now fixed.
[originally from svn r1524]
the private key file given in the config; if it spots this then it
avoids trying it again (and in particular avoids needing to ask for
the passphrase when it knows perfectly well it won't work).
[originally from svn r1523]
load a key that is already loaded. This makes command lines such as
`pageant mykey -c mycommand' almost infinitely more useful.
[originally from svn r1522]
^M instead of the Telnet New Line code. Unix-type telnetds don't
care one way or the other; RDB claims some telnetds prefer Telnet
NL; and now someone has found one that can't deal with Telnet NL and
prefers ^M. Sigh.
[originally from svn r1520]
we really need to know what character sequence you were _expecting_
your function key to generate before we can even think about making
PuTTY generate it.
[originally from svn r1519]
process. This is functional in SSH, and vestigial (just returns 0)
in the other three protocols. Plink's Windows exit code is now
determined by the remote process exit code, which should make it
more usable in scripting applications. Tested in both SSH1 and SSH2.
[originally from svn r1518]
if the PuTTY window has the mouse capture (i.e. a drag-select is in
progress). This means you can drag-select at your leisure without
the screen contents wandering around providing you with a moving
target. Likewise dragging the scrollbar to find a piece of history
in the scrollback.
[originally from svn r1517]
were using RegCreateKey instead of RegOpenKey by mistake. This also
required a fix in settings.c to deal gracefully with a NULL return
from enum_settings_start() - since the use of RCK had caused this
never to happen, the code path had never been tested.
[originally from svn r1516]
mouse capture, which in turn will only occur if the initial click
was in the PuTTY client area. Prevents mouse drag events without an
initiating click, and also prevents selection occurring at
unexpected moments such as if you move the mouse before releasing
the second click after double-clicking the title bar to maximise the
window.
[originally from svn r1515]