- Change the creator of files we don't want the user to open to 'pTTI' (for
"PuTTY internal"), and give them application-missing strings.
- Provide missing-application names for saved sessions.
- Provide a ResEdit 'TMPL' resource for integers in saved sessions.
- Provide an icon for saved session stationery pads (maybe "Default Settings"
should be one of these by default). No code to handle this yet.
[originally from svn r2640]
preserve the old file in case the update is interrupted and replace it
atomically, so we just overwrite in place. Much simpler.
[originally from svn r2635]
areas of the code. Not all back-ends have been tested, but Telnet and SSH
behave reasonably.
Incidentally, almost all of this patch was written through Mac PuTTY,
admittedly over a Telnet connection.
[originally from svn r2615]
link-module const variable `be_default_protocol' which suggests a sensible
default to the front end (which can ignore it). (DEFAULT_PORT is replaced by a
lookup in the backend[] table.)
Still not pretty, but it does mean that the recent fix for `ssh-default'
doesn't break PuTTYtel.
[originally from svn r2613]
unitab_xterm. Most linedraw characters display correctly, but it's clear
that RDB and Apple disagree on some of the mappings.
[originally from svn r2601]
vttest apart from the "mad programmer" screen, which I think is a linedraw
problem.
This also intorduces proper clipping of the drawn text for good measure.
[originally from svn r2593]
rest of PuTTY has of DNS resolution, so I've replaced them with something
more conventional. Sorry.
The new code has the advantage of working, of course.
[originally from svn r2551]
and to convert to a string only on demand. This makes it possible to have
the string contain the error number if we don't recognise it.
[originally from svn r2548]
we can have runtime switching between MacTCP and OpenTransport, and so
that we can cope if there's no TCP/IP stack available at all (albeit with
very little functionality at present).
[originally from svn r2546]
we're going to be a security program, we can at least make a token
effort to use the most secure local X auth available! And I'm still
half-tempted to see if I can support it for remote X servers too...
[originally from svn r2537]
Windows and Mac backends have acquired auth-finding functions which
do nothing; Unix backend has acquired one which actually works, so
Plink can now do X forwarding believably.
(This checkin stretches into some unlikely parts of the code because
there have been one or two knock-on effects involving `const'. Bah.)
[originally from svn r2536]