mirror of git://git.tartarus.org/simon/putty.git, used for client testing
Перейти к файлу
Simon Tatham 291533d3f9 New piece of Windows infrastructure: winhandl.c takes Plink's
thread-based approach to stdin and stdout, wraps it in a halfway
sensible API, and makes it a globally available service across all
network tools.

There is no direct functionality enhancement from this checkin:
winplink.c now talks to the new API instead of doing it all
internally, but does nothing different as a result.

However, this should lay the groundwork for several diverse pieces
of work in future: pipe-based ProxyCommand on Windows, a serial port
back end, and (hopefully) a pipe-based means of communicating with
Pageant, which should have sensible blocking behaviour and hence
permit asynchronous agent requests and decrypt-on-demand.

[originally from svn r6797]
2006-08-25 22:10:16 +00:00
charset
contrib
doc
mac
macosx
testdata
unix Shifts left and right by 32 were tripping a gcc warning (fatal with 2006-08-15 20:29:02 +00:00
windows New piece of Windows infrastructure: winhandl.c takes Plink's 2006-08-25 22:10:16 +00:00
CHECKLST.txt
LATEST.VER
LICENCE
README Spell out more explicitly what needs to be done with vanilla VC6, since it 2006-07-07 20:56:22 +00:00
README.txt
Recipe New piece of Windows infrastructure: winhandl.c takes Plink's 2006-08-25 22:10:16 +00:00
be_all.c
be_none.c
be_nossh.c
cmdgen.c
cmdline.c
config.c
cproxy.c
dialog.c
dialog.h
import.c
int64.c Some extra int64 functions. 2006-08-05 13:48:53 +00:00
int64.h Some extra int64 functions. 2006-08-05 13:48:53 +00:00
ldisc.c
ldisc.h
ldiscucs.c
logging.c
minibidi.c
misc.c
misc.h
mkauto.sh
mkfiles.pl Large file support for psftp and pscp on both Windows and Unix. On Unix 2006-08-12 15:20:19 +00:00
mksrcarc.sh
mkunxarc.sh
network.h
nocproxy.c
noprint.c
notiming.c
pinger.c
portfwd.c
pproxy.c
proxy.c
proxy.h
pscp.c Large file support for psftp and pscp on both Windows and Unix. On Unix 2006-08-12 15:20:19 +00:00
psftp.c Large file support for psftp and pscp on both Windows and Unix. On Unix 2006-08-12 15:20:19 +00:00
psftp.h Large file support for psftp and pscp on both Windows and Unix. On Unix 2006-08-12 15:20:19 +00:00
putty.h
puttymem.h
puttyps.h
raw.c
resource.h
rlogin.c
settings.c
sftp.c
sftp.h
ssh.c
ssh.h
sshaes.c
ssharcf.c
sshblowf.c
sshbn.c
sshcrc.c
sshcrcda.c
sshdes.c
sshdh.c
sshdss.c
sshdssg.c
sshmd5.c
sshprime.c
sshpubk.c
sshrand.c
sshrsa.c
sshrsag.c
sshsh256.c
sshsh512.c
sshsha.c
sshzlib.c
storage.h
telnet.c
terminal.c Er, ahem. Other half of r6788. :-/ 2006-08-15 22:48:01 +00:00
terminal.h Er, ahem. Other half of r6788. :-/ 2006-08-15 22:48:01 +00:00
testback.c
time.c
timing.c
tree234.c
tree234.h
version.c
wcwidth.c
wildcard.c
x11fwd.c

README.txt

Этот файл содержит невидимые символы Юникода!

Этот файл содержит невидимые символы Юникода, которые могут быть отображены не так, как показано ниже. Если это намеренно, можете спокойно проигнорировать это предупреждение. Используйте кнопку Экранировать, чтобы показать скрытые символы.

PuTTY README
============

This is the README file for the PuTTY installer distribution. If
you're reading this, you've probably just run our installer and
installed PuTTY on your system.

What should I do next?
----------------------

If you want to use PuTTY to connect to other computers, or use PSFTP
to transfer files, you should just be able to run them from the
Start menu.

If you want to use the command-line-only file transfer utility PSCP,
you will probably want to put the PuTTY installation directory on
your PATH. How you do this depends on your version of Windows. On
Windows NT and 2000, you can set it using Control Panel > System; on
Windows 95 you will need to edit AUTOEXEC.BAT. Consult your Windows
manuals for details.

What do I do if it doesn't work?
--------------------------------

The PuTTY home web site is

    http://www.chiark.greenend.org.uk/~sgtatham/putty/

Here you will find our list of known bugs and pending feature
requests. If your problem is not listed in there, or in the FAQ, or
in the manuals, read the Feedback page to find out how to report
bugs to us. PLEASE read the Feedback page carefully: it is there to
save you time as well as us. Do not send us one-line bug reports
telling us `it doesn't work'.