diff --git a/.gitignore b/.gitignore index 9a41137..662c486 100644 --- a/.gitignore +++ b/.gitignore @@ -1,158 +1,9 @@ -*.o -*.pyc -.dirstamp -.deps -.DS_Store .vs +*.obj +*.cobj +*.log +*.tlog *.vcxproj.user *.lastcodeanalysissucceeded -*.pdb -*.ilk -*.res -*.RES -*.pch -*.rsp -*.obj -*.exe -*.ncb -*.plg -*.dsw -*.opt -*.dsp -*.tds -*.td2 -*.map -/Makefile.mgw -/Makefile.vc -/Makefile.lcc -/MSVC -/*.log -/*.GID -/local -/Output -/pageant -/plink -/pscp -/psftp -/putty -/puttytel -/puttygen -/pterm -/puttyapp -/ptermapp -/osxlaunch -/uppity -/unix/PuTTY.app -/unix/Pterm.app -/fuzzterm -/testcrypt -/testsc -/testzlib -/cgtest -/scctest -/*.DSA -/*.RSA -/*.cnt -/*.hlp -/.bmake -/build.log -/build.out -/uxconfig.h -/empty.h -/config.status -/Makefile.am -/Makefile.in -/Makefile -/compile -/config.status -/configure -/stamp-h1 -/aclocal.m4 -/ar-lib -/autom4te.cache -/depcomp -/install-sh -/local -/missing -/uxconfig.in -/uxconfig.in~ -/uxconfig.h -/licence.h -/*.a -/charset/sbcsdat.c -/contrib/cygtermd/cygtermd.exe -/doc/*.html -/doc/*.txt -/doc/*.cnt -/doc/*.hlp -/doc/*.gid -/doc/*.GID -/doc/*.chm -/doc/*.log -/doc/*.1 -/doc/*.info -/doc/vstr.but -/doc/*.hhp -/doc/*.hhc -/doc/*.hhk -/doc/licence.but -/doc/copy.but -/icons/*.pam -/icons/*.png -/icons/*.ico -/icons/*.icns -/icons/*.xpm -/icons/*.c -/unix/Makefile.gtk -/unix/Makefile.ux -/unix/Makefile.local -/unix/empty.h -/unix/plink -/unix/pterm -/unix/putty -/unix/puttytel -/unix/psftp -/unix/pscp -/unix/puttygen -/unix/stamp-h1 -/unix/*.log -/unix/.deps -/windows/*.pdb -/windows/*.ilk -/windows/*.res -/windows/*.RES -/windows/*.pch -/windows/*.rsp -/windows/*.obj -/windows/*.exe -/windows/*.ncb -/windows/*.plg -/windows/*.dsw -/windows/*.opt -/windows/*.dsp -/windows/*.tds -/windows/*.td2 -/windows/*.map -/windows/*.rcpp -/windows/Makefile.clangcl -/windows/Makefile.mgw -/windows/Makefile.vc -/windows/Makefile.lcc -/windows/MSVC -/windows/DEVCPP -/windows/VS2010 -/windows/VS2012 -/windows/*.log -/windows/*.GID -/windows/local -/windows/Output -/windows/*.DSA -/windows/*.RSA -/windows/*.cnt -/windows/*.hlp -/windows/.bmake -/windows/*.sln -/windows/*.suo -/windows/*.msi -/windows/*.wixobj -/windows/*.wixpdb +*.manifest +Temp \ No newline at end of file diff --git a/Buildscr b/Buildscr index 32bdde2..b462029 100644 --- a/Buildscr +++ b/Buildscr @@ -35,7 +35,7 @@ module putty ifeq "$(RELEASE)" "" set Ndate $(!builddate) ifneq "$(Ndate)" "" in . do echo $(Ndate) | perl -pe 's/(....)(..)(..)/$$1-$$2-$$3/' > date ifneq "$(Ndate)" "" read Date date -set Epoch 16971 # update this at every release +set Epoch 17091 # update this at every release ifneq "$(Ndate)" "" in . do echo $(Ndate) | perl -ne 'use Time::Local; /(....)(..)(..)/ and print timegm(0,0,0,$$3,$$2-1,$$1) / 86400 - $(Epoch)' > days ifneq "$(Ndate)" "" read Days days @@ -44,7 +44,7 @@ ifneq "$(Ndate)" "" read Days days # comparisons with the surrounding actual releases. ifeq "$(RELEASE)" "" read Lastver putty/LATEST.VER -# Set up the textual version strings for the docs build and installer. +# Set up the textual version strings for the docs build and installers. # We have one of these including the word 'PuTTY', and one without, # which are inconveniently capitalised differently. ifneq "$(RELEASE)" "" set Puttytextver PuTTY release $(RELEASE) @@ -80,7 +80,7 @@ ifneq "$(PRERELEASE)" "" set Autoconfver $(PRERELEASE)~pre$(Ndate).$(vcsid) ifneq "$(SNAPSHOT)" "" set Autoconfver $(Lastver)-$(Date).$(vcsid) ifeq "$(RELEASE)$(PRERELEASE)$(SNAPSHOT)" "" set Autoconfver Custom.$(Date).$(vcsid) -# Set up the filenames for the Windows installer (minus extension, +# Set up the filenames for the Windows installers (minus extension, # which goes on later). ifneq "$(RELEASE)" "" set Isuffix $(RELEASE)-installer ifneq "$(PRERELEASE)" "" set Isuffix $(PRERELEASE)-pre$(Ndate)-installer @@ -91,13 +91,7 @@ set Ifilename64 putty-64bit-$(Isuffix) set Ifilenamea32 putty-arm32-$(Isuffix) set Ifilenamea64 putty-arm64-$(Isuffix) -# Set up the version string for the Windows installer. -ifneq "$(RELEASE)" "" set Iversion $(RELEASE) -ifneq "$(PRERELEASE)" "" set Iversion $(PRERELEASE)-pre$(Ndate).$(vcsid) -ifneq "$(SNAPSHOT)" "" set Iversion $(Date).$(vcsid) -ifeq "$(RELEASE)$(PRERELEASE)$(SNAPSHOT)" "" set Iversion Custom-$(Date).$(vcsid) - -# Set up the Windows version resource info, for both the installer and +# Set up the Windows version resource info, for both the installers and # the individual programs. This must be a sequence of four 16-bit # integers compared lexicographically, and we define it as follows: # @@ -153,14 +147,7 @@ in putty do make -j$(nproc) in putty do python test/cryptsuite.py enddelegate -# Munge the installer script locally so that it reports the version -# we're really building. -in putty/windows do perl -i~ -pe 'BEGIN{$$a=shift@ARGV;}s/^(AppVerName=).*$$/$$1$$a/' '$(Puttytextver)' putty.iss -in putty/windows do perl -i~ -pe 'BEGIN{$$a=shift@ARGV;}s/^(VersionInfoTextVersion=).*$$/$$1$$a/' '$(Textver)' putty.iss -in putty/windows do perl -i~ -pe 'BEGIN{$$a=shift@ARGV;}s/^(AppVersion=).*$$/$$1$$a/' '$(Iversion)' putty.iss -in putty/windows do perl -i~ -pe 'BEGIN{$$a=shift@ARGV;}s/^(VersionInfoVersion=)\d+\.\d+\.\d+\.\d+\r?$$/$$1$$a/' '$(Winver)' putty.iss - -# Windowsify LICENCE, since it's going in the Windows installer. +# Windowsify LICENCE, since it's going in the Windows installers. in putty do perl -i~ -pe 'y/\015//d;s/$$/\015/' LICENCE # Some gratuitous theming for the MSI installer UI. @@ -174,7 +161,7 @@ mkdir putty/windows/buildold mkdir putty/windows/abuild32 mkdir putty/windows/abuild64 -# Build the binaries to go in the installer, in both 32- and 64-bit +# Build the binaries to go in the installers, in both 32- and 64-bit # flavours. # # For the 32-bit ones, we set a subsystem version of 5.01, which @@ -207,7 +194,7 @@ ifneq "$(cross_winsigncode)" "" in putty/windows do $(cross_winsigncode) -N -i h # of these versions of the binaries. We'll make the rest below. in putty do for hash in md5 sha1 sha256 sha512; do for dir_plat in "build32 w32" "build64 w64" "abuild32 wa32" "abuild64 wa64"; do set -- $$dir_plat; (cd windows/$$1 && $${hash}sum *.exe | sed 's!\( \+\)!\1'$$2'/!;s!$$! (installer version)!') >> $${hash}sums.installer; done; done -# Build a WiX MSI installer, for each of build32 and build64. +# Build a WiX MSI installer, for each build flavour. in putty/windows with wixonlinux do candle -arch x86 -dRealPlatform=x86 -dDllOk=yes -dBuilddir=build32/ -dWinver="$(Winver)" -dPuttytextver="$(Puttytextver)" installer.wxs && light -ext WixUIExtension -ext WixUtilExtension -sval installer.wixobj -o installer32.msi -spdb in putty/windows with wixonlinux do candle -arch x64 -dRealPlatform=x64 -dDllOk=yes -dBuilddir=build64/ -dWinver="$(Winver)" -dPuttytextver="$(Puttytextver)" installer.wxs && light -ext WixUIExtension -ext WixUtilExtension -sval installer.wixobj -o installer64.msi -spdb in putty/windows with wixonlinux do candle -arch x64 -dRealPlatform=Arm -dDllOk=no -dBuilddir=abuild32/ -dWinver="$(Winver)" -dPuttytextver="$(Puttytextver)" installer.wxs && light -ext WixUIExtension -ext WixUtilExtension -sval installer.wixobj -o installera32.msi -spdb diff --git a/Buildscr.cv b/Buildscr.cv index a888e24..deaf8be 100644 --- a/Buildscr.cv +++ b/Buildscr.cv @@ -25,7 +25,7 @@ enddelegate # Windows scanner for download). delegate covscan32wine in putty do tar xzvf cov-int.tar.gz - in putty/windows do cov-build --dir ../cov-int make -f Makefile.mgw CC=winegcc RC=wrc XFLAGS=-DCOVERITY + in putty/windows do cov-build --dir ../cov-int make -f Makefile.mgw CC=winegcc RC=wrc XFLAGS="-DCOVERITY -DNO_SECUREZEROMEMORY -D_FORCE_SOFTWARE_AES" in putty do tar czvf cov-int.tar.gz cov-int return putty/cov-int.tar.gz enddelegate diff --git a/CHECKLST.txt b/CHECKLST.txt new file mode 100644 index 0000000..abf5cd4 --- /dev/null +++ b/CHECKLST.txt @@ -0,0 +1,213 @@ +Checklists for PuTTY administrative procedures +============================================== + +Going into pre-release stabilisation +------------------------------------ + +When we begin to work towards a release and want to enabling +pre-releases on the website: + + - Make a branch whose tip will be the current state of the + pre-release. Regardless of whether the branch is from master or + from a prior release branch, the name of the branch must now be in + the form 'pre-X.YZ', or else the website will fail to link to it + properly in gitweb and the build script will check out the wrong + thing. + + - Edit ~/adm/puttysnap.sh on my build machine to set $prerelver correctly. + + - Edit ~/adm/puttysnap.sh on the master machine to enable pre-release + builds, by changing the 'if false' to 'if true'. + + - Put the website into pre-release mode, by defining prerel_version() + in components/Base.mc to return the upcoming version number. Also + add a news announcement in components/news. (Previous naming + convention has been to name it in the form 'X.YZ-pre.mi'.) + +Things to do during the branch-stabilisation period: + + - Go through the source (including the documentation), and the + website, and review anything tagged with a comment containing the + word XXX-REVIEW-BEFORE-RELEASE. (Any such comments should state + clearly what needs to be done.) + + - Do some testing of the Windows version with Minefield (you can + build a Minefield version using 'bob . XFLAGS=-DMINEFIELD'), and of + the Unix version with valgrind. In particular, any headline + features for the release should get a workout with memory checking + enabled! + +Making a release candidate build +-------------------------------- + + - Make a directory to hold all the release paraphernalia. I usually + call it ~/src/putty/X.YZ (where X.YZ will stand throughout for the + version number). In that directory, make a git clone of the PuTTY + repository, where you can make release-related commits and tags + tentatively, and keep them out of the way of any 'git push' you + might still be doing in other checkouts. + + - Double-check that we have removed anything tagged with a comment + containing the words XXX-REMOVE-BEFORE-RELEASE or + XXX-REVIEW-BEFORE-RELEASE. ('git grep XXX-RE' should only show up + hits in this file itself.) + + - Now update the version numbers and the transcripts in the docs, by + checking out the release branch in the release-specific checkout + and running + + ./release.pl --version=X.YZ --setver + + Then check that the resulting automated git commit has updated the + version number in the following places: + + * putty/LATEST.VER + * putty/doc/plink.but + * putty/doc/pscp.but + + and also check that it has reset the definition of 'Epoch' in + Buildscr. + + - Make the release tag, pointing at the version-update commit we just + generated. + + - If the release is on a branch (which I expect it generally will + be), merge that branch to master. + + - Make a release-candidate build from the release tag, and put the + build.out and build.log dfiles somewhere safe. Normally I store + these in an adjacent directory, so I'll run a command like + bob -o ../X.YZ/build-X.YZ-rcN.out -l ../X.YZ/build-X.YZ-rcN.log -c X.YZ . RELEASE=X.YZ + This should generate a basically valid release directory as + `build-X.YZ-rcN.out/putty', and provide link maps and sign.sh + alongside that. + + - Double-check in build-X.YZ-rcN.log that the release was built from + the right git commit. + + - Make a preliminary gpg signature, but don't run the full release- + signing procedure. (We use the presence of a full set of GPG + signatures to distinguish _abandoned_ release candidates from the + one that ended up being the release.) In the 'build.X.YZ-rcN.out' + directory, run + sh sign.sh -r -p putty + and you should only have to enter the release key passphrase once, + which will generate a clearsigned file called + sha512sums-preliminary.gpg _outside_ the 'putty' subdirectory. + + - For my own safety, make the release candidate build read-only. + chmod -R a-w build-X.YZ-rcN.out build-X.YZ-rcN.log + + - Now do some checking of the release binaries, and pass them to the + rest of the team to do some as well. Do at least these things: + * make sure they basically work + * check they report the right version number + * if there's any easily observable behaviour difference between + the release branch and master, arrange to observe it + * test the Windows installer + * test the Unix source tarball. + +Preparing to make the release +----------------------------- + + - Write a release announcement (basically a summary of the changes + since the last release). Squirrel it away in + thyestes:src/putty-local/announce- in case it's needed again + within days of the release going out. + + - Update the website, in a local checkout: + * Write a release file in components/releases which identifies the + new version, a section for the Changes page, and a news + announcement for the front page. + + The one thing this can't yet contain is the release date; + that has to be put in at the last minute, when the release + goes live. Fill in 'FIXME', for the moment. + * Disable the pre-release sections of the website (if previously + enabled), by editing prerel_version() in components/Base.mc to + return undef. + + - Update the wishlist, in a local checkout: + * If there are any last-minute wishlist entries (e.g. security + vulnerabilities fixed in the new release), write entries for + them. + * If any other bug fixes have been cherry-picked to the release + branch (so that the wishlist mechanism can't automatically mark + them as fixed in the new release), add appropriate Fixed-in + headers for those. + + - Sign the release in full. In the `build-X.YZ-rcN.out' directory, + re-verify that the preliminary signed checksums file has a correct + signature on it and also matches the files you're about to sign for real: + gpg -d sha512sums-preliminary.gpg | (cd putty; grep -vF ' (installer version)' | grep . | sha512sum -c) + If the combined output of that pipeline reports both a good + signature (from the release key) and a successful verification of + all the sha512sums, then all is well, so now run + sh sign.sh -r putty + and enter the release key passphrase a lot of times. + +The actual release procedure +---------------------------- + +Once all the above preparation is done and the release has been built +locally, this is the procedure for putting it up on the web. + + - Make a final adjustment to your local website changes, filling in + the release date in components/releases/X.YZ.mi. + + - Upload the release itself and its link maps to everywhere it needs + to be, by running this in the build.out directory: + ../release.pl --version=X.YZ --upload + + - Check that downloads via version-numbered URLs all work: + ../release.pl --version=X.YZ --precheck + If this has trouble accessing chiark's ftp server, that is + unfortunately normal; add --no-ftp and try again. + + - Switch the 'latest' links over to the new release: + * Update the HTTP redirect at the:www/putty/htaccess . + * Update the FTP symlink at chiark:ftp/putty-latest . + + - Now verify that downloads via the 'latest' URLs are all redirected + correctly and work: + ../release.pl --version=X.YZ --postcheck + + - Push all the git repositories: + * run 'git push' in the website checkout + * run 'git push' in the wishlist checkout + * push from the main PuTTY checkout. Typically this one will be + pushing both the release tag and an update to the master branch, + plus removing the pre-release branch, so you'll want some + commands along these lines: + git push origin master # update the master branch + git push origin --tags # should push the new release tag + git push origin :pre-X.YZ # delete the pre-release branch + + - Run ~/adm/puttyweb.sh on thyestes to update the website after all + those git pushes. + + - Check that the unpublished website on thyestes looks sensible. + + - Run webupdate, so that all the changes on thyestes propagate to + chiark. Important to do this _before_ announcing that the release + is available. + + - After running webupdate, run update-rsync on chiark and verify that + the rsync mirror package (~/ftp/putty-website-mirror) contains a + subdirectory for the new version and that the links from its + latest.html point into that subdirectory. + + - Announce the release! + + Construct a release announcement email whose message body is the + announcement written above, and which includes the following + headers: + * Reply-To: + * Subject: PuTTY X.YZ is released + + Mail that release announcement to + . + + Post it to comp.security.ssh. + + Mention it in on mono. + + - Edit the master ~/adm/puttysnap.sh to disable pre-release builds, + if they were previously enabled. + + - Relax (slightly). diff --git a/LATEST.VER b/LATEST.VER new file mode 100644 index 0000000..b214dd9 --- /dev/null +++ b/LATEST.VER @@ -0,0 +1 @@ +0.72 diff --git a/Makefile.am b/Makefile.am new file mode 100644 index 0000000..3360c6b --- /dev/null +++ b/Makefile.am @@ -0,0 +1,398 @@ +# Makefile.am for putty under Unix with Autoconf/Automake. +# +# This file was created by `mkfiles.pl' from the `Recipe' file. +# DO NOT EDIT THIS FILE DIRECTLY; edit Recipe or mkfiles.pl instead. + +AUTOMAKE_OPTIONS = subdir-objects + +allsources = agentf.c aqsync.c be_all_s.c be_misc.c be_none.c be_nos_s.c \ + be_ssh.c callback.c cgtest.c charset/charset.h \ + charset/enum.c charset/fromucs.c charset/internal.h \ + charset/localenc.c charset/macenc.c charset/mimeenc.c \ + charset/sbcs.c charset/sbcsdat.c charset/slookup.c \ + charset/toucs.c charset/utf8.c charset/xenc.c cmdgen.c \ + cmdline.c conf.c config.c cproxy.c defs.h dialog.c dialog.h \ + ecc.c ecc.h errsock.c fuzzterm.c import.c ldisc.c ldisc.h \ + licence.h logging.c mainchan.c marshal.c marshal.h memory.c \ + minibidi.c misc.c misc.h miscucs.c mpint.c mpint.h mpint_i.h \ + network.h nocmdline.c nocproxy.c nogss.c noshare.c noterm.c \ + notiming.c nullplug.c pageant.c pageant.h pgssapi.c \ + pgssapi.h pinger.c portfwd.c proxy.c proxy.h pscp.c psftp.c \ + psftp.h psftpcommon.c putty.h puttymem.h puttyps.h raw.c \ + rlogin.c scpserver.c sercfg.c sesschan.c sessprep.c \ + settings.c sftp.c sftp.h sftpcommon.c sftpserver.c ssh.c \ + ssh.h ssh1bpp.c ssh1censor.c ssh1connection-client.c \ + ssh1connection-server.c ssh1connection.c ssh1connection.h \ + ssh1login-server.c ssh1login.c ssh2bpp-bare.c ssh2bpp.c \ + ssh2censor.c ssh2connection-client.c ssh2connection-server.c \ + ssh2connection.c ssh2connection.h ssh2kex-client.c \ + ssh2kex-server.c ssh2transhk.c ssh2transport.c \ + ssh2transport.h ssh2userauth-server.c ssh2userauth.c \ + sshaes.c ssharcf.c sshauxcrypt.c sshbcrypt.c sshblowf.c \ + sshblowf.h sshbpp.h sshccp.c sshchan.h sshcommon.c sshcr.h \ + sshcrc.c sshcrcda.c sshdes.c sshdh.c sshdss.c sshdssg.c \ + sshecc.c sshecdsag.c sshgss.h sshgssc.c sshgssc.h sshhmac.c \ + sshmac.c sshmd5.c sshppl.h sshprime.c sshprng.c sshpubk.c \ + sshrand.c sshrsa.c sshrsag.c sshserver.c sshserver.h \ + sshsh256.c sshsh512.c sshsha.c sshshare.c sshsignals.h \ + sshttymodes.h sshverstring.c sshzlib.c storage.h stripctrl.c \ + telnet.c terminal.c terminal.h testcrypt.c testcrypt.h \ + testsc.c testzlib.c time.c timing.c tree234.c tree234.h \ + unix/gtkapp.c unix/gtkask.c unix/gtkcfg.c unix/gtkcols.c \ + unix/gtkcols.h unix/gtkcomm.c unix/gtkcompat.h unix/gtkdlg.c \ + unix/gtkfont.c unix/gtkfont.h unix/gtkmain.c unix/gtkmisc.c \ + unix/gtkmisc.h unix/gtkwin.c unix/osxlaunch.c unix/procnet.c \ + unix/unix.h unix/ux_x11.c unix/uxagentc.c unix/uxagentsock.c \ + unix/uxcfg.c unix/uxcons.c unix/uxfdsock.c unix/uxgen.c \ + unix/uxgss.c unix/uxmisc.c unix/uxnet.c unix/uxnogtk.c \ + unix/uxnoise.c unix/uxpeer.c unix/uxpgnt.c unix/uxplink.c \ + unix/uxpoll.c unix/uxprint.c unix/uxproxy.c unix/uxpterm.c \ + unix/uxpty.c unix/uxputty.c unix/uxsel.c unix/uxser.c \ + unix/uxserver.c unix/uxsftp.c unix/uxsftpserver.c \ + unix/uxshare.c unix/uxsignal.c unix/uxstore.c unix/uxucs.c \ + unix/uxutils.c unix/x11misc.c unix/x11misc.h unix/xkeysym.c \ + unix/xpmptcfg.c unix/xpmpterm.c unix/xpmpucfg.c \ + unix/xpmputty.c utils.c version.c version.h wcwidth.c \ + wildcard.c windows/pageant.rc windows/plink.rc \ + windows/pscp.rc windows/psftp.rc windows/putty.rc \ + windows/puttygen.rc windows/puttytel.rc windows/rcstuff.h \ + windows/sizetip.c windows/version.rc2 windows/win_res.h \ + windows/win_res.rc2 windows/wincapi.c windows/wincapi.h \ + windows/wincfg.c windows/wincons.c windows/winctrls.c \ + windows/windefs.c windows/windlg.c windows/window.c \ + windows/wingss.c windows/winhandl.c windows/winhelp.c \ + windows/winhelp.h windows/winhelp.rc2 windows/winhsock.c \ + windows/winjump.c windows/winmisc.c windows/winmiscs.c \ + windows/winnet.c windows/winnohlp.c windows/winnoise.c \ + windows/winnojmp.c windows/winnpc.c windows/winnps.c \ + windows/winpgen.c windows/winpgnt.c windows/winpgntc.c \ + windows/winplink.c windows/winprint.c windows/winproxy.c \ + windows/winsecur.c windows/winsecur.h windows/winser.c \ + windows/winsftp.c windows/winshare.c windows/winstore.c \ + windows/winstuff.h windows/wintime.c windows/winucs.c \ + windows/winutils.c windows/winx11.c x11fwd.c + +if HAVE_GTK +bin_PROGRAMS = plink pscp psftp puttygen pageant pterm putty puttytel +else +bin_PROGRAMS = plink pscp psftp puttygen +endif + +if HAVE_GTK +noinst_PROGRAMS = cgtest fuzzterm osxlaunch testcrypt testsc testzlib uppity \ + ptermapp puttyapp +else +noinst_PROGRAMS = cgtest fuzzterm osxlaunch testcrypt testsc testzlib uppity +endif + +AM_CPPFLAGS = -I$(srcdir)/./ -I$(srcdir)/charset/ -I$(srcdir)/windows/ \ + -I$(srcdir)/unix/ +if HAVE_GTK +AM_CFLAGS = $(GTK_CFLAGS) $(COMPAT) $(XFLAGS) $(WARNINGOPTS) +else +AM_CFLAGS = $(COMPAT) $(XFLAGS) $(WARNINGOPTS) +endif + +libversion_a_SOURCES = version.c +libversion_a_CFLAGS = $(COMPAT) $(XFLAGS) $(WARNINGOPTS) +noinst_LIBRARIES = libversion.a + +cgtest_SOURCES = cgtest.c conf.c ecc.c import.c marshal.c memory.c misc.c \ + mpint.c notiming.c sshaes.c sshauxcrypt.c sshbcrypt.c \ + sshblowf.c sshdes.c sshdss.c sshdssg.c sshecc.c sshecdsag.c \ + sshhmac.c sshmd5.c sshprime.c sshprng.c sshpubk.c sshrand.c \ + sshrsa.c sshrsag.c sshsh256.c sshsh512.c sshsha.c \ + stripctrl.c time.c tree234.c unix/uxcons.c unix/uxgen.c \ + unix/uxmisc.c unix/uxnogtk.c unix/uxnoise.c unix/uxpoll.c \ + unix/uxstore.c unix/uxutils.c utils.c wcwidth.c +cgtest_LDADD = libversion.a + +fuzzterm_SOURCES = be_none.c callback.c charset/fromucs.c charset/localenc.c \ + charset/macenc.c charset/mimeenc.c charset/sbcs.c \ + charset/sbcsdat.c charset/slookup.c charset/toucs.c \ + charset/utf8.c charset/xenc.c conf.c config.c dialog.c \ + fuzzterm.c logging.c marshal.c memory.c minibidi.c misc.c \ + miscucs.c sercfg.c settings.c stripctrl.c terminal.c time.c \ + timing.c tree234.c unix/uxcfg.c unix/uxmisc.c unix/uxnogtk.c \ + unix/uxprint.c unix/uxstore.c unix/uxucs.c utils.c wcwidth.c +fuzzterm_LDADD = libversion.a + +osxlaunch_SOURCES = unix/osxlaunch.c + +if HAVE_GTK +pageant_SOURCES = aqsync.c be_misc.c be_none.c callback.c conf.c ecc.c \ + errsock.c logging.c marshal.c memory.c misc.c mpint.c \ + nocproxy.c nogss.c nullplug.c pageant.c proxy.c settings.c \ + sshaes.c sshauxcrypt.c sshdes.c sshdss.c sshecc.c sshhmac.c \ + sshmd5.c sshprng.c sshpubk.c sshrsa.c sshsh256.c sshsh512.c \ + sshsha.c stripctrl.c time.c timing.c tree234.c unix/gtkask.c \ + unix/gtkmisc.c unix/ux_x11.c unix/uxagentc.c \ + unix/uxagentsock.c unix/uxcons.c unix/uxfdsock.c \ + unix/uxmisc.c unix/uxnet.c unix/uxnoise.c unix/uxpeer.c \ + unix/uxpgnt.c unix/uxpoll.c unix/uxproxy.c unix/uxsel.c \ + unix/uxsignal.c unix/uxstore.c unix/uxutils.c utils.c \ + wcwidth.c x11fwd.c +pageant_LDADD = libversion.a $(GTK_LIBS) +endif + +plink_SOURCES = agentf.c aqsync.c be_all_s.c be_misc.c callback.c cmdline.c \ + conf.c cproxy.c ecc.c errsock.c ldisc.c logging.c mainchan.c \ + marshal.c memory.c misc.c mpint.c noterm.c nullplug.c \ + pgssapi.c pinger.c portfwd.c proxy.c raw.c rlogin.c \ + sessprep.c settings.c ssh.c ssh1bpp.c ssh1censor.c \ + ssh1connection-client.c ssh1connection.c ssh1login.c \ + ssh2bpp-bare.c ssh2bpp.c ssh2censor.c \ + ssh2connection-client.c ssh2connection.c ssh2kex-client.c \ + ssh2transhk.c ssh2transport.c ssh2userauth.c sshaes.c \ + ssharcf.c sshauxcrypt.c sshblowf.c sshccp.c sshcommon.c \ + sshcrc.c sshcrcda.c sshdes.c sshdh.c sshdss.c sshecc.c \ + sshgssc.c sshhmac.c sshmac.c sshmd5.c sshprng.c sshpubk.c \ + sshrand.c sshrsa.c sshsh256.c sshsh512.c sshsha.c sshshare.c \ + sshverstring.c sshzlib.c stripctrl.c telnet.c time.c \ + timing.c tree234.c unix/ux_x11.c unix/uxagentc.c \ + unix/uxcons.c unix/uxfdsock.c unix/uxgss.c unix/uxmisc.c \ + unix/uxnet.c unix/uxnogtk.c unix/uxnoise.c unix/uxpeer.c \ + unix/uxplink.c unix/uxpoll.c unix/uxproxy.c unix/uxsel.c \ + unix/uxser.c unix/uxshare.c unix/uxsignal.c unix/uxstore.c \ + unix/uxutils.c utils.c wcwidth.c wildcard.c x11fwd.c +plink_LDADD = libversion.a + +pscp_SOURCES = agentf.c aqsync.c be_misc.c be_ssh.c callback.c cmdline.c \ + conf.c cproxy.c ecc.c errsock.c logging.c mainchan.c \ + marshal.c memory.c misc.c mpint.c nullplug.c pgssapi.c \ + pinger.c portfwd.c proxy.c pscp.c psftpcommon.c settings.c \ + sftp.c sftpcommon.c ssh.c ssh1bpp.c ssh1censor.c \ + ssh1connection-client.c ssh1connection.c ssh1login.c \ + ssh2bpp-bare.c ssh2bpp.c ssh2censor.c \ + ssh2connection-client.c ssh2connection.c ssh2kex-client.c \ + ssh2transhk.c ssh2transport.c ssh2userauth.c sshaes.c \ + ssharcf.c sshauxcrypt.c sshblowf.c sshccp.c sshcommon.c \ + sshcrc.c sshcrcda.c sshdes.c sshdh.c sshdss.c sshecc.c \ + sshgssc.c sshhmac.c sshmac.c sshmd5.c sshprng.c sshpubk.c \ + sshrand.c sshrsa.c sshsh256.c sshsh512.c sshsha.c sshshare.c \ + sshverstring.c sshzlib.c stripctrl.c time.c timing.c \ + tree234.c unix/uxagentc.c unix/uxcons.c unix/uxfdsock.c \ + unix/uxgss.c unix/uxmisc.c unix/uxnet.c unix/uxnogtk.c \ + unix/uxnoise.c unix/uxpeer.c unix/uxpoll.c unix/uxproxy.c \ + unix/uxsel.c unix/uxsftp.c unix/uxshare.c unix/uxstore.c \ + unix/uxutils.c utils.c wcwidth.c wildcard.c x11fwd.c +pscp_LDADD = libversion.a + +psftp_SOURCES = agentf.c aqsync.c be_misc.c be_ssh.c callback.c cmdline.c \ + conf.c cproxy.c ecc.c errsock.c logging.c mainchan.c \ + marshal.c memory.c misc.c mpint.c nullplug.c pgssapi.c \ + pinger.c portfwd.c proxy.c psftp.c psftpcommon.c settings.c \ + sftp.c sftpcommon.c ssh.c ssh1bpp.c ssh1censor.c \ + ssh1connection-client.c ssh1connection.c ssh1login.c \ + ssh2bpp-bare.c ssh2bpp.c ssh2censor.c \ + ssh2connection-client.c ssh2connection.c ssh2kex-client.c \ + ssh2transhk.c ssh2transport.c ssh2userauth.c sshaes.c \ + ssharcf.c sshauxcrypt.c sshblowf.c sshccp.c sshcommon.c \ + sshcrc.c sshcrcda.c sshdes.c sshdh.c sshdss.c sshecc.c \ + sshgssc.c sshhmac.c sshmac.c sshmd5.c sshprng.c sshpubk.c \ + sshrand.c sshrsa.c sshsh256.c sshsh512.c sshsha.c sshshare.c \ + sshverstring.c sshzlib.c stripctrl.c time.c timing.c \ + tree234.c unix/uxagentc.c unix/uxcons.c unix/uxfdsock.c \ + unix/uxgss.c unix/uxmisc.c unix/uxnet.c unix/uxnogtk.c \ + unix/uxnoise.c unix/uxpeer.c unix/uxpoll.c unix/uxproxy.c \ + unix/uxsel.c unix/uxsftp.c unix/uxshare.c unix/uxstore.c \ + unix/uxutils.c utils.c wcwidth.c wildcard.c x11fwd.c +psftp_LDADD = libversion.a + +if HAVE_GTK +pterm_SOURCES = be_none.c callback.c charset/fromucs.c charset/localenc.c \ + charset/macenc.c charset/mimeenc.c charset/sbcs.c \ + charset/sbcsdat.c charset/slookup.c charset/toucs.c \ + charset/utf8.c charset/xenc.c cmdline.c conf.c config.c \ + dialog.c ldisc.c logging.c marshal.c memory.c minibidi.c \ + misc.c miscucs.c nocproxy.c nogss.c sercfg.c sessprep.c \ + settings.c stripctrl.c terminal.c time.c timing.c tree234.c \ + unix/gtkcfg.c unix/gtkcols.c unix/gtkcomm.c unix/gtkdlg.c \ + unix/gtkfont.c unix/gtkmain.c unix/gtkmisc.c unix/gtkwin.c \ + unix/uxcfg.c unix/uxmisc.c unix/uxprint.c unix/uxpterm.c \ + unix/uxpty.c unix/uxsel.c unix/uxsignal.c unix/uxstore.c \ + unix/uxucs.c unix/x11misc.c unix/xkeysym.c unix/xpmptcfg.c \ + unix/xpmpterm.c utils.c wcwidth.c +pterm_LDADD = libversion.a $(GTK_LIBS) +endif + +if HAVE_GTK +ptermapp_SOURCES = be_none.c callback.c charset/fromucs.c charset/localenc.c \ + charset/macenc.c charset/mimeenc.c charset/sbcs.c \ + charset/sbcsdat.c charset/slookup.c charset/toucs.c \ + charset/utf8.c charset/xenc.c conf.c config.c dialog.c \ + ldisc.c logging.c marshal.c memory.c minibidi.c misc.c \ + miscucs.c nocmdline.c nocproxy.c nogss.c sercfg.c sessprep.c \ + settings.c stripctrl.c terminal.c time.c timing.c tree234.c \ + unix/gtkapp.c unix/gtkcfg.c unix/gtkcols.c unix/gtkcomm.c \ + unix/gtkdlg.c unix/gtkfont.c unix/gtkmisc.c unix/gtkwin.c \ + unix/uxcfg.c unix/uxmisc.c unix/uxprint.c unix/uxpterm.c \ + unix/uxpty.c unix/uxsel.c unix/uxsignal.c unix/uxstore.c \ + unix/uxucs.c unix/x11misc.c unix/xkeysym.c unix/xpmptcfg.c \ + unix/xpmpterm.c utils.c wcwidth.c +ptermapp_LDADD = libversion.a $(GTK_LIBS) +endif + +if HAVE_GTK +putty_SOURCES = agentf.c aqsync.c be_all_s.c be_misc.c callback.c \ + charset/fromucs.c charset/localenc.c charset/macenc.c \ + charset/mimeenc.c charset/sbcs.c charset/sbcsdat.c \ + charset/slookup.c charset/toucs.c charset/utf8.c \ + charset/xenc.c cmdline.c conf.c config.c cproxy.c dialog.c \ + ecc.c errsock.c ldisc.c logging.c mainchan.c marshal.c \ + memory.c minibidi.c misc.c miscucs.c mpint.c nullplug.c \ + pgssapi.c pinger.c portfwd.c proxy.c raw.c rlogin.c sercfg.c \ + sessprep.c settings.c ssh.c ssh1bpp.c ssh1censor.c \ + ssh1connection-client.c ssh1connection.c ssh1login.c \ + ssh2bpp-bare.c ssh2bpp.c ssh2censor.c \ + ssh2connection-client.c ssh2connection.c ssh2kex-client.c \ + ssh2transhk.c ssh2transport.c ssh2userauth.c sshaes.c \ + ssharcf.c sshauxcrypt.c sshblowf.c sshccp.c sshcommon.c \ + sshcrc.c sshcrcda.c sshdes.c sshdh.c sshdss.c sshecc.c \ + sshgssc.c sshhmac.c sshmac.c sshmd5.c sshprng.c sshpubk.c \ + sshrand.c sshrsa.c sshsh256.c sshsh512.c sshsha.c sshshare.c \ + sshverstring.c sshzlib.c stripctrl.c telnet.c terminal.c \ + time.c timing.c tree234.c unix/gtkcfg.c unix/gtkcols.c \ + unix/gtkcomm.c unix/gtkdlg.c unix/gtkfont.c unix/gtkmain.c \ + unix/gtkmisc.c unix/gtkwin.c unix/ux_x11.c unix/uxagentc.c \ + unix/uxcfg.c unix/uxfdsock.c unix/uxgss.c unix/uxmisc.c \ + unix/uxnet.c unix/uxnoise.c unix/uxpeer.c unix/uxpoll.c \ + unix/uxprint.c unix/uxproxy.c unix/uxputty.c unix/uxsel.c \ + unix/uxser.c unix/uxshare.c unix/uxsignal.c unix/uxstore.c \ + unix/uxucs.c unix/uxutils.c unix/x11misc.c unix/xkeysym.c \ + unix/xpmpucfg.c unix/xpmputty.c utils.c wcwidth.c wildcard.c \ + x11fwd.c +putty_LDADD = libversion.a $(GTK_LIBS) +endif + +if HAVE_GTK +puttyapp_SOURCES = agentf.c aqsync.c be_all_s.c be_misc.c callback.c \ + charset/fromucs.c charset/localenc.c charset/macenc.c \ + charset/mimeenc.c charset/sbcs.c charset/sbcsdat.c \ + charset/slookup.c charset/toucs.c charset/utf8.c \ + charset/xenc.c conf.c config.c cproxy.c dialog.c ecc.c \ + errsock.c ldisc.c logging.c mainchan.c marshal.c memory.c \ + minibidi.c misc.c miscucs.c mpint.c nocmdline.c nullplug.c \ + pgssapi.c pinger.c portfwd.c proxy.c raw.c rlogin.c sercfg.c \ + sessprep.c settings.c ssh.c ssh1bpp.c ssh1censor.c \ + ssh1connection-client.c ssh1connection.c ssh1login.c \ + ssh2bpp-bare.c ssh2bpp.c ssh2censor.c \ + ssh2connection-client.c ssh2connection.c ssh2kex-client.c \ + ssh2transhk.c ssh2transport.c ssh2userauth.c sshaes.c \ + ssharcf.c sshauxcrypt.c sshblowf.c sshccp.c sshcommon.c \ + sshcrc.c sshcrcda.c sshdes.c sshdh.c sshdss.c sshecc.c \ + sshgssc.c sshhmac.c sshmac.c sshmd5.c sshprng.c sshpubk.c \ + sshrand.c sshrsa.c sshsh256.c sshsh512.c sshsha.c sshshare.c \ + sshverstring.c sshzlib.c stripctrl.c telnet.c terminal.c \ + time.c timing.c tree234.c unix/gtkapp.c unix/gtkcfg.c \ + unix/gtkcols.c unix/gtkcomm.c unix/gtkdlg.c unix/gtkfont.c \ + unix/gtkmisc.c unix/gtkwin.c unix/ux_x11.c unix/uxagentc.c \ + unix/uxcfg.c unix/uxfdsock.c unix/uxgss.c unix/uxmisc.c \ + unix/uxnet.c unix/uxnoise.c unix/uxpeer.c unix/uxpoll.c \ + unix/uxprint.c unix/uxproxy.c unix/uxputty.c unix/uxsel.c \ + unix/uxser.c unix/uxshare.c unix/uxsignal.c unix/uxstore.c \ + unix/uxucs.c unix/uxutils.c unix/x11misc.c unix/xkeysym.c \ + unix/xpmpucfg.c unix/xpmputty.c utils.c wcwidth.c wildcard.c \ + x11fwd.c +puttyapp_LDADD = libversion.a $(GTK_LIBS) +endif + +puttygen_SOURCES = cmdgen.c conf.c ecc.c import.c marshal.c memory.c misc.c \ + mpint.c notiming.c sshaes.c sshauxcrypt.c sshbcrypt.c \ + sshblowf.c sshdes.c sshdss.c sshdssg.c sshecc.c sshecdsag.c \ + sshhmac.c sshmd5.c sshprime.c sshprng.c sshpubk.c sshrand.c \ + sshrsa.c sshrsag.c sshsh256.c sshsh512.c sshsha.c \ + stripctrl.c time.c tree234.c unix/uxcons.c unix/uxgen.c \ + unix/uxmisc.c unix/uxnogtk.c unix/uxnoise.c unix/uxpoll.c \ + unix/uxstore.c unix/uxutils.c utils.c wcwidth.c +puttygen_LDADD = libversion.a + +if HAVE_GTK +puttytel_SOURCES = be_misc.c be_nos_s.c callback.c charset/fromucs.c \ + charset/localenc.c charset/macenc.c charset/mimeenc.c \ + charset/sbcs.c charset/sbcsdat.c charset/slookup.c \ + charset/toucs.c charset/utf8.c charset/xenc.c cmdline.c \ + conf.c config.c dialog.c errsock.c ldisc.c logging.c \ + marshal.c memory.c minibidi.c misc.c miscucs.c nocproxy.c \ + nogss.c pinger.c proxy.c raw.c rlogin.c sercfg.c sessprep.c \ + settings.c stripctrl.c telnet.c terminal.c time.c timing.c \ + tree234.c unix/gtkcfg.c unix/gtkcols.c unix/gtkcomm.c \ + unix/gtkdlg.c unix/gtkfont.c unix/gtkmain.c unix/gtkmisc.c \ + unix/gtkwin.c unix/uxcfg.c unix/uxfdsock.c unix/uxmisc.c \ + unix/uxnet.c unix/uxpeer.c unix/uxpoll.c unix/uxprint.c \ + unix/uxproxy.c unix/uxputty.c unix/uxsel.c unix/uxser.c \ + unix/uxsignal.c unix/uxstore.c unix/uxucs.c unix/uxutils.c \ + unix/x11misc.c unix/xkeysym.c unix/xpmpucfg.c \ + unix/xpmputty.c utils.c wcwidth.c +puttytel_LDADD = libversion.a $(GTK_LIBS) +endif + +testcrypt_SOURCES = ecc.c marshal.c memory.c mpint.c sshaes.c ssharcf.c \ + sshauxcrypt.c sshblowf.c sshccp.c sshcrc.c sshcrcda.c \ + sshdes.c sshdh.c sshdss.c sshecc.c sshhmac.c sshmd5.c \ + sshprime.c sshprng.c sshrsa.c sshsh256.c sshsh512.c sshsha.c \ + testcrypt.c tree234.c unix/uxutils.c utils.c + +testsc_SOURCES = ecc.c marshal.c memory.c mpint.c sshaes.c ssharcf.c \ + sshauxcrypt.c sshblowf.c sshccp.c sshcrc.c sshcrcda.c \ + sshdes.c sshdh.c sshdss.c sshecc.c sshhmac.c sshmac.c \ + sshmd5.c sshrsa.c sshsh256.c sshsh512.c sshsha.c testsc.c \ + tree234.c unix/uxutils.c utils.c wildcard.c + +testzlib_SOURCES = marshal.c memory.c sshzlib.c testzlib.c utils.c + +uppity_SOURCES = be_misc.c be_none.c callback.c conf.c cproxy.c ecc.c \ + errsock.c logging.c marshal.c memory.c misc.c mpint.c \ + nullplug.c pgssapi.c portfwd.c proxy.c scpserver.c \ + sesschan.c settings.c sftpcommon.c sftpserver.c ssh1bpp.c \ + ssh1censor.c ssh1connection-server.c ssh1connection.c \ + ssh1login-server.c ssh2bpp.c ssh2censor.c \ + ssh2connection-server.c ssh2connection.c ssh2kex-server.c \ + ssh2transhk.c ssh2transport.c ssh2userauth-server.c sshaes.c \ + ssharcf.c sshauxcrypt.c sshblowf.c sshccp.c sshcommon.c \ + sshcrc.c sshcrcda.c sshdes.c sshdh.c sshdss.c sshecc.c \ + sshgssc.c sshhmac.c sshmac.c sshmd5.c sshprime.c sshprng.c \ + sshpubk.c sshrand.c sshrsa.c sshrsag.c sshserver.c \ + sshsh256.c sshsh512.c sshsha.c sshverstring.c sshzlib.c \ + stripctrl.c time.c timing.c tree234.c unix/procnet.c \ + unix/ux_x11.c unix/uxagentsock.c unix/uxfdsock.c \ + unix/uxgss.c unix/uxmisc.c unix/uxnet.c unix/uxnogtk.c \ + unix/uxnoise.c unix/uxpeer.c unix/uxpoll.c unix/uxproxy.c \ + unix/uxpty.c unix/uxsel.c unix/uxserver.c \ + unix/uxsftpserver.c unix/uxsignal.c unix/uxstore.c \ + unix/uxutils.c utils.c wcwidth.c wildcard.c x11fwd.c +uppity_LDADD = libversion.a + +if AUTO_GIT_COMMIT +BUILT_SOURCES = empty.h +CLEANFILES = empty.h +libversion_a_CFLAGS += -DSOURCE_COMMIT=\"`git --git-dir=$(srcdir)/.git rev-parse HEAD 2>/dev/null`\" +empty.h: $(allsources) + echo '/* Empty file touched by automake makefile to force rebuild of version.o */' >$@ +endif + +# Run the cryptsuite tests as part of 'make check'. Override +# PUTTY_TESTCRYPT so that cryptsuite will take the testcrypt binary +# from the build directory instead of the source directory, in case +# this is an out-of-tree build. +check-local: testcrypt + PUTTY_TESTCRYPT=./testcrypt $(srcdir)/test/cryptsuite.py + +if HAVE_GTK +man1_MANS = doc/plink.1 doc/pscp.1 doc/psftp.1 doc/puttygen.1 \ + doc/pageant.1 doc/pterm.1 doc/putty.1 doc/puttytel.1 +else +man1_MANS = doc/plink.1 doc/pscp.1 doc/psftp.1 doc/puttygen.1 +endif +if HAVE_SETID_CMD +install-exec-local: + @SETID_CMD@ $(bindir)/pterm + chmod @SETID_MODE@ $(bindir)/pterm +endif +if HAVE_QUARTZ +noinst_SCRIPTS = unix/PuTTY.app unix/Pterm.app +unix/PuTTY.app: unix/putty.bundle puttyapp osxlaunch + rm -rf $@ && PUTTY_GTK_PREFIX_FROM_MAKEFILE=$$(pkg-config --variable=prefix gtk+-3.0) gtk-mac-bundler $< +unix/Pterm.app: unix/pterm.bundle ptermapp osxlaunch + rm -rf $@ && PUTTY_GTK_PREFIX_FROM_MAKEFILE=$$(pkg-config --variable=prefix gtk+-3.0) gtk-mac-bundler $< +endif diff --git a/Makefile.in b/Makefile.in new file mode 100644 index 0000000..effd70a --- /dev/null +++ b/Makefile.in @@ -0,0 +1,2267 @@ +# Makefile.in generated by automake 1.15.1 from Makefile.am. +# @configure_input@ + +# Copyright (C) 1994-2017 Free Software Foundation, Inc. + +# This Makefile.in is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY, to the extent permitted by law; without +# even the implied warranty of MERCHANTABILITY or FITNESS FOR A +# PARTICULAR PURPOSE. + +@SET_MAKE@ + +# Makefile.am for putty under Unix with Autoconf/Automake. +# +# This file was created by `mkfiles.pl' from the `Recipe' file. +# DO NOT EDIT THIS FILE DIRECTLY; edit Recipe or mkfiles.pl instead. + + + +VPATH = @srcdir@ +am__is_gnu_make = { \ + if test -z '$(MAKELEVEL)'; then \ + false; \ + elif test -n '$(MAKE_HOST)'; then \ + true; \ + elif test -n '$(MAKE_VERSION)' && test -n '$(CURDIR)'; then \ + true; \ + else \ + false; \ + fi; \ +} +am__make_running_with_option = \ + case $${target_option-} in \ + ?) ;; \ + *) echo "am__make_running_with_option: internal error: invalid" \ + "target option '$${target_option-}' specified" >&2; \ + exit 1;; \ + esac; \ + has_opt=no; \ + sane_makeflags=$$MAKEFLAGS; \ + if $(am__is_gnu_make); then \ + sane_makeflags=$$MFLAGS; \ + else \ + case $$MAKEFLAGS in \ + *\\[\ \ ]*) \ + bs=\\; \ + sane_makeflags=`printf '%s\n' "$$MAKEFLAGS" \ + | sed "s/$$bs$$bs[$$bs $$bs ]*//g"`;; \ + esac; \ + fi; \ + skip_next=no; \ + strip_trailopt () \ + { \ + flg=`printf '%s\n' "$$flg" | sed "s/$$1.*$$//"`; \ + }; \ + for flg in $$sane_makeflags; do \ + test $$skip_next = yes && { skip_next=no; continue; }; \ + case $$flg in \ + *=*|--*) continue;; \ + -*I) strip_trailopt 'I'; skip_next=yes;; \ + -*I?*) strip_trailopt 'I';; \ + -*O) strip_trailopt 'O'; skip_next=yes;; \ + -*O?*) strip_trailopt 'O';; \ + -*l) strip_trailopt 'l'; skip_next=yes;; \ + -*l?*) strip_trailopt 'l';; \ + -[dEDm]) skip_next=yes;; \ + -[JT]) skip_next=yes;; \ + esac; \ + case $$flg in \ + *$$target_option*) has_opt=yes; break;; \ + esac; \ + done; \ + test $$has_opt = yes +am__make_dryrun = (target_option=n; $(am__make_running_with_option)) +am__make_keepgoing = (target_option=k; $(am__make_running_with_option)) +pkgdatadir = $(datadir)/@PACKAGE@ +pkgincludedir = $(includedir)/@PACKAGE@ +pkglibdir = $(libdir)/@PACKAGE@ +pkglibexecdir = $(libexecdir)/@PACKAGE@ +am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd +install_sh_DATA = $(install_sh) -c -m 644 +install_sh_PROGRAM = $(install_sh) -c +install_sh_SCRIPT = $(install_sh) -c +INSTALL_HEADER = $(INSTALL_DATA) +transform = $(program_transform_name) +NORMAL_INSTALL = : +PRE_INSTALL = : +POST_INSTALL = : +NORMAL_UNINSTALL = : +PRE_UNINSTALL = : +POST_UNINSTALL = : +@HAVE_GTK_FALSE@bin_PROGRAMS = plink$(EXEEXT) pscp$(EXEEXT) \ +@HAVE_GTK_FALSE@ psftp$(EXEEXT) puttygen$(EXEEXT) +@HAVE_GTK_TRUE@bin_PROGRAMS = plink$(EXEEXT) pscp$(EXEEXT) \ +@HAVE_GTK_TRUE@ psftp$(EXEEXT) puttygen$(EXEEXT) \ +@HAVE_GTK_TRUE@ pageant$(EXEEXT) pterm$(EXEEXT) putty$(EXEEXT) \ +@HAVE_GTK_TRUE@ puttytel$(EXEEXT) +@HAVE_GTK_FALSE@noinst_PROGRAMS = cgtest$(EXEEXT) fuzzterm$(EXEEXT) \ +@HAVE_GTK_FALSE@ osxlaunch$(EXEEXT) testcrypt$(EXEEXT) \ +@HAVE_GTK_FALSE@ testsc$(EXEEXT) testzlib$(EXEEXT) \ +@HAVE_GTK_FALSE@ uppity$(EXEEXT) +@HAVE_GTK_TRUE@noinst_PROGRAMS = cgtest$(EXEEXT) fuzzterm$(EXEEXT) \ +@HAVE_GTK_TRUE@ osxlaunch$(EXEEXT) testcrypt$(EXEEXT) \ +@HAVE_GTK_TRUE@ testsc$(EXEEXT) testzlib$(EXEEXT) \ +@HAVE_GTK_TRUE@ uppity$(EXEEXT) ptermapp$(EXEEXT) \ +@HAVE_GTK_TRUE@ puttyapp$(EXEEXT) +@AUTO_GIT_COMMIT_TRUE@am__append_1 = -DSOURCE_COMMIT=\"`git --git-dir=$(srcdir)/.git rev-parse HEAD 2>/dev/null`\" +subdir = . +ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 +am__aclocal_m4_deps = $(top_srcdir)/configure.ac +am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ + $(ACLOCAL_M4) +DIST_COMMON = $(srcdir)/Makefile.am $(top_srcdir)/configure \ + $(am__configure_deps) $(am__DIST_COMMON) +am__CONFIG_DISTCLEAN_FILES = config.status config.cache config.log \ + configure.lineno config.status.lineno +mkinstalldirs = $(install_sh) -d +CONFIG_HEADER = uxconfig.h +CONFIG_CLEAN_FILES = +CONFIG_CLEAN_VPATH_FILES = +LIBRARIES = $(noinst_LIBRARIES) +ARFLAGS = cru +AM_V_AR = $(am__v_AR_@AM_V@) +am__v_AR_ = $(am__v_AR_@AM_DEFAULT_V@) +am__v_AR_0 = @echo " AR " $@; +am__v_AR_1 = +libversion_a_AR = $(AR) $(ARFLAGS) +libversion_a_LIBADD = +am_libversion_a_OBJECTS = libversion_a-version.$(OBJEXT) +libversion_a_OBJECTS = $(am_libversion_a_OBJECTS) +am__installdirs = "$(DESTDIR)$(bindir)" "$(DESTDIR)$(man1dir)" +PROGRAMS = $(bin_PROGRAMS) $(noinst_PROGRAMS) +am__dirstamp = $(am__leading_dot)dirstamp +am_cgtest_OBJECTS = cgtest.$(OBJEXT) conf.$(OBJEXT) ecc.$(OBJEXT) \ + import.$(OBJEXT) marshal.$(OBJEXT) memory.$(OBJEXT) \ + misc.$(OBJEXT) mpint.$(OBJEXT) notiming.$(OBJEXT) \ + sshaes.$(OBJEXT) sshauxcrypt.$(OBJEXT) sshbcrypt.$(OBJEXT) \ + sshblowf.$(OBJEXT) sshdes.$(OBJEXT) sshdss.$(OBJEXT) \ + sshdssg.$(OBJEXT) sshecc.$(OBJEXT) sshecdsag.$(OBJEXT) \ + sshhmac.$(OBJEXT) sshmd5.$(OBJEXT) sshprime.$(OBJEXT) \ + sshprng.$(OBJEXT) sshpubk.$(OBJEXT) sshrand.$(OBJEXT) \ + sshrsa.$(OBJEXT) sshrsag.$(OBJEXT) sshsh256.$(OBJEXT) \ + sshsh512.$(OBJEXT) sshsha.$(OBJEXT) stripctrl.$(OBJEXT) \ + time.$(OBJEXT) tree234.$(OBJEXT) unix/uxcons.$(OBJEXT) \ + unix/uxgen.$(OBJEXT) unix/uxmisc.$(OBJEXT) \ + unix/uxnogtk.$(OBJEXT) unix/uxnoise.$(OBJEXT) \ + unix/uxpoll.$(OBJEXT) unix/uxstore.$(OBJEXT) \ + unix/uxutils.$(OBJEXT) utils.$(OBJEXT) wcwidth.$(OBJEXT) +cgtest_OBJECTS = $(am_cgtest_OBJECTS) +cgtest_DEPENDENCIES = libversion.a +am_fuzzterm_OBJECTS = be_none.$(OBJEXT) callback.$(OBJEXT) \ + charset/fromucs.$(OBJEXT) charset/localenc.$(OBJEXT) \ + charset/macenc.$(OBJEXT) charset/mimeenc.$(OBJEXT) \ + charset/sbcs.$(OBJEXT) charset/sbcsdat.$(OBJEXT) \ + charset/slookup.$(OBJEXT) charset/toucs.$(OBJEXT) \ + charset/utf8.$(OBJEXT) charset/xenc.$(OBJEXT) conf.$(OBJEXT) \ + config.$(OBJEXT) dialog.$(OBJEXT) fuzzterm.$(OBJEXT) \ + logging.$(OBJEXT) marshal.$(OBJEXT) memory.$(OBJEXT) \ + minibidi.$(OBJEXT) misc.$(OBJEXT) miscucs.$(OBJEXT) \ + sercfg.$(OBJEXT) settings.$(OBJEXT) stripctrl.$(OBJEXT) \ + terminal.$(OBJEXT) time.$(OBJEXT) timing.$(OBJEXT) \ + tree234.$(OBJEXT) unix/uxcfg.$(OBJEXT) unix/uxmisc.$(OBJEXT) \ + unix/uxnogtk.$(OBJEXT) unix/uxprint.$(OBJEXT) \ + unix/uxstore.$(OBJEXT) unix/uxucs.$(OBJEXT) utils.$(OBJEXT) \ + wcwidth.$(OBJEXT) +fuzzterm_OBJECTS = $(am_fuzzterm_OBJECTS) +fuzzterm_DEPENDENCIES = libversion.a +am_osxlaunch_OBJECTS = unix/osxlaunch.$(OBJEXT) +osxlaunch_OBJECTS = $(am_osxlaunch_OBJECTS) +osxlaunch_LDADD = $(LDADD) +am__pageant_SOURCES_DIST = aqsync.c be_misc.c be_none.c callback.c \ + conf.c ecc.c errsock.c logging.c marshal.c memory.c misc.c \ + mpint.c nocproxy.c nogss.c nullplug.c pageant.c proxy.c \ + settings.c sshaes.c sshauxcrypt.c sshdes.c sshdss.c sshecc.c \ + sshhmac.c sshmd5.c sshprng.c sshpubk.c sshrsa.c sshsh256.c \ + sshsh512.c sshsha.c stripctrl.c time.c timing.c tree234.c \ + unix/gtkask.c unix/gtkmisc.c unix/ux_x11.c unix/uxagentc.c \ + unix/uxagentsock.c unix/uxcons.c unix/uxfdsock.c unix/uxmisc.c \ + unix/uxnet.c unix/uxnoise.c unix/uxpeer.c unix/uxpgnt.c \ + unix/uxpoll.c unix/uxproxy.c unix/uxsel.c unix/uxsignal.c \ + unix/uxstore.c unix/uxutils.c utils.c wcwidth.c x11fwd.c +@HAVE_GTK_TRUE@am_pageant_OBJECTS = aqsync.$(OBJEXT) be_misc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ be_none.$(OBJEXT) callback.$(OBJEXT) \ +@HAVE_GTK_TRUE@ conf.$(OBJEXT) ecc.$(OBJEXT) errsock.$(OBJEXT) \ +@HAVE_GTK_TRUE@ logging.$(OBJEXT) marshal.$(OBJEXT) \ +@HAVE_GTK_TRUE@ memory.$(OBJEXT) misc.$(OBJEXT) mpint.$(OBJEXT) \ +@HAVE_GTK_TRUE@ nocproxy.$(OBJEXT) nogss.$(OBJEXT) \ +@HAVE_GTK_TRUE@ nullplug.$(OBJEXT) pageant.$(OBJEXT) \ +@HAVE_GTK_TRUE@ proxy.$(OBJEXT) settings.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshaes.$(OBJEXT) sshauxcrypt.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshdes.$(OBJEXT) sshdss.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshecc.$(OBJEXT) sshhmac.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshmd5.$(OBJEXT) sshprng.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshpubk.$(OBJEXT) sshrsa.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshsh256.$(OBJEXT) sshsh512.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshsha.$(OBJEXT) stripctrl.$(OBJEXT) \ +@HAVE_GTK_TRUE@ time.$(OBJEXT) timing.$(OBJEXT) \ +@HAVE_GTK_TRUE@ tree234.$(OBJEXT) unix/gtkask.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkmisc.$(OBJEXT) unix/ux_x11.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxagentc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxagentsock.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxcons.$(OBJEXT) unix/uxfdsock.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxmisc.$(OBJEXT) unix/uxnet.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxnoise.$(OBJEXT) unix/uxpeer.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxpgnt.$(OBJEXT) unix/uxpoll.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxproxy.$(OBJEXT) unix/uxsel.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxsignal.$(OBJEXT) unix/uxstore.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxutils.$(OBJEXT) utils.$(OBJEXT) \ +@HAVE_GTK_TRUE@ wcwidth.$(OBJEXT) x11fwd.$(OBJEXT) +pageant_OBJECTS = $(am_pageant_OBJECTS) +am__DEPENDENCIES_1 = +@HAVE_GTK_TRUE@pageant_DEPENDENCIES = libversion.a \ +@HAVE_GTK_TRUE@ $(am__DEPENDENCIES_1) +am_plink_OBJECTS = agentf.$(OBJEXT) aqsync.$(OBJEXT) \ + be_all_s.$(OBJEXT) be_misc.$(OBJEXT) callback.$(OBJEXT) \ + cmdline.$(OBJEXT) conf.$(OBJEXT) cproxy.$(OBJEXT) \ + ecc.$(OBJEXT) errsock.$(OBJEXT) ldisc.$(OBJEXT) \ + logging.$(OBJEXT) mainchan.$(OBJEXT) marshal.$(OBJEXT) \ + memory.$(OBJEXT) misc.$(OBJEXT) mpint.$(OBJEXT) \ + noterm.$(OBJEXT) nullplug.$(OBJEXT) pgssapi.$(OBJEXT) \ + pinger.$(OBJEXT) portfwd.$(OBJEXT) proxy.$(OBJEXT) \ + raw.$(OBJEXT) rlogin.$(OBJEXT) sessprep.$(OBJEXT) \ + settings.$(OBJEXT) ssh.$(OBJEXT) ssh1bpp.$(OBJEXT) \ + ssh1censor.$(OBJEXT) ssh1connection-client.$(OBJEXT) \ + ssh1connection.$(OBJEXT) ssh1login.$(OBJEXT) \ + ssh2bpp-bare.$(OBJEXT) ssh2bpp.$(OBJEXT) ssh2censor.$(OBJEXT) \ + ssh2connection-client.$(OBJEXT) ssh2connection.$(OBJEXT) \ + ssh2kex-client.$(OBJEXT) ssh2transhk.$(OBJEXT) \ + ssh2transport.$(OBJEXT) ssh2userauth.$(OBJEXT) \ + sshaes.$(OBJEXT) ssharcf.$(OBJEXT) sshauxcrypt.$(OBJEXT) \ + sshblowf.$(OBJEXT) sshccp.$(OBJEXT) sshcommon.$(OBJEXT) \ + sshcrc.$(OBJEXT) sshcrcda.$(OBJEXT) sshdes.$(OBJEXT) \ + sshdh.$(OBJEXT) sshdss.$(OBJEXT) sshecc.$(OBJEXT) \ + sshgssc.$(OBJEXT) sshhmac.$(OBJEXT) sshmac.$(OBJEXT) \ + sshmd5.$(OBJEXT) sshprng.$(OBJEXT) sshpubk.$(OBJEXT) \ + sshrand.$(OBJEXT) sshrsa.$(OBJEXT) sshsh256.$(OBJEXT) \ + sshsh512.$(OBJEXT) sshsha.$(OBJEXT) sshshare.$(OBJEXT) \ + sshverstring.$(OBJEXT) sshzlib.$(OBJEXT) stripctrl.$(OBJEXT) \ + telnet.$(OBJEXT) time.$(OBJEXT) timing.$(OBJEXT) \ + tree234.$(OBJEXT) unix/ux_x11.$(OBJEXT) \ + unix/uxagentc.$(OBJEXT) unix/uxcons.$(OBJEXT) \ + unix/uxfdsock.$(OBJEXT) unix/uxgss.$(OBJEXT) \ + unix/uxmisc.$(OBJEXT) unix/uxnet.$(OBJEXT) \ + unix/uxnogtk.$(OBJEXT) unix/uxnoise.$(OBJEXT) \ + unix/uxpeer.$(OBJEXT) unix/uxplink.$(OBJEXT) \ + unix/uxpoll.$(OBJEXT) unix/uxproxy.$(OBJEXT) \ + unix/uxsel.$(OBJEXT) unix/uxser.$(OBJEXT) \ + unix/uxshare.$(OBJEXT) unix/uxsignal.$(OBJEXT) \ + unix/uxstore.$(OBJEXT) unix/uxutils.$(OBJEXT) utils.$(OBJEXT) \ + wcwidth.$(OBJEXT) wildcard.$(OBJEXT) x11fwd.$(OBJEXT) +plink_OBJECTS = $(am_plink_OBJECTS) +plink_DEPENDENCIES = libversion.a +am_pscp_OBJECTS = agentf.$(OBJEXT) aqsync.$(OBJEXT) be_misc.$(OBJEXT) \ + be_ssh.$(OBJEXT) callback.$(OBJEXT) cmdline.$(OBJEXT) \ + conf.$(OBJEXT) cproxy.$(OBJEXT) ecc.$(OBJEXT) \ + errsock.$(OBJEXT) logging.$(OBJEXT) mainchan.$(OBJEXT) \ + marshal.$(OBJEXT) memory.$(OBJEXT) misc.$(OBJEXT) \ + mpint.$(OBJEXT) nullplug.$(OBJEXT) pgssapi.$(OBJEXT) \ + pinger.$(OBJEXT) portfwd.$(OBJEXT) proxy.$(OBJEXT) \ + pscp.$(OBJEXT) psftpcommon.$(OBJEXT) settings.$(OBJEXT) \ + sftp.$(OBJEXT) sftpcommon.$(OBJEXT) ssh.$(OBJEXT) \ + ssh1bpp.$(OBJEXT) ssh1censor.$(OBJEXT) \ + ssh1connection-client.$(OBJEXT) ssh1connection.$(OBJEXT) \ + ssh1login.$(OBJEXT) ssh2bpp-bare.$(OBJEXT) ssh2bpp.$(OBJEXT) \ + ssh2censor.$(OBJEXT) ssh2connection-client.$(OBJEXT) \ + ssh2connection.$(OBJEXT) ssh2kex-client.$(OBJEXT) \ + ssh2transhk.$(OBJEXT) ssh2transport.$(OBJEXT) \ + ssh2userauth.$(OBJEXT) sshaes.$(OBJEXT) ssharcf.$(OBJEXT) \ + sshauxcrypt.$(OBJEXT) sshblowf.$(OBJEXT) sshccp.$(OBJEXT) \ + sshcommon.$(OBJEXT) sshcrc.$(OBJEXT) sshcrcda.$(OBJEXT) \ + sshdes.$(OBJEXT) sshdh.$(OBJEXT) sshdss.$(OBJEXT) \ + sshecc.$(OBJEXT) sshgssc.$(OBJEXT) sshhmac.$(OBJEXT) \ + sshmac.$(OBJEXT) sshmd5.$(OBJEXT) sshprng.$(OBJEXT) \ + sshpubk.$(OBJEXT) sshrand.$(OBJEXT) sshrsa.$(OBJEXT) \ + sshsh256.$(OBJEXT) sshsh512.$(OBJEXT) sshsha.$(OBJEXT) \ + sshshare.$(OBJEXT) sshverstring.$(OBJEXT) sshzlib.$(OBJEXT) \ + stripctrl.$(OBJEXT) time.$(OBJEXT) timing.$(OBJEXT) \ + tree234.$(OBJEXT) unix/uxagentc.$(OBJEXT) \ + unix/uxcons.$(OBJEXT) unix/uxfdsock.$(OBJEXT) \ + unix/uxgss.$(OBJEXT) unix/uxmisc.$(OBJEXT) \ + unix/uxnet.$(OBJEXT) unix/uxnogtk.$(OBJEXT) \ + unix/uxnoise.$(OBJEXT) unix/uxpeer.$(OBJEXT) \ + unix/uxpoll.$(OBJEXT) unix/uxproxy.$(OBJEXT) \ + unix/uxsel.$(OBJEXT) unix/uxsftp.$(OBJEXT) \ + unix/uxshare.$(OBJEXT) unix/uxstore.$(OBJEXT) \ + unix/uxutils.$(OBJEXT) utils.$(OBJEXT) wcwidth.$(OBJEXT) \ + wildcard.$(OBJEXT) x11fwd.$(OBJEXT) +pscp_OBJECTS = $(am_pscp_OBJECTS) +pscp_DEPENDENCIES = libversion.a +am_psftp_OBJECTS = agentf.$(OBJEXT) aqsync.$(OBJEXT) be_misc.$(OBJEXT) \ + be_ssh.$(OBJEXT) callback.$(OBJEXT) cmdline.$(OBJEXT) \ + conf.$(OBJEXT) cproxy.$(OBJEXT) ecc.$(OBJEXT) \ + errsock.$(OBJEXT) logging.$(OBJEXT) mainchan.$(OBJEXT) \ + marshal.$(OBJEXT) memory.$(OBJEXT) misc.$(OBJEXT) \ + mpint.$(OBJEXT) nullplug.$(OBJEXT) pgssapi.$(OBJEXT) \ + pinger.$(OBJEXT) portfwd.$(OBJEXT) proxy.$(OBJEXT) \ + psftp.$(OBJEXT) psftpcommon.$(OBJEXT) settings.$(OBJEXT) \ + sftp.$(OBJEXT) sftpcommon.$(OBJEXT) ssh.$(OBJEXT) \ + ssh1bpp.$(OBJEXT) ssh1censor.$(OBJEXT) \ + ssh1connection-client.$(OBJEXT) ssh1connection.$(OBJEXT) \ + ssh1login.$(OBJEXT) ssh2bpp-bare.$(OBJEXT) ssh2bpp.$(OBJEXT) \ + ssh2censor.$(OBJEXT) ssh2connection-client.$(OBJEXT) \ + ssh2connection.$(OBJEXT) ssh2kex-client.$(OBJEXT) \ + ssh2transhk.$(OBJEXT) ssh2transport.$(OBJEXT) \ + ssh2userauth.$(OBJEXT) sshaes.$(OBJEXT) ssharcf.$(OBJEXT) \ + sshauxcrypt.$(OBJEXT) sshblowf.$(OBJEXT) sshccp.$(OBJEXT) \ + sshcommon.$(OBJEXT) sshcrc.$(OBJEXT) sshcrcda.$(OBJEXT) \ + sshdes.$(OBJEXT) sshdh.$(OBJEXT) sshdss.$(OBJEXT) \ + sshecc.$(OBJEXT) sshgssc.$(OBJEXT) sshhmac.$(OBJEXT) \ + sshmac.$(OBJEXT) sshmd5.$(OBJEXT) sshprng.$(OBJEXT) \ + sshpubk.$(OBJEXT) sshrand.$(OBJEXT) sshrsa.$(OBJEXT) \ + sshsh256.$(OBJEXT) sshsh512.$(OBJEXT) sshsha.$(OBJEXT) \ + sshshare.$(OBJEXT) sshverstring.$(OBJEXT) sshzlib.$(OBJEXT) \ + stripctrl.$(OBJEXT) time.$(OBJEXT) timing.$(OBJEXT) \ + tree234.$(OBJEXT) unix/uxagentc.$(OBJEXT) \ + unix/uxcons.$(OBJEXT) unix/uxfdsock.$(OBJEXT) \ + unix/uxgss.$(OBJEXT) unix/uxmisc.$(OBJEXT) \ + unix/uxnet.$(OBJEXT) unix/uxnogtk.$(OBJEXT) \ + unix/uxnoise.$(OBJEXT) unix/uxpeer.$(OBJEXT) \ + unix/uxpoll.$(OBJEXT) unix/uxproxy.$(OBJEXT) \ + unix/uxsel.$(OBJEXT) unix/uxsftp.$(OBJEXT) \ + unix/uxshare.$(OBJEXT) unix/uxstore.$(OBJEXT) \ + unix/uxutils.$(OBJEXT) utils.$(OBJEXT) wcwidth.$(OBJEXT) \ + wildcard.$(OBJEXT) x11fwd.$(OBJEXT) +psftp_OBJECTS = $(am_psftp_OBJECTS) +psftp_DEPENDENCIES = libversion.a +am__pterm_SOURCES_DIST = be_none.c callback.c charset/fromucs.c \ + charset/localenc.c charset/macenc.c charset/mimeenc.c \ + charset/sbcs.c charset/sbcsdat.c charset/slookup.c \ + charset/toucs.c charset/utf8.c charset/xenc.c cmdline.c conf.c \ + config.c dialog.c ldisc.c logging.c marshal.c memory.c \ + minibidi.c misc.c miscucs.c nocproxy.c nogss.c sercfg.c \ + sessprep.c settings.c stripctrl.c terminal.c time.c timing.c \ + tree234.c unix/gtkcfg.c unix/gtkcols.c unix/gtkcomm.c \ + unix/gtkdlg.c unix/gtkfont.c unix/gtkmain.c unix/gtkmisc.c \ + unix/gtkwin.c unix/uxcfg.c unix/uxmisc.c unix/uxprint.c \ + unix/uxpterm.c unix/uxpty.c unix/uxsel.c unix/uxsignal.c \ + unix/uxstore.c unix/uxucs.c unix/x11misc.c unix/xkeysym.c \ + unix/xpmptcfg.c unix/xpmpterm.c utils.c wcwidth.c +@HAVE_GTK_TRUE@am_pterm_OBJECTS = be_none.$(OBJEXT) callback.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/fromucs.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/localenc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/macenc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/mimeenc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/sbcs.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/sbcsdat.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/slookup.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/toucs.$(OBJEXT) charset/utf8.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/xenc.$(OBJEXT) cmdline.$(OBJEXT) \ +@HAVE_GTK_TRUE@ conf.$(OBJEXT) config.$(OBJEXT) \ +@HAVE_GTK_TRUE@ dialog.$(OBJEXT) ldisc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ logging.$(OBJEXT) marshal.$(OBJEXT) \ +@HAVE_GTK_TRUE@ memory.$(OBJEXT) minibidi.$(OBJEXT) \ +@HAVE_GTK_TRUE@ misc.$(OBJEXT) miscucs.$(OBJEXT) \ +@HAVE_GTK_TRUE@ nocproxy.$(OBJEXT) nogss.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sercfg.$(OBJEXT) sessprep.$(OBJEXT) \ +@HAVE_GTK_TRUE@ settings.$(OBJEXT) stripctrl.$(OBJEXT) \ +@HAVE_GTK_TRUE@ terminal.$(OBJEXT) time.$(OBJEXT) \ +@HAVE_GTK_TRUE@ timing.$(OBJEXT) tree234.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkcfg.$(OBJEXT) unix/gtkcols.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkcomm.$(OBJEXT) unix/gtkdlg.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkfont.$(OBJEXT) unix/gtkmain.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkmisc.$(OBJEXT) unix/gtkwin.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxcfg.$(OBJEXT) unix/uxmisc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxprint.$(OBJEXT) unix/uxpterm.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxpty.$(OBJEXT) unix/uxsel.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxsignal.$(OBJEXT) unix/uxstore.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxucs.$(OBJEXT) unix/x11misc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/xkeysym.$(OBJEXT) unix/xpmptcfg.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/xpmpterm.$(OBJEXT) utils.$(OBJEXT) \ +@HAVE_GTK_TRUE@ wcwidth.$(OBJEXT) +pterm_OBJECTS = $(am_pterm_OBJECTS) +@HAVE_GTK_TRUE@pterm_DEPENDENCIES = libversion.a $(am__DEPENDENCIES_1) +am__ptermapp_SOURCES_DIST = be_none.c callback.c charset/fromucs.c \ + charset/localenc.c charset/macenc.c charset/mimeenc.c \ + charset/sbcs.c charset/sbcsdat.c charset/slookup.c \ + charset/toucs.c charset/utf8.c charset/xenc.c conf.c config.c \ + dialog.c ldisc.c logging.c marshal.c memory.c minibidi.c \ + misc.c miscucs.c nocmdline.c nocproxy.c nogss.c sercfg.c \ + sessprep.c settings.c stripctrl.c terminal.c time.c timing.c \ + tree234.c unix/gtkapp.c unix/gtkcfg.c unix/gtkcols.c \ + unix/gtkcomm.c unix/gtkdlg.c unix/gtkfont.c unix/gtkmisc.c \ + unix/gtkwin.c unix/uxcfg.c unix/uxmisc.c unix/uxprint.c \ + unix/uxpterm.c unix/uxpty.c unix/uxsel.c unix/uxsignal.c \ + unix/uxstore.c unix/uxucs.c unix/x11misc.c unix/xkeysym.c \ + unix/xpmptcfg.c unix/xpmpterm.c utils.c wcwidth.c +@HAVE_GTK_TRUE@am_ptermapp_OBJECTS = be_none.$(OBJEXT) \ +@HAVE_GTK_TRUE@ callback.$(OBJEXT) charset/fromucs.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/localenc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/macenc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/mimeenc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/sbcs.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/sbcsdat.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/slookup.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/toucs.$(OBJEXT) charset/utf8.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/xenc.$(OBJEXT) conf.$(OBJEXT) \ +@HAVE_GTK_TRUE@ config.$(OBJEXT) dialog.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ldisc.$(OBJEXT) logging.$(OBJEXT) \ +@HAVE_GTK_TRUE@ marshal.$(OBJEXT) memory.$(OBJEXT) \ +@HAVE_GTK_TRUE@ minibidi.$(OBJEXT) misc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ miscucs.$(OBJEXT) nocmdline.$(OBJEXT) \ +@HAVE_GTK_TRUE@ nocproxy.$(OBJEXT) nogss.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sercfg.$(OBJEXT) sessprep.$(OBJEXT) \ +@HAVE_GTK_TRUE@ settings.$(OBJEXT) stripctrl.$(OBJEXT) \ +@HAVE_GTK_TRUE@ terminal.$(OBJEXT) time.$(OBJEXT) \ +@HAVE_GTK_TRUE@ timing.$(OBJEXT) tree234.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkapp.$(OBJEXT) unix/gtkcfg.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkcols.$(OBJEXT) unix/gtkcomm.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkdlg.$(OBJEXT) unix/gtkfont.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkmisc.$(OBJEXT) unix/gtkwin.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxcfg.$(OBJEXT) unix/uxmisc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxprint.$(OBJEXT) unix/uxpterm.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxpty.$(OBJEXT) unix/uxsel.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxsignal.$(OBJEXT) unix/uxstore.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxucs.$(OBJEXT) unix/x11misc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/xkeysym.$(OBJEXT) unix/xpmptcfg.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/xpmpterm.$(OBJEXT) utils.$(OBJEXT) \ +@HAVE_GTK_TRUE@ wcwidth.$(OBJEXT) +ptermapp_OBJECTS = $(am_ptermapp_OBJECTS) +@HAVE_GTK_TRUE@ptermapp_DEPENDENCIES = libversion.a \ +@HAVE_GTK_TRUE@ $(am__DEPENDENCIES_1) +am__putty_SOURCES_DIST = agentf.c aqsync.c be_all_s.c be_misc.c \ + callback.c charset/fromucs.c charset/localenc.c \ + charset/macenc.c charset/mimeenc.c charset/sbcs.c \ + charset/sbcsdat.c charset/slookup.c charset/toucs.c \ + charset/utf8.c charset/xenc.c cmdline.c conf.c config.c \ + cproxy.c dialog.c ecc.c errsock.c ldisc.c logging.c mainchan.c \ + marshal.c memory.c minibidi.c misc.c miscucs.c mpint.c \ + nullplug.c pgssapi.c pinger.c portfwd.c proxy.c raw.c rlogin.c \ + sercfg.c sessprep.c settings.c ssh.c ssh1bpp.c ssh1censor.c \ + ssh1connection-client.c ssh1connection.c ssh1login.c \ + ssh2bpp-bare.c ssh2bpp.c ssh2censor.c ssh2connection-client.c \ + ssh2connection.c ssh2kex-client.c ssh2transhk.c \ + ssh2transport.c ssh2userauth.c sshaes.c ssharcf.c \ + sshauxcrypt.c sshblowf.c sshccp.c sshcommon.c sshcrc.c \ + sshcrcda.c sshdes.c sshdh.c sshdss.c sshecc.c sshgssc.c \ + sshhmac.c sshmac.c sshmd5.c sshprng.c sshpubk.c sshrand.c \ + sshrsa.c sshsh256.c sshsh512.c sshsha.c sshshare.c \ + sshverstring.c sshzlib.c stripctrl.c telnet.c terminal.c \ + time.c timing.c tree234.c unix/gtkcfg.c unix/gtkcols.c \ + unix/gtkcomm.c unix/gtkdlg.c unix/gtkfont.c unix/gtkmain.c \ + unix/gtkmisc.c unix/gtkwin.c unix/ux_x11.c unix/uxagentc.c \ + unix/uxcfg.c unix/uxfdsock.c unix/uxgss.c unix/uxmisc.c \ + unix/uxnet.c unix/uxnoise.c unix/uxpeer.c unix/uxpoll.c \ + unix/uxprint.c unix/uxproxy.c unix/uxputty.c unix/uxsel.c \ + unix/uxser.c unix/uxshare.c unix/uxsignal.c unix/uxstore.c \ + unix/uxucs.c unix/uxutils.c unix/x11misc.c unix/xkeysym.c \ + unix/xpmpucfg.c unix/xpmputty.c utils.c wcwidth.c wildcard.c \ + x11fwd.c +@HAVE_GTK_TRUE@am_putty_OBJECTS = agentf.$(OBJEXT) aqsync.$(OBJEXT) \ +@HAVE_GTK_TRUE@ be_all_s.$(OBJEXT) be_misc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ callback.$(OBJEXT) charset/fromucs.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/localenc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/macenc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/mimeenc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/sbcs.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/sbcsdat.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/slookup.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/toucs.$(OBJEXT) charset/utf8.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/xenc.$(OBJEXT) cmdline.$(OBJEXT) \ +@HAVE_GTK_TRUE@ conf.$(OBJEXT) config.$(OBJEXT) \ +@HAVE_GTK_TRUE@ cproxy.$(OBJEXT) dialog.$(OBJEXT) ecc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ errsock.$(OBJEXT) ldisc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ logging.$(OBJEXT) mainchan.$(OBJEXT) \ +@HAVE_GTK_TRUE@ marshal.$(OBJEXT) memory.$(OBJEXT) \ +@HAVE_GTK_TRUE@ minibidi.$(OBJEXT) misc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ miscucs.$(OBJEXT) mpint.$(OBJEXT) \ +@HAVE_GTK_TRUE@ nullplug.$(OBJEXT) pgssapi.$(OBJEXT) \ +@HAVE_GTK_TRUE@ pinger.$(OBJEXT) portfwd.$(OBJEXT) \ +@HAVE_GTK_TRUE@ proxy.$(OBJEXT) raw.$(OBJEXT) rlogin.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sercfg.$(OBJEXT) sessprep.$(OBJEXT) \ +@HAVE_GTK_TRUE@ settings.$(OBJEXT) ssh.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh1bpp.$(OBJEXT) ssh1censor.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh1connection-client.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh1connection.$(OBJEXT) ssh1login.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh2bpp-bare.$(OBJEXT) ssh2bpp.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh2censor.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh2connection-client.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh2connection.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh2kex-client.$(OBJEXT) ssh2transhk.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh2transport.$(OBJEXT) ssh2userauth.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshaes.$(OBJEXT) ssharcf.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshauxcrypt.$(OBJEXT) sshblowf.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshccp.$(OBJEXT) sshcommon.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshcrc.$(OBJEXT) sshcrcda.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshdes.$(OBJEXT) sshdh.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshdss.$(OBJEXT) sshecc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshgssc.$(OBJEXT) sshhmac.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshmac.$(OBJEXT) sshmd5.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshprng.$(OBJEXT) sshpubk.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshrand.$(OBJEXT) sshrsa.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshsh256.$(OBJEXT) sshsh512.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshsha.$(OBJEXT) sshshare.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshverstring.$(OBJEXT) sshzlib.$(OBJEXT) \ +@HAVE_GTK_TRUE@ stripctrl.$(OBJEXT) telnet.$(OBJEXT) \ +@HAVE_GTK_TRUE@ terminal.$(OBJEXT) time.$(OBJEXT) \ +@HAVE_GTK_TRUE@ timing.$(OBJEXT) tree234.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkcfg.$(OBJEXT) unix/gtkcols.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkcomm.$(OBJEXT) unix/gtkdlg.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkfont.$(OBJEXT) unix/gtkmain.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkmisc.$(OBJEXT) unix/gtkwin.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/ux_x11.$(OBJEXT) unix/uxagentc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxcfg.$(OBJEXT) unix/uxfdsock.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxgss.$(OBJEXT) unix/uxmisc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxnet.$(OBJEXT) unix/uxnoise.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxpeer.$(OBJEXT) unix/uxpoll.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxprint.$(OBJEXT) unix/uxproxy.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxputty.$(OBJEXT) unix/uxsel.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxser.$(OBJEXT) unix/uxshare.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxsignal.$(OBJEXT) unix/uxstore.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxucs.$(OBJEXT) unix/uxutils.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/x11misc.$(OBJEXT) unix/xkeysym.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/xpmpucfg.$(OBJEXT) unix/xpmputty.$(OBJEXT) \ +@HAVE_GTK_TRUE@ utils.$(OBJEXT) wcwidth.$(OBJEXT) \ +@HAVE_GTK_TRUE@ wildcard.$(OBJEXT) x11fwd.$(OBJEXT) +putty_OBJECTS = $(am_putty_OBJECTS) +@HAVE_GTK_TRUE@putty_DEPENDENCIES = libversion.a $(am__DEPENDENCIES_1) +am__puttyapp_SOURCES_DIST = agentf.c aqsync.c be_all_s.c be_misc.c \ + callback.c charset/fromucs.c charset/localenc.c \ + charset/macenc.c charset/mimeenc.c charset/sbcs.c \ + charset/sbcsdat.c charset/slookup.c charset/toucs.c \ + charset/utf8.c charset/xenc.c conf.c config.c cproxy.c \ + dialog.c ecc.c errsock.c ldisc.c logging.c mainchan.c \ + marshal.c memory.c minibidi.c misc.c miscucs.c mpint.c \ + nocmdline.c nullplug.c pgssapi.c pinger.c portfwd.c proxy.c \ + raw.c rlogin.c sercfg.c sessprep.c settings.c ssh.c ssh1bpp.c \ + ssh1censor.c ssh1connection-client.c ssh1connection.c \ + ssh1login.c ssh2bpp-bare.c ssh2bpp.c ssh2censor.c \ + ssh2connection-client.c ssh2connection.c ssh2kex-client.c \ + ssh2transhk.c ssh2transport.c ssh2userauth.c sshaes.c \ + ssharcf.c sshauxcrypt.c sshblowf.c sshccp.c sshcommon.c \ + sshcrc.c sshcrcda.c sshdes.c sshdh.c sshdss.c sshecc.c \ + sshgssc.c sshhmac.c sshmac.c sshmd5.c sshprng.c sshpubk.c \ + sshrand.c sshrsa.c sshsh256.c sshsh512.c sshsha.c sshshare.c \ + sshverstring.c sshzlib.c stripctrl.c telnet.c terminal.c \ + time.c timing.c tree234.c unix/gtkapp.c unix/gtkcfg.c \ + unix/gtkcols.c unix/gtkcomm.c unix/gtkdlg.c unix/gtkfont.c \ + unix/gtkmisc.c unix/gtkwin.c unix/ux_x11.c unix/uxagentc.c \ + unix/uxcfg.c unix/uxfdsock.c unix/uxgss.c unix/uxmisc.c \ + unix/uxnet.c unix/uxnoise.c unix/uxpeer.c unix/uxpoll.c \ + unix/uxprint.c unix/uxproxy.c unix/uxputty.c unix/uxsel.c \ + unix/uxser.c unix/uxshare.c unix/uxsignal.c unix/uxstore.c \ + unix/uxucs.c unix/uxutils.c unix/x11misc.c unix/xkeysym.c \ + unix/xpmpucfg.c unix/xpmputty.c utils.c wcwidth.c wildcard.c \ + x11fwd.c +@HAVE_GTK_TRUE@am_puttyapp_OBJECTS = agentf.$(OBJEXT) aqsync.$(OBJEXT) \ +@HAVE_GTK_TRUE@ be_all_s.$(OBJEXT) be_misc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ callback.$(OBJEXT) charset/fromucs.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/localenc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/macenc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/mimeenc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/sbcs.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/sbcsdat.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/slookup.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/toucs.$(OBJEXT) charset/utf8.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/xenc.$(OBJEXT) conf.$(OBJEXT) \ +@HAVE_GTK_TRUE@ config.$(OBJEXT) cproxy.$(OBJEXT) \ +@HAVE_GTK_TRUE@ dialog.$(OBJEXT) ecc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ errsock.$(OBJEXT) ldisc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ logging.$(OBJEXT) mainchan.$(OBJEXT) \ +@HAVE_GTK_TRUE@ marshal.$(OBJEXT) memory.$(OBJEXT) \ +@HAVE_GTK_TRUE@ minibidi.$(OBJEXT) misc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ miscucs.$(OBJEXT) mpint.$(OBJEXT) \ +@HAVE_GTK_TRUE@ nocmdline.$(OBJEXT) nullplug.$(OBJEXT) \ +@HAVE_GTK_TRUE@ pgssapi.$(OBJEXT) pinger.$(OBJEXT) \ +@HAVE_GTK_TRUE@ portfwd.$(OBJEXT) proxy.$(OBJEXT) raw.$(OBJEXT) \ +@HAVE_GTK_TRUE@ rlogin.$(OBJEXT) sercfg.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sessprep.$(OBJEXT) settings.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh.$(OBJEXT) ssh1bpp.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh1censor.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh1connection-client.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh1connection.$(OBJEXT) ssh1login.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh2bpp-bare.$(OBJEXT) ssh2bpp.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh2censor.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh2connection-client.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh2connection.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh2kex-client.$(OBJEXT) ssh2transhk.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ssh2transport.$(OBJEXT) ssh2userauth.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshaes.$(OBJEXT) ssharcf.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshauxcrypt.$(OBJEXT) sshblowf.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshccp.$(OBJEXT) sshcommon.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshcrc.$(OBJEXT) sshcrcda.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshdes.$(OBJEXT) sshdh.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshdss.$(OBJEXT) sshecc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshgssc.$(OBJEXT) sshhmac.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshmac.$(OBJEXT) sshmd5.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshprng.$(OBJEXT) sshpubk.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshrand.$(OBJEXT) sshrsa.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshsh256.$(OBJEXT) sshsh512.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshsha.$(OBJEXT) sshshare.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sshverstring.$(OBJEXT) sshzlib.$(OBJEXT) \ +@HAVE_GTK_TRUE@ stripctrl.$(OBJEXT) telnet.$(OBJEXT) \ +@HAVE_GTK_TRUE@ terminal.$(OBJEXT) time.$(OBJEXT) \ +@HAVE_GTK_TRUE@ timing.$(OBJEXT) tree234.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkapp.$(OBJEXT) unix/gtkcfg.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkcols.$(OBJEXT) unix/gtkcomm.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkdlg.$(OBJEXT) unix/gtkfont.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkmisc.$(OBJEXT) unix/gtkwin.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/ux_x11.$(OBJEXT) unix/uxagentc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxcfg.$(OBJEXT) unix/uxfdsock.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxgss.$(OBJEXT) unix/uxmisc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxnet.$(OBJEXT) unix/uxnoise.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxpeer.$(OBJEXT) unix/uxpoll.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxprint.$(OBJEXT) unix/uxproxy.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxputty.$(OBJEXT) unix/uxsel.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxser.$(OBJEXT) unix/uxshare.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxsignal.$(OBJEXT) unix/uxstore.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxucs.$(OBJEXT) unix/uxutils.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/x11misc.$(OBJEXT) unix/xkeysym.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/xpmpucfg.$(OBJEXT) unix/xpmputty.$(OBJEXT) \ +@HAVE_GTK_TRUE@ utils.$(OBJEXT) wcwidth.$(OBJEXT) \ +@HAVE_GTK_TRUE@ wildcard.$(OBJEXT) x11fwd.$(OBJEXT) +puttyapp_OBJECTS = $(am_puttyapp_OBJECTS) +@HAVE_GTK_TRUE@puttyapp_DEPENDENCIES = libversion.a \ +@HAVE_GTK_TRUE@ $(am__DEPENDENCIES_1) +am_puttygen_OBJECTS = cmdgen.$(OBJEXT) conf.$(OBJEXT) ecc.$(OBJEXT) \ + import.$(OBJEXT) marshal.$(OBJEXT) memory.$(OBJEXT) \ + misc.$(OBJEXT) mpint.$(OBJEXT) notiming.$(OBJEXT) \ + sshaes.$(OBJEXT) sshauxcrypt.$(OBJEXT) sshbcrypt.$(OBJEXT) \ + sshblowf.$(OBJEXT) sshdes.$(OBJEXT) sshdss.$(OBJEXT) \ + sshdssg.$(OBJEXT) sshecc.$(OBJEXT) sshecdsag.$(OBJEXT) \ + sshhmac.$(OBJEXT) sshmd5.$(OBJEXT) sshprime.$(OBJEXT) \ + sshprng.$(OBJEXT) sshpubk.$(OBJEXT) sshrand.$(OBJEXT) \ + sshrsa.$(OBJEXT) sshrsag.$(OBJEXT) sshsh256.$(OBJEXT) \ + sshsh512.$(OBJEXT) sshsha.$(OBJEXT) stripctrl.$(OBJEXT) \ + time.$(OBJEXT) tree234.$(OBJEXT) unix/uxcons.$(OBJEXT) \ + unix/uxgen.$(OBJEXT) unix/uxmisc.$(OBJEXT) \ + unix/uxnogtk.$(OBJEXT) unix/uxnoise.$(OBJEXT) \ + unix/uxpoll.$(OBJEXT) unix/uxstore.$(OBJEXT) \ + unix/uxutils.$(OBJEXT) utils.$(OBJEXT) wcwidth.$(OBJEXT) +puttygen_OBJECTS = $(am_puttygen_OBJECTS) +puttygen_DEPENDENCIES = libversion.a +am__puttytel_SOURCES_DIST = be_misc.c be_nos_s.c callback.c \ + charset/fromucs.c charset/localenc.c charset/macenc.c \ + charset/mimeenc.c charset/sbcs.c charset/sbcsdat.c \ + charset/slookup.c charset/toucs.c charset/utf8.c \ + charset/xenc.c cmdline.c conf.c config.c dialog.c errsock.c \ + ldisc.c logging.c marshal.c memory.c minibidi.c misc.c \ + miscucs.c nocproxy.c nogss.c pinger.c proxy.c raw.c rlogin.c \ + sercfg.c sessprep.c settings.c stripctrl.c telnet.c terminal.c \ + time.c timing.c tree234.c unix/gtkcfg.c unix/gtkcols.c \ + unix/gtkcomm.c unix/gtkdlg.c unix/gtkfont.c unix/gtkmain.c \ + unix/gtkmisc.c unix/gtkwin.c unix/uxcfg.c unix/uxfdsock.c \ + unix/uxmisc.c unix/uxnet.c unix/uxpeer.c unix/uxpoll.c \ + unix/uxprint.c unix/uxproxy.c unix/uxputty.c unix/uxsel.c \ + unix/uxser.c unix/uxsignal.c unix/uxstore.c unix/uxucs.c \ + unix/uxutils.c unix/x11misc.c unix/xkeysym.c unix/xpmpucfg.c \ + unix/xpmputty.c utils.c wcwidth.c +@HAVE_GTK_TRUE@am_puttytel_OBJECTS = be_misc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ be_nos_s.$(OBJEXT) callback.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/fromucs.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/localenc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/macenc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/mimeenc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/sbcs.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/sbcsdat.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/slookup.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/toucs.$(OBJEXT) charset/utf8.$(OBJEXT) \ +@HAVE_GTK_TRUE@ charset/xenc.$(OBJEXT) cmdline.$(OBJEXT) \ +@HAVE_GTK_TRUE@ conf.$(OBJEXT) config.$(OBJEXT) \ +@HAVE_GTK_TRUE@ dialog.$(OBJEXT) errsock.$(OBJEXT) \ +@HAVE_GTK_TRUE@ ldisc.$(OBJEXT) logging.$(OBJEXT) \ +@HAVE_GTK_TRUE@ marshal.$(OBJEXT) memory.$(OBJEXT) \ +@HAVE_GTK_TRUE@ minibidi.$(OBJEXT) misc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ miscucs.$(OBJEXT) nocproxy.$(OBJEXT) \ +@HAVE_GTK_TRUE@ nogss.$(OBJEXT) pinger.$(OBJEXT) \ +@HAVE_GTK_TRUE@ proxy.$(OBJEXT) raw.$(OBJEXT) rlogin.$(OBJEXT) \ +@HAVE_GTK_TRUE@ sercfg.$(OBJEXT) sessprep.$(OBJEXT) \ +@HAVE_GTK_TRUE@ settings.$(OBJEXT) stripctrl.$(OBJEXT) \ +@HAVE_GTK_TRUE@ telnet.$(OBJEXT) terminal.$(OBJEXT) \ +@HAVE_GTK_TRUE@ time.$(OBJEXT) timing.$(OBJEXT) \ +@HAVE_GTK_TRUE@ tree234.$(OBJEXT) unix/gtkcfg.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkcols.$(OBJEXT) unix/gtkcomm.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkdlg.$(OBJEXT) unix/gtkfont.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkmain.$(OBJEXT) unix/gtkmisc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/gtkwin.$(OBJEXT) unix/uxcfg.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxfdsock.$(OBJEXT) unix/uxmisc.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxnet.$(OBJEXT) unix/uxpeer.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxpoll.$(OBJEXT) unix/uxprint.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxproxy.$(OBJEXT) unix/uxputty.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxsel.$(OBJEXT) unix/uxser.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxsignal.$(OBJEXT) unix/uxstore.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/uxucs.$(OBJEXT) unix/uxutils.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/x11misc.$(OBJEXT) unix/xkeysym.$(OBJEXT) \ +@HAVE_GTK_TRUE@ unix/xpmpucfg.$(OBJEXT) unix/xpmputty.$(OBJEXT) \ +@HAVE_GTK_TRUE@ utils.$(OBJEXT) wcwidth.$(OBJEXT) +puttytel_OBJECTS = $(am_puttytel_OBJECTS) +@HAVE_GTK_TRUE@puttytel_DEPENDENCIES = libversion.a \ +@HAVE_GTK_TRUE@ $(am__DEPENDENCIES_1) +am_testcrypt_OBJECTS = ecc.$(OBJEXT) marshal.$(OBJEXT) \ + memory.$(OBJEXT) mpint.$(OBJEXT) sshaes.$(OBJEXT) \ + ssharcf.$(OBJEXT) sshauxcrypt.$(OBJEXT) sshblowf.$(OBJEXT) \ + sshccp.$(OBJEXT) sshcrc.$(OBJEXT) sshcrcda.$(OBJEXT) \ + sshdes.$(OBJEXT) sshdh.$(OBJEXT) sshdss.$(OBJEXT) \ + sshecc.$(OBJEXT) sshhmac.$(OBJEXT) sshmd5.$(OBJEXT) \ + sshprime.$(OBJEXT) sshprng.$(OBJEXT) sshrsa.$(OBJEXT) \ + sshsh256.$(OBJEXT) sshsh512.$(OBJEXT) sshsha.$(OBJEXT) \ + testcrypt.$(OBJEXT) tree234.$(OBJEXT) unix/uxutils.$(OBJEXT) \ + utils.$(OBJEXT) +testcrypt_OBJECTS = $(am_testcrypt_OBJECTS) +testcrypt_LDADD = $(LDADD) +am_testsc_OBJECTS = ecc.$(OBJEXT) marshal.$(OBJEXT) memory.$(OBJEXT) \ + mpint.$(OBJEXT) sshaes.$(OBJEXT) ssharcf.$(OBJEXT) \ + sshauxcrypt.$(OBJEXT) sshblowf.$(OBJEXT) sshccp.$(OBJEXT) \ + sshcrc.$(OBJEXT) sshcrcda.$(OBJEXT) sshdes.$(OBJEXT) \ + sshdh.$(OBJEXT) sshdss.$(OBJEXT) sshecc.$(OBJEXT) \ + sshhmac.$(OBJEXT) sshmac.$(OBJEXT) sshmd5.$(OBJEXT) \ + sshrsa.$(OBJEXT) sshsh256.$(OBJEXT) sshsh512.$(OBJEXT) \ + sshsha.$(OBJEXT) testsc.$(OBJEXT) tree234.$(OBJEXT) \ + unix/uxutils.$(OBJEXT) utils.$(OBJEXT) wildcard.$(OBJEXT) +testsc_OBJECTS = $(am_testsc_OBJECTS) +testsc_LDADD = $(LDADD) +am_testzlib_OBJECTS = marshal.$(OBJEXT) memory.$(OBJEXT) \ + sshzlib.$(OBJEXT) testzlib.$(OBJEXT) utils.$(OBJEXT) +testzlib_OBJECTS = $(am_testzlib_OBJECTS) +testzlib_LDADD = $(LDADD) +am_uppity_OBJECTS = be_misc.$(OBJEXT) be_none.$(OBJEXT) \ + callback.$(OBJEXT) conf.$(OBJEXT) cproxy.$(OBJEXT) \ + ecc.$(OBJEXT) errsock.$(OBJEXT) logging.$(OBJEXT) \ + marshal.$(OBJEXT) memory.$(OBJEXT) misc.$(OBJEXT) \ + mpint.$(OBJEXT) nullplug.$(OBJEXT) pgssapi.$(OBJEXT) \ + portfwd.$(OBJEXT) proxy.$(OBJEXT) scpserver.$(OBJEXT) \ + sesschan.$(OBJEXT) settings.$(OBJEXT) sftpcommon.$(OBJEXT) \ + sftpserver.$(OBJEXT) ssh1bpp.$(OBJEXT) ssh1censor.$(OBJEXT) \ + ssh1connection-server.$(OBJEXT) ssh1connection.$(OBJEXT) \ + ssh1login-server.$(OBJEXT) ssh2bpp.$(OBJEXT) \ + ssh2censor.$(OBJEXT) ssh2connection-server.$(OBJEXT) \ + ssh2connection.$(OBJEXT) ssh2kex-server.$(OBJEXT) \ + ssh2transhk.$(OBJEXT) ssh2transport.$(OBJEXT) \ + ssh2userauth-server.$(OBJEXT) sshaes.$(OBJEXT) \ + ssharcf.$(OBJEXT) sshauxcrypt.$(OBJEXT) sshblowf.$(OBJEXT) \ + sshccp.$(OBJEXT) sshcommon.$(OBJEXT) sshcrc.$(OBJEXT) \ + sshcrcda.$(OBJEXT) sshdes.$(OBJEXT) sshdh.$(OBJEXT) \ + sshdss.$(OBJEXT) sshecc.$(OBJEXT) sshgssc.$(OBJEXT) \ + sshhmac.$(OBJEXT) sshmac.$(OBJEXT) sshmd5.$(OBJEXT) \ + sshprime.$(OBJEXT) sshprng.$(OBJEXT) sshpubk.$(OBJEXT) \ + sshrand.$(OBJEXT) sshrsa.$(OBJEXT) sshrsag.$(OBJEXT) \ + sshserver.$(OBJEXT) sshsh256.$(OBJEXT) sshsh512.$(OBJEXT) \ + sshsha.$(OBJEXT) sshverstring.$(OBJEXT) sshzlib.$(OBJEXT) \ + stripctrl.$(OBJEXT) time.$(OBJEXT) timing.$(OBJEXT) \ + tree234.$(OBJEXT) unix/procnet.$(OBJEXT) unix/ux_x11.$(OBJEXT) \ + unix/uxagentsock.$(OBJEXT) unix/uxfdsock.$(OBJEXT) \ + unix/uxgss.$(OBJEXT) unix/uxmisc.$(OBJEXT) \ + unix/uxnet.$(OBJEXT) unix/uxnogtk.$(OBJEXT) \ + unix/uxnoise.$(OBJEXT) unix/uxpeer.$(OBJEXT) \ + unix/uxpoll.$(OBJEXT) unix/uxproxy.$(OBJEXT) \ + unix/uxpty.$(OBJEXT) unix/uxsel.$(OBJEXT) \ + unix/uxserver.$(OBJEXT) unix/uxsftpserver.$(OBJEXT) \ + unix/uxsignal.$(OBJEXT) unix/uxstore.$(OBJEXT) \ + unix/uxutils.$(OBJEXT) utils.$(OBJEXT) wcwidth.$(OBJEXT) \ + wildcard.$(OBJEXT) x11fwd.$(OBJEXT) +uppity_OBJECTS = $(am_uppity_OBJECTS) +uppity_DEPENDENCIES = libversion.a +SCRIPTS = $(noinst_SCRIPTS) +AM_V_P = $(am__v_P_@AM_V@) +am__v_P_ = $(am__v_P_@AM_DEFAULT_V@) +am__v_P_0 = false +am__v_P_1 = : +AM_V_GEN = $(am__v_GEN_@AM_V@) +am__v_GEN_ = $(am__v_GEN_@AM_DEFAULT_V@) +am__v_GEN_0 = @echo " GEN " $@; +am__v_GEN_1 = +AM_V_at = $(am__v_at_@AM_V@) +am__v_at_ = $(am__v_at_@AM_DEFAULT_V@) +am__v_at_0 = @ +am__v_at_1 = +DEFAULT_INCLUDES = -I.@am__isrc@ +depcomp = $(SHELL) $(top_srcdir)/depcomp +am__depfiles_maybe = depfiles +am__mv = mv -f +AM_V_lt = $(am__v_lt_@AM_V@) +am__v_lt_ = $(am__v_lt_@AM_DEFAULT_V@) +am__v_lt_0 = --silent +am__v_lt_1 = +COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \ + $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) +AM_V_CC = $(am__v_CC_@AM_V@) +am__v_CC_ = $(am__v_CC_@AM_DEFAULT_V@) +am__v_CC_0 = @echo " CC " $@; +am__v_CC_1 = +CCLD = $(CC) +LINK = $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@ +AM_V_CCLD = $(am__v_CCLD_@AM_V@) +am__v_CCLD_ = $(am__v_CCLD_@AM_DEFAULT_V@) +am__v_CCLD_0 = @echo " CCLD " $@; +am__v_CCLD_1 = +SOURCES = $(libversion_a_SOURCES) $(cgtest_SOURCES) \ + $(fuzzterm_SOURCES) $(osxlaunch_SOURCES) $(pageant_SOURCES) \ + $(plink_SOURCES) $(pscp_SOURCES) $(psftp_SOURCES) \ + $(pterm_SOURCES) $(ptermapp_SOURCES) $(putty_SOURCES) \ + $(puttyapp_SOURCES) $(puttygen_SOURCES) $(puttytel_SOURCES) \ + $(testcrypt_SOURCES) $(testsc_SOURCES) $(testzlib_SOURCES) \ + $(uppity_SOURCES) +DIST_SOURCES = $(libversion_a_SOURCES) $(cgtest_SOURCES) \ + $(fuzzterm_SOURCES) $(osxlaunch_SOURCES) \ + $(am__pageant_SOURCES_DIST) $(plink_SOURCES) $(pscp_SOURCES) \ + $(psftp_SOURCES) $(am__pterm_SOURCES_DIST) \ + $(am__ptermapp_SOURCES_DIST) $(am__putty_SOURCES_DIST) \ + $(am__puttyapp_SOURCES_DIST) $(puttygen_SOURCES) \ + $(am__puttytel_SOURCES_DIST) $(testcrypt_SOURCES) \ + $(testsc_SOURCES) $(testzlib_SOURCES) $(uppity_SOURCES) +am__can_run_installinfo = \ + case $$AM_UPDATE_INFO_DIR in \ + n|no|NO) false;; \ + *) (install-info --version) >/dev/null 2>&1;; \ + esac +am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`; +am__vpath_adj = case $$p in \ + $(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \ + *) f=$$p;; \ + esac; +am__strip_dir = f=`echo $$p | sed -e 's|^.*/||'`; +am__install_max = 40 +am__nobase_strip_setup = \ + srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*|]/\\\\&/g'` +am__nobase_strip = \ + for p in $$list; do echo "$$p"; done | sed -e "s|$$srcdirstrip/||" +am__nobase_list = $(am__nobase_strip_setup); \ + for p in $$list; do echo "$$p $$p"; done | \ + sed "s| $$srcdirstrip/| |;"' / .*\//!s/ .*/ ./; s,\( .*\)/[^/]*$$,\1,' | \ + $(AWK) 'BEGIN { files["."] = "" } { files[$$2] = files[$$2] " " $$1; \ + if (++n[$$2] == $(am__install_max)) \ + { print $$2, files[$$2]; n[$$2] = 0; files[$$2] = "" } } \ + END { for (dir in files) print dir, files[dir] }' +am__base_list = \ + sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \ + sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g' +am__uninstall_files_from_dir = { \ + test -z "$$files" \ + || { test ! -d "$$dir" && test ! -f "$$dir" && test ! -r "$$dir"; } \ + || { echo " ( cd '$$dir' && rm -f" $$files ")"; \ + $(am__cd) "$$dir" && rm -f $$files; }; \ + } +man1dir = $(mandir)/man1 +NROFF = nroff +MANS = $(man1_MANS) +am__tagged_files = $(HEADERS) $(SOURCES) $(TAGS_FILES) \ + $(LISP)uxconfig.in +# Read a list of newline-separated strings from the standard input, +# and print each of them once, without duplicates. Input order is +# *not* preserved. +am__uniquify_input = $(AWK) '\ + BEGIN { nonempty = 0; } \ + { items[$$0] = 1; nonempty = 1; } \ + END { if (nonempty) { for (i in items) print i; }; } \ +' +# Make sure the list of sources is unique. This is necessary because, +# e.g., the same source file might be shared among _SOURCES variables +# for different programs/libraries. +am__define_uniq_tagged_files = \ + list='$(am__tagged_files)'; \ + unique=`for i in $$list; do \ + if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ + done | $(am__uniquify_input)` +ETAGS = etags +CTAGS = ctags +CSCOPE = cscope +AM_RECURSIVE_TARGETS = cscope +am__DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/uxconfig.in README \ + ar-lib compile depcomp install-sh missing +DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) +distdir = $(PACKAGE)-$(VERSION) +top_distdir = $(distdir) +am__remove_distdir = \ + if test -d "$(distdir)"; then \ + find "$(distdir)" -type d ! -perm -200 -exec chmod u+w {} ';' \ + && rm -rf "$(distdir)" \ + || { sleep 5 && rm -rf "$(distdir)"; }; \ + else :; fi +am__post_remove_distdir = $(am__remove_distdir) +DIST_ARCHIVES = $(distdir).tar.gz +GZIP_ENV = --best +DIST_TARGETS = dist-gzip +distuninstallcheck_listfiles = find . -type f -print +am__distuninstallcheck_listfiles = $(distuninstallcheck_listfiles) \ + | sed 's|^\./|$(prefix)/|' | grep -v '$(infodir)/dir$$' +distcleancheck_listfiles = find . -type f -print +ACLOCAL = @ACLOCAL@ +AMTAR = @AMTAR@ +AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@ +AR = @AR@ +AUTOCONF = @AUTOCONF@ +AUTOHEADER = @AUTOHEADER@ +AUTOMAKE = @AUTOMAKE@ +AWK = @AWK@ +CC = @CC@ +CCDEPMODE = @CCDEPMODE@ +CFLAGS = @CFLAGS@ +CPP = @CPP@ +CPPFLAGS = @CPPFLAGS@ +CYGPATH_W = @CYGPATH_W@ +DEFS = @DEFS@ +DEPDIR = @DEPDIR@ +ECHO_C = @ECHO_C@ +ECHO_N = @ECHO_N@ +ECHO_T = @ECHO_T@ +EGREP = @EGREP@ +EXEEXT = @EXEEXT@ +GREP = @GREP@ +GTK1_CONFIG = @GTK1_CONFIG@ +GTK_CFLAGS = @GTK_CFLAGS@ +GTK_LIBS = @GTK_LIBS@ +INSTALL = @INSTALL@ +INSTALL_DATA = @INSTALL_DATA@ +INSTALL_PROGRAM = @INSTALL_PROGRAM@ +INSTALL_SCRIPT = @INSTALL_SCRIPT@ +INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@ +LDFLAGS = @LDFLAGS@ +LIBOBJS = @LIBOBJS@ +LIBS = @LIBS@ +LTLIBOBJS = @LTLIBOBJS@ +MAKEINFO = @MAKEINFO@ +MKDIR_P = @MKDIR_P@ +OBJEXT = @OBJEXT@ +PACKAGE = @PACKAGE@ +PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@ +PACKAGE_NAME = @PACKAGE_NAME@ +PACKAGE_STRING = @PACKAGE_STRING@ +PACKAGE_TARNAME = @PACKAGE_TARNAME@ +PACKAGE_URL = @PACKAGE_URL@ +PACKAGE_VERSION = @PACKAGE_VERSION@ +PATH_SEPARATOR = @PATH_SEPARATOR@ +PKG_CONFIG = @PKG_CONFIG@ +PKG_CONFIG_LIBDIR = @PKG_CONFIG_LIBDIR@ +PKG_CONFIG_PATH = @PKG_CONFIG_PATH@ +RANLIB = @RANLIB@ +SETID_CMD = @SETID_CMD@ +SETID_MODE = @SETID_MODE@ +SET_MAKE = @SET_MAKE@ +SHELL = @SHELL@ +STRIP = @STRIP@ +VERSION = @VERSION@ +WARNINGOPTS = @WARNINGOPTS@ +abs_builddir = @abs_builddir@ +abs_srcdir = @abs_srcdir@ +abs_top_builddir = @abs_top_builddir@ +abs_top_srcdir = @abs_top_srcdir@ +ac_ct_AR = @ac_ct_AR@ +ac_ct_CC = @ac_ct_CC@ +am__include = @am__include@ +am__leading_dot = @am__leading_dot@ +am__quote = @am__quote@ +am__tar = @am__tar@ +am__untar = @am__untar@ +bindir = @bindir@ +build_alias = @build_alias@ +builddir = @builddir@ +datadir = @datadir@ +datarootdir = @datarootdir@ +docdir = @docdir@ +dvidir = @dvidir@ +exec_prefix = @exec_prefix@ +host_alias = @host_alias@ +htmldir = @htmldir@ +includedir = @includedir@ +infodir = @infodir@ +install_sh = @install_sh@ +libdir = @libdir@ +libexecdir = @libexecdir@ +localedir = @localedir@ +localstatedir = @localstatedir@ +mandir = @mandir@ +mkdir_p = @mkdir_p@ +oldincludedir = @oldincludedir@ +pdfdir = @pdfdir@ +prefix = @prefix@ +program_transform_name = @program_transform_name@ +psdir = @psdir@ +runstatedir = @runstatedir@ +sbindir = @sbindir@ +sharedstatedir = @sharedstatedir@ +srcdir = @srcdir@ +sysconfdir = @sysconfdir@ +target_alias = @target_alias@ +top_build_prefix = @top_build_prefix@ +top_builddir = @top_builddir@ +top_srcdir = @top_srcdir@ +AUTOMAKE_OPTIONS = subdir-objects +allsources = agentf.c aqsync.c be_all_s.c be_misc.c be_none.c be_nos_s.c \ + be_ssh.c callback.c cgtest.c charset/charset.h \ + charset/enum.c charset/fromucs.c charset/internal.h \ + charset/localenc.c charset/macenc.c charset/mimeenc.c \ + charset/sbcs.c charset/sbcsdat.c charset/slookup.c \ + charset/toucs.c charset/utf8.c charset/xenc.c cmdgen.c \ + cmdline.c conf.c config.c cproxy.c defs.h dialog.c dialog.h \ + ecc.c ecc.h errsock.c fuzzterm.c import.c ldisc.c ldisc.h \ + licence.h logging.c mainchan.c marshal.c marshal.h memory.c \ + minibidi.c misc.c misc.h miscucs.c mpint.c mpint.h mpint_i.h \ + network.h nocmdline.c nocproxy.c nogss.c noshare.c noterm.c \ + notiming.c nullplug.c pageant.c pageant.h pgssapi.c \ + pgssapi.h pinger.c portfwd.c proxy.c proxy.h pscp.c psftp.c \ + psftp.h psftpcommon.c putty.h puttymem.h puttyps.h raw.c \ + rlogin.c scpserver.c sercfg.c sesschan.c sessprep.c \ + settings.c sftp.c sftp.h sftpcommon.c sftpserver.c ssh.c \ + ssh.h ssh1bpp.c ssh1censor.c ssh1connection-client.c \ + ssh1connection-server.c ssh1connection.c ssh1connection.h \ + ssh1login-server.c ssh1login.c ssh2bpp-bare.c ssh2bpp.c \ + ssh2censor.c ssh2connection-client.c ssh2connection-server.c \ + ssh2connection.c ssh2connection.h ssh2kex-client.c \ + ssh2kex-server.c ssh2transhk.c ssh2transport.c \ + ssh2transport.h ssh2userauth-server.c ssh2userauth.c \ + sshaes.c ssharcf.c sshauxcrypt.c sshbcrypt.c sshblowf.c \ + sshblowf.h sshbpp.h sshccp.c sshchan.h sshcommon.c sshcr.h \ + sshcrc.c sshcrcda.c sshdes.c sshdh.c sshdss.c sshdssg.c \ + sshecc.c sshecdsag.c sshgss.h sshgssc.c sshgssc.h sshhmac.c \ + sshmac.c sshmd5.c sshppl.h sshprime.c sshprng.c sshpubk.c \ + sshrand.c sshrsa.c sshrsag.c sshserver.c sshserver.h \ + sshsh256.c sshsh512.c sshsha.c sshshare.c sshsignals.h \ + sshttymodes.h sshverstring.c sshzlib.c storage.h stripctrl.c \ + telnet.c terminal.c terminal.h testcrypt.c testcrypt.h \ + testsc.c testzlib.c time.c timing.c tree234.c tree234.h \ + unix/gtkapp.c unix/gtkask.c unix/gtkcfg.c unix/gtkcols.c \ + unix/gtkcols.h unix/gtkcomm.c unix/gtkcompat.h unix/gtkdlg.c \ + unix/gtkfont.c unix/gtkfont.h unix/gtkmain.c unix/gtkmisc.c \ + unix/gtkmisc.h unix/gtkwin.c unix/osxlaunch.c unix/procnet.c \ + unix/unix.h unix/ux_x11.c unix/uxagentc.c unix/uxagentsock.c \ + unix/uxcfg.c unix/uxcons.c unix/uxfdsock.c unix/uxgen.c \ + unix/uxgss.c unix/uxmisc.c unix/uxnet.c unix/uxnogtk.c \ + unix/uxnoise.c unix/uxpeer.c unix/uxpgnt.c unix/uxplink.c \ + unix/uxpoll.c unix/uxprint.c unix/uxproxy.c unix/uxpterm.c \ + unix/uxpty.c unix/uxputty.c unix/uxsel.c unix/uxser.c \ + unix/uxserver.c unix/uxsftp.c unix/uxsftpserver.c \ + unix/uxshare.c unix/uxsignal.c unix/uxstore.c unix/uxucs.c \ + unix/uxutils.c unix/x11misc.c unix/x11misc.h unix/xkeysym.c \ + unix/xpmptcfg.c unix/xpmpterm.c unix/xpmpucfg.c \ + unix/xpmputty.c utils.c version.c version.h wcwidth.c \ + wildcard.c windows/pageant.rc windows/plink.rc \ + windows/pscp.rc windows/psftp.rc windows/putty.rc \ + windows/puttygen.rc windows/puttytel.rc windows/rcstuff.h \ + windows/sizetip.c windows/version.rc2 windows/win_res.h \ + windows/win_res.rc2 windows/wincapi.c windows/wincapi.h \ + windows/wincfg.c windows/wincons.c windows/winctrls.c \ + windows/windefs.c windows/windlg.c windows/window.c \ + windows/wingss.c windows/winhandl.c windows/winhelp.c \ + windows/winhelp.h windows/winhelp.rc2 windows/winhsock.c \ + windows/winjump.c windows/winmisc.c windows/winmiscs.c \ + windows/winnet.c windows/winnohlp.c windows/winnoise.c \ + windows/winnojmp.c windows/winnpc.c windows/winnps.c \ + windows/winpgen.c windows/winpgnt.c windows/winpgntc.c \ + windows/winplink.c windows/winprint.c windows/winproxy.c \ + windows/winsecur.c windows/winsecur.h windows/winser.c \ + windows/winsftp.c windows/winshare.c windows/winstore.c \ + windows/winstuff.h windows/wintime.c windows/winucs.c \ + windows/winutils.c windows/winx11.c x11fwd.c + +AM_CPPFLAGS = -I$(srcdir)/./ -I$(srcdir)/charset/ -I$(srcdir)/windows/ \ + -I$(srcdir)/unix/ + +@HAVE_GTK_FALSE@AM_CFLAGS = $(COMPAT) $(XFLAGS) $(WARNINGOPTS) +@HAVE_GTK_TRUE@AM_CFLAGS = $(GTK_CFLAGS) $(COMPAT) $(XFLAGS) $(WARNINGOPTS) +libversion_a_SOURCES = version.c +libversion_a_CFLAGS = $(COMPAT) $(XFLAGS) $(WARNINGOPTS) \ + $(am__append_1) +noinst_LIBRARIES = libversion.a +cgtest_SOURCES = cgtest.c conf.c ecc.c import.c marshal.c memory.c misc.c \ + mpint.c notiming.c sshaes.c sshauxcrypt.c sshbcrypt.c \ + sshblowf.c sshdes.c sshdss.c sshdssg.c sshecc.c sshecdsag.c \ + sshhmac.c sshmd5.c sshprime.c sshprng.c sshpubk.c sshrand.c \ + sshrsa.c sshrsag.c sshsh256.c sshsh512.c sshsha.c \ + stripctrl.c time.c tree234.c unix/uxcons.c unix/uxgen.c \ + unix/uxmisc.c unix/uxnogtk.c unix/uxnoise.c unix/uxpoll.c \ + unix/uxstore.c unix/uxutils.c utils.c wcwidth.c + +cgtest_LDADD = libversion.a +fuzzterm_SOURCES = be_none.c callback.c charset/fromucs.c charset/localenc.c \ + charset/macenc.c charset/mimeenc.c charset/sbcs.c \ + charset/sbcsdat.c charset/slookup.c charset/toucs.c \ + charset/utf8.c charset/xenc.c conf.c config.c dialog.c \ + fuzzterm.c logging.c marshal.c memory.c minibidi.c misc.c \ + miscucs.c sercfg.c settings.c stripctrl.c terminal.c time.c \ + timing.c tree234.c unix/uxcfg.c unix/uxmisc.c unix/uxnogtk.c \ + unix/uxprint.c unix/uxstore.c unix/uxucs.c utils.c wcwidth.c + +fuzzterm_LDADD = libversion.a +osxlaunch_SOURCES = unix/osxlaunch.c +@HAVE_GTK_TRUE@pageant_SOURCES = aqsync.c be_misc.c be_none.c callback.c conf.c ecc.c \ +@HAVE_GTK_TRUE@ errsock.c logging.c marshal.c memory.c misc.c mpint.c \ +@HAVE_GTK_TRUE@ nocproxy.c nogss.c nullplug.c pageant.c proxy.c settings.c \ +@HAVE_GTK_TRUE@ sshaes.c sshauxcrypt.c sshdes.c sshdss.c sshecc.c sshhmac.c \ +@HAVE_GTK_TRUE@ sshmd5.c sshprng.c sshpubk.c sshrsa.c sshsh256.c sshsh512.c \ +@HAVE_GTK_TRUE@ sshsha.c stripctrl.c time.c timing.c tree234.c unix/gtkask.c \ +@HAVE_GTK_TRUE@ unix/gtkmisc.c unix/ux_x11.c unix/uxagentc.c \ +@HAVE_GTK_TRUE@ unix/uxagentsock.c unix/uxcons.c unix/uxfdsock.c \ +@HAVE_GTK_TRUE@ unix/uxmisc.c unix/uxnet.c unix/uxnoise.c unix/uxpeer.c \ +@HAVE_GTK_TRUE@ unix/uxpgnt.c unix/uxpoll.c unix/uxproxy.c unix/uxsel.c \ +@HAVE_GTK_TRUE@ unix/uxsignal.c unix/uxstore.c unix/uxutils.c utils.c \ +@HAVE_GTK_TRUE@ wcwidth.c x11fwd.c + +@HAVE_GTK_TRUE@pageant_LDADD = libversion.a $(GTK_LIBS) +plink_SOURCES = agentf.c aqsync.c be_all_s.c be_misc.c callback.c cmdline.c \ + conf.c cproxy.c ecc.c errsock.c ldisc.c logging.c mainchan.c \ + marshal.c memory.c misc.c mpint.c noterm.c nullplug.c \ + pgssapi.c pinger.c portfwd.c proxy.c raw.c rlogin.c \ + sessprep.c settings.c ssh.c ssh1bpp.c ssh1censor.c \ + ssh1connection-client.c ssh1connection.c ssh1login.c \ + ssh2bpp-bare.c ssh2bpp.c ssh2censor.c \ + ssh2connection-client.c ssh2connection.c ssh2kex-client.c \ + ssh2transhk.c ssh2transport.c ssh2userauth.c sshaes.c \ + ssharcf.c sshauxcrypt.c sshblowf.c sshccp.c sshcommon.c \ + sshcrc.c sshcrcda.c sshdes.c sshdh.c sshdss.c sshecc.c \ + sshgssc.c sshhmac.c sshmac.c sshmd5.c sshprng.c sshpubk.c \ + sshrand.c sshrsa.c sshsh256.c sshsh512.c sshsha.c sshshare.c \ + sshverstring.c sshzlib.c stripctrl.c telnet.c time.c \ + timing.c tree234.c unix/ux_x11.c unix/uxagentc.c \ + unix/uxcons.c unix/uxfdsock.c unix/uxgss.c unix/uxmisc.c \ + unix/uxnet.c unix/uxnogtk.c unix/uxnoise.c unix/uxpeer.c \ + unix/uxplink.c unix/uxpoll.c unix/uxproxy.c unix/uxsel.c \ + unix/uxser.c unix/uxshare.c unix/uxsignal.c unix/uxstore.c \ + unix/uxutils.c utils.c wcwidth.c wildcard.c x11fwd.c + +plink_LDADD = libversion.a +pscp_SOURCES = agentf.c aqsync.c be_misc.c be_ssh.c callback.c cmdline.c \ + conf.c cproxy.c ecc.c errsock.c logging.c mainchan.c \ + marshal.c memory.c misc.c mpint.c nullplug.c pgssapi.c \ + pinger.c portfwd.c proxy.c pscp.c psftpcommon.c settings.c \ + sftp.c sftpcommon.c ssh.c ssh1bpp.c ssh1censor.c \ + ssh1connection-client.c ssh1connection.c ssh1login.c \ + ssh2bpp-bare.c ssh2bpp.c ssh2censor.c \ + ssh2connection-client.c ssh2connection.c ssh2kex-client.c \ + ssh2transhk.c ssh2transport.c ssh2userauth.c sshaes.c \ + ssharcf.c sshauxcrypt.c sshblowf.c sshccp.c sshcommon.c \ + sshcrc.c sshcrcda.c sshdes.c sshdh.c sshdss.c sshecc.c \ + sshgssc.c sshhmac.c sshmac.c sshmd5.c sshprng.c sshpubk.c \ + sshrand.c sshrsa.c sshsh256.c sshsh512.c sshsha.c sshshare.c \ + sshverstring.c sshzlib.c stripctrl.c time.c timing.c \ + tree234.c unix/uxagentc.c unix/uxcons.c unix/uxfdsock.c \ + unix/uxgss.c unix/uxmisc.c unix/uxnet.c unix/uxnogtk.c \ + unix/uxnoise.c unix/uxpeer.c unix/uxpoll.c unix/uxproxy.c \ + unix/uxsel.c unix/uxsftp.c unix/uxshare.c unix/uxstore.c \ + unix/uxutils.c utils.c wcwidth.c wildcard.c x11fwd.c + +pscp_LDADD = libversion.a +psftp_SOURCES = agentf.c aqsync.c be_misc.c be_ssh.c callback.c cmdline.c \ + conf.c cproxy.c ecc.c errsock.c logging.c mainchan.c \ + marshal.c memory.c misc.c mpint.c nullplug.c pgssapi.c \ + pinger.c portfwd.c proxy.c psftp.c psftpcommon.c settings.c \ + sftp.c sftpcommon.c ssh.c ssh1bpp.c ssh1censor.c \ + ssh1connection-client.c ssh1connection.c ssh1login.c \ + ssh2bpp-bare.c ssh2bpp.c ssh2censor.c \ + ssh2connection-client.c ssh2connection.c ssh2kex-client.c \ + ssh2transhk.c ssh2transport.c ssh2userauth.c sshaes.c \ + ssharcf.c sshauxcrypt.c sshblowf.c sshccp.c sshcommon.c \ + sshcrc.c sshcrcda.c sshdes.c sshdh.c sshdss.c sshecc.c \ + sshgssc.c sshhmac.c sshmac.c sshmd5.c sshprng.c sshpubk.c \ + sshrand.c sshrsa.c sshsh256.c sshsh512.c sshsha.c sshshare.c \ + sshverstring.c sshzlib.c stripctrl.c time.c timing.c \ + tree234.c unix/uxagentc.c unix/uxcons.c unix/uxfdsock.c \ + unix/uxgss.c unix/uxmisc.c unix/uxnet.c unix/uxnogtk.c \ + unix/uxnoise.c unix/uxpeer.c unix/uxpoll.c unix/uxproxy.c \ + unix/uxsel.c unix/uxsftp.c unix/uxshare.c unix/uxstore.c \ + unix/uxutils.c utils.c wcwidth.c wildcard.c x11fwd.c + +psftp_LDADD = libversion.a +@HAVE_GTK_TRUE@pterm_SOURCES = be_none.c callback.c charset/fromucs.c charset/localenc.c \ +@HAVE_GTK_TRUE@ charset/macenc.c charset/mimeenc.c charset/sbcs.c \ +@HAVE_GTK_TRUE@ charset/sbcsdat.c charset/slookup.c charset/toucs.c \ +@HAVE_GTK_TRUE@ charset/utf8.c charset/xenc.c cmdline.c conf.c config.c \ +@HAVE_GTK_TRUE@ dialog.c ldisc.c logging.c marshal.c memory.c minibidi.c \ +@HAVE_GTK_TRUE@ misc.c miscucs.c nocproxy.c nogss.c sercfg.c sessprep.c \ +@HAVE_GTK_TRUE@ settings.c stripctrl.c terminal.c time.c timing.c tree234.c \ +@HAVE_GTK_TRUE@ unix/gtkcfg.c unix/gtkcols.c unix/gtkcomm.c unix/gtkdlg.c \ +@HAVE_GTK_TRUE@ unix/gtkfont.c unix/gtkmain.c unix/gtkmisc.c unix/gtkwin.c \ +@HAVE_GTK_TRUE@ unix/uxcfg.c unix/uxmisc.c unix/uxprint.c unix/uxpterm.c \ +@HAVE_GTK_TRUE@ unix/uxpty.c unix/uxsel.c unix/uxsignal.c unix/uxstore.c \ +@HAVE_GTK_TRUE@ unix/uxucs.c unix/x11misc.c unix/xkeysym.c unix/xpmptcfg.c \ +@HAVE_GTK_TRUE@ unix/xpmpterm.c utils.c wcwidth.c + +@HAVE_GTK_TRUE@pterm_LDADD = libversion.a $(GTK_LIBS) +@HAVE_GTK_TRUE@ptermapp_SOURCES = be_none.c callback.c charset/fromucs.c charset/localenc.c \ +@HAVE_GTK_TRUE@ charset/macenc.c charset/mimeenc.c charset/sbcs.c \ +@HAVE_GTK_TRUE@ charset/sbcsdat.c charset/slookup.c charset/toucs.c \ +@HAVE_GTK_TRUE@ charset/utf8.c charset/xenc.c conf.c config.c dialog.c \ +@HAVE_GTK_TRUE@ ldisc.c logging.c marshal.c memory.c minibidi.c misc.c \ +@HAVE_GTK_TRUE@ miscucs.c nocmdline.c nocproxy.c nogss.c sercfg.c sessprep.c \ +@HAVE_GTK_TRUE@ settings.c stripctrl.c terminal.c time.c timing.c tree234.c \ +@HAVE_GTK_TRUE@ unix/gtkapp.c unix/gtkcfg.c unix/gtkcols.c unix/gtkcomm.c \ +@HAVE_GTK_TRUE@ unix/gtkdlg.c unix/gtkfont.c unix/gtkmisc.c unix/gtkwin.c \ +@HAVE_GTK_TRUE@ unix/uxcfg.c unix/uxmisc.c unix/uxprint.c unix/uxpterm.c \ +@HAVE_GTK_TRUE@ unix/uxpty.c unix/uxsel.c unix/uxsignal.c unix/uxstore.c \ +@HAVE_GTK_TRUE@ unix/uxucs.c unix/x11misc.c unix/xkeysym.c unix/xpmptcfg.c \ +@HAVE_GTK_TRUE@ unix/xpmpterm.c utils.c wcwidth.c + +@HAVE_GTK_TRUE@ptermapp_LDADD = libversion.a $(GTK_LIBS) +@HAVE_GTK_TRUE@putty_SOURCES = agentf.c aqsync.c be_all_s.c be_misc.c callback.c \ +@HAVE_GTK_TRUE@ charset/fromucs.c charset/localenc.c charset/macenc.c \ +@HAVE_GTK_TRUE@ charset/mimeenc.c charset/sbcs.c charset/sbcsdat.c \ +@HAVE_GTK_TRUE@ charset/slookup.c charset/toucs.c charset/utf8.c \ +@HAVE_GTK_TRUE@ charset/xenc.c cmdline.c conf.c config.c cproxy.c dialog.c \ +@HAVE_GTK_TRUE@ ecc.c errsock.c ldisc.c logging.c mainchan.c marshal.c \ +@HAVE_GTK_TRUE@ memory.c minibidi.c misc.c miscucs.c mpint.c nullplug.c \ +@HAVE_GTK_TRUE@ pgssapi.c pinger.c portfwd.c proxy.c raw.c rlogin.c sercfg.c \ +@HAVE_GTK_TRUE@ sessprep.c settings.c ssh.c ssh1bpp.c ssh1censor.c \ +@HAVE_GTK_TRUE@ ssh1connection-client.c ssh1connection.c ssh1login.c \ +@HAVE_GTK_TRUE@ ssh2bpp-bare.c ssh2bpp.c ssh2censor.c \ +@HAVE_GTK_TRUE@ ssh2connection-client.c ssh2connection.c ssh2kex-client.c \ +@HAVE_GTK_TRUE@ ssh2transhk.c ssh2transport.c ssh2userauth.c sshaes.c \ +@HAVE_GTK_TRUE@ ssharcf.c sshauxcrypt.c sshblowf.c sshccp.c sshcommon.c \ +@HAVE_GTK_TRUE@ sshcrc.c sshcrcda.c sshdes.c sshdh.c sshdss.c sshecc.c \ +@HAVE_GTK_TRUE@ sshgssc.c sshhmac.c sshmac.c sshmd5.c sshprng.c sshpubk.c \ +@HAVE_GTK_TRUE@ sshrand.c sshrsa.c sshsh256.c sshsh512.c sshsha.c sshshare.c \ +@HAVE_GTK_TRUE@ sshverstring.c sshzlib.c stripctrl.c telnet.c terminal.c \ +@HAVE_GTK_TRUE@ time.c timing.c tree234.c unix/gtkcfg.c unix/gtkcols.c \ +@HAVE_GTK_TRUE@ unix/gtkcomm.c unix/gtkdlg.c unix/gtkfont.c unix/gtkmain.c \ +@HAVE_GTK_TRUE@ unix/gtkmisc.c unix/gtkwin.c unix/ux_x11.c unix/uxagentc.c \ +@HAVE_GTK_TRUE@ unix/uxcfg.c unix/uxfdsock.c unix/uxgss.c unix/uxmisc.c \ +@HAVE_GTK_TRUE@ unix/uxnet.c unix/uxnoise.c unix/uxpeer.c unix/uxpoll.c \ +@HAVE_GTK_TRUE@ unix/uxprint.c unix/uxproxy.c unix/uxputty.c unix/uxsel.c \ +@HAVE_GTK_TRUE@ unix/uxser.c unix/uxshare.c unix/uxsignal.c unix/uxstore.c \ +@HAVE_GTK_TRUE@ unix/uxucs.c unix/uxutils.c unix/x11misc.c unix/xkeysym.c \ +@HAVE_GTK_TRUE@ unix/xpmpucfg.c unix/xpmputty.c utils.c wcwidth.c wildcard.c \ +@HAVE_GTK_TRUE@ x11fwd.c + +@HAVE_GTK_TRUE@putty_LDADD = libversion.a $(GTK_LIBS) +@HAVE_GTK_TRUE@puttyapp_SOURCES = agentf.c aqsync.c be_all_s.c be_misc.c callback.c \ +@HAVE_GTK_TRUE@ charset/fromucs.c charset/localenc.c charset/macenc.c \ +@HAVE_GTK_TRUE@ charset/mimeenc.c charset/sbcs.c charset/sbcsdat.c \ +@HAVE_GTK_TRUE@ charset/slookup.c charset/toucs.c charset/utf8.c \ +@HAVE_GTK_TRUE@ charset/xenc.c conf.c config.c cproxy.c dialog.c ecc.c \ +@HAVE_GTK_TRUE@ errsock.c ldisc.c logging.c mainchan.c marshal.c memory.c \ +@HAVE_GTK_TRUE@ minibidi.c misc.c miscucs.c mpint.c nocmdline.c nullplug.c \ +@HAVE_GTK_TRUE@ pgssapi.c pinger.c portfwd.c proxy.c raw.c rlogin.c sercfg.c \ +@HAVE_GTK_TRUE@ sessprep.c settings.c ssh.c ssh1bpp.c ssh1censor.c \ +@HAVE_GTK_TRUE@ ssh1connection-client.c ssh1connection.c ssh1login.c \ +@HAVE_GTK_TRUE@ ssh2bpp-bare.c ssh2bpp.c ssh2censor.c \ +@HAVE_GTK_TRUE@ ssh2connection-client.c ssh2connection.c ssh2kex-client.c \ +@HAVE_GTK_TRUE@ ssh2transhk.c ssh2transport.c ssh2userauth.c sshaes.c \ +@HAVE_GTK_TRUE@ ssharcf.c sshauxcrypt.c sshblowf.c sshccp.c sshcommon.c \ +@HAVE_GTK_TRUE@ sshcrc.c sshcrcda.c sshdes.c sshdh.c sshdss.c sshecc.c \ +@HAVE_GTK_TRUE@ sshgssc.c sshhmac.c sshmac.c sshmd5.c sshprng.c sshpubk.c \ +@HAVE_GTK_TRUE@ sshrand.c sshrsa.c sshsh256.c sshsh512.c sshsha.c sshshare.c \ +@HAVE_GTK_TRUE@ sshverstring.c sshzlib.c stripctrl.c telnet.c terminal.c \ +@HAVE_GTK_TRUE@ time.c timing.c tree234.c unix/gtkapp.c unix/gtkcfg.c \ +@HAVE_GTK_TRUE@ unix/gtkcols.c unix/gtkcomm.c unix/gtkdlg.c unix/gtkfont.c \ +@HAVE_GTK_TRUE@ unix/gtkmisc.c unix/gtkwin.c unix/ux_x11.c unix/uxagentc.c \ +@HAVE_GTK_TRUE@ unix/uxcfg.c unix/uxfdsock.c unix/uxgss.c unix/uxmisc.c \ +@HAVE_GTK_TRUE@ unix/uxnet.c unix/uxnoise.c unix/uxpeer.c unix/uxpoll.c \ +@HAVE_GTK_TRUE@ unix/uxprint.c unix/uxproxy.c unix/uxputty.c unix/uxsel.c \ +@HAVE_GTK_TRUE@ unix/uxser.c unix/uxshare.c unix/uxsignal.c unix/uxstore.c \ +@HAVE_GTK_TRUE@ unix/uxucs.c unix/uxutils.c unix/x11misc.c unix/xkeysym.c \ +@HAVE_GTK_TRUE@ unix/xpmpucfg.c unix/xpmputty.c utils.c wcwidth.c wildcard.c \ +@HAVE_GTK_TRUE@ x11fwd.c + +@HAVE_GTK_TRUE@puttyapp_LDADD = libversion.a $(GTK_LIBS) +puttygen_SOURCES = cmdgen.c conf.c ecc.c import.c marshal.c memory.c misc.c \ + mpint.c notiming.c sshaes.c sshauxcrypt.c sshbcrypt.c \ + sshblowf.c sshdes.c sshdss.c sshdssg.c sshecc.c sshecdsag.c \ + sshhmac.c sshmd5.c sshprime.c sshprng.c sshpubk.c sshrand.c \ + sshrsa.c sshrsag.c sshsh256.c sshsh512.c sshsha.c \ + stripctrl.c time.c tree234.c unix/uxcons.c unix/uxgen.c \ + unix/uxmisc.c unix/uxnogtk.c unix/uxnoise.c unix/uxpoll.c \ + unix/uxstore.c unix/uxutils.c utils.c wcwidth.c + +puttygen_LDADD = libversion.a +@HAVE_GTK_TRUE@puttytel_SOURCES = be_misc.c be_nos_s.c callback.c charset/fromucs.c \ +@HAVE_GTK_TRUE@ charset/localenc.c charset/macenc.c charset/mimeenc.c \ +@HAVE_GTK_TRUE@ charset/sbcs.c charset/sbcsdat.c charset/slookup.c \ +@HAVE_GTK_TRUE@ charset/toucs.c charset/utf8.c charset/xenc.c cmdline.c \ +@HAVE_GTK_TRUE@ conf.c config.c dialog.c errsock.c ldisc.c logging.c \ +@HAVE_GTK_TRUE@ marshal.c memory.c minibidi.c misc.c miscucs.c nocproxy.c \ +@HAVE_GTK_TRUE@ nogss.c pinger.c proxy.c raw.c rlogin.c sercfg.c sessprep.c \ +@HAVE_GTK_TRUE@ settings.c stripctrl.c telnet.c terminal.c time.c timing.c \ +@HAVE_GTK_TRUE@ tree234.c unix/gtkcfg.c unix/gtkcols.c unix/gtkcomm.c \ +@HAVE_GTK_TRUE@ unix/gtkdlg.c unix/gtkfont.c unix/gtkmain.c unix/gtkmisc.c \ +@HAVE_GTK_TRUE@ unix/gtkwin.c unix/uxcfg.c unix/uxfdsock.c unix/uxmisc.c \ +@HAVE_GTK_TRUE@ unix/uxnet.c unix/uxpeer.c unix/uxpoll.c unix/uxprint.c \ +@HAVE_GTK_TRUE@ unix/uxproxy.c unix/uxputty.c unix/uxsel.c unix/uxser.c \ +@HAVE_GTK_TRUE@ unix/uxsignal.c unix/uxstore.c unix/uxucs.c unix/uxutils.c \ +@HAVE_GTK_TRUE@ unix/x11misc.c unix/xkeysym.c unix/xpmpucfg.c \ +@HAVE_GTK_TRUE@ unix/xpmputty.c utils.c wcwidth.c + +@HAVE_GTK_TRUE@puttytel_LDADD = libversion.a $(GTK_LIBS) +testcrypt_SOURCES = ecc.c marshal.c memory.c mpint.c sshaes.c ssharcf.c \ + sshauxcrypt.c sshblowf.c sshccp.c sshcrc.c sshcrcda.c \ + sshdes.c sshdh.c sshdss.c sshecc.c sshhmac.c sshmd5.c \ + sshprime.c sshprng.c sshrsa.c sshsh256.c sshsh512.c sshsha.c \ + testcrypt.c tree234.c unix/uxutils.c utils.c + +testsc_SOURCES = ecc.c marshal.c memory.c mpint.c sshaes.c ssharcf.c \ + sshauxcrypt.c sshblowf.c sshccp.c sshcrc.c sshcrcda.c \ + sshdes.c sshdh.c sshdss.c sshecc.c sshhmac.c sshmac.c \ + sshmd5.c sshrsa.c sshsh256.c sshsh512.c sshsha.c testsc.c \ + tree234.c unix/uxutils.c utils.c wildcard.c + +testzlib_SOURCES = marshal.c memory.c sshzlib.c testzlib.c utils.c +uppity_SOURCES = be_misc.c be_none.c callback.c conf.c cproxy.c ecc.c \ + errsock.c logging.c marshal.c memory.c misc.c mpint.c \ + nullplug.c pgssapi.c portfwd.c proxy.c scpserver.c \ + sesschan.c settings.c sftpcommon.c sftpserver.c ssh1bpp.c \ + ssh1censor.c ssh1connection-server.c ssh1connection.c \ + ssh1login-server.c ssh2bpp.c ssh2censor.c \ + ssh2connection-server.c ssh2connection.c ssh2kex-server.c \ + ssh2transhk.c ssh2transport.c ssh2userauth-server.c sshaes.c \ + ssharcf.c sshauxcrypt.c sshblowf.c sshccp.c sshcommon.c \ + sshcrc.c sshcrcda.c sshdes.c sshdh.c sshdss.c sshecc.c \ + sshgssc.c sshhmac.c sshmac.c sshmd5.c sshprime.c sshprng.c \ + sshpubk.c sshrand.c sshrsa.c sshrsag.c sshserver.c \ + sshsh256.c sshsh512.c sshsha.c sshverstring.c sshzlib.c \ + stripctrl.c time.c timing.c tree234.c unix/procnet.c \ + unix/ux_x11.c unix/uxagentsock.c unix/uxfdsock.c \ + unix/uxgss.c unix/uxmisc.c unix/uxnet.c unix/uxnogtk.c \ + unix/uxnoise.c unix/uxpeer.c unix/uxpoll.c unix/uxproxy.c \ + unix/uxpty.c unix/uxsel.c unix/uxserver.c \ + unix/uxsftpserver.c unix/uxsignal.c unix/uxstore.c \ + unix/uxutils.c utils.c wcwidth.c wildcard.c x11fwd.c + +uppity_LDADD = libversion.a +@AUTO_GIT_COMMIT_TRUE@BUILT_SOURCES = empty.h +@AUTO_GIT_COMMIT_TRUE@CLEANFILES = empty.h +@HAVE_GTK_FALSE@man1_MANS = doc/plink.1 doc/pscp.1 doc/psftp.1 doc/puttygen.1 +@HAVE_GTK_TRUE@man1_MANS = doc/plink.1 doc/pscp.1 doc/psftp.1 doc/puttygen.1 \ +@HAVE_GTK_TRUE@ doc/pageant.1 doc/pterm.1 doc/putty.1 doc/puttytel.1 + +@HAVE_QUARTZ_TRUE@noinst_SCRIPTS = unix/PuTTY.app unix/Pterm.app +all: $(BUILT_SOURCES) uxconfig.h + $(MAKE) $(AM_MAKEFLAGS) all-am + +.SUFFIXES: +.SUFFIXES: .c .o .obj +am--refresh: Makefile + @: +$(srcdir)/Makefile.in: $(srcdir)/Makefile.am $(am__configure_deps) + @for dep in $?; do \ + case '$(am__configure_deps)' in \ + *$$dep*) \ + echo ' cd $(srcdir) && $(AUTOMAKE) --foreign'; \ + $(am__cd) $(srcdir) && $(AUTOMAKE) --foreign \ + && exit 0; \ + exit 1;; \ + esac; \ + done; \ + echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign Makefile'; \ + $(am__cd) $(top_srcdir) && \ + $(AUTOMAKE) --foreign Makefile +Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status + @case '$?' in \ + *config.status*) \ + echo ' $(SHELL) ./config.status'; \ + $(SHELL) ./config.status;; \ + *) \ + echo ' cd $(top_builddir) && $(SHELL) ./config.status $@ $(am__depfiles_maybe)'; \ + cd $(top_builddir) && $(SHELL) ./config.status $@ $(am__depfiles_maybe);; \ + esac; + +$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES) + $(SHELL) ./config.status --recheck + +$(top_srcdir)/configure: $(am__configure_deps) + $(am__cd) $(srcdir) && $(AUTOCONF) +$(ACLOCAL_M4): $(am__aclocal_m4_deps) + $(am__cd) $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS) +$(am__aclocal_m4_deps): + +uxconfig.h: stamp-h1 + @test -f $@ || rm -f stamp-h1 + @test -f $@ || $(MAKE) $(AM_MAKEFLAGS) stamp-h1 + +stamp-h1: $(srcdir)/uxconfig.in $(top_builddir)/config.status + @rm -f stamp-h1 + cd $(top_builddir) && $(SHELL) ./config.status uxconfig.h +$(srcdir)/uxconfig.in: $(am__configure_deps) + ($(am__cd) $(top_srcdir) && $(AUTOHEADER)) + rm -f stamp-h1 + touch $@ + +distclean-hdr: + -rm -f uxconfig.h stamp-h1 + +clean-noinstLIBRARIES: + -test -z "$(noinst_LIBRARIES)" || rm -f $(noinst_LIBRARIES) + +libversion.a: $(libversion_a_OBJECTS) $(libversion_a_DEPENDENCIES) $(EXTRA_libversion_a_DEPENDENCIES) + $(AM_V_at)-rm -f libversion.a + $(AM_V_AR)$(libversion_a_AR) libversion.a $(libversion_a_OBJECTS) $(libversion_a_LIBADD) + $(AM_V_at)$(RANLIB) libversion.a +install-binPROGRAMS: $(bin_PROGRAMS) + @$(NORMAL_INSTALL) + @list='$(bin_PROGRAMS)'; test -n "$(bindir)" || list=; \ + if test -n "$$list"; then \ + echo " $(MKDIR_P) '$(DESTDIR)$(bindir)'"; \ + $(MKDIR_P) "$(DESTDIR)$(bindir)" || exit 1; \ + fi; \ + for p in $$list; do echo "$$p $$p"; done | \ + sed 's/$(EXEEXT)$$//' | \ + while read p p1; do if test -f $$p \ + ; then echo "$$p"; echo "$$p"; else :; fi; \ + done | \ + sed -e 'p;s,.*/,,;n;h' \ + -e 's|.*|.|' \ + -e 'p;x;s,.*/,,;s/$(EXEEXT)$$//;$(transform);s/$$/$(EXEEXT)/' | \ + sed 'N;N;N;s,\n, ,g' | \ + $(AWK) 'BEGIN { files["."] = ""; dirs["."] = 1 } \ + { d=$$3; if (dirs[d] != 1) { print "d", d; dirs[d] = 1 } \ + if ($$2 == $$4) files[d] = files[d] " " $$1; \ + else { print "f", $$3 "/" $$4, $$1; } } \ + END { for (d in files) print "f", d, files[d] }' | \ + while read type dir files; do \ + if test "$$dir" = .; then dir=; else dir=/$$dir; fi; \ + test -z "$$files" || { \ + echo " $(INSTALL_PROGRAM_ENV) $(INSTALL_PROGRAM) $$files '$(DESTDIR)$(bindir)$$dir'"; \ + $(INSTALL_PROGRAM_ENV) $(INSTALL_PROGRAM) $$files "$(DESTDIR)$(bindir)$$dir" || exit $$?; \ + } \ + ; done + +uninstall-binPROGRAMS: + @$(NORMAL_UNINSTALL) + @list='$(bin_PROGRAMS)'; test -n "$(bindir)" || list=; \ + files=`for p in $$list; do echo "$$p"; done | \ + sed -e 'h;s,^.*/,,;s/$(EXEEXT)$$//;$(transform)' \ + -e 's/$$/$(EXEEXT)/' \ + `; \ + test -n "$$list" || exit 0; \ + echo " ( cd '$(DESTDIR)$(bindir)' && rm -f" $$files ")"; \ + cd "$(DESTDIR)$(bindir)" && rm -f $$files + +clean-binPROGRAMS: + -test -z "$(bin_PROGRAMS)" || rm -f $(bin_PROGRAMS) + +clean-noinstPROGRAMS: + -test -z "$(noinst_PROGRAMS)" || rm -f $(noinst_PROGRAMS) +unix/$(am__dirstamp): + @$(MKDIR_P) unix + @: > unix/$(am__dirstamp) +unix/$(DEPDIR)/$(am__dirstamp): + @$(MKDIR_P) unix/$(DEPDIR) + @: > unix/$(DEPDIR)/$(am__dirstamp) +unix/uxcons.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxgen.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxmisc.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxnogtk.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxnoise.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxpoll.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxstore.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxutils.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) + +cgtest$(EXEEXT): $(cgtest_OBJECTS) $(cgtest_DEPENDENCIES) $(EXTRA_cgtest_DEPENDENCIES) + @rm -f cgtest$(EXEEXT) + $(AM_V_CCLD)$(LINK) $(cgtest_OBJECTS) $(cgtest_LDADD) $(LIBS) +charset/$(am__dirstamp): + @$(MKDIR_P) charset + @: > charset/$(am__dirstamp) +charset/$(DEPDIR)/$(am__dirstamp): + @$(MKDIR_P) charset/$(DEPDIR) + @: > charset/$(DEPDIR)/$(am__dirstamp) +charset/fromucs.$(OBJEXT): charset/$(am__dirstamp) \ + charset/$(DEPDIR)/$(am__dirstamp) +charset/localenc.$(OBJEXT): charset/$(am__dirstamp) \ + charset/$(DEPDIR)/$(am__dirstamp) +charset/macenc.$(OBJEXT): charset/$(am__dirstamp) \ + charset/$(DEPDIR)/$(am__dirstamp) +charset/mimeenc.$(OBJEXT): charset/$(am__dirstamp) \ + charset/$(DEPDIR)/$(am__dirstamp) +charset/sbcs.$(OBJEXT): charset/$(am__dirstamp) \ + charset/$(DEPDIR)/$(am__dirstamp) +charset/sbcsdat.$(OBJEXT): charset/$(am__dirstamp) \ + charset/$(DEPDIR)/$(am__dirstamp) +charset/slookup.$(OBJEXT): charset/$(am__dirstamp) \ + charset/$(DEPDIR)/$(am__dirstamp) +charset/toucs.$(OBJEXT): charset/$(am__dirstamp) \ + charset/$(DEPDIR)/$(am__dirstamp) +charset/utf8.$(OBJEXT): charset/$(am__dirstamp) \ + charset/$(DEPDIR)/$(am__dirstamp) +charset/xenc.$(OBJEXT): charset/$(am__dirstamp) \ + charset/$(DEPDIR)/$(am__dirstamp) +unix/uxcfg.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxprint.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxucs.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) + +fuzzterm$(EXEEXT): $(fuzzterm_OBJECTS) $(fuzzterm_DEPENDENCIES) $(EXTRA_fuzzterm_DEPENDENCIES) + @rm -f fuzzterm$(EXEEXT) + $(AM_V_CCLD)$(LINK) $(fuzzterm_OBJECTS) $(fuzzterm_LDADD) $(LIBS) +unix/osxlaunch.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) + +osxlaunch$(EXEEXT): $(osxlaunch_OBJECTS) $(osxlaunch_DEPENDENCIES) $(EXTRA_osxlaunch_DEPENDENCIES) + @rm -f osxlaunch$(EXEEXT) + $(AM_V_CCLD)$(LINK) $(osxlaunch_OBJECTS) $(osxlaunch_LDADD) $(LIBS) +unix/gtkask.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/gtkmisc.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/ux_x11.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxagentc.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxagentsock.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxfdsock.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxnet.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxpeer.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxpgnt.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxproxy.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxsel.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxsignal.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) + +pageant$(EXEEXT): $(pageant_OBJECTS) $(pageant_DEPENDENCIES) $(EXTRA_pageant_DEPENDENCIES) + @rm -f pageant$(EXEEXT) + $(AM_V_CCLD)$(LINK) $(pageant_OBJECTS) $(pageant_LDADD) $(LIBS) +unix/uxgss.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxplink.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxser.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxshare.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) + +plink$(EXEEXT): $(plink_OBJECTS) $(plink_DEPENDENCIES) $(EXTRA_plink_DEPENDENCIES) + @rm -f plink$(EXEEXT) + $(AM_V_CCLD)$(LINK) $(plink_OBJECTS) $(plink_LDADD) $(LIBS) +unix/uxsftp.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) + +pscp$(EXEEXT): $(pscp_OBJECTS) $(pscp_DEPENDENCIES) $(EXTRA_pscp_DEPENDENCIES) + @rm -f pscp$(EXEEXT) + $(AM_V_CCLD)$(LINK) $(pscp_OBJECTS) $(pscp_LDADD) $(LIBS) + +psftp$(EXEEXT): $(psftp_OBJECTS) $(psftp_DEPENDENCIES) $(EXTRA_psftp_DEPENDENCIES) + @rm -f psftp$(EXEEXT) + $(AM_V_CCLD)$(LINK) $(psftp_OBJECTS) $(psftp_LDADD) $(LIBS) +unix/gtkcfg.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/gtkcols.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/gtkcomm.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/gtkdlg.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/gtkfont.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/gtkmain.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/gtkwin.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxpterm.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxpty.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/x11misc.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/xkeysym.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/xpmptcfg.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/xpmpterm.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) + +pterm$(EXEEXT): $(pterm_OBJECTS) $(pterm_DEPENDENCIES) $(EXTRA_pterm_DEPENDENCIES) + @rm -f pterm$(EXEEXT) + $(AM_V_CCLD)$(LINK) $(pterm_OBJECTS) $(pterm_LDADD) $(LIBS) +unix/gtkapp.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) + +ptermapp$(EXEEXT): $(ptermapp_OBJECTS) $(ptermapp_DEPENDENCIES) $(EXTRA_ptermapp_DEPENDENCIES) + @rm -f ptermapp$(EXEEXT) + $(AM_V_CCLD)$(LINK) $(ptermapp_OBJECTS) $(ptermapp_LDADD) $(LIBS) +unix/uxputty.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/xpmpucfg.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/xpmputty.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) + +putty$(EXEEXT): $(putty_OBJECTS) $(putty_DEPENDENCIES) $(EXTRA_putty_DEPENDENCIES) + @rm -f putty$(EXEEXT) + $(AM_V_CCLD)$(LINK) $(putty_OBJECTS) $(putty_LDADD) $(LIBS) + +puttyapp$(EXEEXT): $(puttyapp_OBJECTS) $(puttyapp_DEPENDENCIES) $(EXTRA_puttyapp_DEPENDENCIES) + @rm -f puttyapp$(EXEEXT) + $(AM_V_CCLD)$(LINK) $(puttyapp_OBJECTS) $(puttyapp_LDADD) $(LIBS) + +puttygen$(EXEEXT): $(puttygen_OBJECTS) $(puttygen_DEPENDENCIES) $(EXTRA_puttygen_DEPENDENCIES) + @rm -f puttygen$(EXEEXT) + $(AM_V_CCLD)$(LINK) $(puttygen_OBJECTS) $(puttygen_LDADD) $(LIBS) + +puttytel$(EXEEXT): $(puttytel_OBJECTS) $(puttytel_DEPENDENCIES) $(EXTRA_puttytel_DEPENDENCIES) + @rm -f puttytel$(EXEEXT) + $(AM_V_CCLD)$(LINK) $(puttytel_OBJECTS) $(puttytel_LDADD) $(LIBS) + +testcrypt$(EXEEXT): $(testcrypt_OBJECTS) $(testcrypt_DEPENDENCIES) $(EXTRA_testcrypt_DEPENDENCIES) + @rm -f testcrypt$(EXEEXT) + $(AM_V_CCLD)$(LINK) $(testcrypt_OBJECTS) $(testcrypt_LDADD) $(LIBS) + +testsc$(EXEEXT): $(testsc_OBJECTS) $(testsc_DEPENDENCIES) $(EXTRA_testsc_DEPENDENCIES) + @rm -f testsc$(EXEEXT) + $(AM_V_CCLD)$(LINK) $(testsc_OBJECTS) $(testsc_LDADD) $(LIBS) + +testzlib$(EXEEXT): $(testzlib_OBJECTS) $(testzlib_DEPENDENCIES) $(EXTRA_testzlib_DEPENDENCIES) + @rm -f testzlib$(EXEEXT) + $(AM_V_CCLD)$(LINK) $(testzlib_OBJECTS) $(testzlib_LDADD) $(LIBS) +unix/procnet.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxserver.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) +unix/uxsftpserver.$(OBJEXT): unix/$(am__dirstamp) \ + unix/$(DEPDIR)/$(am__dirstamp) + +uppity$(EXEEXT): $(uppity_OBJECTS) $(uppity_DEPENDENCIES) $(EXTRA_uppity_DEPENDENCIES) + @rm -f uppity$(EXEEXT) + $(AM_V_CCLD)$(LINK) $(uppity_OBJECTS) $(uppity_LDADD) $(LIBS) + +mostlyclean-compile: + -rm -f *.$(OBJEXT) + -rm -f charset/*.$(OBJEXT) + -rm -f unix/*.$(OBJEXT) + +distclean-compile: + -rm -f *.tab.c + +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/agentf.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/aqsync.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/be_all_s.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/be_misc.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/be_none.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/be_nos_s.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/be_ssh.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/callback.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/cgtest.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/cmdgen.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/cmdline.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/conf.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/config.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/cproxy.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/dialog.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ecc.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/errsock.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/fuzzterm.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/import.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ldisc.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/libversion_a-version.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/logging.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/mainchan.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/marshal.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/memory.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/minibidi.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/misc.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/miscucs.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/mpint.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/nocmdline.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/nocproxy.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/nogss.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/noterm.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/notiming.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/nullplug.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/pageant.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/pgssapi.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/pinger.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/portfwd.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/proxy.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/pscp.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/psftp.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/psftpcommon.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/raw.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/rlogin.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/scpserver.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sercfg.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sesschan.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sessprep.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/settings.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sftp.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sftpcommon.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sftpserver.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh1bpp.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh1censor.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh1connection-client.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh1connection-server.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh1connection.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh1login-server.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh1login.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh2bpp-bare.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh2bpp.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh2censor.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh2connection-client.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh2connection-server.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh2connection.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh2kex-client.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh2kex-server.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh2transhk.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh2transport.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh2userauth-server.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssh2userauth.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshaes.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/ssharcf.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshauxcrypt.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshbcrypt.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshblowf.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshccp.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshcommon.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshcrc.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshcrcda.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshdes.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshdh.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshdss.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshdssg.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshecc.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshecdsag.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshgssc.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshhmac.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshmac.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshmd5.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshprime.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshprng.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshpubk.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshrand.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshrsa.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshrsag.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshserver.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshsh256.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshsh512.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshsha.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshshare.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshverstring.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/sshzlib.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/stripctrl.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/telnet.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/terminal.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/testcrypt.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/testsc.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/testzlib.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/time.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/timing.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/tree234.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/utils.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/wcwidth.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/wildcard.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/x11fwd.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@charset/$(DEPDIR)/fromucs.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@charset/$(DEPDIR)/localenc.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@charset/$(DEPDIR)/macenc.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@charset/$(DEPDIR)/mimeenc.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@charset/$(DEPDIR)/sbcs.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@charset/$(DEPDIR)/sbcsdat.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@charset/$(DEPDIR)/slookup.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@charset/$(DEPDIR)/toucs.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@charset/$(DEPDIR)/utf8.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@charset/$(DEPDIR)/xenc.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/gtkapp.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/gtkask.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/gtkcfg.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/gtkcols.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/gtkcomm.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/gtkdlg.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/gtkfont.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/gtkmain.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/gtkmisc.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/gtkwin.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/osxlaunch.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/procnet.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/ux_x11.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxagentc.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxagentsock.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxcfg.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxcons.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxfdsock.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxgen.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxgss.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxmisc.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxnet.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxnogtk.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxnoise.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxpeer.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxpgnt.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxplink.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxpoll.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxprint.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxproxy.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxpterm.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxpty.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxputty.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxsel.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxser.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxserver.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxsftp.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxsftpserver.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxshare.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxsignal.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxstore.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxucs.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/uxutils.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/x11misc.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/xkeysym.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/xpmptcfg.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/xpmpterm.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/xpmpucfg.Po@am__quote@ +@AMDEP_TRUE@@am__include@ @am__quote@unix/$(DEPDIR)/xpmputty.Po@am__quote@ + +.c.o: +@am__fastdepCC_TRUE@ $(AM_V_CC)depbase=`echo $@ | sed 's|[^/]*$$|$(DEPDIR)/&|;s|\.o$$||'`;\ +@am__fastdepCC_TRUE@ $(COMPILE) -MT $@ -MD -MP -MF $$depbase.Tpo -c -o $@ $< &&\ +@am__fastdepCC_TRUE@ $(am__mv) $$depbase.Tpo $$depbase.Po +@AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='$<' object='$@' libtool=no @AMDEPBACKSLASH@ +@AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ +@am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(COMPILE) -c -o $@ $< + +.c.obj: +@am__fastdepCC_TRUE@ $(AM_V_CC)depbase=`echo $@ | sed 's|[^/]*$$|$(DEPDIR)/&|;s|\.obj$$||'`;\ +@am__fastdepCC_TRUE@ $(COMPILE) -MT $@ -MD -MP -MF $$depbase.Tpo -c -o $@ `$(CYGPATH_W) '$<'` &&\ +@am__fastdepCC_TRUE@ $(am__mv) $$depbase.Tpo $$depbase.Po +@AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='$<' object='$@' libtool=no @AMDEPBACKSLASH@ +@AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ +@am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(COMPILE) -c -o $@ `$(CYGPATH_W) '$<'` + +libversion_a-version.o: version.c +@am__fastdepCC_TRUE@ $(AM_V_CC)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(libversion_a_CFLAGS) $(CFLAGS) -MT libversion_a-version.o -MD -MP -MF $(DEPDIR)/libversion_a-version.Tpo -c -o libversion_a-version.o `test -f 'version.c' || echo '$(srcdir)/'`version.c +@am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) $(DEPDIR)/libversion_a-version.Tpo $(DEPDIR)/libversion_a-version.Po +@AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='version.c' object='libversion_a-version.o' libtool=no @AMDEPBACKSLASH@ +@AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ +@am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(libversion_a_CFLAGS) $(CFLAGS) -c -o libversion_a-version.o `test -f 'version.c' || echo '$(srcdir)/'`version.c + +libversion_a-version.obj: version.c +@am__fastdepCC_TRUE@ $(AM_V_CC)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(libversion_a_CFLAGS) $(CFLAGS) -MT libversion_a-version.obj -MD -MP -MF $(DEPDIR)/libversion_a-version.Tpo -c -o libversion_a-version.obj `if test -f 'version.c'; then $(CYGPATH_W) 'version.c'; else $(CYGPATH_W) '$(srcdir)/version.c'; fi` +@am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) $(DEPDIR)/libversion_a-version.Tpo $(DEPDIR)/libversion_a-version.Po +@AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='version.c' object='libversion_a-version.obj' libtool=no @AMDEPBACKSLASH@ +@AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@ +@am__fastdepCC_FALSE@ $(AM_V_CC@am__nodep@)$(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(libversion_a_CFLAGS) $(CFLAGS) -c -o libversion_a-version.obj `if test -f 'version.c'; then $(CYGPATH_W) 'version.c'; else $(CYGPATH_W) '$(srcdir)/version.c'; fi` +install-man1: $(man1_MANS) + @$(NORMAL_INSTALL) + @list1='$(man1_MANS)'; \ + list2=''; \ + test -n "$(man1dir)" \ + && test -n "`echo $$list1$$list2`" \ + || exit 0; \ + echo " $(MKDIR_P) '$(DESTDIR)$(man1dir)'"; \ + $(MKDIR_P) "$(DESTDIR)$(man1dir)" || exit 1; \ + { for i in $$list1; do echo "$$i"; done; \ + if test -n "$$list2"; then \ + for i in $$list2; do echo "$$i"; done \ + | sed -n '/\.1[a-z]*$$/p'; \ + fi; \ + } | while read p; do \ + if test -f $$p; then d=; else d="$(srcdir)/"; fi; \ + echo "$$d$$p"; echo "$$p"; \ + done | \ + sed -e 'n;s,.*/,,;p;h;s,.*\.,,;s,^[^1][0-9a-z]*$$,1,;x' \ + -e 's,\.[0-9a-z]*$$,,;$(transform);G;s,\n,.,' | \ + sed 'N;N;s,\n, ,g' | { \ + list=; while read file base inst; do \ + if test "$$base" = "$$inst"; then list="$$list $$file"; else \ + echo " $(INSTALL_DATA) '$$file' '$(DESTDIR)$(man1dir)/$$inst'"; \ + $(INSTALL_DATA) "$$file" "$(DESTDIR)$(man1dir)/$$inst" || exit $$?; \ + fi; \ + done; \ + for i in $$list; do echo "$$i"; done | $(am__base_list) | \ + while read files; do \ + test -z "$$files" || { \ + echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(man1dir)'"; \ + $(INSTALL_DATA) $$files "$(DESTDIR)$(man1dir)" || exit $$?; }; \ + done; } + +uninstall-man1: + @$(NORMAL_UNINSTALL) + @list='$(man1_MANS)'; test -n "$(man1dir)" || exit 0; \ + files=`{ for i in $$list; do echo "$$i"; done; \ + } | sed -e 's,.*/,,;h;s,.*\.,,;s,^[^1][0-9a-z]*$$,1,;x' \ + -e 's,\.[0-9a-z]*$$,,;$(transform);G;s,\n,.,'`; \ + dir='$(DESTDIR)$(man1dir)'; $(am__uninstall_files_from_dir) + +ID: $(am__tagged_files) + $(am__define_uniq_tagged_files); mkid -fID $$unique +tags: tags-am +TAGS: tags + +tags-am: $(TAGS_DEPENDENCIES) $(am__tagged_files) + set x; \ + here=`pwd`; \ + $(am__define_uniq_tagged_files); \ + shift; \ + if test -z "$(ETAGS_ARGS)$$*$$unique"; then :; else \ + test -n "$$unique" || unique=$$empty_fix; \ + if test $$# -gt 0; then \ + $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \ + "$$@" $$unique; \ + else \ + $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \ + $$unique; \ + fi; \ + fi +ctags: ctags-am + +CTAGS: ctags +ctags-am: $(TAGS_DEPENDENCIES) $(am__tagged_files) + $(am__define_uniq_tagged_files); \ + test -z "$(CTAGS_ARGS)$$unique" \ + || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \ + $$unique + +GTAGS: + here=`$(am__cd) $(top_builddir) && pwd` \ + && $(am__cd) $(top_srcdir) \ + && gtags -i $(GTAGS_ARGS) "$$here" +cscope: cscope.files + test ! -s cscope.files \ + || $(CSCOPE) -b -q $(AM_CSCOPEFLAGS) $(CSCOPEFLAGS) -i cscope.files $(CSCOPE_ARGS) +clean-cscope: + -rm -f cscope.files +cscope.files: clean-cscope cscopelist +cscopelist: cscopelist-am + +cscopelist-am: $(am__tagged_files) + list='$(am__tagged_files)'; \ + case "$(srcdir)" in \ + [\\/]* | ?:[\\/]*) sdir="$(srcdir)" ;; \ + *) sdir=$(subdir)/$(srcdir) ;; \ + esac; \ + for i in $$list; do \ + if test -f "$$i"; then \ + echo "$(subdir)/$$i"; \ + else \ + echo "$$sdir/$$i"; \ + fi; \ + done >> $(top_builddir)/cscope.files + +distclean-tags: + -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags + -rm -f cscope.out cscope.in.out cscope.po.out cscope.files + +distdir: $(DISTFILES) + $(am__remove_distdir) + test -d "$(distdir)" || mkdir "$(distdir)" + @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + list='$(DISTFILES)'; \ + dist_files=`for file in $$list; do echo $$file; done | \ + sed -e "s|^$$srcdirstrip/||;t" \ + -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \ + case $$dist_files in \ + */*) $(MKDIR_P) `echo "$$dist_files" | \ + sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \ + sort -u` ;; \ + esac; \ + for file in $$dist_files; do \ + if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ + if test -d $$d/$$file; then \ + dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test -d "$(distdir)/$$file"; then \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ + if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ + cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ + cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \ + else \ + test -f "$(distdir)/$$file" \ + || cp -p $$d/$$file "$(distdir)/$$file" \ + || exit 1; \ + fi; \ + done + -test -n "$(am__skip_mode_fix)" \ + || find "$(distdir)" -type d ! -perm -755 \ + -exec chmod u+rwx,go+rx {} \; -o \ + ! -type d ! -perm -444 -links 1 -exec chmod a+r {} \; -o \ + ! -type d ! -perm -400 -exec chmod a+r {} \; -o \ + ! -type d ! -perm -444 -exec $(install_sh) -c -m a+r {} {} \; \ + || chmod -R a+r "$(distdir)" +dist-gzip: distdir + tardir=$(distdir) && $(am__tar) | eval GZIP= gzip $(GZIP_ENV) -c >$(distdir).tar.gz + $(am__post_remove_distdir) + +dist-bzip2: distdir + tardir=$(distdir) && $(am__tar) | BZIP2=$${BZIP2--9} bzip2 -c >$(distdir).tar.bz2 + $(am__post_remove_distdir) + +dist-lzip: distdir + tardir=$(distdir) && $(am__tar) | lzip -c $${LZIP_OPT--9} >$(distdir).tar.lz + $(am__post_remove_distdir) + +dist-xz: distdir + tardir=$(distdir) && $(am__tar) | XZ_OPT=$${XZ_OPT--e} xz -c >$(distdir).tar.xz + $(am__post_remove_distdir) + +dist-tarZ: distdir + @echo WARNING: "Support for distribution archives compressed with" \ + "legacy program 'compress' is deprecated." >&2 + @echo WARNING: "It will be removed altogether in Automake 2.0" >&2 + tardir=$(distdir) && $(am__tar) | compress -c >$(distdir).tar.Z + $(am__post_remove_distdir) + +dist-shar: distdir + @echo WARNING: "Support for shar distribution archives is" \ + "deprecated." >&2 + @echo WARNING: "It will be removed altogether in Automake 2.0" >&2 + shar $(distdir) | eval GZIP= gzip $(GZIP_ENV) -c >$(distdir).shar.gz + $(am__post_remove_distdir) + +dist-zip: distdir + -rm -f $(distdir).zip + zip -rq $(distdir).zip $(distdir) + $(am__post_remove_distdir) + +dist dist-all: + $(MAKE) $(AM_MAKEFLAGS) $(DIST_TARGETS) am__post_remove_distdir='@:' + $(am__post_remove_distdir) + +# This target untars the dist file and tries a VPATH configuration. Then +# it guarantees that the distribution is self-contained by making another +# tarfile. +distcheck: dist + case '$(DIST_ARCHIVES)' in \ + *.tar.gz*) \ + eval GZIP= gzip $(GZIP_ENV) -dc $(distdir).tar.gz | $(am__untar) ;;\ + *.tar.bz2*) \ + bzip2 -dc $(distdir).tar.bz2 | $(am__untar) ;;\ + *.tar.lz*) \ + lzip -dc $(distdir).tar.lz | $(am__untar) ;;\ + *.tar.xz*) \ + xz -dc $(distdir).tar.xz | $(am__untar) ;;\ + *.tar.Z*) \ + uncompress -c $(distdir).tar.Z | $(am__untar) ;;\ + *.shar.gz*) \ + eval GZIP= gzip $(GZIP_ENV) -dc $(distdir).shar.gz | unshar ;;\ + *.zip*) \ + unzip $(distdir).zip ;;\ + esac + chmod -R a-w $(distdir) + chmod u+w $(distdir) + mkdir $(distdir)/_build $(distdir)/_build/sub $(distdir)/_inst + chmod a-w $(distdir) + test -d $(distdir)/_build || exit 0; \ + dc_install_base=`$(am__cd) $(distdir)/_inst && pwd | sed -e 's,^[^:\\/]:[\\/],/,'` \ + && dc_destdir="$${TMPDIR-/tmp}/am-dc-$$$$/" \ + && am__cwd=`pwd` \ + && $(am__cd) $(distdir)/_build/sub \ + && ../../configure \ + $(AM_DISTCHECK_CONFIGURE_FLAGS) \ + $(DISTCHECK_CONFIGURE_FLAGS) \ + --srcdir=../.. --prefix="$$dc_install_base" \ + && $(MAKE) $(AM_MAKEFLAGS) \ + && $(MAKE) $(AM_MAKEFLAGS) dvi \ + && $(MAKE) $(AM_MAKEFLAGS) check \ + && $(MAKE) $(AM_MAKEFLAGS) install \ + && $(MAKE) $(AM_MAKEFLAGS) installcheck \ + && $(MAKE) $(AM_MAKEFLAGS) uninstall \ + && $(MAKE) $(AM_MAKEFLAGS) distuninstallcheck_dir="$$dc_install_base" \ + distuninstallcheck \ + && chmod -R a-w "$$dc_install_base" \ + && ({ \ + (cd ../.. && umask 077 && mkdir "$$dc_destdir") \ + && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" install \ + && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" uninstall \ + && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" \ + distuninstallcheck_dir="$$dc_destdir" distuninstallcheck; \ + } || { rm -rf "$$dc_destdir"; exit 1; }) \ + && rm -rf "$$dc_destdir" \ + && $(MAKE) $(AM_MAKEFLAGS) dist \ + && rm -rf $(DIST_ARCHIVES) \ + && $(MAKE) $(AM_MAKEFLAGS) distcleancheck \ + && cd "$$am__cwd" \ + || exit 1 + $(am__post_remove_distdir) + @(echo "$(distdir) archives ready for distribution: "; \ + list='$(DIST_ARCHIVES)'; for i in $$list; do echo $$i; done) | \ + sed -e 1h -e 1s/./=/g -e 1p -e 1x -e '$$p' -e '$$x' +distuninstallcheck: + @test -n '$(distuninstallcheck_dir)' || { \ + echo 'ERROR: trying to run $@ with an empty' \ + '$$(distuninstallcheck_dir)' >&2; \ + exit 1; \ + }; \ + $(am__cd) '$(distuninstallcheck_dir)' || { \ + echo 'ERROR: cannot chdir into $(distuninstallcheck_dir)' >&2; \ + exit 1; \ + }; \ + test `$(am__distuninstallcheck_listfiles) | wc -l` -eq 0 \ + || { echo "ERROR: files left after uninstall:" ; \ + if test -n "$(DESTDIR)"; then \ + echo " (check DESTDIR support)"; \ + fi ; \ + $(distuninstallcheck_listfiles) ; \ + exit 1; } >&2 +distcleancheck: distclean + @if test '$(srcdir)' = . ; then \ + echo "ERROR: distcleancheck can only run from a VPATH build" ; \ + exit 1 ; \ + fi + @test `$(distcleancheck_listfiles) | wc -l` -eq 0 \ + || { echo "ERROR: files left in build directory after distclean:" ; \ + $(distcleancheck_listfiles) ; \ + exit 1; } >&2 +check-am: all-am + $(MAKE) $(AM_MAKEFLAGS) check-local +check: $(BUILT_SOURCES) + $(MAKE) $(AM_MAKEFLAGS) check-am +all-am: Makefile $(LIBRARIES) $(PROGRAMS) $(SCRIPTS) $(MANS) \ + uxconfig.h +installdirs: + for dir in "$(DESTDIR)$(bindir)" "$(DESTDIR)$(man1dir)"; do \ + test -z "$$dir" || $(MKDIR_P) "$$dir"; \ + done +install: $(BUILT_SOURCES) + $(MAKE) $(AM_MAKEFLAGS) install-am +install-exec: install-exec-am +install-data: install-data-am +uninstall: uninstall-am + +install-am: all-am + @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am + +installcheck: installcheck-am +install-strip: + if test -z '$(STRIP)'; then \ + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + install; \ + else \ + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'" install; \ + fi +mostlyclean-generic: + +clean-generic: + -test -z "$(CLEANFILES)" || rm -f $(CLEANFILES) + +distclean-generic: + -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) + -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES) + -rm -f charset/$(DEPDIR)/$(am__dirstamp) + -rm -f charset/$(am__dirstamp) + -rm -f unix/$(DEPDIR)/$(am__dirstamp) + -rm -f unix/$(am__dirstamp) + +maintainer-clean-generic: + @echo "This command is intended for maintainers to use" + @echo "it deletes files that may require special tools to rebuild." + -test -z "$(BUILT_SOURCES)" || rm -f $(BUILT_SOURCES) +@HAVE_SETID_CMD_FALSE@install-exec-local: +clean: clean-am + +clean-am: clean-binPROGRAMS clean-generic clean-noinstLIBRARIES \ + clean-noinstPROGRAMS mostlyclean-am + +distclean: distclean-am + -rm -f $(am__CONFIG_DISTCLEAN_FILES) + -rm -rf ./$(DEPDIR) charset/$(DEPDIR) unix/$(DEPDIR) + -rm -f Makefile +distclean-am: clean-am distclean-compile distclean-generic \ + distclean-hdr distclean-tags + +dvi: dvi-am + +dvi-am: + +html: html-am + +html-am: + +info: info-am + +info-am: + +install-data-am: install-man + +install-dvi: install-dvi-am + +install-dvi-am: + +install-exec-am: install-binPROGRAMS install-exec-local + +install-html: install-html-am + +install-html-am: + +install-info: install-info-am + +install-info-am: + +install-man: install-man1 + +install-pdf: install-pdf-am + +install-pdf-am: + +install-ps: install-ps-am + +install-ps-am: + +installcheck-am: + +maintainer-clean: maintainer-clean-am + -rm -f $(am__CONFIG_DISTCLEAN_FILES) + -rm -rf $(top_srcdir)/autom4te.cache + -rm -rf ./$(DEPDIR) charset/$(DEPDIR) unix/$(DEPDIR) + -rm -f Makefile +maintainer-clean-am: distclean-am maintainer-clean-generic + +mostlyclean: mostlyclean-am + +mostlyclean-am: mostlyclean-compile mostlyclean-generic + +pdf: pdf-am + +pdf-am: + +ps: ps-am + +ps-am: + +uninstall-am: uninstall-binPROGRAMS uninstall-man + +uninstall-man: uninstall-man1 + +.MAKE: all check check-am install install-am install-strip + +.PHONY: CTAGS GTAGS TAGS all all-am am--refresh check check-am \ + check-local clean clean-binPROGRAMS clean-cscope clean-generic \ + clean-noinstLIBRARIES clean-noinstPROGRAMS cscope \ + cscopelist-am ctags ctags-am dist dist-all dist-bzip2 \ + dist-gzip dist-lzip dist-shar dist-tarZ dist-xz dist-zip \ + distcheck distclean distclean-compile distclean-generic \ + distclean-hdr distclean-tags distcleancheck distdir \ + distuninstallcheck dvi dvi-am html html-am info info-am \ + install install-am install-binPROGRAMS install-data \ + install-data-am install-dvi install-dvi-am install-exec \ + install-exec-am install-exec-local install-html \ + install-html-am install-info install-info-am install-man \ + install-man1 install-pdf install-pdf-am install-ps \ + install-ps-am install-strip installcheck installcheck-am \ + installdirs maintainer-clean maintainer-clean-generic \ + mostlyclean mostlyclean-compile mostlyclean-generic pdf pdf-am \ + ps ps-am tags tags-am uninstall uninstall-am \ + uninstall-binPROGRAMS uninstall-man uninstall-man1 + +.PRECIOUS: Makefile + +@AUTO_GIT_COMMIT_TRUE@empty.h: $(allsources) +@AUTO_GIT_COMMIT_TRUE@ echo '/* Empty file touched by automake makefile to force rebuild of version.o */' >$@ + +# Run the cryptsuite tests as part of 'make check'. Override +# PUTTY_TESTCRYPT so that cryptsuite will take the testcrypt binary +# from the build directory instead of the source directory, in case +# this is an out-of-tree build. +check-local: testcrypt + PUTTY_TESTCRYPT=./testcrypt $(srcdir)/test/cryptsuite.py +@HAVE_SETID_CMD_TRUE@install-exec-local: +@HAVE_SETID_CMD_TRUE@ @SETID_CMD@ $(bindir)/pterm +@HAVE_SETID_CMD_TRUE@ chmod @SETID_MODE@ $(bindir)/pterm +@HAVE_QUARTZ_TRUE@unix/PuTTY.app: unix/putty.bundle puttyapp osxlaunch +@HAVE_QUARTZ_TRUE@ rm -rf $@ && PUTTY_GTK_PREFIX_FROM_MAKEFILE=$$(pkg-config --variable=prefix gtk+-3.0) gtk-mac-bundler $< +@HAVE_QUARTZ_TRUE@unix/Pterm.app: unix/pterm.bundle ptermapp osxlaunch +@HAVE_QUARTZ_TRUE@ rm -rf $@ && PUTTY_GTK_PREFIX_FROM_MAKEFILE=$$(pkg-config --variable=prefix gtk+-3.0) gtk-mac-bundler $< + +# Tell versions [3.59,3.63) of GNU make to not export all variables. +# Otherwise a system limit (for SysV at least) may be exceeded. +.NOEXPORT: diff --git a/Recipe b/Recipe index d696b0a..bd2962f 100644 --- a/Recipe +++ b/Recipe @@ -239,7 +239,7 @@ CFLAGS += -DWINVER=0x0500 -D_WIN32_WINDOWS=0x0410 -D_WIN32_WINNT=0x0500 CONF = conf marshal # Terminal emulator and its (platform-independent) dependencies. -TERMINAL = terminal stripctrl wcwidth ldiscucs logging tree234 minibidi +TERMINAL = terminal stripctrl wcwidth logging tree234 minibidi + config dialog CONF # GUI front end and terminal emulator (putty, puttytel). @@ -279,7 +279,7 @@ WINSSH = SSH winnoise wincapi winpgntc wingss winshare winnps winnpc UXSSH = SSH uxnoise uxagentc uxgss uxshare # SFTP implementation (pscp, psftp). -SFTP = sftp sftpcommon logging cmdline +SFTP = psftpcommon sftp sftpcommon logging cmdline # Miscellaneous objects appearing in all the utilities, or all the # network ones, or the Unix or Windows subsets of those in turn. @@ -365,7 +365,7 @@ PUTTYGEN_UNIX = sshrsag sshdssg sshprime sshdes ARITH sshmd5 version sshprng + sshrand uxnoise sshsha MISC sshrsa sshdss uxcons uxstore uxmisc + sshpubk sshaes sshsh256 sshsh512 IMPORT puttygen.res time tree234 + uxgen notiming CONF sshecc sshecdsag uxnogtk sshauxcrypt sshhmac - + uxpoll + + uxpoll uxutils puttygen : [U] cmdgen PUTTYGEN_UNIX cgtest : [UT] cgtest PUTTYGEN_UNIX @@ -376,7 +376,7 @@ pageant : [X] uxpgnt uxagentc aqsync pageant sshrsa sshpubk sshdes ARITH + sshmd5 version tree234 misc sshaes sshsha sshdss sshsh256 sshsh512 + sshecc CONF uxsignal nocproxy nogss be_none x11fwd ux_x11 uxcons + gtkask gtkmisc nullplug logging UXMISC uxagentsock utils memory - + sshauxcrypt sshhmac + + sshauxcrypt sshhmac sshprng uxnoise ptermapp : [XT] GTKTERM uxmisc misc ldisc settings uxpty uxsel BE_NONE uxstore + uxsignal CHARSET uxpterm version time xpmpterm xpmptcfg @@ -397,7 +397,7 @@ testsc : [UT] testsc SSHCRYPTO marshal utils memory tree234 wildcard testzlib : [UT] testzlib sshzlib utils marshal memory uppity : [UT] uxserver SSHSERVER UXMISC uxsignal uxnoise uxgss uxnogtk - + uxpty uxsftpserver ux_x11 uxagentsock + + uxpty uxsftpserver ux_x11 uxagentsock procnet # ---------------------------------------------------------------------- # On Windows, provide a means of removing local test binaries that we diff --git a/aclocal.m4 b/aclocal.m4 new file mode 100644 index 0000000..598c657 --- /dev/null +++ b/aclocal.m4 @@ -0,0 +1,1885 @@ +# generated automatically by aclocal 1.15.1 -*- Autoconf -*- + +# Copyright (C) 1996-2017 Free Software Foundation, Inc. + +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY, to the extent permitted by law; without +# even the implied warranty of MERCHANTABILITY or FITNESS FOR A +# PARTICULAR PURPOSE. + +m4_ifndef([AC_CONFIG_MACRO_DIRS], [m4_defun([_AM_CONFIG_MACRO_DIRS], [])m4_defun([AC_CONFIG_MACRO_DIRS], [_AM_CONFIG_MACRO_DIRS($@)])]) +m4_ifndef([AC_AUTOCONF_VERSION], + [m4_copy([m4_PACKAGE_VERSION], [AC_AUTOCONF_VERSION])])dnl +m4_if(m4_defn([AC_AUTOCONF_VERSION]), [2.69],, +[m4_warning([this file was generated for autoconf 2.69. +You have another version of autoconf. It may work, but is not guaranteed to. +If you have problems, you may need to regenerate the build system entirely. +To do so, use the procedure documented by the package, typically 'autoreconf'.])]) + +# Configure paths for GTK+ +# Owen Taylor 1997-2001 + +dnl AM_PATH_GTK_2_0([MINIMUM-VERSION, [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND [, MODULES]]]]) +dnl Test for GTK+, and define GTK_CFLAGS and GTK_LIBS, if gthread is specified in MODULES, +dnl pass to pkg-config +dnl +AC_DEFUN([AM_PATH_GTK_2_0], +[dnl +dnl Get the cflags and libraries from pkg-config +dnl +AC_ARG_ENABLE(gtktest, [ --disable-gtktest do not try to compile and run a test GTK+ program], + , enable_gtktest=yes) + + pkg_config_args=gtk+-2.0 + for module in . $4 + do + case "$module" in + gthread) + pkg_config_args="$pkg_config_args gthread-2.0" + ;; + esac + done + + no_gtk="" + + AC_REQUIRE([PKG_PROG_PKG_CONFIG]) + PKG_PROG_PKG_CONFIG([0.7]) + + min_gtk_version=ifelse([$1], ,2.0.0,$1) + AC_MSG_CHECKING(for GTK+ - version >= $min_gtk_version) + + if test x$PKG_CONFIG != xno ; then + ## don't try to run the test against uninstalled libtool libs + if $PKG_CONFIG --uninstalled $pkg_config_args; then + echo "Will use uninstalled version of GTK+ found in PKG_CONFIG_PATH" + enable_gtktest=no + fi + + if $PKG_CONFIG --atleast-version $min_gtk_version $pkg_config_args; then + : + else + no_gtk=yes + fi + fi + + if test x"$no_gtk" = x ; then + GTK_CFLAGS=`$PKG_CONFIG $pkg_config_args --cflags` + GTK_LIBS=`$PKG_CONFIG $pkg_config_args --libs` + gtk_config_major_version=`$PKG_CONFIG --modversion gtk+-2.0 | \ + sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\1/'` + gtk_config_minor_version=`$PKG_CONFIG --modversion gtk+-2.0 | \ + sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\2/'` + gtk_config_micro_version=`$PKG_CONFIG --modversion gtk+-2.0 | \ + sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\3/'` + if test "x$enable_gtktest" = "xyes" ; then + ac_save_CFLAGS="$CFLAGS" + ac_save_LIBS="$LIBS" + CFLAGS="$CFLAGS $GTK_CFLAGS" + LIBS="$GTK_LIBS $LIBS" +dnl +dnl Now check if the installed GTK+ is sufficiently new. (Also sanity +dnl checks the results of pkg-config to some extent) +dnl + rm -f conf.gtktest + AC_TRY_RUN([ +#include +#include +#include + +int +main () +{ + int major, minor, micro; + char *tmp_version; + + fclose (fopen ("conf.gtktest", "w")); + + /* HP/UX 9 (%@#!) writes to sscanf strings */ + tmp_version = g_strdup("$min_gtk_version"); + if (sscanf(tmp_version, "%d.%d.%d", &major, &minor, µ) != 3) { + printf("%s, bad version string\n", "$min_gtk_version"); + exit(1); + } + + if ((gtk_major_version != $gtk_config_major_version) || + (gtk_minor_version != $gtk_config_minor_version) || + (gtk_micro_version != $gtk_config_micro_version)) + { + printf("\n*** 'pkg-config --modversion gtk+-2.0' returned %d.%d.%d, but GTK+ (%d.%d.%d)\n", + $gtk_config_major_version, $gtk_config_minor_version, $gtk_config_micro_version, + gtk_major_version, gtk_minor_version, gtk_micro_version); + printf ("*** was found! If pkg-config was correct, then it is best\n"); + printf ("*** to remove the old version of GTK+. You may also be able to fix the error\n"); + printf("*** by modifying your LD_LIBRARY_PATH enviroment variable, or by editing\n"); + printf("*** /etc/ld.so.conf. Make sure you have run ldconfig if that is\n"); + printf("*** required on your system.\n"); + printf("*** If pkg-config was wrong, set the environment variable PKG_CONFIG_PATH\n"); + printf("*** to point to the correct configuration files\n"); + } + else if ((gtk_major_version != GTK_MAJOR_VERSION) || + (gtk_minor_version != GTK_MINOR_VERSION) || + (gtk_micro_version != GTK_MICRO_VERSION)) + { + printf("*** GTK+ header files (version %d.%d.%d) do not match\n", + GTK_MAJOR_VERSION, GTK_MINOR_VERSION, GTK_MICRO_VERSION); + printf("*** library (version %d.%d.%d)\n", + gtk_major_version, gtk_minor_version, gtk_micro_version); + } + else + { + if ((gtk_major_version > major) || + ((gtk_major_version == major) && (gtk_minor_version > minor)) || + ((gtk_major_version == major) && (gtk_minor_version == minor) && (gtk_micro_version >= micro))) + { + return 0; + } + else + { + printf("\n*** An old version of GTK+ (%d.%d.%d) was found.\n", + gtk_major_version, gtk_minor_version, gtk_micro_version); + printf("*** You need a version of GTK+ newer than %d.%d.%d. The latest version of\n", + major, minor, micro); + printf("*** GTK+ is always available from ftp://ftp.gtk.org.\n"); + printf("***\n"); + printf("*** If you have already installed a sufficiently new version, this error\n"); + printf("*** probably means that the wrong copy of the pkg-config shell script is\n"); + printf("*** being found. The easiest way to fix this is to remove the old version\n"); + printf("*** of GTK+, but you can also set the PKG_CONFIG environment to point to the\n"); + printf("*** correct copy of pkg-config. (In this case, you will have to\n"); + printf("*** modify your LD_LIBRARY_PATH enviroment variable, or edit /etc/ld.so.conf\n"); + printf("*** so that the correct libraries are found at run-time))\n"); + } + } + return 1; +} +],, no_gtk=yes,[echo $ac_n "cross compiling; assumed OK... $ac_c"]) + CFLAGS="$ac_save_CFLAGS" + LIBS="$ac_save_LIBS" + fi + fi + if test "x$no_gtk" = x ; then + AC_MSG_RESULT(yes (version $gtk_config_major_version.$gtk_config_minor_version.$gtk_config_micro_version)) + ifelse([$2], , :, [$2]) + else + AC_MSG_RESULT(no) + if test "$PKG_CONFIG" = "no" ; then + echo "*** A new enough version of pkg-config was not found." + echo "*** See http://pkgconfig.sourceforge.net" + else + if test -f conf.gtktest ; then + : + else + echo "*** Could not run GTK+ test program, checking why..." + ac_save_CFLAGS="$CFLAGS" + ac_save_LIBS="$LIBS" + CFLAGS="$CFLAGS $GTK_CFLAGS" + LIBS="$LIBS $GTK_LIBS" + AC_TRY_LINK([ +#include +#include +], [ return ((gtk_major_version) || (gtk_minor_version) || (gtk_micro_version)); ], + [ echo "*** The test program compiled, but did not run. This usually means" + echo "*** that the run-time linker is not finding GTK+ or finding the wrong" + echo "*** version of GTK+. If it is not finding GTK+, you'll need to set your" + echo "*** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point" + echo "*** to the installed location Also, make sure you have run ldconfig if that" + echo "*** is required on your system" + echo "***" + echo "*** If you have an old version installed, it is best to remove it, although" + echo "*** you may also be able to get things to work by modifying LD_LIBRARY_PATH" ], + [ echo "*** The test program failed to compile or link. See the file config.log for the" + echo "*** exact error that occured. This usually means GTK+ is incorrectly installed."]) + CFLAGS="$ac_save_CFLAGS" + LIBS="$ac_save_LIBS" + fi + fi + GTK_CFLAGS="" + GTK_LIBS="" + ifelse([$3], , :, [$3]) + fi + AC_SUBST(GTK_CFLAGS) + AC_SUBST(GTK_LIBS) + rm -f conf.gtktest +]) + +# Configure paths for GTK+ +# Owen Taylor 1997-2001 + +dnl AM_PATH_GTK_3_0([MINIMUM-VERSION, [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND [, MODULES]]]]) +dnl Test for GTK+, and define GTK_CFLAGS and GTK_LIBS, if gthread is specified in MODULES, +dnl pass to pkg-config +dnl +AC_DEFUN([AM_PATH_GTK_3_0], +[m4_warn([obsolete], [AM_PATH_GTK_3_0 is deprecated, use PKG_CHECK_MODULES([GTK], [gtk+-3.0]) instead]) +dnl Get the cflags and libraries from pkg-config +dnl +AC_ARG_ENABLE(gtktest, [ --disable-gtktest do not try to compile and run a test GTK+ program], + , enable_gtktest=yes) + min_gtk_version=ifelse([$1], [], [3.0.0], [$1]) + + pkg_config_args="gtk+-3.0 >= $min_gtk_version" + for module in . $4 + do + case "$module" in + gthread) + pkg_config_args="$pkg_config_args gthread-2.0" + ;; + esac + done + + no_gtk="" + + PKG_PROG_PKG_CONFIG([0.16]) + + if test -z "$PKG_CONFIG"; then + no_gtk=yes + fi + + AC_MSG_CHECKING(for GTK+ - version >= $min_gtk_version) + + if test -n "$PKG_CONFIG"; then + ## don't try to run the test against uninstalled libtool libs + if $PKG_CONFIG --uninstalled $pkg_config_args; then + echo "Will use uninstalled version of GTK+ found in PKG_CONFIG_PATH" + enable_gtktest=no + fi + + if $PKG_CONFIG $pkg_config_args; then + : + else + no_gtk=yes + fi + fi + + if test x"$no_gtk" = x ; then + GTK_CFLAGS=`$PKG_CONFIG $pkg_config_args --cflags` + GTK_LIBS=`$PKG_CONFIG $pkg_config_args --libs` + gtk_config_major_version=`$PKG_CONFIG --modversion gtk+-3.0 | \ + sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\1/'` + gtk_config_minor_version=`$PKG_CONFIG --modversion gtk+-3.0 | \ + sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\2/'` + gtk_config_micro_version=`$PKG_CONFIG --modversion gtk+-3.0 | \ + sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\3/'` + if test "x$enable_gtktest" = "xyes" ; then + ac_save_CFLAGS="$CFLAGS" + ac_save_LIBS="$LIBS" + CFLAGS="$CFLAGS $GTK_CFLAGS" + LIBS="$GTK_LIBS $LIBS" +dnl +dnl Now check if the installed GTK+ is sufficiently new. (Also sanity +dnl checks the results of pkg-config to some extent) +dnl + rm -f conf.gtktest + AC_TRY_RUN([ +#include +#include +#include + +int +main () +{ + unsigned int major, minor, micro; + + fclose (fopen ("conf.gtktest", "w")); + + if (sscanf("$min_gtk_version", "%u.%u.%u", &major, &minor, µ) != 3) { + printf("%s, bad version string\n", "$min_gtk_version"); + exit(1); + } + + if ((gtk_major_version != $gtk_config_major_version) || + (gtk_minor_version != $gtk_config_minor_version) || + (gtk_micro_version != $gtk_config_micro_version)) + { + printf("\n*** 'pkg-config --modversion gtk+-3.0' returned %d.%d.%d, but GTK+ (%d.%d.%d)\n", + $gtk_config_major_version, $gtk_config_minor_version, $gtk_config_micro_version, + gtk_major_version, gtk_minor_version, gtk_micro_version); + printf ("*** was found! If pkg-config was correct, then it is best\n"); + printf ("*** to remove the old version of GTK+. You may also be able to fix the error\n"); + printf("*** by modifying your LD_LIBRARY_PATH enviroment variable, or by editing\n"); + printf("*** /etc/ld.so.conf. Make sure you have run ldconfig if that is\n"); + printf("*** required on your system.\n"); + printf("*** If pkg-config was wrong, set the environment variable PKG_CONFIG_PATH\n"); + printf("*** to point to the correct configuration files\n"); + } + else if ((gtk_major_version != GTK_MAJOR_VERSION) || + (gtk_minor_version != GTK_MINOR_VERSION) || + (gtk_micro_version != GTK_MICRO_VERSION)) + { + printf("*** GTK+ header files (version %d.%d.%d) do not match\n", + GTK_MAJOR_VERSION, GTK_MINOR_VERSION, GTK_MICRO_VERSION); + printf("*** library (version %d.%d.%d)\n", + gtk_major_version, gtk_minor_version, gtk_micro_version); + } + else + { + if ((gtk_major_version > major) || + ((gtk_major_version == major) && (gtk_minor_version > minor)) || + ((gtk_major_version == major) && (gtk_minor_version == minor) && (gtk_micro_version >= micro))) + { + return 0; + } + else + { + printf("\n*** An old version of GTK+ (%u.%u.%u) was found.\n", + gtk_major_version, gtk_minor_version, gtk_micro_version); + printf("*** You need a version of GTK+ newer than %u.%u.%u. The latest version of\n", + major, minor, micro); + printf("*** GTK+ is always available from ftp://ftp.gtk.org.\n"); + printf("***\n"); + printf("*** If you have already installed a sufficiently new version, this error\n"); + printf("*** probably means that the wrong copy of the pkg-config shell script is\n"); + printf("*** being found. The easiest way to fix this is to remove the old version\n"); + printf("*** of GTK+, but you can also set the PKG_CONFIG environment to point to the\n"); + printf("*** correct copy of pkg-config. (In this case, you will have to\n"); + printf("*** modify your LD_LIBRARY_PATH enviroment variable, or edit /etc/ld.so.conf\n"); + printf("*** so that the correct libraries are found at run-time))\n"); + } + } + return 1; +} +],, no_gtk=yes,[echo $ac_n "cross compiling; assumed OK... $ac_c"]) + CFLAGS="$ac_save_CFLAGS" + LIBS="$ac_save_LIBS" + fi + fi + if test "x$no_gtk" = x ; then + AC_MSG_RESULT(yes (version $gtk_config_major_version.$gtk_config_minor_version.$gtk_config_micro_version)) + ifelse([$2], , :, [$2]) + else + AC_MSG_RESULT(no) + if test -z "$PKG_CONFIG"; then + echo "*** A new enough version of pkg-config was not found." + echo "*** See http://pkgconfig.sourceforge.net" + else + if test -f conf.gtktest ; then + : + else + echo "*** Could not run GTK+ test program, checking why..." + ac_save_CFLAGS="$CFLAGS" + ac_save_LIBS="$LIBS" + CFLAGS="$CFLAGS $GTK_CFLAGS" + LIBS="$LIBS $GTK_LIBS" + AC_TRY_LINK([ +#include +#include +], [ return ((gtk_major_version) || (gtk_minor_version) || (gtk_micro_version)); ], + [ echo "*** The test program compiled, but did not run. This usually means" + echo "*** that the run-time linker is not finding GTK+ or finding the wrong" + echo "*** version of GTK+. If it is not finding GTK+, you'll need to set your" + echo "*** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point" + echo "*** to the installed location Also, make sure you have run ldconfig if that" + echo "*** is required on your system" + echo "***" + echo "*** If you have an old version installed, it is best to remove it, although" + echo "*** you may also be able to get things to work by modifying LD_LIBRARY_PATH" ], + [ echo "*** The test program failed to compile or link. See the file config.log for the" + echo "*** exact error that occurred. This usually means GTK+ is incorrectly installed."]) + CFLAGS="$ac_save_CFLAGS" + LIBS="$ac_save_LIBS" + fi + fi + GTK_CFLAGS="" + GTK_LIBS="" + ifelse([$3], , :, [$3]) + fi + AC_SUBST(GTK_CFLAGS) + AC_SUBST(GTK_LIBS) + rm -f conf.gtktest +]) + +dnl GTK_CHECK_BACKEND(BACKEND-NAME [, MINIMUM-VERSION [, ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND]]]) +dnl Tests for BACKEND-NAME in the GTK targets list +dnl +AC_DEFUN([GTK_CHECK_BACKEND], +[m4_warn([obsolete], [GTK_CHECK_BACKEND is deprecated, use PKG_CHECK_MODULES([GTK_X11], [gtk+-x11-3.0]) or similar instead]) + pkg_config_args=ifelse([$1],,gtk+-3.0, gtk+-$1-3.0) + min_gtk_version=ifelse([$2],,3.0.0,$2) + pkg_config_args="$pkg_config_args >= $min_gtk_version" + + PKG_PROG_PKG_CONFIG([0.16]) + AS_IF([test -z "$PKG_CONFIG"], [AC_MSG_ERROR([No pkg-config found])]) + + if $PKG_CONFIG $pkg_config_args ; then + target_found=yes + else + target_found=no + fi + + if test "x$target_found" = "xno"; then + ifelse([$4],,[AC_MSG_ERROR([Backend $backend not found.])],[$4]) + else + ifelse([$3],,[:],[$3]) + fi +]) + +dnl pkg.m4 - Macros to locate and utilise pkg-config. -*- Autoconf -*- +dnl serial 11 (pkg-config-0.29.1) +dnl +dnl Copyright © 2004 Scott James Remnant . +dnl Copyright © 2012-2015 Dan Nicholson +dnl +dnl This program is free software; you can redistribute it and/or modify +dnl it under the terms of the GNU General Public License as published by +dnl the Free Software Foundation; either version 2 of the License, or +dnl (at your option) any later version. +dnl +dnl This program is distributed in the hope that it will be useful, but +dnl WITHOUT ANY WARRANTY; without even the implied warranty of +dnl MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU +dnl General Public License for more details. +dnl +dnl You should have received a copy of the GNU General Public License +dnl along with this program; if not, write to the Free Software +dnl Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA +dnl 02111-1307, USA. +dnl +dnl As a special exception to the GNU General Public License, if you +dnl distribute this file as part of a program that contains a +dnl configuration script generated by Autoconf, you may include it under +dnl the same distribution terms that you use for the rest of that +dnl program. + +dnl PKG_PREREQ(MIN-VERSION) +dnl ----------------------- +dnl Since: 0.29 +dnl +dnl Verify that the version of the pkg-config macros are at least +dnl MIN-VERSION. Unlike PKG_PROG_PKG_CONFIG, which checks the user's +dnl installed version of pkg-config, this checks the developer's version +dnl of pkg.m4 when generating configure. +dnl +dnl To ensure that this macro is defined, also add: +dnl m4_ifndef([PKG_PREREQ], +dnl [m4_fatal([must install pkg-config 0.29 or later before running autoconf/autogen])]) +dnl +dnl See the "Since" comment for each macro you use to see what version +dnl of the macros you require. +m4_defun([PKG_PREREQ], +[m4_define([PKG_MACROS_VERSION], [0.29.1]) +m4_if(m4_version_compare(PKG_MACROS_VERSION, [$1]), -1, + [m4_fatal([pkg.m4 version $1 or higher is required but ]PKG_MACROS_VERSION[ found])]) +])dnl PKG_PREREQ + +dnl PKG_PROG_PKG_CONFIG([MIN-VERSION]) +dnl ---------------------------------- +dnl Since: 0.16 +dnl +dnl Search for the pkg-config tool and set the PKG_CONFIG variable to +dnl first found in the path. Checks that the version of pkg-config found +dnl is at least MIN-VERSION. If MIN-VERSION is not specified, 0.9.0 is +dnl used since that's the first version where most current features of +dnl pkg-config existed. +AC_DEFUN([PKG_PROG_PKG_CONFIG], +[m4_pattern_forbid([^_?PKG_[A-Z_]+$]) +m4_pattern_allow([^PKG_CONFIG(_(PATH|LIBDIR|SYSROOT_DIR|ALLOW_SYSTEM_(CFLAGS|LIBS)))?$]) +m4_pattern_allow([^PKG_CONFIG_(DISABLE_UNINSTALLED|TOP_BUILD_DIR|DEBUG_SPEW)$]) +AC_ARG_VAR([PKG_CONFIG], [path to pkg-config utility]) +AC_ARG_VAR([PKG_CONFIG_PATH], [directories to add to pkg-config's search path]) +AC_ARG_VAR([PKG_CONFIG_LIBDIR], [path overriding pkg-config's built-in search path]) + +if test "x$ac_cv_env_PKG_CONFIG_set" != "xset"; then + AC_PATH_TOOL([PKG_CONFIG], [pkg-config]) +fi +if test -n "$PKG_CONFIG"; then + _pkg_min_version=m4_default([$1], [0.9.0]) + AC_MSG_CHECKING([pkg-config is at least version $_pkg_min_version]) + if $PKG_CONFIG --atleast-pkgconfig-version $_pkg_min_version; then + AC_MSG_RESULT([yes]) + else + AC_MSG_RESULT([no]) + PKG_CONFIG="" + fi +fi[]dnl +])dnl PKG_PROG_PKG_CONFIG + +dnl PKG_CHECK_EXISTS(MODULES, [ACTION-IF-FOUND], [ACTION-IF-NOT-FOUND]) +dnl ------------------------------------------------------------------- +dnl Since: 0.18 +dnl +dnl Check to see whether a particular set of modules exists. Similar to +dnl PKG_CHECK_MODULES(), but does not set variables or print errors. +dnl +dnl Please remember that m4 expands AC_REQUIRE([PKG_PROG_PKG_CONFIG]) +dnl only at the first occurence in configure.ac, so if the first place +dnl it's called might be skipped (such as if it is within an "if", you +dnl have to call PKG_CHECK_EXISTS manually +AC_DEFUN([PKG_CHECK_EXISTS], +[AC_REQUIRE([PKG_PROG_PKG_CONFIG])dnl +if test -n "$PKG_CONFIG" && \ + AC_RUN_LOG([$PKG_CONFIG --exists --print-errors "$1"]); then + m4_default([$2], [:]) +m4_ifvaln([$3], [else + $3])dnl +fi]) + +dnl _PKG_CONFIG([VARIABLE], [COMMAND], [MODULES]) +dnl --------------------------------------------- +dnl Internal wrapper calling pkg-config via PKG_CONFIG and setting +dnl pkg_failed based on the result. +m4_define([_PKG_CONFIG], +[if test -n "$$1"; then + pkg_cv_[]$1="$$1" + elif test -n "$PKG_CONFIG"; then + PKG_CHECK_EXISTS([$3], + [pkg_cv_[]$1=`$PKG_CONFIG --[]$2 "$3" 2>/dev/null` + test "x$?" != "x0" && pkg_failed=yes ], + [pkg_failed=yes]) + else + pkg_failed=untried +fi[]dnl +])dnl _PKG_CONFIG + +dnl _PKG_SHORT_ERRORS_SUPPORTED +dnl --------------------------- +dnl Internal check to see if pkg-config supports short errors. +AC_DEFUN([_PKG_SHORT_ERRORS_SUPPORTED], +[AC_REQUIRE([PKG_PROG_PKG_CONFIG]) +if $PKG_CONFIG --atleast-pkgconfig-version 0.20; then + _pkg_short_errors_supported=yes +else + _pkg_short_errors_supported=no +fi[]dnl +])dnl _PKG_SHORT_ERRORS_SUPPORTED + + +dnl PKG_CHECK_MODULES(VARIABLE-PREFIX, MODULES, [ACTION-IF-FOUND], +dnl [ACTION-IF-NOT-FOUND]) +dnl -------------------------------------------------------------- +dnl Since: 0.4.0 +dnl +dnl Note that if there is a possibility the first call to +dnl PKG_CHECK_MODULES might not happen, you should be sure to include an +dnl explicit call to PKG_PROG_PKG_CONFIG in your configure.ac +AC_DEFUN([PKG_CHECK_MODULES], +[AC_REQUIRE([PKG_PROG_PKG_CONFIG])dnl +AC_ARG_VAR([$1][_CFLAGS], [C compiler flags for $1, overriding pkg-config])dnl +AC_ARG_VAR([$1][_LIBS], [linker flags for $1, overriding pkg-config])dnl + +pkg_failed=no +AC_MSG_CHECKING([for $1]) + +_PKG_CONFIG([$1][_CFLAGS], [cflags], [$2]) +_PKG_CONFIG([$1][_LIBS], [libs], [$2]) + +m4_define([_PKG_TEXT], [Alternatively, you may set the environment variables $1[]_CFLAGS +and $1[]_LIBS to avoid the need to call pkg-config. +See the pkg-config man page for more details.]) + +if test $pkg_failed = yes; then + AC_MSG_RESULT([no]) + _PKG_SHORT_ERRORS_SUPPORTED + if test $_pkg_short_errors_supported = yes; then + $1[]_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs "$2" 2>&1` + else + $1[]_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs "$2" 2>&1` + fi + # Put the nasty error message in config.log where it belongs + echo "$$1[]_PKG_ERRORS" >&AS_MESSAGE_LOG_FD + + m4_default([$4], [AC_MSG_ERROR( +[Package requirements ($2) were not met: + +$$1_PKG_ERRORS + +Consider adjusting the PKG_CONFIG_PATH environment variable if you +installed software in a non-standard prefix. + +_PKG_TEXT])[]dnl + ]) +elif test $pkg_failed = untried; then + AC_MSG_RESULT([no]) + m4_default([$4], [AC_MSG_FAILURE( +[The pkg-config script could not be found or is too old. Make sure it +is in your PATH or set the PKG_CONFIG environment variable to the full +path to pkg-config. + +_PKG_TEXT + +To get pkg-config, see .])[]dnl + ]) +else + $1[]_CFLAGS=$pkg_cv_[]$1[]_CFLAGS + $1[]_LIBS=$pkg_cv_[]$1[]_LIBS + AC_MSG_RESULT([yes]) + $3 +fi[]dnl +])dnl PKG_CHECK_MODULES + + +dnl PKG_CHECK_MODULES_STATIC(VARIABLE-PREFIX, MODULES, [ACTION-IF-FOUND], +dnl [ACTION-IF-NOT-FOUND]) +dnl --------------------------------------------------------------------- +dnl Since: 0.29 +dnl +dnl Checks for existence of MODULES and gathers its build flags with +dnl static libraries enabled. Sets VARIABLE-PREFIX_CFLAGS from --cflags +dnl and VARIABLE-PREFIX_LIBS from --libs. +dnl +dnl Note that if there is a possibility the first call to +dnl PKG_CHECK_MODULES_STATIC might not happen, you should be sure to +dnl include an explicit call to PKG_PROG_PKG_CONFIG in your +dnl configure.ac. +AC_DEFUN([PKG_CHECK_MODULES_STATIC], +[AC_REQUIRE([PKG_PROG_PKG_CONFIG])dnl +_save_PKG_CONFIG=$PKG_CONFIG +PKG_CONFIG="$PKG_CONFIG --static" +PKG_CHECK_MODULES($@) +PKG_CONFIG=$_save_PKG_CONFIG[]dnl +])dnl PKG_CHECK_MODULES_STATIC + + +dnl PKG_INSTALLDIR([DIRECTORY]) +dnl ------------------------- +dnl Since: 0.27 +dnl +dnl Substitutes the variable pkgconfigdir as the location where a module +dnl should install pkg-config .pc files. By default the directory is +dnl $libdir/pkgconfig, but the default can be changed by passing +dnl DIRECTORY. The user can override through the --with-pkgconfigdir +dnl parameter. +AC_DEFUN([PKG_INSTALLDIR], +[m4_pushdef([pkg_default], [m4_default([$1], ['${libdir}/pkgconfig'])]) +m4_pushdef([pkg_description], + [pkg-config installation directory @<:@]pkg_default[@:>@]) +AC_ARG_WITH([pkgconfigdir], + [AS_HELP_STRING([--with-pkgconfigdir], pkg_description)],, + [with_pkgconfigdir=]pkg_default) +AC_SUBST([pkgconfigdir], [$with_pkgconfigdir]) +m4_popdef([pkg_default]) +m4_popdef([pkg_description]) +])dnl PKG_INSTALLDIR + + +dnl PKG_NOARCH_INSTALLDIR([DIRECTORY]) +dnl -------------------------------- +dnl Since: 0.27 +dnl +dnl Substitutes the variable noarch_pkgconfigdir as the location where a +dnl module should install arch-independent pkg-config .pc files. By +dnl default the directory is $datadir/pkgconfig, but the default can be +dnl changed by passing DIRECTORY. The user can override through the +dnl --with-noarch-pkgconfigdir parameter. +AC_DEFUN([PKG_NOARCH_INSTALLDIR], +[m4_pushdef([pkg_default], [m4_default([$1], ['${datadir}/pkgconfig'])]) +m4_pushdef([pkg_description], + [pkg-config arch-independent installation directory @<:@]pkg_default[@:>@]) +AC_ARG_WITH([noarch-pkgconfigdir], + [AS_HELP_STRING([--with-noarch-pkgconfigdir], pkg_description)],, + [with_noarch_pkgconfigdir=]pkg_default) +AC_SUBST([noarch_pkgconfigdir], [$with_noarch_pkgconfigdir]) +m4_popdef([pkg_default]) +m4_popdef([pkg_description]) +])dnl PKG_NOARCH_INSTALLDIR + + +dnl PKG_CHECK_VAR(VARIABLE, MODULE, CONFIG-VARIABLE, +dnl [ACTION-IF-FOUND], [ACTION-IF-NOT-FOUND]) +dnl ------------------------------------------- +dnl Since: 0.28 +dnl +dnl Retrieves the value of the pkg-config variable for the given module. +AC_DEFUN([PKG_CHECK_VAR], +[AC_REQUIRE([PKG_PROG_PKG_CONFIG])dnl +AC_ARG_VAR([$1], [value of $3 for $2, overriding pkg-config])dnl + +_PKG_CONFIG([$1], [variable="][$3]["], [$2]) +AS_VAR_COPY([$1], [pkg_cv_][$1]) + +AS_VAR_IF([$1], [""], [$5], [$4])dnl +])dnl PKG_CHECK_VAR + +# Copyright (C) 2002-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# AM_AUTOMAKE_VERSION(VERSION) +# ---------------------------- +# Automake X.Y traces this macro to ensure aclocal.m4 has been +# generated from the m4 files accompanying Automake X.Y. +# (This private macro should not be called outside this file.) +AC_DEFUN([AM_AUTOMAKE_VERSION], +[am__api_version='1.15' +dnl Some users find AM_AUTOMAKE_VERSION and mistake it for a way to +dnl require some minimum version. Point them to the right macro. +m4_if([$1], [1.15.1], [], + [AC_FATAL([Do not call $0, use AM_INIT_AUTOMAKE([$1]).])])dnl +]) + +# _AM_AUTOCONF_VERSION(VERSION) +# ----------------------------- +# aclocal traces this macro to find the Autoconf version. +# This is a private macro too. Using m4_define simplifies +# the logic in aclocal, which can simply ignore this definition. +m4_define([_AM_AUTOCONF_VERSION], []) + +# AM_SET_CURRENT_AUTOMAKE_VERSION +# ------------------------------- +# Call AM_AUTOMAKE_VERSION and AM_AUTOMAKE_VERSION so they can be traced. +# This function is AC_REQUIREd by AM_INIT_AUTOMAKE. +AC_DEFUN([AM_SET_CURRENT_AUTOMAKE_VERSION], +[AM_AUTOMAKE_VERSION([1.15.1])dnl +m4_ifndef([AC_AUTOCONF_VERSION], + [m4_copy([m4_PACKAGE_VERSION], [AC_AUTOCONF_VERSION])])dnl +_AM_AUTOCONF_VERSION(m4_defn([AC_AUTOCONF_VERSION]))]) + +# Copyright (C) 2011-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# AM_PROG_AR([ACT-IF-FAIL]) +# ------------------------- +# Try to determine the archiver interface, and trigger the ar-lib wrapper +# if it is needed. If the detection of archiver interface fails, run +# ACT-IF-FAIL (default is to abort configure with a proper error message). +AC_DEFUN([AM_PROG_AR], +[AC_BEFORE([$0], [LT_INIT])dnl +AC_BEFORE([$0], [AC_PROG_LIBTOOL])dnl +AC_REQUIRE([AM_AUX_DIR_EXPAND])dnl +AC_REQUIRE_AUX_FILE([ar-lib])dnl +AC_CHECK_TOOLS([AR], [ar lib "link -lib"], [false]) +: ${AR=ar} + +AC_CACHE_CHECK([the archiver ($AR) interface], [am_cv_ar_interface], + [AC_LANG_PUSH([C]) + am_cv_ar_interface=ar + AC_COMPILE_IFELSE([AC_LANG_SOURCE([[int some_variable = 0;]])], + [am_ar_try='$AR cru libconftest.a conftest.$ac_objext >&AS_MESSAGE_LOG_FD' + AC_TRY_EVAL([am_ar_try]) + if test "$ac_status" -eq 0; then + am_cv_ar_interface=ar + else + am_ar_try='$AR -NOLOGO -OUT:conftest.lib conftest.$ac_objext >&AS_MESSAGE_LOG_FD' + AC_TRY_EVAL([am_ar_try]) + if test "$ac_status" -eq 0; then + am_cv_ar_interface=lib + else + am_cv_ar_interface=unknown + fi + fi + rm -f conftest.lib libconftest.a + ]) + AC_LANG_POP([C])]) + +case $am_cv_ar_interface in +ar) + ;; +lib) + # Microsoft lib, so override with the ar-lib wrapper script. + # FIXME: It is wrong to rewrite AR. + # But if we don't then we get into trouble of one sort or another. + # A longer-term fix would be to have automake use am__AR in this case, + # and then we could set am__AR="$am_aux_dir/ar-lib \$(AR)" or something + # similar. + AR="$am_aux_dir/ar-lib $AR" + ;; +unknown) + m4_default([$1], + [AC_MSG_ERROR([could not determine $AR interface])]) + ;; +esac +AC_SUBST([AR])dnl +]) + +# AM_AUX_DIR_EXPAND -*- Autoconf -*- + +# Copyright (C) 2001-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# For projects using AC_CONFIG_AUX_DIR([foo]), Autoconf sets +# $ac_aux_dir to '$srcdir/foo'. In other projects, it is set to +# '$srcdir', '$srcdir/..', or '$srcdir/../..'. +# +# Of course, Automake must honor this variable whenever it calls a +# tool from the auxiliary directory. The problem is that $srcdir (and +# therefore $ac_aux_dir as well) can be either absolute or relative, +# depending on how configure is run. This is pretty annoying, since +# it makes $ac_aux_dir quite unusable in subdirectories: in the top +# source directory, any form will work fine, but in subdirectories a +# relative path needs to be adjusted first. +# +# $ac_aux_dir/missing +# fails when called from a subdirectory if $ac_aux_dir is relative +# $top_srcdir/$ac_aux_dir/missing +# fails if $ac_aux_dir is absolute, +# fails when called from a subdirectory in a VPATH build with +# a relative $ac_aux_dir +# +# The reason of the latter failure is that $top_srcdir and $ac_aux_dir +# are both prefixed by $srcdir. In an in-source build this is usually +# harmless because $srcdir is '.', but things will broke when you +# start a VPATH build or use an absolute $srcdir. +# +# So we could use something similar to $top_srcdir/$ac_aux_dir/missing, +# iff we strip the leading $srcdir from $ac_aux_dir. That would be: +# am_aux_dir='\$(top_srcdir)/'`expr "$ac_aux_dir" : "$srcdir//*\(.*\)"` +# and then we would define $MISSING as +# MISSING="\${SHELL} $am_aux_dir/missing" +# This will work as long as MISSING is not called from configure, because +# unfortunately $(top_srcdir) has no meaning in configure. +# However there are other variables, like CC, which are often used in +# configure, and could therefore not use this "fixed" $ac_aux_dir. +# +# Another solution, used here, is to always expand $ac_aux_dir to an +# absolute PATH. The drawback is that using absolute paths prevent a +# configured tree to be moved without reconfiguration. + +AC_DEFUN([AM_AUX_DIR_EXPAND], +[AC_REQUIRE([AC_CONFIG_AUX_DIR_DEFAULT])dnl +# Expand $ac_aux_dir to an absolute path. +am_aux_dir=`cd "$ac_aux_dir" && pwd` +]) + +# AM_CONDITIONAL -*- Autoconf -*- + +# Copyright (C) 1997-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# AM_CONDITIONAL(NAME, SHELL-CONDITION) +# ------------------------------------- +# Define a conditional. +AC_DEFUN([AM_CONDITIONAL], +[AC_PREREQ([2.52])dnl + m4_if([$1], [TRUE], [AC_FATAL([$0: invalid condition: $1])], + [$1], [FALSE], [AC_FATAL([$0: invalid condition: $1])])dnl +AC_SUBST([$1_TRUE])dnl +AC_SUBST([$1_FALSE])dnl +_AM_SUBST_NOTMAKE([$1_TRUE])dnl +_AM_SUBST_NOTMAKE([$1_FALSE])dnl +m4_define([_AM_COND_VALUE_$1], [$2])dnl +if $2; then + $1_TRUE= + $1_FALSE='#' +else + $1_TRUE='#' + $1_FALSE= +fi +AC_CONFIG_COMMANDS_PRE( +[if test -z "${$1_TRUE}" && test -z "${$1_FALSE}"; then + AC_MSG_ERROR([[conditional "$1" was never defined. +Usually this means the macro was only invoked conditionally.]]) +fi])]) + +# Copyright (C) 1999-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + + +# There are a few dirty hacks below to avoid letting 'AC_PROG_CC' be +# written in clear, in which case automake, when reading aclocal.m4, +# will think it sees a *use*, and therefore will trigger all it's +# C support machinery. Also note that it means that autoscan, seeing +# CC etc. in the Makefile, will ask for an AC_PROG_CC use... + + +# _AM_DEPENDENCIES(NAME) +# ---------------------- +# See how the compiler implements dependency checking. +# NAME is "CC", "CXX", "OBJC", "OBJCXX", "UPC", or "GJC". +# We try a few techniques and use that to set a single cache variable. +# +# We don't AC_REQUIRE the corresponding AC_PROG_CC since the latter was +# modified to invoke _AM_DEPENDENCIES(CC); we would have a circular +# dependency, and given that the user is not expected to run this macro, +# just rely on AC_PROG_CC. +AC_DEFUN([_AM_DEPENDENCIES], +[AC_REQUIRE([AM_SET_DEPDIR])dnl +AC_REQUIRE([AM_OUTPUT_DEPENDENCY_COMMANDS])dnl +AC_REQUIRE([AM_MAKE_INCLUDE])dnl +AC_REQUIRE([AM_DEP_TRACK])dnl + +m4_if([$1], [CC], [depcc="$CC" am_compiler_list=], + [$1], [CXX], [depcc="$CXX" am_compiler_list=], + [$1], [OBJC], [depcc="$OBJC" am_compiler_list='gcc3 gcc'], + [$1], [OBJCXX], [depcc="$OBJCXX" am_compiler_list='gcc3 gcc'], + [$1], [UPC], [depcc="$UPC" am_compiler_list=], + [$1], [GCJ], [depcc="$GCJ" am_compiler_list='gcc3 gcc'], + [depcc="$$1" am_compiler_list=]) + +AC_CACHE_CHECK([dependency style of $depcc], + [am_cv_$1_dependencies_compiler_type], +[if test -z "$AMDEP_TRUE" && test -f "$am_depcomp"; then + # We make a subdir and do the tests there. Otherwise we can end up + # making bogus files that we don't know about and never remove. For + # instance it was reported that on HP-UX the gcc test will end up + # making a dummy file named 'D' -- because '-MD' means "put the output + # in D". + rm -rf conftest.dir + mkdir conftest.dir + # Copy depcomp to subdir because otherwise we won't find it if we're + # using a relative directory. + cp "$am_depcomp" conftest.dir + cd conftest.dir + # We will build objects and dependencies in a subdirectory because + # it helps to detect inapplicable dependency modes. For instance + # both Tru64's cc and ICC support -MD to output dependencies as a + # side effect of compilation, but ICC will put the dependencies in + # the current directory while Tru64 will put them in the object + # directory. + mkdir sub + + am_cv_$1_dependencies_compiler_type=none + if test "$am_compiler_list" = ""; then + am_compiler_list=`sed -n ['s/^#*\([a-zA-Z0-9]*\))$/\1/p'] < ./depcomp` + fi + am__universal=false + m4_case([$1], [CC], + [case " $depcc " in #( + *\ -arch\ *\ -arch\ *) am__universal=true ;; + esac], + [CXX], + [case " $depcc " in #( + *\ -arch\ *\ -arch\ *) am__universal=true ;; + esac]) + + for depmode in $am_compiler_list; do + # Setup a source with many dependencies, because some compilers + # like to wrap large dependency lists on column 80 (with \), and + # we should not choose a depcomp mode which is confused by this. + # + # We need to recreate these files for each test, as the compiler may + # overwrite some of them when testing with obscure command lines. + # This happens at least with the AIX C compiler. + : > sub/conftest.c + for i in 1 2 3 4 5 6; do + echo '#include "conftst'$i'.h"' >> sub/conftest.c + # Using ": > sub/conftst$i.h" creates only sub/conftst1.h with + # Solaris 10 /bin/sh. + echo '/* dummy */' > sub/conftst$i.h + done + echo "${am__include} ${am__quote}sub/conftest.Po${am__quote}" > confmf + + # We check with '-c' and '-o' for the sake of the "dashmstdout" + # mode. It turns out that the SunPro C++ compiler does not properly + # handle '-M -o', and we need to detect this. Also, some Intel + # versions had trouble with output in subdirs. + am__obj=sub/conftest.${OBJEXT-o} + am__minus_obj="-o $am__obj" + case $depmode in + gcc) + # This depmode causes a compiler race in universal mode. + test "$am__universal" = false || continue + ;; + nosideeffect) + # After this tag, mechanisms are not by side-effect, so they'll + # only be used when explicitly requested. + if test "x$enable_dependency_tracking" = xyes; then + continue + else + break + fi + ;; + msvc7 | msvc7msys | msvisualcpp | msvcmsys) + # This compiler won't grok '-c -o', but also, the minuso test has + # not run yet. These depmodes are late enough in the game, and + # so weak that their functioning should not be impacted. + am__obj=conftest.${OBJEXT-o} + am__minus_obj= + ;; + none) break ;; + esac + if depmode=$depmode \ + source=sub/conftest.c object=$am__obj \ + depfile=sub/conftest.Po tmpdepfile=sub/conftest.TPo \ + $SHELL ./depcomp $depcc -c $am__minus_obj sub/conftest.c \ + >/dev/null 2>conftest.err && + grep sub/conftst1.h sub/conftest.Po > /dev/null 2>&1 && + grep sub/conftst6.h sub/conftest.Po > /dev/null 2>&1 && + grep $am__obj sub/conftest.Po > /dev/null 2>&1 && + ${MAKE-make} -s -f confmf > /dev/null 2>&1; then + # icc doesn't choke on unknown options, it will just issue warnings + # or remarks (even with -Werror). So we grep stderr for any message + # that says an option was ignored or not supported. + # When given -MP, icc 7.0 and 7.1 complain thusly: + # icc: Command line warning: ignoring option '-M'; no argument required + # The diagnosis changed in icc 8.0: + # icc: Command line remark: option '-MP' not supported + if (grep 'ignoring option' conftest.err || + grep 'not supported' conftest.err) >/dev/null 2>&1; then :; else + am_cv_$1_dependencies_compiler_type=$depmode + break + fi + fi + done + + cd .. + rm -rf conftest.dir +else + am_cv_$1_dependencies_compiler_type=none +fi +]) +AC_SUBST([$1DEPMODE], [depmode=$am_cv_$1_dependencies_compiler_type]) +AM_CONDITIONAL([am__fastdep$1], [ + test "x$enable_dependency_tracking" != xno \ + && test "$am_cv_$1_dependencies_compiler_type" = gcc3]) +]) + + +# AM_SET_DEPDIR +# ------------- +# Choose a directory name for dependency files. +# This macro is AC_REQUIREd in _AM_DEPENDENCIES. +AC_DEFUN([AM_SET_DEPDIR], +[AC_REQUIRE([AM_SET_LEADING_DOT])dnl +AC_SUBST([DEPDIR], ["${am__leading_dot}deps"])dnl +]) + + +# AM_DEP_TRACK +# ------------ +AC_DEFUN([AM_DEP_TRACK], +[AC_ARG_ENABLE([dependency-tracking], [dnl +AS_HELP_STRING( + [--enable-dependency-tracking], + [do not reject slow dependency extractors]) +AS_HELP_STRING( + [--disable-dependency-tracking], + [speeds up one-time build])]) +if test "x$enable_dependency_tracking" != xno; then + am_depcomp="$ac_aux_dir/depcomp" + AMDEPBACKSLASH='\' + am__nodep='_no' +fi +AM_CONDITIONAL([AMDEP], [test "x$enable_dependency_tracking" != xno]) +AC_SUBST([AMDEPBACKSLASH])dnl +_AM_SUBST_NOTMAKE([AMDEPBACKSLASH])dnl +AC_SUBST([am__nodep])dnl +_AM_SUBST_NOTMAKE([am__nodep])dnl +]) + +# Generate code to set up dependency tracking. -*- Autoconf -*- + +# Copyright (C) 1999-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + + +# _AM_OUTPUT_DEPENDENCY_COMMANDS +# ------------------------------ +AC_DEFUN([_AM_OUTPUT_DEPENDENCY_COMMANDS], +[{ + # Older Autoconf quotes --file arguments for eval, but not when files + # are listed without --file. Let's play safe and only enable the eval + # if we detect the quoting. + case $CONFIG_FILES in + *\'*) eval set x "$CONFIG_FILES" ;; + *) set x $CONFIG_FILES ;; + esac + shift + for mf + do + # Strip MF so we end up with the name of the file. + mf=`echo "$mf" | sed -e 's/:.*$//'` + # Check whether this is an Automake generated Makefile or not. + # We used to match only the files named 'Makefile.in', but + # some people rename them; so instead we look at the file content. + # Grep'ing the first line is not enough: some people post-process + # each Makefile.in and add a new line on top of each file to say so. + # Grep'ing the whole file is not good either: AIX grep has a line + # limit of 2048, but all sed's we know have understand at least 4000. + if sed -n 's,^#.*generated by automake.*,X,p' "$mf" | grep X >/dev/null 2>&1; then + dirpart=`AS_DIRNAME("$mf")` + else + continue + fi + # Extract the definition of DEPDIR, am__include, and am__quote + # from the Makefile without running 'make'. + DEPDIR=`sed -n 's/^DEPDIR = //p' < "$mf"` + test -z "$DEPDIR" && continue + am__include=`sed -n 's/^am__include = //p' < "$mf"` + test -z "$am__include" && continue + am__quote=`sed -n 's/^am__quote = //p' < "$mf"` + # Find all dependency output files, they are included files with + # $(DEPDIR) in their names. We invoke sed twice because it is the + # simplest approach to changing $(DEPDIR) to its actual value in the + # expansion. + for file in `sed -n " + s/^$am__include $am__quote\(.*(DEPDIR).*\)$am__quote"'$/\1/p' <"$mf" | \ + sed -e 's/\$(DEPDIR)/'"$DEPDIR"'/g'`; do + # Make sure the directory exists. + test -f "$dirpart/$file" && continue + fdir=`AS_DIRNAME(["$file"])` + AS_MKDIR_P([$dirpart/$fdir]) + # echo "creating $dirpart/$file" + echo '# dummy' > "$dirpart/$file" + done + done +} +])# _AM_OUTPUT_DEPENDENCY_COMMANDS + + +# AM_OUTPUT_DEPENDENCY_COMMANDS +# ----------------------------- +# This macro should only be invoked once -- use via AC_REQUIRE. +# +# This code is only required when automatic dependency tracking +# is enabled. FIXME. This creates each '.P' file that we will +# need in order to bootstrap the dependency handling code. +AC_DEFUN([AM_OUTPUT_DEPENDENCY_COMMANDS], +[AC_CONFIG_COMMANDS([depfiles], + [test x"$AMDEP_TRUE" != x"" || _AM_OUTPUT_DEPENDENCY_COMMANDS], + [AMDEP_TRUE="$AMDEP_TRUE" ac_aux_dir="$ac_aux_dir"]) +]) + +# Do all the work for Automake. -*- Autoconf -*- + +# Copyright (C) 1996-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# This macro actually does too much. Some checks are only needed if +# your package does certain things. But this isn't really a big deal. + +dnl Redefine AC_PROG_CC to automatically invoke _AM_PROG_CC_C_O. +m4_define([AC_PROG_CC], +m4_defn([AC_PROG_CC]) +[_AM_PROG_CC_C_O +]) + +# AM_INIT_AUTOMAKE(PACKAGE, VERSION, [NO-DEFINE]) +# AM_INIT_AUTOMAKE([OPTIONS]) +# ----------------------------------------------- +# The call with PACKAGE and VERSION arguments is the old style +# call (pre autoconf-2.50), which is being phased out. PACKAGE +# and VERSION should now be passed to AC_INIT and removed from +# the call to AM_INIT_AUTOMAKE. +# We support both call styles for the transition. After +# the next Automake release, Autoconf can make the AC_INIT +# arguments mandatory, and then we can depend on a new Autoconf +# release and drop the old call support. +AC_DEFUN([AM_INIT_AUTOMAKE], +[AC_PREREQ([2.65])dnl +dnl Autoconf wants to disallow AM_ names. We explicitly allow +dnl the ones we care about. +m4_pattern_allow([^AM_[A-Z]+FLAGS$])dnl +AC_REQUIRE([AM_SET_CURRENT_AUTOMAKE_VERSION])dnl +AC_REQUIRE([AC_PROG_INSTALL])dnl +if test "`cd $srcdir && pwd`" != "`pwd`"; then + # Use -I$(srcdir) only when $(srcdir) != ., so that make's output + # is not polluted with repeated "-I." + AC_SUBST([am__isrc], [' -I$(srcdir)'])_AM_SUBST_NOTMAKE([am__isrc])dnl + # test to see if srcdir already configured + if test -f $srcdir/config.status; then + AC_MSG_ERROR([source directory already configured; run "make distclean" there first]) + fi +fi + +# test whether we have cygpath +if test -z "$CYGPATH_W"; then + if (cygpath --version) >/dev/null 2>/dev/null; then + CYGPATH_W='cygpath -w' + else + CYGPATH_W=echo + fi +fi +AC_SUBST([CYGPATH_W]) + +# Define the identity of the package. +dnl Distinguish between old-style and new-style calls. +m4_ifval([$2], +[AC_DIAGNOSE([obsolete], + [$0: two- and three-arguments forms are deprecated.]) +m4_ifval([$3], [_AM_SET_OPTION([no-define])])dnl + AC_SUBST([PACKAGE], [$1])dnl + AC_SUBST([VERSION], [$2])], +[_AM_SET_OPTIONS([$1])dnl +dnl Diagnose old-style AC_INIT with new-style AM_AUTOMAKE_INIT. +m4_if( + m4_ifdef([AC_PACKAGE_NAME], [ok]):m4_ifdef([AC_PACKAGE_VERSION], [ok]), + [ok:ok],, + [m4_fatal([AC_INIT should be called with package and version arguments])])dnl + AC_SUBST([PACKAGE], ['AC_PACKAGE_TARNAME'])dnl + AC_SUBST([VERSION], ['AC_PACKAGE_VERSION'])])dnl + +_AM_IF_OPTION([no-define],, +[AC_DEFINE_UNQUOTED([PACKAGE], ["$PACKAGE"], [Name of package]) + AC_DEFINE_UNQUOTED([VERSION], ["$VERSION"], [Version number of package])])dnl + +# Some tools Automake needs. +AC_REQUIRE([AM_SANITY_CHECK])dnl +AC_REQUIRE([AC_ARG_PROGRAM])dnl +AM_MISSING_PROG([ACLOCAL], [aclocal-${am__api_version}]) +AM_MISSING_PROG([AUTOCONF], [autoconf]) +AM_MISSING_PROG([AUTOMAKE], [automake-${am__api_version}]) +AM_MISSING_PROG([AUTOHEADER], [autoheader]) +AM_MISSING_PROG([MAKEINFO], [makeinfo]) +AC_REQUIRE([AM_PROG_INSTALL_SH])dnl +AC_REQUIRE([AM_PROG_INSTALL_STRIP])dnl +AC_REQUIRE([AC_PROG_MKDIR_P])dnl +# For better backward compatibility. To be removed once Automake 1.9.x +# dies out for good. For more background, see: +# +# +AC_SUBST([mkdir_p], ['$(MKDIR_P)']) +# We need awk for the "check" target (and possibly the TAP driver). The +# system "awk" is bad on some platforms. +AC_REQUIRE([AC_PROG_AWK])dnl +AC_REQUIRE([AC_PROG_MAKE_SET])dnl +AC_REQUIRE([AM_SET_LEADING_DOT])dnl +_AM_IF_OPTION([tar-ustar], [_AM_PROG_TAR([ustar])], + [_AM_IF_OPTION([tar-pax], [_AM_PROG_TAR([pax])], + [_AM_PROG_TAR([v7])])]) +_AM_IF_OPTION([no-dependencies],, +[AC_PROVIDE_IFELSE([AC_PROG_CC], + [_AM_DEPENDENCIES([CC])], + [m4_define([AC_PROG_CC], + m4_defn([AC_PROG_CC])[_AM_DEPENDENCIES([CC])])])dnl +AC_PROVIDE_IFELSE([AC_PROG_CXX], + [_AM_DEPENDENCIES([CXX])], + [m4_define([AC_PROG_CXX], + m4_defn([AC_PROG_CXX])[_AM_DEPENDENCIES([CXX])])])dnl +AC_PROVIDE_IFELSE([AC_PROG_OBJC], + [_AM_DEPENDENCIES([OBJC])], + [m4_define([AC_PROG_OBJC], + m4_defn([AC_PROG_OBJC])[_AM_DEPENDENCIES([OBJC])])])dnl +AC_PROVIDE_IFELSE([AC_PROG_OBJCXX], + [_AM_DEPENDENCIES([OBJCXX])], + [m4_define([AC_PROG_OBJCXX], + m4_defn([AC_PROG_OBJCXX])[_AM_DEPENDENCIES([OBJCXX])])])dnl +]) +AC_REQUIRE([AM_SILENT_RULES])dnl +dnl The testsuite driver may need to know about EXEEXT, so add the +dnl 'am__EXEEXT' conditional if _AM_COMPILER_EXEEXT was seen. This +dnl macro is hooked onto _AC_COMPILER_EXEEXT early, see below. +AC_CONFIG_COMMANDS_PRE(dnl +[m4_provide_if([_AM_COMPILER_EXEEXT], + [AM_CONDITIONAL([am__EXEEXT], [test -n "$EXEEXT"])])])dnl + +# POSIX will say in a future version that running "rm -f" with no argument +# is OK; and we want to be able to make that assumption in our Makefile +# recipes. So use an aggressive probe to check that the usage we want is +# actually supported "in the wild" to an acceptable degree. +# See automake bug#10828. +# To make any issue more visible, cause the running configure to be aborted +# by default if the 'rm' program in use doesn't match our expectations; the +# user can still override this though. +if rm -f && rm -fr && rm -rf; then : OK; else + cat >&2 <<'END' +Oops! + +Your 'rm' program seems unable to run without file operands specified +on the command line, even when the '-f' option is present. This is contrary +to the behaviour of most rm programs out there, and not conforming with +the upcoming POSIX standard: + +Please tell bug-automake@gnu.org about your system, including the value +of your $PATH and any error possibly output before this message. This +can help us improve future automake versions. + +END + if test x"$ACCEPT_INFERIOR_RM_PROGRAM" = x"yes"; then + echo 'Configuration will proceed anyway, since you have set the' >&2 + echo 'ACCEPT_INFERIOR_RM_PROGRAM variable to "yes"' >&2 + echo >&2 + else + cat >&2 <<'END' +Aborting the configuration process, to ensure you take notice of the issue. + +You can download and install GNU coreutils to get an 'rm' implementation +that behaves properly: . + +If you want to complete the configuration process using your problematic +'rm' anyway, export the environment variable ACCEPT_INFERIOR_RM_PROGRAM +to "yes", and re-run configure. + +END + AC_MSG_ERROR([Your 'rm' program is bad, sorry.]) + fi +fi +dnl The trailing newline in this macro's definition is deliberate, for +dnl backward compatibility and to allow trailing 'dnl'-style comments +dnl after the AM_INIT_AUTOMAKE invocation. See automake bug#16841. +]) + +dnl Hook into '_AC_COMPILER_EXEEXT' early to learn its expansion. Do not +dnl add the conditional right here, as _AC_COMPILER_EXEEXT may be further +dnl mangled by Autoconf and run in a shell conditional statement. +m4_define([_AC_COMPILER_EXEEXT], +m4_defn([_AC_COMPILER_EXEEXT])[m4_provide([_AM_COMPILER_EXEEXT])]) + +# When config.status generates a header, we must update the stamp-h file. +# This file resides in the same directory as the config header +# that is generated. The stamp files are numbered to have different names. + +# Autoconf calls _AC_AM_CONFIG_HEADER_HOOK (when defined) in the +# loop where config.status creates the headers, so we can generate +# our stamp files there. +AC_DEFUN([_AC_AM_CONFIG_HEADER_HOOK], +[# Compute $1's index in $config_headers. +_am_arg=$1 +_am_stamp_count=1 +for _am_header in $config_headers :; do + case $_am_header in + $_am_arg | $_am_arg:* ) + break ;; + * ) + _am_stamp_count=`expr $_am_stamp_count + 1` ;; + esac +done +echo "timestamp for $_am_arg" >`AS_DIRNAME(["$_am_arg"])`/stamp-h[]$_am_stamp_count]) + +# Copyright (C) 2001-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# AM_PROG_INSTALL_SH +# ------------------ +# Define $install_sh. +AC_DEFUN([AM_PROG_INSTALL_SH], +[AC_REQUIRE([AM_AUX_DIR_EXPAND])dnl +if test x"${install_sh+set}" != xset; then + case $am_aux_dir in + *\ * | *\ *) + install_sh="\${SHELL} '$am_aux_dir/install-sh'" ;; + *) + install_sh="\${SHELL} $am_aux_dir/install-sh" + esac +fi +AC_SUBST([install_sh])]) + +# Copyright (C) 2003-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# Check whether the underlying file-system supports filenames +# with a leading dot. For instance MS-DOS doesn't. +AC_DEFUN([AM_SET_LEADING_DOT], +[rm -rf .tst 2>/dev/null +mkdir .tst 2>/dev/null +if test -d .tst; then + am__leading_dot=. +else + am__leading_dot=_ +fi +rmdir .tst 2>/dev/null +AC_SUBST([am__leading_dot])]) + +# Check to see how 'make' treats includes. -*- Autoconf -*- + +# Copyright (C) 2001-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# AM_MAKE_INCLUDE() +# ----------------- +# Check to see how make treats includes. +AC_DEFUN([AM_MAKE_INCLUDE], +[am_make=${MAKE-make} +cat > confinc << 'END' +am__doit: + @echo this is the am__doit target +.PHONY: am__doit +END +# If we don't find an include directive, just comment out the code. +AC_MSG_CHECKING([for style of include used by $am_make]) +am__include="#" +am__quote= +_am_result=none +# First try GNU make style include. +echo "include confinc" > confmf +# Ignore all kinds of additional output from 'make'. +case `$am_make -s -f confmf 2> /dev/null` in #( +*the\ am__doit\ target*) + am__include=include + am__quote= + _am_result=GNU + ;; +esac +# Now try BSD make style include. +if test "$am__include" = "#"; then + echo '.include "confinc"' > confmf + case `$am_make -s -f confmf 2> /dev/null` in #( + *the\ am__doit\ target*) + am__include=.include + am__quote="\"" + _am_result=BSD + ;; + esac +fi +AC_SUBST([am__include]) +AC_SUBST([am__quote]) +AC_MSG_RESULT([$_am_result]) +rm -f confinc confmf +]) + +# Fake the existence of programs that GNU maintainers use. -*- Autoconf -*- + +# Copyright (C) 1997-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# AM_MISSING_PROG(NAME, PROGRAM) +# ------------------------------ +AC_DEFUN([AM_MISSING_PROG], +[AC_REQUIRE([AM_MISSING_HAS_RUN]) +$1=${$1-"${am_missing_run}$2"} +AC_SUBST($1)]) + +# AM_MISSING_HAS_RUN +# ------------------ +# Define MISSING if not defined so far and test if it is modern enough. +# If it is, set am_missing_run to use it, otherwise, to nothing. +AC_DEFUN([AM_MISSING_HAS_RUN], +[AC_REQUIRE([AM_AUX_DIR_EXPAND])dnl +AC_REQUIRE_AUX_FILE([missing])dnl +if test x"${MISSING+set}" != xset; then + case $am_aux_dir in + *\ * | *\ *) + MISSING="\${SHELL} \"$am_aux_dir/missing\"" ;; + *) + MISSING="\${SHELL} $am_aux_dir/missing" ;; + esac +fi +# Use eval to expand $SHELL +if eval "$MISSING --is-lightweight"; then + am_missing_run="$MISSING " +else + am_missing_run= + AC_MSG_WARN(['missing' script is too old or missing]) +fi +]) + +# Helper functions for option handling. -*- Autoconf -*- + +# Copyright (C) 2001-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# _AM_MANGLE_OPTION(NAME) +# ----------------------- +AC_DEFUN([_AM_MANGLE_OPTION], +[[_AM_OPTION_]m4_bpatsubst($1, [[^a-zA-Z0-9_]], [_])]) + +# _AM_SET_OPTION(NAME) +# -------------------- +# Set option NAME. Presently that only means defining a flag for this option. +AC_DEFUN([_AM_SET_OPTION], +[m4_define(_AM_MANGLE_OPTION([$1]), [1])]) + +# _AM_SET_OPTIONS(OPTIONS) +# ------------------------ +# OPTIONS is a space-separated list of Automake options. +AC_DEFUN([_AM_SET_OPTIONS], +[m4_foreach_w([_AM_Option], [$1], [_AM_SET_OPTION(_AM_Option)])]) + +# _AM_IF_OPTION(OPTION, IF-SET, [IF-NOT-SET]) +# ------------------------------------------- +# Execute IF-SET if OPTION is set, IF-NOT-SET otherwise. +AC_DEFUN([_AM_IF_OPTION], +[m4_ifset(_AM_MANGLE_OPTION([$1]), [$2], [$3])]) + +# Copyright (C) 1999-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# _AM_PROG_CC_C_O +# --------------- +# Like AC_PROG_CC_C_O, but changed for automake. We rewrite AC_PROG_CC +# to automatically call this. +AC_DEFUN([_AM_PROG_CC_C_O], +[AC_REQUIRE([AM_AUX_DIR_EXPAND])dnl +AC_REQUIRE_AUX_FILE([compile])dnl +AC_LANG_PUSH([C])dnl +AC_CACHE_CHECK( + [whether $CC understands -c and -o together], + [am_cv_prog_cc_c_o], + [AC_LANG_CONFTEST([AC_LANG_PROGRAM([])]) + # Make sure it works both with $CC and with simple cc. + # Following AC_PROG_CC_C_O, we do the test twice because some + # compilers refuse to overwrite an existing .o file with -o, + # though they will create one. + am_cv_prog_cc_c_o=yes + for am_i in 1 2; do + if AM_RUN_LOG([$CC -c conftest.$ac_ext -o conftest2.$ac_objext]) \ + && test -f conftest2.$ac_objext; then + : OK + else + am_cv_prog_cc_c_o=no + break + fi + done + rm -f core conftest* + unset am_i]) +if test "$am_cv_prog_cc_c_o" != yes; then + # Losing compiler, so override with the script. + # FIXME: It is wrong to rewrite CC. + # But if we don't then we get into trouble of one sort or another. + # A longer-term fix would be to have automake use am__CC in this case, + # and then we could set am__CC="\$(top_srcdir)/compile \$(CC)" + CC="$am_aux_dir/compile $CC" +fi +AC_LANG_POP([C])]) + +# For backward compatibility. +AC_DEFUN_ONCE([AM_PROG_CC_C_O], [AC_REQUIRE([AC_PROG_CC])]) + +# Copyright (C) 2001-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# AM_RUN_LOG(COMMAND) +# ------------------- +# Run COMMAND, save the exit status in ac_status, and log it. +# (This has been adapted from Autoconf's _AC_RUN_LOG macro.) +AC_DEFUN([AM_RUN_LOG], +[{ echo "$as_me:$LINENO: $1" >&AS_MESSAGE_LOG_FD + ($1) >&AS_MESSAGE_LOG_FD 2>&AS_MESSAGE_LOG_FD + ac_status=$? + echo "$as_me:$LINENO: \$? = $ac_status" >&AS_MESSAGE_LOG_FD + (exit $ac_status); }]) + +# Check to make sure that the build environment is sane. -*- Autoconf -*- + +# Copyright (C) 1996-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# AM_SANITY_CHECK +# --------------- +AC_DEFUN([AM_SANITY_CHECK], +[AC_MSG_CHECKING([whether build environment is sane]) +# Reject unsafe characters in $srcdir or the absolute working directory +# name. Accept space and tab only in the latter. +am_lf=' +' +case `pwd` in + *[[\\\"\#\$\&\'\`$am_lf]]*) + AC_MSG_ERROR([unsafe absolute working directory name]);; +esac +case $srcdir in + *[[\\\"\#\$\&\'\`$am_lf\ \ ]]*) + AC_MSG_ERROR([unsafe srcdir value: '$srcdir']);; +esac + +# Do 'set' in a subshell so we don't clobber the current shell's +# arguments. Must try -L first in case configure is actually a +# symlink; some systems play weird games with the mod time of symlinks +# (eg FreeBSD returns the mod time of the symlink's containing +# directory). +if ( + am_has_slept=no + for am_try in 1 2; do + echo "timestamp, slept: $am_has_slept" > conftest.file + set X `ls -Lt "$srcdir/configure" conftest.file 2> /dev/null` + if test "$[*]" = "X"; then + # -L didn't work. + set X `ls -t "$srcdir/configure" conftest.file` + fi + if test "$[*]" != "X $srcdir/configure conftest.file" \ + && test "$[*]" != "X conftest.file $srcdir/configure"; then + + # If neither matched, then we have a broken ls. This can happen + # if, for instance, CONFIG_SHELL is bash and it inherits a + # broken ls alias from the environment. This has actually + # happened. Such a system could not be considered "sane". + AC_MSG_ERROR([ls -t appears to fail. Make sure there is not a broken + alias in your environment]) + fi + if test "$[2]" = conftest.file || test $am_try -eq 2; then + break + fi + # Just in case. + sleep 1 + am_has_slept=yes + done + test "$[2]" = conftest.file + ) +then + # Ok. + : +else + AC_MSG_ERROR([newly created file is older than distributed files! +Check your system clock]) +fi +AC_MSG_RESULT([yes]) +# If we didn't sleep, we still need to ensure time stamps of config.status and +# generated files are strictly newer. +am_sleep_pid= +if grep 'slept: no' conftest.file >/dev/null 2>&1; then + ( sleep 1 ) & + am_sleep_pid=$! +fi +AC_CONFIG_COMMANDS_PRE( + [AC_MSG_CHECKING([that generated files are newer than configure]) + if test -n "$am_sleep_pid"; then + # Hide warnings about reused PIDs. + wait $am_sleep_pid 2>/dev/null + fi + AC_MSG_RESULT([done])]) +rm -f conftest.file +]) + +# Copyright (C) 2009-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# AM_SILENT_RULES([DEFAULT]) +# -------------------------- +# Enable less verbose build rules; with the default set to DEFAULT +# ("yes" being less verbose, "no" or empty being verbose). +AC_DEFUN([AM_SILENT_RULES], +[AC_ARG_ENABLE([silent-rules], [dnl +AS_HELP_STRING( + [--enable-silent-rules], + [less verbose build output (undo: "make V=1")]) +AS_HELP_STRING( + [--disable-silent-rules], + [verbose build output (undo: "make V=0")])dnl +]) +case $enable_silent_rules in @%:@ ((( + yes) AM_DEFAULT_VERBOSITY=0;; + no) AM_DEFAULT_VERBOSITY=1;; + *) AM_DEFAULT_VERBOSITY=m4_if([$1], [yes], [0], [1]);; +esac +dnl +dnl A few 'make' implementations (e.g., NonStop OS and NextStep) +dnl do not support nested variable expansions. +dnl See automake bug#9928 and bug#10237. +am_make=${MAKE-make} +AC_CACHE_CHECK([whether $am_make supports nested variables], + [am_cv_make_support_nested_variables], + [if AS_ECHO([['TRUE=$(BAR$(V)) +BAR0=false +BAR1=true +V=1 +am__doit: + @$(TRUE) +.PHONY: am__doit']]) | $am_make -f - >/dev/null 2>&1; then + am_cv_make_support_nested_variables=yes +else + am_cv_make_support_nested_variables=no +fi]) +if test $am_cv_make_support_nested_variables = yes; then + dnl Using '$V' instead of '$(V)' breaks IRIX make. + AM_V='$(V)' + AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)' +else + AM_V=$AM_DEFAULT_VERBOSITY + AM_DEFAULT_V=$AM_DEFAULT_VERBOSITY +fi +AC_SUBST([AM_V])dnl +AM_SUBST_NOTMAKE([AM_V])dnl +AC_SUBST([AM_DEFAULT_V])dnl +AM_SUBST_NOTMAKE([AM_DEFAULT_V])dnl +AC_SUBST([AM_DEFAULT_VERBOSITY])dnl +AM_BACKSLASH='\' +AC_SUBST([AM_BACKSLASH])dnl +_AM_SUBST_NOTMAKE([AM_BACKSLASH])dnl +]) + +# Copyright (C) 2001-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# AM_PROG_INSTALL_STRIP +# --------------------- +# One issue with vendor 'install' (even GNU) is that you can't +# specify the program used to strip binaries. This is especially +# annoying in cross-compiling environments, where the build's strip +# is unlikely to handle the host's binaries. +# Fortunately install-sh will honor a STRIPPROG variable, so we +# always use install-sh in "make install-strip", and initialize +# STRIPPROG with the value of the STRIP variable (set by the user). +AC_DEFUN([AM_PROG_INSTALL_STRIP], +[AC_REQUIRE([AM_PROG_INSTALL_SH])dnl +# Installed binaries are usually stripped using 'strip' when the user +# run "make install-strip". However 'strip' might not be the right +# tool to use in cross-compilation environments, therefore Automake +# will honor the 'STRIP' environment variable to overrule this program. +dnl Don't test for $cross_compiling = yes, because it might be 'maybe'. +if test "$cross_compiling" != no; then + AC_CHECK_TOOL([STRIP], [strip], :) +fi +INSTALL_STRIP_PROGRAM="\$(install_sh) -c -s" +AC_SUBST([INSTALL_STRIP_PROGRAM])]) + +# Copyright (C) 2006-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# _AM_SUBST_NOTMAKE(VARIABLE) +# --------------------------- +# Prevent Automake from outputting VARIABLE = @VARIABLE@ in Makefile.in. +# This macro is traced by Automake. +AC_DEFUN([_AM_SUBST_NOTMAKE]) + +# AM_SUBST_NOTMAKE(VARIABLE) +# -------------------------- +# Public sister of _AM_SUBST_NOTMAKE. +AC_DEFUN([AM_SUBST_NOTMAKE], [_AM_SUBST_NOTMAKE($@)]) + +# Check how to create a tarball. -*- Autoconf -*- + +# Copyright (C) 2004-2017 Free Software Foundation, Inc. +# +# This file is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# _AM_PROG_TAR(FORMAT) +# -------------------- +# Check how to create a tarball in format FORMAT. +# FORMAT should be one of 'v7', 'ustar', or 'pax'. +# +# Substitute a variable $(am__tar) that is a command +# writing to stdout a FORMAT-tarball containing the directory +# $tardir. +# tardir=directory && $(am__tar) > result.tar +# +# Substitute a variable $(am__untar) that extract such +# a tarball read from stdin. +# $(am__untar) < result.tar +# +AC_DEFUN([_AM_PROG_TAR], +[# Always define AMTAR for backward compatibility. Yes, it's still used +# in the wild :-( We should find a proper way to deprecate it ... +AC_SUBST([AMTAR], ['$${TAR-tar}']) + +# We'll loop over all known methods to create a tar archive until one works. +_am_tools='gnutar m4_if([$1], [ustar], [plaintar]) pax cpio none' + +m4_if([$1], [v7], + [am__tar='$${TAR-tar} chof - "$$tardir"' am__untar='$${TAR-tar} xf -'], + + [m4_case([$1], + [ustar], + [# The POSIX 1988 'ustar' format is defined with fixed-size fields. + # There is notably a 21 bits limit for the UID and the GID. In fact, + # the 'pax' utility can hang on bigger UID/GID (see automake bug#8343 + # and bug#13588). + am_max_uid=2097151 # 2^21 - 1 + am_max_gid=$am_max_uid + # The $UID and $GID variables are not portable, so we need to resort + # to the POSIX-mandated id(1) utility. Errors in the 'id' calls + # below are definitely unexpected, so allow the users to see them + # (that is, avoid stderr redirection). + am_uid=`id -u || echo unknown` + am_gid=`id -g || echo unknown` + AC_MSG_CHECKING([whether UID '$am_uid' is supported by ustar format]) + if test $am_uid -le $am_max_uid; then + AC_MSG_RESULT([yes]) + else + AC_MSG_RESULT([no]) + _am_tools=none + fi + AC_MSG_CHECKING([whether GID '$am_gid' is supported by ustar format]) + if test $am_gid -le $am_max_gid; then + AC_MSG_RESULT([yes]) + else + AC_MSG_RESULT([no]) + _am_tools=none + fi], + + [pax], + [], + + [m4_fatal([Unknown tar format])]) + + AC_MSG_CHECKING([how to create a $1 tar archive]) + + # Go ahead even if we have the value already cached. We do so because we + # need to set the values for the 'am__tar' and 'am__untar' variables. + _am_tools=${am_cv_prog_tar_$1-$_am_tools} + + for _am_tool in $_am_tools; do + case $_am_tool in + gnutar) + for _am_tar in tar gnutar gtar; do + AM_RUN_LOG([$_am_tar --version]) && break + done + am__tar="$_am_tar --format=m4_if([$1], [pax], [posix], [$1]) -chf - "'"$$tardir"' + am__tar_="$_am_tar --format=m4_if([$1], [pax], [posix], [$1]) -chf - "'"$tardir"' + am__untar="$_am_tar -xf -" + ;; + plaintar) + # Must skip GNU tar: if it does not support --format= it doesn't create + # ustar tarball either. + (tar --version) >/dev/null 2>&1 && continue + am__tar='tar chf - "$$tardir"' + am__tar_='tar chf - "$tardir"' + am__untar='tar xf -' + ;; + pax) + am__tar='pax -L -x $1 -w "$$tardir"' + am__tar_='pax -L -x $1 -w "$tardir"' + am__untar='pax -r' + ;; + cpio) + am__tar='find "$$tardir" -print | cpio -o -H $1 -L' + am__tar_='find "$tardir" -print | cpio -o -H $1 -L' + am__untar='cpio -i -H $1 -d' + ;; + none) + am__tar=false + am__tar_=false + am__untar=false + ;; + esac + + # If the value was cached, stop now. We just wanted to have am__tar + # and am__untar set. + test -n "${am_cv_prog_tar_$1}" && break + + # tar/untar a dummy directory, and stop if the command works. + rm -rf conftest.dir + mkdir conftest.dir + echo GrepMe > conftest.dir/file + AM_RUN_LOG([tardir=conftest.dir && eval $am__tar_ >conftest.tar]) + rm -rf conftest.dir + if test -s conftest.tar; then + AM_RUN_LOG([$am__untar /dev/null 2>&1 && break + fi + done + rm -rf conftest.dir + + AC_CACHE_VAL([am_cv_prog_tar_$1], [am_cv_prog_tar_$1=$_am_tool]) + AC_MSG_RESULT([$am_cv_prog_tar_$1])]) + +AC_SUBST([am__tar]) +AC_SUBST([am__untar]) +]) # _AM_PROG_TAR + diff --git a/ar-lib b/ar-lib new file mode 100644 index 0000000..05094d3 --- /dev/null +++ b/ar-lib @@ -0,0 +1,270 @@ +#! /bin/sh +# Wrapper for Microsoft lib.exe + +me=ar-lib +scriptversion=2012-03-01.08; # UTC + +# Copyright (C) 2010-2017 Free Software Foundation, Inc. +# Written by Peter Rosin . +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2, or (at your option) +# any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, see . + +# As a special exception to the GNU General Public License, if you +# distribute this file as part of a program that contains a +# configuration script generated by Autoconf, you may include it under +# the same distribution terms that you use for the rest of that program. + +# This file is maintained in Automake, please report +# bugs to or send patches to +# . + + +# func_error message +func_error () +{ + echo "$me: $1" 1>&2 + exit 1 +} + +file_conv= + +# func_file_conv build_file +# Convert a $build file to $host form and store it in $file +# Currently only supports Windows hosts. +func_file_conv () +{ + file=$1 + case $file in + / | /[!/]*) # absolute file, and not a UNC file + if test -z "$file_conv"; then + # lazily determine how to convert abs files + case `uname -s` in + MINGW*) + file_conv=mingw + ;; + CYGWIN*) + file_conv=cygwin + ;; + *) + file_conv=wine + ;; + esac + fi + case $file_conv in + mingw) + file=`cmd //C echo "$file " | sed -e 's/"\(.*\) " *$/\1/'` + ;; + cygwin) + file=`cygpath -m "$file" || echo "$file"` + ;; + wine) + file=`winepath -w "$file" || echo "$file"` + ;; + esac + ;; + esac +} + +# func_at_file at_file operation archive +# Iterate over all members in AT_FILE performing OPERATION on ARCHIVE +# for each of them. +# When interpreting the content of the @FILE, do NOT use func_file_conv, +# since the user would need to supply preconverted file names to +# binutils ar, at least for MinGW. +func_at_file () +{ + operation=$2 + archive=$3 + at_file_contents=`cat "$1"` + eval set x "$at_file_contents" + shift + + for member + do + $AR -NOLOGO $operation:"$member" "$archive" || exit $? + done +} + +case $1 in + '') + func_error "no command. Try '$0 --help' for more information." + ;; + -h | --h*) + cat <n_prompts; i++) { if (promptsgot < nprompts) { p->prompts[i]->result = dupstr(prompts[promptsgot++]); + if (cgtest_verbose) + printf(" prompt \"%s\": response \"%s\"\n", + p->prompts[i]->prompt, p->prompts[i]->result); } else { promptsgot++; /* track number of requests anyway */ ret = 0; + if (cgtest_verbose) + printf(" prompt \"%s\": no response preloaded\n", + p->prompts[i]->prompt); } } return ret; @@ -215,7 +222,8 @@ int main(int argc, char **argv) enum { PRIVATE, PUBLIC, PUBLICO, FP, OPENSSH_AUTO, OPENSSH_NEW, SSHCOM } outtype = PRIVATE; int bits = -1; - char *comment = NULL, *origcomment = NULL; + const char *comment = NULL; + char *origcomment = NULL; bool change_passphrase = false; bool errs = false, nogo = false; int intype = SSH_KEYTYPE_UNOPENABLE; @@ -735,6 +743,9 @@ int main(int argc, char **argv) assert(infile != NULL); + sfree(origcomment); + origcomment = NULL; + /* * Find out whether the input key is encrypted. */ @@ -781,7 +792,11 @@ int main(int argc, char **argv) strbuf *blob; BinarySource src[1]; + sfree(origcomment); + origcomment = NULL; + blob = strbuf_new(); + ret = rsa_ssh1_loadpub(infilename, BinarySink_UPCAST(blob), &origcomment, &error); BinarySource_BARE_INIT(src, blob->u, blob->len); @@ -807,6 +822,8 @@ int main(int argc, char **argv) case SSH_KEYTYPE_SSH2_PUBLIC_RFC4716: case SSH_KEYTYPE_SSH2_PUBLIC_OPENSSH: if (!load_encrypted) { + sfree(origcomment); + origcomment = NULL; ssh2blob = strbuf_new(); if (ssh2_userkey_loadpub(infilename, &ssh2alg, BinarySink_UPCAST(ssh2blob), &origcomment, &error)) { @@ -933,6 +950,7 @@ int main(int argc, char **argv) int real_outtype; case PRIVATE: + random_ref(); /* we'll need a few random bytes in the save file */ if (sshver == 1) { assert(ssh1key); ret = rsa_ssh1_savekey(outfilename, ssh1key, new_passphrase); @@ -1068,12 +1086,15 @@ int main(int argc, char **argv) if (ssh1key) { freersakey(ssh1key); + sfree(ssh1key); } if (ssh2key) { sfree(ssh2key->comment); ssh_key_free(ssh2key->key); sfree(ssh2key); } + if (ssh2blob) + strbuf_free(ssh2blob); sfree(origcomment); if (infilename) filename_free(infilename); @@ -1126,7 +1147,33 @@ void test(int retval, ...) va_end(ap); promptsgot = 0; + if (cgtest_verbose) { + printf("run:"); + for (int i = 0; i < argc; i++) { + static const char okchars[] = + "0123456789abcdefghijklmnopqrstuvwxyz" + "ABCDEFGHIJKLMNOPQRSTUVWXYZ%+,-./:=[]^_"; + const char *arg = argv[i]; + + printf(" "); + if (arg[strspn(arg, okchars)]) { + printf("'"); + for (const char *c = argv[i]; *c; c++) { + if (*c == '\'') { + printf("'\\''"); + } else { + putchar(*c); + } + } + printf("'"); + } else { + fputs(arg, stdout); + } + } + printf("\n"); + } ret = cmdgen_main(argc, argv); + random_clear(); if (ret != retval) { printf("FAILED retval (exp %d got %d):", retval, ret); @@ -1180,19 +1227,21 @@ void filecmp(char *file1, char *file2, char *fmt, ...) char *cleanup_fp(char *s) { - char *p; + ptrlen pl = ptrlen_from_asciz(s); + static const char separators[] = " \n\t"; - if (!strncmp(s, "ssh-", 4)) { - s += strcspn(s, " \n\t"); - s += strspn(s, " \n\t"); - } + /* Skip initial key type word if we find one */ + if (ptrlen_startswith(pl, PTRLEN_LITERAL("ssh-"), NULL)) + ptrlen_get_word(&pl, separators); - p = s; - s += strcspn(s, " \n\t"); - s += strspn(s, " \n\t"); - s += strcspn(s, " \n\t"); + /* Expect two words giving the key length and the hash */ + ptrlen bits = ptrlen_get_word(&pl, separators); + ptrlen hash = ptrlen_get_word(&pl, separators); - return dupprintf("%.*s", (int)(s - p), p); + /* Strip "MD5:" prefix if it's present, and do nothing if it isn't */ + ptrlen_startswith(hash, PTRLEN_LITERAL("MD5:"), &hash); + + return dupprintf("%.*s %.*s", PTRLEN_PRINTF(bits), PTRLEN_PRINTF(hash)); } char *get_fp(char *filename) @@ -1243,6 +1292,9 @@ int main(int argc, char **argv) int i; static char *const keytypes[] = { "rsa1", "dsa", "rsa" }; + if (getenv("CGTEST_VERBOSE")) + cgtest_verbose = true; + /* * Even when this thing is compiled for automatic test mode, * it's helpful to be able to invoke it with command-line @@ -1279,7 +1331,7 @@ int main(int argc, char **argv) { char *cmdbuf; fp = NULL; - cmdbuf = dupprintf("ssh-keygen -l -f '%s' > '%s'", + cmdbuf = dupprintf("ssh-keygen -E md5 -l -f '%s' > '%s'", pubfilename, tmpfilename1); if (system(cmdbuf) || (fp = get_fp(tmpfilename1)) == NULL) { diff --git a/compile b/compile new file mode 100644 index 0000000..a85b723 --- /dev/null +++ b/compile @@ -0,0 +1,347 @@ +#! /bin/sh +# Wrapper for compilers which do not understand '-c -o'. + +scriptversion=2012-10-14.11; # UTC + +# Copyright (C) 1999-2014 Free Software Foundation, Inc. +# Written by Tom Tromey . +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2, or (at your option) +# any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, see . + +# As a special exception to the GNU General Public License, if you +# distribute this file as part of a program that contains a +# configuration script generated by Autoconf, you may include it under +# the same distribution terms that you use for the rest of that program. + +# This file is maintained in Automake, please report +# bugs to or send patches to +# . + +nl=' +' + +# We need space, tab and new line, in precisely that order. Quoting is +# there to prevent tools from complaining about whitespace usage. +IFS=" "" $nl" + +file_conv= + +# func_file_conv build_file lazy +# Convert a $build file to $host form and store it in $file +# Currently only supports Windows hosts. If the determined conversion +# type is listed in (the comma separated) LAZY, no conversion will +# take place. +func_file_conv () +{ + file=$1 + case $file in + / | /[!/]*) # absolute file, and not a UNC file + if test -z "$file_conv"; then + # lazily determine how to convert abs files + case `uname -s` in + MINGW*) + file_conv=mingw + ;; + CYGWIN*) + file_conv=cygwin + ;; + *) + file_conv=wine + ;; + esac + fi + case $file_conv/,$2, in + *,$file_conv,*) + ;; + mingw/*) + file=`cmd //C echo "$file " | sed -e 's/"\(.*\) " *$/\1/'` + ;; + cygwin/*) + file=`cygpath -m "$file" || echo "$file"` + ;; + wine/*) + file=`winepath -w "$file" || echo "$file"` + ;; + esac + ;; + esac +} + +# func_cl_dashL linkdir +# Make cl look for libraries in LINKDIR +func_cl_dashL () +{ + func_file_conv "$1" + if test -z "$lib_path"; then + lib_path=$file + else + lib_path="$lib_path;$file" + fi + linker_opts="$linker_opts -LIBPATH:$file" +} + +# func_cl_dashl library +# Do a library search-path lookup for cl +func_cl_dashl () +{ + lib=$1 + found=no + save_IFS=$IFS + IFS=';' + for dir in $lib_path $LIB + do + IFS=$save_IFS + if $shared && test -f "$dir/$lib.dll.lib"; then + found=yes + lib=$dir/$lib.dll.lib + break + fi + if test -f "$dir/$lib.lib"; then + found=yes + lib=$dir/$lib.lib + break + fi + if test -f "$dir/lib$lib.a"; then + found=yes + lib=$dir/lib$lib.a + break + fi + done + IFS=$save_IFS + + if test "$found" != yes; then + lib=$lib.lib + fi +} + +# func_cl_wrapper cl arg... +# Adjust compile command to suit cl +func_cl_wrapper () +{ + # Assume a capable shell + lib_path= + shared=: + linker_opts= + for arg + do + if test -n "$eat"; then + eat= + else + case $1 in + -o) + # configure might choose to run compile as 'compile cc -o foo foo.c'. + eat=1 + case $2 in + *.o | *.[oO][bB][jJ]) + func_file_conv "$2" + set x "$@" -Fo"$file" + shift + ;; + *) + func_file_conv "$2" + set x "$@" -Fe"$file" + shift + ;; + esac + ;; + -I) + eat=1 + func_file_conv "$2" mingw + set x "$@" -I"$file" + shift + ;; + -I*) + func_file_conv "${1#-I}" mingw + set x "$@" -I"$file" + shift + ;; + -l) + eat=1 + func_cl_dashl "$2" + set x "$@" "$lib" + shift + ;; + -l*) + func_cl_dashl "${1#-l}" + set x "$@" "$lib" + shift + ;; + -L) + eat=1 + func_cl_dashL "$2" + ;; + -L*) + func_cl_dashL "${1#-L}" + ;; + -static) + shared=false + ;; + -Wl,*) + arg=${1#-Wl,} + save_ifs="$IFS"; IFS=',' + for flag in $arg; do + IFS="$save_ifs" + linker_opts="$linker_opts $flag" + done + IFS="$save_ifs" + ;; + -Xlinker) + eat=1 + linker_opts="$linker_opts $2" + ;; + -*) + set x "$@" "$1" + shift + ;; + *.cc | *.CC | *.cxx | *.CXX | *.[cC]++) + func_file_conv "$1" + set x "$@" -Tp"$file" + shift + ;; + *.c | *.cpp | *.CPP | *.lib | *.LIB | *.Lib | *.OBJ | *.obj | *.[oO]) + func_file_conv "$1" mingw + set x "$@" "$file" + shift + ;; + *) + set x "$@" "$1" + shift + ;; + esac + fi + shift + done + if test -n "$linker_opts"; then + linker_opts="-link$linker_opts" + fi + exec "$@" $linker_opts + exit 1 +} + +eat= + +case $1 in + '') + echo "$0: No command. Try '$0 --help' for more information." 1>&2 + exit 1; + ;; + -h | --h*) + cat <<\EOF +Usage: compile [--help] [--version] PROGRAM [ARGS] + +Wrapper for compilers which do not understand '-c -o'. +Remove '-o dest.o' from ARGS, run PROGRAM with the remaining +arguments, and rename the output as expected. + +If you are trying to build a whole package this is not the +right script to run: please start by reading the file 'INSTALL'. + +Report bugs to . +EOF + exit $? + ;; + -v | --v*) + echo "compile $scriptversion" + exit $? + ;; + cl | *[/\\]cl | cl.exe | *[/\\]cl.exe ) + func_cl_wrapper "$@" # Doesn't return... + ;; +esac + +ofile= +cfile= + +for arg +do + if test -n "$eat"; then + eat= + else + case $1 in + -o) + # configure might choose to run compile as 'compile cc -o foo foo.c'. + # So we strip '-o arg' only if arg is an object. + eat=1 + case $2 in + *.o | *.obj) + ofile=$2 + ;; + *) + set x "$@" -o "$2" + shift + ;; + esac + ;; + *.c) + cfile=$1 + set x "$@" "$1" + shift + ;; + *) + set x "$@" "$1" + shift + ;; + esac + fi + shift +done + +if test -z "$ofile" || test -z "$cfile"; then + # If no '-o' option was seen then we might have been invoked from a + # pattern rule where we don't need one. That is ok -- this is a + # normal compilation that the losing compiler can handle. If no + # '.c' file was seen then we are probably linking. That is also + # ok. + exec "$@" +fi + +# Name of file we expect compiler to create. +cofile=`echo "$cfile" | sed 's|^.*[\\/]||; s|^[a-zA-Z]:||; s/\.c$/.o/'` + +# Create the lock directory. +# Note: use '[/\\:.-]' here to ensure that we don't use the same name +# that we are using for the .o file. Also, base the name on the expected +# object file name, since that is what matters with a parallel build. +lockdir=`echo "$cofile" | sed -e 's|[/\\:.-]|_|g'`.d +while true; do + if mkdir "$lockdir" >/dev/null 2>&1; then + break + fi + sleep 1 +done +# FIXME: race condition here if user kills between mkdir and trap. +trap "rmdir '$lockdir'; exit 1" 1 2 15 + +# Run the compile. +"$@" +ret=$? + +if test -f "$cofile"; then + test "$cofile" = "$ofile" || mv "$cofile" "$ofile" +elif test -f "${cofile}bj"; then + test "${cofile}bj" = "$ofile" || mv "${cofile}bj" "$ofile" +fi + +rmdir "$lockdir" +exit $ret + +# Local Variables: +# mode: shell-script +# sh-indentation: 2 +# eval: (add-hook 'write-file-hooks 'time-stamp) +# time-stamp-start: "scriptversion=" +# time-stamp-format: "%:y-%02m-%02d.%02H" +# time-stamp-time-zone: "UTC" +# time-stamp-end: "; # UTC" +# End: diff --git a/config.c b/config.c index 7c2af59..4b75f00 100644 --- a/config.c +++ b/config.c @@ -858,7 +858,7 @@ static void sessionsaver_handler(union control *ctrl, dlgparam *dlg, * valid host name in it, then load it and go. */ if (dlg_last_focused(ctrl, dlg) == ssd->listbox && - !conf_launchable(conf)) { + !conf_launchable(conf) && dlg_is_visible(ssd->listbox, dlg)) { Conf *conf2 = conf_new(); bool mbl = false; if (!load_selected_session(ssd, dlg, conf2, &mbl)) { @@ -1899,10 +1899,6 @@ void setup_config_box(struct controlbox *b, bool midsession, HELPCTX(features_retitle), conf_checkbox_handler, I(CONF_no_remote_wintitle)); - ctrl_checkbox(s, "Disable remote-controlled clearing of scrollback", 'e', - HELPCTX(features_clearscroll), - conf_checkbox_handler, - I(CONF_no_remote_clearscroll)); ctrl_radiobuttons(s, "Response to remote title query (SECURITY):", 'q', 3, HELPCTX(features_qtitle), conf_radiobutton_handler, @@ -1910,6 +1906,10 @@ void setup_config_box(struct controlbox *b, bool midsession, "None", I(TITLE_NONE), "Empty string", I(TITLE_EMPTY), "Window title", I(TITLE_REAL), NULL); + ctrl_checkbox(s, "Disable remote-controlled clearing of scrollback", 'e', + HELPCTX(features_clearscroll), + conf_checkbox_handler, + I(CONF_no_remote_clearscroll)); ctrl_checkbox(s, "Disable destructive backspace on server sending ^?",'b', HELPCTX(features_dbackspace), conf_checkbox_handler, I(CONF_no_dbackspace)); @@ -1918,10 +1918,10 @@ void setup_config_box(struct controlbox *b, bool midsession, I(CONF_no_remote_charset)); ctrl_checkbox(s, "Disable Arabic text shaping", 'l', HELPCTX(features_arabicshaping), conf_checkbox_handler, - I(CONF_arabicshaping)); + I(CONF_no_arabicshaping)); ctrl_checkbox(s, "Disable bidirectional text display", 'd', HELPCTX(features_bidi), conf_checkbox_handler, - I(CONF_bidi)); + I(CONF_no_bidi)); /* * The Window panel. @@ -2520,10 +2520,12 @@ void setup_config_box(struct controlbox *b, bool midsession, HELPCTX(ssh_kexlist), kexlist_handler, P(NULL)); c->listbox.height = KEX_MAX; +#ifndef NO_GSSAPI ctrl_checkbox(s, "Attempt GSSAPI key exchange", 'k', HELPCTX(ssh_gssapi), conf_checkbox_handler, I(CONF_try_gssapi_kex)); +#endif s = ctrl_getset(b, "Connection/SSH/Kex", "repeat", "Options controlling key re-exchange"); @@ -2533,11 +2535,13 @@ void setup_config_box(struct controlbox *b, bool midsession, conf_editbox_handler, I(CONF_ssh_rekey_time), I(-1)); +#ifndef NO_GSSAPI ctrl_editbox(s, "Minutes between GSS checks (0 for never)", NO_SHORTCUT, 20, HELPCTX(ssh_kex_repeat), conf_editbox_handler, I(CONF_gssapirekey), I(-1)); +#endif ctrl_editbox(s, "Max data before rekey (0 for no limit)", 'x', 20, HELPCTX(ssh_kex_repeat), conf_editbox_handler, diff --git a/configure b/configure new file mode 100644 index 0000000..599d1e4 --- /dev/null +++ b/configure @@ -0,0 +1,7503 @@ +#! /bin/sh +# Guess values for system-dependent variables and create Makefiles. +# Generated by GNU Autoconf 2.69 for putty 0.72. +# +# +# Copyright (C) 1992-1996, 1998-2012 Free Software Foundation, Inc. +# +# +# This configure script is free software; the Free Software Foundation +# gives unlimited permission to copy, distribute and modify it. +## -------------------- ## +## M4sh Initialization. ## +## -------------------- ## + +# Be more Bourne compatible +DUALCASE=1; export DUALCASE # for MKS sh +if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then : + emulate sh + NULLCMD=: + # Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which + # is contrary to our usage. Disable this feature. + alias -g '${1+"$@"}'='"$@"' + setopt NO_GLOB_SUBST +else + case `(set -o) 2>/dev/null` in #( + *posix*) : + set -o posix ;; #( + *) : + ;; +esac +fi + + +as_nl=' +' +export as_nl +# Printing a long string crashes Solaris 7 /usr/bin/printf. +as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\' +as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo +as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo +# Prefer a ksh shell builtin over an external printf program on Solaris, +# but without wasting forks for bash or zsh. +if test -z "$BASH_VERSION$ZSH_VERSION" \ + && (test "X`print -r -- $as_echo`" = "X$as_echo") 2>/dev/null; then + as_echo='print -r --' + as_echo_n='print -rn --' +elif (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then + as_echo='printf %s\n' + as_echo_n='printf %s' +else + if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then + as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"' + as_echo_n='/usr/ucb/echo -n' + else + as_echo_body='eval expr "X$1" : "X\\(.*\\)"' + as_echo_n_body='eval + arg=$1; + case $arg in #( + *"$as_nl"*) + expr "X$arg" : "X\\(.*\\)$as_nl"; + arg=`expr "X$arg" : ".*$as_nl\\(.*\\)"`;; + esac; + expr "X$arg" : "X\\(.*\\)" | tr -d "$as_nl" + ' + export as_echo_n_body + as_echo_n='sh -c $as_echo_n_body as_echo' + fi + export as_echo_body + as_echo='sh -c $as_echo_body as_echo' +fi + +# The user is always right. +if test "${PATH_SEPARATOR+set}" != set; then + PATH_SEPARATOR=: + (PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 && { + (PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 || + PATH_SEPARATOR=';' + } +fi + + +# IFS +# We need space, tab and new line, in precisely that order. Quoting is +# there to prevent editors from complaining about space-tab. +# (If _AS_PATH_WALK were called with IFS unset, it would disable word +# splitting by setting IFS to empty value.) +IFS=" "" $as_nl" + +# Find who we are. Look in the path if we contain no directory separator. +as_myself= +case $0 in #(( + *[\\/]* ) as_myself=$0 ;; + *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break + done +IFS=$as_save_IFS + + ;; +esac +# We did not find ourselves, most probably we were run as `sh COMMAND' +# in which case we are not to be found in the path. +if test "x$as_myself" = x; then + as_myself=$0 +fi +if test ! -f "$as_myself"; then + $as_echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2 + exit 1 +fi + +# Unset variables that we do not need and which cause bugs (e.g. in +# pre-3.0 UWIN ksh). But do not cause bugs in bash 2.01; the "|| exit 1" +# suppresses any "Segmentation fault" message there. '((' could +# trigger a bug in pdksh 5.2.14. +for as_var in BASH_ENV ENV MAIL MAILPATH +do eval test x\${$as_var+set} = xset \ + && ( (unset $as_var) || exit 1) >/dev/null 2>&1 && unset $as_var || : +done +PS1='$ ' +PS2='> ' +PS4='+ ' + +# NLS nuisances. +LC_ALL=C +export LC_ALL +LANGUAGE=C +export LANGUAGE + +# CDPATH. +(unset CDPATH) >/dev/null 2>&1 && unset CDPATH + +# Use a proper internal environment variable to ensure we don't fall + # into an infinite loop, continuously re-executing ourselves. + if test x"${_as_can_reexec}" != xno && test "x$CONFIG_SHELL" != x; then + _as_can_reexec=no; export _as_can_reexec; + # We cannot yet assume a decent shell, so we have to provide a +# neutralization value for shells without unset; and this also +# works around shells that cannot unset nonexistent variables. +# Preserve -v and -x to the replacement shell. +BASH_ENV=/dev/null +ENV=/dev/null +(unset BASH_ENV) >/dev/null 2>&1 && unset BASH_ENV ENV +case $- in # (((( + *v*x* | *x*v* ) as_opts=-vx ;; + *v* ) as_opts=-v ;; + *x* ) as_opts=-x ;; + * ) as_opts= ;; +esac +exec $CONFIG_SHELL $as_opts "$as_myself" ${1+"$@"} +# Admittedly, this is quite paranoid, since all the known shells bail +# out after a failed `exec'. +$as_echo "$0: could not re-execute with $CONFIG_SHELL" >&2 +as_fn_exit 255 + fi + # We don't want this to propagate to other subprocesses. + { _as_can_reexec=; unset _as_can_reexec;} +if test "x$CONFIG_SHELL" = x; then + as_bourne_compatible="if test -n \"\${ZSH_VERSION+set}\" && (emulate sh) >/dev/null 2>&1; then : + emulate sh + NULLCMD=: + # Pre-4.2 versions of Zsh do word splitting on \${1+\"\$@\"}, which + # is contrary to our usage. Disable this feature. + alias -g '\${1+\"\$@\"}'='\"\$@\"' + setopt NO_GLOB_SUBST +else + case \`(set -o) 2>/dev/null\` in #( + *posix*) : + set -o posix ;; #( + *) : + ;; +esac +fi +" + as_required="as_fn_return () { (exit \$1); } +as_fn_success () { as_fn_return 0; } +as_fn_failure () { as_fn_return 1; } +as_fn_ret_success () { return 0; } +as_fn_ret_failure () { return 1; } + +exitcode=0 +as_fn_success || { exitcode=1; echo as_fn_success failed.; } +as_fn_failure && { exitcode=1; echo as_fn_failure succeeded.; } +as_fn_ret_success || { exitcode=1; echo as_fn_ret_success failed.; } +as_fn_ret_failure && { exitcode=1; echo as_fn_ret_failure succeeded.; } +if ( set x; as_fn_ret_success y && test x = \"\$1\" ); then : + +else + exitcode=1; echo positional parameters were not saved. +fi +test x\$exitcode = x0 || exit 1 +test -x / || exit 1" + as_suggested=" as_lineno_1=";as_suggested=$as_suggested$LINENO;as_suggested=$as_suggested" as_lineno_1a=\$LINENO + as_lineno_2=";as_suggested=$as_suggested$LINENO;as_suggested=$as_suggested" as_lineno_2a=\$LINENO + eval 'test \"x\$as_lineno_1'\$as_run'\" != \"x\$as_lineno_2'\$as_run'\" && + test \"x\`expr \$as_lineno_1'\$as_run' + 1\`\" = \"x\$as_lineno_2'\$as_run'\"' || exit 1 +test \$(( 1 + 1 )) = 2 || exit 1" + if (eval "$as_required") 2>/dev/null; then : + as_have_required=yes +else + as_have_required=no +fi + if test x$as_have_required = xyes && (eval "$as_suggested") 2>/dev/null; then : + +else + as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +as_found=false +for as_dir in /bin$PATH_SEPARATOR/usr/bin$PATH_SEPARATOR$PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + as_found=: + case $as_dir in #( + /*) + for as_base in sh bash ksh sh5; do + # Try only shells that exist, to save several forks. + as_shell=$as_dir/$as_base + if { test -f "$as_shell" || test -f "$as_shell.exe"; } && + { $as_echo "$as_bourne_compatible""$as_required" | as_run=a "$as_shell"; } 2>/dev/null; then : + CONFIG_SHELL=$as_shell as_have_required=yes + if { $as_echo "$as_bourne_compatible""$as_suggested" | as_run=a "$as_shell"; } 2>/dev/null; then : + break 2 +fi +fi + done;; + esac + as_found=false +done +$as_found || { if { test -f "$SHELL" || test -f "$SHELL.exe"; } && + { $as_echo "$as_bourne_compatible""$as_required" | as_run=a "$SHELL"; } 2>/dev/null; then : + CONFIG_SHELL=$SHELL as_have_required=yes +fi; } +IFS=$as_save_IFS + + + if test "x$CONFIG_SHELL" != x; then : + export CONFIG_SHELL + # We cannot yet assume a decent shell, so we have to provide a +# neutralization value for shells without unset; and this also +# works around shells that cannot unset nonexistent variables. +# Preserve -v and -x to the replacement shell. +BASH_ENV=/dev/null +ENV=/dev/null +(unset BASH_ENV) >/dev/null 2>&1 && unset BASH_ENV ENV +case $- in # (((( + *v*x* | *x*v* ) as_opts=-vx ;; + *v* ) as_opts=-v ;; + *x* ) as_opts=-x ;; + * ) as_opts= ;; +esac +exec $CONFIG_SHELL $as_opts "$as_myself" ${1+"$@"} +# Admittedly, this is quite paranoid, since all the known shells bail +# out after a failed `exec'. +$as_echo "$0: could not re-execute with $CONFIG_SHELL" >&2 +exit 255 +fi + + if test x$as_have_required = xno; then : + $as_echo "$0: This script requires a shell more modern than all" + $as_echo "$0: the shells that I found on your system." + if test x${ZSH_VERSION+set} = xset ; then + $as_echo "$0: In particular, zsh $ZSH_VERSION has bugs and should" + $as_echo "$0: be upgraded to zsh 4.3.4 or later." + else + $as_echo "$0: Please tell bug-autoconf@gnu.org about your system, +$0: including any error possibly output before this +$0: message. Then install a modern shell, or manually run +$0: the script under such a shell if you do have one." + fi + exit 1 +fi +fi +fi +SHELL=${CONFIG_SHELL-/bin/sh} +export SHELL +# Unset more variables known to interfere with behavior of common tools. +CLICOLOR_FORCE= GREP_OPTIONS= +unset CLICOLOR_FORCE GREP_OPTIONS + +## --------------------- ## +## M4sh Shell Functions. ## +## --------------------- ## +# as_fn_unset VAR +# --------------- +# Portably unset VAR. +as_fn_unset () +{ + { eval $1=; unset $1;} +} +as_unset=as_fn_unset + +# as_fn_set_status STATUS +# ----------------------- +# Set $? to STATUS, without forking. +as_fn_set_status () +{ + return $1 +} # as_fn_set_status + +# as_fn_exit STATUS +# ----------------- +# Exit the shell with STATUS, even in a "trap 0" or "set -e" context. +as_fn_exit () +{ + set +e + as_fn_set_status $1 + exit $1 +} # as_fn_exit + +# as_fn_mkdir_p +# ------------- +# Create "$as_dir" as a directory, including parents if necessary. +as_fn_mkdir_p () +{ + + case $as_dir in #( + -*) as_dir=./$as_dir;; + esac + test -d "$as_dir" || eval $as_mkdir_p || { + as_dirs= + while :; do + case $as_dir in #( + *\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'( + *) as_qdir=$as_dir;; + esac + as_dirs="'$as_qdir' $as_dirs" + as_dir=`$as_dirname -- "$as_dir" || +$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ + X"$as_dir" : 'X\(//\)[^/]' \| \ + X"$as_dir" : 'X\(//\)$' \| \ + X"$as_dir" : 'X\(/\)' \| . 2>/dev/null || +$as_echo X"$as_dir" | + sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ + s//\1/ + q + } + /^X\(\/\/\)[^/].*/{ + s//\1/ + q + } + /^X\(\/\/\)$/{ + s//\1/ + q + } + /^X\(\/\).*/{ + s//\1/ + q + } + s/.*/./; q'` + test -d "$as_dir" && break + done + test -z "$as_dirs" || eval "mkdir $as_dirs" + } || test -d "$as_dir" || as_fn_error $? "cannot create directory $as_dir" + + +} # as_fn_mkdir_p + +# as_fn_executable_p FILE +# ----------------------- +# Test if FILE is an executable regular file. +as_fn_executable_p () +{ + test -f "$1" && test -x "$1" +} # as_fn_executable_p +# as_fn_append VAR VALUE +# ---------------------- +# Append the text in VALUE to the end of the definition contained in VAR. Take +# advantage of any shell optimizations that allow amortized linear growth over +# repeated appends, instead of the typical quadratic growth present in naive +# implementations. +if (eval "as_var=1; as_var+=2; test x\$as_var = x12") 2>/dev/null; then : + eval 'as_fn_append () + { + eval $1+=\$2 + }' +else + as_fn_append () + { + eval $1=\$$1\$2 + } +fi # as_fn_append + +# as_fn_arith ARG... +# ------------------ +# Perform arithmetic evaluation on the ARGs, and store the result in the +# global $as_val. Take advantage of shells that can avoid forks. The arguments +# must be portable across $(()) and expr. +if (eval "test \$(( 1 + 1 )) = 2") 2>/dev/null; then : + eval 'as_fn_arith () + { + as_val=$(( $* )) + }' +else + as_fn_arith () + { + as_val=`expr "$@" || test $? -eq 1` + } +fi # as_fn_arith + + +# as_fn_error STATUS ERROR [LINENO LOG_FD] +# ---------------------------------------- +# Output "`basename $0`: error: ERROR" to stderr. If LINENO and LOG_FD are +# provided, also output the error to LOG_FD, referencing LINENO. Then exit the +# script with STATUS, using 1 if that was 0. +as_fn_error () +{ + as_status=$1; test $as_status -eq 0 && as_status=1 + if test "$4"; then + as_lineno=${as_lineno-"$3"} as_lineno_stack=as_lineno_stack=$as_lineno_stack + $as_echo "$as_me:${as_lineno-$LINENO}: error: $2" >&$4 + fi + $as_echo "$as_me: error: $2" >&2 + as_fn_exit $as_status +} # as_fn_error + +if expr a : '\(a\)' >/dev/null 2>&1 && + test "X`expr 00001 : '.*\(...\)'`" = X001; then + as_expr=expr +else + as_expr=false +fi + +if (basename -- /) >/dev/null 2>&1 && test "X`basename -- / 2>&1`" = "X/"; then + as_basename=basename +else + as_basename=false +fi + +if (as_dir=`dirname -- /` && test "X$as_dir" = X/) >/dev/null 2>&1; then + as_dirname=dirname +else + as_dirname=false +fi + +as_me=`$as_basename -- "$0" || +$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \ + X"$0" : 'X\(//\)$' \| \ + X"$0" : 'X\(/\)' \| . 2>/dev/null || +$as_echo X/"$0" | + sed '/^.*\/\([^/][^/]*\)\/*$/{ + s//\1/ + q + } + /^X\/\(\/\/\)$/{ + s//\1/ + q + } + /^X\/\(\/\).*/{ + s//\1/ + q + } + s/.*/./; q'` + +# Avoid depending upon Character Ranges. +as_cr_letters='abcdefghijklmnopqrstuvwxyz' +as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ' +as_cr_Letters=$as_cr_letters$as_cr_LETTERS +as_cr_digits='0123456789' +as_cr_alnum=$as_cr_Letters$as_cr_digits + + + as_lineno_1=$LINENO as_lineno_1a=$LINENO + as_lineno_2=$LINENO as_lineno_2a=$LINENO + eval 'test "x$as_lineno_1'$as_run'" != "x$as_lineno_2'$as_run'" && + test "x`expr $as_lineno_1'$as_run' + 1`" = "x$as_lineno_2'$as_run'"' || { + # Blame Lee E. McMahon (1931-1989) for sed's syntax. :-) + sed -n ' + p + /[$]LINENO/= + ' <$as_myself | + sed ' + s/[$]LINENO.*/&-/ + t lineno + b + :lineno + N + :loop + s/[$]LINENO\([^'$as_cr_alnum'_].*\n\)\(.*\)/\2\1\2/ + t loop + s/-\n.*// + ' >$as_me.lineno && + chmod +x "$as_me.lineno" || + { $as_echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2; as_fn_exit 1; } + + # If we had to re-execute with $CONFIG_SHELL, we're ensured to have + # already done that, so ensure we don't try to do so again and fall + # in an infinite loop. This has already happened in practice. + _as_can_reexec=no; export _as_can_reexec + # Don't try to exec as it changes $[0], causing all sort of problems + # (the dirname of $[0] is not the place where we might find the + # original and so on. Autoconf is especially sensitive to this). + . "./$as_me.lineno" + # Exit status is that of the last command. + exit +} + +ECHO_C= ECHO_N= ECHO_T= +case `echo -n x` in #((((( +-n*) + case `echo 'xy\c'` in + *c*) ECHO_T=' ';; # ECHO_T is single tab character. + xy) ECHO_C='\c';; + *) echo `echo ksh88 bug on AIX 6.1` > /dev/null + ECHO_T=' ';; + esac;; +*) + ECHO_N='-n';; +esac + +rm -f conf$$ conf$$.exe conf$$.file +if test -d conf$$.dir; then + rm -f conf$$.dir/conf$$.file +else + rm -f conf$$.dir + mkdir conf$$.dir 2>/dev/null +fi +if (echo >conf$$.file) 2>/dev/null; then + if ln -s conf$$.file conf$$ 2>/dev/null; then + as_ln_s='ln -s' + # ... but there are two gotchas: + # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail. + # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable. + # In both cases, we have to default to `cp -pR'. + ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe || + as_ln_s='cp -pR' + elif ln conf$$.file conf$$ 2>/dev/null; then + as_ln_s=ln + else + as_ln_s='cp -pR' + fi +else + as_ln_s='cp -pR' +fi +rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file +rmdir conf$$.dir 2>/dev/null + +if mkdir -p . 2>/dev/null; then + as_mkdir_p='mkdir -p "$as_dir"' +else + test -d ./-p && rmdir ./-p + as_mkdir_p=false +fi + +as_test_x='test -x' +as_executable_p=as_fn_executable_p + +# Sed expression to map a string onto a valid CPP name. +as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'" + +# Sed expression to map a string onto a valid variable name. +as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'" + + +test -n "$DJDIR" || exec 7<&0 &1 + +# Name of the host. +# hostname on some systems (SVR3.2, old GNU/Linux) returns a bogus exit status, +# so uname gets run too. +ac_hostname=`(hostname || uname -n) 2>/dev/null | sed 1q` + +# +# Initializations. +# +ac_default_prefix=/usr/local +ac_clean_files= +ac_config_libobj_dir=. +LIBOBJS= +cross_compiling=no +subdirs= +MFLAGS= +MAKEFLAGS= + +# Identity of this package. +PACKAGE_NAME='putty' +PACKAGE_TARNAME='putty' +PACKAGE_VERSION='0.72' +PACKAGE_STRING='putty 0.72' +PACKAGE_BUGREPORT='' +PACKAGE_URL='' + +# Factoring default headers for most tests. +ac_includes_default="\ +#include +#ifdef HAVE_SYS_TYPES_H +# include +#endif +#ifdef HAVE_SYS_STAT_H +# include +#endif +#ifdef STDC_HEADERS +# include +# include +#else +# ifdef HAVE_STDLIB_H +# include +# endif +#endif +#ifdef HAVE_STRING_H +# if !defined STDC_HEADERS && defined HAVE_MEMORY_H +# include +# endif +# include +#endif +#ifdef HAVE_STRINGS_H +# include +#endif +#ifdef HAVE_INTTYPES_H +# include +#endif +#ifdef HAVE_STDINT_H +# include +#endif +#ifdef HAVE_UNISTD_H +# include +#endif" + +ac_subst_vars='am__EXEEXT_FALSE +am__EXEEXT_TRUE +LTLIBOBJS +LIBOBJS +WARNINGOPTS +EGREP +GREP +CPP +HAVE_GTK_FALSE +HAVE_GTK_TRUE +GTK1_CONFIG +GTK_LIBS +GTK_CFLAGS +PKG_CONFIG_LIBDIR +PKG_CONFIG_PATH +PKG_CONFIG +HAVE_QUARTZ_FALSE +HAVE_QUARTZ_TRUE +AUTO_GIT_COMMIT_FALSE +AUTO_GIT_COMMIT_TRUE +SETID_MODE +SETID_CMD +HAVE_SETID_CMD_FALSE +HAVE_SETID_CMD_TRUE +am__fastdepCC_FALSE +am__fastdepCC_TRUE +CCDEPMODE +am__nodep +AMDEPBACKSLASH +AMDEP_FALSE +AMDEP_TRUE +am__quote +am__include +DEPDIR +OBJEXT +EXEEXT +ac_ct_CC +CPPFLAGS +LDFLAGS +CFLAGS +CC +ac_ct_AR +AR +RANLIB +AM_BACKSLASH +AM_DEFAULT_VERBOSITY +AM_DEFAULT_V +AM_V +am__untar +am__tar +AMTAR +am__leading_dot +SET_MAKE +AWK +mkdir_p +MKDIR_P +INSTALL_STRIP_PROGRAM +STRIP +install_sh +MAKEINFO +AUTOHEADER +AUTOMAKE +AUTOCONF +ACLOCAL +VERSION +PACKAGE +CYGPATH_W +am__isrc +INSTALL_DATA +INSTALL_SCRIPT +INSTALL_PROGRAM +target_alias +host_alias +build_alias +LIBS +ECHO_T +ECHO_N +ECHO_C +DEFS +mandir +localedir +libdir +psdir +pdfdir +dvidir +htmldir +infodir +docdir +oldincludedir +includedir +runstatedir +localstatedir +sharedstatedir +sysconfdir +datadir +datarootdir +libexecdir +sbindir +bindir +program_transform_name +prefix +exec_prefix +PACKAGE_URL +PACKAGE_BUGREPORT +PACKAGE_STRING +PACKAGE_VERSION +PACKAGE_TARNAME +PACKAGE_NAME +PATH_SEPARATOR +SHELL' +ac_subst_files='' +ac_user_opts=' +enable_option_checking +enable_silent_rules +enable_dependency_tracking +enable_setuid +enable_setgid +enable_git_commit +with_gssapi +with_quartz +with_gtk +enable_gtktest +' + ac_precious_vars='build_alias +host_alias +target_alias +CC +CFLAGS +LDFLAGS +LIBS +CPPFLAGS +PKG_CONFIG +PKG_CONFIG_PATH +PKG_CONFIG_LIBDIR +CPP' + + +# Initialize some variables set by options. +ac_init_help= +ac_init_version=false +ac_unrecognized_opts= +ac_unrecognized_sep= +# The variables have the same names as the options, with +# dashes changed to underlines. +cache_file=/dev/null +exec_prefix=NONE +no_create= +no_recursion= +prefix=NONE +program_prefix=NONE +program_suffix=NONE +program_transform_name=s,x,x, +silent= +site= +srcdir= +verbose= +x_includes=NONE +x_libraries=NONE + +# Installation directory options. +# These are left unexpanded so users can "make install exec_prefix=/foo" +# and all the variables that are supposed to be based on exec_prefix +# by default will actually change. +# Use braces instead of parens because sh, perl, etc. also accept them. +# (The list follows the same order as the GNU Coding Standards.) +bindir='${exec_prefix}/bin' +sbindir='${exec_prefix}/sbin' +libexecdir='${exec_prefix}/libexec' +datarootdir='${prefix}/share' +datadir='${datarootdir}' +sysconfdir='${prefix}/etc' +sharedstatedir='${prefix}/com' +localstatedir='${prefix}/var' +runstatedir='${localstatedir}/run' +includedir='${prefix}/include' +oldincludedir='/usr/include' +docdir='${datarootdir}/doc/${PACKAGE_TARNAME}' +infodir='${datarootdir}/info' +htmldir='${docdir}' +dvidir='${docdir}' +pdfdir='${docdir}' +psdir='${docdir}' +libdir='${exec_prefix}/lib' +localedir='${datarootdir}/locale' +mandir='${datarootdir}/man' + +ac_prev= +ac_dashdash= +for ac_option +do + # If the previous option needs an argument, assign it. + if test -n "$ac_prev"; then + eval $ac_prev=\$ac_option + ac_prev= + continue + fi + + case $ac_option in + *=?*) ac_optarg=`expr "X$ac_option" : '[^=]*=\(.*\)'` ;; + *=) ac_optarg= ;; + *) ac_optarg=yes ;; + esac + + # Accept the important Cygnus configure options, so we can diagnose typos. + + case $ac_dashdash$ac_option in + --) + ac_dashdash=yes ;; + + -bindir | --bindir | --bindi | --bind | --bin | --bi) + ac_prev=bindir ;; + -bindir=* | --bindir=* | --bindi=* | --bind=* | --bin=* | --bi=*) + bindir=$ac_optarg ;; + + -build | --build | --buil | --bui | --bu) + ac_prev=build_alias ;; + -build=* | --build=* | --buil=* | --bui=* | --bu=*) + build_alias=$ac_optarg ;; + + -cache-file | --cache-file | --cache-fil | --cache-fi \ + | --cache-f | --cache- | --cache | --cach | --cac | --ca | --c) + ac_prev=cache_file ;; + -cache-file=* | --cache-file=* | --cache-fil=* | --cache-fi=* \ + | --cache-f=* | --cache-=* | --cache=* | --cach=* | --cac=* | --ca=* | --c=*) + cache_file=$ac_optarg ;; + + --config-cache | -C) + cache_file=config.cache ;; + + -datadir | --datadir | --datadi | --datad) + ac_prev=datadir ;; + -datadir=* | --datadir=* | --datadi=* | --datad=*) + datadir=$ac_optarg ;; + + -datarootdir | --datarootdir | --datarootdi | --datarootd | --dataroot \ + | --dataroo | --dataro | --datar) + ac_prev=datarootdir ;; + -datarootdir=* | --datarootdir=* | --datarootdi=* | --datarootd=* \ + | --dataroot=* | --dataroo=* | --dataro=* | --datar=*) + datarootdir=$ac_optarg ;; + + -disable-* | --disable-*) + ac_useropt=`expr "x$ac_option" : 'x-*disable-\(.*\)'` + # Reject names that are not valid shell variable names. + expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null && + as_fn_error $? "invalid feature name: $ac_useropt" + ac_useropt_orig=$ac_useropt + ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'` + case $ac_user_opts in + *" +"enable_$ac_useropt" +"*) ;; + *) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--disable-$ac_useropt_orig" + ac_unrecognized_sep=', ';; + esac + eval enable_$ac_useropt=no ;; + + -docdir | --docdir | --docdi | --doc | --do) + ac_prev=docdir ;; + -docdir=* | --docdir=* | --docdi=* | --doc=* | --do=*) + docdir=$ac_optarg ;; + + -dvidir | --dvidir | --dvidi | --dvid | --dvi | --dv) + ac_prev=dvidir ;; + -dvidir=* | --dvidir=* | --dvidi=* | --dvid=* | --dvi=* | --dv=*) + dvidir=$ac_optarg ;; + + -enable-* | --enable-*) + ac_useropt=`expr "x$ac_option" : 'x-*enable-\([^=]*\)'` + # Reject names that are not valid shell variable names. + expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null && + as_fn_error $? "invalid feature name: $ac_useropt" + ac_useropt_orig=$ac_useropt + ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'` + case $ac_user_opts in + *" +"enable_$ac_useropt" +"*) ;; + *) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--enable-$ac_useropt_orig" + ac_unrecognized_sep=', ';; + esac + eval enable_$ac_useropt=\$ac_optarg ;; + + -exec-prefix | --exec_prefix | --exec-prefix | --exec-prefi \ + | --exec-pref | --exec-pre | --exec-pr | --exec-p | --exec- \ + | --exec | --exe | --ex) + ac_prev=exec_prefix ;; + -exec-prefix=* | --exec_prefix=* | --exec-prefix=* | --exec-prefi=* \ + | --exec-pref=* | --exec-pre=* | --exec-pr=* | --exec-p=* | --exec-=* \ + | --exec=* | --exe=* | --ex=*) + exec_prefix=$ac_optarg ;; + + -gas | --gas | --ga | --g) + # Obsolete; use --with-gas. + with_gas=yes ;; + + -help | --help | --hel | --he | -h) + ac_init_help=long ;; + -help=r* | --help=r* | --hel=r* | --he=r* | -hr*) + ac_init_help=recursive ;; + -help=s* | --help=s* | --hel=s* | --he=s* | -hs*) + ac_init_help=short ;; + + -host | --host | --hos | --ho) + ac_prev=host_alias ;; + -host=* | --host=* | --hos=* | --ho=*) + host_alias=$ac_optarg ;; + + -htmldir | --htmldir | --htmldi | --htmld | --html | --htm | --ht) + ac_prev=htmldir ;; + -htmldir=* | --htmldir=* | --htmldi=* | --htmld=* | --html=* | --htm=* \ + | --ht=*) + htmldir=$ac_optarg ;; + + -includedir | --includedir | --includedi | --included | --include \ + | --includ | --inclu | --incl | --inc) + ac_prev=includedir ;; + -includedir=* | --includedir=* | --includedi=* | --included=* | --include=* \ + | --includ=* | --inclu=* | --incl=* | --inc=*) + includedir=$ac_optarg ;; + + -infodir | --infodir | --infodi | --infod | --info | --inf) + ac_prev=infodir ;; + -infodir=* | --infodir=* | --infodi=* | --infod=* | --info=* | --inf=*) + infodir=$ac_optarg ;; + + -libdir | --libdir | --libdi | --libd) + ac_prev=libdir ;; + -libdir=* | --libdir=* | --libdi=* | --libd=*) + libdir=$ac_optarg ;; + + -libexecdir | --libexecdir | --libexecdi | --libexecd | --libexec \ + | --libexe | --libex | --libe) + ac_prev=libexecdir ;; + -libexecdir=* | --libexecdir=* | --libexecdi=* | --libexecd=* | --libexec=* \ + | --libexe=* | --libex=* | --libe=*) + libexecdir=$ac_optarg ;; + + -localedir | --localedir | --localedi | --localed | --locale) + ac_prev=localedir ;; + -localedir=* | --localedir=* | --localedi=* | --localed=* | --locale=*) + localedir=$ac_optarg ;; + + -localstatedir | --localstatedir | --localstatedi | --localstated \ + | --localstate | --localstat | --localsta | --localst | --locals) + ac_prev=localstatedir ;; + -localstatedir=* | --localstatedir=* | --localstatedi=* | --localstated=* \ + | --localstate=* | --localstat=* | --localsta=* | --localst=* | --locals=*) + localstatedir=$ac_optarg ;; + + -mandir | --mandir | --mandi | --mand | --man | --ma | --m) + ac_prev=mandir ;; + -mandir=* | --mandir=* | --mandi=* | --mand=* | --man=* | --ma=* | --m=*) + mandir=$ac_optarg ;; + + -nfp | --nfp | --nf) + # Obsolete; use --without-fp. + with_fp=no ;; + + -no-create | --no-create | --no-creat | --no-crea | --no-cre \ + | --no-cr | --no-c | -n) + no_create=yes ;; + + -no-recursion | --no-recursion | --no-recursio | --no-recursi \ + | --no-recurs | --no-recur | --no-recu | --no-rec | --no-re | --no-r) + no_recursion=yes ;; + + -oldincludedir | --oldincludedir | --oldincludedi | --oldincluded \ + | --oldinclude | --oldinclud | --oldinclu | --oldincl | --oldinc \ + | --oldin | --oldi | --old | --ol | --o) + ac_prev=oldincludedir ;; + -oldincludedir=* | --oldincludedir=* | --oldincludedi=* | --oldincluded=* \ + | --oldinclude=* | --oldinclud=* | --oldinclu=* | --oldincl=* | --oldinc=* \ + | --oldin=* | --oldi=* | --old=* | --ol=* | --o=*) + oldincludedir=$ac_optarg ;; + + -prefix | --prefix | --prefi | --pref | --pre | --pr | --p) + ac_prev=prefix ;; + -prefix=* | --prefix=* | --prefi=* | --pref=* | --pre=* | --pr=* | --p=*) + prefix=$ac_optarg ;; + + -program-prefix | --program-prefix | --program-prefi | --program-pref \ + | --program-pre | --program-pr | --program-p) + ac_prev=program_prefix ;; + -program-prefix=* | --program-prefix=* | --program-prefi=* \ + | --program-pref=* | --program-pre=* | --program-pr=* | --program-p=*) + program_prefix=$ac_optarg ;; + + -program-suffix | --program-suffix | --program-suffi | --program-suff \ + | --program-suf | --program-su | --program-s) + ac_prev=program_suffix ;; + -program-suffix=* | --program-suffix=* | --program-suffi=* \ + | --program-suff=* | --program-suf=* | --program-su=* | --program-s=*) + program_suffix=$ac_optarg ;; + + -program-transform-name | --program-transform-name \ + | --program-transform-nam | --program-transform-na \ + | --program-transform-n | --program-transform- \ + | --program-transform | --program-transfor \ + | --program-transfo | --program-transf \ + | --program-trans | --program-tran \ + | --progr-tra | --program-tr | --program-t) + ac_prev=program_transform_name ;; + -program-transform-name=* | --program-transform-name=* \ + | --program-transform-nam=* | --program-transform-na=* \ + | --program-transform-n=* | --program-transform-=* \ + | --program-transform=* | --program-transfor=* \ + | --program-transfo=* | --program-transf=* \ + | --program-trans=* | --program-tran=* \ + | --progr-tra=* | --program-tr=* | --program-t=*) + program_transform_name=$ac_optarg ;; + + -pdfdir | --pdfdir | --pdfdi | --pdfd | --pdf | --pd) + ac_prev=pdfdir ;; + -pdfdir=* | --pdfdir=* | --pdfdi=* | --pdfd=* | --pdf=* | --pd=*) + pdfdir=$ac_optarg ;; + + -psdir | --psdir | --psdi | --psd | --ps) + ac_prev=psdir ;; + -psdir=* | --psdir=* | --psdi=* | --psd=* | --ps=*) + psdir=$ac_optarg ;; + + -q | -quiet | --quiet | --quie | --qui | --qu | --q \ + | -silent | --silent | --silen | --sile | --sil) + silent=yes ;; + + -runstatedir | --runstatedir | --runstatedi | --runstated \ + | --runstate | --runstat | --runsta | --runst | --runs \ + | --run | --ru | --r) + ac_prev=runstatedir ;; + -runstatedir=* | --runstatedir=* | --runstatedi=* | --runstated=* \ + | --runstate=* | --runstat=* | --runsta=* | --runst=* | --runs=* \ + | --run=* | --ru=* | --r=*) + runstatedir=$ac_optarg ;; + + -sbindir | --sbindir | --sbindi | --sbind | --sbin | --sbi | --sb) + ac_prev=sbindir ;; + -sbindir=* | --sbindir=* | --sbindi=* | --sbind=* | --sbin=* \ + | --sbi=* | --sb=*) + sbindir=$ac_optarg ;; + + -sharedstatedir | --sharedstatedir | --sharedstatedi \ + | --sharedstated | --sharedstate | --sharedstat | --sharedsta \ + | --sharedst | --shareds | --shared | --share | --shar \ + | --sha | --sh) + ac_prev=sharedstatedir ;; + -sharedstatedir=* | --sharedstatedir=* | --sharedstatedi=* \ + | --sharedstated=* | --sharedstate=* | --sharedstat=* | --sharedsta=* \ + | --sharedst=* | --shareds=* | --shared=* | --share=* | --shar=* \ + | --sha=* | --sh=*) + sharedstatedir=$ac_optarg ;; + + -site | --site | --sit) + ac_prev=site ;; + -site=* | --site=* | --sit=*) + site=$ac_optarg ;; + + -srcdir | --srcdir | --srcdi | --srcd | --src | --sr) + ac_prev=srcdir ;; + -srcdir=* | --srcdir=* | --srcdi=* | --srcd=* | --src=* | --sr=*) + srcdir=$ac_optarg ;; + + -sysconfdir | --sysconfdir | --sysconfdi | --sysconfd | --sysconf \ + | --syscon | --sysco | --sysc | --sys | --sy) + ac_prev=sysconfdir ;; + -sysconfdir=* | --sysconfdir=* | --sysconfdi=* | --sysconfd=* | --sysconf=* \ + | --syscon=* | --sysco=* | --sysc=* | --sys=* | --sy=*) + sysconfdir=$ac_optarg ;; + + -target | --target | --targe | --targ | --tar | --ta | --t) + ac_prev=target_alias ;; + -target=* | --target=* | --targe=* | --targ=* | --tar=* | --ta=* | --t=*) + target_alias=$ac_optarg ;; + + -v | -verbose | --verbose | --verbos | --verbo | --verb) + verbose=yes ;; + + -version | --version | --versio | --versi | --vers | -V) + ac_init_version=: ;; + + -with-* | --with-*) + ac_useropt=`expr "x$ac_option" : 'x-*with-\([^=]*\)'` + # Reject names that are not valid shell variable names. + expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null && + as_fn_error $? "invalid package name: $ac_useropt" + ac_useropt_orig=$ac_useropt + ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'` + case $ac_user_opts in + *" +"with_$ac_useropt" +"*) ;; + *) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--with-$ac_useropt_orig" + ac_unrecognized_sep=', ';; + esac + eval with_$ac_useropt=\$ac_optarg ;; + + -without-* | --without-*) + ac_useropt=`expr "x$ac_option" : 'x-*without-\(.*\)'` + # Reject names that are not valid shell variable names. + expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null && + as_fn_error $? "invalid package name: $ac_useropt" + ac_useropt_orig=$ac_useropt + ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'` + case $ac_user_opts in + *" +"with_$ac_useropt" +"*) ;; + *) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--without-$ac_useropt_orig" + ac_unrecognized_sep=', ';; + esac + eval with_$ac_useropt=no ;; + + --x) + # Obsolete; use --with-x. + with_x=yes ;; + + -x-includes | --x-includes | --x-include | --x-includ | --x-inclu \ + | --x-incl | --x-inc | --x-in | --x-i) + ac_prev=x_includes ;; + -x-includes=* | --x-includes=* | --x-include=* | --x-includ=* | --x-inclu=* \ + | --x-incl=* | --x-inc=* | --x-in=* | --x-i=*) + x_includes=$ac_optarg ;; + + -x-libraries | --x-libraries | --x-librarie | --x-librari \ + | --x-librar | --x-libra | --x-libr | --x-lib | --x-li | --x-l) + ac_prev=x_libraries ;; + -x-libraries=* | --x-libraries=* | --x-librarie=* | --x-librari=* \ + | --x-librar=* | --x-libra=* | --x-libr=* | --x-lib=* | --x-li=* | --x-l=*) + x_libraries=$ac_optarg ;; + + -*) as_fn_error $? "unrecognized option: \`$ac_option' +Try \`$0 --help' for more information" + ;; + + *=*) + ac_envvar=`expr "x$ac_option" : 'x\([^=]*\)='` + # Reject names that are not valid shell variable names. + case $ac_envvar in #( + '' | [0-9]* | *[!_$as_cr_alnum]* ) + as_fn_error $? "invalid variable name: \`$ac_envvar'" ;; + esac + eval $ac_envvar=\$ac_optarg + export $ac_envvar ;; + + *) + # FIXME: should be removed in autoconf 3.0. + $as_echo "$as_me: WARNING: you should use --build, --host, --target" >&2 + expr "x$ac_option" : ".*[^-._$as_cr_alnum]" >/dev/null && + $as_echo "$as_me: WARNING: invalid host type: $ac_option" >&2 + : "${build_alias=$ac_option} ${host_alias=$ac_option} ${target_alias=$ac_option}" + ;; + + esac +done + +if test -n "$ac_prev"; then + ac_option=--`echo $ac_prev | sed 's/_/-/g'` + as_fn_error $? "missing argument to $ac_option" +fi + +if test -n "$ac_unrecognized_opts"; then + case $enable_option_checking in + no) ;; + fatal) as_fn_error $? "unrecognized options: $ac_unrecognized_opts" ;; + *) $as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2 ;; + esac +fi + +# Check all directory arguments for consistency. +for ac_var in exec_prefix prefix bindir sbindir libexecdir datarootdir \ + datadir sysconfdir sharedstatedir localstatedir includedir \ + oldincludedir docdir infodir htmldir dvidir pdfdir psdir \ + libdir localedir mandir runstatedir +do + eval ac_val=\$$ac_var + # Remove trailing slashes. + case $ac_val in + */ ) + ac_val=`expr "X$ac_val" : 'X\(.*[^/]\)' \| "X$ac_val" : 'X\(.*\)'` + eval $ac_var=\$ac_val;; + esac + # Be sure to have absolute directory names. + case $ac_val in + [\\/$]* | ?:[\\/]* ) continue;; + NONE | '' ) case $ac_var in *prefix ) continue;; esac;; + esac + as_fn_error $? "expected an absolute directory name for --$ac_var: $ac_val" +done + +# There might be people who depend on the old broken behavior: `$host' +# used to hold the argument of --host etc. +# FIXME: To remove some day. +build=$build_alias +host=$host_alias +target=$target_alias + +# FIXME: To remove some day. +if test "x$host_alias" != x; then + if test "x$build_alias" = x; then + cross_compiling=maybe + elif test "x$build_alias" != "x$host_alias"; then + cross_compiling=yes + fi +fi + +ac_tool_prefix= +test -n "$host_alias" && ac_tool_prefix=$host_alias- + +test "$silent" = yes && exec 6>/dev/null + + +ac_pwd=`pwd` && test -n "$ac_pwd" && +ac_ls_di=`ls -di .` && +ac_pwd_ls_di=`cd "$ac_pwd" && ls -di .` || + as_fn_error $? "working directory cannot be determined" +test "X$ac_ls_di" = "X$ac_pwd_ls_di" || + as_fn_error $? "pwd does not report name of working directory" + + +# Find the source files, if location was not specified. +if test -z "$srcdir"; then + ac_srcdir_defaulted=yes + # Try the directory containing this script, then the parent directory. + ac_confdir=`$as_dirname -- "$as_myself" || +$as_expr X"$as_myself" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ + X"$as_myself" : 'X\(//\)[^/]' \| \ + X"$as_myself" : 'X\(//\)$' \| \ + X"$as_myself" : 'X\(/\)' \| . 2>/dev/null || +$as_echo X"$as_myself" | + sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ + s//\1/ + q + } + /^X\(\/\/\)[^/].*/{ + s//\1/ + q + } + /^X\(\/\/\)$/{ + s//\1/ + q + } + /^X\(\/\).*/{ + s//\1/ + q + } + s/.*/./; q'` + srcdir=$ac_confdir + if test ! -r "$srcdir/$ac_unique_file"; then + srcdir=.. + fi +else + ac_srcdir_defaulted=no +fi +if test ! -r "$srcdir/$ac_unique_file"; then + test "$ac_srcdir_defaulted" = yes && srcdir="$ac_confdir or .." + as_fn_error $? "cannot find sources ($ac_unique_file) in $srcdir" +fi +ac_msg="sources are in $srcdir, but \`cd $srcdir' does not work" +ac_abs_confdir=`( + cd "$srcdir" && test -r "./$ac_unique_file" || as_fn_error $? "$ac_msg" + pwd)` +# When building in place, set srcdir=. +if test "$ac_abs_confdir" = "$ac_pwd"; then + srcdir=. +fi +# Remove unnecessary trailing slashes from srcdir. +# Double slashes in file names in object file debugging info +# mess up M-x gdb in Emacs. +case $srcdir in +*/) srcdir=`expr "X$srcdir" : 'X\(.*[^/]\)' \| "X$srcdir" : 'X\(.*\)'`;; +esac +for ac_var in $ac_precious_vars; do + eval ac_env_${ac_var}_set=\${${ac_var}+set} + eval ac_env_${ac_var}_value=\$${ac_var} + eval ac_cv_env_${ac_var}_set=\${${ac_var}+set} + eval ac_cv_env_${ac_var}_value=\$${ac_var} +done + +# +# Report the --help message. +# +if test "$ac_init_help" = "long"; then + # Omit some internal or obsolete options to make the list less imposing. + # This message is too long to be a string in the A/UX 3.1 sh. + cat <<_ACEOF +\`configure' configures putty 0.72 to adapt to many kinds of systems. + +Usage: $0 [OPTION]... [VAR=VALUE]... + +To assign environment variables (e.g., CC, CFLAGS...), specify them as +VAR=VALUE. See below for descriptions of some of the useful variables. + +Defaults for the options are specified in brackets. + +Configuration: + -h, --help display this help and exit + --help=short display options specific to this package + --help=recursive display the short help of all the included packages + -V, --version display version information and exit + -q, --quiet, --silent do not print \`checking ...' messages + --cache-file=FILE cache test results in FILE [disabled] + -C, --config-cache alias for \`--cache-file=config.cache' + -n, --no-create do not create output files + --srcdir=DIR find the sources in DIR [configure dir or \`..'] + +Installation directories: + --prefix=PREFIX install architecture-independent files in PREFIX + [$ac_default_prefix] + --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX + [PREFIX] + +By default, \`make install' will install all the files in +\`$ac_default_prefix/bin', \`$ac_default_prefix/lib' etc. You can specify +an installation prefix other than \`$ac_default_prefix' using \`--prefix', +for instance \`--prefix=\$HOME'. + +For better control, use the options below. + +Fine tuning of the installation directories: + --bindir=DIR user executables [EPREFIX/bin] + --sbindir=DIR system admin executables [EPREFIX/sbin] + --libexecdir=DIR program executables [EPREFIX/libexec] + --sysconfdir=DIR read-only single-machine data [PREFIX/etc] + --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] + --localstatedir=DIR modifiable single-machine data [PREFIX/var] + --runstatedir=DIR modifiable per-process data [LOCALSTATEDIR/run] + --libdir=DIR object code libraries [EPREFIX/lib] + --includedir=DIR C header files [PREFIX/include] + --oldincludedir=DIR C header files for non-gcc [/usr/include] + --datarootdir=DIR read-only arch.-independent data root [PREFIX/share] + --datadir=DIR read-only architecture-independent data [DATAROOTDIR] + --infodir=DIR info documentation [DATAROOTDIR/info] + --localedir=DIR locale-dependent data [DATAROOTDIR/locale] + --mandir=DIR man documentation [DATAROOTDIR/man] + --docdir=DIR documentation root [DATAROOTDIR/doc/putty] + --htmldir=DIR html documentation [DOCDIR] + --dvidir=DIR dvi documentation [DOCDIR] + --pdfdir=DIR pdf documentation [DOCDIR] + --psdir=DIR ps documentation [DOCDIR] +_ACEOF + + cat <<\_ACEOF + +Program names: + --program-prefix=PREFIX prepend PREFIX to installed program names + --program-suffix=SUFFIX append SUFFIX to installed program names + --program-transform-name=PROGRAM run sed PROGRAM on installed program names +_ACEOF +fi + +if test -n "$ac_init_help"; then + case $ac_init_help in + short | recursive ) echo "Configuration of putty 0.72:";; + esac + cat <<\_ACEOF + +Optional Features: + --disable-option-checking ignore unrecognized --enable/--with options + --disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no) + --enable-FEATURE[=ARG] include FEATURE [ARG=yes] + --enable-silent-rules less verbose build output (undo: "make V=1") + --disable-silent-rules verbose build output (undo: "make V=0") + --enable-dependency-tracking + do not reject slow dependency extractors + --disable-dependency-tracking + speeds up one-time build + --enable-setuid=USER make pterm setuid to a given user + --enable-setgid=GROUP make pterm setgid to a given group + --disable-git-commit disable embedding current git HEAD in binaries + --disable-gtktest do not try to compile and run a test GTK+ program + +Optional Packages: + --with-PACKAGE[=ARG] use PACKAGE [ARG=yes] + --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no) + --without-gssapi disable GSSAPI support + --with-quartz build for the MacOS Quartz GTK back end + --with-gtk=VER specify GTK version to use (`1', `2' or `3') + --without-gtk do not use GTK (build command-line tools only) + +Some influential environment variables: + CC C compiler command + CFLAGS C compiler flags + LDFLAGS linker flags, e.g. -L if you have libraries in a + nonstandard directory + LIBS libraries to pass to the linker, e.g. -l + CPPFLAGS (Objective) C/C++ preprocessor flags, e.g. -I if + you have headers in a nonstandard directory + PKG_CONFIG path to pkg-config utility + PKG_CONFIG_PATH + directories to add to pkg-config's search path + PKG_CONFIG_LIBDIR + path overriding pkg-config's built-in search path + CPP C preprocessor + +Use these variables to override the choices made by `configure' or to help +it to find libraries and programs with nonstandard names/locations. + +Report bugs to the package provider. +_ACEOF +ac_status=$? +fi + +if test "$ac_init_help" = "recursive"; then + # If there are subdirs, report their specific --help. + for ac_dir in : $ac_subdirs_all; do test "x$ac_dir" = x: && continue + test -d "$ac_dir" || + { cd "$srcdir" && ac_pwd=`pwd` && srcdir=. && test -d "$ac_dir"; } || + continue + ac_builddir=. + +case "$ac_dir" in +.) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;; +*) + ac_dir_suffix=/`$as_echo "$ac_dir" | sed 's|^\.[\\/]||'` + # A ".." for each directory in $ac_dir_suffix. + ac_top_builddir_sub=`$as_echo "$ac_dir_suffix" | sed 's|/[^\\/]*|/..|g;s|/||'` + case $ac_top_builddir_sub in + "") ac_top_builddir_sub=. ac_top_build_prefix= ;; + *) ac_top_build_prefix=$ac_top_builddir_sub/ ;; + esac ;; +esac +ac_abs_top_builddir=$ac_pwd +ac_abs_builddir=$ac_pwd$ac_dir_suffix +# for backward compatibility: +ac_top_builddir=$ac_top_build_prefix + +case $srcdir in + .) # We are building in place. + ac_srcdir=. + ac_top_srcdir=$ac_top_builddir_sub + ac_abs_top_srcdir=$ac_pwd ;; + [\\/]* | ?:[\\/]* ) # Absolute name. + ac_srcdir=$srcdir$ac_dir_suffix; + ac_top_srcdir=$srcdir + ac_abs_top_srcdir=$srcdir ;; + *) # Relative name. + ac_srcdir=$ac_top_build_prefix$srcdir$ac_dir_suffix + ac_top_srcdir=$ac_top_build_prefix$srcdir + ac_abs_top_srcdir=$ac_pwd/$srcdir ;; +esac +ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix + + cd "$ac_dir" || { ac_status=$?; continue; } + # Check for guested configure. + if test -f "$ac_srcdir/configure.gnu"; then + echo && + $SHELL "$ac_srcdir/configure.gnu" --help=recursive + elif test -f "$ac_srcdir/configure"; then + echo && + $SHELL "$ac_srcdir/configure" --help=recursive + else + $as_echo "$as_me: WARNING: no configuration information is in $ac_dir" >&2 + fi || ac_status=$? + cd "$ac_pwd" || { ac_status=$?; break; } + done +fi + +test -n "$ac_init_help" && exit $ac_status +if $ac_init_version; then + cat <<\_ACEOF +putty configure 0.72 +generated by GNU Autoconf 2.69 + +Copyright (C) 2012 Free Software Foundation, Inc. +This configure script is free software; the Free Software Foundation +gives unlimited permission to copy, distribute and modify it. +_ACEOF + exit +fi + +## ------------------------ ## +## Autoconf initialization. ## +## ------------------------ ## + +# ac_fn_c_try_compile LINENO +# -------------------------- +# Try to compile conftest.$ac_ext, and return whether this succeeded. +ac_fn_c_try_compile () +{ + as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack + rm -f conftest.$ac_objext + if { { ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\"" +$as_echo "$ac_try_echo"; } >&5 + (eval "$ac_compile") 2>conftest.err + ac_status=$? + if test -s conftest.err; then + grep -v '^ *+' conftest.err >conftest.er1 + cat conftest.er1 >&5 + mv -f conftest.er1 conftest.err + fi + $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 + test $ac_status = 0; } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest.$ac_objext; then : + ac_retval=0 +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + ac_retval=1 +fi + eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno + as_fn_set_status $ac_retval + +} # ac_fn_c_try_compile + +# ac_fn_c_check_header_compile LINENO HEADER VAR INCLUDES +# ------------------------------------------------------- +# Tests whether HEADER exists and can be compiled using the include files in +# INCLUDES, setting the cache variable VAR accordingly. +ac_fn_c_check_header_compile () +{ + as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack + { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5 +$as_echo_n "checking for $2... " >&6; } +if eval \${$3+:} false; then : + $as_echo_n "(cached) " >&6 +else + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ +$4 +#include <$2> +_ACEOF +if ac_fn_c_try_compile "$LINENO"; then : + eval "$3=yes" +else + eval "$3=no" +fi +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext +fi +eval ac_res=\$$3 + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } + eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno + +} # ac_fn_c_check_header_compile + +# ac_fn_c_try_run LINENO +# ---------------------- +# Try to link conftest.$ac_ext, and return whether this succeeded. Assumes +# that executables *can* be run. +ac_fn_c_try_run () +{ + as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack + if { { ac_try="$ac_link" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\"" +$as_echo "$ac_try_echo"; } >&5 + (eval "$ac_link") 2>&5 + ac_status=$? + $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 + test $ac_status = 0; } && { ac_try='./conftest$ac_exeext' + { { case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\"" +$as_echo "$ac_try_echo"; } >&5 + (eval "$ac_try") 2>&5 + ac_status=$? + $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 + test $ac_status = 0; }; }; then : + ac_retval=0 +else + $as_echo "$as_me: program exited with status $ac_status" >&5 + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + ac_retval=$ac_status +fi + rm -rf conftest.dSYM conftest_ipa8_conftest.oo + eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno + as_fn_set_status $ac_retval + +} # ac_fn_c_try_run + +# ac_fn_c_try_link LINENO +# ----------------------- +# Try to link conftest.$ac_ext, and return whether this succeeded. +ac_fn_c_try_link () +{ + as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack + rm -f conftest.$ac_objext conftest$ac_exeext + if { { ac_try="$ac_link" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\"" +$as_echo "$ac_try_echo"; } >&5 + (eval "$ac_link") 2>conftest.err + ac_status=$? + if test -s conftest.err; then + grep -v '^ *+' conftest.err >conftest.er1 + cat conftest.er1 >&5 + mv -f conftest.er1 conftest.err + fi + $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 + test $ac_status = 0; } && { + test -z "$ac_c_werror_flag" || + test ! -s conftest.err + } && test -s conftest$ac_exeext && { + test "$cross_compiling" = yes || + test -x conftest$ac_exeext + }; then : + ac_retval=0 +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + ac_retval=1 +fi + # Delete the IPA/IPO (Inter Procedural Analysis/Optimization) information + # created by the PGI compiler (conftest_ipa8_conftest.oo), as it would + # interfere with the next link command; also delete a directory that is + # left behind by Apple's compiler. We do this before executing the actions. + rm -rf conftest.dSYM conftest_ipa8_conftest.oo + eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno + as_fn_set_status $ac_retval + +} # ac_fn_c_try_link + +# ac_fn_c_check_func LINENO FUNC VAR +# ---------------------------------- +# Tests whether FUNC exists, setting the cache variable VAR accordingly +ac_fn_c_check_func () +{ + as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack + { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5 +$as_echo_n "checking for $2... " >&6; } +if eval \${$3+:} false; then : + $as_echo_n "(cached) " >&6 +else + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ +/* Define $2 to an innocuous variant, in case declares $2. + For example, HP-UX 11i declares gettimeofday. */ +#define $2 innocuous_$2 + +/* System header to define __stub macros and hopefully few prototypes, + which can conflict with char $2 (); below. + Prefer to if __STDC__ is defined, since + exists even on freestanding compilers. */ + +#ifdef __STDC__ +# include +#else +# include +#endif + +#undef $2 + +/* Override any GCC internal prototype to avoid an error. + Use char because int might match the return type of a GCC + builtin and then its argument prototype would still apply. */ +#ifdef __cplusplus +extern "C" +#endif +char $2 (); +/* The GNU C library defines this for functions which it implements + to always fail with ENOSYS. Some functions are actually named + something starting with __ and the normal name is an alias. */ +#if defined __stub_$2 || defined __stub___$2 +choke me +#endif + +int +main () +{ +return $2 (); + ; + return 0; +} +_ACEOF +if ac_fn_c_try_link "$LINENO"; then : + eval "$3=yes" +else + eval "$3=no" +fi +rm -f core conftest.err conftest.$ac_objext \ + conftest$ac_exeext conftest.$ac_ext +fi +eval ac_res=\$$3 + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } + eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno + +} # ac_fn_c_check_func + +# ac_fn_c_try_cpp LINENO +# ---------------------- +# Try to preprocess conftest.$ac_ext, and return whether this succeeded. +ac_fn_c_try_cpp () +{ + as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack + if { { ac_try="$ac_cpp conftest.$ac_ext" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\"" +$as_echo "$ac_try_echo"; } >&5 + (eval "$ac_cpp conftest.$ac_ext") 2>conftest.err + ac_status=$? + if test -s conftest.err; then + grep -v '^ *+' conftest.err >conftest.er1 + cat conftest.er1 >&5 + mv -f conftest.er1 conftest.err + fi + $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 + test $ac_status = 0; } > conftest.i && { + test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" || + test ! -s conftest.err + }; then : + ac_retval=0 +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + + ac_retval=1 +fi + eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno + as_fn_set_status $ac_retval + +} # ac_fn_c_try_cpp + +# ac_fn_c_check_header_mongrel LINENO HEADER VAR INCLUDES +# ------------------------------------------------------- +# Tests whether HEADER exists, giving a warning if it cannot be compiled using +# the include files in INCLUDES and setting the cache variable VAR +# accordingly. +ac_fn_c_check_header_mongrel () +{ + as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack + if eval \${$3+:} false; then : + { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5 +$as_echo_n "checking for $2... " >&6; } +if eval \${$3+:} false; then : + $as_echo_n "(cached) " >&6 +fi +eval ac_res=\$$3 + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +else + # Is the header compilable? +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking $2 usability" >&5 +$as_echo_n "checking $2 usability... " >&6; } +cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ +$4 +#include <$2> +_ACEOF +if ac_fn_c_try_compile "$LINENO"; then : + ac_header_compiler=yes +else + ac_header_compiler=no +fi +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_header_compiler" >&5 +$as_echo "$ac_header_compiler" >&6; } + +# Is the header present? +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking $2 presence" >&5 +$as_echo_n "checking $2 presence... " >&6; } +cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ +#include <$2> +_ACEOF +if ac_fn_c_try_cpp "$LINENO"; then : + ac_header_preproc=yes +else + ac_header_preproc=no +fi +rm -f conftest.err conftest.i conftest.$ac_ext +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_header_preproc" >&5 +$as_echo "$ac_header_preproc" >&6; } + +# So? What about this header? +case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in #(( + yes:no: ) + { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: accepted by the compiler, rejected by the preprocessor!" >&5 +$as_echo "$as_me: WARNING: $2: accepted by the compiler, rejected by the preprocessor!" >&2;} + { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $2: proceeding with the compiler's result" >&2;} + ;; + no:yes:* ) + { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: present but cannot be compiled" >&5 +$as_echo "$as_me: WARNING: $2: present but cannot be compiled" >&2;} + { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: check for missing prerequisite headers?" >&5 +$as_echo "$as_me: WARNING: $2: check for missing prerequisite headers?" >&2;} + { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: see the Autoconf documentation" >&5 +$as_echo "$as_me: WARNING: $2: see the Autoconf documentation" >&2;} + { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: section \"Present But Cannot Be Compiled\"" >&5 +$as_echo "$as_me: WARNING: $2: section \"Present But Cannot Be Compiled\"" >&2;} + { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: proceeding with the compiler's result" >&5 +$as_echo "$as_me: WARNING: $2: proceeding with the compiler's result" >&2;} + ;; +esac + { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5 +$as_echo_n "checking for $2... " >&6; } +if eval \${$3+:} false; then : + $as_echo_n "(cached) " >&6 +else + eval "$3=\$ac_header_compiler" +fi +eval ac_res=\$$3 + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } +fi + eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno + +} # ac_fn_c_check_header_mongrel + +# ac_fn_c_check_decl LINENO SYMBOL VAR INCLUDES +# --------------------------------------------- +# Tests whether SYMBOL is declared in INCLUDES, setting cache variable VAR +# accordingly. +ac_fn_c_check_decl () +{ + as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack + as_decl_name=`echo $2|sed 's/ *(.*//'` + as_decl_use=`echo $2|sed -e 's/(/((/' -e 's/)/) 0&/' -e 's/,/) 0& (/g'` + { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether $as_decl_name is declared" >&5 +$as_echo_n "checking whether $as_decl_name is declared... " >&6; } +if eval \${$3+:} false; then : + $as_echo_n "(cached) " >&6 +else + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ +$4 +int +main () +{ +#ifndef $as_decl_name +#ifdef __cplusplus + (void) $as_decl_use; +#else + (void) $as_decl_name; +#endif +#endif + + ; + return 0; +} +_ACEOF +if ac_fn_c_try_compile "$LINENO"; then : + eval "$3=yes" +else + eval "$3=no" +fi +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext +fi +eval ac_res=\$$3 + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5 +$as_echo "$ac_res" >&6; } + eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno + +} # ac_fn_c_check_decl +cat >config.log <<_ACEOF +This file contains any messages produced by compilers while +running configure, to aid debugging if configure makes a mistake. + +It was created by putty $as_me 0.72, which was +generated by GNU Autoconf 2.69. Invocation command line was + + $ $0 $@ + +_ACEOF +exec 5>>config.log +{ +cat <<_ASUNAME +## --------- ## +## Platform. ## +## --------- ## + +hostname = `(hostname || uname -n) 2>/dev/null | sed 1q` +uname -m = `(uname -m) 2>/dev/null || echo unknown` +uname -r = `(uname -r) 2>/dev/null || echo unknown` +uname -s = `(uname -s) 2>/dev/null || echo unknown` +uname -v = `(uname -v) 2>/dev/null || echo unknown` + +/usr/bin/uname -p = `(/usr/bin/uname -p) 2>/dev/null || echo unknown` +/bin/uname -X = `(/bin/uname -X) 2>/dev/null || echo unknown` + +/bin/arch = `(/bin/arch) 2>/dev/null || echo unknown` +/usr/bin/arch -k = `(/usr/bin/arch -k) 2>/dev/null || echo unknown` +/usr/convex/getsysinfo = `(/usr/convex/getsysinfo) 2>/dev/null || echo unknown` +/usr/bin/hostinfo = `(/usr/bin/hostinfo) 2>/dev/null || echo unknown` +/bin/machine = `(/bin/machine) 2>/dev/null || echo unknown` +/usr/bin/oslevel = `(/usr/bin/oslevel) 2>/dev/null || echo unknown` +/bin/universe = `(/bin/universe) 2>/dev/null || echo unknown` + +_ASUNAME + +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + $as_echo "PATH: $as_dir" + done +IFS=$as_save_IFS + +} >&5 + +cat >&5 <<_ACEOF + + +## ----------- ## +## Core tests. ## +## ----------- ## + +_ACEOF + + +# Keep a trace of the command line. +# Strip out --no-create and --no-recursion so they do not pile up. +# Strip out --silent because we don't want to record it for future runs. +# Also quote any args containing shell meta-characters. +# Make two passes to allow for proper duplicate-argument suppression. +ac_configure_args= +ac_configure_args0= +ac_configure_args1= +ac_must_keep_next=false +for ac_pass in 1 2 +do + for ac_arg + do + case $ac_arg in + -no-create | --no-c* | -n | -no-recursion | --no-r*) continue ;; + -q | -quiet | --quiet | --quie | --qui | --qu | --q \ + | -silent | --silent | --silen | --sile | --sil) + continue ;; + *\'*) + ac_arg=`$as_echo "$ac_arg" | sed "s/'/'\\\\\\\\''/g"` ;; + esac + case $ac_pass in + 1) as_fn_append ac_configure_args0 " '$ac_arg'" ;; + 2) + as_fn_append ac_configure_args1 " '$ac_arg'" + if test $ac_must_keep_next = true; then + ac_must_keep_next=false # Got value, back to normal. + else + case $ac_arg in + *=* | --config-cache | -C | -disable-* | --disable-* \ + | -enable-* | --enable-* | -gas | --g* | -nfp | --nf* \ + | -q | -quiet | --q* | -silent | --sil* | -v | -verb* \ + | -with-* | --with-* | -without-* | --without-* | --x) + case "$ac_configure_args0 " in + "$ac_configure_args1"*" '$ac_arg' "* ) continue ;; + esac + ;; + -* ) ac_must_keep_next=true ;; + esac + fi + as_fn_append ac_configure_args " '$ac_arg'" + ;; + esac + done +done +{ ac_configure_args0=; unset ac_configure_args0;} +{ ac_configure_args1=; unset ac_configure_args1;} + +# When interrupted or exit'd, cleanup temporary files, and complete +# config.log. We remove comments because anyway the quotes in there +# would cause problems or look ugly. +# WARNING: Use '\'' to represent an apostrophe within the trap. +# WARNING: Do not start the trap code with a newline, due to a FreeBSD 4.0 bug. +trap 'exit_status=$? + # Save into config.log some information that might help in debugging. + { + echo + + $as_echo "## ---------------- ## +## Cache variables. ## +## ---------------- ##" + echo + # The following way of writing the cache mishandles newlines in values, +( + for ac_var in `(set) 2>&1 | sed -n '\''s/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'\''`; do + eval ac_val=\$$ac_var + case $ac_val in #( + *${as_nl}*) + case $ac_var in #( + *_cv_*) { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: cache variable $ac_var contains a newline" >&5 +$as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;; + esac + case $ac_var in #( + _ | IFS | as_nl) ;; #( + BASH_ARGV | BASH_SOURCE) eval $ac_var= ;; #( + *) { eval $ac_var=; unset $ac_var;} ;; + esac ;; + esac + done + (set) 2>&1 | + case $as_nl`(ac_space='\'' '\''; set) 2>&1` in #( + *${as_nl}ac_space=\ *) + sed -n \ + "s/'\''/'\''\\\\'\'''\''/g; + s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='\''\\2'\''/p" + ;; #( + *) + sed -n "/^[_$as_cr_alnum]*_cv_[_$as_cr_alnum]*=/p" + ;; + esac | + sort +) + echo + + $as_echo "## ----------------- ## +## Output variables. ## +## ----------------- ##" + echo + for ac_var in $ac_subst_vars + do + eval ac_val=\$$ac_var + case $ac_val in + *\'\''*) ac_val=`$as_echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;; + esac + $as_echo "$ac_var='\''$ac_val'\''" + done | sort + echo + + if test -n "$ac_subst_files"; then + $as_echo "## ------------------- ## +## File substitutions. ## +## ------------------- ##" + echo + for ac_var in $ac_subst_files + do + eval ac_val=\$$ac_var + case $ac_val in + *\'\''*) ac_val=`$as_echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;; + esac + $as_echo "$ac_var='\''$ac_val'\''" + done | sort + echo + fi + + if test -s confdefs.h; then + $as_echo "## ----------- ## +## confdefs.h. ## +## ----------- ##" + echo + cat confdefs.h + echo + fi + test "$ac_signal" != 0 && + $as_echo "$as_me: caught signal $ac_signal" + $as_echo "$as_me: exit $exit_status" + } >&5 + rm -f core *.core core.conftest.* && + rm -f -r conftest* confdefs* conf$$* $ac_clean_files && + exit $exit_status +' 0 +for ac_signal in 1 2 13 15; do + trap 'ac_signal='$ac_signal'; as_fn_exit 1' $ac_signal +done +ac_signal=0 + +# confdefs.h avoids OS command line length limits that DEFS can exceed. +rm -f -r conftest* confdefs.h + +$as_echo "/* confdefs.h */" > confdefs.h + +# Predefined preprocessor variables. + +cat >>confdefs.h <<_ACEOF +#define PACKAGE_NAME "$PACKAGE_NAME" +_ACEOF + +cat >>confdefs.h <<_ACEOF +#define PACKAGE_TARNAME "$PACKAGE_TARNAME" +_ACEOF + +cat >>confdefs.h <<_ACEOF +#define PACKAGE_VERSION "$PACKAGE_VERSION" +_ACEOF + +cat >>confdefs.h <<_ACEOF +#define PACKAGE_STRING "$PACKAGE_STRING" +_ACEOF + +cat >>confdefs.h <<_ACEOF +#define PACKAGE_BUGREPORT "$PACKAGE_BUGREPORT" +_ACEOF + +cat >>confdefs.h <<_ACEOF +#define PACKAGE_URL "$PACKAGE_URL" +_ACEOF + + +# Let the site file select an alternate cache file if it wants to. +# Prefer an explicitly selected file to automatically selected ones. +ac_site_file1=NONE +ac_site_file2=NONE +if test -n "$CONFIG_SITE"; then + # We do not want a PATH search for config.site. + case $CONFIG_SITE in #(( + -*) ac_site_file1=./$CONFIG_SITE;; + */*) ac_site_file1=$CONFIG_SITE;; + *) ac_site_file1=./$CONFIG_SITE;; + esac +elif test "x$prefix" != xNONE; then + ac_site_file1=$prefix/share/config.site + ac_site_file2=$prefix/etc/config.site +else + ac_site_file1=$ac_default_prefix/share/config.site + ac_site_file2=$ac_default_prefix/etc/config.site +fi +for ac_site_file in "$ac_site_file1" "$ac_site_file2" +do + test "x$ac_site_file" = xNONE && continue + if test /dev/null != "$ac_site_file" && test -r "$ac_site_file"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: loading site script $ac_site_file" >&5 +$as_echo "$as_me: loading site script $ac_site_file" >&6;} + sed 's/^/| /' "$ac_site_file" >&5 + . "$ac_site_file" \ + || { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +as_fn_error $? "failed to load site script $ac_site_file +See \`config.log' for more details" "$LINENO" 5; } + fi +done + +if test -r "$cache_file"; then + # Some versions of bash will fail to source /dev/null (special files + # actually), so we avoid doing that. DJGPP emulates it as a regular file. + if test /dev/null != "$cache_file" && test -f "$cache_file"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: loading cache $cache_file" >&5 +$as_echo "$as_me: loading cache $cache_file" >&6;} + case $cache_file in + [\\/]* | ?:[\\/]* ) . "$cache_file";; + *) . "./$cache_file";; + esac + fi +else + { $as_echo "$as_me:${as_lineno-$LINENO}: creating cache $cache_file" >&5 +$as_echo "$as_me: creating cache $cache_file" >&6;} + >$cache_file +fi + +# Check that the precious variables saved in the cache have kept the same +# value. +ac_cache_corrupted=false +for ac_var in $ac_precious_vars; do + eval ac_old_set=\$ac_cv_env_${ac_var}_set + eval ac_new_set=\$ac_env_${ac_var}_set + eval ac_old_val=\$ac_cv_env_${ac_var}_value + eval ac_new_val=\$ac_env_${ac_var}_value + case $ac_old_set,$ac_new_set in + set,) + { $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5 +$as_echo "$as_me: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&2;} + ac_cache_corrupted=: ;; + ,set) + { $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was not set in the previous run" >&5 +$as_echo "$as_me: error: \`$ac_var' was not set in the previous run" >&2;} + ac_cache_corrupted=: ;; + ,);; + *) + if test "x$ac_old_val" != "x$ac_new_val"; then + # differences in whitespace do not lead to failure. + ac_old_val_w=`echo x $ac_old_val` + ac_new_val_w=`echo x $ac_new_val` + if test "$ac_old_val_w" != "$ac_new_val_w"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' has changed since the previous run:" >&5 +$as_echo "$as_me: error: \`$ac_var' has changed since the previous run:" >&2;} + ac_cache_corrupted=: + else + { $as_echo "$as_me:${as_lineno-$LINENO}: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&5 +$as_echo "$as_me: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&2;} + eval $ac_var=\$ac_old_val + fi + { $as_echo "$as_me:${as_lineno-$LINENO}: former value: \`$ac_old_val'" >&5 +$as_echo "$as_me: former value: \`$ac_old_val'" >&2;} + { $as_echo "$as_me:${as_lineno-$LINENO}: current value: \`$ac_new_val'" >&5 +$as_echo "$as_me: current value: \`$ac_new_val'" >&2;} + fi;; + esac + # Pass precious variables to config.status. + if test "$ac_new_set" = set; then + case $ac_new_val in + *\'*) ac_arg=$ac_var=`$as_echo "$ac_new_val" | sed "s/'/'\\\\\\\\''/g"` ;; + *) ac_arg=$ac_var=$ac_new_val ;; + esac + case " $ac_configure_args " in + *" '$ac_arg' "*) ;; # Avoid dups. Use of quotes ensures accuracy. + *) as_fn_append ac_configure_args " '$ac_arg'" ;; + esac + fi +done +if $ac_cache_corrupted; then + { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} + { $as_echo "$as_me:${as_lineno-$LINENO}: error: changes in the environment can compromise the build" >&5 +$as_echo "$as_me: error: changes in the environment can compromise the build" >&2;} + as_fn_error $? "run \`make distclean' and/or \`rm $cache_file' and start over" "$LINENO" 5 +fi +## -------------------- ## +## Main body of script. ## +## -------------------- ## + +ac_ext=c +ac_cpp='$CPP $CPPFLAGS' +ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' +ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' +ac_compiler_gnu=$ac_cv_c_compiler_gnu + + +ac_config_files="$ac_config_files Makefile" + +ac_config_headers="$ac_config_headers uxconfig.h:uxconfig.in" + +am__api_version='1.15' + +ac_aux_dir= +for ac_dir in "$srcdir" "$srcdir/.." "$srcdir/../.."; do + if test -f "$ac_dir/install-sh"; then + ac_aux_dir=$ac_dir + ac_install_sh="$ac_aux_dir/install-sh -c" + break + elif test -f "$ac_dir/install.sh"; then + ac_aux_dir=$ac_dir + ac_install_sh="$ac_aux_dir/install.sh -c" + break + elif test -f "$ac_dir/shtool"; then + ac_aux_dir=$ac_dir + ac_install_sh="$ac_aux_dir/shtool install -c" + break + fi +done +if test -z "$ac_aux_dir"; then + as_fn_error $? "cannot find install-sh, install.sh, or shtool in \"$srcdir\" \"$srcdir/..\" \"$srcdir/../..\"" "$LINENO" 5 +fi + +# These three variables are undocumented and unsupported, +# and are intended to be withdrawn in a future Autoconf release. +# They can cause serious problems if a builder's source tree is in a directory +# whose full name contains unusual characters. +ac_config_guess="$SHELL $ac_aux_dir/config.guess" # Please don't use this var. +ac_config_sub="$SHELL $ac_aux_dir/config.sub" # Please don't use this var. +ac_configure="$SHELL $ac_aux_dir/configure" # Please don't use this var. + + +# Find a good install program. We prefer a C program (faster), +# so one script is as good as another. But avoid the broken or +# incompatible versions: +# SysV /etc/install, /usr/sbin/install +# SunOS /usr/etc/install +# IRIX /sbin/install +# AIX /bin/install +# AmigaOS /C/install, which installs bootblocks on floppy discs +# AIX 4 /usr/bin/installbsd, which doesn't work without a -g flag +# AFS /usr/afsws/bin/install, which mishandles nonexistent args +# SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff" +# OS/2's system install, which has a completely different semantic +# ./install, which can be erroneously created by make from ./install.sh. +# Reject install programs that cannot install multiple files. +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for a BSD-compatible install" >&5 +$as_echo_n "checking for a BSD-compatible install... " >&6; } +if test -z "$INSTALL"; then +if ${ac_cv_path_install+:} false; then : + $as_echo_n "(cached) " >&6 +else + as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + # Account for people who put trailing slashes in PATH elements. +case $as_dir/ in #(( + ./ | .// | /[cC]/* | \ + /etc/* | /usr/sbin/* | /usr/etc/* | /sbin/* | /usr/afsws/bin/* | \ + ?:[\\/]os2[\\/]install[\\/]* | ?:[\\/]OS2[\\/]INSTALL[\\/]* | \ + /usr/ucb/* ) ;; + *) + # OSF1 and SCO ODT 3.0 have their own names for install. + # Don't use installbsd from OSF since it installs stuff as root + # by default. + for ac_prog in ginstall scoinst install; do + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_prog$ac_exec_ext"; then + if test $ac_prog = install && + grep dspmsg "$as_dir/$ac_prog$ac_exec_ext" >/dev/null 2>&1; then + # AIX install. It has an incompatible calling convention. + : + elif test $ac_prog = install && + grep pwplus "$as_dir/$ac_prog$ac_exec_ext" >/dev/null 2>&1; then + # program-specific install script used by HP pwplus--don't use. + : + else + rm -rf conftest.one conftest.two conftest.dir + echo one > conftest.one + echo two > conftest.two + mkdir conftest.dir + if "$as_dir/$ac_prog$ac_exec_ext" -c conftest.one conftest.two "`pwd`/conftest.dir" && + test -s conftest.one && test -s conftest.two && + test -s conftest.dir/conftest.one && + test -s conftest.dir/conftest.two + then + ac_cv_path_install="$as_dir/$ac_prog$ac_exec_ext -c" + break 3 + fi + fi + fi + done + done + ;; +esac + + done +IFS=$as_save_IFS + +rm -rf conftest.one conftest.two conftest.dir + +fi + if test "${ac_cv_path_install+set}" = set; then + INSTALL=$ac_cv_path_install + else + # As a last resort, use the slow shell script. Don't cache a + # value for INSTALL within a source directory, because that will + # break other packages using the cache if that directory is + # removed, or if the value is a relative name. + INSTALL=$ac_install_sh + fi +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $INSTALL" >&5 +$as_echo "$INSTALL" >&6; } + +# Use test -z because SunOS4 sh mishandles braces in ${var-val}. +# It thinks the first close brace ends the variable substitution. +test -z "$INSTALL_PROGRAM" && INSTALL_PROGRAM='${INSTALL}' + +test -z "$INSTALL_SCRIPT" && INSTALL_SCRIPT='${INSTALL}' + +test -z "$INSTALL_DATA" && INSTALL_DATA='${INSTALL} -m 644' + +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether build environment is sane" >&5 +$as_echo_n "checking whether build environment is sane... " >&6; } +# Reject unsafe characters in $srcdir or the absolute working directory +# name. Accept space and tab only in the latter. +am_lf=' +' +case `pwd` in + *[\\\"\#\$\&\'\`$am_lf]*) + as_fn_error $? "unsafe absolute working directory name" "$LINENO" 5;; +esac +case $srcdir in + *[\\\"\#\$\&\'\`$am_lf\ \ ]*) + as_fn_error $? "unsafe srcdir value: '$srcdir'" "$LINENO" 5;; +esac + +# Do 'set' in a subshell so we don't clobber the current shell's +# arguments. Must try -L first in case configure is actually a +# symlink; some systems play weird games with the mod time of symlinks +# (eg FreeBSD returns the mod time of the symlink's containing +# directory). +if ( + am_has_slept=no + for am_try in 1 2; do + echo "timestamp, slept: $am_has_slept" > conftest.file + set X `ls -Lt "$srcdir/configure" conftest.file 2> /dev/null` + if test "$*" = "X"; then + # -L didn't work. + set X `ls -t "$srcdir/configure" conftest.file` + fi + if test "$*" != "X $srcdir/configure conftest.file" \ + && test "$*" != "X conftest.file $srcdir/configure"; then + + # If neither matched, then we have a broken ls. This can happen + # if, for instance, CONFIG_SHELL is bash and it inherits a + # broken ls alias from the environment. This has actually + # happened. Such a system could not be considered "sane". + as_fn_error $? "ls -t appears to fail. Make sure there is not a broken + alias in your environment" "$LINENO" 5 + fi + if test "$2" = conftest.file || test $am_try -eq 2; then + break + fi + # Just in case. + sleep 1 + am_has_slept=yes + done + test "$2" = conftest.file + ) +then + # Ok. + : +else + as_fn_error $? "newly created file is older than distributed files! +Check your system clock" "$LINENO" 5 +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5 +$as_echo "yes" >&6; } +# If we didn't sleep, we still need to ensure time stamps of config.status and +# generated files are strictly newer. +am_sleep_pid= +if grep 'slept: no' conftest.file >/dev/null 2>&1; then + ( sleep 1 ) & + am_sleep_pid=$! +fi + +rm -f conftest.file + +test "$program_prefix" != NONE && + program_transform_name="s&^&$program_prefix&;$program_transform_name" +# Use a double $ so make ignores it. +test "$program_suffix" != NONE && + program_transform_name="s&\$&$program_suffix&;$program_transform_name" +# Double any \ or $. +# By default was `s,x,x', remove it if useless. +ac_script='s/[\\$]/&&/g;s/;s,x,x,$//' +program_transform_name=`$as_echo "$program_transform_name" | sed "$ac_script"` + +# Expand $ac_aux_dir to an absolute path. +am_aux_dir=`cd "$ac_aux_dir" && pwd` + +if test x"${MISSING+set}" != xset; then + case $am_aux_dir in + *\ * | *\ *) + MISSING="\${SHELL} \"$am_aux_dir/missing\"" ;; + *) + MISSING="\${SHELL} $am_aux_dir/missing" ;; + esac +fi +# Use eval to expand $SHELL +if eval "$MISSING --is-lightweight"; then + am_missing_run="$MISSING " +else + am_missing_run= + { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: 'missing' script is too old or missing" >&5 +$as_echo "$as_me: WARNING: 'missing' script is too old or missing" >&2;} +fi + +if test x"${install_sh+set}" != xset; then + case $am_aux_dir in + *\ * | *\ *) + install_sh="\${SHELL} '$am_aux_dir/install-sh'" ;; + *) + install_sh="\${SHELL} $am_aux_dir/install-sh" + esac +fi + +# Installed binaries are usually stripped using 'strip' when the user +# run "make install-strip". However 'strip' might not be the right +# tool to use in cross-compilation environments, therefore Automake +# will honor the 'STRIP' environment variable to overrule this program. +if test "$cross_compiling" != no; then + if test -n "$ac_tool_prefix"; then + # Extract the first word of "${ac_tool_prefix}strip", so it can be a program name with args. +set dummy ${ac_tool_prefix}strip; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_prog_STRIP+:} false; then : + $as_echo_n "(cached) " >&6 +else + if test -n "$STRIP"; then + ac_cv_prog_STRIP="$STRIP" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_prog_STRIP="${ac_tool_prefix}strip" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + +fi +fi +STRIP=$ac_cv_prog_STRIP +if test -n "$STRIP"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $STRIP" >&5 +$as_echo "$STRIP" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + +fi +if test -z "$ac_cv_prog_STRIP"; then + ac_ct_STRIP=$STRIP + # Extract the first word of "strip", so it can be a program name with args. +set dummy strip; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_prog_ac_ct_STRIP+:} false; then : + $as_echo_n "(cached) " >&6 +else + if test -n "$ac_ct_STRIP"; then + ac_cv_prog_ac_ct_STRIP="$ac_ct_STRIP" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_prog_ac_ct_STRIP="strip" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + +fi +fi +ac_ct_STRIP=$ac_cv_prog_ac_ct_STRIP +if test -n "$ac_ct_STRIP"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_ct_STRIP" >&5 +$as_echo "$ac_ct_STRIP" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + if test "x$ac_ct_STRIP" = x; then + STRIP=":" + else + case $cross_compiling:$ac_tool_warned in +yes:) +{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5 +$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;} +ac_tool_warned=yes ;; +esac + STRIP=$ac_ct_STRIP + fi +else + STRIP="$ac_cv_prog_STRIP" +fi + +fi +INSTALL_STRIP_PROGRAM="\$(install_sh) -c -s" + +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for a thread-safe mkdir -p" >&5 +$as_echo_n "checking for a thread-safe mkdir -p... " >&6; } +if test -z "$MKDIR_P"; then + if ${ac_cv_path_mkdir+:} false; then : + $as_echo_n "(cached) " >&6 +else + as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH$PATH_SEPARATOR/opt/sfw/bin +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_prog in mkdir gmkdir; do + for ac_exec_ext in '' $ac_executable_extensions; do + as_fn_executable_p "$as_dir/$ac_prog$ac_exec_ext" || continue + case `"$as_dir/$ac_prog$ac_exec_ext" --version 2>&1` in #( + 'mkdir (GNU coreutils) '* | \ + 'mkdir (coreutils) '* | \ + 'mkdir (fileutils) '4.1*) + ac_cv_path_mkdir=$as_dir/$ac_prog$ac_exec_ext + break 3;; + esac + done + done + done +IFS=$as_save_IFS + +fi + + test -d ./--version && rmdir ./--version + if test "${ac_cv_path_mkdir+set}" = set; then + MKDIR_P="$ac_cv_path_mkdir -p" + else + # As a last resort, use the slow shell script. Don't cache a + # value for MKDIR_P within a source directory, because that will + # break other packages using the cache if that directory is + # removed, or if the value is a relative name. + MKDIR_P="$ac_install_sh -d" + fi +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $MKDIR_P" >&5 +$as_echo "$MKDIR_P" >&6; } + +for ac_prog in gawk mawk nawk awk +do + # Extract the first word of "$ac_prog", so it can be a program name with args. +set dummy $ac_prog; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_prog_AWK+:} false; then : + $as_echo_n "(cached) " >&6 +else + if test -n "$AWK"; then + ac_cv_prog_AWK="$AWK" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_prog_AWK="$ac_prog" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + +fi +fi +AWK=$ac_cv_prog_AWK +if test -n "$AWK"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $AWK" >&5 +$as_echo "$AWK" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + + test -n "$AWK" && break +done + +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether ${MAKE-make} sets \$(MAKE)" >&5 +$as_echo_n "checking whether ${MAKE-make} sets \$(MAKE)... " >&6; } +set x ${MAKE-make} +ac_make=`$as_echo "$2" | sed 's/+/p/g; s/[^a-zA-Z0-9_]/_/g'` +if eval \${ac_cv_prog_make_${ac_make}_set+:} false; then : + $as_echo_n "(cached) " >&6 +else + cat >conftest.make <<\_ACEOF +SHELL = /bin/sh +all: + @echo '@@@%%%=$(MAKE)=@@@%%%' +_ACEOF +# GNU make sometimes prints "make[1]: Entering ...", which would confuse us. +case `${MAKE-make} -f conftest.make 2>/dev/null` in + *@@@%%%=?*=@@@%%%*) + eval ac_cv_prog_make_${ac_make}_set=yes;; + *) + eval ac_cv_prog_make_${ac_make}_set=no;; +esac +rm -f conftest.make +fi +if eval test \$ac_cv_prog_make_${ac_make}_set = yes; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5 +$as_echo "yes" >&6; } + SET_MAKE= +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } + SET_MAKE="MAKE=${MAKE-make}" +fi + +rm -rf .tst 2>/dev/null +mkdir .tst 2>/dev/null +if test -d .tst; then + am__leading_dot=. +else + am__leading_dot=_ +fi +rmdir .tst 2>/dev/null + +# Check whether --enable-silent-rules was given. +if test "${enable_silent_rules+set}" = set; then : + enableval=$enable_silent_rules; +fi + +case $enable_silent_rules in # ((( + yes) AM_DEFAULT_VERBOSITY=0;; + no) AM_DEFAULT_VERBOSITY=1;; + *) AM_DEFAULT_VERBOSITY=1;; +esac +am_make=${MAKE-make} +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether $am_make supports nested variables" >&5 +$as_echo_n "checking whether $am_make supports nested variables... " >&6; } +if ${am_cv_make_support_nested_variables+:} false; then : + $as_echo_n "(cached) " >&6 +else + if $as_echo 'TRUE=$(BAR$(V)) +BAR0=false +BAR1=true +V=1 +am__doit: + @$(TRUE) +.PHONY: am__doit' | $am_make -f - >/dev/null 2>&1; then + am_cv_make_support_nested_variables=yes +else + am_cv_make_support_nested_variables=no +fi +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $am_cv_make_support_nested_variables" >&5 +$as_echo "$am_cv_make_support_nested_variables" >&6; } +if test $am_cv_make_support_nested_variables = yes; then + AM_V='$(V)' + AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)' +else + AM_V=$AM_DEFAULT_VERBOSITY + AM_DEFAULT_V=$AM_DEFAULT_VERBOSITY +fi +AM_BACKSLASH='\' + +if test "`cd $srcdir && pwd`" != "`pwd`"; then + # Use -I$(srcdir) only when $(srcdir) != ., so that make's output + # is not polluted with repeated "-I." + am__isrc=' -I$(srcdir)' + # test to see if srcdir already configured + if test -f $srcdir/config.status; then + as_fn_error $? "source directory already configured; run \"make distclean\" there first" "$LINENO" 5 + fi +fi + +# test whether we have cygpath +if test -z "$CYGPATH_W"; then + if (cygpath --version) >/dev/null 2>/dev/null; then + CYGPATH_W='cygpath -w' + else + CYGPATH_W=echo + fi +fi + + +# Define the identity of the package. + PACKAGE='putty' + VERSION='0.72' + + +cat >>confdefs.h <<_ACEOF +#define PACKAGE "$PACKAGE" +_ACEOF + + +cat >>confdefs.h <<_ACEOF +#define VERSION "$VERSION" +_ACEOF + +# Some tools Automake needs. + +ACLOCAL=${ACLOCAL-"${am_missing_run}aclocal-${am__api_version}"} + + +AUTOCONF=${AUTOCONF-"${am_missing_run}autoconf"} + + +AUTOMAKE=${AUTOMAKE-"${am_missing_run}automake-${am__api_version}"} + + +AUTOHEADER=${AUTOHEADER-"${am_missing_run}autoheader"} + + +MAKEINFO=${MAKEINFO-"${am_missing_run}makeinfo"} + +# For better backward compatibility. To be removed once Automake 1.9.x +# dies out for good. For more background, see: +# +# +mkdir_p='$(MKDIR_P)' + +# We need awk for the "check" target (and possibly the TAP driver). The +# system "awk" is bad on some platforms. +# Always define AMTAR for backward compatibility. Yes, it's still used +# in the wild :-( We should find a proper way to deprecate it ... +AMTAR='$${TAR-tar}' + + +# We'll loop over all known methods to create a tar archive until one works. +_am_tools='gnutar pax cpio none' + +am__tar='$${TAR-tar} chof - "$$tardir"' am__untar='$${TAR-tar} xf -' + + + + + + +# POSIX will say in a future version that running "rm -f" with no argument +# is OK; and we want to be able to make that assumption in our Makefile +# recipes. So use an aggressive probe to check that the usage we want is +# actually supported "in the wild" to an acceptable degree. +# See automake bug#10828. +# To make any issue more visible, cause the running configure to be aborted +# by default if the 'rm' program in use doesn't match our expectations; the +# user can still override this though. +if rm -f && rm -fr && rm -rf; then : OK; else + cat >&2 <<'END' +Oops! + +Your 'rm' program seems unable to run without file operands specified +on the command line, even when the '-f' option is present. This is contrary +to the behaviour of most rm programs out there, and not conforming with +the upcoming POSIX standard: + +Please tell bug-automake@gnu.org about your system, including the value +of your $PATH and any error possibly output before this message. This +can help us improve future automake versions. + +END + if test x"$ACCEPT_INFERIOR_RM_PROGRAM" = x"yes"; then + echo 'Configuration will proceed anyway, since you have set the' >&2 + echo 'ACCEPT_INFERIOR_RM_PROGRAM variable to "yes"' >&2 + echo >&2 + else + cat >&2 <<'END' +Aborting the configuration process, to ensure you take notice of the issue. + +You can download and install GNU coreutils to get an 'rm' implementation +that behaves properly: . + +If you want to complete the configuration process using your problematic +'rm' anyway, export the environment variable ACCEPT_INFERIOR_RM_PROGRAM +to "yes", and re-run configure. + +END + as_fn_error $? "Your 'rm' program is bad, sorry." "$LINENO" 5 + fi +fi + + + +if test -n "$ac_tool_prefix"; then + # Extract the first word of "${ac_tool_prefix}ranlib", so it can be a program name with args. +set dummy ${ac_tool_prefix}ranlib; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_prog_RANLIB+:} false; then : + $as_echo_n "(cached) " >&6 +else + if test -n "$RANLIB"; then + ac_cv_prog_RANLIB="$RANLIB" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_prog_RANLIB="${ac_tool_prefix}ranlib" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + +fi +fi +RANLIB=$ac_cv_prog_RANLIB +if test -n "$RANLIB"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $RANLIB" >&5 +$as_echo "$RANLIB" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + +fi +if test -z "$ac_cv_prog_RANLIB"; then + ac_ct_RANLIB=$RANLIB + # Extract the first word of "ranlib", so it can be a program name with args. +set dummy ranlib; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_prog_ac_ct_RANLIB+:} false; then : + $as_echo_n "(cached) " >&6 +else + if test -n "$ac_ct_RANLIB"; then + ac_cv_prog_ac_ct_RANLIB="$ac_ct_RANLIB" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_prog_ac_ct_RANLIB="ranlib" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + +fi +fi +ac_ct_RANLIB=$ac_cv_prog_ac_ct_RANLIB +if test -n "$ac_ct_RANLIB"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_ct_RANLIB" >&5 +$as_echo "$ac_ct_RANLIB" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + if test "x$ac_ct_RANLIB" = x; then + RANLIB=":" + else + case $cross_compiling:$ac_tool_warned in +yes:) +{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5 +$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;} +ac_tool_warned=yes ;; +esac + RANLIB=$ac_ct_RANLIB + fi +else + RANLIB="$ac_cv_prog_RANLIB" +fi + +DEPDIR="${am__leading_dot}deps" + +ac_config_commands="$ac_config_commands depfiles" + + +am_make=${MAKE-make} +cat > confinc << 'END' +am__doit: + @echo this is the am__doit target +.PHONY: am__doit +END +# If we don't find an include directive, just comment out the code. +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for style of include used by $am_make" >&5 +$as_echo_n "checking for style of include used by $am_make... " >&6; } +am__include="#" +am__quote= +_am_result=none +# First try GNU make style include. +echo "include confinc" > confmf +# Ignore all kinds of additional output from 'make'. +case `$am_make -s -f confmf 2> /dev/null` in #( +*the\ am__doit\ target*) + am__include=include + am__quote= + _am_result=GNU + ;; +esac +# Now try BSD make style include. +if test "$am__include" = "#"; then + echo '.include "confinc"' > confmf + case `$am_make -s -f confmf 2> /dev/null` in #( + *the\ am__doit\ target*) + am__include=.include + am__quote="\"" + _am_result=BSD + ;; + esac +fi + + +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $_am_result" >&5 +$as_echo "$_am_result" >&6; } +rm -f confinc confmf + +# Check whether --enable-dependency-tracking was given. +if test "${enable_dependency_tracking+set}" = set; then : + enableval=$enable_dependency_tracking; +fi + +if test "x$enable_dependency_tracking" != xno; then + am_depcomp="$ac_aux_dir/depcomp" + AMDEPBACKSLASH='\' + am__nodep='_no' +fi + if test "x$enable_dependency_tracking" != xno; then + AMDEP_TRUE= + AMDEP_FALSE='#' +else + AMDEP_TRUE='#' + AMDEP_FALSE= +fi + + +ac_ext=c +ac_cpp='$CPP $CPPFLAGS' +ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' +ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' +ac_compiler_gnu=$ac_cv_c_compiler_gnu +if test -n "$ac_tool_prefix"; then + # Extract the first word of "${ac_tool_prefix}gcc", so it can be a program name with args. +set dummy ${ac_tool_prefix}gcc; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_prog_CC+:} false; then : + $as_echo_n "(cached) " >&6 +else + if test -n "$CC"; then + ac_cv_prog_CC="$CC" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_prog_CC="${ac_tool_prefix}gcc" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + +fi +fi +CC=$ac_cv_prog_CC +if test -n "$CC"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $CC" >&5 +$as_echo "$CC" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + +fi +if test -z "$ac_cv_prog_CC"; then + ac_ct_CC=$CC + # Extract the first word of "gcc", so it can be a program name with args. +set dummy gcc; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_prog_ac_ct_CC+:} false; then : + $as_echo_n "(cached) " >&6 +else + if test -n "$ac_ct_CC"; then + ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_prog_ac_ct_CC="gcc" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + +fi +fi +ac_ct_CC=$ac_cv_prog_ac_ct_CC +if test -n "$ac_ct_CC"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_ct_CC" >&5 +$as_echo "$ac_ct_CC" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + if test "x$ac_ct_CC" = x; then + CC="" + else + case $cross_compiling:$ac_tool_warned in +yes:) +{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5 +$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;} +ac_tool_warned=yes ;; +esac + CC=$ac_ct_CC + fi +else + CC="$ac_cv_prog_CC" +fi + +if test -z "$CC"; then + if test -n "$ac_tool_prefix"; then + # Extract the first word of "${ac_tool_prefix}cc", so it can be a program name with args. +set dummy ${ac_tool_prefix}cc; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_prog_CC+:} false; then : + $as_echo_n "(cached) " >&6 +else + if test -n "$CC"; then + ac_cv_prog_CC="$CC" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_prog_CC="${ac_tool_prefix}cc" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + +fi +fi +CC=$ac_cv_prog_CC +if test -n "$CC"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $CC" >&5 +$as_echo "$CC" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + + fi +fi +if test -z "$CC"; then + # Extract the first word of "cc", so it can be a program name with args. +set dummy cc; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_prog_CC+:} false; then : + $as_echo_n "(cached) " >&6 +else + if test -n "$CC"; then + ac_cv_prog_CC="$CC" # Let the user override the test. +else + ac_prog_rejected=no +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + if test "$as_dir/$ac_word$ac_exec_ext" = "/usr/ucb/cc"; then + ac_prog_rejected=yes + continue + fi + ac_cv_prog_CC="cc" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + +if test $ac_prog_rejected = yes; then + # We found a bogon in the path, so make sure we never use it. + set dummy $ac_cv_prog_CC + shift + if test $# != 0; then + # We chose a different compiler from the bogus one. + # However, it has the same basename, so the bogon will be chosen + # first if we set CC to just the basename; use the full file name. + shift + ac_cv_prog_CC="$as_dir/$ac_word${1+' '}$@" + fi +fi +fi +fi +CC=$ac_cv_prog_CC +if test -n "$CC"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $CC" >&5 +$as_echo "$CC" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + +fi +if test -z "$CC"; then + if test -n "$ac_tool_prefix"; then + for ac_prog in cl.exe + do + # Extract the first word of "$ac_tool_prefix$ac_prog", so it can be a program name with args. +set dummy $ac_tool_prefix$ac_prog; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_prog_CC+:} false; then : + $as_echo_n "(cached) " >&6 +else + if test -n "$CC"; then + ac_cv_prog_CC="$CC" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_prog_CC="$ac_tool_prefix$ac_prog" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + +fi +fi +CC=$ac_cv_prog_CC +if test -n "$CC"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $CC" >&5 +$as_echo "$CC" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + + test -n "$CC" && break + done +fi +if test -z "$CC"; then + ac_ct_CC=$CC + for ac_prog in cl.exe +do + # Extract the first word of "$ac_prog", so it can be a program name with args. +set dummy $ac_prog; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_prog_ac_ct_CC+:} false; then : + $as_echo_n "(cached) " >&6 +else + if test -n "$ac_ct_CC"; then + ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_prog_ac_ct_CC="$ac_prog" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + +fi +fi +ac_ct_CC=$ac_cv_prog_ac_ct_CC +if test -n "$ac_ct_CC"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_ct_CC" >&5 +$as_echo "$ac_ct_CC" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + + test -n "$ac_ct_CC" && break +done + + if test "x$ac_ct_CC" = x; then + CC="" + else + case $cross_compiling:$ac_tool_warned in +yes:) +{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5 +$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;} +ac_tool_warned=yes ;; +esac + CC=$ac_ct_CC + fi +fi + +fi + + +test -z "$CC" && { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +as_fn_error $? "no acceptable C compiler found in \$PATH +See \`config.log' for more details" "$LINENO" 5; } + +# Provide some information about the compiler. +$as_echo "$as_me:${as_lineno-$LINENO}: checking for C compiler version" >&5 +set X $ac_compile +ac_compiler=$2 +for ac_option in --version -v -V -qversion; do + { { ac_try="$ac_compiler $ac_option >&5" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\"" +$as_echo "$ac_try_echo"; } >&5 + (eval "$ac_compiler $ac_option >&5") 2>conftest.err + ac_status=$? + if test -s conftest.err; then + sed '10a\ +... rest of stderr output deleted ... + 10q' conftest.err >conftest.er1 + cat conftest.er1 >&5 + fi + rm -f conftest.er1 conftest.err + $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 + test $ac_status = 0; } +done + +cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ + +int +main () +{ + + ; + return 0; +} +_ACEOF +ac_clean_files_save=$ac_clean_files +ac_clean_files="$ac_clean_files a.out a.out.dSYM a.exe b.out" +# Try to create an executable without -o first, disregard a.out. +# It will help us diagnose broken compilers, and finding out an intuition +# of exeext. +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the C compiler works" >&5 +$as_echo_n "checking whether the C compiler works... " >&6; } +ac_link_default=`$as_echo "$ac_link" | sed 's/ -o *conftest[^ ]*//'` + +# The possible output files: +ac_files="a.out conftest.exe conftest a.exe a_out.exe b.out conftest.*" + +ac_rmfiles= +for ac_file in $ac_files +do + case $ac_file in + *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj ) ;; + * ) ac_rmfiles="$ac_rmfiles $ac_file";; + esac +done +rm -f $ac_rmfiles + +if { { ac_try="$ac_link_default" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\"" +$as_echo "$ac_try_echo"; } >&5 + (eval "$ac_link_default") 2>&5 + ac_status=$? + $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 + test $ac_status = 0; }; then : + # Autoconf-2.13 could set the ac_cv_exeext variable to `no'. +# So ignore a value of `no', otherwise this would lead to `EXEEXT = no' +# in a Makefile. We should not override ac_cv_exeext if it was cached, +# so that the user can short-circuit this test for compilers unknown to +# Autoconf. +for ac_file in $ac_files '' +do + test -f "$ac_file" || continue + case $ac_file in + *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj ) + ;; + [ab].out ) + # We found the default executable, but exeext='' is most + # certainly right. + break;; + *.* ) + if test "${ac_cv_exeext+set}" = set && test "$ac_cv_exeext" != no; + then :; else + ac_cv_exeext=`expr "$ac_file" : '[^.]*\(\..*\)'` + fi + # We set ac_cv_exeext here because the later test for it is not + # safe: cross compilers may not add the suffix if given an `-o' + # argument, so we may need to know it at that point already. + # Even if this section looks crufty: it has the advantage of + # actually working. + break;; + * ) + break;; + esac +done +test "$ac_cv_exeext" = no && ac_cv_exeext= + +else + ac_file='' +fi +if test -z "$ac_file"; then : + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +$as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + +{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +as_fn_error 77 "C compiler cannot create executables +See \`config.log' for more details" "$LINENO" 5; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5 +$as_echo "yes" >&6; } +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for C compiler default output file name" >&5 +$as_echo_n "checking for C compiler default output file name... " >&6; } +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_file" >&5 +$as_echo "$ac_file" >&6; } +ac_exeext=$ac_cv_exeext + +rm -f -r a.out a.out.dSYM a.exe conftest$ac_cv_exeext b.out +ac_clean_files=$ac_clean_files_save +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for suffix of executables" >&5 +$as_echo_n "checking for suffix of executables... " >&6; } +if { { ac_try="$ac_link" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\"" +$as_echo "$ac_try_echo"; } >&5 + (eval "$ac_link") 2>&5 + ac_status=$? + $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 + test $ac_status = 0; }; then : + # If both `conftest.exe' and `conftest' are `present' (well, observable) +# catch `conftest.exe'. For instance with Cygwin, `ls conftest' will +# work properly (i.e., refer to `conftest.exe'), while it won't with +# `rm'. +for ac_file in conftest.exe conftest conftest.*; do + test -f "$ac_file" || continue + case $ac_file in + *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj ) ;; + *.* ) ac_cv_exeext=`expr "$ac_file" : '[^.]*\(\..*\)'` + break;; + * ) break;; + esac +done +else + { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +as_fn_error $? "cannot compute suffix of executables: cannot compile and link +See \`config.log' for more details" "$LINENO" 5; } +fi +rm -f conftest conftest$ac_cv_exeext +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_exeext" >&5 +$as_echo "$ac_cv_exeext" >&6; } + +rm -f conftest.$ac_ext +EXEEXT=$ac_cv_exeext +ac_exeext=$EXEEXT +cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ +#include +int +main () +{ +FILE *f = fopen ("conftest.out", "w"); + return ferror (f) || fclose (f) != 0; + + ; + return 0; +} +_ACEOF +ac_clean_files="$ac_clean_files conftest.out" +# Check that the compiler produces executables we can run. If not, either +# the compiler is broken, or we cross compile. +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether we are cross compiling" >&5 +$as_echo_n "checking whether we are cross compiling... " >&6; } +if test "$cross_compiling" != yes; then + { { ac_try="$ac_link" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\"" +$as_echo "$ac_try_echo"; } >&5 + (eval "$ac_link") 2>&5 + ac_status=$? + $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 + test $ac_status = 0; } + if { ac_try='./conftest$ac_cv_exeext' + { { case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\"" +$as_echo "$ac_try_echo"; } >&5 + (eval "$ac_try") 2>&5 + ac_status=$? + $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 + test $ac_status = 0; }; }; then + cross_compiling=no + else + if test "$cross_compiling" = maybe; then + cross_compiling=yes + else + { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +as_fn_error $? "cannot run C compiled programs. +If you meant to cross compile, use \`--host'. +See \`config.log' for more details" "$LINENO" 5; } + fi + fi +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $cross_compiling" >&5 +$as_echo "$cross_compiling" >&6; } + +rm -f conftest.$ac_ext conftest$ac_cv_exeext conftest.out +ac_clean_files=$ac_clean_files_save +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for suffix of object files" >&5 +$as_echo_n "checking for suffix of object files... " >&6; } +if ${ac_cv_objext+:} false; then : + $as_echo_n "(cached) " >&6 +else + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ + +int +main () +{ + + ; + return 0; +} +_ACEOF +rm -f conftest.o conftest.obj +if { { ac_try="$ac_compile" +case "(($ac_try" in + *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; + *) ac_try_echo=$ac_try;; +esac +eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\"" +$as_echo "$ac_try_echo"; } >&5 + (eval "$ac_compile") 2>&5 + ac_status=$? + $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 + test $ac_status = 0; }; then : + for ac_file in conftest.o conftest.obj conftest.*; do + test -f "$ac_file" || continue; + case $ac_file in + *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM ) ;; + *) ac_cv_objext=`expr "$ac_file" : '.*\.\(.*\)'` + break;; + esac +done +else + $as_echo "$as_me: failed program was:" >&5 +sed 's/^/| /' conftest.$ac_ext >&5 + +{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +as_fn_error $? "cannot compute suffix of object files: cannot compile +See \`config.log' for more details" "$LINENO" 5; } +fi +rm -f conftest.$ac_cv_objext conftest.$ac_ext +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_objext" >&5 +$as_echo "$ac_cv_objext" >&6; } +OBJEXT=$ac_cv_objext +ac_objext=$OBJEXT +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether we are using the GNU C compiler" >&5 +$as_echo_n "checking whether we are using the GNU C compiler... " >&6; } +if ${ac_cv_c_compiler_gnu+:} false; then : + $as_echo_n "(cached) " >&6 +else + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ + +int +main () +{ +#ifndef __GNUC__ + choke me +#endif + + ; + return 0; +} +_ACEOF +if ac_fn_c_try_compile "$LINENO"; then : + ac_compiler_gnu=yes +else + ac_compiler_gnu=no +fi +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext +ac_cv_c_compiler_gnu=$ac_compiler_gnu + +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_c_compiler_gnu" >&5 +$as_echo "$ac_cv_c_compiler_gnu" >&6; } +if test $ac_compiler_gnu = yes; then + GCC=yes +else + GCC= +fi +ac_test_CFLAGS=${CFLAGS+set} +ac_save_CFLAGS=$CFLAGS +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether $CC accepts -g" >&5 +$as_echo_n "checking whether $CC accepts -g... " >&6; } +if ${ac_cv_prog_cc_g+:} false; then : + $as_echo_n "(cached) " >&6 +else + ac_save_c_werror_flag=$ac_c_werror_flag + ac_c_werror_flag=yes + ac_cv_prog_cc_g=no + CFLAGS="-g" + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ + +int +main () +{ + + ; + return 0; +} +_ACEOF +if ac_fn_c_try_compile "$LINENO"; then : + ac_cv_prog_cc_g=yes +else + CFLAGS="" + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ + +int +main () +{ + + ; + return 0; +} +_ACEOF +if ac_fn_c_try_compile "$LINENO"; then : + +else + ac_c_werror_flag=$ac_save_c_werror_flag + CFLAGS="-g" + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ + +int +main () +{ + + ; + return 0; +} +_ACEOF +if ac_fn_c_try_compile "$LINENO"; then : + ac_cv_prog_cc_g=yes +fi +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext +fi +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext +fi +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext + ac_c_werror_flag=$ac_save_c_werror_flag +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_g" >&5 +$as_echo "$ac_cv_prog_cc_g" >&6; } +if test "$ac_test_CFLAGS" = set; then + CFLAGS=$ac_save_CFLAGS +elif test $ac_cv_prog_cc_g = yes; then + if test "$GCC" = yes; then + CFLAGS="-g -O2" + else + CFLAGS="-g" + fi +else + if test "$GCC" = yes; then + CFLAGS="-O2" + else + CFLAGS= + fi +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $CC option to accept ISO C89" >&5 +$as_echo_n "checking for $CC option to accept ISO C89... " >&6; } +if ${ac_cv_prog_cc_c89+:} false; then : + $as_echo_n "(cached) " >&6 +else + ac_cv_prog_cc_c89=no +ac_save_CC=$CC +cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ +#include +#include +struct stat; +/* Most of the following tests are stolen from RCS 5.7's src/conf.sh. */ +struct buf { int x; }; +FILE * (*rcsopen) (struct buf *, struct stat *, int); +static char *e (p, i) + char **p; + int i; +{ + return p[i]; +} +static char *f (char * (*g) (char **, int), char **p, ...) +{ + char *s; + va_list v; + va_start (v,p); + s = g (p, va_arg (v,int)); + va_end (v); + return s; +} + +/* OSF 4.0 Compaq cc is some sort of almost-ANSI by default. It has + function prototypes and stuff, but not '\xHH' hex character constants. + These don't provoke an error unfortunately, instead are silently treated + as 'x'. The following induces an error, until -std is added to get + proper ANSI mode. Curiously '\x00'!='x' always comes out true, for an + array size at least. It's necessary to write '\x00'==0 to get something + that's true only with -std. */ +int osf4_cc_array ['\x00' == 0 ? 1 : -1]; + +/* IBM C 6 for AIX is almost-ANSI by default, but it replaces macro parameters + inside strings and character constants. */ +#define FOO(x) 'x' +int xlc6_cc_array[FOO(a) == 'x' ? 1 : -1]; + +int test (int i, double x); +struct s1 {int (*f) (int a);}; +struct s2 {int (*f) (double a);}; +int pairnames (int, char **, FILE *(*)(struct buf *, struct stat *, int), int, int); +int argc; +char **argv; +int +main () +{ +return f (e, argv, 0) != argv[0] || f (e, argv, 1) != argv[1]; + ; + return 0; +} +_ACEOF +for ac_arg in '' -qlanglvl=extc89 -qlanglvl=ansi -std \ + -Ae "-Aa -D_HPUX_SOURCE" "-Xc -D__EXTENSIONS__" +do + CC="$ac_save_CC $ac_arg" + if ac_fn_c_try_compile "$LINENO"; then : + ac_cv_prog_cc_c89=$ac_arg +fi +rm -f core conftest.err conftest.$ac_objext + test "x$ac_cv_prog_cc_c89" != "xno" && break +done +rm -f conftest.$ac_ext +CC=$ac_save_CC + +fi +# AC_CACHE_VAL +case "x$ac_cv_prog_cc_c89" in + x) + { $as_echo "$as_me:${as_lineno-$LINENO}: result: none needed" >&5 +$as_echo "none needed" >&6; } ;; + xno) + { $as_echo "$as_me:${as_lineno-$LINENO}: result: unsupported" >&5 +$as_echo "unsupported" >&6; } ;; + *) + CC="$CC $ac_cv_prog_cc_c89" + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_c89" >&5 +$as_echo "$ac_cv_prog_cc_c89" >&6; } ;; +esac +if test "x$ac_cv_prog_cc_c89" != xno; then : + +fi + +ac_ext=c +ac_cpp='$CPP $CPPFLAGS' +ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' +ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' +ac_compiler_gnu=$ac_cv_c_compiler_gnu + +ac_ext=c +ac_cpp='$CPP $CPPFLAGS' +ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' +ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' +ac_compiler_gnu=$ac_cv_c_compiler_gnu +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether $CC understands -c and -o together" >&5 +$as_echo_n "checking whether $CC understands -c and -o together... " >&6; } +if ${am_cv_prog_cc_c_o+:} false; then : + $as_echo_n "(cached) " >&6 +else + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ + +int +main () +{ + + ; + return 0; +} +_ACEOF + # Make sure it works both with $CC and with simple cc. + # Following AC_PROG_CC_C_O, we do the test twice because some + # compilers refuse to overwrite an existing .o file with -o, + # though they will create one. + am_cv_prog_cc_c_o=yes + for am_i in 1 2; do + if { echo "$as_me:$LINENO: $CC -c conftest.$ac_ext -o conftest2.$ac_objext" >&5 + ($CC -c conftest.$ac_ext -o conftest2.$ac_objext) >&5 2>&5 + ac_status=$? + echo "$as_me:$LINENO: \$? = $ac_status" >&5 + (exit $ac_status); } \ + && test -f conftest2.$ac_objext; then + : OK + else + am_cv_prog_cc_c_o=no + break + fi + done + rm -f core conftest* + unset am_i +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $am_cv_prog_cc_c_o" >&5 +$as_echo "$am_cv_prog_cc_c_o" >&6; } +if test "$am_cv_prog_cc_c_o" != yes; then + # Losing compiler, so override with the script. + # FIXME: It is wrong to rewrite CC. + # But if we don't then we get into trouble of one sort or another. + # A longer-term fix would be to have automake use am__CC in this case, + # and then we could set am__CC="\$(top_srcdir)/compile \$(CC)" + CC="$am_aux_dir/compile $CC" +fi +ac_ext=c +ac_cpp='$CPP $CPPFLAGS' +ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' +ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' +ac_compiler_gnu=$ac_cv_c_compiler_gnu + + +depcc="$CC" am_compiler_list= + +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking dependency style of $depcc" >&5 +$as_echo_n "checking dependency style of $depcc... " >&6; } +if ${am_cv_CC_dependencies_compiler_type+:} false; then : + $as_echo_n "(cached) " >&6 +else + if test -z "$AMDEP_TRUE" && test -f "$am_depcomp"; then + # We make a subdir and do the tests there. Otherwise we can end up + # making bogus files that we don't know about and never remove. For + # instance it was reported that on HP-UX the gcc test will end up + # making a dummy file named 'D' -- because '-MD' means "put the output + # in D". + rm -rf conftest.dir + mkdir conftest.dir + # Copy depcomp to subdir because otherwise we won't find it if we're + # using a relative directory. + cp "$am_depcomp" conftest.dir + cd conftest.dir + # We will build objects and dependencies in a subdirectory because + # it helps to detect inapplicable dependency modes. For instance + # both Tru64's cc and ICC support -MD to output dependencies as a + # side effect of compilation, but ICC will put the dependencies in + # the current directory while Tru64 will put them in the object + # directory. + mkdir sub + + am_cv_CC_dependencies_compiler_type=none + if test "$am_compiler_list" = ""; then + am_compiler_list=`sed -n 's/^#*\([a-zA-Z0-9]*\))$/\1/p' < ./depcomp` + fi + am__universal=false + case " $depcc " in #( + *\ -arch\ *\ -arch\ *) am__universal=true ;; + esac + + for depmode in $am_compiler_list; do + # Setup a source with many dependencies, because some compilers + # like to wrap large dependency lists on column 80 (with \), and + # we should not choose a depcomp mode which is confused by this. + # + # We need to recreate these files for each test, as the compiler may + # overwrite some of them when testing with obscure command lines. + # This happens at least with the AIX C compiler. + : > sub/conftest.c + for i in 1 2 3 4 5 6; do + echo '#include "conftst'$i'.h"' >> sub/conftest.c + # Using ": > sub/conftst$i.h" creates only sub/conftst1.h with + # Solaris 10 /bin/sh. + echo '/* dummy */' > sub/conftst$i.h + done + echo "${am__include} ${am__quote}sub/conftest.Po${am__quote}" > confmf + + # We check with '-c' and '-o' for the sake of the "dashmstdout" + # mode. It turns out that the SunPro C++ compiler does not properly + # handle '-M -o', and we need to detect this. Also, some Intel + # versions had trouble with output in subdirs. + am__obj=sub/conftest.${OBJEXT-o} + am__minus_obj="-o $am__obj" + case $depmode in + gcc) + # This depmode causes a compiler race in universal mode. + test "$am__universal" = false || continue + ;; + nosideeffect) + # After this tag, mechanisms are not by side-effect, so they'll + # only be used when explicitly requested. + if test "x$enable_dependency_tracking" = xyes; then + continue + else + break + fi + ;; + msvc7 | msvc7msys | msvisualcpp | msvcmsys) + # This compiler won't grok '-c -o', but also, the minuso test has + # not run yet. These depmodes are late enough in the game, and + # so weak that their functioning should not be impacted. + am__obj=conftest.${OBJEXT-o} + am__minus_obj= + ;; + none) break ;; + esac + if depmode=$depmode \ + source=sub/conftest.c object=$am__obj \ + depfile=sub/conftest.Po tmpdepfile=sub/conftest.TPo \ + $SHELL ./depcomp $depcc -c $am__minus_obj sub/conftest.c \ + >/dev/null 2>conftest.err && + grep sub/conftst1.h sub/conftest.Po > /dev/null 2>&1 && + grep sub/conftst6.h sub/conftest.Po > /dev/null 2>&1 && + grep $am__obj sub/conftest.Po > /dev/null 2>&1 && + ${MAKE-make} -s -f confmf > /dev/null 2>&1; then + # icc doesn't choke on unknown options, it will just issue warnings + # or remarks (even with -Werror). So we grep stderr for any message + # that says an option was ignored or not supported. + # When given -MP, icc 7.0 and 7.1 complain thusly: + # icc: Command line warning: ignoring option '-M'; no argument required + # The diagnosis changed in icc 8.0: + # icc: Command line remark: option '-MP' not supported + if (grep 'ignoring option' conftest.err || + grep 'not supported' conftest.err) >/dev/null 2>&1; then :; else + am_cv_CC_dependencies_compiler_type=$depmode + break + fi + fi + done + + cd .. + rm -rf conftest.dir +else + am_cv_CC_dependencies_compiler_type=none +fi + +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $am_cv_CC_dependencies_compiler_type" >&5 +$as_echo "$am_cv_CC_dependencies_compiler_type" >&6; } +CCDEPMODE=depmode=$am_cv_CC_dependencies_compiler_type + + if + test "x$enable_dependency_tracking" != xno \ + && test "$am_cv_CC_dependencies_compiler_type" = gcc3; then + am__fastdepCC_TRUE= + am__fastdepCC_FALSE='#' +else + am__fastdepCC_TRUE='#' + am__fastdepCC_FALSE= +fi + + + +if test -n "$ac_tool_prefix"; then + for ac_prog in ar lib "link -lib" + do + # Extract the first word of "$ac_tool_prefix$ac_prog", so it can be a program name with args. +set dummy $ac_tool_prefix$ac_prog; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_prog_AR+:} false; then : + $as_echo_n "(cached) " >&6 +else + if test -n "$AR"; then + ac_cv_prog_AR="$AR" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_prog_AR="$ac_tool_prefix$ac_prog" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + +fi +fi +AR=$ac_cv_prog_AR +if test -n "$AR"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $AR" >&5 +$as_echo "$AR" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + + test -n "$AR" && break + done +fi +if test -z "$AR"; then + ac_ct_AR=$AR + for ac_prog in ar lib "link -lib" +do + # Extract the first word of "$ac_prog", so it can be a program name with args. +set dummy $ac_prog; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_prog_ac_ct_AR+:} false; then : + $as_echo_n "(cached) " >&6 +else + if test -n "$ac_ct_AR"; then + ac_cv_prog_ac_ct_AR="$ac_ct_AR" # Let the user override the test. +else +as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_prog_ac_ct_AR="$ac_prog" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + +fi +fi +ac_ct_AR=$ac_cv_prog_ac_ct_AR +if test -n "$ac_ct_AR"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_ct_AR" >&5 +$as_echo "$ac_ct_AR" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + + test -n "$ac_ct_AR" && break +done + + if test "x$ac_ct_AR" = x; then + AR="false" + else + case $cross_compiling:$ac_tool_warned in +yes:) +{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5 +$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;} +ac_tool_warned=yes ;; +esac + AR=$ac_ct_AR + fi +fi + +: ${AR=ar} + +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking the archiver ($AR) interface" >&5 +$as_echo_n "checking the archiver ($AR) interface... " >&6; } +if ${am_cv_ar_interface+:} false; then : + $as_echo_n "(cached) " >&6 +else + ac_ext=c +ac_cpp='$CPP $CPPFLAGS' +ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' +ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' +ac_compiler_gnu=$ac_cv_c_compiler_gnu + + am_cv_ar_interface=ar + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ +int some_variable = 0; +_ACEOF +if ac_fn_c_try_compile "$LINENO"; then : + am_ar_try='$AR cru libconftest.a conftest.$ac_objext >&5' + { { eval echo "\"\$as_me\":${as_lineno-$LINENO}: \"$am_ar_try\""; } >&5 + (eval $am_ar_try) 2>&5 + ac_status=$? + $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 + test $ac_status = 0; } + if test "$ac_status" -eq 0; then + am_cv_ar_interface=ar + else + am_ar_try='$AR -NOLOGO -OUT:conftest.lib conftest.$ac_objext >&5' + { { eval echo "\"\$as_me\":${as_lineno-$LINENO}: \"$am_ar_try\""; } >&5 + (eval $am_ar_try) 2>&5 + ac_status=$? + $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 + test $ac_status = 0; } + if test "$ac_status" -eq 0; then + am_cv_ar_interface=lib + else + am_cv_ar_interface=unknown + fi + fi + rm -f conftest.lib libconftest.a + +fi +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext + ac_ext=c +ac_cpp='$CPP $CPPFLAGS' +ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' +ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' +ac_compiler_gnu=$ac_cv_c_compiler_gnu + +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $am_cv_ar_interface" >&5 +$as_echo "$am_cv_ar_interface" >&6; } + +case $am_cv_ar_interface in +ar) + ;; +lib) + # Microsoft lib, so override with the ar-lib wrapper script. + # FIXME: It is wrong to rewrite AR. + # But if we don't then we get into trouble of one sort or another. + # A longer-term fix would be to have automake use am__AR in this case, + # and then we could set am__AR="$am_aux_dir/ar-lib \$(AR)" or something + # similar. + AR="$am_aux_dir/ar-lib $AR" + ;; +unknown) + as_fn_error $? "could not determine $AR interface" "$LINENO" 5 + ;; +esac + + + + { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $CC option to accept ISO C99" >&5 +$as_echo_n "checking for $CC option to accept ISO C99... " >&6; } +if ${ac_cv_prog_cc_c99+:} false; then : + $as_echo_n "(cached) " >&6 +else + ac_cv_prog_cc_c99=no +ac_save_CC=$CC +cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ +#include +#include +#include +#include +#include + +// Check varargs macros. These examples are taken from C99 6.10.3.5. +#define debug(...) fprintf (stderr, __VA_ARGS__) +#define showlist(...) puts (#__VA_ARGS__) +#define report(test,...) ((test) ? puts (#test) : printf (__VA_ARGS__)) +static void +test_varargs_macros (void) +{ + int x = 1234; + int y = 5678; + debug ("Flag"); + debug ("X = %d\n", x); + showlist (The first, second, and third items.); + report (x>y, "x is %d but y is %d", x, y); +} + +// Check long long types. +#define BIG64 18446744073709551615ull +#define BIG32 4294967295ul +#define BIG_OK (BIG64 / BIG32 == 4294967297ull && BIG64 % BIG32 == 0) +#if !BIG_OK + your preprocessor is broken; +#endif +#if BIG_OK +#else + your preprocessor is broken; +#endif +static long long int bignum = -9223372036854775807LL; +static unsigned long long int ubignum = BIG64; + +struct incomplete_array +{ + int datasize; + double data[]; +}; + +struct named_init { + int number; + const wchar_t *name; + double average; +}; + +typedef const char *ccp; + +static inline int +test_restrict (ccp restrict text) +{ + // See if C++-style comments work. + // Iterate through items via the restricted pointer. + // Also check for declarations in for loops. + for (unsigned int i = 0; *(text+i) != '\0'; ++i) + continue; + return 0; +} + +// Check varargs and va_copy. +static void +test_varargs (const char *format, ...) +{ + va_list args; + va_start (args, format); + va_list args_copy; + va_copy (args_copy, args); + + const char *str; + int number; + float fnumber; + + while (*format) + { + switch (*format++) + { + case 's': // string + str = va_arg (args_copy, const char *); + break; + case 'd': // int + number = va_arg (args_copy, int); + break; + case 'f': // float + fnumber = va_arg (args_copy, double); + break; + default: + break; + } + } + va_end (args_copy); + va_end (args); +} + +int +main () +{ + + // Check bool. + _Bool success = false; + + // Check restrict. + if (test_restrict ("String literal") == 0) + success = true; + char *restrict newvar = "Another string"; + + // Check varargs. + test_varargs ("s, d' f .", "string", 65, 34.234); + test_varargs_macros (); + + // Check flexible array members. + struct incomplete_array *ia = + malloc (sizeof (struct incomplete_array) + (sizeof (double) * 10)); + ia->datasize = 10; + for (int i = 0; i < ia->datasize; ++i) + ia->data[i] = i * 1.234; + + // Check named initializers. + struct named_init ni = { + .number = 34, + .name = L"Test wide string", + .average = 543.34343, + }; + + ni.number = 58; + + int dynamic_array[ni.number]; + dynamic_array[ni.number - 1] = 543; + + // work around unused variable warnings + return (!success || bignum == 0LL || ubignum == 0uLL || newvar[0] == 'x' + || dynamic_array[ni.number - 1] != 543); + + ; + return 0; +} +_ACEOF +for ac_arg in '' -std=gnu99 -std=c99 -c99 -AC99 -D_STDC_C99= -qlanglvl=extc99 +do + CC="$ac_save_CC $ac_arg" + if ac_fn_c_try_compile "$LINENO"; then : + ac_cv_prog_cc_c99=$ac_arg +fi +rm -f core conftest.err conftest.$ac_objext + test "x$ac_cv_prog_cc_c99" != "xno" && break +done +rm -f conftest.$ac_ext +CC=$ac_save_CC + +fi +# AC_CACHE_VAL +case "x$ac_cv_prog_cc_c99" in + x) + { $as_echo "$as_me:${as_lineno-$LINENO}: result: none needed" >&5 +$as_echo "none needed" >&6; } ;; + xno) + { $as_echo "$as_me:${as_lineno-$LINENO}: result: unsupported" >&5 +$as_echo "unsupported" >&6; } ;; + *) + CC="$CC $ac_cv_prog_cc_c99" + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_c99" >&5 +$as_echo "$ac_cv_prog_cc_c99" >&6; } ;; +esac +if test "x$ac_cv_prog_cc_c99" != xno; then : + +fi + + + +# Mild abuse of the '--enable' option format to allow manual +# specification of setuid or setgid setup in pterm. +setidtype=none +# Check whether --enable-setuid was given. +if test "${enable_setuid+set}" = set; then : + enableval=$enable_setuid; case "$enableval" in + no) setidtype=none;; + *) setidtype=setuid; setidval="$enableval";; + esac +fi + +# Check whether --enable-setgid was given. +if test "${enable_setgid+set}" = set; then : + enableval=$enable_setgid; case "$enableval" in + no) setidtype=none;; + *) setidtype=setgid; setidval="$enableval";; + esac +fi + + if test "$setidtype" != "none"; then + HAVE_SETID_CMD_TRUE= + HAVE_SETID_CMD_FALSE='#' +else + HAVE_SETID_CMD_TRUE='#' + HAVE_SETID_CMD_FALSE= +fi + +if test "x$setidtype" = "xsetuid"; then : + SETID_CMD="chown $setidval"; SETID_MODE="4755" +fi +if test "x$setidtype" = "xsetgid"; then : + SETID_CMD="chgrp $setidval"; SETID_MODE="2755" +fi + + + +# Check whether --enable-git-commit was given. +if test "${enable_git_commit+set}" = set; then : + enableval=$enable_git_commit; +else + if test -d "$srcdir/.git"; then + enable_git_commit=yes; else enable_git_commit=no; fi +fi + + +if test "x$enable_git_commit" = "xyes" -a ! -d "$srcdir/.git"; then + as_fn_error $? "Cannot --enable-git-commit when source tree is not a git checkout" "$LINENO" 5 +fi + if test "x$enable_git_commit" = "xyes"; then + AUTO_GIT_COMMIT_TRUE= + AUTO_GIT_COMMIT_FALSE='#' +else + AUTO_GIT_COMMIT_TRUE='#' + AUTO_GIT_COMMIT_FALSE= +fi + + + +# Check whether --with-gssapi was given. +if test "${with_gssapi+set}" = set; then : + withval=$with_gssapi; +else + with_gssapi=yes +fi + + + +# Check whether --with-quartz was given. +if test "${with_quartz+set}" = set; then : + withval=$with_quartz; +$as_echo "#define OSX_GTK 1" >>confdefs.h + + with_quartz=yes +else + with_quartz=no +fi + + + if test "x$with_quartz" = "xyes"; then + HAVE_QUARTZ_TRUE= + HAVE_QUARTZ_FALSE='#' +else + HAVE_QUARTZ_TRUE='#' + HAVE_QUARTZ_FALSE= +fi + + +WITH_GSSAPI= +if test "x$with_gssapi" != xno; then : + +$as_echo "#define WITH_GSSAPI 1" >>confdefs.h + +fi + + +# Check whether --with-gtk was given. +if test "${with_gtk+set}" = set; then : + withval=$with_gtk; gtk_version_desired="$withval" +else + gtk_version_desired="any" +fi + + +case "$gtk_version_desired" in + 1 | 2 | 3 | any | no) ;; + yes) gtk_version_desired="any" ;; + *) as_fn_error $? "Invalid GTK version specified" "$LINENO" 5 +esac + +for ac_header in utmpx.h +do : + ac_fn_c_check_header_compile "$LINENO" "utmpx.h" "ac_cv_header_utmpx_h" " +#include +#include +" +if test "x$ac_cv_header_utmpx_h" = xyes; then : + cat >>confdefs.h <<_ACEOF +#define HAVE_UTMPX_H 1 +_ACEOF + +fi + +done + + +# Look for GTK 3, GTK 2 and GTK 1, in descending order of preference. +# If we can't find any, have the makefile only build the CLI programs. + +gtk=none + +case "$gtk_version_desired:$gtk" in + 3:none | any:none) + +# Check whether --enable-gtktest was given. +if test "${enable_gtktest+set}" = set; then : + enableval=$enable_gtktest; +else + enable_gtktest=yes +fi + + min_gtk_version=3.0.0 + + pkg_config_args="gtk+-3.0 >= $min_gtk_version" + for module in . + do + case "$module" in + gthread) + pkg_config_args="$pkg_config_args gthread-2.0" + ;; + esac + done + + no_gtk="" + + + + + + + + +if test "x$ac_cv_env_PKG_CONFIG_set" != "xset"; then + if test -n "$ac_tool_prefix"; then + # Extract the first word of "${ac_tool_prefix}pkg-config", so it can be a program name with args. +set dummy ${ac_tool_prefix}pkg-config; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_path_PKG_CONFIG+:} false; then : + $as_echo_n "(cached) " >&6 +else + case $PKG_CONFIG in + [\\/]* | ?:[\\/]*) + ac_cv_path_PKG_CONFIG="$PKG_CONFIG" # Let the user override the test with a path. + ;; + *) + as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_path_PKG_CONFIG="$as_dir/$ac_word$ac_exec_ext" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + + ;; +esac +fi +PKG_CONFIG=$ac_cv_path_PKG_CONFIG +if test -n "$PKG_CONFIG"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $PKG_CONFIG" >&5 +$as_echo "$PKG_CONFIG" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + +fi +if test -z "$ac_cv_path_PKG_CONFIG"; then + ac_pt_PKG_CONFIG=$PKG_CONFIG + # Extract the first word of "pkg-config", so it can be a program name with args. +set dummy pkg-config; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_path_ac_pt_PKG_CONFIG+:} false; then : + $as_echo_n "(cached) " >&6 +else + case $ac_pt_PKG_CONFIG in + [\\/]* | ?:[\\/]*) + ac_cv_path_ac_pt_PKG_CONFIG="$ac_pt_PKG_CONFIG" # Let the user override the test with a path. + ;; + *) + as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_path_ac_pt_PKG_CONFIG="$as_dir/$ac_word$ac_exec_ext" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + + ;; +esac +fi +ac_pt_PKG_CONFIG=$ac_cv_path_ac_pt_PKG_CONFIG +if test -n "$ac_pt_PKG_CONFIG"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_pt_PKG_CONFIG" >&5 +$as_echo "$ac_pt_PKG_CONFIG" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + if test "x$ac_pt_PKG_CONFIG" = x; then + PKG_CONFIG="" + else + case $cross_compiling:$ac_tool_warned in +yes:) +{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5 +$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;} +ac_tool_warned=yes ;; +esac + PKG_CONFIG=$ac_pt_PKG_CONFIG + fi +else + PKG_CONFIG="$ac_cv_path_PKG_CONFIG" +fi + +fi +if test -n "$PKG_CONFIG"; then + _pkg_min_version=0.16 + { $as_echo "$as_me:${as_lineno-$LINENO}: checking pkg-config is at least version $_pkg_min_version" >&5 +$as_echo_n "checking pkg-config is at least version $_pkg_min_version... " >&6; } + if $PKG_CONFIG --atleast-pkgconfig-version $_pkg_min_version; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5 +$as_echo "yes" >&6; } + else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } + PKG_CONFIG="" + fi +fi + + if test -z "$PKG_CONFIG"; then + no_gtk=yes + fi + + { $as_echo "$as_me:${as_lineno-$LINENO}: checking for GTK+ - version >= $min_gtk_version" >&5 +$as_echo_n "checking for GTK+ - version >= $min_gtk_version... " >&6; } + + if test -n "$PKG_CONFIG"; then + ## don't try to run the test against uninstalled libtool libs + if $PKG_CONFIG --uninstalled $pkg_config_args; then + echo "Will use uninstalled version of GTK+ found in PKG_CONFIG_PATH" + enable_gtktest=no + fi + + if $PKG_CONFIG $pkg_config_args; then + : + else + no_gtk=yes + fi + fi + + if test x"$no_gtk" = x ; then + GTK_CFLAGS=`$PKG_CONFIG $pkg_config_args --cflags` + GTK_LIBS=`$PKG_CONFIG $pkg_config_args --libs` + gtk_config_major_version=`$PKG_CONFIG --modversion gtk+-3.0 | \ + sed 's/\([0-9]*\).\([0-9]*\).\([0-9]*\)/\1/'` + gtk_config_minor_version=`$PKG_CONFIG --modversion gtk+-3.0 | \ + sed 's/\([0-9]*\).\([0-9]*\).\([0-9]*\)/\2/'` + gtk_config_micro_version=`$PKG_CONFIG --modversion gtk+-3.0 | \ + sed 's/\([0-9]*\).\([0-9]*\).\([0-9]*\)/\3/'` + if test "x$enable_gtktest" = "xyes" ; then + ac_save_CFLAGS="$CFLAGS" + ac_save_LIBS="$LIBS" + CFLAGS="$CFLAGS $GTK_CFLAGS" + LIBS="$GTK_LIBS $LIBS" + rm -f conf.gtktest + if test "$cross_compiling" = yes; then : + echo $ac_n "cross compiling; assumed OK... $ac_c" +else + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ + +#include +#include +#include + +int +main () +{ + unsigned int major, minor, micro; + + fclose (fopen ("conf.gtktest", "w")); + + if (sscanf("$min_gtk_version", "%u.%u.%u", &major, &minor, µ) != 3) { + printf("%s, bad version string\n", "$min_gtk_version"); + exit(1); + } + + if ((gtk_major_version != $gtk_config_major_version) || + (gtk_minor_version != $gtk_config_minor_version) || + (gtk_micro_version != $gtk_config_micro_version)) + { + printf("\n*** 'pkg-config --modversion gtk+-3.0' returned %d.%d.%d, but GTK+ (%d.%d.%d)\n", + $gtk_config_major_version, $gtk_config_minor_version, $gtk_config_micro_version, + gtk_major_version, gtk_minor_version, gtk_micro_version); + printf ("*** was found! If pkg-config was correct, then it is best\n"); + printf ("*** to remove the old version of GTK+. You may also be able to fix the error\n"); + printf("*** by modifying your LD_LIBRARY_PATH enviroment variable, or by editing\n"); + printf("*** /etc/ld.so.conf. Make sure you have run ldconfig if that is\n"); + printf("*** required on your system.\n"); + printf("*** If pkg-config was wrong, set the environment variable PKG_CONFIG_PATH\n"); + printf("*** to point to the correct configuration files\n"); + } + else if ((gtk_major_version != GTK_MAJOR_VERSION) || + (gtk_minor_version != GTK_MINOR_VERSION) || + (gtk_micro_version != GTK_MICRO_VERSION)) + { + printf("*** GTK+ header files (version %d.%d.%d) do not match\n", + GTK_MAJOR_VERSION, GTK_MINOR_VERSION, GTK_MICRO_VERSION); + printf("*** library (version %d.%d.%d)\n", + gtk_major_version, gtk_minor_version, gtk_micro_version); + } + else + { + if ((gtk_major_version > major) || + ((gtk_major_version == major) && (gtk_minor_version > minor)) || + ((gtk_major_version == major) && (gtk_minor_version == minor) && (gtk_micro_version >= micro))) + { + return 0; + } + else + { + printf("\n*** An old version of GTK+ (%u.%u.%u) was found.\n", + gtk_major_version, gtk_minor_version, gtk_micro_version); + printf("*** You need a version of GTK+ newer than %u.%u.%u. The latest version of\n", + major, minor, micro); + printf("*** GTK+ is always available from ftp://ftp.gtk.org.\n"); + printf("***\n"); + printf("*** If you have already installed a sufficiently new version, this error\n"); + printf("*** probably means that the wrong copy of the pkg-config shell script is\n"); + printf("*** being found. The easiest way to fix this is to remove the old version\n"); + printf("*** of GTK+, but you can also set the PKG_CONFIG environment to point to the\n"); + printf("*** correct copy of pkg-config. (In this case, you will have to\n"); + printf("*** modify your LD_LIBRARY_PATH enviroment variable, or edit /etc/ld.so.conf\n"); + printf("*** so that the correct libraries are found at run-time))\n"); + } + } + return 1; +} + +_ACEOF +if ac_fn_c_try_run "$LINENO"; then : + +else + no_gtk=yes +fi +rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \ + conftest.$ac_objext conftest.beam conftest.$ac_ext +fi + + CFLAGS="$ac_save_CFLAGS" + LIBS="$ac_save_LIBS" + fi + fi + if test "x$no_gtk" = x ; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: yes (version $gtk_config_major_version.$gtk_config_minor_version.$gtk_config_micro_version)" >&5 +$as_echo "yes (version $gtk_config_major_version.$gtk_config_minor_version.$gtk_config_micro_version)" >&6; } + gtk=3 + else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } + if test -z "$PKG_CONFIG"; then + echo "*** A new enough version of pkg-config was not found." + echo "*** See http://pkgconfig.sourceforge.net" + else + if test -f conf.gtktest ; then + : + else + echo "*** Could not run GTK+ test program, checking why..." + ac_save_CFLAGS="$CFLAGS" + ac_save_LIBS="$LIBS" + CFLAGS="$CFLAGS $GTK_CFLAGS" + LIBS="$LIBS $GTK_LIBS" + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ + +#include +#include + +int +main () +{ + return ((gtk_major_version) || (gtk_minor_version) || (gtk_micro_version)); + ; + return 0; +} +_ACEOF +if ac_fn_c_try_link "$LINENO"; then : + echo "*** The test program compiled, but did not run. This usually means" + echo "*** that the run-time linker is not finding GTK+ or finding the wrong" + echo "*** version of GTK+. If it is not finding GTK+, you'll need to set your" + echo "*** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point" + echo "*** to the installed location Also, make sure you have run ldconfig if that" + echo "*** is required on your system" + echo "***" + echo "*** If you have an old version installed, it is best to remove it, although" + echo "*** you may also be able to get things to work by modifying LD_LIBRARY_PATH" +else + echo "*** The test program failed to compile or link. See the file config.log for the" + echo "*** exact error that occurred. This usually means GTK+ is incorrectly installed." +fi +rm -f core conftest.err conftest.$ac_objext \ + conftest$ac_exeext conftest.$ac_ext + CFLAGS="$ac_save_CFLAGS" + LIBS="$ac_save_LIBS" + fi + fi + GTK_CFLAGS="" + GTK_LIBS="" + : + fi + + + rm -f conf.gtktest + + ;; +esac + +case "$gtk_version_desired:$gtk" in + 2:none | any:none) + # Check whether --enable-gtktest was given. +if test "${enable_gtktest+set}" = set; then : + enableval=$enable_gtktest; +else + enable_gtktest=yes +fi + + + pkg_config_args=gtk+-2.0 + for module in . + do + case "$module" in + gthread) + pkg_config_args="$pkg_config_args gthread-2.0" + ;; + esac + done + + no_gtk="" + + + + + + + + + +if test "x$ac_cv_env_PKG_CONFIG_set" != "xset"; then + if test -n "$ac_tool_prefix"; then + # Extract the first word of "${ac_tool_prefix}pkg-config", so it can be a program name with args. +set dummy ${ac_tool_prefix}pkg-config; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_path_PKG_CONFIG+:} false; then : + $as_echo_n "(cached) " >&6 +else + case $PKG_CONFIG in + [\\/]* | ?:[\\/]*) + ac_cv_path_PKG_CONFIG="$PKG_CONFIG" # Let the user override the test with a path. + ;; + *) + as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_path_PKG_CONFIG="$as_dir/$ac_word$ac_exec_ext" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + + ;; +esac +fi +PKG_CONFIG=$ac_cv_path_PKG_CONFIG +if test -n "$PKG_CONFIG"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $PKG_CONFIG" >&5 +$as_echo "$PKG_CONFIG" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + +fi +if test -z "$ac_cv_path_PKG_CONFIG"; then + ac_pt_PKG_CONFIG=$PKG_CONFIG + # Extract the first word of "pkg-config", so it can be a program name with args. +set dummy pkg-config; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_path_ac_pt_PKG_CONFIG+:} false; then : + $as_echo_n "(cached) " >&6 +else + case $ac_pt_PKG_CONFIG in + [\\/]* | ?:[\\/]*) + ac_cv_path_ac_pt_PKG_CONFIG="$ac_pt_PKG_CONFIG" # Let the user override the test with a path. + ;; + *) + as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_path_ac_pt_PKG_CONFIG="$as_dir/$ac_word$ac_exec_ext" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + + ;; +esac +fi +ac_pt_PKG_CONFIG=$ac_cv_path_ac_pt_PKG_CONFIG +if test -n "$ac_pt_PKG_CONFIG"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_pt_PKG_CONFIG" >&5 +$as_echo "$ac_pt_PKG_CONFIG" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + if test "x$ac_pt_PKG_CONFIG" = x; then + PKG_CONFIG="" + else + case $cross_compiling:$ac_tool_warned in +yes:) +{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5 +$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;} +ac_tool_warned=yes ;; +esac + PKG_CONFIG=$ac_pt_PKG_CONFIG + fi +else + PKG_CONFIG="$ac_cv_path_PKG_CONFIG" +fi + +fi +if test -n "$PKG_CONFIG"; then + _pkg_min_version=0.7 + { $as_echo "$as_me:${as_lineno-$LINENO}: checking pkg-config is at least version $_pkg_min_version" >&5 +$as_echo_n "checking pkg-config is at least version $_pkg_min_version... " >&6; } + if $PKG_CONFIG --atleast-pkgconfig-version $_pkg_min_version; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5 +$as_echo "yes" >&6; } + else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } + PKG_CONFIG="" + fi +fi + + min_gtk_version=2.0.0 + { $as_echo "$as_me:${as_lineno-$LINENO}: checking for GTK+ - version >= $min_gtk_version" >&5 +$as_echo_n "checking for GTK+ - version >= $min_gtk_version... " >&6; } + + if test x$PKG_CONFIG != xno ; then + ## don't try to run the test against uninstalled libtool libs + if $PKG_CONFIG --uninstalled $pkg_config_args; then + echo "Will use uninstalled version of GTK+ found in PKG_CONFIG_PATH" + enable_gtktest=no + fi + + if $PKG_CONFIG --atleast-version $min_gtk_version $pkg_config_args; then + : + else + no_gtk=yes + fi + fi + + if test x"$no_gtk" = x ; then + GTK_CFLAGS=`$PKG_CONFIG $pkg_config_args --cflags` + GTK_LIBS=`$PKG_CONFIG $pkg_config_args --libs` + gtk_config_major_version=`$PKG_CONFIG --modversion gtk+-2.0 | \ + sed 's/\([0-9]*\).\([0-9]*\).\([0-9]*\)/\1/'` + gtk_config_minor_version=`$PKG_CONFIG --modversion gtk+-2.0 | \ + sed 's/\([0-9]*\).\([0-9]*\).\([0-9]*\)/\2/'` + gtk_config_micro_version=`$PKG_CONFIG --modversion gtk+-2.0 | \ + sed 's/\([0-9]*\).\([0-9]*\).\([0-9]*\)/\3/'` + if test "x$enable_gtktest" = "xyes" ; then + ac_save_CFLAGS="$CFLAGS" + ac_save_LIBS="$LIBS" + CFLAGS="$CFLAGS $GTK_CFLAGS" + LIBS="$GTK_LIBS $LIBS" + rm -f conf.gtktest + if test "$cross_compiling" = yes; then : + echo $ac_n "cross compiling; assumed OK... $ac_c" +else + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ + +#include +#include +#include + +int +main () +{ + int major, minor, micro; + char *tmp_version; + + fclose (fopen ("conf.gtktest", "w")); + + /* HP/UX 9 (%@#!) writes to sscanf strings */ + tmp_version = g_strdup("$min_gtk_version"); + if (sscanf(tmp_version, "%d.%d.%d", &major, &minor, µ) != 3) { + printf("%s, bad version string\n", "$min_gtk_version"); + exit(1); + } + + if ((gtk_major_version != $gtk_config_major_version) || + (gtk_minor_version != $gtk_config_minor_version) || + (gtk_micro_version != $gtk_config_micro_version)) + { + printf("\n*** 'pkg-config --modversion gtk+-2.0' returned %d.%d.%d, but GTK+ (%d.%d.%d)\n", + $gtk_config_major_version, $gtk_config_minor_version, $gtk_config_micro_version, + gtk_major_version, gtk_minor_version, gtk_micro_version); + printf ("*** was found! If pkg-config was correct, then it is best\n"); + printf ("*** to remove the old version of GTK+. You may also be able to fix the error\n"); + printf("*** by modifying your LD_LIBRARY_PATH enviroment variable, or by editing\n"); + printf("*** /etc/ld.so.conf. Make sure you have run ldconfig if that is\n"); + printf("*** required on your system.\n"); + printf("*** If pkg-config was wrong, set the environment variable PKG_CONFIG_PATH\n"); + printf("*** to point to the correct configuration files\n"); + } + else if ((gtk_major_version != GTK_MAJOR_VERSION) || + (gtk_minor_version != GTK_MINOR_VERSION) || + (gtk_micro_version != GTK_MICRO_VERSION)) + { + printf("*** GTK+ header files (version %d.%d.%d) do not match\n", + GTK_MAJOR_VERSION, GTK_MINOR_VERSION, GTK_MICRO_VERSION); + printf("*** library (version %d.%d.%d)\n", + gtk_major_version, gtk_minor_version, gtk_micro_version); + } + else + { + if ((gtk_major_version > major) || + ((gtk_major_version == major) && (gtk_minor_version > minor)) || + ((gtk_major_version == major) && (gtk_minor_version == minor) && (gtk_micro_version >= micro))) + { + return 0; + } + else + { + printf("\n*** An old version of GTK+ (%d.%d.%d) was found.\n", + gtk_major_version, gtk_minor_version, gtk_micro_version); + printf("*** You need a version of GTK+ newer than %d.%d.%d. The latest version of\n", + major, minor, micro); + printf("*** GTK+ is always available from ftp://ftp.gtk.org.\n"); + printf("***\n"); + printf("*** If you have already installed a sufficiently new version, this error\n"); + printf("*** probably means that the wrong copy of the pkg-config shell script is\n"); + printf("*** being found. The easiest way to fix this is to remove the old version\n"); + printf("*** of GTK+, but you can also set the PKG_CONFIG environment to point to the\n"); + printf("*** correct copy of pkg-config. (In this case, you will have to\n"); + printf("*** modify your LD_LIBRARY_PATH enviroment variable, or edit /etc/ld.so.conf\n"); + printf("*** so that the correct libraries are found at run-time))\n"); + } + } + return 1; +} + +_ACEOF +if ac_fn_c_try_run "$LINENO"; then : + +else + no_gtk=yes +fi +rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \ + conftest.$ac_objext conftest.beam conftest.$ac_ext +fi + + CFLAGS="$ac_save_CFLAGS" + LIBS="$ac_save_LIBS" + fi + fi + if test "x$no_gtk" = x ; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: yes (version $gtk_config_major_version.$gtk_config_minor_version.$gtk_config_micro_version)" >&5 +$as_echo "yes (version $gtk_config_major_version.$gtk_config_minor_version.$gtk_config_micro_version)" >&6; } + gtk=2 + else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } + if test "$PKG_CONFIG" = "no" ; then + echo "*** A new enough version of pkg-config was not found." + echo "*** See http://pkgconfig.sourceforge.net" + else + if test -f conf.gtktest ; then + : + else + echo "*** Could not run GTK+ test program, checking why..." + ac_save_CFLAGS="$CFLAGS" + ac_save_LIBS="$LIBS" + CFLAGS="$CFLAGS $GTK_CFLAGS" + LIBS="$LIBS $GTK_LIBS" + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ + +#include +#include + +int +main () +{ + return ((gtk_major_version) || (gtk_minor_version) || (gtk_micro_version)); + ; + return 0; +} +_ACEOF +if ac_fn_c_try_link "$LINENO"; then : + echo "*** The test program compiled, but did not run. This usually means" + echo "*** that the run-time linker is not finding GTK+ or finding the wrong" + echo "*** version of GTK+. If it is not finding GTK+, you'll need to set your" + echo "*** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point" + echo "*** to the installed location Also, make sure you have run ldconfig if that" + echo "*** is required on your system" + echo "***" + echo "*** If you have an old version installed, it is best to remove it, although" + echo "*** you may also be able to get things to work by modifying LD_LIBRARY_PATH" +else + echo "*** The test program failed to compile or link. See the file config.log for the" + echo "*** exact error that occured. This usually means GTK+ is incorrectly installed." +fi +rm -f core conftest.err conftest.$ac_objext \ + conftest$ac_exeext conftest.$ac_ext + CFLAGS="$ac_save_CFLAGS" + LIBS="$ac_save_LIBS" + fi + fi + GTK_CFLAGS="" + GTK_LIBS="" + : + fi + + + rm -f conf.gtktest + + ;; +esac + +case "$gtk_version_desired:$gtk" in + 1:none | any:none) + + # manual check for gtk1 + # Extract the first word of "gtk-config", so it can be a program name with args. +set dummy gtk-config; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_path_GTK1_CONFIG+:} false; then : + $as_echo_n "(cached) " >&6 +else + case $GTK1_CONFIG in + [\\/]* | ?:[\\/]*) + ac_cv_path_GTK1_CONFIG="$GTK1_CONFIG" # Let the user override the test with a path. + ;; + *) + as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_path_GTK1_CONFIG="$as_dir/$ac_word$ac_exec_ext" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + + test -z "$ac_cv_path_GTK1_CONFIG" && ac_cv_path_GTK1_CONFIG="absent" + ;; +esac +fi +GTK1_CONFIG=$ac_cv_path_GTK1_CONFIG +if test -n "$GTK1_CONFIG"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $GTK1_CONFIG" >&5 +$as_echo "$GTK1_CONFIG" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + + if test "$GTK1_CONFIG" != "absent"; then + GTK_CFLAGS="`"$GTK1_CONFIG" --cflags`" + GTK_LIBS=`"$GTK1_CONFIG" --libs` + + + gtk=1 + fi + + ;; +esac + +case "$gtk" in + 1) + # Add some manual #defines to make the GTK 1 headers work when + # compiling in C99 mode. Left to themselves, they'll expect the + # old-style pre-C99 GNU semantics of 'inline' and 'extern inline', + # with the effect that they'll end up defining out-of-line + # versions of the inlined functions in more than one translation + # unit and cause a link failure. Override them to 'static inline', + # which is safe. + GTK_CFLAGS="$GTK_CFLAGS -DG_INLINE_FUNC='static inline' -DG_CAN_INLINE=1" +esac + + if test "$gtk" != "none"; then + HAVE_GTK_TRUE= + HAVE_GTK_FALSE='#' +else + HAVE_GTK_TRUE='#' + HAVE_GTK_FALSE= +fi + + +if test "$gtk" = "2" -o "$gtk" = "3"; then + ac_save_CFLAGS="$CFLAGS" + ac_save_LIBS="$LIBS" + CFLAGS="$CFLAGS $GTK_CFLAGS" + LIBS="$GTK_LIBS $LIBS" + for ac_func in pango_font_family_is_monospace pango_font_map_list_families +do : + as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +ac_fn_c_check_func "$LINENO" "$ac_func" "$as_ac_var" +if eval test \"x\$"$as_ac_var"\" = x"yes"; then : + cat >>confdefs.h <<_ACEOF +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 +_ACEOF + +fi +done + + CFLAGS="$ac_save_CFLAGS" + LIBS="$ac_save_LIBS" +fi + +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for library containing socket" >&5 +$as_echo_n "checking for library containing socket... " >&6; } +if ${ac_cv_search_socket+:} false; then : + $as_echo_n "(cached) " >&6 +else + ac_func_search_save_LIBS=$LIBS +cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ + +/* Override any GCC internal prototype to avoid an error. + Use char because int might match the return type of a GCC + builtin and then its argument prototype would still apply. */ +#ifdef __cplusplus +extern "C" +#endif +char socket (); +int +main () +{ +return socket (); + ; + return 0; +} +_ACEOF +for ac_lib in '' xnet; do + if test -z "$ac_lib"; then + ac_res="none required" + else + ac_res=-l$ac_lib + LIBS="-l$ac_lib $ac_func_search_save_LIBS" + fi + if ac_fn_c_try_link "$LINENO"; then : + ac_cv_search_socket=$ac_res +fi +rm -f core conftest.err conftest.$ac_objext \ + conftest$ac_exeext + if ${ac_cv_search_socket+:} false; then : + break +fi +done +if ${ac_cv_search_socket+:} false; then : + +else + ac_cv_search_socket=no +fi +rm conftest.$ac_ext +LIBS=$ac_func_search_save_LIBS +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_search_socket" >&5 +$as_echo "$ac_cv_search_socket" >&6; } +ac_res=$ac_cv_search_socket +if test "$ac_res" != no; then : + test "$ac_res" = "none required" || LIBS="$ac_res $LIBS" + +fi + + +ac_ext=c +ac_cpp='$CPP $CPPFLAGS' +ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' +ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' +ac_compiler_gnu=$ac_cv_c_compiler_gnu +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking how to run the C preprocessor" >&5 +$as_echo_n "checking how to run the C preprocessor... " >&6; } +# On Suns, sometimes $CPP names a directory. +if test -n "$CPP" && test -d "$CPP"; then + CPP= +fi +if test -z "$CPP"; then + if ${ac_cv_prog_CPP+:} false; then : + $as_echo_n "(cached) " >&6 +else + # Double quotes because CPP needs to be expanded + for CPP in "$CC -E" "$CC -E -traditional-cpp" "/lib/cpp" + do + ac_preproc_ok=false +for ac_c_preproc_warn_flag in '' yes +do + # Use a header file that comes with gcc, so configuring glibc + # with a fresh cross-compiler works. + # Prefer to if __STDC__ is defined, since + # exists even on freestanding compilers. + # On the NeXT, cc -E runs the code through the compiler's parser, + # not just through cpp. "Syntax error" is here to catch this case. + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ +#ifdef __STDC__ +# include +#else +# include +#endif + Syntax error +_ACEOF +if ac_fn_c_try_cpp "$LINENO"; then : + +else + # Broken: fails on valid input. +continue +fi +rm -f conftest.err conftest.i conftest.$ac_ext + + # OK, works on sane cases. Now check whether nonexistent headers + # can be detected and how. + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ +#include +_ACEOF +if ac_fn_c_try_cpp "$LINENO"; then : + # Broken: success on invalid input. +continue +else + # Passes both tests. +ac_preproc_ok=: +break +fi +rm -f conftest.err conftest.i conftest.$ac_ext + +done +# Because of `break', _AC_PREPROC_IFELSE's cleaning code was skipped. +rm -f conftest.i conftest.err conftest.$ac_ext +if $ac_preproc_ok; then : + break +fi + + done + ac_cv_prog_CPP=$CPP + +fi + CPP=$ac_cv_prog_CPP +else + ac_cv_prog_CPP=$CPP +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $CPP" >&5 +$as_echo "$CPP" >&6; } +ac_preproc_ok=false +for ac_c_preproc_warn_flag in '' yes +do + # Use a header file that comes with gcc, so configuring glibc + # with a fresh cross-compiler works. + # Prefer to if __STDC__ is defined, since + # exists even on freestanding compilers. + # On the NeXT, cc -E runs the code through the compiler's parser, + # not just through cpp. "Syntax error" is here to catch this case. + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ +#ifdef __STDC__ +# include +#else +# include +#endif + Syntax error +_ACEOF +if ac_fn_c_try_cpp "$LINENO"; then : + +else + # Broken: fails on valid input. +continue +fi +rm -f conftest.err conftest.i conftest.$ac_ext + + # OK, works on sane cases. Now check whether nonexistent headers + # can be detected and how. + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ +#include +_ACEOF +if ac_fn_c_try_cpp "$LINENO"; then : + # Broken: success on invalid input. +continue +else + # Passes both tests. +ac_preproc_ok=: +break +fi +rm -f conftest.err conftest.i conftest.$ac_ext + +done +# Because of `break', _AC_PREPROC_IFELSE's cleaning code was skipped. +rm -f conftest.i conftest.err conftest.$ac_ext +if $ac_preproc_ok; then : + +else + { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +as_fn_error $? "C preprocessor \"$CPP\" fails sanity check +See \`config.log' for more details" "$LINENO" 5; } +fi + +ac_ext=c +ac_cpp='$CPP $CPPFLAGS' +ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5' +ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5' +ac_compiler_gnu=$ac_cv_c_compiler_gnu + + +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for grep that handles long lines and -e" >&5 +$as_echo_n "checking for grep that handles long lines and -e... " >&6; } +if ${ac_cv_path_GREP+:} false; then : + $as_echo_n "(cached) " >&6 +else + if test -z "$GREP"; then + ac_path_GREP_found=false + # Loop through the user's path and test for each of PROGNAME-LIST + as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH$PATH_SEPARATOR/usr/xpg4/bin +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_prog in grep ggrep; do + for ac_exec_ext in '' $ac_executable_extensions; do + ac_path_GREP="$as_dir/$ac_prog$ac_exec_ext" + as_fn_executable_p "$ac_path_GREP" || continue +# Check for GNU ac_path_GREP and select it if it is found. + # Check for GNU $ac_path_GREP +case `"$ac_path_GREP" --version 2>&1` in +*GNU*) + ac_cv_path_GREP="$ac_path_GREP" ac_path_GREP_found=:;; +*) + ac_count=0 + $as_echo_n 0123456789 >"conftest.in" + while : + do + cat "conftest.in" "conftest.in" >"conftest.tmp" + mv "conftest.tmp" "conftest.in" + cp "conftest.in" "conftest.nl" + $as_echo 'GREP' >> "conftest.nl" + "$ac_path_GREP" -e 'GREP$' -e '-(cannot match)-' < "conftest.nl" >"conftest.out" 2>/dev/null || break + diff "conftest.out" "conftest.nl" >/dev/null 2>&1 || break + as_fn_arith $ac_count + 1 && ac_count=$as_val + if test $ac_count -gt ${ac_path_GREP_max-0}; then + # Best one so far, save it but keep looking for a better one + ac_cv_path_GREP="$ac_path_GREP" + ac_path_GREP_max=$ac_count + fi + # 10*(2^10) chars as input seems more than enough + test $ac_count -gt 10 && break + done + rm -f conftest.in conftest.tmp conftest.nl conftest.out;; +esac + + $ac_path_GREP_found && break 3 + done + done + done +IFS=$as_save_IFS + if test -z "$ac_cv_path_GREP"; then + as_fn_error $? "no acceptable grep could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" "$LINENO" 5 + fi +else + ac_cv_path_GREP=$GREP +fi + +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_path_GREP" >&5 +$as_echo "$ac_cv_path_GREP" >&6; } + GREP="$ac_cv_path_GREP" + + +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for egrep" >&5 +$as_echo_n "checking for egrep... " >&6; } +if ${ac_cv_path_EGREP+:} false; then : + $as_echo_n "(cached) " >&6 +else + if echo a | $GREP -E '(a|b)' >/dev/null 2>&1 + then ac_cv_path_EGREP="$GREP -E" + else + if test -z "$EGREP"; then + ac_path_EGREP_found=false + # Loop through the user's path and test for each of PROGNAME-LIST + as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH$PATH_SEPARATOR/usr/xpg4/bin +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_prog in egrep; do + for ac_exec_ext in '' $ac_executable_extensions; do + ac_path_EGREP="$as_dir/$ac_prog$ac_exec_ext" + as_fn_executable_p "$ac_path_EGREP" || continue +# Check for GNU ac_path_EGREP and select it if it is found. + # Check for GNU $ac_path_EGREP +case `"$ac_path_EGREP" --version 2>&1` in +*GNU*) + ac_cv_path_EGREP="$ac_path_EGREP" ac_path_EGREP_found=:;; +*) + ac_count=0 + $as_echo_n 0123456789 >"conftest.in" + while : + do + cat "conftest.in" "conftest.in" >"conftest.tmp" + mv "conftest.tmp" "conftest.in" + cp "conftest.in" "conftest.nl" + $as_echo 'EGREP' >> "conftest.nl" + "$ac_path_EGREP" 'EGREP$' < "conftest.nl" >"conftest.out" 2>/dev/null || break + diff "conftest.out" "conftest.nl" >/dev/null 2>&1 || break + as_fn_arith $ac_count + 1 && ac_count=$as_val + if test $ac_count -gt ${ac_path_EGREP_max-0}; then + # Best one so far, save it but keep looking for a better one + ac_cv_path_EGREP="$ac_path_EGREP" + ac_path_EGREP_max=$ac_count + fi + # 10*(2^10) chars as input seems more than enough + test $ac_count -gt 10 && break + done + rm -f conftest.in conftest.tmp conftest.nl conftest.out;; +esac + + $ac_path_EGREP_found && break 3 + done + done + done +IFS=$as_save_IFS + if test -z "$ac_cv_path_EGREP"; then + as_fn_error $? "no acceptable egrep could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" "$LINENO" 5 + fi +else + ac_cv_path_EGREP=$EGREP +fi + + fi +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_path_EGREP" >&5 +$as_echo "$ac_cv_path_EGREP" >&6; } + EGREP="$ac_cv_path_EGREP" + + +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for ANSI C header files" >&5 +$as_echo_n "checking for ANSI C header files... " >&6; } +if ${ac_cv_header_stdc+:} false; then : + $as_echo_n "(cached) " >&6 +else + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ +#include +#include +#include +#include + +int +main () +{ + + ; + return 0; +} +_ACEOF +if ac_fn_c_try_compile "$LINENO"; then : + ac_cv_header_stdc=yes +else + ac_cv_header_stdc=no +fi +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext + +if test $ac_cv_header_stdc = yes; then + # SunOS 4.x string.h does not declare mem*, contrary to ANSI. + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ +#include + +_ACEOF +if (eval "$ac_cpp conftest.$ac_ext") 2>&5 | + $EGREP "memchr" >/dev/null 2>&1; then : + +else + ac_cv_header_stdc=no +fi +rm -f conftest* + +fi + +if test $ac_cv_header_stdc = yes; then + # ISC 2.0.2 stdlib.h does not declare free, contrary to ANSI. + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ +#include + +_ACEOF +if (eval "$ac_cpp conftest.$ac_ext") 2>&5 | + $EGREP "free" >/dev/null 2>&1; then : + +else + ac_cv_header_stdc=no +fi +rm -f conftest* + +fi + +if test $ac_cv_header_stdc = yes; then + # /bin/cc in Irix-4.0.5 gets non-ANSI ctype macros unless using -ansi. + if test "$cross_compiling" = yes; then : + : +else + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ +#include +#include +#if ((' ' & 0x0FF) == 0x020) +# define ISLOWER(c) ('a' <= (c) && (c) <= 'z') +# define TOUPPER(c) (ISLOWER(c) ? 'A' + ((c) - 'a') : (c)) +#else +# define ISLOWER(c) \ + (('a' <= (c) && (c) <= 'i') \ + || ('j' <= (c) && (c) <= 'r') \ + || ('s' <= (c) && (c) <= 'z')) +# define TOUPPER(c) (ISLOWER(c) ? ((c) | 0x40) : (c)) +#endif + +#define XOR(e, f) (((e) && !(f)) || (!(e) && (f))) +int +main () +{ + int i; + for (i = 0; i < 256; i++) + if (XOR (islower (i), ISLOWER (i)) + || toupper (i) != TOUPPER (i)) + return 2; + return 0; +} +_ACEOF +if ac_fn_c_try_run "$LINENO"; then : + +else + ac_cv_header_stdc=no +fi +rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \ + conftest.$ac_objext conftest.beam conftest.$ac_ext +fi + +fi +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_header_stdc" >&5 +$as_echo "$ac_cv_header_stdc" >&6; } +if test $ac_cv_header_stdc = yes; then + +$as_echo "#define STDC_HEADERS 1" >>confdefs.h + +fi + +# On IRIX 5.3, sys/types and inttypes.h are conflicting. +for ac_header in sys/types.h sys/stat.h stdlib.h string.h memory.h strings.h \ + inttypes.h stdint.h unistd.h +do : + as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` +ac_fn_c_check_header_compile "$LINENO" "$ac_header" "$as_ac_Header" "$ac_includes_default +" +if eval test \"x\$"$as_ac_Header"\" = x"yes"; then : + cat >>confdefs.h <<_ACEOF +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 +_ACEOF + +fi + +done + + +if test "x$with_gssapi" != xno; then : + { $as_echo "$as_me:${as_lineno-$LINENO}: checking for library containing dlopen" >&5 +$as_echo_n "checking for library containing dlopen... " >&6; } +if ${ac_cv_search_dlopen+:} false; then : + $as_echo_n "(cached) " >&6 +else + ac_func_search_save_LIBS=$LIBS +cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ + +/* Override any GCC internal prototype to avoid an error. + Use char because int might match the return type of a GCC + builtin and then its argument prototype would still apply. */ +#ifdef __cplusplus +extern "C" +#endif +char dlopen (); +int +main () +{ +return dlopen (); + ; + return 0; +} +_ACEOF +for ac_lib in '' dl; do + if test -z "$ac_lib"; then + ac_res="none required" + else + ac_res=-l$ac_lib + LIBS="-l$ac_lib $ac_func_search_save_LIBS" + fi + if ac_fn_c_try_link "$LINENO"; then : + ac_cv_search_dlopen=$ac_res +fi +rm -f core conftest.err conftest.$ac_objext \ + conftest$ac_exeext + if ${ac_cv_search_dlopen+:} false; then : + break +fi +done +if ${ac_cv_search_dlopen+:} false; then : + +else + ac_cv_search_dlopen=no +fi +rm conftest.$ac_ext +LIBS=$ac_func_search_save_LIBS +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_search_dlopen" >&5 +$as_echo "$ac_cv_search_dlopen" >&6; } +ac_res=$ac_cv_search_dlopen +if test "$ac_res" != no; then : + test "$ac_res" = "none required" || LIBS="$ac_res $LIBS" + +else + +$as_echo "#define NO_LIBDL 1" >>confdefs.h + + for ac_header in gssapi/gssapi.h +do : + ac_fn_c_check_header_mongrel "$LINENO" "gssapi/gssapi.h" "ac_cv_header_gssapi_gssapi_h" "$ac_includes_default" +if test "x$ac_cv_header_gssapi_gssapi_h" = xyes; then : + cat >>confdefs.h <<_ACEOF +#define HAVE_GSSAPI_GSSAPI_H 1 +_ACEOF + +fi + +done + + { $as_echo "$as_me:${as_lineno-$LINENO}: checking for library containing gss_init_sec_context" >&5 +$as_echo_n "checking for library containing gss_init_sec_context... " >&6; } +if ${ac_cv_search_gss_init_sec_context+:} false; then : + $as_echo_n "(cached) " >&6 +else + ac_func_search_save_LIBS=$LIBS +cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ + +/* Override any GCC internal prototype to avoid an error. + Use char because int might match the return type of a GCC + builtin and then its argument prototype would still apply. */ +#ifdef __cplusplus +extern "C" +#endif +char gss_init_sec_context (); +int +main () +{ +return gss_init_sec_context (); + ; + return 0; +} +_ACEOF +for ac_lib in '' gssapi gssapi_krb5 gss; do + if test -z "$ac_lib"; then + ac_res="none required" + else + ac_res=-l$ac_lib + LIBS="-l$ac_lib $ac_func_search_save_LIBS" + fi + if ac_fn_c_try_link "$LINENO"; then : + ac_cv_search_gss_init_sec_context=$ac_res +fi +rm -f core conftest.err conftest.$ac_objext \ + conftest$ac_exeext + if ${ac_cv_search_gss_init_sec_context+:} false; then : + break +fi +done +if ${ac_cv_search_gss_init_sec_context+:} false; then : + +else + ac_cv_search_gss_init_sec_context=no +fi +rm conftest.$ac_ext +LIBS=$ac_func_search_save_LIBS +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_search_gss_init_sec_context" >&5 +$as_echo "$ac_cv_search_gss_init_sec_context" >&6; } +ac_res=$ac_cv_search_gss_init_sec_context +if test "$ac_res" != no; then : + test "$ac_res" = "none required" || LIBS="$ac_res $LIBS" + +else + +$as_echo "#define NO_GSSAPI_LIB 1" >>confdefs.h + +fi + +fi + +fi + +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for XOpenDisplay in -lX11" >&5 +$as_echo_n "checking for XOpenDisplay in -lX11... " >&6; } +if ${ac_cv_lib_X11_XOpenDisplay+:} false; then : + $as_echo_n "(cached) " >&6 +else + ac_check_lib_save_LIBS=$LIBS +LIBS="-lX11 $LIBS" +cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ + +/* Override any GCC internal prototype to avoid an error. + Use char because int might match the return type of a GCC + builtin and then its argument prototype would still apply. */ +#ifdef __cplusplus +extern "C" +#endif +char XOpenDisplay (); +int +main () +{ +return XOpenDisplay (); + ; + return 0; +} +_ACEOF +if ac_fn_c_try_link "$LINENO"; then : + ac_cv_lib_X11_XOpenDisplay=yes +else + ac_cv_lib_X11_XOpenDisplay=no +fi +rm -f core conftest.err conftest.$ac_objext \ + conftest$ac_exeext conftest.$ac_ext +LIBS=$ac_check_lib_save_LIBS +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_X11_XOpenDisplay" >&5 +$as_echo "$ac_cv_lib_X11_XOpenDisplay" >&6; } +if test "x$ac_cv_lib_X11_XOpenDisplay" = xyes; then : + GTK_LIBS="-lX11 $GTK_LIBS" + +$as_echo "#define HAVE_LIBX11 /**/" >>confdefs.h + +fi + + +for ac_func in getaddrinfo posix_openpt ptsname setresuid strsignal updwtmpx fstatat dirfd futimes setpwent endpwent +do : + as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` +ac_fn_c_check_func "$LINENO" "$ac_func" "$as_ac_var" +if eval test \"x\$"$as_ac_var"\" = x"yes"; then : + cat >>confdefs.h <<_ACEOF +#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1 +_ACEOF + +fi +done + +ac_fn_c_check_decl "$LINENO" "CLOCK_MONOTONIC" "ac_cv_have_decl_CLOCK_MONOTONIC" "#include +" +if test "x$ac_cv_have_decl_CLOCK_MONOTONIC" = xyes; then : + ac_have_decl=1 +else + ac_have_decl=0 +fi + +cat >>confdefs.h <<_ACEOF +#define HAVE_DECL_CLOCK_MONOTONIC $ac_have_decl +_ACEOF + +for ac_header in sys/auxv.h asm/hwcap.h glob.h +do : + as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` +ac_fn_c_check_header_mongrel "$LINENO" "$ac_header" "$as_ac_Header" "$ac_includes_default" +if eval test \"x\$"$as_ac_Header"\" = x"yes"; then : + cat >>confdefs.h <<_ACEOF +#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1 +_ACEOF + +fi + +done + +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for library containing clock_gettime" >&5 +$as_echo_n "checking for library containing clock_gettime... " >&6; } +if ${ac_cv_search_clock_gettime+:} false; then : + $as_echo_n "(cached) " >&6 +else + ac_func_search_save_LIBS=$LIBS +cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ + +/* Override any GCC internal prototype to avoid an error. + Use char because int might match the return type of a GCC + builtin and then its argument prototype would still apply. */ +#ifdef __cplusplus +extern "C" +#endif +char clock_gettime (); +int +main () +{ +return clock_gettime (); + ; + return 0; +} +_ACEOF +for ac_lib in '' rt; do + if test -z "$ac_lib"; then + ac_res="none required" + else + ac_res=-l$ac_lib + LIBS="-l$ac_lib $ac_func_search_save_LIBS" + fi + if ac_fn_c_try_link "$LINENO"; then : + ac_cv_search_clock_gettime=$ac_res +fi +rm -f core conftest.err conftest.$ac_objext \ + conftest$ac_exeext + if ${ac_cv_search_clock_gettime+:} false; then : + break +fi +done +if ${ac_cv_search_clock_gettime+:} false; then : + +else + ac_cv_search_clock_gettime=no +fi +rm conftest.$ac_ext +LIBS=$ac_func_search_save_LIBS +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_search_clock_gettime" >&5 +$as_echo "$ac_cv_search_clock_gettime" >&6; } +ac_res=$ac_cv_search_clock_gettime +if test "$ac_res" != no; then : + test "$ac_res" = "none required" || LIBS="$ac_res $LIBS" + +$as_echo "#define HAVE_CLOCK_GETTIME /**/" >>confdefs.h + +fi + + +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for SO_PEERCRED and dependencies" >&5 +$as_echo_n "checking for SO_PEERCRED and dependencies... " >&6; } +if ${x_cv_linux_so_peercred+:} false; then : + $as_echo_n "(cached) " >&6 +else + + cat confdefs.h - <<_ACEOF >conftest.$ac_ext +/* end confdefs.h. */ + + + #define _GNU_SOURCE + #include + #include + +int +main () +{ + + struct ucred cr; + socklen_t crlen = sizeof(cr); + return getsockopt(0, SOL_SOCKET, SO_PEERCRED, &cr, &crlen) + + cr.pid + cr.uid + cr.gid; + + + ; + return 0; +} +_ACEOF +if ac_fn_c_try_compile "$LINENO"; then : + x_cv_linux_so_peercred=yes +else + x_cv_linux_so_peercred=no + +fi +rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext + +fi +{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $x_cv_linux_so_peercred" >&5 +$as_echo "$x_cv_linux_so_peercred" >&6; } +if test $x_cv_linux_so_peercred = yes; then : + +$as_echo "#define HAVE_SO_PEERCRED 1" >>confdefs.h + + +fi + +if test "x$GCC" = "xyes"; then + : + WARNINGOPTS='-Wall -Werror -Wpointer-arith -Wvla' + +else + : + +fi + +cat >confcache <<\_ACEOF +# This file is a shell script that caches the results of configure +# tests run on this system so they can be shared between configure +# scripts and configure runs, see configure's option --config-cache. +# It is not useful on other systems. If it contains results you don't +# want to keep, you may remove or edit it. +# +# config.status only pays attention to the cache file if you give it +# the --recheck option to rerun configure. +# +# `ac_cv_env_foo' variables (set or unset) will be overridden when +# loading this file, other *unset* `ac_cv_foo' will be assigned the +# following values. + +_ACEOF + +# The following way of writing the cache mishandles newlines in values, +# but we know of no workaround that is simple, portable, and efficient. +# So, we kill variables containing newlines. +# Ultrix sh set writes to stderr and can't be redirected directly, +# and sets the high bit in the cache file unless we assign to the vars. +( + for ac_var in `(set) 2>&1 | sed -n 's/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'`; do + eval ac_val=\$$ac_var + case $ac_val in #( + *${as_nl}*) + case $ac_var in #( + *_cv_*) { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: cache variable $ac_var contains a newline" >&5 +$as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;; + esac + case $ac_var in #( + _ | IFS | as_nl) ;; #( + BASH_ARGV | BASH_SOURCE) eval $ac_var= ;; #( + *) { eval $ac_var=; unset $ac_var;} ;; + esac ;; + esac + done + + (set) 2>&1 | + case $as_nl`(ac_space=' '; set) 2>&1` in #( + *${as_nl}ac_space=\ *) + # `set' does not quote correctly, so add quotes: double-quote + # substitution turns \\\\ into \\, and sed turns \\ into \. + sed -n \ + "s/'/'\\\\''/g; + s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='\\2'/p" + ;; #( + *) + # `set' quotes correctly as required by POSIX, so do not add quotes. + sed -n "/^[_$as_cr_alnum]*_cv_[_$as_cr_alnum]*=/p" + ;; + esac | + sort +) | + sed ' + /^ac_cv_env_/b end + t clear + :clear + s/^\([^=]*\)=\(.*[{}].*\)$/test "${\1+set}" = set || &/ + t end + s/^\([^=]*\)=\(.*\)$/\1=${\1=\2}/ + :end' >>confcache +if diff "$cache_file" confcache >/dev/null 2>&1; then :; else + if test -w "$cache_file"; then + if test "x$cache_file" != "x/dev/null"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: updating cache $cache_file" >&5 +$as_echo "$as_me: updating cache $cache_file" >&6;} + if test ! -f "$cache_file" || test -h "$cache_file"; then + cat confcache >"$cache_file" + else + case $cache_file in #( + */* | ?:*) + mv -f confcache "$cache_file"$$ && + mv -f "$cache_file"$$ "$cache_file" ;; #( + *) + mv -f confcache "$cache_file" ;; + esac + fi + fi + else + { $as_echo "$as_me:${as_lineno-$LINENO}: not updating unwritable cache $cache_file" >&5 +$as_echo "$as_me: not updating unwritable cache $cache_file" >&6;} + fi +fi +rm -f confcache + +test "x$prefix" = xNONE && prefix=$ac_default_prefix +# Let make expand exec_prefix. +test "x$exec_prefix" = xNONE && exec_prefix='${prefix}' + +DEFS=-DHAVE_CONFIG_H + +ac_libobjs= +ac_ltlibobjs= +U= +for ac_i in : $LIBOBJS; do test "x$ac_i" = x: && continue + # 1. Remove the extension, and $U if already installed. + ac_script='s/\$U\././;s/\.o$//;s/\.obj$//' + ac_i=`$as_echo "$ac_i" | sed "$ac_script"` + # 2. Prepend LIBOBJDIR. When used with automake>=1.10 LIBOBJDIR + # will be set to the directory where LIBOBJS objects are built. + as_fn_append ac_libobjs " \${LIBOBJDIR}$ac_i\$U.$ac_objext" + as_fn_append ac_ltlibobjs " \${LIBOBJDIR}$ac_i"'$U.lo' +done +LIBOBJS=$ac_libobjs + +LTLIBOBJS=$ac_ltlibobjs + + +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking that generated files are newer than configure" >&5 +$as_echo_n "checking that generated files are newer than configure... " >&6; } + if test -n "$am_sleep_pid"; then + # Hide warnings about reused PIDs. + wait $am_sleep_pid 2>/dev/null + fi + { $as_echo "$as_me:${as_lineno-$LINENO}: result: done" >&5 +$as_echo "done" >&6; } + if test -n "$EXEEXT"; then + am__EXEEXT_TRUE= + am__EXEEXT_FALSE='#' +else + am__EXEEXT_TRUE='#' + am__EXEEXT_FALSE= +fi + +if test -z "${AMDEP_TRUE}" && test -z "${AMDEP_FALSE}"; then + as_fn_error $? "conditional \"AMDEP\" was never defined. +Usually this means the macro was only invoked conditionally." "$LINENO" 5 +fi +if test -z "${am__fastdepCC_TRUE}" && test -z "${am__fastdepCC_FALSE}"; then + as_fn_error $? "conditional \"am__fastdepCC\" was never defined. +Usually this means the macro was only invoked conditionally." "$LINENO" 5 +fi +if test -z "${HAVE_SETID_CMD_TRUE}" && test -z "${HAVE_SETID_CMD_FALSE}"; then + as_fn_error $? "conditional \"HAVE_SETID_CMD\" was never defined. +Usually this means the macro was only invoked conditionally." "$LINENO" 5 +fi +if test -z "${AUTO_GIT_COMMIT_TRUE}" && test -z "${AUTO_GIT_COMMIT_FALSE}"; then + as_fn_error $? "conditional \"AUTO_GIT_COMMIT\" was never defined. +Usually this means the macro was only invoked conditionally." "$LINENO" 5 +fi +if test -z "${HAVE_QUARTZ_TRUE}" && test -z "${HAVE_QUARTZ_FALSE}"; then + as_fn_error $? "conditional \"HAVE_QUARTZ\" was never defined. +Usually this means the macro was only invoked conditionally." "$LINENO" 5 +fi +if test -z "${HAVE_GTK_TRUE}" && test -z "${HAVE_GTK_FALSE}"; then + as_fn_error $? "conditional \"HAVE_GTK\" was never defined. +Usually this means the macro was only invoked conditionally." "$LINENO" 5 +fi + +: "${CONFIG_STATUS=./config.status}" +ac_write_fail=0 +ac_clean_files_save=$ac_clean_files +ac_clean_files="$ac_clean_files $CONFIG_STATUS" +{ $as_echo "$as_me:${as_lineno-$LINENO}: creating $CONFIG_STATUS" >&5 +$as_echo "$as_me: creating $CONFIG_STATUS" >&6;} +as_write_fail=0 +cat >$CONFIG_STATUS <<_ASEOF || as_write_fail=1 +#! $SHELL +# Generated by $as_me. +# Run this file to recreate the current configuration. +# Compiler output produced by configure, useful for debugging +# configure, is in config.log if it exists. + +debug=false +ac_cs_recheck=false +ac_cs_silent=false + +SHELL=\${CONFIG_SHELL-$SHELL} +export SHELL +_ASEOF +cat >>$CONFIG_STATUS <<\_ASEOF || as_write_fail=1 +## -------------------- ## +## M4sh Initialization. ## +## -------------------- ## + +# Be more Bourne compatible +DUALCASE=1; export DUALCASE # for MKS sh +if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then : + emulate sh + NULLCMD=: + # Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which + # is contrary to our usage. Disable this feature. + alias -g '${1+"$@"}'='"$@"' + setopt NO_GLOB_SUBST +else + case `(set -o) 2>/dev/null` in #( + *posix*) : + set -o posix ;; #( + *) : + ;; +esac +fi + + +as_nl=' +' +export as_nl +# Printing a long string crashes Solaris 7 /usr/bin/printf. +as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\' +as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo +as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo +# Prefer a ksh shell builtin over an external printf program on Solaris, +# but without wasting forks for bash or zsh. +if test -z "$BASH_VERSION$ZSH_VERSION" \ + && (test "X`print -r -- $as_echo`" = "X$as_echo") 2>/dev/null; then + as_echo='print -r --' + as_echo_n='print -rn --' +elif (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then + as_echo='printf %s\n' + as_echo_n='printf %s' +else + if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then + as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"' + as_echo_n='/usr/ucb/echo -n' + else + as_echo_body='eval expr "X$1" : "X\\(.*\\)"' + as_echo_n_body='eval + arg=$1; + case $arg in #( + *"$as_nl"*) + expr "X$arg" : "X\\(.*\\)$as_nl"; + arg=`expr "X$arg" : ".*$as_nl\\(.*\\)"`;; + esac; + expr "X$arg" : "X\\(.*\\)" | tr -d "$as_nl" + ' + export as_echo_n_body + as_echo_n='sh -c $as_echo_n_body as_echo' + fi + export as_echo_body + as_echo='sh -c $as_echo_body as_echo' +fi + +# The user is always right. +if test "${PATH_SEPARATOR+set}" != set; then + PATH_SEPARATOR=: + (PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 && { + (PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 || + PATH_SEPARATOR=';' + } +fi + + +# IFS +# We need space, tab and new line, in precisely that order. Quoting is +# there to prevent editors from complaining about space-tab. +# (If _AS_PATH_WALK were called with IFS unset, it would disable word +# splitting by setting IFS to empty value.) +IFS=" "" $as_nl" + +# Find who we are. Look in the path if we contain no directory separator. +as_myself= +case $0 in #(( + *[\\/]* ) as_myself=$0 ;; + *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break + done +IFS=$as_save_IFS + + ;; +esac +# We did not find ourselves, most probably we were run as `sh COMMAND' +# in which case we are not to be found in the path. +if test "x$as_myself" = x; then + as_myself=$0 +fi +if test ! -f "$as_myself"; then + $as_echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2 + exit 1 +fi + +# Unset variables that we do not need and which cause bugs (e.g. in +# pre-3.0 UWIN ksh). But do not cause bugs in bash 2.01; the "|| exit 1" +# suppresses any "Segmentation fault" message there. '((' could +# trigger a bug in pdksh 5.2.14. +for as_var in BASH_ENV ENV MAIL MAILPATH +do eval test x\${$as_var+set} = xset \ + && ( (unset $as_var) || exit 1) >/dev/null 2>&1 && unset $as_var || : +done +PS1='$ ' +PS2='> ' +PS4='+ ' + +# NLS nuisances. +LC_ALL=C +export LC_ALL +LANGUAGE=C +export LANGUAGE + +# CDPATH. +(unset CDPATH) >/dev/null 2>&1 && unset CDPATH + + +# as_fn_error STATUS ERROR [LINENO LOG_FD] +# ---------------------------------------- +# Output "`basename $0`: error: ERROR" to stderr. If LINENO and LOG_FD are +# provided, also output the error to LOG_FD, referencing LINENO. Then exit the +# script with STATUS, using 1 if that was 0. +as_fn_error () +{ + as_status=$1; test $as_status -eq 0 && as_status=1 + if test "$4"; then + as_lineno=${as_lineno-"$3"} as_lineno_stack=as_lineno_stack=$as_lineno_stack + $as_echo "$as_me:${as_lineno-$LINENO}: error: $2" >&$4 + fi + $as_echo "$as_me: error: $2" >&2 + as_fn_exit $as_status +} # as_fn_error + + +# as_fn_set_status STATUS +# ----------------------- +# Set $? to STATUS, without forking. +as_fn_set_status () +{ + return $1 +} # as_fn_set_status + +# as_fn_exit STATUS +# ----------------- +# Exit the shell with STATUS, even in a "trap 0" or "set -e" context. +as_fn_exit () +{ + set +e + as_fn_set_status $1 + exit $1 +} # as_fn_exit + +# as_fn_unset VAR +# --------------- +# Portably unset VAR. +as_fn_unset () +{ + { eval $1=; unset $1;} +} +as_unset=as_fn_unset +# as_fn_append VAR VALUE +# ---------------------- +# Append the text in VALUE to the end of the definition contained in VAR. Take +# advantage of any shell optimizations that allow amortized linear growth over +# repeated appends, instead of the typical quadratic growth present in naive +# implementations. +if (eval "as_var=1; as_var+=2; test x\$as_var = x12") 2>/dev/null; then : + eval 'as_fn_append () + { + eval $1+=\$2 + }' +else + as_fn_append () + { + eval $1=\$$1\$2 + } +fi # as_fn_append + +# as_fn_arith ARG... +# ------------------ +# Perform arithmetic evaluation on the ARGs, and store the result in the +# global $as_val. Take advantage of shells that can avoid forks. The arguments +# must be portable across $(()) and expr. +if (eval "test \$(( 1 + 1 )) = 2") 2>/dev/null; then : + eval 'as_fn_arith () + { + as_val=$(( $* )) + }' +else + as_fn_arith () + { + as_val=`expr "$@" || test $? -eq 1` + } +fi # as_fn_arith + + +if expr a : '\(a\)' >/dev/null 2>&1 && + test "X`expr 00001 : '.*\(...\)'`" = X001; then + as_expr=expr +else + as_expr=false +fi + +if (basename -- /) >/dev/null 2>&1 && test "X`basename -- / 2>&1`" = "X/"; then + as_basename=basename +else + as_basename=false +fi + +if (as_dir=`dirname -- /` && test "X$as_dir" = X/) >/dev/null 2>&1; then + as_dirname=dirname +else + as_dirname=false +fi + +as_me=`$as_basename -- "$0" || +$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \ + X"$0" : 'X\(//\)$' \| \ + X"$0" : 'X\(/\)' \| . 2>/dev/null || +$as_echo X/"$0" | + sed '/^.*\/\([^/][^/]*\)\/*$/{ + s//\1/ + q + } + /^X\/\(\/\/\)$/{ + s//\1/ + q + } + /^X\/\(\/\).*/{ + s//\1/ + q + } + s/.*/./; q'` + +# Avoid depending upon Character Ranges. +as_cr_letters='abcdefghijklmnopqrstuvwxyz' +as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ' +as_cr_Letters=$as_cr_letters$as_cr_LETTERS +as_cr_digits='0123456789' +as_cr_alnum=$as_cr_Letters$as_cr_digits + +ECHO_C= ECHO_N= ECHO_T= +case `echo -n x` in #((((( +-n*) + case `echo 'xy\c'` in + *c*) ECHO_T=' ';; # ECHO_T is single tab character. + xy) ECHO_C='\c';; + *) echo `echo ksh88 bug on AIX 6.1` > /dev/null + ECHO_T=' ';; + esac;; +*) + ECHO_N='-n';; +esac + +rm -f conf$$ conf$$.exe conf$$.file +if test -d conf$$.dir; then + rm -f conf$$.dir/conf$$.file +else + rm -f conf$$.dir + mkdir conf$$.dir 2>/dev/null +fi +if (echo >conf$$.file) 2>/dev/null; then + if ln -s conf$$.file conf$$ 2>/dev/null; then + as_ln_s='ln -s' + # ... but there are two gotchas: + # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail. + # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable. + # In both cases, we have to default to `cp -pR'. + ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe || + as_ln_s='cp -pR' + elif ln conf$$.file conf$$ 2>/dev/null; then + as_ln_s=ln + else + as_ln_s='cp -pR' + fi +else + as_ln_s='cp -pR' +fi +rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file +rmdir conf$$.dir 2>/dev/null + + +# as_fn_mkdir_p +# ------------- +# Create "$as_dir" as a directory, including parents if necessary. +as_fn_mkdir_p () +{ + + case $as_dir in #( + -*) as_dir=./$as_dir;; + esac + test -d "$as_dir" || eval $as_mkdir_p || { + as_dirs= + while :; do + case $as_dir in #( + *\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'( + *) as_qdir=$as_dir;; + esac + as_dirs="'$as_qdir' $as_dirs" + as_dir=`$as_dirname -- "$as_dir" || +$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ + X"$as_dir" : 'X\(//\)[^/]' \| \ + X"$as_dir" : 'X\(//\)$' \| \ + X"$as_dir" : 'X\(/\)' \| . 2>/dev/null || +$as_echo X"$as_dir" | + sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ + s//\1/ + q + } + /^X\(\/\/\)[^/].*/{ + s//\1/ + q + } + /^X\(\/\/\)$/{ + s//\1/ + q + } + /^X\(\/\).*/{ + s//\1/ + q + } + s/.*/./; q'` + test -d "$as_dir" && break + done + test -z "$as_dirs" || eval "mkdir $as_dirs" + } || test -d "$as_dir" || as_fn_error $? "cannot create directory $as_dir" + + +} # as_fn_mkdir_p +if mkdir -p . 2>/dev/null; then + as_mkdir_p='mkdir -p "$as_dir"' +else + test -d ./-p && rmdir ./-p + as_mkdir_p=false +fi + + +# as_fn_executable_p FILE +# ----------------------- +# Test if FILE is an executable regular file. +as_fn_executable_p () +{ + test -f "$1" && test -x "$1" +} # as_fn_executable_p +as_test_x='test -x' +as_executable_p=as_fn_executable_p + +# Sed expression to map a string onto a valid CPP name. +as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'" + +# Sed expression to map a string onto a valid variable name. +as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'" + + +exec 6>&1 +## ----------------------------------- ## +## Main body of $CONFIG_STATUS script. ## +## ----------------------------------- ## +_ASEOF +test $as_write_fail = 0 && chmod +x $CONFIG_STATUS || ac_write_fail=1 + +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 +# Save the log message, to keep $0 and so on meaningful, and to +# report actual input values of CONFIG_FILES etc. instead of their +# values after options handling. +ac_log=" +This file was extended by putty $as_me 0.72, which was +generated by GNU Autoconf 2.69. Invocation command line was + + CONFIG_FILES = $CONFIG_FILES + CONFIG_HEADERS = $CONFIG_HEADERS + CONFIG_LINKS = $CONFIG_LINKS + CONFIG_COMMANDS = $CONFIG_COMMANDS + $ $0 $@ + +on `(hostname || uname -n) 2>/dev/null | sed 1q` +" + +_ACEOF + +case $ac_config_files in *" +"*) set x $ac_config_files; shift; ac_config_files=$*;; +esac + +case $ac_config_headers in *" +"*) set x $ac_config_headers; shift; ac_config_headers=$*;; +esac + + +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 +# Files that config.status was made for. +config_files="$ac_config_files" +config_headers="$ac_config_headers" +config_commands="$ac_config_commands" + +_ACEOF + +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 +ac_cs_usage="\ +\`$as_me' instantiates files and other configuration actions +from templates according to the current configuration. Unless the files +and actions are specified as TAGs, all are instantiated by default. + +Usage: $0 [OPTION]... [TAG]... + + -h, --help print this help, then exit + -V, --version print version number and configuration settings, then exit + --config print configuration, then exit + -q, --quiet, --silent + do not print progress messages + -d, --debug don't remove temporary files + --recheck update $as_me by reconfiguring in the same conditions + --file=FILE[:TEMPLATE] + instantiate the configuration file FILE + --header=FILE[:TEMPLATE] + instantiate the configuration header FILE + +Configuration files: +$config_files + +Configuration headers: +$config_headers + +Configuration commands: +$config_commands + +Report bugs to the package provider." + +_ACEOF +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 +ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`" +ac_cs_version="\\ +putty config.status 0.72 +configured by $0, generated by GNU Autoconf 2.69, + with options \\"\$ac_cs_config\\" + +Copyright (C) 2012 Free Software Foundation, Inc. +This config.status script is free software; the Free Software Foundation +gives unlimited permission to copy, distribute and modify it." + +ac_pwd='$ac_pwd' +srcdir='$srcdir' +INSTALL='$INSTALL' +MKDIR_P='$MKDIR_P' +AWK='$AWK' +test -n "\$AWK" || AWK=awk +_ACEOF + +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 +# The default lists apply if the user does not specify any file. +ac_need_defaults=: +while test $# != 0 +do + case $1 in + --*=?*) + ac_option=`expr "X$1" : 'X\([^=]*\)='` + ac_optarg=`expr "X$1" : 'X[^=]*=\(.*\)'` + ac_shift=: + ;; + --*=) + ac_option=`expr "X$1" : 'X\([^=]*\)='` + ac_optarg= + ac_shift=: + ;; + *) + ac_option=$1 + ac_optarg=$2 + ac_shift=shift + ;; + esac + + case $ac_option in + # Handling of the options. + -recheck | --recheck | --rechec | --reche | --rech | --rec | --re | --r) + ac_cs_recheck=: ;; + --version | --versio | --versi | --vers | --ver | --ve | --v | -V ) + $as_echo "$ac_cs_version"; exit ;; + --config | --confi | --conf | --con | --co | --c ) + $as_echo "$ac_cs_config"; exit ;; + --debug | --debu | --deb | --de | --d | -d ) + debug=: ;; + --file | --fil | --fi | --f ) + $ac_shift + case $ac_optarg in + *\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;; + '') as_fn_error $? "missing file argument" ;; + esac + as_fn_append CONFIG_FILES " '$ac_optarg'" + ac_need_defaults=false;; + --header | --heade | --head | --hea ) + $ac_shift + case $ac_optarg in + *\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;; + esac + as_fn_append CONFIG_HEADERS " '$ac_optarg'" + ac_need_defaults=false;; + --he | --h) + # Conflict between --help and --header + as_fn_error $? "ambiguous option: \`$1' +Try \`$0 --help' for more information.";; + --help | --hel | -h ) + $as_echo "$ac_cs_usage"; exit ;; + -q | -quiet | --quiet | --quie | --qui | --qu | --q \ + | -silent | --silent | --silen | --sile | --sil | --si | --s) + ac_cs_silent=: ;; + + # This is an error. + -*) as_fn_error $? "unrecognized option: \`$1' +Try \`$0 --help' for more information." ;; + + *) as_fn_append ac_config_targets " $1" + ac_need_defaults=false ;; + + esac + shift +done + +ac_configure_extra_args= + +if $ac_cs_silent; then + exec 6>/dev/null + ac_configure_extra_args="$ac_configure_extra_args --silent" +fi + +_ACEOF +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 +if \$ac_cs_recheck; then + set X $SHELL '$0' $ac_configure_args \$ac_configure_extra_args --no-create --no-recursion + shift + \$as_echo "running CONFIG_SHELL=$SHELL \$*" >&6 + CONFIG_SHELL='$SHELL' + export CONFIG_SHELL + exec "\$@" +fi + +_ACEOF +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 +exec 5>>config.log +{ + echo + sed 'h;s/./-/g;s/^.../## /;s/...$/ ##/;p;x;p;x' <<_ASBOX +## Running $as_me. ## +_ASBOX + $as_echo "$ac_log" +} >&5 + +_ACEOF +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 +# +# INIT-COMMANDS +# +AMDEP_TRUE="$AMDEP_TRUE" ac_aux_dir="$ac_aux_dir" + +_ACEOF + +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 + +# Handling of arguments. +for ac_config_target in $ac_config_targets +do + case $ac_config_target in + "Makefile") CONFIG_FILES="$CONFIG_FILES Makefile" ;; + "uxconfig.h") CONFIG_HEADERS="$CONFIG_HEADERS uxconfig.h:uxconfig.in" ;; + "depfiles") CONFIG_COMMANDS="$CONFIG_COMMANDS depfiles" ;; + + *) as_fn_error $? "invalid argument: \`$ac_config_target'" "$LINENO" 5;; + esac +done + + +# If the user did not use the arguments to specify the items to instantiate, +# then the envvar interface is used. Set only those that are not. +# We use the long form for the default assignment because of an extremely +# bizarre bug on SunOS 4.1.3. +if $ac_need_defaults; then + test "${CONFIG_FILES+set}" = set || CONFIG_FILES=$config_files + test "${CONFIG_HEADERS+set}" = set || CONFIG_HEADERS=$config_headers + test "${CONFIG_COMMANDS+set}" = set || CONFIG_COMMANDS=$config_commands +fi + +# Have a temporary directory for convenience. Make it in the build tree +# simply because there is no reason against having it here, and in addition, +# creating and moving files from /tmp can sometimes cause problems. +# Hook for its removal unless debugging. +# Note that there is a small window in which the directory will not be cleaned: +# after its creation but before its name has been assigned to `$tmp'. +$debug || +{ + tmp= ac_tmp= + trap 'exit_status=$? + : "${ac_tmp:=$tmp}" + { test ! -d "$ac_tmp" || rm -fr "$ac_tmp"; } && exit $exit_status +' 0 + trap 'as_fn_exit 1' 1 2 13 15 +} +# Create a (secure) tmp directory for tmp files. + +{ + tmp=`(umask 077 && mktemp -d "./confXXXXXX") 2>/dev/null` && + test -d "$tmp" +} || +{ + tmp=./conf$$-$RANDOM + (umask 077 && mkdir "$tmp") +} || as_fn_error $? "cannot create a temporary directory in ." "$LINENO" 5 +ac_tmp=$tmp + +# Set up the scripts for CONFIG_FILES section. +# No need to generate them if there are no CONFIG_FILES. +# This happens for instance with `./config.status config.h'. +if test -n "$CONFIG_FILES"; then + + +ac_cr=`echo X | tr X '\015'` +# On cygwin, bash can eat \r inside `` if the user requested igncr. +# But we know of no other shell where ac_cr would be empty at this +# point, so we can use a bashism as a fallback. +if test "x$ac_cr" = x; then + eval ac_cr=\$\'\\r\' +fi +ac_cs_awk_cr=`$AWK 'BEGIN { print "a\rb" }' /dev/null` +if test "$ac_cs_awk_cr" = "a${ac_cr}b"; then + ac_cs_awk_cr='\\r' +else + ac_cs_awk_cr=$ac_cr +fi + +echo 'BEGIN {' >"$ac_tmp/subs1.awk" && +_ACEOF + + +{ + echo "cat >conf$$subs.awk <<_ACEOF" && + echo "$ac_subst_vars" | sed 's/.*/&!$&$ac_delim/' && + echo "_ACEOF" +} >conf$$subs.sh || + as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5 +ac_delim_num=`echo "$ac_subst_vars" | grep -c '^'` +ac_delim='%!_!# ' +for ac_last_try in false false false false false :; do + . ./conf$$subs.sh || + as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5 + + ac_delim_n=`sed -n "s/.*$ac_delim\$/X/p" conf$$subs.awk | grep -c X` + if test $ac_delim_n = $ac_delim_num; then + break + elif $ac_last_try; then + as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5 + else + ac_delim="$ac_delim!$ac_delim _$ac_delim!! " + fi +done +rm -f conf$$subs.sh + +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 +cat >>"\$ac_tmp/subs1.awk" <<\\_ACAWK && +_ACEOF +sed -n ' +h +s/^/S["/; s/!.*/"]=/ +p +g +s/^[^!]*!// +:repl +t repl +s/'"$ac_delim"'$// +t delim +:nl +h +s/\(.\{148\}\)..*/\1/ +t more1 +s/["\\]/\\&/g; s/^/"/; s/$/\\n"\\/ +p +n +b repl +:more1 +s/["\\]/\\&/g; s/^/"/; s/$/"\\/ +p +g +s/.\{148\}// +t nl +:delim +h +s/\(.\{148\}\)..*/\1/ +t more2 +s/["\\]/\\&/g; s/^/"/; s/$/"/ +p +b +:more2 +s/["\\]/\\&/g; s/^/"/; s/$/"\\/ +p +g +s/.\{148\}// +t delim +' >$CONFIG_STATUS || ac_write_fail=1 +rm -f conf$$subs.awk +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 +_ACAWK +cat >>"\$ac_tmp/subs1.awk" <<_ACAWK && + for (key in S) S_is_set[key] = 1 + FS = "" + +} +{ + line = $ 0 + nfields = split(line, field, "@") + substed = 0 + len = length(field[1]) + for (i = 2; i < nfields; i++) { + key = field[i] + keylen = length(key) + if (S_is_set[key]) { + value = S[key] + line = substr(line, 1, len) "" value "" substr(line, len + keylen + 3) + len += length(value) + length(field[++i]) + substed = 1 + } else + len += 1 + keylen + } + + print line +} + +_ACAWK +_ACEOF +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 +if sed "s/$ac_cr//" < /dev/null > /dev/null 2>&1; then + sed "s/$ac_cr\$//; s/$ac_cr/$ac_cs_awk_cr/g" +else + cat +fi < "$ac_tmp/subs1.awk" > "$ac_tmp/subs.awk" \ + || as_fn_error $? "could not setup config files machinery" "$LINENO" 5 +_ACEOF + +# VPATH may cause trouble with some makes, so we remove sole $(srcdir), +# ${srcdir} and @srcdir@ entries from VPATH if srcdir is ".", strip leading and +# trailing colons and then remove the whole line if VPATH becomes empty +# (actually we leave an empty line to preserve line numbers). +if test "x$srcdir" = x.; then + ac_vpsub='/^[ ]*VPATH[ ]*=[ ]*/{ +h +s/// +s/^/:/ +s/[ ]*$/:/ +s/:\$(srcdir):/:/g +s/:\${srcdir}:/:/g +s/:@srcdir@:/:/g +s/^:*// +s/:*$// +x +s/\(=[ ]*\).*/\1/ +G +s/\n// +s/^[^=]*=[ ]*$// +}' +fi + +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 +fi # test -n "$CONFIG_FILES" + +# Set up the scripts for CONFIG_HEADERS section. +# No need to generate them if there are no CONFIG_HEADERS. +# This happens for instance with `./config.status Makefile'. +if test -n "$CONFIG_HEADERS"; then +cat >"$ac_tmp/defines.awk" <<\_ACAWK || +BEGIN { +_ACEOF + +# Transform confdefs.h into an awk script `defines.awk', embedded as +# here-document in config.status, that substitutes the proper values into +# config.h.in to produce config.h. + +# Create a delimiter string that does not exist in confdefs.h, to ease +# handling of long lines. +ac_delim='%!_!# ' +for ac_last_try in false false :; do + ac_tt=`sed -n "/$ac_delim/p" confdefs.h` + if test -z "$ac_tt"; then + break + elif $ac_last_try; then + as_fn_error $? "could not make $CONFIG_HEADERS" "$LINENO" 5 + else + ac_delim="$ac_delim!$ac_delim _$ac_delim!! " + fi +done + +# For the awk script, D is an array of macro values keyed by name, +# likewise P contains macro parameters if any. Preserve backslash +# newline sequences. + +ac_word_re=[_$as_cr_Letters][_$as_cr_alnum]* +sed -n ' +s/.\{148\}/&'"$ac_delim"'/g +t rset +:rset +s/^[ ]*#[ ]*define[ ][ ]*/ / +t def +d +:def +s/\\$// +t bsnl +s/["\\]/\\&/g +s/^ \('"$ac_word_re"'\)\(([^()]*)\)[ ]*\(.*\)/P["\1"]="\2"\ +D["\1"]=" \3"/p +s/^ \('"$ac_word_re"'\)[ ]*\(.*\)/D["\1"]=" \2"/p +d +:bsnl +s/["\\]/\\&/g +s/^ \('"$ac_word_re"'\)\(([^()]*)\)[ ]*\(.*\)/P["\1"]="\2"\ +D["\1"]=" \3\\\\\\n"\\/p +t cont +s/^ \('"$ac_word_re"'\)[ ]*\(.*\)/D["\1"]=" \2\\\\\\n"\\/p +t cont +d +:cont +n +s/.\{148\}/&'"$ac_delim"'/g +t clear +:clear +s/\\$// +t bsnlc +s/["\\]/\\&/g; s/^/"/; s/$/"/p +d +:bsnlc +s/["\\]/\\&/g; s/^/"/; s/$/\\\\\\n"\\/p +b cont +' >$CONFIG_STATUS || ac_write_fail=1 + +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 + for (key in D) D_is_set[key] = 1 + FS = "" +} +/^[\t ]*#[\t ]*(define|undef)[\t ]+$ac_word_re([\t (]|\$)/ { + line = \$ 0 + split(line, arg, " ") + if (arg[1] == "#") { + defundef = arg[2] + mac1 = arg[3] + } else { + defundef = substr(arg[1], 2) + mac1 = arg[2] + } + split(mac1, mac2, "(") #) + macro = mac2[1] + prefix = substr(line, 1, index(line, defundef) - 1) + if (D_is_set[macro]) { + # Preserve the white space surrounding the "#". + print prefix "define", macro P[macro] D[macro] + next + } else { + # Replace #undef with comments. This is necessary, for example, + # in the case of _POSIX_SOURCE, which is predefined and required + # on some systems where configure will not decide to define it. + if (defundef == "undef") { + print "/*", prefix defundef, macro, "*/" + next + } + } +} +{ print } +_ACAWK +_ACEOF +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 + as_fn_error $? "could not setup config headers machinery" "$LINENO" 5 +fi # test -n "$CONFIG_HEADERS" + + +eval set X " :F $CONFIG_FILES :H $CONFIG_HEADERS :C $CONFIG_COMMANDS" +shift +for ac_tag +do + case $ac_tag in + :[FHLC]) ac_mode=$ac_tag; continue;; + esac + case $ac_mode$ac_tag in + :[FHL]*:*);; + :L* | :C*:*) as_fn_error $? "invalid tag \`$ac_tag'" "$LINENO" 5;; + :[FH]-) ac_tag=-:-;; + :[FH]*) ac_tag=$ac_tag:$ac_tag.in;; + esac + ac_save_IFS=$IFS + IFS=: + set x $ac_tag + IFS=$ac_save_IFS + shift + ac_file=$1 + shift + + case $ac_mode in + :L) ac_source=$1;; + :[FH]) + ac_file_inputs= + for ac_f + do + case $ac_f in + -) ac_f="$ac_tmp/stdin";; + *) # Look for the file first in the build tree, then in the source tree + # (if the path is not absolute). The absolute path cannot be DOS-style, + # because $ac_f cannot contain `:'. + test -f "$ac_f" || + case $ac_f in + [\\/$]*) false;; + *) test -f "$srcdir/$ac_f" && ac_f="$srcdir/$ac_f";; + esac || + as_fn_error 1 "cannot find input file: \`$ac_f'" "$LINENO" 5;; + esac + case $ac_f in *\'*) ac_f=`$as_echo "$ac_f" | sed "s/'/'\\\\\\\\''/g"`;; esac + as_fn_append ac_file_inputs " '$ac_f'" + done + + # Let's still pretend it is `configure' which instantiates (i.e., don't + # use $as_me), people would be surprised to read: + # /* config.h. Generated by config.status. */ + configure_input='Generated from '` + $as_echo "$*" | sed 's|^[^:]*/||;s|:[^:]*/|, |g' + `' by configure.' + if test x"$ac_file" != x-; then + configure_input="$ac_file. $configure_input" + { $as_echo "$as_me:${as_lineno-$LINENO}: creating $ac_file" >&5 +$as_echo "$as_me: creating $ac_file" >&6;} + fi + # Neutralize special characters interpreted by sed in replacement strings. + case $configure_input in #( + *\&* | *\|* | *\\* ) + ac_sed_conf_input=`$as_echo "$configure_input" | + sed 's/[\\\\&|]/\\\\&/g'`;; #( + *) ac_sed_conf_input=$configure_input;; + esac + + case $ac_tag in + *:-:* | *:-) cat >"$ac_tmp/stdin" \ + || as_fn_error $? "could not create $ac_file" "$LINENO" 5 ;; + esac + ;; + esac + + ac_dir=`$as_dirname -- "$ac_file" || +$as_expr X"$ac_file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ + X"$ac_file" : 'X\(//\)[^/]' \| \ + X"$ac_file" : 'X\(//\)$' \| \ + X"$ac_file" : 'X\(/\)' \| . 2>/dev/null || +$as_echo X"$ac_file" | + sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ + s//\1/ + q + } + /^X\(\/\/\)[^/].*/{ + s//\1/ + q + } + /^X\(\/\/\)$/{ + s//\1/ + q + } + /^X\(\/\).*/{ + s//\1/ + q + } + s/.*/./; q'` + as_dir="$ac_dir"; as_fn_mkdir_p + ac_builddir=. + +case "$ac_dir" in +.) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;; +*) + ac_dir_suffix=/`$as_echo "$ac_dir" | sed 's|^\.[\\/]||'` + # A ".." for each directory in $ac_dir_suffix. + ac_top_builddir_sub=`$as_echo "$ac_dir_suffix" | sed 's|/[^\\/]*|/..|g;s|/||'` + case $ac_top_builddir_sub in + "") ac_top_builddir_sub=. ac_top_build_prefix= ;; + *) ac_top_build_prefix=$ac_top_builddir_sub/ ;; + esac ;; +esac +ac_abs_top_builddir=$ac_pwd +ac_abs_builddir=$ac_pwd$ac_dir_suffix +# for backward compatibility: +ac_top_builddir=$ac_top_build_prefix + +case $srcdir in + .) # We are building in place. + ac_srcdir=. + ac_top_srcdir=$ac_top_builddir_sub + ac_abs_top_srcdir=$ac_pwd ;; + [\\/]* | ?:[\\/]* ) # Absolute name. + ac_srcdir=$srcdir$ac_dir_suffix; + ac_top_srcdir=$srcdir + ac_abs_top_srcdir=$srcdir ;; + *) # Relative name. + ac_srcdir=$ac_top_build_prefix$srcdir$ac_dir_suffix + ac_top_srcdir=$ac_top_build_prefix$srcdir + ac_abs_top_srcdir=$ac_pwd/$srcdir ;; +esac +ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix + + + case $ac_mode in + :F) + # + # CONFIG_FILE + # + + case $INSTALL in + [\\/$]* | ?:[\\/]* ) ac_INSTALL=$INSTALL ;; + *) ac_INSTALL=$ac_top_build_prefix$INSTALL ;; + esac + ac_MKDIR_P=$MKDIR_P + case $MKDIR_P in + [\\/$]* | ?:[\\/]* ) ;; + */*) ac_MKDIR_P=$ac_top_build_prefix$MKDIR_P ;; + esac +_ACEOF + +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 +# If the template does not know about datarootdir, expand it. +# FIXME: This hack should be removed a few years after 2.60. +ac_datarootdir_hack=; ac_datarootdir_seen= +ac_sed_dataroot=' +/datarootdir/ { + p + q +} +/@datadir@/p +/@docdir@/p +/@infodir@/p +/@localedir@/p +/@mandir@/p' +case `eval "sed -n \"\$ac_sed_dataroot\" $ac_file_inputs"` in +*datarootdir*) ac_datarootdir_seen=yes;; +*@datadir@*|*@docdir@*|*@infodir@*|*@localedir@*|*@mandir@*) + { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&5 +$as_echo "$as_me: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&2;} +_ACEOF +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 + ac_datarootdir_hack=' + s&@datadir@&$datadir&g + s&@docdir@&$docdir&g + s&@infodir@&$infodir&g + s&@localedir@&$localedir&g + s&@mandir@&$mandir&g + s&\\\${datarootdir}&$datarootdir&g' ;; +esac +_ACEOF + +# Neutralize VPATH when `$srcdir' = `.'. +# Shell code in configure.ac might set extrasub. +# FIXME: do we really want to maintain this feature? +cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 +ac_sed_extra="$ac_vpsub +$extrasub +_ACEOF +cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 +:t +/@[a-zA-Z_][a-zA-Z_0-9]*@/!b +s|@configure_input@|$ac_sed_conf_input|;t t +s&@top_builddir@&$ac_top_builddir_sub&;t t +s&@top_build_prefix@&$ac_top_build_prefix&;t t +s&@srcdir@&$ac_srcdir&;t t +s&@abs_srcdir@&$ac_abs_srcdir&;t t +s&@top_srcdir@&$ac_top_srcdir&;t t +s&@abs_top_srcdir@&$ac_abs_top_srcdir&;t t +s&@builddir@&$ac_builddir&;t t +s&@abs_builddir@&$ac_abs_builddir&;t t +s&@abs_top_builddir@&$ac_abs_top_builddir&;t t +s&@INSTALL@&$ac_INSTALL&;t t +s&@MKDIR_P@&$ac_MKDIR_P&;t t +$ac_datarootdir_hack +" +eval sed \"\$ac_sed_extra\" "$ac_file_inputs" | $AWK -f "$ac_tmp/subs.awk" \ + >$ac_tmp/out || as_fn_error $? "could not create $ac_file" "$LINENO" 5 + +test -z "$ac_datarootdir_hack$ac_datarootdir_seen" && + { ac_out=`sed -n '/\${datarootdir}/p' "$ac_tmp/out"`; test -n "$ac_out"; } && + { ac_out=`sed -n '/^[ ]*datarootdir[ ]*:*=/p' \ + "$ac_tmp/out"`; test -z "$ac_out"; } && + { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $ac_file contains a reference to the variable \`datarootdir' +which seems to be undefined. Please make sure it is defined" >&5 +$as_echo "$as_me: WARNING: $ac_file contains a reference to the variable \`datarootdir' +which seems to be undefined. Please make sure it is defined" >&2;} + + rm -f "$ac_tmp/stdin" + case $ac_file in + -) cat "$ac_tmp/out" && rm -f "$ac_tmp/out";; + *) rm -f "$ac_file" && mv "$ac_tmp/out" "$ac_file";; + esac \ + || as_fn_error $? "could not create $ac_file" "$LINENO" 5 + ;; + :H) + # + # CONFIG_HEADER + # + if test x"$ac_file" != x-; then + { + $as_echo "/* $configure_input */" \ + && eval '$AWK -f "$ac_tmp/defines.awk"' "$ac_file_inputs" + } >"$ac_tmp/config.h" \ + || as_fn_error $? "could not create $ac_file" "$LINENO" 5 + if diff "$ac_file" "$ac_tmp/config.h" >/dev/null 2>&1; then + { $as_echo "$as_me:${as_lineno-$LINENO}: $ac_file is unchanged" >&5 +$as_echo "$as_me: $ac_file is unchanged" >&6;} + else + rm -f "$ac_file" + mv "$ac_tmp/config.h" "$ac_file" \ + || as_fn_error $? "could not create $ac_file" "$LINENO" 5 + fi + else + $as_echo "/* $configure_input */" \ + && eval '$AWK -f "$ac_tmp/defines.awk"' "$ac_file_inputs" \ + || as_fn_error $? "could not create -" "$LINENO" 5 + fi +# Compute "$ac_file"'s index in $config_headers. +_am_arg="$ac_file" +_am_stamp_count=1 +for _am_header in $config_headers :; do + case $_am_header in + $_am_arg | $_am_arg:* ) + break ;; + * ) + _am_stamp_count=`expr $_am_stamp_count + 1` ;; + esac +done +echo "timestamp for $_am_arg" >`$as_dirname -- "$_am_arg" || +$as_expr X"$_am_arg" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ + X"$_am_arg" : 'X\(//\)[^/]' \| \ + X"$_am_arg" : 'X\(//\)$' \| \ + X"$_am_arg" : 'X\(/\)' \| . 2>/dev/null || +$as_echo X"$_am_arg" | + sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ + s//\1/ + q + } + /^X\(\/\/\)[^/].*/{ + s//\1/ + q + } + /^X\(\/\/\)$/{ + s//\1/ + q + } + /^X\(\/\).*/{ + s//\1/ + q + } + s/.*/./; q'`/stamp-h$_am_stamp_count + ;; + + :C) { $as_echo "$as_me:${as_lineno-$LINENO}: executing $ac_file commands" >&5 +$as_echo "$as_me: executing $ac_file commands" >&6;} + ;; + esac + + + case $ac_file$ac_mode in + "depfiles":C) test x"$AMDEP_TRUE" != x"" || { + # Older Autoconf quotes --file arguments for eval, but not when files + # are listed without --file. Let's play safe and only enable the eval + # if we detect the quoting. + case $CONFIG_FILES in + *\'*) eval set x "$CONFIG_FILES" ;; + *) set x $CONFIG_FILES ;; + esac + shift + for mf + do + # Strip MF so we end up with the name of the file. + mf=`echo "$mf" | sed -e 's/:.*$//'` + # Check whether this is an Automake generated Makefile or not. + # We used to match only the files named 'Makefile.in', but + # some people rename them; so instead we look at the file content. + # Grep'ing the first line is not enough: some people post-process + # each Makefile.in and add a new line on top of each file to say so. + # Grep'ing the whole file is not good either: AIX grep has a line + # limit of 2048, but all sed's we know have understand at least 4000. + if sed -n 's,^#.*generated by automake.*,X,p' "$mf" | grep X >/dev/null 2>&1; then + dirpart=`$as_dirname -- "$mf" || +$as_expr X"$mf" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ + X"$mf" : 'X\(//\)[^/]' \| \ + X"$mf" : 'X\(//\)$' \| \ + X"$mf" : 'X\(/\)' \| . 2>/dev/null || +$as_echo X"$mf" | + sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ + s//\1/ + q + } + /^X\(\/\/\)[^/].*/{ + s//\1/ + q + } + /^X\(\/\/\)$/{ + s//\1/ + q + } + /^X\(\/\).*/{ + s//\1/ + q + } + s/.*/./; q'` + else + continue + fi + # Extract the definition of DEPDIR, am__include, and am__quote + # from the Makefile without running 'make'. + DEPDIR=`sed -n 's/^DEPDIR = //p' < "$mf"` + test -z "$DEPDIR" && continue + am__include=`sed -n 's/^am__include = //p' < "$mf"` + test -z "$am__include" && continue + am__quote=`sed -n 's/^am__quote = //p' < "$mf"` + # Find all dependency output files, they are included files with + # $(DEPDIR) in their names. We invoke sed twice because it is the + # simplest approach to changing $(DEPDIR) to its actual value in the + # expansion. + for file in `sed -n " + s/^$am__include $am__quote\(.*(DEPDIR).*\)$am__quote"'$/\1/p' <"$mf" | \ + sed -e 's/\$(DEPDIR)/'"$DEPDIR"'/g'`; do + # Make sure the directory exists. + test -f "$dirpart/$file" && continue + fdir=`$as_dirname -- "$file" || +$as_expr X"$file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ + X"$file" : 'X\(//\)[^/]' \| \ + X"$file" : 'X\(//\)$' \| \ + X"$file" : 'X\(/\)' \| . 2>/dev/null || +$as_echo X"$file" | + sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ + s//\1/ + q + } + /^X\(\/\/\)[^/].*/{ + s//\1/ + q + } + /^X\(\/\/\)$/{ + s//\1/ + q + } + /^X\(\/\).*/{ + s//\1/ + q + } + s/.*/./; q'` + as_dir=$dirpart/$fdir; as_fn_mkdir_p + # echo "creating $dirpart/$file" + echo '# dummy' > "$dirpart/$file" + done + done +} + ;; + + esac +done # for ac_tag + + +as_fn_exit 0 +_ACEOF +ac_clean_files=$ac_clean_files_save + +test $ac_write_fail = 0 || + as_fn_error $? "write failure creating $CONFIG_STATUS" "$LINENO" 5 + + +# configure is writing to config.log, and then calls config.status. +# config.status does its own redirection, appending to config.log. +# Unfortunately, on DOS this fails, as config.log is still kept open +# by configure, so config.status won't be able to write to it; its +# output is simply discarded. So we exec the FD to /dev/null, +# effectively closing config.log, so it can be properly (re)opened and +# appended to by config.status. When coming back to configure, we +# need to make the FD available again. +if test "$no_create" != yes; then + ac_cs_success=: + ac_config_status_args= + test "$silent" = yes && + ac_config_status_args="$ac_config_status_args --quiet" + exec 5>/dev/null + $SHELL $CONFIG_STATUS $ac_config_status_args || ac_cs_success=false + exec 5>>config.log + # Use ||, not &&, to avoid exiting from the if with $? = 1, which + # would make configure fail if this is the last instruction. + $ac_cs_success || as_fn_exit 1 +fi +if test -n "$ac_unrecognized_opts" && test "$enable_option_checking" != no; then + { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: unrecognized options: $ac_unrecognized_opts" >&5 +$as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2;} +fi + + +if test "$gtk_version_desired" = "no"; then cat <]]) +AC_CHECK_HEADERS([sys/auxv.h asm/hwcap.h glob.h]) AC_SEARCH_LIBS([clock_gettime], [rt], [AC_DEFINE([HAVE_CLOCK_GETTIME],[],[Define if clock_gettime() is available])]) AC_CACHE_CHECK([for SO_PEERCRED and dependencies], [x_cv_linux_so_peercred], [ diff --git a/contrib/kh2reg.py b/contrib/kh2reg.py index 3c2a9c5..272124d 100755 --- a/contrib/kh2reg.py +++ b/contrib/kh2reg.py @@ -8,8 +8,7 @@ # kh2reg.py --unix known_hosts1 2 3 4 ... > sshhostkeys # Creates data suitable for storing in ~/.putty/sshhostkeys (Unix). # Line endings are someone else's problem as is traditional. -# Originally developed for Python 1.5.2, but probably won't run on that -# any more. +# Should run under either Python 2 or 3. import fileinput import base64 @@ -17,7 +16,11 @@ import string import re import sys -import getopt +import argparse +import itertools +import collections +import hashlib +from functools import reduce def winmungestr(s): "Duplicate of PuTTY's mungestr() in winstore.c:1.10 for Registry keys" @@ -31,48 +34,161 @@ def winmungestr(s): candot = 1 return r -def strtolong(s): - "Convert arbitrary-length big-endian binary data to a Python long" - bytes = struct.unpack(">%luB" % len(s), s) - return reduce ((lambda a, b: (long(a) << 8) + long(b)), bytes) +def strtoint(s): + "Convert arbitrary-length big-endian binary data to a Python int" + bytes = struct.unpack(">{:d}B".format(len(s)), s) + return reduce ((lambda a, b: (int(a) << 8) + int(b)), bytes) -def strtolong_le(s): - "Convert arbitrary-length little-endian binary data to a Python long" - bytes = reversed(struct.unpack(">%luB" % len(s), s)) - return reduce ((lambda a, b: (long(a) << 8) + long(b)), bytes) +def strtoint_le(s): + "Convert arbitrary-length little-endian binary data to a Python int" + bytes = reversed(struct.unpack(">{:d}B".format(len(s)), s)) + return reduce ((lambda a, b: (int(a) << 8) + int(b)), bytes) -def longtohex(n): - """Convert long int to lower-case hex. - - Ick, Python (at least in 1.5.2) doesn't appear to have a way to - turn a long int into an unadorned hex string -- % gets upset if the - number is too big, and raw hex() uses uppercase (sometimes), and - adds unwanted "0x...L" around it.""" - - plain=string.lower(re.match(r"0x([0-9A-Fa-f]*)l?$", hex(n), re.I).group(1)) - return "0x" + plain +def inttohex(n): + "Convert int to lower-case hex." + return "0x{:x}".format(n) def warn(s): "Warning with file/line number" sys.stderr.write("%s:%d: %s\n" % (fileinput.filename(), fileinput.filelineno(), s)) -output_type = 'windows' - -try: - optlist, args = getopt.getopt(sys.argv[1:], '', [ 'win', 'unix' ]) - if filter(lambda x: x[0] == '--unix', optlist): - output_type = 'unix' -except getopt.error, e: - sys.stderr.write(str(e) + "\n") - sys.exit(1) - -if output_type == 'windows': - # Output REG file header. - sys.stdout.write("""REGEDIT4 - -[HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys] -""") +class HMAC(object): + def __init__(self, hashclass, blocksize): + self.hashclass = hashclass + self.blocksize = blocksize + self.struct = struct.Struct(">{:d}B".format(self.blocksize)) + def pad_key(self, key): + return key + b'\0' * (self.blocksize - len(key)) + def xor_key(self, key, xor): + return self.struct.pack(*[b ^ xor for b in self.struct.unpack(key)]) + def keyed_hash(self, key, padbyte, string): + return self.hashclass(self.xor_key(key, padbyte) + string).digest() + def compute(self, key, string): + if len(key) > self.blocksize: + key = self.hashclass(key).digest() + key = self.pad_key(key) + return self.keyed_hash(key, 0x5C, self.keyed_hash(key, 0x36, string)) + +def openssh_hashed_host_match(hashed_host, try_host): + if hashed_host.startswith(b'|1|'): + salt, expected = hashed_host[3:].split(b'|') + salt = base64.decodestring(salt) + expected = base64.decodestring(expected) + mac = HMAC(hashlib.sha1, 64) + else: + return False # unrecognised magic number prefix + + return mac.compute(salt, try_host) == expected + +def invert(n, p): + """Compute inverse mod p.""" + if n % p == 0: + raise ZeroDivisionError() + a = n, 1, 0 + b = p, 0, 1 + while b[0]: + q = a[0] // b[0] + a = a[0] - q*b[0], a[1] - q*b[1], a[2] - q*b[2] + b, a = a, b + assert abs(a[0]) == 1 + return a[1]*a[0] + +def jacobi(n,m): + """Compute the Jacobi symbol. + + The special case of this when m is prime is the Legendre symbol, + which is 0 if n is congruent to 0 mod m; 1 if n is congruent to a + non-zero square number mod m; -1 if n is not congruent to any + square mod m. + + """ + assert m & 1 + acc = 1 + while True: + n %= m + if n == 0: + return 0 + while not (n & 1): + n >>= 1 + if (m & 7) not in {1,7}: + acc *= -1 + if n == 1: + return acc + if (n & 3) == 3 and (m & 3) == 3: + acc *= -1 + n, m = m, n + +class SqrtModP(object): + """Class for finding square roots of numbers mod p. + + p must be an odd prime (but its primality is not checked).""" + + def __init__(self, p): + p = abs(p) + assert p & 1 + self.p = p + + # Decompose p as 2^e k + 1 for odd k. + self.k = p-1 + self.e = 0 + while not (self.k & 1): + self.k >>= 1 + self.e += 1 + + # Find a non-square mod p. + for self.z in itertools.count(1): + if jacobi(self.z, self.p) == -1: + break + self.zinv = invert(self.z, self.p) + + def sqrt_recurse(self, a): + ak = pow(a, self.k, self.p) + for i in range(self.e, -1, -1): + if ak == 1: + break + ak = ak*ak % self.p + assert i > 0 + if i == self.e: + return pow(a, (self.k+1) // 2, self.p) + r_prime = self.sqrt_recurse(a * pow(self.z, 2**i, self.p)) + return r_prime * pow(self.zinv, 2**(i-1), self.p) % self.p + + def sqrt(self, a): + j = jacobi(a, self.p) + if j == 0: + return 0 + if j < 0: + raise ValueError("{} has no square root mod {}".format(a, self.p)) + a %= self.p + r = self.sqrt_recurse(a) + assert r*r % self.p == a + # Normalise to the smaller (or 'positive') one of the two roots. + return min(r, self.p - r) + + def __str__(self): + return "{}({})".format(type(self).__name__, self.p) + def __repr__(self): + return self.__str__() + + instances = {} + + @classmethod + def make(cls, p): + if p not in cls.instances: + cls.instances[p] = cls(p) + return cls.instances[p] + + @classmethod + def root(cls, n, p): + return cls.make(p).sqrt(n) + +NistCurve = collections.namedtuple("NistCurve", "p a b") +nist_curves = { + "ecdsa-sha2-nistp256": NistCurve(0xffffffff00000001000000000000000000000000ffffffffffffffffffffffff, 0xffffffff00000001000000000000000000000000fffffffffffffffffffffffc, 0x5ac635d8aa3a93e7b3ebbd55769886bc651d06b0cc53b0f63bce3c3e27d2604b), + "ecdsa-sha2-nistp384": NistCurve(0xfffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffeffffffff0000000000000000ffffffff, 0xfffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffeffffffff0000000000000000fffffffc, 0xb3312fa7e23ee7e4988e056be3f82d19181d9c6efe8141120314088f5013875ac656398d8a2ed19d2a85c8edd3ec2aef), + "ecdsa-sha2-nistp521": NistCurve(0x01ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff, 0x01fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffc, 0x0051953eb9618e1c9a1f929a21a0b68540eea2da725b99b315f3b8b489918ef109e156193951ec7e937b1652c0bd3bb1bf073573df883d2c34f1ef451fd46b503f00), +} class BlankInputLine(Exception): pass @@ -85,19 +201,17 @@ class KeyFormatError(Exception): def __init__(self, msg): self.msg = msg -# Now process all known_hosts input. -for line in fileinput.input(args): - +def handle_line(line, output_formatter, try_hosts): try: # Remove leading/trailing whitespace (should zap CR and LF) - line = string.strip (line) + line = line.strip() # Skip blanks and comments if line == '' or line[0] == '#': raise BlankInputLine # Split line on spaces. - fields = string.split (line, ' ') + fields = line.split(' ') # Common fields hostpat = fields[0] @@ -111,14 +225,15 @@ def __init__(self, msg): # Treat as SSH-1-type host key. # Format: hostpat bits10 exp10 mod10 comment... # (PuTTY doesn't store the number of bits.) - keyparams = map (long, fields[2:4]) + keyparams = map (int, fields[2:4]) keytype = "rsa" else: # Treat as SSH-2-type host key. # Format: hostpat keytype keyblob64 comment... - sshkeytype, blob = fields[1], base64.decodestring (fields[2]) + sshkeytype, blob = fields[1], base64.decodestring( + fields[2].encode("ASCII")) # 'blob' consists of a number of # uint32 N (big-endian) @@ -133,7 +248,7 @@ def __init__(self, msg): blob = blob [struct.calcsize(sizefmt) + size : ] # The first field is keytype again. - if subfields[0] != sshkeytype: + if subfields[0].decode("ASCII") != sshkeytype: raise KeyFormatError(""" outer and embedded key types do not match: '%s', '%s' """ % (sshkeytype, subfields[1])) @@ -144,51 +259,58 @@ def __init__(self, msg): keytype = "rsa2" # The rest of the subfields we can treat as an opaque list # of bignums (same numbers and order as stored by PuTTY). - keyparams = map (strtolong, subfields[1:]) + keyparams = map (strtoint, subfields[1:]) elif sshkeytype == "ssh-dss": keytype = "dss" # Same again. - keyparams = map (strtolong, subfields[1:]) + keyparams = map (strtoint, subfields[1:]) - elif sshkeytype == "ecdsa-sha2-nistp256" \ - or sshkeytype == "ecdsa-sha2-nistp384" \ - or sshkeytype == "ecdsa-sha2-nistp521": + elif sshkeytype in nist_curves: keytype = sshkeytype # Have to parse this a bit. if len(subfields) > 3: raise KeyFormatError("too many subfields in blob") (curvename, Q) = subfields[1:] # First is yet another copy of the key name. - if not re.match("ecdsa-sha2-" + re.escape(curvename), - sshkeytype): + if not re.match("ecdsa-sha2-" + re.escape( + curvename.decode("ASCII")), sshkeytype): raise KeyFormatError("key type mismatch ('%s' vs '%s')" % (sshkeytype, curvename)) # Second contains key material X and Y (hopefully). # First a magic octet indicating point compression. - if struct.unpack("B", Q[0])[0] != 4: - # No-one seems to use this. - raise KeyFormatError("can't convert point-compressed ECDSA") - # Then two equal-length bignums (X and Y). - bnlen = len(Q)-1 - if (bnlen % 1) != 0: - raise KeyFormatError("odd-length X+Y") - bnlen = bnlen / 2 - (x,y) = Q[1:bnlen+1], Q[bnlen+1:2*bnlen+1] - keyparams = [curvename] + map (strtolong, [x,y]) + point_type = struct.unpack_from("B", Q, 0)[0] + Qrest = Q[1:] + if point_type == 4: + # Then two equal-length bignums (X and Y). + bnlen = len(Qrest) + if (bnlen % 1) != 0: + raise KeyFormatError("odd-length X+Y") + bnlen = bnlen // 2 + x = strtoint(Qrest[:bnlen]) + y = strtoint(Qrest[bnlen:]) + elif 2 <= point_type <= 3: + # A compressed point just specifies X, and leaves + # Y implicit except for parity, so we have to + # recover it from the curve equation. + curve = nist_curves[sshkeytype] + x = strtoint(Qrest) + yy = (x*x*x + curve.a*x + curve.b) % curve.p + y = SqrtModP.root(yy, curve.p) + if y % 2 != point_type % 2: + y = curve.p - y + + keyparams = [curvename, x, y] elif sshkeytype == "ssh-ed25519": keytype = sshkeytype if len(subfields) != 2: raise KeyFormatError("wrong number of subfields in blob") - if subfields[0] != sshkeytype: - raise KeyFormatError("key type mismatch ('%s' vs '%s')" - % (sshkeytype, subfields[0])) # Key material y, with the top bit being repurposed as # the expected parity of the associated x (point # compression). - y = strtolong_le(subfields[1]) + y = strtoint_le(subfields[1]) x_parity = y >> 255 y &= ~(1 << 255) @@ -197,19 +319,10 @@ def __init__(self, msg): d = 0x52036cee2b6ffe738cc740797779e89800700a4d4141d8ab75eb4dca135978a3 # Recover x^2 = (y^2 - 1) / (d y^2 + 1). - # - # With no real time constraints here, it's easier to - # take the inverse of the denominator by raising it to - # the power p-2 (by Fermat's Little Theorem) than - # faffing about with the properly efficient Euclid - # method. - xx = (y*y - 1) * pow(d*y*y + 1, p-2, p) % p - - # Take the square root, which may require trying twice. - x = pow(xx, (p+3)/8, p) - if pow(x, 2, p) != xx: - x = x * pow(2, (p-1)/4, p) % p - assert pow(x, 2, p) == xx + xx = (y*y - 1) * invert(d*y*y + 1, p) % p + + # Take the square root. + x = SqrtModP.root(xx, p) # Pick the square root of the correct parity. if (x % 2) != x_parity: @@ -220,51 +333,108 @@ def __init__(self, msg): raise UnknownKeyType(sshkeytype) # Now print out one line per host pattern, discarding wildcards. - for host in string.split (hostpat, ','): + for host in hostpat.split(','): if re.search (r"[*?!]", host): warn("skipping wildcard host pattern '%s'" % host) continue - elif re.match (r"\|", host): - warn("skipping hashed hostname '%s'" % host) - continue - else: - m = re.match (r"\[([^]]*)\]:(\d*)$", host) - if m: - (host, port) = m.group(1,2) - port = int(port) - else: - port = 22 - # Slightly bizarre output key format: 'type@port:hostname' - # XXX: does PuTTY do anything useful with literal IP[v4]s? - key = keytype + ("@%d:%s" % (port, host)) - # Most of these are numbers, but there's the occasional - # string that needs passing through - value = string.join (map ( - lambda x: x if isinstance(x, basestring) else longtohex(x), - keyparams), ',') - if output_type == 'unix': - # Unix format. - sys.stdout.write('%s %s\n' % (key, value)) + + if re.match (r"\|", host): + for try_host in try_hosts: + if openssh_hashed_host_match(host.encode('ASCII'), + try_host.encode('UTF-8')): + host = try_host + break else: - # Windows format. - # XXX: worry about double quotes? - sys.stdout.write("\"%s\"=\"%s\"\n" - % (winmungestr(key), value)) + warn("unable to match hashed hostname '%s'" % host) + continue - except UnknownKeyType, k: + m = re.match (r"\[([^]]*)\]:(\d*)$", host) + if m: + (host, port) = m.group(1,2) + port = int(port) + else: + port = 22 + # Slightly bizarre output key format: 'type@port:hostname' + # XXX: does PuTTY do anything useful with literal IP[v4]s? + key = keytype + ("@%d:%s" % (port, host)) + # Most of these are numbers, but there's the occasional + # string that needs passing through + value = ",".join(map( + lambda x: x if isinstance(x, str) + else x.decode('ASCII') if isinstance(x, bytes) + else inttohex(x), keyparams)) + output_formatter.key(key, value) + + except UnknownKeyType as k: warn("unknown SSH key type '%s', skipping" % k.keytype) - except KeyFormatError, k: + except KeyFormatError as k: warn("trouble parsing key (%s), skipping" % k.msg) except BlankInputLine: pass -# The spec at http://support.microsoft.com/kb/310516 says we need -# a blank line at the end of the reg file: -# -# Note the registry file should contain a blank line at the -# bottom of the file. -# -if output_type == 'windows': - # Output REG file header. - sys.stdout.write("\n") - +class OutputFormatter(object): + def __init__(self, fh): + self.fh = fh + def header(self): + pass + def trailer(self): + pass + +class WindowsOutputFormatter(OutputFormatter): + def header(self): + # Output REG file header. + self.fh.write("""REGEDIT4 + +[HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys] +""") + + def key(self, key, value): + # XXX: worry about double quotes? + self.fh.write("\"%s\"=\"%s\"\n" % (winmungestr(key), value)) + + def trailer(self): + # The spec at http://support.microsoft.com/kb/310516 says we need + # a blank line at the end of the reg file: + # + # Note the registry file should contain a blank line at the + # bottom of the file. + # + self.fh.write("\n") + +class UnixOutputFormatter(OutputFormatter): + def key(self, key, value): + self.fh.write('%s %s\n' % (key, value)) + +def main(): + parser = argparse.ArgumentParser( + description="Convert OpenSSH known hosts files to PuTTY's format.") + group = parser.add_mutually_exclusive_group() + group.add_argument( + "--windows", "--win", action='store_const', + dest="output_formatter_class", const=WindowsOutputFormatter, + help="Produce Windows .reg file output that regedit.exe can import" + " (default).") + group.add_argument( + "--unix", action='store_const', + dest="output_formatter_class", const=UnixOutputFormatter, + help="Produce a file suitable for use as ~/.putty/sshhostkeys.") + parser.add_argument("-o", "--output", type=argparse.FileType("w"), + default=argparse.FileType("w")("-"), + help="Output file to write to (default stdout).") + parser.add_argument("--hostname", action="append", + help="Host name(s) to try matching against hashed " + "host entries in input.") + parser.add_argument("infile", nargs="*", + help="Input file(s) to read from (default stdin).") + parser.set_defaults(output_formatter_class=WindowsOutputFormatter, + hostname=[]) + args = parser.parse_args() + + output_formatter = args.output_formatter_class(args.output) + output_formatter.header() + for line in fileinput.input(args.infile): + handle_line(line, output_formatter, args.hostname) + output_formatter.trailer() + +if __name__ == "__main__": + main() diff --git a/defs.h b/defs.h index 6c37b99..afeb506 100644 --- a/defs.h +++ b/defs.h @@ -16,12 +16,13 @@ #include #if defined _MSC_VER && _MSC_VER < 1800 -/* Work around lack of inttypes.h in older MSVC */ +/* Work around lack of inttypes.h and strtoumax in older MSVC */ #define PRIx32 "x" #define PRIu64 "I64u" #define PRIdMAX "I64d" #define PRIXMAX "I64X" #define SCNu64 "I64u" +uintmax_t strtoumax(const char *nptr, char **endptr, int base); #else #include #endif @@ -79,6 +80,7 @@ typedef struct MontgomeryPoint MontgomeryPoint; typedef struct EdwardsCurve EdwardsCurve; typedef struct EdwardsPoint EdwardsPoint; +typedef struct SshServerConfig SshServerConfig; typedef struct SftpServer SftpServer; typedef struct SftpServerVtable SftpServerVtable; diff --git a/depcomp b/depcomp new file mode 100644 index 0000000..b39f98f --- /dev/null +++ b/depcomp @@ -0,0 +1,791 @@ +#! /bin/sh +# depcomp - compile a program generating dependencies as side-effects + +scriptversion=2016-01-11.22; # UTC + +# Copyright (C) 1999-2017 Free Software Foundation, Inc. + +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2, or (at your option) +# any later version. + +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. + +# You should have received a copy of the GNU General Public License +# along with this program. If not, see . + +# As a special exception to the GNU General Public License, if you +# distribute this file as part of a program that contains a +# configuration script generated by Autoconf, you may include it under +# the same distribution terms that you use for the rest of that program. + +# Originally written by Alexandre Oliva . + +case $1 in + '') + echo "$0: No command. Try '$0 --help' for more information." 1>&2 + exit 1; + ;; + -h | --h*) + cat <<\EOF +Usage: depcomp [--help] [--version] PROGRAM [ARGS] + +Run PROGRAMS ARGS to compile a file, generating dependencies +as side-effects. + +Environment variables: + depmode Dependency tracking mode. + source Source file read by 'PROGRAMS ARGS'. + object Object file output by 'PROGRAMS ARGS'. + DEPDIR directory where to store dependencies. + depfile Dependency file to output. + tmpdepfile Temporary file to use when outputting dependencies. + libtool Whether libtool is used (yes/no). + +Report bugs to . +EOF + exit $? + ;; + -v | --v*) + echo "depcomp $scriptversion" + exit $? + ;; +esac + +# Get the directory component of the given path, and save it in the +# global variables '$dir'. Note that this directory component will +# be either empty or ending with a '/' character. This is deliberate. +set_dir_from () +{ + case $1 in + */*) dir=`echo "$1" | sed -e 's|/[^/]*$|/|'`;; + *) dir=;; + esac +} + +# Get the suffix-stripped basename of the given path, and save it the +# global variable '$base'. +set_base_from () +{ + base=`echo "$1" | sed -e 's|^.*/||' -e 's/\.[^.]*$//'` +} + +# If no dependency file was actually created by the compiler invocation, +# we still have to create a dummy depfile, to avoid errors with the +# Makefile "include basename.Plo" scheme. +make_dummy_depfile () +{ + echo "#dummy" > "$depfile" +} + +# Factor out some common post-processing of the generated depfile. +# Requires the auxiliary global variable '$tmpdepfile' to be set. +aix_post_process_depfile () +{ + # If the compiler actually managed to produce a dependency file, + # post-process it. + if test -f "$tmpdepfile"; then + # Each line is of the form 'foo.o: dependency.h'. + # Do two passes, one to just change these to + # $object: dependency.h + # and one to simply output + # dependency.h: + # which is needed to avoid the deleted-header problem. + { sed -e "s,^.*\.[$lower]*:,$object:," < "$tmpdepfile" + sed -e "s,^.*\.[$lower]*:[$tab ]*,," -e 's,$,:,' < "$tmpdepfile" + } > "$depfile" + rm -f "$tmpdepfile" + else + make_dummy_depfile + fi +} + +# A tabulation character. +tab=' ' +# A newline character. +nl=' +' +# Character ranges might be problematic outside the C locale. +# These definitions help. +upper=ABCDEFGHIJKLMNOPQRSTUVWXYZ +lower=abcdefghijklmnopqrstuvwxyz +digits=0123456789 +alpha=${upper}${lower} + +if test -z "$depmode" || test -z "$source" || test -z "$object"; then + echo "depcomp: Variables source, object and depmode must be set" 1>&2 + exit 1 +fi + +# Dependencies for sub/bar.o or sub/bar.obj go into sub/.deps/bar.Po. +depfile=${depfile-`echo "$object" | + sed 's|[^\\/]*$|'${DEPDIR-.deps}'/&|;s|\.\([^.]*\)$|.P\1|;s|Pobj$|Po|'`} +tmpdepfile=${tmpdepfile-`echo "$depfile" | sed 's/\.\([^.]*\)$/.T\1/'`} + +rm -f "$tmpdepfile" + +# Avoid interferences from the environment. +gccflag= dashmflag= + +# Some modes work just like other modes, but use different flags. We +# parameterize here, but still list the modes in the big case below, +# to make depend.m4 easier to write. Note that we *cannot* use a case +# here, because this file can only contain one case statement. +if test "$depmode" = hp; then + # HP compiler uses -M and no extra arg. + gccflag=-M + depmode=gcc +fi + +if test "$depmode" = dashXmstdout; then + # This is just like dashmstdout with a different argument. + dashmflag=-xM + depmode=dashmstdout +fi + +cygpath_u="cygpath -u -f -" +if test "$depmode" = msvcmsys; then + # This is just like msvisualcpp but w/o cygpath translation. + # Just convert the backslash-escaped backslashes to single forward + # slashes to satisfy depend.m4 + cygpath_u='sed s,\\\\,/,g' + depmode=msvisualcpp +fi + +if test "$depmode" = msvc7msys; then + # This is just like msvc7 but w/o cygpath translation. + # Just convert the backslash-escaped backslashes to single forward + # slashes to satisfy depend.m4 + cygpath_u='sed s,\\\\,/,g' + depmode=msvc7 +fi + +if test "$depmode" = xlc; then + # IBM C/C++ Compilers xlc/xlC can output gcc-like dependency information. + gccflag=-qmakedep=gcc,-MF + depmode=gcc +fi + +case "$depmode" in +gcc3) +## gcc 3 implements dependency tracking that does exactly what +## we want. Yay! Note: for some reason libtool 1.4 doesn't like +## it if -MD -MP comes after the -MF stuff. Hmm. +## Unfortunately, FreeBSD c89 acceptance of flags depends upon +## the command line argument order; so add the flags where they +## appear in depend2.am. Note that the slowdown incurred here +## affects only configure: in makefiles, %FASTDEP% shortcuts this. + for arg + do + case $arg in + -c) set fnord "$@" -MT "$object" -MD -MP -MF "$tmpdepfile" "$arg" ;; + *) set fnord "$@" "$arg" ;; + esac + shift # fnord + shift # $arg + done + "$@" + stat=$? + if test $stat -ne 0; then + rm -f "$tmpdepfile" + exit $stat + fi + mv "$tmpdepfile" "$depfile" + ;; + +gcc) +## Note that this doesn't just cater to obsosete pre-3.x GCC compilers. +## but also to in-use compilers like IMB xlc/xlC and the HP C compiler. +## (see the conditional assignment to $gccflag above). +## There are various ways to get dependency output from gcc. Here's +## why we pick this rather obscure method: +## - Don't want to use -MD because we'd like the dependencies to end +## up in a subdir. Having to rename by hand is ugly. +## (We might end up doing this anyway to support other compilers.) +## - The DEPENDENCIES_OUTPUT environment variable makes gcc act like +## -MM, not -M (despite what the docs say). Also, it might not be +## supported by the other compilers which use the 'gcc' depmode. +## - Using -M directly means running the compiler twice (even worse +## than renaming). + if test -z "$gccflag"; then + gccflag=-MD, + fi + "$@" -Wp,"$gccflag$tmpdepfile" + stat=$? + if test $stat -ne 0; then + rm -f "$tmpdepfile" + exit $stat + fi + rm -f "$depfile" + echo "$object : \\" > "$depfile" + # The second -e expression handles DOS-style file names with drive + # letters. + sed -e 's/^[^:]*: / /' \ + -e 's/^['$alpha']:\/[^:]*: / /' < "$tmpdepfile" >> "$depfile" +## This next piece of magic avoids the "deleted header file" problem. +## The problem is that when a header file which appears in a .P file +## is deleted, the dependency causes make to die (because there is +## typically no way to rebuild the header). We avoid this by adding +## dummy dependencies for each header file. Too bad gcc doesn't do +## this for us directly. +## Some versions of gcc put a space before the ':'. On the theory +## that the space means something, we add a space to the output as +## well. hp depmode also adds that space, but also prefixes the VPATH +## to the object. Take care to not repeat it in the output. +## Some versions of the HPUX 10.20 sed can't process this invocation +## correctly. Breaking it into two sed invocations is a workaround. + tr ' ' "$nl" < "$tmpdepfile" \ + | sed -e 's/^\\$//' -e '/^$/d' -e "s|.*$object$||" -e '/:$/d' \ + | sed -e 's/$/ :/' >> "$depfile" + rm -f "$tmpdepfile" + ;; + +hp) + # This case exists only to let depend.m4 do its work. It works by + # looking at the text of this script. This case will never be run, + # since it is checked for above. + exit 1 + ;; + +sgi) + if test "$libtool" = yes; then + "$@" "-Wp,-MDupdate,$tmpdepfile" + else + "$@" -MDupdate "$tmpdepfile" + fi + stat=$? + if test $stat -ne 0; then + rm -f "$tmpdepfile" + exit $stat + fi + rm -f "$depfile" + + if test -f "$tmpdepfile"; then # yes, the sourcefile depend on other files + echo "$object : \\" > "$depfile" + # Clip off the initial element (the dependent). Don't try to be + # clever and replace this with sed code, as IRIX sed won't handle + # lines with more than a fixed number of characters (4096 in + # IRIX 6.2 sed, 8192 in IRIX 6.5). We also remove comment lines; + # the IRIX cc adds comments like '#:fec' to the end of the + # dependency line. + tr ' ' "$nl" < "$tmpdepfile" \ + | sed -e 's/^.*\.o://' -e 's/#.*$//' -e '/^$/ d' \ + | tr "$nl" ' ' >> "$depfile" + echo >> "$depfile" + # The second pass generates a dummy entry for each header file. + tr ' ' "$nl" < "$tmpdepfile" \ + | sed -e 's/^.*\.o://' -e 's/#.*$//' -e '/^$/ d' -e 's/$/:/' \ + >> "$depfile" + else + make_dummy_depfile + fi + rm -f "$tmpdepfile" + ;; + +xlc) + # This case exists only to let depend.m4 do its work. It works by + # looking at the text of this script. This case will never be run, + # since it is checked for above. + exit 1 + ;; + +aix) + # The C for AIX Compiler uses -M and outputs the dependencies + # in a .u file. In older versions, this file always lives in the + # current directory. Also, the AIX compiler puts '$object:' at the + # start of each line; $object doesn't have directory information. + # Version 6 uses the directory in both cases. + set_dir_from "$object" + set_base_from "$object" + if test "$libtool" = yes; then + tmpdepfile1=$dir$base.u + tmpdepfile2=$base.u + tmpdepfile3=$dir.libs/$base.u + "$@" -Wc,-M + else + tmpdepfile1=$dir$base.u + tmpdepfile2=$dir$base.u + tmpdepfile3=$dir$base.u + "$@" -M + fi + stat=$? + if test $stat -ne 0; then + rm -f "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3" + exit $stat + fi + + for tmpdepfile in "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3" + do + test -f "$tmpdepfile" && break + done + aix_post_process_depfile + ;; + +tcc) + # tcc (Tiny C Compiler) understand '-MD -MF file' since version 0.9.26 + # FIXME: That version still under development at the moment of writing. + # Make that this statement remains true also for stable, released + # versions. + # It will wrap lines (doesn't matter whether long or short) with a + # trailing '\', as in: + # + # foo.o : \ + # foo.c \ + # foo.h \ + # + # It will put a trailing '\' even on the last line, and will use leading + # spaces rather than leading tabs (at least since its commit 0394caf7 + # "Emit spaces for -MD"). + "$@" -MD -MF "$tmpdepfile" + stat=$? + if test $stat -ne 0; then + rm -f "$tmpdepfile" + exit $stat + fi + rm -f "$depfile" + # Each non-empty line is of the form 'foo.o : \' or ' dep.h \'. + # We have to change lines of the first kind to '$object: \'. + sed -e "s|.*:|$object :|" < "$tmpdepfile" > "$depfile" + # And for each line of the second kind, we have to emit a 'dep.h:' + # dummy dependency, to avoid the deleted-header problem. + sed -n -e 's|^ *\(.*\) *\\$|\1:|p' < "$tmpdepfile" >> "$depfile" + rm -f "$tmpdepfile" + ;; + +## The order of this option in the case statement is important, since the +## shell code in configure will try each of these formats in the order +## listed in this file. A plain '-MD' option would be understood by many +## compilers, so we must ensure this comes after the gcc and icc options. +pgcc) + # Portland's C compiler understands '-MD'. + # Will always output deps to 'file.d' where file is the root name of the + # source file under compilation, even if file resides in a subdirectory. + # The object file name does not affect the name of the '.d' file. + # pgcc 10.2 will output + # foo.o: sub/foo.c sub/foo.h + # and will wrap long lines using '\' : + # foo.o: sub/foo.c ... \ + # sub/foo.h ... \ + # ... + set_dir_from "$object" + # Use the source, not the object, to determine the base name, since + # that's sadly what pgcc will do too. + set_base_from "$source" + tmpdepfile=$base.d + + # For projects that build the same source file twice into different object + # files, the pgcc approach of using the *source* file root name can cause + # problems in parallel builds. Use a locking strategy to avoid stomping on + # the same $tmpdepfile. + lockdir=$base.d-lock + trap " + echo '$0: caught signal, cleaning up...' >&2 + rmdir '$lockdir' + exit 1 + " 1 2 13 15 + numtries=100 + i=$numtries + while test $i -gt 0; do + # mkdir is a portable test-and-set. + if mkdir "$lockdir" 2>/dev/null; then + # This process acquired the lock. + "$@" -MD + stat=$? + # Release the lock. + rmdir "$lockdir" + break + else + # If the lock is being held by a different process, wait + # until the winning process is done or we timeout. + while test -d "$lockdir" && test $i -gt 0; do + sleep 1 + i=`expr $i - 1` + done + fi + i=`expr $i - 1` + done + trap - 1 2 13 15 + if test $i -le 0; then + echo "$0: failed to acquire lock after $numtries attempts" >&2 + echo "$0: check lockdir '$lockdir'" >&2 + exit 1 + fi + + if test $stat -ne 0; then + rm -f "$tmpdepfile" + exit $stat + fi + rm -f "$depfile" + # Each line is of the form `foo.o: dependent.h', + # or `foo.o: dep1.h dep2.h \', or ` dep3.h dep4.h \'. + # Do two passes, one to just change these to + # `$object: dependent.h' and one to simply `dependent.h:'. + sed "s,^[^:]*:,$object :," < "$tmpdepfile" > "$depfile" + # Some versions of the HPUX 10.20 sed can't process this invocation + # correctly. Breaking it into two sed invocations is a workaround. + sed 's,^[^:]*: \(.*\)$,\1,;s/^\\$//;/^$/d;/:$/d' < "$tmpdepfile" \ + | sed -e 's/$/ :/' >> "$depfile" + rm -f "$tmpdepfile" + ;; + +hp2) + # The "hp" stanza above does not work with aCC (C++) and HP's ia64 + # compilers, which have integrated preprocessors. The correct option + # to use with these is +Maked; it writes dependencies to a file named + # 'foo.d', which lands next to the object file, wherever that + # happens to be. + # Much of this is similar to the tru64 case; see comments there. + set_dir_from "$object" + set_base_from "$object" + if test "$libtool" = yes; then + tmpdepfile1=$dir$base.d + tmpdepfile2=$dir.libs/$base.d + "$@" -Wc,+Maked + else + tmpdepfile1=$dir$base.d + tmpdepfile2=$dir$base.d + "$@" +Maked + fi + stat=$? + if test $stat -ne 0; then + rm -f "$tmpdepfile1" "$tmpdepfile2" + exit $stat + fi + + for tmpdepfile in "$tmpdepfile1" "$tmpdepfile2" + do + test -f "$tmpdepfile" && break + done + if test -f "$tmpdepfile"; then + sed -e "s,^.*\.[$lower]*:,$object:," "$tmpdepfile" > "$depfile" + # Add 'dependent.h:' lines. + sed -ne '2,${ + s/^ *// + s/ \\*$// + s/$/:/ + p + }' "$tmpdepfile" >> "$depfile" + else + make_dummy_depfile + fi + rm -f "$tmpdepfile" "$tmpdepfile2" + ;; + +tru64) + # The Tru64 compiler uses -MD to generate dependencies as a side + # effect. 'cc -MD -o foo.o ...' puts the dependencies into 'foo.o.d'. + # At least on Alpha/Redhat 6.1, Compaq CCC V6.2-504 seems to put + # dependencies in 'foo.d' instead, so we check for that too. + # Subdirectories are respected. + set_dir_from "$object" + set_base_from "$object" + + if test "$libtool" = yes; then + # Libtool generates 2 separate objects for the 2 libraries. These + # two compilations output dependencies in $dir.libs/$base.o.d and + # in $dir$base.o.d. We have to check for both files, because + # one of the two compilations can be disabled. We should prefer + # $dir$base.o.d over $dir.libs/$base.o.d because the latter is + # automatically cleaned when .libs/ is deleted, while ignoring + # the former would cause a distcleancheck panic. + tmpdepfile1=$dir$base.o.d # libtool 1.5 + tmpdepfile2=$dir.libs/$base.o.d # Likewise. + tmpdepfile3=$dir.libs/$base.d # Compaq CCC V6.2-504 + "$@" -Wc,-MD + else + tmpdepfile1=$dir$base.d + tmpdepfile2=$dir$base.d + tmpdepfile3=$dir$base.d + "$@" -MD + fi + + stat=$? + if test $stat -ne 0; then + rm -f "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3" + exit $stat + fi + + for tmpdepfile in "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3" + do + test -f "$tmpdepfile" && break + done + # Same post-processing that is required for AIX mode. + aix_post_process_depfile + ;; + +msvc7) + if test "$libtool" = yes; then + showIncludes=-Wc,-showIncludes + else + showIncludes=-showIncludes + fi + "$@" $showIncludes > "$tmpdepfile" + stat=$? + grep -v '^Note: including file: ' "$tmpdepfile" + if test $stat -ne 0; then + rm -f "$tmpdepfile" + exit $stat + fi + rm -f "$depfile" + echo "$object : \\" > "$depfile" + # The first sed program below extracts the file names and escapes + # backslashes for cygpath. The second sed program outputs the file + # name when reading, but also accumulates all include files in the + # hold buffer in order to output them again at the end. This only + # works with sed implementations that can handle large buffers. + sed < "$tmpdepfile" -n ' +/^Note: including file: *\(.*\)/ { + s//\1/ + s/\\/\\\\/g + p +}' | $cygpath_u | sort -u | sed -n ' +s/ /\\ /g +s/\(.*\)/'"$tab"'\1 \\/p +s/.\(.*\) \\/\1:/ +H +$ { + s/.*/'"$tab"'/ + G + p +}' >> "$depfile" + echo >> "$depfile" # make sure the fragment doesn't end with a backslash + rm -f "$tmpdepfile" + ;; + +msvc7msys) + # This case exists only to let depend.m4 do its work. It works by + # looking at the text of this script. This case will never be run, + # since it is checked for above. + exit 1 + ;; + +#nosideeffect) + # This comment above is used by automake to tell side-effect + # dependency tracking mechanisms from slower ones. + +dashmstdout) + # Important note: in order to support this mode, a compiler *must* + # always write the preprocessed file to stdout, regardless of -o. + "$@" || exit $? + + # Remove the call to Libtool. + if test "$libtool" = yes; then + while test "X$1" != 'X--mode=compile'; do + shift + done + shift + fi + + # Remove '-o $object'. + IFS=" " + for arg + do + case $arg in + -o) + shift + ;; + $object) + shift + ;; + *) + set fnord "$@" "$arg" + shift # fnord + shift # $arg + ;; + esac + done + + test -z "$dashmflag" && dashmflag=-M + # Require at least two characters before searching for ':' + # in the target name. This is to cope with DOS-style filenames: + # a dependency such as 'c:/foo/bar' could be seen as target 'c' otherwise. + "$@" $dashmflag | + sed "s|^[$tab ]*[^:$tab ][^:][^:]*:[$tab ]*|$object: |" > "$tmpdepfile" + rm -f "$depfile" + cat < "$tmpdepfile" > "$depfile" + # Some versions of the HPUX 10.20 sed can't process this sed invocation + # correctly. Breaking it into two sed invocations is a workaround. + tr ' ' "$nl" < "$tmpdepfile" \ + | sed -e 's/^\\$//' -e '/^$/d' -e '/:$/d' \ + | sed -e 's/$/ :/' >> "$depfile" + rm -f "$tmpdepfile" + ;; + +dashXmstdout) + # This case only exists to satisfy depend.m4. It is never actually + # run, as this mode is specially recognized in the preamble. + exit 1 + ;; + +makedepend) + "$@" || exit $? + # Remove any Libtool call + if test "$libtool" = yes; then + while test "X$1" != 'X--mode=compile'; do + shift + done + shift + fi + # X makedepend + shift + cleared=no eat=no + for arg + do + case $cleared in + no) + set ""; shift + cleared=yes ;; + esac + if test $eat = yes; then + eat=no + continue + fi + case "$arg" in + -D*|-I*) + set fnord "$@" "$arg"; shift ;; + # Strip any option that makedepend may not understand. Remove + # the object too, otherwise makedepend will parse it as a source file. + -arch) + eat=yes ;; + -*|$object) + ;; + *) + set fnord "$@" "$arg"; shift ;; + esac + done + obj_suffix=`echo "$object" | sed 's/^.*\././'` + touch "$tmpdepfile" + ${MAKEDEPEND-makedepend} -o"$obj_suffix" -f"$tmpdepfile" "$@" + rm -f "$depfile" + # makedepend may prepend the VPATH from the source file name to the object. + # No need to regex-escape $object, excess matching of '.' is harmless. + sed "s|^.*\($object *:\)|\1|" "$tmpdepfile" > "$depfile" + # Some versions of the HPUX 10.20 sed can't process the last invocation + # correctly. Breaking it into two sed invocations is a workaround. + sed '1,2d' "$tmpdepfile" \ + | tr ' ' "$nl" \ + | sed -e 's/^\\$//' -e '/^$/d' -e '/:$/d' \ + | sed -e 's/$/ :/' >> "$depfile" + rm -f "$tmpdepfile" "$tmpdepfile".bak + ;; + +cpp) + # Important note: in order to support this mode, a compiler *must* + # always write the preprocessed file to stdout. + "$@" || exit $? + + # Remove the call to Libtool. + if test "$libtool" = yes; then + while test "X$1" != 'X--mode=compile'; do + shift + done + shift + fi + + # Remove '-o $object'. + IFS=" " + for arg + do + case $arg in + -o) + shift + ;; + $object) + shift + ;; + *) + set fnord "$@" "$arg" + shift # fnord + shift # $arg + ;; + esac + done + + "$@" -E \ + | sed -n -e '/^# [0-9][0-9]* "\([^"]*\)".*/ s:: \1 \\:p' \ + -e '/^#line [0-9][0-9]* "\([^"]*\)".*/ s:: \1 \\:p' \ + | sed '$ s: \\$::' > "$tmpdepfile" + rm -f "$depfile" + echo "$object : \\" > "$depfile" + cat < "$tmpdepfile" >> "$depfile" + sed < "$tmpdepfile" '/^$/d;s/^ //;s/ \\$//;s/$/ :/' >> "$depfile" + rm -f "$tmpdepfile" + ;; + +msvisualcpp) + # Important note: in order to support this mode, a compiler *must* + # always write the preprocessed file to stdout. + "$@" || exit $? + + # Remove the call to Libtool. + if test "$libtool" = yes; then + while test "X$1" != 'X--mode=compile'; do + shift + done + shift + fi + + IFS=" " + for arg + do + case "$arg" in + -o) + shift + ;; + $object) + shift + ;; + "-Gm"|"/Gm"|"-Gi"|"/Gi"|"-ZI"|"/ZI") + set fnord "$@" + shift + shift + ;; + *) + set fnord "$@" "$arg" + shift + shift + ;; + esac + done + "$@" -E 2>/dev/null | + sed -n '/^#line [0-9][0-9]* "\([^"]*\)"/ s::\1:p' | $cygpath_u | sort -u > "$tmpdepfile" + rm -f "$depfile" + echo "$object : \\" > "$depfile" + sed < "$tmpdepfile" -n -e 's% %\\ %g' -e '/^\(.*\)$/ s::'"$tab"'\1 \\:p' >> "$depfile" + echo "$tab" >> "$depfile" + sed < "$tmpdepfile" -n -e 's% %\\ %g' -e '/^\(.*\)$/ s::\1\::p' >> "$depfile" + rm -f "$tmpdepfile" + ;; + +msvcmsys) + # This case exists only to let depend.m4 do its work. It works by + # looking at the text of this script. This case will never be run, + # since it is checked for above. + exit 1 + ;; + +none) + exec "$@" + ;; + +*) + echo "Unknown depmode $depmode" 1>&2 + exit 1 + ;; +esac + +exit 0 + +# Local Variables: +# mode: shell-script +# sh-indentation: 2 +# eval: (add-hook 'write-file-hooks 'time-stamp) +# time-stamp-start: "scriptversion=" +# time-stamp-format: "%:y-%02m-%02d.%02H" +# time-stamp-time-zone: "UTC0" +# time-stamp-end: "; # UTC" +# End: diff --git a/dialog.h b/dialog.h index 6ccda34..ac1601c 100644 --- a/dialog.h +++ b/dialog.h @@ -585,6 +585,10 @@ void dlg_label_change(union control *ctrl, dlgparam *dp, char const *text); * functionality on it! */ union control *dlg_last_focused(union control *ctrl, dlgparam *dp); +/* + * Find out whether a particular control is currently visible. + */ +bool dlg_is_visible(union control *ctrl, dlgparam *dp); /* * During event processing, you might well want to give an error * indication to the user. dlg_beep() is a quick and easy generic diff --git a/doc/AppendixA.html b/doc/AppendixA.html new file mode 100644 index 0000000..20defde --- /dev/null +++ b/doc/AppendixA.html @@ -0,0 +1,1000 @@ + + + + +PuTTY FAQ + + + + + + + +

Previous | Contents | Index | Next

+ + +

Appendix A: PuTTY FAQ

+

+This FAQ is published on the PuTTY web site, and also provided as an appendix in the manual. +

+

A.1 Introduction

+

A.1.1 What is PuTTY?

+

+PuTTY is a client program for the SSH, Telnet and Rlogin network protocols. +

+

+These protocols are all used to run a remote session on a computer, over a network. PuTTY implements the client end of that session: the end at which the session is displayed, rather than the end at which it runs. +

+

+In really simple terms: you run PuTTY on a Windows machine, and tell it to connect to (for example) a Unix machine. PuTTY opens a window. Then, anything you type into that window is sent straight to the Unix machine, and everything the Unix machine sends back is displayed in the window. So you can work on the Unix machine as if you were sitting at its console, while actually sitting somewhere else. +

+

A.2 Features supported in PuTTY

+

+In general, if you want to know if PuTTY supports a particular feature, you should look for it on the PuTTY web site. In particular: +

+
  • +try the changes page, and see if you can find the feature on there. If a feature is listed there, it's been implemented. If it's listed as a change made since the latest version, it should be available in the development snapshots, in which case testing will be very welcome. +
    • +
  • +try the Wishlist page, and see if you can find the feature there. If it's on there, and not in the ‘Recently fixed’ section, it probably hasn't been implemented. +
    • +
+

A.2.1 Does PuTTY support SSH-2?

+

+Yes. SSH-2 support has been available in PuTTY since version 0.50 in 2000. +

+

+Public key authentication (both RSA and DSA) in SSH-2 was new in version 0.52 in 2002. +

+

A.2.2 Does PuTTY support reading OpenSSH or ssh.com SSH-2 private key files?

+

+PuTTY doesn't support this natively (see the wishlist entry for reasons why not), but as of 0.53 PuTTYgen can convert both OpenSSH and ssh.com private key files into PuTTY's format. +

+

A.2.3 Does PuTTY support SSH-1?

+

+Yes. SSH-1 support has always been available in PuTTY. +

+

+However, the SSH-1 protocol has many weaknesses and is no longer considered secure; you should use SSH-2 instead if at all possible. +

+

+As of 0.68, PuTTY will no longer fall back to SSH-1 if the server doesn't appear to support SSH-2; you must explicitly ask for SSH-1. +

+

A.2.4 Does PuTTY support local echo?

+

+Yes. Version 0.52 has proper support for local echo. +

+

+In version 0.51 and before, local echo could not be separated from local line editing (where you type a line of text locally, and it is not sent to the server until you press Return, so you have the chance to edit it and correct mistakes before the server sees it). New in version 0.52, local echo and local line editing are separate options, and by default PuTTY will try to determine automatically whether to enable them or not, based on which protocol you have selected and also based on hints from the server. If you have a problem with PuTTY's default choice, you can force each option to be enabled or disabled as you choose. The controls are in the Terminal panel, in the section marked ‘Line discipline options’. +

+

A.2.5 Does PuTTY support storing settings, so I don't have to change them every time?

+

+Yes, all of PuTTY's settings can be saved in named session profiles. You can also change the default settings that are used for new sessions. See section 4.1.2 in the documentation for how to do this. +

+

A.2.6 Does PuTTY support storing its settings in a disk file?

+

+Not at present, although section 4.30 in the documentation gives a method of achieving the same effect. +

+

A.2.7 Does PuTTY support full-screen mode, like a DOS box?

+

+Yes; this was added in version 0.52, in 2002. +

+

A.2.8 Does PuTTY have the ability to remember my password so I don't have to type it every time?

+

+No, it doesn't. +

+

+Remembering your password is a bad plan for obvious security reasons: anyone who gains access to your machine while you're away from your desk can find out the remembered password, and use it, abuse it or change it. +

+

+In addition, it's not even possible for PuTTY to automatically send your password in a Telnet session, because Telnet doesn't give the client software any indication of which part of the login process is the password prompt. PuTTY would have to guess, by looking for words like ‘password’ in the session data; and if your login program is written in something other than English, this won't work. +

+

+In SSH, remembering your password would be possible in theory, but there doesn't seem to be much point since SSH supports public key authentication, which is more flexible and more secure. See chapter 8 in the documentation for a full discussion of public key authentication. +

+

A.2.9 Is there an option to turn off the annoying host key prompts?

+

+No, there isn't. And there won't be. Even if you write it yourself and send us the patch, we won't accept it. +

+

+Those annoying host key prompts are the whole point of SSH. Without them, all the cryptographic technology SSH uses to secure your session is doing nothing more than making an attacker's job slightly harder; instead of sitting between you and the server with a packet sniffer, the attacker must actually subvert a router and start modifying the packets going back and forth. But that's not all that much harder than just sniffing; and without host key checking, it will go completely undetected by client or server. +

+

+Host key checking is your guarantee that the encryption you put on your data at the client end is the same encryption taken off the data at the server end; it's your guarantee that it hasn't been removed and replaced somewhere on the way. Host key checking makes the attacker's job astronomically hard, compared to packet sniffing, and even compared to subverting a router. Instead of applying a little intelligence and keeping an eye on Bugtraq, the attacker must now perform a brute-force attack against at least one military-strength cipher. That insignificant host key prompt really does make that much difference. +

+

+If you're having a specific problem with host key checking - perhaps you want an automated batch job to make use of PSCP or Plink, and the interactive host key prompt is hanging the batch process - then the right way to fix it is to add the correct host key to the Registry in advance, or if the Registry is not available, to use the -hostkey command-line option. That way, you retain the important feature of host key checking: the right key will be accepted and the wrong ones will not. Adding an option to turn host key checking off completely is the wrong solution and we will not do it. +

+

+If you have host keys available in the common known_hosts format, we have a script called kh2reg.py to convert them to a Windows .REG file, which can be installed ahead of time by double-clicking or using REGEDIT. +

+

A.2.10 Will you write an SSH server for the PuTTY suite, to go with the client?

+

+Not one that you'd want to use. +

+

+While much of the protocol and networking code can be made common between a client and server, to make a useful general-purpose server requires all sorts of fiddly new code like interacting with OS authentication databases and the like. +

+

+A special-purpose SSH server (called Uppity) can now be built from the PuTTY source code, and indeed it is not usable as a general-purpose server; it exists mainly as a test harness. +

+

+If someone else wants to use this as a basis for writing a general-purpose SSH server, they'd be perfectly welcome to of course; but we don't have time, and we don't have motivation. The code is available if anyone else wants to try it. +

+

A.2.11 Can PSCP or PSFTP transfer files in ASCII mode?

+

+Unfortunately not. +

+

+This was a limitation of the file transfer protocols as originally specified: the SCP and SFTP protocols had no notion of transferring a file in anything other than binary mode. (This is still true of SCP.) +

+

+The current draft protocol spec of SFTP proposes a means of implementing ASCII transfer. At some point PSCP/PSFTP may implement this proposal. +

+

A.3 Ports to other operating systems

+

+The eventual goal is for PuTTY to be a multi-platform program, able to run on at least Windows, Mac OS and Unix. +

+

+PuTTY has been gaining a generalised porting layer, drawing a clear line between platform-dependent and platform-independent code. The general intention was for this porting layer to evolve naturally as part of the process of doing the first port; a Unix port has now been released and the plan seems to be working so far. +

+

A.3.1 What ports of PuTTY exist?

+

+Currently, release versions of PuTTY tools only run on Windows systems and Unix. +

+

+As of 0.68, the supplied PuTTY executables run on versions of Windows from XP onwards, up to and including Windows 10; and we know of no reason why PuTTY should not continue to work on future versions of Windows. We provide 32-bit and 64-bit Windows executables for the common x86 processor family; see question A.6.10 for discussion of the compatibility issues around that. The 32-bit executables require a Pentium 4 or newer processor. We also provide executables for Windows on Arm processors. +

+

+(We used to also provide executables for Windows for the Alpha processor, but stopped after 0.58 due to lack of interest.) +

+

+In the development code, a partial port to Mac OS exists (see question A.3.6). +

+

+Currently PuTTY does not run on Windows CE (see question A.3.4). +

+

+We do not have release-quality ports for any other systems at the present time. If anyone told you we had an Android port, or an iOS port, or any other port of PuTTY, they were mistaken. We don't. +

+

+There are some third-party ports to various platforms, mentioned on the Links page of our website. +

+

A.3.2 Is there a port to Unix?

+

+There are Unix ports of most of the traditional PuTTY tools, and also one entirely new application. +

+

+If you look at the source release, you should find a unix subdirectory. There are a couple of ways of building it, including the usual configure/make; see the file README in the source distribution. This should build you: +

+
  • +Unix ports of PuTTY, Plink, PSCP, and PSFTP, which work pretty much the same as their Windows counterparts; +
    • +
  • +Command-line versions of PuTTYgen and Pageant, whose user interface is quite different to the Windows GUI versions; +
    • +
  • +pterm - an xterm-type program which supports the same terminal emulation as PuTTY. +
    • +
+

+If you don't have Gtk, you should still be able to build the command-line tools. +

+

A.3.3 What's the point of the Unix port? Unix has OpenSSH.

+

+All sorts of little things. pterm is directly useful to anyone who prefers PuTTY's terminal emulation to xterm's, which at least some people do. Unix Plink has apparently found a niche among people who find the complexity of OpenSSL makes OpenSSH hard to install (and who don't mind Plink not having as many features). Some users want to generate a large number of SSH keys on Unix and then copy them all into PuTTY, and the Unix PuTTYgen should allow them to automate that conversion process. +

+

+There were development advantages as well; porting PuTTY to Unix was a valuable path-finding effort for other future ports, and also allowed us to use the excellent Linux tool Valgrind to help with debugging, which has already improved PuTTY's stability on all platforms. +

+

+However, if you're a Unix user and you can see no reason to switch from OpenSSH to PuTTY/Plink, then you're probably right. We don't expect our Unix port to be the right thing for everybody. +

+

A.3.4 Will there be a port to Windows CE or PocketPC?

+

+We once did some work on such a port, but it only reached an early stage, and certainly not a useful one. It's no longer being actively worked on. +

+

A.3.5 Is there a port to Windows 3.1?

+

+PuTTY is a 32-bit application from the ground up, so it won't run on Windows 3.1 as a native 16-bit program; and it would be very hard to port it to do so, because of Windows 3.1's vile memory allocation mechanisms. +

+

+However, it is possible in theory to compile the existing PuTTY source in such a way that it will run under Win32s (an extension to Windows 3.1 to let you run 32-bit programs). In order to do this you'll need the right kind of C compiler - modern versions of Visual C at least have stopped being backwards compatible to Win32s. Also, the last time we tried this it didn't work very well. +

+

A.3.6 Will there be a port to the Mac?

+

+We hope so! +

+

+We attempted one around 2005, written as a native Cocoa application, but it turned out to be very slow to redraw its window for some reason we never got to the bottom of. +

+

+In 2015, after porting the GTK front end to work with GTK 3, we began another attempt based on making small changes to the GTK code and building it against the OS X Quartz version of GTK 3. This doesn't seem to have the window redrawing problem any more, so it's already got further than the last effort, but it is still substantially unfinished. +

+

+If any OS X and/or GTK programming experts are keen to have a finished version of this, we urge them to help out with some of the remaining problems! See the TODO list in unix/gtkapp.c in the source code. +

+

A.3.7 Will there be a port to EPOC?

+

+I hope so, but given that ports aren't really progressing very fast even on systems the developers do already know how to program for, it might be a long time before any of us get round to learning a new system and doing the port for that. +

+

+However, some of the work has been done by other people; see the Links page of our website for various third-party ports. +

+

A.3.8 Will there be a port to the iPhone?

+

+We have no plans to write such a port ourselves; none of us has an iPhone, and developing and publishing applications for it looks awkward and expensive. +

+

+However, there is a third-party SSH client for the iPhone and iPod Touch called pTerm, which is apparently based on PuTTY. (This is nothing to do with our similarly-named pterm, which is a standalone terminal emulator for Unix systems; see question A.3.2.) +

+

A.4 Embedding PuTTY in other programs

+

A.4.1 Is the SSH or Telnet code available as a DLL?

+

+No, it isn't. It would take a reasonable amount of rewriting for this to be possible, and since the PuTTY project itself doesn't believe in DLLs (they make installation more error-prone) none of us has taken the time to do it. +

+

+Most of the code cleanup work would be a good thing to happen in general, so if anyone feels like helping, we wouldn't say no. +

+

+See also the wishlist entry. +

+

A.4.2 Is the SSH or Telnet code available as a Visual Basic component?

+

+No, it isn't. None of the PuTTY team uses Visual Basic, and none of us has any particular need to make SSH connections from a Visual Basic application. In addition, all the preliminary work to turn it into a DLL would be necessary first; and furthermore, we don't even know how to write VB components. +

+

+If someone offers to do some of this work for us, we might consider it, but unless that happens I can't see VB integration being anywhere other than the very bottom of our priority list. +

+

A.4.3 How can I use PuTTY to make an SSH connection from within another program?

+

+Probably your best bet is to use Plink, the command-line connection tool. If you can start Plink as a second Windows process, and arrange for your primary process to be able to send data to the Plink process, and receive data from it, through pipes, then you should be able to make SSH connections from your program. +

+

+This is what CVS for Windows does, for example. +

+

A.5 Details of PuTTY's operation

+

A.5.1 What terminal type does PuTTY use?

+

+For most purposes, PuTTY can be considered to be an xterm terminal. +

+

+PuTTY also supports some terminal control sequences not supported by the real xterm: notably the Linux console sequences that reconfigure the colour palette, and the title bar control sequences used by DECterm (which are different from the xterm ones; PuTTY supports both). +

+

+By default, PuTTY announces its terminal type to the server as xterm. If you have a problem with this, you can reconfigure it to say something else; vt220 might help if you have trouble. +

+

A.5.2 Where does PuTTY store its data?

+

+On Windows, PuTTY stores most of its data (saved sessions, SSH host keys) in the Registry. The precise location is +

+
HKEY_CURRENT_USER\Software\SimonTatham\PuTTY
+
+

+and within that area, saved sessions are stored under Sessions while host keys are stored under SshHostKeys. +

+

+PuTTY also requires a random number seed file, to improve the unpredictability of randomly chosen data needed as part of the SSH cryptography. This is stored by default in a file called PUTTY.RND; this is stored by default in the ‘Application Data’ directory, or failing that, one of a number of fallback locations. If you want to change the location of the random number seed file, you can put your chosen pathname in the Registry, at +

+
HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\RandSeedFile
+
+

+You can ask PuTTY to delete all this data; see question A.8.2. +

+

+On Unix, PuTTY stores all of this data in a directory ~/.putty by default. +

+

A.5.3 Why do small PuTTY icons appear next to the login prompts?

+

+As of PuTTY 0.71, some lines of text in the terminal window are marked with a small copy of the PuTTY icon (as far as pixels allow). +

+

+This is to show trustworthiness. When the PuTTY icon appears next to a line of text, it indicates that that line of text was generated by PuTTY itself, and not generated by the server and sent to PuTTY. +

+

+Text that comes from the server does not have this icon, and we've arranged that the server should not be able to fake it. (There's no control sequence the server can send which will make PuTTY draw its own icon, and if the server tries to move the cursor back up to a line that already has an icon and overwrite the text, the icon will disappear.) +

+

+This lets you tell the difference between (for example) a legitimate prompt in which PuTTY itself asks you for your private key passphrase, and a fake prompt in which the server tries to send the identical text to trick you into telling it your private key passphrase. +

+

A.5.4 Why has Plink started saying ‘Press Return to begin session’?

+

+As of PuTTY 0.71, if you use Plink for an interactive SSH session, then after the login phase has finished, it will present a final interactive prompt saying ‘Access granted. Press Return to begin session’. +

+

+This is another defence against servers trying to mimic the real authentication prompts after the session has started. When you pass through that prompt, you know that everything after it is generated by the server and not by Plink itself, so any request for your private key passphrase should be treated with suspicion. +

+

+In Plink, we can't use the defence described in section A.5.3: Plink is running in the terminal, so anything it can write into the terminal, the server could write in the same way after the session starts. And we can't just print a separator line without a pause, because then the server could simply move the cursor back up to it and overwrite it (probably with a brief flicker, but you might easily miss that). The only robust defence anyone has come up with involves this pause. +

+

+If you trust your server not to be abusive, you can turn this off. It will also not appear in various other circumstances where Plink can be confident it isn't necessary. See section 7.2.3.6 for details. +

+

A.6 HOWTO questions

+

A.6.1 What login name / password should I use?

+

+This is not a question you should be asking us. +

+

+PuTTY is a communications tool, for making connections to other computers. We maintain the tool; we don't administer any computers that you're likely to be able to use, in the same way that the people who make web browsers aren't responsible for most of the content you can view in them. We cannot help with questions of this sort. +

+

+If you know the name of the computer you want to connect to, but don't know what login name or password to use, you should talk to whoever administers that computer. If you don't know who that is, see the next question for some possible ways to find out. +

+

A.6.2 What commands can I type into my PuTTY terminal window?

+

+Again, this is not a question you should be asking us. You need to read the manuals, or ask the administrator, of the computer you have connected to. +

+

+PuTTY does not process the commands you type into it. It's only a communications tool. It makes a connection to another computer; it passes the commands you type to that other computer; and it passes the other computer's responses back to you. Therefore, the precise range of commands you can use will not depend on PuTTY, but on what kind of computer you have connected to and what software is running on it. The PuTTY team cannot help you with that. +

+

+(Think of PuTTY as being a bit like a telephone. If you phone somebody up and you don't know what language to speak to make them understand you, it isn't the telephone company's job to find that out for you. We just provide the means for you to get in touch; making yourself understood is somebody else's problem.) +

+

+If you are unsure of where to start looking for the administrator of your server, a good place to start might be to remember how you found out the host name in the PuTTY configuration. If you were given that host name by e-mail, for example, you could try asking the person who sent you that e-mail. If your company's IT department provided you with ready-made PuTTY saved sessions, then that IT department can probably also tell you something about what commands you can type during those sessions. But the PuTTY maintainer team does not administer any server you are likely to be connecting to, and cannot help you with questions of this type. +

+

A.6.3 How can I make PuTTY start up maximised?

+

+Create a Windows shortcut to start PuTTY from, and set it as ‘Run Maximized’. +

+

A.6.4 How can I create a Windows shortcut to start a particular saved session directly?

+

+To run a PuTTY session saved under the name ‘mysession’, create a Windows shortcut that invokes PuTTY with a command line like +

+
\path\name\to\putty.exe -load "mysession"
+
+

+(Note: prior to 0.53, the syntax was @session. This is now deprecated and may be removed at some point.) +

+

A.6.5 How can I start an SSH session straight from the command line?

+

+Use the command line putty -ssh host.name. Alternatively, create a saved session that specifies the SSH protocol, and start the saved session as shown in question A.6.4. +

+

A.6.6 How do I copy and paste between PuTTY and other Windows applications?

+

+Copy and paste works similarly to the X Window System. You use the left mouse button to select text in the PuTTY window. The act of selection automatically copies the text to the clipboard: there is no need to press Ctrl-Ins or Ctrl-C or anything else. In fact, pressing Ctrl-C will send a Ctrl-C character to the other end of your connection (just like it does the rest of the time), which may have unpleasant effects. The only thing you need to do, to copy text to the clipboard, is to select it. +

+

+To paste the clipboard contents into a PuTTY window, by default you click the right mouse button. If you have a three-button mouse and are used to X applications, you can configure pasting to be done by the middle button instead, but this is not the default because most Windows users don't have a middle button at all. +

+

+You can also paste by pressing Shift-Ins. +

+

A.6.7 How do I use all PuTTY's features (public keys, proxying, cipher selection, etc.) in PSCP, PSFTP and Plink?

+

+Most major features (e.g., public keys, port forwarding) are available through command line options. See the documentation. +

+

+Not all features are accessible from the command line yet, although we'd like to fix this. In the meantime, you can use most of PuTTY's features if you create a PuTTY saved session, and then use the name of the saved session on the command line in place of a hostname. This works for PSCP, PSFTP and Plink (but don't expect port forwarding in the file transfer applications!). +

+

A.6.8 How do I use PSCP.EXE? When I double-click it gives me a command prompt window which then closes instantly.

+

+PSCP is a command-line application, not a GUI application. If you run it without arguments, it will simply print a help message and terminate. +

+

+To use PSCP properly, run it from a Command Prompt window. See chapter 5 in the documentation for more details. +

+

A.6.9 How do I use PSCP to copy a file whose name has spaces in?

+

+If PSCP is using the traditional SCP protocol, this is confusing. If you're specifying a file at the local end, you just use one set of quotes as you would normally do: +

+
pscp "local filename with spaces" user@host:
+pscp user@host:myfile "local filename with spaces"
+
+

+But if the filename you're specifying is on the remote side, you have to use backslashes and two sets of quotes: +

+
pscp user@host:"\"remote filename with spaces\"" local_filename
+pscp local_filename user@host:"\"remote filename with spaces\""
+
+

+Worse still, in a remote-to-local copy you have to specify the local file name explicitly, otherwise PSCP will complain that they don't match (unless you specified the -unsafe option). The following command will give an error message: +

+
c:\>pscp user@host:"\"oo er\"" .
+warning: remote host tried to write to a file called 'oo er'
+         when we requested a file called '"oo er"'.
+
+

+Instead, you need to specify the local file name in full: +

+
c:\>pscp user@host:"\"oo er\"" "oo er"
+
+

+If PSCP is using the newer SFTP protocol, none of this is a problem, and all filenames with spaces in are specified using a single pair of quotes in the obvious way: +

+
pscp "local file" user@host:
+pscp user@host:"remote file" .
+
+

A.6.10 Should I run the 32-bit or the 64-bit version?

+

+If you're not sure, the 32-bit version is generally the safe option. It will run perfectly well on all processors and on all versions of Windows that PuTTY supports. PuTTY doesn't require to run as a 64-bit application to work well, and having a 32-bit PuTTY on a 64-bit system isn't likely to cause you any trouble. +

+

+The 64-bit version (first released in 0.68) will only run if you have a 64-bit processor and a 64-bit edition of Windows (both of these things are likely to be true of any recent Windows PC). It will run somewhat faster (in particular, the cryptography will be faster, especially during link setup), but it will consume slightly more memory. +

+

+If you need to use an external DLL for GSSAPI authentication, that DLL may only be available in a 32-bit or 64-bit form, and that will dictate the version of PuTTY you need to use. (You will probably know if you're doing this; see section 4.24.2 in the documentation.) +

+

A.7 Troubleshooting

+

A.7.1 Why do I see ‘Fatal: Protocol error: Expected control record’ in PSCP?

+

+This happens because PSCP was expecting to see data from the server that was part of the PSCP protocol exchange, and instead it saw data that it couldn't make any sense of at all. +

+

+This almost always happens because the startup scripts in your account on the server machine are generating output. This is impossible for PSCP, or any other SCP client, to work around. You should never use startup files (.bashrc, .cshrc and so on) which generate output in non-interactive sessions. +

+

+This is not actually a PuTTY problem. If PSCP fails in this way, then all other SCP clients are likely to fail in exactly the same way. The problem is at the server end. +

+

A.7.2 I clicked on a colour in the Colours panel, and the colour didn't change in my terminal.

+

+That isn't how you're supposed to use the Colours panel. +

+

+During the course of a session, PuTTY potentially uses all the colours listed in the Colours panel. It's not a question of using only one of them and you choosing which one; PuTTY will use them all. The purpose of the Colours panel is to let you adjust the appearance of all the colours. So to change the colour of the cursor, for example, you would select ‘Cursor Colour’, press the ‘Modify’ button, and select a new colour from the dialog box that appeared. Similarly, if you want your session to appear in green, you should select ‘Default Foreground’ and press ‘Modify’. Clicking on ‘ANSI Green’ won't turn your session green; it will only allow you to adjust the shade of green used when PuTTY is instructed by the server to display green text. +

+

A.7.3 After trying to establish an SSH-2 connection, PuTTY says ‘Out of memory’ and dies.

+

+If this happens just while the connection is starting up, this often indicates that for some reason the client and server have failed to establish a session encryption key. Somehow, they have performed calculations that should have given each of them the same key, but have ended up with different keys; so data encrypted by one and decrypted by the other looks like random garbage. +

+

+This causes an ‘out of memory’ error because the first encrypted data PuTTY expects to see is the length of an SSH message. Normally this will be something well under 100 bytes. If the decryption has failed, PuTTY will see a completely random length in the region of two gigabytes, and will try to allocate enough memory to store this non-existent message. This will immediately lead to it thinking it doesn't have enough memory, and panicking. +

+

+If this happens to you, it is quite likely to still be a PuTTY bug and you should report it (although it might be a bug in your SSH server instead); but it doesn't necessarily mean you've actually run out of memory. +

+

A.7.4 When attempting a file transfer, either PSCP or PSFTP says ‘Out of memory’ and dies.

+

+This is almost always caused by your login scripts on the server generating output. PSCP or PSFTP will receive that output when they were expecting to see the start of a file transfer protocol, and they will attempt to interpret the output as file-transfer protocol. This will usually lead to an ‘out of memory’ error for much the same reasons as given in question A.7.3. +

+

+This is a setup problem in your account on your server, not a PSCP/PSFTP bug. Your login scripts should never generate output during non-interactive sessions; secure file transfer is not the only form of remote access that will break if they do. +

+

+On Unix, a simple fix is to ensure that all the parts of your login script that might generate output are in .profile (if you use a Bourne shell derivative) or .login (if you use a C shell). Putting them in more general files such as .bashrc or .cshrc is liable to lead to problems. +

+

A.7.5 PSFTP transfers files much slower than PSCP.

+

+The throughput of PSFTP 0.54 should be much better than 0.53b and prior; we've added code to the SFTP backend to queue several blocks of data rather than waiting for an acknowledgement for each. (The SCP backend did not suffer from this performance issue because SCP is a much simpler protocol.) +

+

A.7.6 When I run full-colour applications, I see areas of black space where colour ought to be, or vice versa.

+

+You almost certainly need to change the ‘Use background colour to erase screen’ setting in the Terminal panel. If there is too much black space (the commoner situation), you should enable it, while if there is too much colour, you should disable it. (See section 4.3.5.) +

+

+In old versions of PuTTY, this was disabled by default, and would not take effect until you reset the terminal (see question A.7.7). Since 0.54, it is enabled by default, and changes take effect immediately. +

+

A.7.7 When I change some terminal settings, nothing happens.

+

+Some of the terminal options (notably Auto Wrap and background-colour screen erase) actually represent the default setting, rather than the currently active setting. The server can send sequences that modify these options in mid-session, but when the terminal is reset (by server action, or by you choosing ‘Reset Terminal’ from the System menu) the defaults are restored. +

+

+In versions 0.53b and prior, if you change one of these options in the middle of a session, you will find that the change does not immediately take effect. It will only take effect once you reset the terminal. +

+

+In version 0.54, the behaviour has changed - changes to these settings take effect immediately. +

+

A.7.8 My PuTTY sessions unexpectedly close after they are idle for a while.

+

+Some types of firewall, and almost any router doing Network Address Translation (NAT, also known as IP masquerading), will forget about a connection through them if the connection does nothing for too long. This will cause the connection to be rudely cut off when contact is resumed. +

+

+You can try to combat this by telling PuTTY to send keepalives: packets of data which have no effect on the actual session, but which reassure the router or firewall that the network connection is still active and worth remembering about. +

+

+Keepalives don't solve everything, unfortunately; although they cause greater robustness against this sort of router, they can also cause a loss of robustness against network dropouts. See section 4.14.1 in the documentation for more discussion of this. +

+

A.7.9 PuTTY's network connections time out too quickly when network connectivity is temporarily lost.

+

+This is a Windows problem, not a PuTTY problem. The timeout value can't be set on per application or per session basis. To increase the TCP timeout globally, you need to tinker with the Registry. +

+

+On Windows 95, 98 or ME, the registry key you need to create or change is +

+
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\
+  MSTCP\MaxDataRetries
+
+

+(it must be of type DWORD in Win95, or String in Win98/ME). (See MS Knowledge Base article 158474 for more information.) +

+

+On Windows NT, 2000, or XP, the registry key to create or change is +

+
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\
+  Parameters\TcpMaxDataRetransmissions
+
+

+and it must be of type DWORD. (See MS Knowledge Base articles 120642 and 314053 for more information.) +

+

+Set the key's value to something like 10. This will cause Windows to try harder to keep connections alive instead of abandoning them. +

+

A.7.10 When I cat a binary file, I get ‘PuTTYPuTTYPuTTY’ on my command line.

+

+Don't do that, then. +

+

+This is designed behaviour; when PuTTY receives the character Control-E from the remote server, it interprets it as a request to identify itself, and so it sends back the string ‘PuTTY’ as if that string had been entered at the keyboard. Control-E should only be sent by programs that are prepared to deal with the response. Writing a binary file to your terminal is likely to output many Control-E characters, and cause this behaviour. Don't do it. It's a bad plan. +

+

+To mitigate the effects, you could configure the answerback string to be empty (see section 4.3.7); but writing binary files to your terminal is likely to cause various other unpleasant behaviour, so this is only a small remedy. +

+

A.7.11 When I cat a binary file, my window title changes to a nonsense string.

+

+Don't do that, then. +

+

+It is designed behaviour that PuTTY should have the ability to adjust the window title on instructions from the server. Normally the control sequence that does this should only be sent deliberately, by programs that know what they are doing and intend to put meaningful text in the window title. Writing a binary file to your terminal runs the risk of sending the same control sequence by accident, and cause unexpected changes in the window title. Don't do it. +

+

A.7.12 My keyboard stops working once PuTTY displays the password prompt.

+

+No, it doesn't. PuTTY just doesn't display the password you type, so that someone looking at your screen can't see what it is. +

+

+Unlike the Windows login prompts, PuTTY doesn't display the password as a row of asterisks either. This is so that someone looking at your screen can't even tell how long your password is, which might be valuable information. +

+

A.7.13 One or more function keys don't do what I expected in a server-side application.

+

+If you've already tried all the relevant options in the PuTTY Keyboard panel, you may need to mail the PuTTY maintainers and ask. +

+

+It is not usually helpful just to tell us which application, which server operating system, and which key isn't working; in order to replicate the problem we would need to have a copy of every operating system, and every application, that anyone has ever complained about. +

+

+PuTTY responds to function key presses by sending a sequence of control characters to the server. If a function key isn't doing what you expect, it's likely that the character sequence your application is expecting to receive is not the same as the one PuTTY is sending. Therefore what we really need to know is what sequence the application is expecting. +

+

+The simplest way to investigate this is to find some other terminal environment, in which that function key does work; and then investigate what sequence the function key is sending in that situation. One reasonably easy way to do this on a Unix system is to type the command cat, and then press the function key. This is likely to produce output of the form ^[[11~. You can also do this in PuTTY, to find out what sequence the function key is producing in that. Then you can mail the PuTTY maintainers and tell us ‘I wanted the F1 key to send ^[[11~, but instead it's sending ^[OP, can this be done?’, or something similar. +

+

+You should still read the Feedback page on the PuTTY website (also provided as appendix B in the manual), and follow the guidelines contained in that. +

+

A.7.14 Why do I see ‘Couldn't load private key from ...’? Why can PuTTYgen load my key but not PuTTY?

+

+It's likely that you've generated an SSH protocol 2 key with PuTTYgen, but you're trying to use it in an SSH-1 connection. SSH-1 and SSH-2 keys have different formats, and (at least in 0.52) PuTTY's reporting of a key in the wrong format isn't optimal. +

+

+To connect using SSH-2 to a server that supports both versions, you need to change the configuration from the default (see question A.2.1). +

+

A.7.15 When I'm connected to a Red Hat Linux 8.0 system, some characters don't display properly.

+

+A common complaint is that hyphens in man pages show up as a-acute. +

+

+With release 8.0, Red Hat appear to have made UTF-8 the default character set. There appears to be no way for terminal emulators such as PuTTY to know this (as far as we know, the appropriate escape sequence to switch into UTF-8 mode isn't sent). +

+

+A fix is to configure sessions to RH8 systems to use UTF-8 translation - see section 4.10.1 in the documentation. (Note that if you use ‘Change Settings’, changes may not take place immediately - see question A.7.7.) +

+

+If you really want to change the character set used by the server, the right place is /etc/sysconfig/i18n, but this shouldn't be necessary. +

+

A.7.16 Since I upgraded to PuTTY 0.54, the scrollback has stopped working when I run screen.

+

+PuTTY's terminal emulator has always had the policy that when the ‘alternate screen’ is in use, nothing is added to the scrollback. This is because the usual sorts of programs which use the alternate screen are things like text editors, which tend to scroll back and forth in the same document a lot; so (a) they would fill up the scrollback with a large amount of unhelpfully disordered text, and (b) they contain their own method for the user to scroll back to the bit they were interested in. We have generally found this policy to do the Right Thing in almost all situations. +

+

+Unfortunately, screen is one exception: it uses the alternate screen, but it's still usually helpful to have PuTTY's scrollback continue working. The simplest solution is to go to the Features control panel and tick ‘Disable switching to alternate terminal screen’. (See section 4.6.4 for more details.) Alternatively, you can tell screen itself not to use the alternate screen: the screen FAQ suggests adding the line ‘termcapinfo xterm ti@:te@’ to your .screenrc file. +

+

+The reason why this only started to be a problem in 0.54 is because screen typically uses an unusual control sequence to switch to the alternate screen, and previous versions of PuTTY did not support this sequence. +

+

A.7.17 Since I upgraded Windows XP to Service Pack 2, I can't use addresses like 127.0.0.2.

+

+Some people who ask PuTTY to listen on localhost addresses other than 127.0.0.1 to forward services such as SMB and Windows Terminal Services have found that doing so no longer works since they upgraded to WinXP SP2. +

+

+This is apparently an issue with SP2 that is acknowledged by Microsoft in MS Knowledge Base article 884020. The article links to a fix you can download. +

+

+(However, we've been told that SP2 also fixes the bug that means you need to use non-127.0.0.1 addresses to forward Terminal Services in the first place.) +

+

A.7.18 PSFTP commands seem to be missing a directory separator (slash).

+

+Some people have reported the following incorrect behaviour with PSFTP: +

+
psftp> pwd
+Remote directory is /dir1/dir2
+psftp> get filename.ext
+/dir1/dir2filename.ext: no such file or directory
+
+

+This is not a bug in PSFTP. There is a known bug in some versions of portable OpenSSH (bug 697) that causes these symptoms; it appears to have been introduced around 3.7.x. It manifests only on certain platforms (AIX is what has been reported to us). +

+

+There is a patch for OpenSSH attached to that bug; it's also fixed in recent versions of portable OpenSSH (from around 3.8). +

+

A.7.19 Do you want to hear about ‘Software caused connection abort’?

+

+In the documentation for PuTTY 0.53 and 0.53b, we mentioned that we'd like to hear about any occurrences of this error. Since the release of PuTTY 0.54, however, we've been convinced that this error doesn't indicate that PuTTY's doing anything wrong, and we don't need to hear about further occurrences. See section 10.15 for our current documentation of this error. +

+

A.7.20 My SSH-2 session locks up for a few seconds every so often.

+

+Recent versions of PuTTY automatically initiate repeat key exchange once per hour, to improve session security. If your client or server machine is slow, you may experience this as a delay of anything up to thirty seconds or so. +

+

+These delays are inconvenient, but they are there for your protection. If they really cause you a problem, you can choose to turn off periodic rekeying using the ‘Kex’ configuration panel (see section 4.20), but be aware that you will be sacrificing security for this. (Falling back to SSH-1 would also remove the delays, but would lose a lot more security still. We do not recommend it.) +

+

A.7.21 PuTTY fails to start up. Windows claims that ‘the application configuration is incorrect’.

+

+This is caused by a bug in certain versions of Windows XP which is triggered by PuTTY 0.58. This was fixed in 0.59. The ‘xp-wont-run’ entry in PuTTY's wishlist has more details. +

+

A.7.22 When I put 32-bit PuTTY in C:\WINDOWS\SYSTEM32 on my 64-bit Windows system, ‘Duplicate Session’ doesn't work.

+

+The short answer is not to put the PuTTY executables in that location. +

+

+On 64-bit systems, C:\WINDOWS\SYSTEM32 is intended to contain only 64-bit binaries; Windows' 32-bit binaries live in C:\WINDOWS\SYSWOW64. When a 32-bit PuTTY executable runs on a 64-bit system, it cannot by default see the ‘real’ C:\WINDOWS\SYSTEM32 at all, because the File System Redirector arranges that the running program sees the appropriate kind of binaries in SYSTEM32. Thus, operations in the PuTTY suite that involve it accessing its own executables, such as ‘New Session’ and ‘Duplicate Session’, will not work. +

+

A.7.23 After I upgraded PuTTY to 0.68, I can no longer connect to my embedded device or appliance.

+

+If your SSH server has started unexpectedly closing SSH connections after you enter your password, and it worked before 0.68, you may have a buggy server that objects to certain SSH protocol extensions. +

+

+The SSH protocol recently gained a new ‘terminal mode’, IUTF8, which PuTTY sends by default; see section 4.25.2. This is the first new terminal mode since the SSH-2 protocol was defined. While servers are supposed to ignore modes they don't know about, some buggy servers will unceremoniously close the connection if they see anything they don't recognise. SSH servers in embedded devices, network appliances, and the like seem to disproportionately have this bug. +

+

+If you think you have such a server, from 0.69 onwards you can disable sending of the IUTF8 mode: on the SSH / TTY panel, select IUTF8 on the list, select ‘Nothing’, and press ‘Set’. (It's not possible to disable sending this mode in 0.68.) +

+

A.8 Security questions

+

A.8.1 Is it safe for me to download PuTTY and use it on a public PC?

+

+It depends on whether you trust that PC. If you don't trust the public PC, don't use PuTTY on it, and don't use any other software you plan to type passwords into either. It might be watching your keystrokes, or it might tamper with the PuTTY binary you download. There is no program safe enough that you can run it on an actively malicious PC and get away with typing passwords into it. +

+

+If you do trust the PC, then it's probably OK to use PuTTY on it (but if you don't trust the network, then the PuTTY download might be tampered with, so it would be better to carry PuTTY with you on a USB stick). +

+

A.8.2 What does PuTTY leave on a system? How can I clean up after it?

+

+PuTTY will leave some Registry entries, and a random seed file, on the PC (see question A.5.2). Windows 7 and up also remember some information about recently launched sessions for the ‘jump list’ feature. +

+

+If you are using PuTTY on a public PC, or somebody else's PC, you might want to clean this information up when you leave. You can do that automatically, by running the command putty -cleanup. See section 3.8.2 in the documentation for more detail. (Note that this only removes settings for the currently logged-in user on multi-user systems.) +

+

+If PuTTY was installed from the installer package, it will also appear in ‘Add/Remove Programs’. Current versions of the installer do not offer to remove the above-mentioned items, so if you want them removed you should run putty -cleanup before uninstalling. +

+

A.8.3 How come PuTTY now supports DSA, when the website used to say how insecure it was?

+

+DSA has a major weakness if badly implemented: it relies on a random number generator to far too great an extent. If the random number generator produces a number an attacker can predict, the DSA private key is exposed - meaning that the attacker can log in as you on all systems that accept that key. +

+

+The PuTTY policy changed because the developers were informed of ways to implement DSA which do not suffer nearly as badly from this weakness, and indeed which don't need to rely on random numbers at all. For this reason we now believe PuTTY's DSA implementation is probably OK. +

+

+The recently added elliptic-curve signature methods are also DSA-style algorithms, so they have this same weakness in principle. Our ECDSA implementation uses the same defence as DSA, while our Ed25519 implementation uses the similar system (but different in details) that the Ed25519 spec mandates. +

+

A.8.4 Couldn't Pageant use VirtualLock() to stop private keys being written to disk?

+

+Unfortunately not. The VirtualLock() function in the Windows API doesn't do a proper job: it may prevent small pieces of a process's memory from being paged to disk while the process is running, but it doesn't stop the process's memory as a whole from being swapped completely out to disk when the process is long-term inactive. And Pageant spends most of its time inactive. +

+

A.9 Administrative questions

+

A.9.1 Would you like me to register you a nicer domain name?

+

+No, thank you. Even if you can find one (most of them seem to have been registered already, by people who didn't ask whether we actually wanted it before they applied), we're happy with the PuTTY web site being exactly where it is. It's not hard to find (just type ‘putty’ into google.com and we're the first link returned), and we don't believe the administrative hassle of moving the site would be worth the benefit. +

+

+In addition, if we did want a custom domain name, we would want to run it ourselves, so we knew for certain that it would continue to point where we wanted it, and wouldn't suddenly change or do strange things. Having it registered for us by a third party who we don't even know is not the best way to achieve this. +

+

A.9.2 Would you like free web hosting for the PuTTY web site?

+

+We already have some, thanks. +

+

A.9.3 Would you link to my web site from the PuTTY web site?

+

+Only if the content of your web page is of definite direct interest to PuTTY users. If your content is unrelated, or only tangentially related, to PuTTY, then the link would simply be advertising for you. +

+

+One very nice effect of the Google ranking mechanism is that by and large, the most popular web sites get the highest rankings. This means that when an ordinary person does a search, the top item in the search is very likely to be a high-quality site or the site they actually wanted, rather than the site which paid the most money for its ranking. +

+

+The PuTTY web site is held in high esteem by Google, for precisely this reason: lots of people have linked to it simply because they like PuTTY, without us ever having to ask anyone to link to us. We feel that it would be an abuse of this esteem to use it to boost the ranking of random advertisers' web sites. If you want your web site to have a high Google ranking, we'd prefer that you achieve this the way we did - by being good enough at what you do that people will link to you simply because they like you. +

+

+In particular, we aren't interested in trading links for money (see above), and we certainly aren't interested in trading links for other links (since we have no advertising on our web site, our Google ranking is not even directly worth anything to us). If we don't want to link to you for free, then we probably won't want to link to you at all. +

+

+If you have software based on PuTTY, or specifically designed to interoperate with PuTTY, or in some other way of genuine interest to PuTTY users, then we will probably be happy to add a link to you on our Links page. And if you're running a particularly valuable mirror of the PuTTY web site, we might be interested in linking to you from our Mirrors page. +

+

A.9.4 Why don't you move PuTTY to SourceForge?

+

+Partly, because we don't want to move the web site location (see question A.9.1). +

+

+Also, security reasons. PuTTY is a security product, and as such it is particularly important to guard the code and the web site against unauthorised modifications which might introduce subtle security flaws. Therefore, we prefer that the Git repository, web site and FTP site remain where they are, under the direct control of system administrators we know and trust personally, rather than being run by a large organisation full of people we've never met and which is known to have had breakins in the past. +

+

+No offence to SourceForge; I think they do a wonderful job. But they're not ideal for everyone, and in particular they're not ideal for us. +

+

A.9.5 Why can't I subscribe to the putty-bugs mailing list?

+

+Because you're not a member of the PuTTY core development team. The putty-bugs mailing list is not a general newsgroup-like discussion forum; it's a contact address for the core developers, and an internal mailing list for us to discuss things among ourselves. If we opened it up for everybody to subscribe to, it would turn into something more like a newsgroup and we would be completely overwhelmed by the volume of traffic. It's hard enough to keep up with the list as it is. +

+

A.9.6 If putty-bugs isn't a general-subscription mailing list, what is?

+

+There isn't one, that we know of. +

+

+If someone else wants to set up a mailing list or other forum for PuTTY users to help each other with common problems, that would be fine with us, though the PuTTY team would almost certainly not have the time to read it. It's probably better to use one of the established newsgroups for this purpose (see section B.1.2). +

+

A.9.7 How can I donate to PuTTY development?

+

+Please, please don't feel you have to. PuTTY is completely free software, and not shareware. We think it's very important that everybody who wants to use PuTTY should be able to, whether they have any money or not; so the last thing we would want is for a PuTTY user to feel guilty because they haven't paid us any money. If you want to keep your money, please do keep it. We wouldn't dream of asking for any. +

+

+Having said all that, if you still really want to give us money, we won't argue :-) The easiest way for us to accept donations is if you send money to <anakin@pobox.com> using PayPal (www.paypal.com). If you don't like PayPal, talk to us; we can probably arrange some alternative means. +

+

+Small donations (tens of dollars or tens of euros) will probably be spent on beer or curry, which helps motivate our volunteer team to continue doing this for the world. Larger donations will be spent on something that actually helps development, if we can find anything (perhaps new hardware, or a copy of Windows XP), but if we can't find anything then we'll just distribute the money among the developers. If you want to be sure your donation is going towards something worthwhile, ask us first. If you don't like these terms, feel perfectly free not to donate. We don't mind. +

+

A.9.8 Can I have permission to put PuTTY on a cover disk / distribute it with other software / etc?

+

+Yes. For most things, you need not bother asking us explicitly for permission; our licence already grants you permission. +

+

+See section B.8 for more details. +

+

A.9.9 Can you sign an agreement indemnifying us against security problems in PuTTY?

+

+No! +

+

+A vendor of physical security products (e.g. locks) might plausibly be willing to accept financial liability for a product that failed to perform as advertised and resulted in damage (e.g. valuables being stolen). The reason they can afford to do this is because they sell a lot of units, and only a small proportion of them will fail; so they can meet their financial liability out of the income from all the rest of their sales, and still have enough left over to make a profit. Financial liability is intrinsically linked to selling your product for money. +

+

+There are two reasons why PuTTY is not analogous to a physical lock in this context. One is that software products don't exhibit random variation: if PuTTY has a security hole (which does happen, although we do our utmost to prevent it and to respond quickly when it does), every copy of PuTTY will have the same hole, so it's likely to affect all the users at the same time. So even if our users were all paying us to use PuTTY, we wouldn't be able to simultaneously pay every affected user compensation in excess of the amount they had paid us in the first place. It just wouldn't work. +

+

+The second, much more important, reason is that PuTTY users don't pay us. The PuTTY team does not have an income; it's a volunteer effort composed of people spending their spare time to try to write useful software. We aren't even a company or any kind of legally recognised organisation. We're just a bunch of people who happen to do some stuff in our spare time. +

+

+Therefore, to ask us to assume financial liability is to ask us to assume a risk of having to pay it out of our own personal pockets: out of the same budget from which we buy food and clothes and pay our rent. That's more than we're willing to give. We're already giving a lot of our spare time to developing software for free; if we had to pay our own money to do it as well, we'd start to wonder why we were bothering. +

+

+Free software fundamentally does not work on the basis of financial guarantees. Your guarantee of the software functioning correctly is simply that you have the source code and can check it before you use it. If you want to be sure there aren't any security holes, do a security audit of the PuTTY code, or hire a security engineer if you don't have the necessary skills yourself: instead of trying to ensure you can get compensation in the event of a disaster, try to ensure there isn't a disaster in the first place. +

+

+If you really want financial security, see if you can find a security engineer who will take financial responsibility for the correctness of their review. (This might be less likely to suffer from the everything-failing-at-once problem mentioned above, because such an engineer would probably be reviewing a lot of different products which would tend to fail independently.) Failing that, see if you can persuade an insurance company to insure you against security incidents, and if the insurer demands it as a condition then get our code reviewed by a security engineer they're happy with. +

+

A.9.10 Can you sign this form granting us permission to use/distribute PuTTY?

+

+If your form contains any clause along the lines of ‘the undersigned represents and warrants’, we're not going to sign it. This is particularly true if it asks us to warrant that PuTTY is secure; see question A.9.9 for more discussion of this. But it doesn't really matter what we're supposed to be warranting: even if it's something we already believe is true, such as that we don't infringe any third-party copyright, we will not sign a document accepting any legal or financial liability. This is simply because the PuTTY development project has no income out of which to satisfy that liability, or pay legal costs, should it become necessary. We cannot afford to be sued. We are assuring you that we have done our best; if that isn't good enough for you, tough. +

+

+The existing PuTTY licence document already gives you permission to use or distribute PuTTY in pretty much any way which does not involve pretending you wrote it or suing us if it goes wrong. We think that really ought to be enough for anybody. +

+

+See also question A.9.12 for another reason why we don't want to do this sort of thing. +

+

A.9.11 Can you write us a formal notice of permission to use PuTTY?

+

+We could, in principle, but it isn't clear what use it would be. If you think there's a serious chance of one of the PuTTY copyright holders suing you (which we don't!), you would presumably want a signed notice from all of them; and we couldn't provide that even if we wanted to, because many of the copyright holders are people who contributed some code in the past and with whom we subsequently lost contact. Therefore the best we would be able to do even in theory would be to have the core development team sign the document, which wouldn't guarantee you that some other copyright holder might not sue. +

+

+See also question A.9.12 for another reason why we don't want to do this sort of thing. +

+

A.9.12 Can you sign anything for us?

+

+Not unless there's an incredibly good reason. +

+

+We are generally unwilling to set a precedent that involves us having to enter into individual agreements with PuTTY users. We estimate that we have literally millions of users, and we absolutely would not have time to go round signing specific agreements with every one of them. So if you want us to sign something specific for you, you might usefully stop to consider whether there's anything special that distinguishes you from 999,999 other users, and therefore any reason we should be willing to sign something for you without it setting such a precedent. +

+

+If your company policy requires you to have an individual agreement with the supplier of any software you use, then your company policy is simply not well suited to using popular free software, and we urge you to consider this as a flaw in your policy. +

+

A.9.13 If you won't sign anything, can you give us some sort of assurance that you won't make PuTTY closed-source in future?

+

+Yes and no. +

+

+If what you want is an assurance that some current version of PuTTY which you've already downloaded will remain free, then you already have that assurance: it's called the PuTTY Licence. It grants you permission to use, distribute and copy the software to which it applies; once we've granted that permission (which we have), we can't just revoke it. +

+

+On the other hand, if you want an assurance that future versions of PuTTY won't be closed-source, that's more difficult. We could in principle sign a document stating that we would never release a closed-source PuTTY, but that wouldn't assure you that we would keep releasing open-source PuTTYs: we would still have the option of ceasing to develop PuTTY at all, which would surely be even worse for you than making it closed-source! (And we almost certainly wouldn't want to sign a document guaranteeing that we would actually continue to do development work on PuTTY; we certainly wouldn't sign it for free. Documents like that are called contracts of employment, and are generally not signed except in return for a sizeable salary.) +

+

+If we were to stop developing PuTTY, or to decide to make all future releases closed-source, then you would still be free to copy the last open release in accordance with the current licence, and in particular you could start your own fork of the project from that release. If this happened, I confidently predict that somebody would do that, and that some kind of a free PuTTY would continue to be developed. There's already precedent for that sort of thing happening in free software. We can't guarantee that somebody other than you would do it, of course; you might have to do it yourself. But we can assure you that there would be nothing preventing anyone from continuing free development if we stopped. +

+

+(Finally, we can also confidently predict that if we made PuTTY closed-source and someone made an open-source fork, most people would switch to the latter. Therefore, it would be pretty stupid of us to try it.) +

+

A.9.14 Can you provide us with export control information / FIPS certification for PuTTY?

+

+Some people have asked us for an Export Control Classification Number (ECCN) for PuTTY. We don't know whether we have one, and as a team of free software developers based in the UK we don't have the time, money, or effort to deal with US bureaucracy to investigate any further. We believe that PuTTY falls under 5D002 on the US Commerce Control List, but that shouldn't be taken as definitive. If you need to know more you should seek professional legal advice. The same applies to any other country's legal requirements and restrictions. +

+

+Similarly, some people have asked us for FIPS certification of the PuTTY tools. Unless someone else is prepared to do the necessary work and pay any costs, we can't provide this. +

+

A.9.15 As one of our existing software vendors, can you just fill in this questionnaire for us?

+

+We periodically receive requests like this, from organisations which have apparently sent out a form letter to everyone listed in their big spreadsheet of ‘software vendors’ requiring them all to answer some long list of questions about supported OS versions, paid support arrangements, compliance with assorted local regulations we haven't heard of, contact phone numbers, and other such administrivia. Many of the questions are obviously meaningless when applied to PuTTY (we don't provide any paid support in the first place!), most of the rest could have been answered with only a very quick look at our website, and some we are actively unwilling to answer (we are private individuals, why would we want to give out our home phone numbers to large corporations?). +

+

+We don't make a habit of responding in full to these questionnaires, because we are not a software vendor. +

+

+A software vendor is a company to which you are paying lots of money in return for some software. They know who you are, and they know you're paying them money; so they have an incentive to fill in your forms and questionnaires, to research any local regulations you cite if they don't already know about them, and generally to provide every scrap of information you might possibly need in the most convenient manner for you, because they want to keep being paid. +

+

+But we are a team of free software developers, and that means your relationship with us is nothing like that at all. If you once downloaded our software from our website, that's great and we hope you found it useful, but it doesn't mean we have the least idea who you are, or any incentive to do lots of unpaid work to support our ‘relationship’ with you. +

+

+It's not that we are unwilling to provide information. We put as much of it as we can on our website for your convenience, and if you actually need to know some fact about PuTTY which you haven't been able to find on the website (and which is not obviously inapplicable to free software in the first place) then please do ask us, and we'll try to answer as best we can. But we put up the website and this FAQ precisely so that we don't have to keep answering the same questions over and over again, so we aren't prepared to fill in completely generic form-letter questionnaires for people who haven't done their best to find the answers here first. +

+

+If you work for an organisation which you think might be at risk of making this mistake, we urge you to reorganise your list of software suppliers so that it clearly distinguishes paid vendors who know about you from free software developers who don't have any idea who you are. Then, only send out these mass mailings to the former. +

+

A.9.16 The sha1sums / sha256sums / etc files on your download page don't match the binaries.

+

+People report this every so often, and usually the reason turns out to be that they've matched up the wrong checksums file with the wrong binaries. +

+

+The PuTTY download page contains more than one version of the software. There's a latest release version; there are the development snapshots; and when we're in the run-up to making a release, there are also pre-release builds of the upcoming new version. Each one has its own collection of binaries, and its own collection of checksums files to go with them. +

+

+So if you've downloaded the release version of the actual program, you need the release version of the checksums too, otherwise you will see a mismatch. Similarly, the development snapshot binaries go with the development snapshot checksums, and so on. (We've colour-coded the download page in an effort to reduce this confusion a bit.) +

+

+Another thing to watch out for: as of 0.71, executables like putty.exe come in two flavours for each platform: the standalone versions on the website, each of which contains embedded help, and the versions installed by the installer, which use a separate help file also in the installer. We provide checksums for both; the latter are indicated with ‘(installer version)’ after the filename. +

+

+If you have double-checked all that, and you still think there's a real mismatch, then please send us a report carefully quoting everything relevant: +

+
  • +the exact URL you got your binary from +
    • +
  • +the checksum of the binary after you downloaded +
    • +
  • +the exact URL you got your checksums file from +
    • +
  • +the checksum that file says the binary should have. +
    • +
+

A.10 Miscellaneous questions

+

A.10.1 Is PuTTY a port of OpenSSH, or based on OpenSSH or OpenSSL?

+

+No, it isn't. PuTTY is almost completely composed of code written from scratch for PuTTY. The only code we share with OpenSSH is the detector for SSH-1 CRC compensation attacks, written by CORE SDI S.A; we share no code at all with OpenSSL. +

+

A.10.2 Where can I buy silly putty?

+

+You're looking at the wrong web site; the only PuTTY we know about here is the name of a computer program. +

+

+If you want the kind of putty you can buy as an executive toy, the PuTTY team can personally recommend Thinking Putty, which you can buy from Crazy Aaron's Putty World, at www.puttyworld.com. +

+

A.10.3 What does ‘PuTTY’ mean?

+

+It's the name of a popular SSH and Telnet client. Any other meaning is in the eye of the beholder. It's been rumoured that ‘PuTTY’ is the antonym of ‘getty’, or that it's the stuff that makes your Windows useful, or that it's a kind of plutonium Teletype. We couldn't possibly comment on such allegations. +

+

A.10.4 How do I pronounce ‘PuTTY’?

+

+Exactly like the English word ‘putty’, which we pronounce /ˈpʌti/. +

+ +

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/AppendixB.html b/doc/AppendixB.html new file mode 100644 index 0000000..e4bf4a4 --- /dev/null +++ b/doc/AppendixB.html @@ -0,0 +1,273 @@ + + + + +Feedback and bug reporting + + + + + + + +

Previous | Contents | Index | Next

+ + +

Appendix B: Feedback and bug reporting

+

+This is a guide to providing feedback to the PuTTY development team. It is provided as both a web page on the PuTTY site, and an appendix in the PuTTY manual. +

+

+Section B.1 gives some general guidelines for sending any kind of e-mail to the development team. Following sections give more specific guidelines for particular types of e-mail, such as bug reports and feature requests. +

+

B.1 General guidelines

+

+The PuTTY development team gets a lot of mail. If you can possibly solve your own problem by reading the manual, reading the FAQ, reading the web site, asking a fellow user, perhaps posting to a newsgroup (see section B.1.2), or some other means, then it would make our lives much easier. +

+

+We get so much e-mail that we literally do not have time to answer it all. We regret this, but there's nothing we can do about it. So if you can possibly avoid sending mail to the PuTTY team, we recommend you do so. In particular, support requests (section B.6) are probably better sent to newsgroups, or passed to a local expert if possible. +

+

+The PuTTY contact email address is a private mailing list containing four or five core developers. Don't be put off by it being a mailing list: if you need to send confidential data as part of a bug report, you can trust the people on the list to respect that confidence. Also, the archives aren't publicly available, so you shouldn't be letting yourself in for any spam by sending us mail. +

+

+Please use a meaningful subject line on your message. We get a lot of mail, and it's hard to find the message we're looking for if they all have subject lines like ‘PuTTY bug’. +

+

B.1.1 Sending large attachments

+

+Since the PuTTY contact address is a mailing list, e-mails larger than 40Kb will be held for inspection by the list administrator, and will not be allowed through unless they really appear to be worth their large size. +

+

+If you are considering sending any kind of large data file to the PuTTY team, it's almost always a bad idea, or at the very least it would be better to ask us first whether we actually need the file. Alternatively, you could put the file on a web site and just send us the URL; that way, we don't have to download it unless we decide we actually need it, and only one of us needs to download it instead of it being automatically copied to all the developers. +

+

+(If the file contains confidential information, then you could encrypt it with our Secure Contact Key; see section E.1 for details.) +

+

+Some people like to send mail in MS Word format. Please don't send us bug reports, or any other mail, as a Word document. Word documents are roughly fifty times larger than writing the same report in plain text. In addition, most of the PuTTY team read their e-mail on Unix machines, so copying the file to a Windows box to run Word is very inconvenient. Not only that, but several of us don't even have a copy of Word! +

+

+Some people like to send us screen shots when demonstrating a problem. Please don't do this without checking with us first - we almost never actually need the information in the screen shot. Sending a screen shot of an error box is almost certainly unnecessary when you could just tell us in plain text what the error was. (On some versions of Windows, pressing Ctrl-C when the error box is displayed will copy the text of the message to the clipboard.) Sending a full-screen shot is occasionally useful, but it's probably still wise to check whether we need it before sending it. +

+

+If you must mail a screen shot, don't send it as a .BMP file. BMPs have no compression and they are much larger than other image formats such as PNG, TIFF and GIF. Convert the file to a properly compressed image format before sending it. +

+

+Please don't mail us executables, at all. Our mail server blocks all incoming e-mail containing executables, as a defence against the vast numbers of e-mail viruses we receive every day. If you mail us an executable, it will just bounce. +

+

+If you have made a tiny modification to the PuTTY code, please send us a patch to the source code if possible, rather than sending us a huge .ZIP file containing the complete sources plus your modification. If you've only changed 10 lines, we'd prefer to receive a mail that's 30 lines long than one containing multiple megabytes of data we already have. +

+

B.1.2 Other places to ask for help

+

+There are two Usenet newsgroups that are particularly relevant to the PuTTY tools: +

+
  • +comp.security.ssh, for questions specific to using the SSH protocol; +
    • +
  • +comp.terminals, for issues relating to terminal emulation (for instance, keyboard problems). +
    • +
+

+Please use the newsgroup most appropriate to your query, and remember that these are general newsgroups, not specifically about PuTTY. +

+

+If you don't have direct access to Usenet, you can access these newsgroups through Google Groups (groups.google.com). +

+

B.2 Reporting bugs

+

+If you think you have found a bug in PuTTY, your first steps should be: +

+
  • +Check the Wishlist page on the PuTTY website, and see if we already know about the problem. If we do, it is almost certainly not necessary to mail us about it, unless you think you have extra information that might be helpful to us in fixing it. (Of course, if we actually need specific extra information about a particular bug, the Wishlist page will say so.) +
    • +
  • +Check the Change Log on the PuTTY website, and see if we have already fixed the bug in the development snapshots. +
    • +
  • +Check the FAQ on the PuTTY website (also provided as appendix A in the manual), and see if it answers your question. The FAQ lists the most common things which people think are bugs, but which aren't bugs. +
    • +
  • +Download the latest development snapshot and see if the problem still happens with that. This really is worth doing. As a general rule we aren't very interested in bugs that appear in the release version but not in the development version, because that usually means they are bugs we have already fixed. On the other hand, if you can find a bug in the development version that doesn't appear in the release, that's likely to be a new bug we've introduced since the release and we're definitely interested in it. +
    • +
+

+If none of those options solved your problem, and you still need to report a bug to us, it is useful if you include some general information: +

+
  • +Tell us what version of PuTTY you are running. To find this out, use the ‘About PuTTY’ option from the System menu. Please do not just tell us ‘I'm running the latest version’; e-mail can be delayed and it may not be obvious which version was the latest at the time you sent the message. +
    • +
  • +PuTTY is a multi-platform application; tell us what version of what OS you are running PuTTY on. (If you're running on Unix, or Windows for Arm, tell us, or we'll assume you're running on Windows for Intel as this is overwhelmingly the case.) +
    • +
  • +Tell us what protocol you are connecting with: SSH, Telnet, Rlogin, or Raw mode, or a serial connection. +
    • +
  • +Tell us what kind of server you are connecting to; what OS, and if possible what SSH server (if you're using SSH). You can get some of this information from the PuTTY Event Log (see section 3.1.3.1 in the manual). +
    • +
  • +Send us the contents of the PuTTY Event Log, unless you have a specific reason not to (for example, if it contains confidential information that you think we should be able to solve your problem without needing to know). +
    • +
  • +Try to give us as much information as you can to help us see the problem for ourselves. If possible, give us a step-by-step sequence of precise instructions for reproducing the fault. +
    • +
  • +Don't just tell us that PuTTY ‘does the wrong thing’; tell us exactly and precisely what it did, and also tell us exactly and precisely what you think it should have done instead. Some people tell us PuTTY does the wrong thing, and it turns out that it was doing the right thing and their expectations were wrong. Help to avoid this problem by telling us exactly what you think it should have done, and exactly what it did do. +
    • +
  • +If you think you can, you're welcome to try to fix the problem yourself. A patch to the code which fixes a bug is an excellent addition to a bug report. However, a patch is never a substitute for a good bug report; if your patch is wrong or inappropriate, and you haven't supplied us with full information about the actual bug, then we won't be able to find a better solution. +
    • +
  • +https://www.chiark.greenend.org.uk/~sgtatham/bugs.html is an article on how to report bugs effectively in general. If your bug report is particularly unclear, we may ask you to go away, read this article, and then report the bug again. +
    • +
+

+It is reasonable to report bugs in PuTTY's documentation, if you think the documentation is unclear or unhelpful. But we do need to be given exact details of what you think the documentation has failed to tell you, or how you think it could be made clearer. If your problem is simply that you don't understand the documentation, we suggest posting to a newsgroup (see section B.1.2) and seeing if someone will explain what you need to know. Then, if you think the documentation could usefully have told you that, send us a bug report and explain how you think we should change it. +

+

B.3 Reporting security vulnerabilities

+

+If you've found a security vulnerability in PuTTY, you might well want to notify us using an encrypted communications channel, to avoid disclosing information about the vulnerability before a fixed release is available. +

+

+For this purpose, we provide a GPG key suitable for encryption: the Secure Contact Key. See section E.1 for details of this. +

+

+(Of course, vulnerabilities are also bugs, so please do include as much information as possible about them, the same way you would with any other bug report.) +

+

B.4 Requesting extra features

+

+If you want to request a new feature in PuTTY, the very first things you should do are: +

+
  • +Check the Wishlist page on the PuTTY website, and see if your feature is already on the list. If it is, it probably won't achieve very much to repeat the request. (But see section B.5 if you want to persuade us to give your particular feature higher priority.) +
    • +
  • +Check the Wishlist and Change Log on the PuTTY website, and see if we have already added your feature in the development snapshots. If it isn't clear, download the latest development snapshot and see if the feature is present. If it is, then it will also be in the next release and there is no need to mail us at all. +
    • +
+

+If you can't find your feature in either the development snapshots or the Wishlist, then you probably do need to submit a feature request. Since the PuTTY authors are very busy, it helps if you try to do some of the work for us: +

+
  • +Do as much of the design as you can. Think about ‘corner cases’; think about how your feature interacts with other existing features. Think about the user interface; if you can't come up with a simple and intuitive interface to your feature, you shouldn't be surprised if we can't either. Always imagine whether it's possible for there to be more than one, or less than one, of something you'd assumed there would be one of. (For example, if you were to want PuTTY to put an icon in the System tray rather than the Taskbar, you should think about what happens if there's more than one PuTTY active; how would the user tell which was which?) +
    • +
  • +If you can program, it may be worth offering to write the feature yourself and send us a patch. However, it is likely to be helpful if you confer with us first; there may be design issues you haven't thought of, or we may be about to make big changes to the code which your patch would clash with, or something. If you check with the maintainers first, there is a better chance of your code actually being usable. Also, read the design principles listed in appendix D: if you do not conform to them, we will probably not be able to accept your patch. +
    • +
+

B.5 Requesting features that have already been requested

+

+If a feature is already listed on the Wishlist, then it usually means we would like to add it to PuTTY at some point. However, this may not be in the near future. If there's a feature on the Wishlist which you would like to see in the near future, there are several things you can do to try to increase its priority level: +

+
  • +Mail us and vote for it. (Be sure to mention that you've seen it on the Wishlist, or we might think you haven't even read the Wishlist). This probably won't have very much effect; if a huge number of people vote for something then it may make a difference, but one or two extra votes for a particular feature are unlikely to change our priority list immediately. Offering a new and compelling justification might help. Also, don't expect a reply. +
    • +
  • +Offer us money if we do the work sooner rather than later. This sometimes works, but not always. The PuTTY team all have full-time jobs and we're doing all of this work in our free time; we may sometimes be willing to give up some more of our free time in exchange for some money, but if you try to bribe us for a big feature it's entirely possible that we simply won't have the time to spare - whether you pay us or not. (Also, we don't accept bribes to add bad features to the Wishlist, because our desire to provide high-quality software to the users comes first.) +
    • +
  • +Offer to help us write the code. This is probably the only way to get a feature implemented quickly, if it's a big one that we don't have time to do ourselves. +
    • +
+

B.6 Support requests

+

+If you're trying to make PuTTY do something for you and it isn't working, but you're not sure whether it's a bug or not, then please consider looking for help somewhere else. This is one of the most common types of mail the PuTTY team receives, and we simply don't have time to answer all the questions. Questions of this type include: +

+
  • +If you want to do something with PuTTY but have no idea where to start, and reading the manual hasn't helped, try posting to a newsgroup (see section B.1.2) and see if someone can explain it to you. +
    • +
  • +If you have tried to do something with PuTTY but it hasn't worked, and you aren't sure whether it's a bug in PuTTY or a bug in your SSH server or simply that you're not doing it right, then try posting to a newsgroup (see section B.1.2) and see if someone can solve your problem. Or try doing the same thing with a different SSH client and see if it works with that. Please do not report it as a PuTTY bug unless you are really sure it is a bug in PuTTY. +
    • +
  • +If someone else installed PuTTY for you, or you're using PuTTY on someone else's computer, try asking them for help first. They're more likely to understand how they installed it and what they expected you to use it for than we are. +
    • +
  • +If you have successfully made a connection to your server and now need to know what to type at the server's command prompt, or other details of how to use the server-end software, talk to your server's system administrator. This is not the PuTTY team's problem. PuTTY is only a communications tool, like a telephone; if you can't speak the same language as the person at the other end of the phone, it isn't the telephone company's job to teach it to you. +
    • +
+

+If you absolutely cannot get a support question answered any other way, you can try mailing it to us, but we can't guarantee to have time to answer it. +

+

B.7 Web server administration

+

+If the PuTTY web site is down (Connection Timed Out), please don't bother mailing us to tell us about it. Most of us read our e-mail on the same machines that host the web site, so if those machines are down then we will notice before we read our e-mail. So there's no point telling us our servers are down. +

+

+Of course, if the web site has some other error (Connection Refused, 404 Not Found, 403 Forbidden, or something else) then we might not have noticed and it might still be worth telling us about it. +

+

+If you want to report a problem with our web site, check that you're looking at our real web site and not a mirror. The real web site is at https://www.chiark.greenend.org.uk/~sgtatham/putty/; if that's not where you're reading this, then don't report the problem to us until you've checked that it's really a problem with the main site. If it's only a problem with the mirror, you should try to contact the administrator of that mirror site first, and only contact us if that doesn't solve the problem (in case we need to remove the mirror from our list). +

+

B.8 Asking permission for things

+

+PuTTY is distributed under the MIT Licence (see appendix C for details). This means you can do almost anything you like with our software, our source code, and our documentation. The only things you aren't allowed to do are to remove our copyright notices or the licence text itself, or to hold us legally responsible if something goes wrong. +

+

+So if you want permission to include PuTTY on a magazine cover disk, or as part of a collection of useful software on a CD or a web site, then permission is already granted. You don't have to mail us and ask. Just go ahead and do it. We don't mind. +

+

+(If you want to distribute PuTTY alongside your own application for use with that application, or if you want to distribute PuTTY within your own organisation, then we recommend, but do not insist, that you offer your own first-line technical support, to answer questions about the interaction of PuTTY with your environment. If your users mail us directly, we won't be able to tell them anything useful about your specific setup.) +

+

+If you want to use parts of the PuTTY source code in another program, then it might be worth mailing us to talk about technical details, but if all you want is to ask permission then you don't need to bother. You already have permission. +

+

+If you just want to link to our web site, just go ahead. (It's not clear that we could stop you doing this, even if we wanted to!) +

+

B.9 Mirroring the PuTTY web site

+

+If you want to set up a mirror of the PuTTY website, go ahead and set one up. Please don't bother asking us for permission before setting up a mirror. You already have permission. +

+

+If the mirror is in a country where we don't already have plenty of mirrors, we may be willing to add it to the list on our mirrors page. Read the guidelines on that page, make sure your mirror works, and email us the information listed at the bottom of the page. +

+

+Note that we do not promise to list your mirror: we get a lot of mirror notifications and yours may not happen to find its way to the top of the list. +

+

+Also note that we link to all our mirror sites using the rel="nofollow" attribute. Running a PuTTY mirror is not intended to be a cheap way to gain search rankings. +

+

+If you have technical questions about the process of mirroring, then you might want to mail us before setting up the mirror (see also the guidelines on the Mirrors page); but if you just want to ask for permission, you don't need to. You already have permission. +

+

B.10 Praise and compliments

+

+One of the most rewarding things about maintaining free software is getting e-mails that just say ‘thanks’. We are always happy to receive e-mails of this type. +

+

+Regrettably we don't have time to answer them all in person. If you mail us a compliment and don't receive a reply, please don't think we've ignored you. We did receive it and we were happy about it; we just didn't have time to tell you so personally. +

+

+To everyone who's ever sent us praise and compliments, in the past and the future: you're welcome! +

+

B.11 E-mail address

+

+The actual address to mail is <putty@projects.tartarus.org>. +

+ +

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/AppendixC.html b/doc/AppendixC.html new file mode 100644 index 0000000..4ba8239 --- /dev/null +++ b/doc/AppendixC.html @@ -0,0 +1,34 @@ + + + + +PuTTY Licence + + + + + + + +

Previous | Contents | Index | Next

+

Appendix C: PuTTY Licence

+

+PuTTY is copyright 1997-2019 Simon Tatham. +

+

+Portions copyright Robert de Bath, Joris van Rantwijk, Delian Delchev, Andreas Schultz, Jeroen Massar, Wez Furlong, Nicolas Barry, Justin Bradford, Ben Harris, Malcolm Smith, Ahmad Khalifa, Markus Kuhn, Colin Watson, Christopher Staite, Lorenz Diener, Christian Brabandt, Jeff Smith, Pavel Kryukov, Maxim Kuznetsov, Svyatoslav Kuzmich, Nico Williams, Viktor Dukhovni, and CORE SDI S.A. +

+

+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ‘Software’), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: +

+

+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. +

+

+THE SOFTWARE IS PROVIDED ‘AS IS’, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. +

+ +

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/AppendixD.html b/doc/AppendixD.html new file mode 100644 index 0000000..f393b11 --- /dev/null +++ b/doc/AppendixD.html @@ -0,0 +1,264 @@ + + + + +PuTTY hacking guide + + + + + + + +

Previous | Contents | Index | Next

+ + +

Appendix D: PuTTY hacking guide

+

+This appendix lists a selection of the design principles applying to the PuTTY source code. If you are planning to send code contributions, you should read this first. +

+

D.1 Cross-OS portability

+

+Despite Windows being its main area of fame, PuTTY is no longer a Windows-only application suite. It has a working Unix port; a Mac port is in progress; more ports may or may not happen at a later date. +

+

+Therefore, embedding Windows-specific code in core modules such as ssh.c is not acceptable. We went to great lengths to remove all the Windows-specific stuff from our core modules, and to shift it out into Windows-specific modules. Adding large amounts of Windows-specific stuff in parts of the code that should be portable is almost guaranteed to make us reject a contribution. +

+

+The PuTTY source base is divided into platform-specific modules and platform-generic modules. The Unix-specific modules are all in the unix subdirectory; the Windows-specific modules are in the windows subdirectory. +

+

+All the modules in the main source directory - notably all of the code for the various back ends - are platform-generic. We want to keep them that way. +

+

+This also means you should stick to the C semantics guaranteed by the C standard: try not to make assumptions about the precise size of basic types such as int and long int; don't use pointer casts to do endianness-dependent operations, and so on. +

+

+(Even within a platform front end you should still be careful of some of these portability issues. The Windows front end compiles on both 32- and 64-bit x86 and also Arm.) +

+

+Our current choice of C standards version is mostly C99. With a couple of exceptions, you can assume that C99 features are available (in particular <stdint.h>, <stdbool.h> and inline), but you shouldn't use things that are new in C11 (such as <uchar.h> or _Generic). +

+

+The exceptions to that rule are due to the need for Visual Studio compatibility: +

+
  • +Don't use variable-length arrays. Visual Studio doesn't support them even now that it's adopted the rest of C99. We use -Wvla when building with gcc and clang, to make it easier to avoid accidentally breaking that rule. +
    • +
  • +For historical reasons, we still build with one older VS version which lacks <inttypes.h>. So that file is included centrally in defs.h, and has a set of workaround definitions for the PRIx64-type macros we use. If you need to use another one of those macros, you need to add a workaround definition in defs.h, and don't casually re-include <inttypes.h> anywhere else in the source file. +
    • +
+

+Here are a few portability assumptions that we do currently allow (because we'd already have to thoroughly vet the existing code if they ever needed to change, and it doesn't seem worth doing that unless we really have to): +

+
  • +You can assume int is at least 32 bits wide. (We've never tried to port PuTTY to a platform with 16-bit int, and it doesn't look likely to be necessary in future.) +
    • +
  • +Similarly, you can assume char is exactly 8 bits. (Exceptions to that are even less likely to be relevant to us than short int.) +
    • +
  • +You can assume that using memset to write zero bytes over a whole structure will have the effect of setting all its pointer fields to NULL. (The standard itself guarantees this for integer fields, but not for pointers.) +
    • +
  • +You can assume that time_t has POSIX semantics, i.e. that it represents an integer number of non-leap seconds since 1970-01-01 00:00:00 UTC. (Times in this format are used in X authorisation, but we could work around that by carefully distinguishing local time_t from time values used in the wire protocol; but these semantics of time_t are also baked into the shared library API used by the GSSAPI authentication code, which would be much harder to change.) +
    • +
  • +You can assume that the execution character encoding is a superset of the printable characters of ASCII. (In particular, it's fine to do arithmetic on a char value representing a Latin alphabetic character, without bothering to allow for EBCDIC or other non-consecutive encodings of the alphabet.) +
    • +
+

+On the other hand, here are some particular things not to assume: +

+
  • +Don't assume anything about the signedness of char. In particular, you must cast char values to unsigned char before passing them to any <ctype.h> function (because those expect a non-negative character value, or EOF). If you need a particular signedness, explicitly specify signed char or unsigned char, or use C99 int8_t or uint8_t. +
    • +
  • +From past experience with MacOS, we're still a bit nervous about '\n' and '\r' potentially having unusual meanings on a given platform. So it's fine to say \n in a string you're passing to printf, but in any context where those characters appear in a standardised wire protocol or a binary file format, they should be spelled '\012' and '\015' respectively. +
    • +
+

D.2 Multiple backends treated equally

+

+PuTTY is not an SSH client with some other stuff tacked on the side. PuTTY is a generic, multiple-backend, remote VT-terminal client which happens to support one backend which is larger, more popular and more useful than the rest. Any extra feature which can possibly be general across all backends should be so: localising features unnecessarily into the SSH back end is a design error. (For example, we had several code submissions for proxy support which worked by hacking ssh.c. Clearly this is completely wrong: the network.h abstraction is the place to put it, so that it will apply to all back ends equally, and indeed we eventually put it there after another contributor sent a better patch.) +

+

+The rest of PuTTY should try to avoid knowing anything about specific back ends if at all possible. To support a feature which is only available in one network protocol, for example, the back end interface should be extended in a general manner such that any back end which is able to provide that feature can do so. If it so happens that only one back end actually does, that's just the way it is, but it shouldn't be relied upon by any code. +

+

D.3 Multiple sessions per process on some platforms

+

+Some ports of PuTTY - notably the in-progress Mac port - are constrained by the operating system to run as a single process potentially managing multiple sessions. +

+

+Therefore, the platform-independent parts of PuTTY never use global variables to store per-session data. The global variables that do exist are tolerated because they are not specific to a particular login session: flags defines properties that are expected to apply equally to all the sessions run by a single PuTTY process, the random number state in sshrand.c and the timer list in timing.c serve all sessions equally, and so on. But most data is specific to a particular network session, and is therefore stored in dynamically allocated data structures, and pointers to these structures are passed around between functions. +

+

+Platform-specific code can reverse this decision if it likes. The Windows code, for historical reasons, stores most of its data as global variables. That's OK, because on Windows we know there is only one session per PuTTY process, so it's safe to do that. But changes to the platform-independent code should avoid introducing global variables, unless they are genuinely cross-session. +

+

D.4 C, not C++

+

+PuTTY is written entirely in C, not in C++. +

+

+We have made some effort to make it easy to compile our code using a C++ compiler: notably, our snew, snewn and sresize macros explicitly cast the return values of malloc and realloc to the target type. (This has type checking advantages even in C: it means you never accidentally allocate the wrong size piece of memory for the pointer type you're assigning it to. C++ friendliness is really a side benefit.) +

+

+We want PuTTY to continue being pure C, at least in the platform-independent parts and the currently existing ports. Patches which switch the Makefiles to compile it as C++ and start using classes will not be accepted. Also, in particular, we disapprove of // comments, at least for the moment. (Perhaps once C99 becomes genuinely widespread we might be more lenient.) +

+

+The one exception: a port to a new platform may use languages other than C if they are necessary to code on that platform. If your favourite PDA has a GUI with a C++ API, then there's no way you can do a port of PuTTY without using C++, so go ahead and use it. But keep the C++ restricted to that platform's subdirectory; if your changes force the Unix or Windows ports to be compiled as C++, they will be unacceptable to us. +

+

D.5 Security-conscious coding

+

+PuTTY is a network application and a security application. Assume your code will end up being fed deliberately malicious data by attackers, and try to code in a way that makes it unlikely to be a security risk. +

+

+In particular, try not to use fixed-size buffers for variable-size data such as strings received from the network (or even the user). We provide functions such as dupcat and dupprintf, which dynamically allocate buffers of the right size for the string they construct. Use these wherever possible. +

+

D.6 Independence of specific compiler

+

+Windows PuTTY can currently be compiled with any of three Windows compilers: MS Visual C, the Cygwin / mingw32 GNU tools, and clang (in MS compatibility mode). +

+

+This is a really useful property of PuTTY, because it means people who want to contribute to the coding don't depend on having a specific compiler; so they don't have to fork out money for MSVC if they don't already have it, but on the other hand if they do have it they also don't have to spend effort installing gcc alongside it. They can use whichever compiler they happen to have available, or install whichever is cheapest and easiest if they don't have one. +

+

+Therefore, we don't want PuTTY to start depending on which compiler you're using. Using GNU extensions to the C language, for example, would ruin this useful property (not that anyone's ever tried it!); and more realistically, depending on an MS-specific library function supplied by the MSVC C library (_snprintf, for example) is a mistake, because that function won't be available under the other compilers. Any function supplied in an official Windows DLL as part of the Windows API is fine, and anything defined in the C library standard is also fine, because those should be available irrespective of compilation environment. But things in between, available as non-standard library and language extensions in only one compiler, are disallowed. +

+

+(_snprintf in particular should be unnecessary, since we provide dupprintf; see section D.5.) +

+

+Compiler independence should apply on all platforms, of course, not just on Windows. +

+

D.7 Small code size

+

+PuTTY is tiny, compared to many other Windows applications. And it's easy to install: it depends on no DLLs, no other applications, no service packs or system upgrades. It's just one executable. You install that executable wherever you want to, and run it. +

+

+We want to keep both these properties - the small size, and the ease of installation - if at all possible. So code contributions that depend critically on external DLLs, or that add a huge amount to the code size for a feature which is only useful to a small minority of users, are likely to be thrown out immediately. +

+

+We do vaguely intend to introduce a DLL plugin interface for PuTTY, whereby seriously large extra features can be implemented in plugin modules. The important thing, though, is that those DLLs will be optional; if PuTTY can't find them on startup, it should run perfectly happily and just won't provide those particular features. A full installation of PuTTY might one day contain ten or twenty little DLL plugins, which would cut down a little on the ease of installation - but if you really needed ease of installation you could still just install the one PuTTY binary, or just the DLLs you really needed, and it would still work fine. +

+

+Depending on external DLLs is something we'd like to avoid if at all possible (though for some purposes, such as complex SSH authentication mechanisms, it may be unavoidable). If it can't be avoided, the important thing is to follow the same principle of graceful degradation: if a DLL can't be found, then PuTTY should run happily and just not supply the feature that depended on it. +

+

D.8 Single-threaded code

+

+PuTTY and its supporting tools, or at least the vast majority of them, run in only one OS thread. +

+

+This means that if you're devising some piece of internal mechanism, there's no need to use locks to make sure it doesn't get called by two threads at once. The only way code can be called re-entrantly is by recursion. +

+

+That said, most of Windows PuTTY's network handling is triggered off Windows messages requested by WSAAsyncSelect(), so if you call MessageBox() deep within some network event handling code you should be aware that you might be re-entered if a network event comes in and is passed on to our window procedure by the MessageBox() message loop. +

+

+Also, the front ends (in particular Windows Plink) can use multiple threads if they like. However, Windows Plink keeps very tight control of its auxiliary threads, and uses them pretty much exclusively as a form of select(). Pretty much all the code outside windows/winplink.c is only ever called from the one primary thread; the others just loop round blocking on file handles and send messages to the main thread when some real work needs doing. This is not considered a portability hazard because that bit of windows/winplink.c will need rewriting on other platforms in any case. +

+

+One important consequence of this: PuTTY has only one thread in which to do everything. That ‘everything’ may include managing more than one login session (section D.3), managing multiple data channels within an SSH session, responding to GUI events even when nothing is happening on the network, and responding to network requests from the server (such as repeat key exchange) even when the program is dealing with complex user interaction such as the re-configuration dialog box. This means that almost none of the PuTTY code can safely block. +

+

D.9 Keystrokes sent to the server wherever possible

+

+In almost all cases, PuTTY sends keystrokes to the server. Even weird keystrokes that you think should be hot keys controlling PuTTY. Even Alt-F4 or Alt-Space, for example. If a keystroke has a well-defined escape sequence that it could usefully be sending to the server, then it should do so, or at the very least it should be configurably able to do so. +

+

+To unconditionally turn a key combination into a hot key to control PuTTY is almost always a design error. If a hot key is really truly required, then try to find a key combination for it which isn't already used in existing PuTTYs (either it sends nothing to the server, or it sends the same thing as some other combination). Even then, be prepared for the possibility that one day that key combination might end up being needed to send something to the server - so make sure that there's an alternative way to invoke whatever PuTTY feature it controls. +

+

D.10 640×480 friendliness in configuration panels

+

+There's a reason we have lots of tiny configuration panels instead of a few huge ones, and that reason is that not everyone has a 1600×1200 desktop. 640×480 is still a viable resolution for running Windows (and indeed it's still the default if you start up in safe mode), so it's still a resolution we care about. +

+

+Accordingly, the PuTTY configuration box, and the PuTTYgen control window, are deliberately kept just small enough to fit comfortably on a 640×480 display. If you're adding controls to either of these boxes and you find yourself wanting to increase the size of the whole box, don't. Split it into more panels instead. +

+

D.11 Automatically generated Makefiles

+

+PuTTY is intended to compile on multiple platforms, and with multiple compilers. It would be horrifying to try to maintain a single Makefile which handled all possible situations, and just as painful to try to directly maintain a set of matching Makefiles for each different compilation environment. +

+

+Therefore, we have moved the problem up by one level. In the PuTTY source archive is a file called Recipe, which lists which source files combine to produce which binaries; and there is also a script called mkfiles.pl, which reads Recipe and writes out the real Makefiles. (The script also reads all the source files and analyses their dependencies on header files, so we get an extra benefit from doing it this way, which is that we can supply correct dependency information even in environments where it's difficult to set up an automated make depend phase.) +

+

+You should never edit any of the PuTTY Makefiles directly. They are not stored in our source repository at all. They are automatically generated by mkfiles.pl from the file Recipe. +

+

+If you need to add a new object file to a particular binary, the right thing to do is to edit Recipe and re-run mkfiles.pl. This will cause the new object file to be added in every tool that requires it, on every platform where it matters, in every Makefile to which it is relevant, and to get all the dependency data right. +

+

+If you send us a patch that modifies one of the Makefiles, you just waste our time, because we will have to convert it into a change to Recipe. If you send us a patch that modifies all of the Makefiles, you will have wasted a lot of your time as well! +

+

+(There is a comment at the top of every Makefile in the PuTTY source archive saying this, but many people don't seem to read it, so it's worth repeating here.) +

+

D.12 Coroutines in the SSH code

+

+Large parts of the code in the various SSH modules (in fact most of the protocol layers) are structured using a set of macros that implement (something close to) Donald Knuth's ‘coroutines’ concept in C. +

+

+Essentially, the purpose of these macros are to arrange that a function can call crReturn() to return to its caller, and the next time it is called control will resume from just after that crReturn statement. +

+

+This means that any local (automatic) variables declared in such a function will be corrupted every time you call crReturn. If you need a variable to persist for longer than that, you must make it a field in some appropriate structure containing the persistent state of the coroutine – typically the main state structure for an SSH protocol layer. +

+

+See https://www.chiark.greenend.org.uk/~sgtatham/coroutines.html for a more in-depth discussion of what these macros are for and how they work. +

+

+Another caveat: most of these coroutines are not guaranteed to run to completion, because the SSH connection (or whatever) that they're part of might be interrupted at any time by an unexpected network event or user action. So whenever a coroutine-managed variable refers to a resource that needs releasing, you should also ensure that the cleanup function for its containing state structure can reliably release it even if the coroutine is aborted at an arbitrary point. +

+

+For example, if an SSH packet protocol layer has to have a field that sometimes points to a piece of allocated memory, then you should ensure that when you free that memory you reset the pointer field to NULL. Then, no matter when the protocol layer's cleanup function is called, it can reliably free the memory if there is any, and not crash if there isn't. +

+

D.13 Single compilation of each source file

+

+The PuTTY build system for any given platform works on the following very simple model: +

+
  • +Each source file is compiled precisely once, to produce a single object file. +
    • +
  • +Each binary is created by linking together some combination of those object files. +
    • +
+

+Therefore, if you need to introduce functionality to a particular module which is only available in some of the tool binaries (for example, a cryptographic proxy authentication mechanism which needs to be left out of PuTTYtel to maintain its usability in crypto-hostile jurisdictions), the wrong way to do it is by adding #ifdefs in (say) proxy.c. This would require separate compilation of proxy.c for PuTTY and PuTTYtel, which means that the entire Makefile-generation architecture (see section D.11) would have to be significantly redesigned. Unless you are prepared to do that redesign yourself, and guarantee that it will still port to any future platforms we might decide to run on, you should not attempt this! +

+

+The right way to introduce a feature like this is to put the new code in a separate source file, and (if necessary) introduce a second new source file defining the same set of functions, but defining them as stubs which don't provide the feature. Then the module whose behaviour needs to vary (proxy.c in this example) can call the functions defined in these two modules, and it will either provide the new feature or not provide it according to which of your new modules it is linked with. +

+

+Of course, object files are never shared between platforms; so it is allowable to use #ifdef to select between platforms. This happens in puttyps.h (choosing which of the platform-specific include files to use), and also in misc.c (the Windows-specific ‘Minefield’ memory diagnostic system). It should be used sparingly, though, if at all. +

+

D.14 Do as we say, not as we do

+

+The current PuTTY code probably does not conform strictly to all of the principles listed above. There may be the occasional SSH-specific piece of code in what should be a backend-independent module, or the occasional dependence on a non-standard X library function under Unix. +

+

+This should not be taken as a licence to go ahead and violate the rules. Where we violate them ourselves, we're not happy about it, and we would welcome patches that fix any existing problems. Please try to help us make our code better, not worse! +

+ +

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/AppendixE.html b/doc/AppendixE.html new file mode 100644 index 0000000..4ab6a8c --- /dev/null +++ b/doc/AppendixE.html @@ -0,0 +1,255 @@ + + + + +PuTTY download keys and signatures + + + + + + + +

Previous | Contents | Index | Next

+ + +

Appendix E: PuTTY download keys and signatures

+

+We create GPG signatures for all the PuTTY files distributed from our web site, so that users can be confident that the files have not been tampered with. Here we identify our public keys, and explain our signature policy so you can have an accurate idea of what each signature guarantees. This description is provided as both a web page on the PuTTY site, and an appendix in the PuTTY manual. +

+

+As of release 0.58, all of the PuTTY executables contain fingerprint material (usually accessed via the -pgpfp command-line option), such that if you have an executable you trust, you can use it to establish a trust path, for instance to a newer version downloaded from the Internet. +

+

+As of release 0.67, the Windows executables and installer also contain built-in signatures that are automatically verified by Windows' own mechanism (‘Authenticode’). The keys used for that are different, and are not covered here. +

+

+(Note that none of the keys, signatures, etc mentioned here have anything to do with keys used with SSH - they are purely for verifying the origin of files distributed by the PuTTY team.) +

+

E.1 Public keys

+

+We maintain multiple keys, stored with different levels of security due to being used in different ways. See section E.2 below for details. +

+

+The keys we provide are: +

+
+Snapshot Key +
+
+Used to sign routine development builds of PuTTY: nightly snapshots, pre-releases, and sometimes also custom diagnostic builds we send to particular users. +
+
+Release Key +
+
+Used to sign manually released versions of PuTTY. +
+
+Secure Contact Key +
+
+An encryption-capable key suitable for people to send confidential messages to the PuTTY team, e.g. reports of vulnerabilities. +
+
+Master Key +
+
+Used to tie all the above keys into the GPG web of trust. The Master Key signs all the other keys, and other GPG users have signed it in turn. +
+
+

+The current issue of those keys are available for download from the PuTTY website, and are also available on PGP keyservers using the key IDs listed below. +

+
+Master Key (2018) +
+
+RSA, 4096-bit. Key ID: 76BC7FE4EBFD2D9E. Fingerprint: 24E1 B1C5 75EA 3C9F F752  A922 76BC 7FE4 EBFD 2D9E +
+
+Release Key (2018) +
+
+RSA, 3072-bit. Key ID: 6289A25F4AE8DA82. Fingerprint: E273 94AC A3F9 D904 9522  E054 6289 A25F 4AE8 DA82 +
+
+Snapshot Key (2018) +
+
+RSA, 3072-bit. Key ID: 38BA7229B7588FD1. Fingerprint: C92B 52E9 9AB6 1DDA 33DB  2B7A 38BA 7229 B758 8FD1 +
+
+Secure Contact Key (2018) +
+
+RSA, 3072-bit. Key ID: 657D487977F95C98. Fingerprint: A680 0082 2998 6E46 22CA  0E43 657D 4879 77F9 5C98 +
+
+

E.2 Security details

+

+The various keys have various different security levels. This section explains what those security levels are, and how far you can expect to trust each key. +

+

E.2.1 The Development Snapshots key

+

+The Development Snapshots private key is stored without a passphrase. This is necessary, because the snapshots are generated every night without human intervention, so nobody would be able to type a passphrase. +

+

+The snapshots are built and signed on a team member's home computers, before being uploaded to the web server from which you download them. +

+

+Therefore, a signature from the Development Snapshots key DOES protect you against: +

+
  • +People tampering with the PuTTY binaries between the PuTTY web site and you. +
    • +
  • +The maintainers of our web server attempting to abuse their root privilege to tamper with the binaries. +
    • +
+

+But it DOES NOT protect you against: +

+
  • +People tampering with the binaries before they are uploaded to our download servers. +
    • +
  • +People tampering with the build machines so that the next set of binaries they build will be malicious in some way. +
    • +
  • +People stealing the unencrypted private key from the build machine it lives on. +
    • +
+

+Of course, we take all reasonable precautions to guard the build machines. But when you see a signature, you should always be certain of precisely what it guarantees and precisely what it does not. +

+

E.2.2 The Releases key

+

+The Releases key is more secure: because it is only used at release time, to sign each release by hand, we can store it encrypted. +

+

+The Releases private key is kept encrypted on the developers' own local machines. So an attacker wanting to steal it would have to also steal the passphrase. +

+

E.2.3 The Secure Contact Key

+

+The Secure Contact Key is stored with a similar level of security to the Release Key: it is stored with a passphrase, and no automated script has access to it. +

+

E.2.4 The Master Keys

+

+The Master Key signs almost nothing. Its purpose is to bind the other keys together and certify that they are all owned by the same people and part of the same integrated setup. The only signatures produced by the Master Key, ever, should be the signatures on the other keys. +

+

+The Master Key is especially long, and its private key and passphrase are stored with special care. +

+

+We have collected some third-party signatures on the Master Key, in order to increase the chances that you can find a suitable trust path to them. +

+

+We have uploaded our various keys to public keyservers, so that even if you don't know any of the people who have signed our keys, you can still be reasonably confident that an attacker would find it hard to substitute fake keys on all the public keyservers at once. +

+

E.3 Key rollover

+

+Our current keys were generated in August 2018. +

+

+Each new Master Key is signed with the old one, to show that it really is owned by the same people and not substituted by an attacker. +

+

+Each new Master Key also signs the previous Release Keys, in case you're trying to verify the signatures on a release prior to the rollover and can find a chain of trust to those keys from any of the people who have signed our new Master Key. +

+

+Each release is signed with the Release Key that was current at the time of release. We don't go back and re-sign old releases with newly generated keys. +

+

+The details of all previous keys are given here. +

+

+Key generated in 2016 (when we first introduced the Secure Contact Key) +

+
+Secure Contact Key (2016) +
+
+RSA, 2048-bit. Main key ID: 2048R/8A0AF00B (long version: 2048R/C4FCAAD08A0AF00B). Encryption subkey ID: 2048R/50C2CF5C (long version: 2048R/9EB39CC150C2CF5C). Fingerprint: 8A26 250E 763F E359 75F3  118F C4FC AAD0 8A0A F00B +
+
+

+Keys generated in the 2015 rollover +

+
+Master Key (2015) +
+
+RSA, 4096-bit. Key ID: 4096R/04676F7C (long version: 4096R/AB585DC604676F7C). Fingerprint: 440D E3B5 B7A1 CA85 B3CC  1718 AB58 5DC6 0467 6F7C +
+
+Release Key (2015) +
+
+RSA, 2048-bit. Key ID: 2048R/B43434E4 (long version: 2048R/9DFE2648B43434E4). Fingerprint: 0054 DDAA 8ADA 15D2 768A  6DE7 9DFE 2648 B434 34E4 +
+
+Snapshot Key (2015) +
+
+RSA, 2048-bit. Key ID: 2048R/D15F7E8A (long version: 2048R/EEF20295D15F7E8A). Fingerprint: 0A3B 0048 FE49 9B67 A234  FEB6 EEF2 0295 D15F 7E8A +
+
+

+Original keys generated in 2000 (two sets, RSA and DSA) +

+
+Master Key (original RSA) +
+
+RSA, 1024-bit. Key ID: 1024R/1E34AC41 (long version: 1024R/9D5877BF1E34AC41). Fingerprint: 8F 15 97 DA 25 30 AB 0D  88 D1 92 54 11 CF 0C 4C +
+
+Master Key (original DSA) +
+
+DSA, 1024-bit. Key ID: 1024D/6A93B34E (long version: 1024D/4F5E6DF56A93B34E). Fingerprint: 313C 3E76 4B74 C2C5 F2AE  83A8 4F5E 6DF5 6A93 B34E +
+
+Release Key (original RSA) +
+
+RSA, 1024-bit. Key ID: 1024R/B41CAE29 (long version: 1024R/EF39CCC0B41CAE29). Fingerprint: AE 65 D3 F7 85 D3 18 E0  3B 0C 9B 02 FF 3A 81 FE +
+
+Release Key (original DSA) +
+
+DSA, 1024-bit. Key ID: 1024D/08B0A90B (long version: 1024D/FECD6F3F08B0A90B). Fingerprint: 00B1 1009 38E6 9800 6518  F0AB FECD 6F3F 08B0 A90B +
+
+Snapshot Key (original RSA) +
+
+RSA, 1024-bit. Key ID: 1024R/32B903A9 (long version: 1024R/FAAED21532B903A9). Fingerprint: 86 8B 1F 79 9C F4 7F BD  8B 1B D7 8E C6 4E 4C 03 +
+
+Snapshot Key (original DSA) +
+
+DSA, 1024-bit. Key ID: 1024D/7D3E4A00 (long version: 1024D/165E56F77D3E4A00). Fingerprint: 63DD 8EF8 32F5 D777 9FF0  2947 165E 56F7 7D3E 4A00 +
+
+ +

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/AppendixF.html b/doc/AppendixF.html new file mode 100644 index 0000000..02b0119 --- /dev/null +++ b/doc/AppendixF.html @@ -0,0 +1,101 @@ + + + + +SSH-2 names specified for PuTTY + + + + + + + +

Previous | Contents | Index | Next

+ + +

Appendix F: SSH-2 names specified for PuTTY

+

+There are various parts of the SSH-2 protocol where things are specified using a textual name. Names ending in @putty.projects.tartarus.org are reserved for allocation by the PuTTY team. Allocated names are documented here. +

+

F.1 Connection protocol channel request names

+

+These names can be sent in a SSH_MSG_CHANNEL_REQUEST message. +

+
+simple@putty.projects.tartarus.org +
+
+This is sent by a client to announce that it will not have more than one channel open at a time in the current connection (that one being the one the request is sent on). The intention is that the server, knowing this, can set the window on that one channel to something very large, and leave flow control to TCP. There is no message-specific data. +
+
+winadj@putty.projects.tartarus.org +
+
+PuTTY sends this request along with some SSH_MSG_CHANNEL_WINDOW_ADJUST messages as part of its window-size tuning. It can be sent on any type of channel. There is no message-specific data. Servers MUST treat it as an unrecognised request and respond with SSH_MSG_CHANNEL_FAILURE. +

+(Some SSH servers get confused by this message, so there is a bug-compatibility mode for disabling it. See section 4.28.3.) +

+ +
+
+

F.2 Key exchange method names

+
+rsa-sha1-draft-00@putty.projects.tartarus.org +
+
+rsa-sha256-draft-00@putty.projects.tartarus.org +
+
+rsa1024-sha1-draft-01@putty.projects.tartarus.org +
+
+rsa1024-sha256-draft-01@putty.projects.tartarus.org +
+
+rsa2048-sha256-draft-01@putty.projects.tartarus.org +
+
+rsa1024-sha1-draft-02@putty.projects.tartarus.org +
+
+rsa2048-sha512-draft-02@putty.projects.tartarus.org +
+
+rsa1024-sha1-draft-03@putty.projects.tartarus.org +
+
+rsa2048-sha256-draft-03@putty.projects.tartarus.org +
+
+rsa1024-sha1-draft-04@putty.projects.tartarus.org +
+
+rsa2048-sha256-draft-04@putty.projects.tartarus.org +
+
+These appeared in various drafts of what eventually became RFC 4432. They have been superseded by rsa1024-sha1 and rsa2048-sha256. +
+
+

F.3 Encryption algorithm names

+
+arcfour128-draft-00@putty.projects.tartarus.org +
+
+arcfour256-draft-00@putty.projects.tartarus.org +
+
+These were used in drafts of what eventually became RFC 4345. They have been superseded by arcfour128 and arcfour256. +
+
+ +

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/Chapter1.html b/doc/Chapter1.html new file mode 100644 index 0000000..81eb532 --- /dev/null +++ b/doc/Chapter1.html @@ -0,0 +1,89 @@ + + + + +Introduction to PuTTY + + + + + + + +

Previous | Contents | Index | Next

+ + +

Chapter 1: Introduction to PuTTY

+

+PuTTY is a free SSH, Telnet and Rlogin client for Windows systems. +

+

1.1 What are SSH, Telnet and Rlogin?

+

+If you already know what SSH, Telnet and Rlogin are, you can safely skip on to the next section. +

+

+SSH, Telnet and Rlogin are three ways of doing the same thing: logging in to a multi-user computer from another computer, over a network. +

+

+Multi-user operating systems, such as Unix and VMS, usually present a command-line interface to the user, much like the ‘Command Prompt’ or ‘MS-DOS Prompt’ in Windows. The system prints a prompt, and you type commands which the system will obey. +

+

+Using this type of interface, there is no need for you to be sitting at the same machine you are typing commands to. The commands, and responses, can be sent over a network, so you can sit at one computer and give commands to another one, or even to more than one. +

+

+SSH, Telnet and Rlogin are network protocols that allow you to do this. On the computer you sit at, you run a client, which makes a network connection to the other computer (the server). The network connection carries your keystrokes and commands from the client to the server, and carries the server's responses back to you. +

+

+These protocols can also be used for other types of keyboard-based interactive session. In particular, there are a lot of bulletin boards, talker systems and MUDs (Multi-User Dungeons) which support access using Telnet. There are even a few that support SSH. +

+

+You might want to use SSH, Telnet or Rlogin if: +

+
  • +you have an account on a Unix or VMS system which you want to be able to access from somewhere else +
    • +
  • +your Internet Service Provider provides you with a login account on a web server. (This might also be known as a shell account. A shell is the program that runs on the server and interprets your commands for you.) +
    • +
  • +you want to use a bulletin board system, talker or MUD which can be accessed using Telnet. +
    • +
+

+You probably do not want to use SSH, Telnet or Rlogin if: +

+
  • +you only use Windows. Windows computers have their own ways of networking between themselves, and unless you are doing something fairly unusual, you will not need to use any of these remote login protocols. +
    • +
+

1.2 How do SSH, Telnet and Rlogin differ?

+

+This list summarises some of the differences between SSH, Telnet and Rlogin. +

+
  • +SSH (which stands for ‘secure shell’) is a recently designed, high-security protocol. It uses strong cryptography to protect your connection against eavesdropping, hijacking and other attacks. Telnet and Rlogin are both older protocols offering minimal security. +
    • +
  • +SSH and Rlogin both allow you to log in to the server without having to type a password. (Rlogin's method of doing this is insecure, and can allow an attacker to access your account on the server. SSH's method is much more secure, and typically breaking the security requires the attacker to have gained access to your actual client machine.) +
    • +
  • +SSH allows you to connect to the server and automatically send a command, so that the server will run that command and then disconnect. So you can use it in automated processing. +
    • +
+

+The Internet is a hostile environment and security is everybody's responsibility. If you are connecting across the open Internet, then we recommend you use SSH. If the server you want to connect to doesn't support SSH, it might be worth trying to persuade the administrator to install it. +

+

+If your client and server are both behind the same (good) firewall, it is more likely to be safe to use Telnet or Rlogin, but we still recommend you use SSH. +

+ +

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/Chapter10.html b/doc/Chapter10.html new file mode 100644 index 0000000..c36e4e5 --- /dev/null +++ b/doc/Chapter10.html @@ -0,0 +1,249 @@ + + + + +Common error messages + + + + + + + +

Previous | Contents | Index | Next

+ + +

Chapter 10: Common error messages

+

+This chapter lists a number of common error messages which PuTTY and its associated tools can produce, and explains what they mean in more detail. +

+

+We do not attempt to list all error messages here: there are many which should never occur, and some which should be self-explanatory. If you get an error message which is not listed in this chapter and which you don't understand, report it to us as a bug (see appendix B) and we will add documentation for it. +

+

10.1 ‘The server's host key is not cached in the registry’

+

+This error message occurs when PuTTY connects to a new SSH server. Every server identifies itself by means of a host key; once PuTTY knows the host key for a server, it will be able to detect if a malicious attacker redirects your connection to another machine. +

+

+If you see this message, it means that PuTTY has not seen this host key before, and has no way of knowing whether it is correct or not. You should attempt to verify the host key by other means, such as asking the machine's administrator. +

+

+If you see this message and you know that your installation of PuTTY has connected to the same server before, it may have been recently upgraded to SSH protocol version 2. SSH protocols 1 and 2 use separate host keys, so when you first use SSH-2 with a server you have only used SSH-1 with before, you will see this message again. You should verify the correctness of the key as before. +

+

+See section 2.2 for more information on host keys. +

+

10.2 ‘WARNING - POTENTIAL SECURITY BREACH!’

+

+This message, followed by ‘The server's host key does not match the one PuTTY has cached in the registry’, means that PuTTY has connected to the SSH server before, knows what its host key should be, but has found a different one. +

+

+This may mean that a malicious attacker has replaced your server with a different one, or has redirected your network connection to their own machine. On the other hand, it may simply mean that the administrator of your server has accidentally changed the key while upgrading the SSH software; this shouldn't happen but it is unfortunately possible. +

+

+You should contact your server's administrator and see whether they expect the host key to have changed. If so, verify the new host key in the same way as you would if it was new. +

+

+See section 2.2 for more information on host keys. +

+

10.3 ‘SSH protocol version 2 required by our configuration but remote only provides (old, insecure) SSH-1’

+

+By default, PuTTY only supports connecting to SSH servers that implement SSH protocol version 2. If you see this message, the server you're trying to connect to only supports the older SSH-1 protocol. +

+

+If the server genuinely only supports SSH-1, then you need to either change the ‘SSH protocol version’ setting (see section 4.19.4), or use the -1 command-line option; in any case, you should not treat the resulting connection as secure. +

+

+You might start seeing this message with new versions of PuTTY (from 0.68 onwards) where you didn't before, because it used to be possible to configure PuTTY to automatically fall back from SSH-2 to SSH-1. This is no longer supported, to prevent the possibility of a downgrade attack. +

+

10.4 ‘The first cipher supported by the server is ... below the configured warning threshold’

+

+This occurs when the SSH server does not offer any ciphers which you have configured PuTTY to consider strong enough. By default, PuTTY puts up this warning only for Blowfish, single-DES, and Arcfour encryption. +

+

+See section 4.22 for more information on this message. +

+

+(There are similar messages for other cryptographic primitives, such as host key algorithms.) +

+

10.5 ‘Remote side sent disconnect message type 2 (protocol error): "Too many authentication failures for root"’

+

+This message is produced by an OpenSSH (or Sun SSH) server if it receives more failed authentication attempts than it is willing to tolerate. +

+

+This can easily happen if you are using Pageant and have a large number of keys loaded into it, since these servers count each offer of a public key as an authentication attempt. This can be worked around by specifying the key that's required for the authentication in the PuTTY configuration (see section 4.23.8); PuTTY will ignore any other keys Pageant may have, but will ask Pageant to do the authentication, so that you don't have to type your passphrase. +

+

+On the server, this can be worked around by disabling public-key authentication or (for Sun SSH only) by increasing MaxAuthTries in sshd_config. +

+

10.6 ‘Out of memory’

+

+This occurs when PuTTY tries to allocate more memory than the system can give it. This may happen for genuine reasons: if the computer really has run out of memory, or if you have configured an extremely large number of lines of scrollback in your terminal. PuTTY is not able to recover from running out of memory; it will terminate immediately after giving this error. +

+

+However, this error can also occur when memory is not running out at all, because PuTTY receives data in the wrong format. In SSH-2 and also in SFTP, the server sends the length of each message before the message itself; so PuTTY will receive the length, try to allocate space for the message, and then receive the rest of the message. If the length PuTTY receives is garbage, it will try to allocate a ridiculous amount of memory, and will terminate with an ‘Out of memory’ error. +

+

+This can happen in SSH-2, if PuTTY and the server have not enabled encryption in the same way (see question A.7.3 in the FAQ). +

+

+This can also happen in PSCP or PSFTP, if your login scripts on the server generate output: the client program will be expecting an SFTP message starting with a length, and if it receives some text from your login scripts instead it will try to interpret them as a message length. See question A.7.4 for details of this. +

+

10.7 ‘Internal error’, ‘Internal fault’, ‘Assertion failed’

+

+Any error beginning with the word ‘Internal’ should never occur. If it does, there is a bug in PuTTY by definition; please see appendix B and report it to us. +

+

+Similarly, any error message starting with ‘Assertion failed’ is a bug in PuTTY. Please report it to us, and include the exact text from the error message box. +

+

10.8 ‘Unable to use key file’, ‘Couldn't load private key’, ‘Couldn't load this key’

+

+Various forms of this error are printed in the PuTTY window, or written to the PuTTY Event Log (see section 3.1.3.1) when trying public-key authentication, or given by Pageant when trying to load a private key. +

+

+If you see one of these messages, it often indicates that you've tried to load a key of an inappropriate type into PuTTY, Plink, PSCP, PSFTP, or Pageant. +

+

+You may have tried to load an SSH-2 key in a ‘foreign’ format (OpenSSH or ssh.com) directly into one of the PuTTY tools, in which case you need to import it into PuTTY's native format (*.PPK) using PuTTYgen – see section 8.2.12. +

+

+Alternatively, you may have specified a key that's inappropriate for the connection you're making. The SSH-2 and the old SSH-1 protocols require different private key formats, and a SSH-1 key can't be used for a SSH-2 connection (or vice versa). +

+

10.9 ‘Server refused our key’, ‘Server refused our public key’, ‘Key refused’

+

+Various forms of this error are printed in the PuTTY window, or written to the PuTTY Event Log (see section 3.1.3.1) when trying public-key authentication. +

+

+If you see one of these messages, it means that PuTTY has sent a public key to the server and offered to authenticate with it, and the server has refused to accept authentication. This usually means that the server is not configured to accept this key to authenticate this user. +

+

+This is almost certainly not a problem with PuTTY. If you see this type of message, the first thing you should do is check your server configuration carefully. Common errors include having the wrong permissions or ownership set on the public key or the user's home directory on the server. Also, read the PuTTY Event Log; the server may have sent diagnostic messages explaining exactly what problem it had with your setup. +

+

+Section 8.3 has some hints on server-side public key setup. +

+

10.10 ‘Access denied’, ‘Authentication refused’

+

+Various forms of this error are printed in the PuTTY window, or written to the PuTTY Event Log (see section 3.1.3.1) during authentication. +

+

+If you see one of these messages, it means that the server has refused all the forms of authentication PuTTY has tried and it has no further ideas. +

+

+It may be worth checking the Event Log for diagnostic messages from the server giving more detail. +

+

+This error can be caused by buggy SSH-1 servers that fail to cope with the various strategies we use for camouflaging passwords in transit. Upgrade your server, or use the workarounds described in section 4.28.11 and possibly section 4.28.12. +

+

10.11 ‘No supported authentication methods available’

+

+This error indicates that PuTTY has run out of ways to authenticate you to an SSH server. This may be because PuTTY has TIS or keyboard-interactive authentication disabled, in which case see section 4.23.4 and section 4.23.5. +

+

10.12 ‘Incorrect MAC received on packet’ or ‘Incorrect CRC received on packet’

+

+This error occurs when PuTTY decrypts an SSH packet and its checksum is not correct. This probably means something has gone wrong in the encryption or decryption process. It's difficult to tell from this error message whether the problem is in the client, in the server, or in between. +

+

+In particular, if the network is corrupting data at the TCP level, it may only be obvious with cryptographic protocols such as SSH, which explicitly check the integrity of the transferred data and complain loudly if the checks fail. Corruption of protocols without integrity protection (such as HTTP) will manifest in more subtle failures (such as misdisplayed text or images in a web browser) which may not be noticed. +

+

+Occasionally this has been caused by server bugs. An example is the bug described at section 4.28.8, although you're very unlikely to encounter that one these days. +

+

+In this context MAC stands for Message Authentication Code. It's a cryptographic term, and it has nothing at all to do with Ethernet MAC (Media Access Control) addresses, or with the Apple computer. +

+

10.13 ‘Incoming packet was garbled on decryption’

+

+This error occurs when PuTTY decrypts an SSH packet and the decrypted data makes no sense. This probably means something has gone wrong in the encryption or decryption process. It's difficult to tell from this error message whether the problem is in the client, in the server, or in between. +

+

+If you get this error, one thing you could try would be to fiddle with the setting of ‘Miscomputes SSH-2 encryption keys’ (see section 4.28.10) or ‘Ignores SSH-2 maximum packet size’ (see section 4.28.5) on the Bugs panel. +

+

10.14 ‘PuTTY X11 proxy: various errors’

+

+This family of errors are reported when PuTTY is doing X forwarding. They are sent back to the X application running on the SSH server, which will usually report the error to the user. +

+

+When PuTTY enables X forwarding (see section 3.4) it creates a virtual X display running on the SSH server. This display requires authentication to connect to it (this is how PuTTY prevents other users on your server machine from connecting through the PuTTY proxy to your real X display). PuTTY also sends the server the details it needs to enable clients to connect, and the server should put this mechanism in place automatically, so your X applications should just work. +

+

+A common reason why people see one of these messages is because they used SSH to log in as one user (let's say ‘fred’), and then used the Unix su command to become another user (typically ‘root’). The original user, ‘fred’, has access to the X authentication data provided by the SSH server, and can run X applications which are forwarded over the SSH connection. However, the second user (‘root’) does not automatically have the authentication data passed on to it, so attempting to run an X application as that user often fails with this error. +

+

+If this happens, it is not a problem with PuTTY. You need to arrange for your X authentication data to be passed from the user you logged in as to the user you used su to become. How you do this depends on your particular system; in fact many modern versions of su do it automatically. +

+

10.15 ‘Network error: Software caused connection abort’

+

+This is a generic error produced by the Windows network code when it kills an established connection for some reason. For example, it might happen if you pull the network cable out of the back of an Ethernet-connected computer, or if Windows has any other similar reason to believe the entire network has become unreachable. +

+

+Windows also generates this error if it has given up on the machine at the other end of the connection ever responding to it. If the network between your client and server goes down and your client then tries to send some data, Windows will make several attempts to send the data and will then give up and kill the connection. In particular, this can occur even if you didn't type anything, if you are using SSH-2 and PuTTY attempts a key re-exchange. (See section 4.20.2 for more about key re-exchange.) +

+

+(It can also occur if you are using keepalives in your connection. Other people have reported that keepalives fix this error for them. See section 4.14.1 for a discussion of the pros and cons of keepalives.) +

+

+We are not aware of any reason why this error might occur that would represent a bug in PuTTY. The problem is between you, your Windows system, your network and the remote system. +

+

10.16 ‘Network error: Connection reset by peer’

+

+This error occurs when the machines at each end of a network connection lose track of the state of the connection between them. For example, you might see it if your SSH server crashes, and manages to reboot fully before you next attempt to send data to it. +

+

+However, the most common reason to see this message is if you are connecting through a firewall or a NAT router which has timed the connection out. See question A.7.8 in the FAQ for more details. You may be able to improve the situation by using keepalives; see section 4.14.1 for details on this. +

+

+Note that Windows can produce this error in some circumstances without seeing a connection reset from the server, for instance if the connection to the network is lost. +

+

10.17 ‘Network error: Connection refused’

+

+This error means that the network connection PuTTY tried to make to your server was rejected by the server. Usually this happens because the server does not provide the service which PuTTY is trying to access. +

+

+Check that you are connecting with the correct protocol (SSH, Telnet or Rlogin), and check that the port number is correct. If that fails, consult the administrator of your server. +

+

10.18 ‘Network error: Connection timed out’

+

+This error means that the network connection PuTTY tried to make to your server received no response at all from the server. Usually this happens because the server machine is completely isolated from the network, or because it is turned off. +

+

+Check that you have correctly entered the host name or IP address of your server machine. If that fails, consult the administrator of your server. +

+

+Unix also generates this error when it tries to send data down a connection and contact with the server has been completely lost during a connection. (There is a delay of minutes before Unix gives up on receiving a reply from the server.) This can occur if you type things into PuTTY while the network is down, but it can also occur if PuTTY decides of its own accord to send data: due to a repeat key exchange in SSH-2 (see section 4.20.2) or due to keepalives (section 4.14.1). +

+

10.19 ‘Network error: Cannot assign requested address’

+

+This means that the operating system rejected the parameters of the network connection PuTTY tried to make, usually without actually trying to connect to anything, because they were simply invalid. +

+

+A common way to provoke this error is to accidentally try to connect to port 0, which is not a valid port number. +

+ +

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/Chapter2.html b/doc/Chapter2.html new file mode 100644 index 0000000..8cff7c7 --- /dev/null +++ b/doc/Chapter2.html @@ -0,0 +1,119 @@ + + + + +Getting started with PuTTY + + + + + + + +

Previous | Contents | Index | Next

+ + +

Chapter 2: Getting started with PuTTY

+

+This chapter gives a quick guide to the simplest types of interactive login session using PuTTY. +

+

2.1 Starting a session

+

+When you start PuTTY, you will see a dialog box. This dialog box allows you to control everything PuTTY can do. See chapter 4 for details of all the things you can control. +

+

+You don't usually need to change most of the configuration options. To start the simplest kind of session, all you need to do is to enter a few basic parameters. +

+

+In the ‘Host Name’ box, enter the Internet host name of the server you want to connect to. You should have been told this by the provider of your login account. +

+

+Now select a login protocol to use, from the ‘Connection type’ buttons. For a login session, you should select Telnet, Rlogin or SSH. See section 1.2 for a description of the differences between the three protocols, and advice on which one to use. The fourth protocol, Raw, is not used for interactive login sessions; you would usually use this for debugging other Internet services (see section 3.6). The fifth option, Serial, is used for connecting to a local serial line, and works somewhat differently: see section 3.7 for more information on this. +

+

+When you change the selected protocol, the number in the ‘Port’ box will change. This is normal: it happens because the various login services are usually provided on different network ports by the server machine. Most servers will use the standard port numbers, so you will not need to change the port setting. If your server provides login services on a non-standard port, your system administrator should have told you which one. (For example, many MUDs run Telnet service on a port other than 23.) +

+

+Once you have filled in the ‘Host Name’, ‘Protocol’, and possibly ‘Port’ settings, you are ready to connect. Press the ‘Open’ button at the bottom of the dialog box, and PuTTY will begin trying to connect you to the server. +

+

2.2 Verifying the host key (SSH only)

+

+If you are not using the SSH protocol, you can skip this section. +

+

+If you are using SSH to connect to a server for the first time, you will probably see a message looking something like this: +

+
The server's host key is not cached in the registry. You
+have no guarantee that the server is the computer you
+think it is.
+The server's rsa2 key fingerprint is:
+ssh-rsa 1024 7b:e5:6f:a7:f4:f9:81:62:5c:e3:1f:bf:8b:57:6c:5a
+If you trust this host, hit Yes to add the key to
+PuTTY's cache and carry on connecting.
+If you want to carry on connecting just once, without
+adding the key to the cache, hit No.
+If you do not trust this host, hit Cancel to abandon the
+connection.
+
+

+This is a feature of the SSH protocol. It is designed to protect you against a network attack known as spoofing: secretly redirecting your connection to a different computer, so that you send your password to the wrong machine. Using this technique, an attacker would be able to learn the password that guards your login account, and could then log in as if they were you and use the account for their own purposes. +

+

+To prevent this attack, each server has a unique identifying code, called a host key. These keys are created in a way that prevents one server from forging another server's key. So if you connect to a server and it sends you a different host key from the one you were expecting, PuTTY can warn you that the server may have been switched and that a spoofing attack might be in progress. +

+

+PuTTY records the host key for each server you connect to, in the Windows Registry. Every time you connect to a server, it checks that the host key presented by the server is the same host key as it was the last time you connected. If it is not, you will see a warning, and you will have the chance to abandon your connection before you type any private information (such as a password) into it. +

+

+However, when you connect to a server you have not connected to before, PuTTY has no way of telling whether the host key is the right one or not. So it gives the warning shown above, and asks you whether you want to trust this host key or not. +

+

+Whether or not to trust the host key is your choice. If you are connecting within a company network, you might feel that all the network users are on the same side and spoofing attacks are unlikely, so you might choose to trust the key without checking it. If you are connecting across a hostile network (such as the Internet), you should check with your system administrator, perhaps by telephone or in person. (Many servers have more than one host key. If the system administrator sends you more than one fingerprint, you should make sure the one PuTTY shows you is on the list, but it doesn't matter which one it is.) +

+

+See section 4.21 for advanced options for managing host keys. +

+

2.3 Logging in

+

+After you have connected, and perhaps verified the server's host key, you will be asked to log in, probably using a username and a password. Your system administrator should have provided you with these. (If, instead, your system administrator has asked you to provide, or provided you with, a ‘public key’ or ‘key file’, see chapter 8.) +

+

+PuTTY will display a text window (the ‘terminal window’ – it will have a black background unless you've changed the defaults), and prompt you to type your username and password into that window. (These prompts will include the PuTTY icon, to distinguish them from any text sent by the server in the same window.) +

+

+Enter the username and the password, and the server should grant you access and begin your session. If you have mistyped your password, most servers will give you several chances to get it right. +

+

+While you are typing your password, you will not usually see the cursor moving in the window, but PuTTY is registering what you type, and will send it when you press Return. (It works this way to avoid revealing the length of your password to anyone watching your screen.) +

+

+If you are using SSH, be careful not to type your username wrongly, because you will not have a chance to correct it after you press Return; many SSH servers do not permit you to make two login attempts using different usernames. If you type your username wrongly, you must close PuTTY and start again. +

+

+If your password is refused but you are sure you have typed it correctly, check that Caps Lock is not enabled. Many login servers, particularly Unix computers, treat upper case and lower case as different when checking your password; so if Caps Lock is on, your password will probably be refused. +

+

2.4 After logging in

+

+After you log in to the server, what happens next is up to the server! Most servers will print some sort of login message and then present a prompt, at which you can type commands which the server will carry out. Some servers will offer you on-line help; others might not. If you are in doubt about what to do next, consult your system administrator. +

+

2.5 Logging out

+

+When you have finished your session, you should log out by typing the server's own logout command. This might vary between servers; if in doubt, try logout or exit, or consult a manual or your system administrator. When the server processes your logout command, the PuTTY window should close itself automatically. +

+

+You can close a PuTTY session using the Close button in the window border, but this might confuse the server - a bit like hanging up a telephone unexpectedly in the middle of a conversation. We recommend you do not do this unless the server has stopped responding to you and you cannot close the window any other way. +

+ +

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/Chapter3.html b/doc/Chapter3.html new file mode 100644 index 0000000..855e24c --- /dev/null +++ b/doc/Chapter3.html @@ -0,0 +1,734 @@ + + + + +Using PuTTY + + + + + + + +

Previous | Contents | Index | Next

+ + +

Chapter 3: Using PuTTY

+

+This chapter provides a general introduction to some more advanced features of PuTTY. For extreme detail and reference purposes, chapter 4 is likely to contain more information. +

+

3.1 During your session

+

+A lot of PuTTY's complexity and features are in the configuration panel. Once you have worked your way through that and started a session, things should be reasonably simple after that. Nevertheless, there are a few more useful features available. +

+

3.1.1 Copying and pasting text

+

+Often in a PuTTY session you will find text on your terminal screen which you want to type in again. Like most other terminal emulators, PuTTY allows you to copy and paste the text rather than having to type it again. Also, copy and paste uses the Windows clipboard, so that you can paste (for example) URLs into a web browser, or paste from a word processor or spreadsheet into your terminal session. +

+

+By default, PuTTY's copy and paste works entirely with the mouse. (This will be familiar to people who have used xterm on Unix.) In order to copy text to the clipboard, you just click the left mouse button in the terminal window, and drag to select text. When you let go of the button, the text is automatically copied to the clipboard. You do not need to press Ctrl-C or Ctrl-Ins; in fact, if you do press Ctrl-C, PuTTY will send a Ctrl-C character down your session to the server where it will probably cause a process to be interrupted. +

+

+Pasting into PuTTY is done using the right button (or the middle mouse button, if you have a three-button mouse and have set it up; see section 4.11.1). (Pressing Shift-Ins, or selecting ‘Paste’ from the Ctrl+right-click context menu, have the same effect.) When you click the right mouse button, PuTTY will read whatever is in the Windows clipboard and paste it into your session. By default, this behaves exactly as if the clipboard contents had been typed at the keyboard; therefore, be careful of pasting formatted text into an editor that does automatic indenting, as you may find that the spaces pasted from the clipboard plus the spaces added by the editor add up to too many spaces and ruin the formatting. (Some remote applications can ask PuTTY to identify text that is being pasted, to avoid this sort of problem; but if your application does not, there is nothing PuTTY can do to avoid this.) +

+

+If you double-click the left mouse button, PuTTY will select a whole word. If you double-click, hold down the second click, and drag the mouse, PuTTY will select a sequence of whole words. (You can adjust precisely what PuTTY considers to be part of a word; see section 4.12.1.) If you triple-click, or triple-click and drag, then PuTTY will select a whole line or sequence of lines. +

+

+If you want to select a rectangular region instead of selecting to the end of each line, you can do this by holding down Alt when you make your selection. You can also configure rectangular selection to be the default, and then holding down Alt gives the normal behaviour instead: see section 4.11.3 for details. +

+

+(In some Unix environments, Alt+drag is intercepted by the window manager. Shift+Alt+drag should work for rectangular selection as well, so you could try that instead.) +

+

+If you have a middle mouse button, then you can use it to adjust an existing selection if you selected something slightly wrong. (If you have configured the middle mouse button to paste, then the right mouse button does this instead.) Click the button on the screen, and you can pick up the nearest end of the selection and drag it to somewhere else. +

+

+If you are running PuTTY itself on Unix (not just using it to connect to a Unix system from Windows), by default you will likely have to use similar mouse actions in other applications to paste the text you copied from PuTTY, and to copy text for pasting into PuTTY; actions like Ctrl-C and Ctrl-V will likely not behave as you expect. Section 4.11.4 explains why this is, and how you can change the behaviour. (On Windows there is only a single selection shared with other applications, so this confusion does not arise.) +

+

+It's possible for the server to ask to handle mouse clicks in the PuTTY window itself. If this happens, the mouse pointer will turn into an arrow, and using the mouse to copy and paste will only work if you hold down Shift. See section 4.6.2 and section 4.11.2 for details of this feature and how to configure it. +

+

+You can customise much of this behaviour, for instance to enable copy and paste from the keyboard; see section 4.11. +

+

3.1.2 Scrolling the screen back

+

+PuTTY keeps track of text that has scrolled up off the top of the terminal. So if something appears on the screen that you want to read, but it scrolls too fast and it's gone by the time you try to look for it, you can use the scrollbar on the right side of the window to look back up the session history and find it again. +

+

+As well as using the scrollbar, you can also page the scrollback up and down by pressing Shift-PgUp and Shift-PgDn. You can scroll a line at a time using Ctrl-PgUp and Ctrl-PgDn, or to the top/bottom of the scrollback with Ctrl-Shift-PgUp and Ctrl-Shift-PgDn. These are still available if you configure the scrollbar to be invisible. +

+

+By default the last 2000 lines scrolled off the top are preserved for you to look at. You can increase (or decrease) this value using the configuration box; see section 4.7.3. +

+

3.1.3 The System menu

+

+If you click the left mouse button on the icon in the top left corner of PuTTY's terminal window, or click the right mouse button on the title bar, you will see the standard Windows system menu containing items like Minimise, Move, Size and Close. +

+

+PuTTY's system menu contains extra program features in addition to the Windows standard options. These extra menu commands are described below. +

+

+(These options are also available in a context menu brought up by holding Ctrl and clicking with the right mouse button anywhere in the PuTTY window.) +

+

3.1.3.1 The PuTTY Event Log

+

+If you choose ‘Event Log’ from the system menu, a small window will pop up in which PuTTY logs significant events during the connection. Most of the events in the log will probably take place during session startup, but a few can occur at any point in the session, and one or two occur right at the end. +

+

+You can use the mouse to select one or more lines of the Event Log, and hit the Copy button to copy them to the clipboard. If you are reporting a bug, it's often useful to paste the contents of the Event Log into your bug report. +

+

+(The Event Log is not the same as the facility to create a log file of your session; that's described in section 3.2.) +

+

3.1.3.2 Special commands

+

+Depending on the protocol used for the current session, there may be a submenu of ‘special commands’. These are protocol-specific tokens, such as a ‘break’ signal, that can be sent down a connection in addition to normal data. Their precise effect is usually up to the server. Currently only Telnet, SSH, and serial connections have special commands. +

+

+The ‘break’ signal can also be invoked from the keyboard with Ctrl-Break. +

+

+In an SSH connection, the following special commands are available: +

+
  • +IGNORE message +

    +Should have no effect. +

    + +
    • +
  • +Repeat key exchange +

    +Only available in SSH-2. Forces a repeat key exchange immediately (and resets associated timers and counters). For more information about repeat key exchanges, see section 4.20.2. +

    + +
    • +
  • +Cache new host key type +

    +Only available in SSH-2. This submenu appears only if the server has host keys of a type that PuTTY doesn't already have cached, and so won't consider. Selecting a key here will allow PuTTY to use that key now and in future: PuTTY will do a fresh key-exchange with the selected key, and immediately add that key to its permanent cache (relying on the host key used at the start of the connection to cross-certify the new key). That key will be used for the rest of the current session; it may not actually be used for future sessions, depending on your preferences (see section 4.21.1). +

    +

    +Normally, PuTTY will carry on using a host key it already knows, even if the server offers key formats that PuTTY would otherwise prefer, to avoid host key prompts. As a result, if you've been using a server for some years, you may still be using an older key than a new user would use, due to server upgrades in the meantime. The SSH protocol unfortunately does not have organised facilities for host key migration and rollover, but this allows you to manually upgrade. +

    + +
    • +
  • +Break +

    +Only available in SSH-2, and only during a session. Optional extension; may not be supported by server. PuTTY requests the server's default break length. +

    + +
    • +
  • +Signals (SIGINT, SIGTERM etc) +

    +Only available in SSH-2, and only during a session. Sends various POSIX signals. Not honoured by all servers. +

    + +
    • +
+

+The following special commands are available in Telnet: +

+
  • +Are You There +
    • +
  • +Break +
    • +
  • +Synch +
    • +
  • +Erase Character +

    +PuTTY can also be configured to send this when the Backspace key is pressed; see section 4.17.3. +

    + +
    • +
  • +Erase Line +
    • +
  • +Go Ahead +
    • +
  • +No Operation +

    +Should have no effect. +

    + +
    • +
  • +Abort Process +
    • +
  • +Abort Output +
    • +
  • +Interrupt Process +

    +PuTTY can also be configured to send this when Ctrl-C is typed; see section 4.17.3. +

    + +
    • +
  • +Suspend Process +

    +PuTTY can also be configured to send this when Ctrl-Z is typed; see section 4.17.3. +

    + +
    • +
  • +End Of Record +
    • +
  • +End Of File +
    • +
+

+With a serial connection, the only available special command is ‘Break’. +

+

3.1.3.3 Starting new sessions

+

+PuTTY's system menu provides some shortcut ways to start new sessions: +

+
  • +Selecting ‘New Session’ will start a completely new instance of PuTTY, and bring up the configuration box as normal. +
    • +
  • +Selecting ‘Duplicate Session’ will start a session in a new window with precisely the same options as your current one - connecting to the same host using the same protocol, with all the same terminal settings and everything. +
    • +
  • +In an inactive window, selecting ‘Restart Session’ will do the same as ‘Duplicate Session’, but in the current window. +
    • +
  • +The ‘Saved Sessions’ submenu gives you quick access to any sets of stored session details you have previously saved. See section 4.1.2 for details of how to create saved sessions. +
    • +
+

3.1.3.4 Changing your session settings

+

+If you select ‘Change Settings’ from the system menu, PuTTY will display a cut-down version of its initial configuration box. This allows you to adjust most properties of your current session. You can change the terminal size, the font, the actions of various keypresses, the colours, and so on. +

+

+Some of the options that are available in the main configuration box are not shown in the cut-down Change Settings box. These are usually options which don't make sense to change in the middle of a session (for example, you can't switch from SSH to Telnet in mid-session). +

+

+You can save the current settings to a saved session for future use from this dialog box. See section 4.1.2 for more on saved sessions. +

+

3.1.3.5 Copy All to Clipboard

+

+This system menu option provides a convenient way to copy the whole contents of the terminal screen (up to the last nonempty line) and scrollback to the clipboard in one go. +

+

3.1.3.6 Clearing and resetting the terminal

+

+The ‘Clear Scrollback’ option on the system menu tells PuTTY to discard all the lines of text that have been kept after they scrolled off the top of the screen. This might be useful, for example, if you displayed sensitive information and wanted to make sure nobody could look over your shoulder and see it. (Note that this only prevents a casual user from using the scrollbar to view the information; the text is not guaranteed not to still be in PuTTY's memory.) +

+

+The ‘Reset Terminal’ option causes a full reset of the terminal emulation. A VT-series terminal is a complex piece of software and can easily get into a state where all the text printed becomes unreadable. (This can happen, for example, if you accidentally output a binary file to your terminal.) If this happens, selecting Reset Terminal should sort it out. +

+

3.1.3.7 Full screen mode

+

+If you find the title bar on a maximised window to be ugly or distracting, you can select Full Screen mode to maximise PuTTY ‘even more’. When you select this, PuTTY will expand to fill the whole screen and its borders, title bar and scrollbar will disappear. (You can configure the scrollbar not to disappear in full-screen mode if you want to keep it; see section 4.7.3.) +

+

+When you are in full-screen mode, you can still access the system menu if you click the left mouse button in the extreme top left corner of the screen. +

+

3.2 Creating a log file of your session

+

+For some purposes you may find you want to log everything that appears on your screen. You can do this using the ‘Logging’ panel in the configuration box. +

+

+To begin a session log, select ‘Change Settings’ from the system menu and go to the Logging panel. Enter a log file name, and select a logging mode. (You can log all session output including the terminal control sequences, or you can just log the printable text. It depends what you want the log for.) Click ‘Apply’ and your log will be started. Later on, you can go back to the Logging panel and select ‘Logging turned off completely’ to stop logging; then PuTTY will close the log file and you can safely read it. +

+

+See section 4.2 for more details and options. +

+

3.3 Altering your character set configuration

+

+If you find that special characters (accented characters, for example, or line-drawing characters) are not being displayed correctly in your PuTTY session, it may be that PuTTY is interpreting the characters sent by the server according to the wrong character set. There are a lot of different character sets available, and no good way for PuTTY to know which to use, so it's entirely possible for this to happen. +

+

+If you click ‘Change Settings’ and look at the ‘Translation’ panel, you should see a large number of character sets which you can select, and other related options. Now all you need is to find out which of them you want! (See section 4.10 for more information.) +

+

3.4 Using X11 forwarding in SSH

+

+The SSH protocol has the ability to securely forward X Window System graphical applications over your encrypted SSH connection, so that you can run an application on the SSH server machine and have it put its windows up on your local machine without sending any X network traffic in the clear. +

+

+In order to use this feature, you will need an X display server for your Windows machine, such as Cygwin/X, X-Win32, or Exceed. This will probably install itself as display number 0 on your local machine; if it doesn't, the manual for the X server should tell you what it does do. +

+

+You should then tick the ‘Enable X11 forwarding’ box in the X11 panel (see section 4.26) before starting your SSH session. The ‘X display location’ box is blank by default, which means that PuTTY will try to use a sensible default such as :0, which is the usual display location where your X server will be installed. If that needs changing, then change it. +

+

+Now you should be able to log in to the SSH server as normal. To check that X forwarding has been successfully negotiated during connection startup, you can check the PuTTY Event Log (see section 3.1.3.1). It should say something like this: +

+
2001-12-05 17:22:01 Requesting X11 forwarding
+2001-12-05 17:22:02 X11 forwarding enabled
+
+

+If the remote system is Unix or Unix-like, you should also be able to see that the DISPLAY environment variable has been set to point at display 10 or above on the SSH server machine itself: +

+
fred@unixbox:~$ echo $DISPLAY
+unixbox:10.0
+
+

+If this works, you should then be able to run X applications in the remote session and have them display their windows on your PC. +

+

+For more options relating to X11 forwarding, see section 4.26. +

+

3.5 Using port forwarding in SSH

+

+The SSH protocol has the ability to forward arbitrary network (TCP) connections over your encrypted SSH connection, to avoid the network traffic being sent in clear. For example, you could use this to connect from your home computer to a POP-3 server on a remote machine without your POP-3 password being visible to network sniffers. +

+

+In order to use port forwarding to connect from your local machine to a port on a remote server, you need to: +

+
  • +Choose a port number on your local machine where PuTTY should listen for incoming connections. There are likely to be plenty of unused port numbers above 3000. (You can also use a local loopback address here; see below for more details.) +
    • +
  • +Now, before you start your SSH connection, go to the Tunnels panel (see section 4.27). Make sure the ‘Local’ radio button is set. Enter the local port number into the ‘Source port’ box. Enter the destination host name and port number into the ‘Destination’ box, separated by a colon (for example, popserver.example.com:110 to connect to a POP-3 server). +
    • +
  • +Now click the ‘Add’ button. The details of your port forwarding should appear in the list box. +
    • +
+

+Now start your session and log in. (Port forwarding will not be enabled until after you have logged in; otherwise it would be easy to perform completely anonymous network attacks, and gain access to anyone's virtual private network.) To check that PuTTY has set up the port forwarding correctly, you can look at the PuTTY Event Log (see section 3.1.3.1). It should say something like this: +

+
2001-12-05 17:22:10 Local port 3110 forwarding to
+         popserver.example.com:110
+
+

+Now if you connect to the source port number on your local PC, you should find that it answers you exactly as if it were the service running on the destination machine. So in this example, you could then configure an e-mail client to use localhost:3110 as a POP-3 server instead of popserver.example.com:110. (Of course, the forwarding will stop happening when your PuTTY session closes down.) +

+

+You can also forward ports in the other direction: arrange for a particular port number on the server machine to be forwarded back to your PC as a connection to a service on your PC or near it. To do this, just select the ‘Remote’ radio button instead of the ‘Local’ one. The ‘Source port’ box will now specify a port number on the server (note that most servers will not allow you to use port numbers under 1024 for this purpose). +

+

+An alternative way to forward local connections to remote hosts is to use dynamic SOCKS proxying. In this mode, PuTTY acts as a SOCKS server, which SOCKS-aware programs can connect to and open forwarded connections to the destination of their choice, so this can be an alternative to long lists of static forwardings. To use this mode, you will need to select the ‘Dynamic’ radio button instead of ‘Local’, and then you should not enter anything into the ‘Destination’ box (it will be ignored). PuTTY will then listen for SOCKS connections on the port you have specified. Most web browsers can be configured to connect to this SOCKS proxy service; also, you can forward other PuTTY connections through it by setting up the Proxy control panel (see section 4.16 for details). +

+

+The source port for a forwarded connection usually does not accept connections from any machine except the SSH client or server machine itself (for local and remote forwardings respectively). There are controls in the Tunnels panel to change this: +

+
  • +The ‘Local ports accept connections from other hosts’ option allows you to set up local-to-remote port forwardings (including dynamic port forwardings) in such a way that machines other than your client PC can connect to the forwarded port. +
    • +
  • +The ‘Remote ports do the same’ option does the same thing for remote-to-local port forwardings (so that machines other than the SSH server machine can connect to the forwarded port.) Note that this feature is only available in the SSH-2 protocol, and not all SSH-2 servers honour it (in OpenSSH, for example, it's usually disabled by default). +
    • +
+

+You can also specify an IP address to listen on. Typically a Windows machine can be asked to listen on any single IP address in the 127.*.*.* range, and all of these are loopback addresses available only to the local machine. So if you forward (for example) 127.0.0.5:79 to a remote machine's finger port, then you should be able to run commands such as finger fred@127.0.0.5. This can be useful if the program connecting to the forwarded port doesn't allow you to change the port number it uses. This feature is available for local-to-remote forwarded ports; SSH-1 is unable to support it for remote-to-local ports, while SSH-2 can support it in theory but servers will not necessarily cooperate. +

+

+(Note that if you're using Windows XP Service Pack 2, you may need to obtain a fix from Microsoft in order to use addresses like 127.0.0.5 - see question A.7.17.) +

+

+For more options relating to port forwarding, see section 4.27. +

+

+If the connection you are forwarding over SSH is itself a second SSH connection made by another copy of PuTTY, you might find the ‘logical host name’ configuration option useful to warn PuTTY of which host key it should be expecting. See section 4.14.5 for details of this. +

+

3.6 Making raw TCP connections

+

+A lot of Internet protocols are composed of commands and responses in plain text. For example, SMTP (the protocol used to transfer e-mail), NNTP (the protocol used to transfer Usenet news), and HTTP (the protocol used to serve Web pages) all consist of commands in readable plain text. +

+

+Sometimes it can be useful to connect directly to one of these services and speak the protocol ‘by hand’, by typing protocol commands and watching the responses. On Unix machines, you can do this using the system's telnet command to connect to the right port number. For example, telnet mailserver.example.com 25 might enable you to talk directly to the SMTP service running on a mail server. +

+

+Although the Unix telnet program provides this functionality, the protocol being used is not really Telnet. Really there is no actual protocol at all; the bytes sent down the connection are exactly the ones you type, and the bytes shown on the screen are exactly the ones sent by the server. Unix telnet will attempt to detect or guess whether the service it is talking to is a real Telnet service or not; PuTTY prefers to be told for certain. +

+

+In order to make a debugging connection to a service of this type, you simply select the fourth protocol name, ‘Raw’, from the ‘Protocol’ buttons in the ‘Session’ configuration panel. (See section 4.1.1.) You can then enter a host name and a port number, and make the connection. +

+

3.7 Connecting to a local serial line

+

+PuTTY can connect directly to a local serial line as an alternative to making a network connection. In this mode, text typed into the PuTTY window will be sent straight out of your computer's serial port, and data received through that port will be displayed in the PuTTY window. You might use this mode, for example, if your serial port is connected to another computer which has a serial connection. +

+

+To make a connection of this type, simply select ‘Serial’ from the ‘Connection type’ radio buttons on the ‘Session’ configuration panel (see section 4.1.1). The ‘Host Name’ and ‘Port’ boxes will transform into ‘Serial line’ and ‘Speed’, allowing you to specify which serial line to use (if your computer has more than one) and what speed (baud rate) to use when transferring data. For further configuration options (data bits, stop bits, parity, flow control), you can use the ‘Serial’ configuration panel (see section 4.29). +

+

+After you start up PuTTY in serial mode, you might find that you have to make the first move, by sending some data out of the serial line in order to notify the device at the other end that someone is there for it to talk to. This probably depends on the device. If you start up a PuTTY serial session and nothing appears in the window, try pressing Return a few times and see if that helps. +

+

+A serial line provides no well defined means for one end of the connection to notify the other that the connection is finished. Therefore, PuTTY in serial mode will remain connected until you close the window using the close button. +

+

3.8 The PuTTY command line

+

+PuTTY can be made to do various things without user intervention by supplying command-line arguments (e.g., from a command prompt window, or a Windows shortcut). +

+

3.8.1 Starting a session from the command line

+

+These options allow you to bypass the configuration window and launch straight into a session. +

+

+To start a connection to a server called host: +

+
putty.exe [-ssh | -telnet | -rlogin | -raw] [user@]host
+
+

+If this syntax is used, settings are taken from the Default Settings (see section 4.1.2); user overrides these settings if supplied. Also, you can specify a protocol, which will override the default protocol (see section 3.8.3.2). +

+

+For telnet sessions, the following alternative syntax is supported (this makes PuTTY suitable for use as a URL handler for telnet URLs in web browsers): +

+
putty.exe telnet://host[:port]/
+
+

+To start a connection to a serial port, e.g. COM1: +

+
putty.exe -serial com1
+
+

+In order to start an existing saved session called sessionname, use the -load option (described in section 3.8.3.1). +

+
putty.exe -load "session name"
+
+

3.8.2 -cleanup

+

+If invoked with the -cleanup option, rather than running as normal, PuTTY will remove its registry entries and random seed file from the local machine (after confirming with the user). It will also attempt to remove information about recently launched sessions stored in the ‘jump list’ on Windows 7 and up. +

+

+Note that on multi-user systems, -cleanup only removes registry entries and files associated with the currently logged-in user. +

+

3.8.3 Standard command-line options

+

+PuTTY and its associated tools support a range of command-line options, most of which are consistent across all the tools. This section lists the available options in all tools. Options which are specific to a particular tool are covered in the chapter about that tool. +

+

3.8.3.1 -load: load a saved session

+

+The -load option causes PuTTY to load configuration details out of a saved session. If these details include a host name, then this option is all you need to make PuTTY start a session. +

+

+You need double quotes around the session name if it contains spaces. +

+

+If you want to create a Windows shortcut to start a PuTTY saved session, this is the option you should use: your shortcut should call something like +

+
d:\path\to\putty.exe -load "my session"
+
+

+(Note that PuTTY itself supports an alternative form of this option, for backwards compatibility. If you execute putty @sessionname it will have the same effect as putty -load "sessionname". With the @ form, no double quotes are required, and the @ sign must be the very first thing on the command line. This form of the option is deprecated.) +

+

3.8.3.2 Selecting a protocol: -ssh, -telnet, -rlogin, -raw -serial

+

+To choose which protocol you want to connect with, you can use one of these options: +

+
  • +-ssh selects the SSH protocol. +
    • +
  • +-telnet selects the Telnet protocol. +
    • +
  • +-rlogin selects the Rlogin protocol. +
    • +
  • +-raw selects the raw protocol. +
    • +
  • +-serial selects a serial connection. +
    • +
+

+These options are not available in the file transfer tools PSCP and PSFTP (which only work with the SSH protocol). +

+

+These options are equivalent to the protocol selection buttons in the Session panel of the PuTTY configuration box (see section 4.1.1). +

+

3.8.3.3 -v: increase verbosity

+

+Most of the PuTTY tools can be made to tell you more about what they are doing by supplying the -v option. If you are having trouble when making a connection, or you're simply curious, you can turn this switch on and hope to find out more about what is happening. +

+

3.8.3.4 -l: specify a login name

+

+You can specify the user name to log in as on the remote server using the -l option. For example, plink login.example.com -l fred. +

+

+These options are equivalent to the username selection box in the Connection panel of the PuTTY configuration box (see section 4.15.1). +

+

3.8.3.5 -L, -R and -D: set up port forwardings

+

+As well as setting up port forwardings in the PuTTY configuration (see section 4.27), you can also set up forwardings on the command line. The command-line options work just like the ones in Unix ssh programs. +

+

+To forward a local port (say 5110) to a remote destination (say popserver.example.com port 110), you can write something like one of these: +

+
putty -L 5110:popserver.example.com:110 -load mysession
+plink mysession -L 5110:popserver.example.com:110
+
+

+To forward a remote port to a local destination, just use the -R option instead of -L: +

+
putty -R 5023:mytelnetserver.myhouse.org:23 -load mysession
+plink mysession -R 5023:mytelnetserver.myhouse.org:23
+
+

+To specify an IP address for the listening end of the tunnel, prepend it to the argument: +

+
plink -L 127.0.0.5:23:localhost:23 myhost
+
+

+To set up SOCKS-based dynamic port forwarding on a local port, use the -D option. For this one you only have to pass the port number: +

+
putty -D 4096 -load mysession
+
+

+For general information on port forwarding, see section 3.5. +

+

+These options are not available in the file transfer tools PSCP and PSFTP. +

+

3.8.3.6 -m: read a remote command or script from a file

+

+The -m option performs a similar function to the ‘Remote command’ box in the SSH panel of the PuTTY configuration box (see section 4.19.1). However, the -m option expects to be given a local file name, and it will read a command from that file. +

+

+With some servers (particularly Unix systems), you can even put multiple lines in this file and execute more than one command in sequence, or a whole shell script; but this is arguably an abuse, and cannot be expected to work on all servers. In particular, it is known not to work with certain ‘embedded’ servers, such as Cisco routers. +

+

+This option is not available in the file transfer tools PSCP and PSFTP. +

+

3.8.3.7 -P: specify a port number

+

+The -P option is used to specify the port number to connect to. If you have a Telnet server running on port 9696 of a machine instead of port 23, for example: +

+
putty -telnet -P 9696 host.name
+plink -telnet -P 9696 host.name
+
+

+(Note that this option is more useful in Plink than in PuTTY, because in PuTTY you can write putty -telnet host.name 9696 in any case.) +

+

+This option is equivalent to the port number control in the Session panel of the PuTTY configuration box (see section 4.1.1). +

+

3.8.3.8 -pw: specify a password

+

+A simple way to automate a remote login is to supply your password on the command line. This is not recommended for reasons of security. If you possibly can, we recommend you set up public-key authentication instead. See chapter 8 for details. +

+

+Note that the -pw option only works when you are using the SSH protocol. Due to fundamental limitations of Telnet and Rlogin, these protocols do not support automated password authentication. +

+

3.8.3.9 -agent and -noagent: control use of Pageant for authentication

+

+The -agent option turns on SSH authentication using Pageant, and -noagent turns it off. These options are only meaningful if you are using SSH. +

+

+See chapter 9 for general information on Pageant. +

+

+These options are equivalent to the agent authentication checkbox in the Auth panel of the PuTTY configuration box (see section 4.23.3). +

+

3.8.3.10 -A and -a: control agent forwarding

+

+The -A option turns on SSH agent forwarding, and -a turns it off. These options are only meaningful if you are using SSH. +

+

+See chapter 9 for general information on Pageant, and section 9.4 for information on agent forwarding. Note that there is a security risk involved with enabling this option; see section 9.5 for details. +

+

+These options are equivalent to the agent forwarding checkbox in the Auth panel of the PuTTY configuration box (see section 4.23.6). +

+

+These options are not available in the file transfer tools PSCP and PSFTP. +

+

3.8.3.11 -X and -x: control X11 forwarding

+

+The -X option turns on X11 forwarding in SSH, and -x turns it off. These options are only meaningful if you are using SSH. +

+

+For information on X11 forwarding, see section 3.4. +

+

+These options are equivalent to the X11 forwarding checkbox in the X11 panel of the PuTTY configuration box (see section 4.26). +

+

+These options are not available in the file transfer tools PSCP and PSFTP. +

+

3.8.3.12 -t and -T: control pseudo-terminal allocation

+

+The -t option ensures PuTTY attempts to allocate a pseudo-terminal at the server, and -T stops it from allocating one. These options are only meaningful if you are using SSH. +

+

+These options are equivalent to the ‘Don't allocate a pseudo-terminal’ checkbox in the SSH panel of the PuTTY configuration box (see section 4.25.1). +

+

+These options are not available in the file transfer tools PSCP and PSFTP. +

+

3.8.3.13 -N: suppress starting a shell or command

+

+The -N option prevents PuTTY from attempting to start a shell or command on the remote server. You might want to use this option if you are only using the SSH connection for port forwarding, and your user account on the server does not have the ability to run a shell. +

+

+This feature is only available in SSH protocol version 2 (since the version 1 protocol assumes you will always want to run a shell). +

+

+This option is equivalent to the ‘Don't start a shell or command at all’ checkbox in the SSH panel of the PuTTY configuration box (see section 4.19.2). +

+

+This option is not available in the file transfer tools PSCP and PSFTP. +

+

3.8.3.14 -nc: make a remote network connection in place of a remote shell or command

+

+The -nc option prevents Plink (or PuTTY) from attempting to start a shell or command on the remote server. Instead, it will instruct the remote server to open a network connection to a host name and port number specified by you, and treat that network connection as if it were the main session. +

+

+You specify a host and port as an argument to the -nc option, with a colon separating the host name from the port number, like this: +

+
plink host1.example.com -nc host2.example.com:1234
+
+

+You might want to use this feature if you needed to make an SSH connection to a target host which you can only reach by going through a proxy host, and rather than using port forwarding you prefer to use the local proxy feature (see section 4.16.1 for more about local proxies). In this situation you might select ‘Local’ proxy type, set your local proxy command to be ‘plink %proxyhost -nc %host:%port’, enter the target host name on the Session panel, and enter the directly reachable proxy host name on the Proxy panel. +

+

+This feature is only available in SSH protocol version 2 (since the version 1 protocol assumes you will always want to run a shell). It is not available in the file transfer tools PSCP and PSFTP. It is available in PuTTY itself, although it is unlikely to be very useful in any tool other than Plink. Also, -nc uses the same server functionality as port forwarding, so it will not work if your server administrator has disabled port forwarding. +

+

+(The option is named -nc after the Unix program nc, short for ‘netcat’. The command ‘plink host1 -nc host2:port’ is very similar in functionality to ‘plink host1 nc host2 port’, which invokes nc on the server and tells it to connect to the specified destination. However, Plink's built-in -nc option does not depend on the nc program being installed on the server.) +

+

3.8.3.15 -C: enable compression

+

+The -C option enables compression of the data sent across the network. This option is only meaningful if you are using SSH. +

+

+This option is equivalent to the ‘Enable compression’ checkbox in the SSH panel of the PuTTY configuration box (see section 4.19.3). +

+

3.8.3.16 -1 and -2: specify an SSH protocol version

+

+The -1 and -2 options force PuTTY to use version 1 or version 2 of the SSH protocol. These options are only meaningful if you are using SSH. +

+

+These options are equivalent to selecting the SSH protocol version in the SSH panel of the PuTTY configuration box (see section 4.19.4). +

+

3.8.3.17 -4 and -6: specify an Internet protocol version

+

+The -4 and -6 options force PuTTY to use the older Internet protocol IPv4 or the newer IPv6 for most outgoing connections. +

+

+These options are equivalent to selecting your preferred Internet protocol version as ‘IPv4’ or ‘IPv6’ in the Connection panel of the PuTTY configuration box (see section 4.14.4). +

+

3.8.3.18 -i: specify an SSH private key

+

+The -i option allows you to specify the name of a private key file in *.PPK format which PuTTY will use to authenticate with the server. This option is only meaningful if you are using SSH. +

+

+If you are using Pageant, you can also specify a public key file (in RFC 4716 or OpenSSH format) to identify a specific key file to use. (This won't work if you're not running Pageant, of course.) +

+

+For general information on public-key authentication, see chapter 8. +

+

+This option is equivalent to the ‘Private key file for authentication’ box in the Auth panel of the PuTTY configuration box (see section 4.23.8). +

+

3.8.3.19 -loghost: specify a logical host name

+

+This option overrides PuTTY's normal SSH host key caching policy by telling it the name of the host you expect your connection to end up at (in cases where this differs from the location PuTTY thinks it's connecting to). It can be a plain host name, or a host name followed by a colon and a port number. See section 4.14.5 for more detail on this. +

+

3.8.3.20 -hostkey: manually specify an expected host key

+

+This option overrides PuTTY's normal SSH host key caching policy by telling it exactly what host key to expect, which can be useful if the normal automatic host key store in the Registry is unavailable. The argument to this option should be either a host key fingerprint, or an SSH-2 public key blob. See section 4.21.2 for more information. +

+

+You can specify this option more than once if you want to configure more than one key to be accepted. +

+

3.8.3.21 -pgpfp: display PGP key fingerprints

+

+This option causes the PuTTY tools not to run as normal, but instead to display the fingerprints of the PuTTY PGP Master Keys, in order to aid with verifying new versions. See appendix E for more information. +

+

3.8.3.22 -sercfg: specify serial port configuration

+

+This option specifies the configuration parameters for the serial port (baud rate, stop bits etc). Its argument is interpreted as a comma-separated list of configuration options, which can be as follows: +

+
  • +Any single digit from 5 to 9 sets the number of data bits. +
    • +
  • +‘1’, ‘1.5’ or ‘2’ sets the number of stop bits. +
    • +
  • +Any other numeric string is interpreted as a baud rate. +
    • +
  • +A single lower-case letter specifies the parity: ‘n’ for none, ‘o’ for odd, ‘e’ for even, ‘m’ for mark and ‘s’ for space. +
    • +
  • +A single upper-case letter specifies the flow control: ‘N’ for none, ‘X’ for XON/XOFF, ‘R’ for RTS/CTS and ‘D’ for DSR/DTR. +
    • +
+

+For example, ‘-sercfg 19200,8,n,1,N’ denotes a baud rate of 19200, 8 data bits, no parity, 1 stop bit and no flow control. +

+

3.8.3.23 -sessionlog, -sshlog, -sshrawlog: specify session logging

+

+These options cause the PuTTY network tools to write out a log file. Each of them expects a file name as an argument, e.g. ‘-sshlog putty.log’ causes an SSH packet log to be written to a file called ‘putty.log’. The three different options select different logging modes, all available from the GUI too: +

+
  • +-sessionlog selects ‘All session output’ logging mode. +
    • +
  • +-sshlog selects ‘SSH packets’ logging mode. +
    • +
  • +-sshrawlog selects ‘SSH packets and raw data’ logging mode. +
    • +
+

+For more information on logging configuration, see section 4.2. +

+

3.8.3.24 -proxycmd: specify a local proxy command

+

+This option enables PuTTY's mode for running a command on the local machine and using it as a proxy for the network connection. It expects a shell command string as an argument. +

+

+See section 4.16.1 for more information on this, and on other proxy settings. In particular, note that since the special sequences described there are understood in the argument string, literal backslashes must be doubled (if you want \ in your command, you must put \\ on the command line). +

+

3.8.3.25 -restrict-acl: restrict the Windows process ACL

+

+This option (on Windows only) causes PuTTY (or another PuTTY tool) to try to lock down the operating system's access control on its own process. If this succeeds, it should present an extra obstacle to malware that has managed to run under the same user id as the PuTTY process, by preventing it from attaching to PuTTY using the same interfaces debuggers use and either reading sensitive information out of its memory or hijacking its network session. +

+

+This option is not enabled by default, because this form of interaction between Windows programs has many legitimate uses, including accessibility software such as screen readers. Also, it cannot provide full security against this class of attack in any case, because PuTTY can only lock down its own ACL after it has started up, and malware could still get in if it attacks the process between startup and lockdown. So it trades away noticeable convenience, and delivers less real security than you might want. However, if you do want to make that tradeoff anyway, the option is available. +

+

+A PuTTY process started with -restrict-acl will pass that on to any processes started with Duplicate Session, New Session etc. (However, if you're invoking PuTTY tools explicitly, for instance as a proxy command, you'll need to arrange to pass them the -restrict-acl option yourself, if that's what you want.) +

+

+If Pageant is started with the -restrict-acl option, and you use it to launch a PuTTY session from its System Tray submenu, then Pageant will not default to starting the PuTTY subprocess with a restricted ACL. This is because PuTTY is more likely to suffer reduced functionality as a result of restricted ACLs (e.g. screen reader software will have a greater need to interact with it), whereas Pageant stores the more critical information (hence benefits more from the extra protection), so it's reasonable to want to run Pageant but not PuTTY with the ACL restrictions. You can force Pageant to start subsidiary PuTTY processes with a restricted ACL if you also pass the -restrict-putty-acl option. +

+ +

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/Chapter4.html b/doc/Chapter4.html new file mode 100644 index 0000000..36011a8 --- /dev/null +++ b/doc/Chapter4.html @@ -0,0 +1,2453 @@ + + + + +Configuring PuTTY + + + + + + + +

Previous | Contents | Index | Next

+ + +

Chapter 4: Configuring PuTTY

+

+This chapter describes all the configuration options in PuTTY. +

+

+PuTTY is configured using the control panel that comes up before you start a session. Some options can also be changed in the middle of a session, by selecting ‘Change Settings’ from the window menu. +

+

4.1 The Session panel

+

+The Session configuration panel contains the basic options you need to specify in order to open a session at all, and also allows you to save your settings to be reloaded later. +

+

4.1.1 The host name section

+

+The top box on the Session panel, labelled ‘Specify your connection by host name’, contains the details that need to be filled in before PuTTY can open a session at all. +

+
  • +The ‘Host Name’ box is where you type the name, or the IP address, of the server you want to connect to. +
    • +
  • +The ‘Connection type’ radio buttons let you choose what type of connection you want to make: a raw connection, a Telnet connection, an Rlogin connection, an SSH connection, or a connection to a local serial line. (See section 1.2 for a summary of the differences between SSH, Telnet and rlogin; see section 3.6 for an explanation of ‘raw’ connections; see section 3.7 for information about using a serial line.) +
    • +
  • +The ‘Port’ box lets you specify which port number on the server to connect to. If you select Telnet, Rlogin, or SSH, this box will be filled in automatically to the usual value, and you will only need to change it if you have an unusual server. If you select Raw mode, you will almost certainly need to fill in the ‘Port’ box yourself. +
    • +
+

+If you select ‘Serial’ from the ‘Connection type’ radio buttons, the ‘Host Name’ and ‘Port’ boxes are replaced by ‘Serial line’ and ‘Speed’; see section 4.29 for more details of these. +

+

4.1.2 Loading and storing saved sessions

+

+The next part of the Session configuration panel allows you to save your preferred PuTTY options so they will appear automatically the next time you start PuTTY. It also allows you to create saved sessions, which contain a full set of configuration options plus a host name and protocol. A saved session contains all the information PuTTY needs to start exactly the session you want. +

+
  • +To save your default settings: first set up the settings the way you want them saved. Then come back to the Session panel. Select the ‘Default Settings’ entry in the saved sessions list, with a single click. Then press the ‘Save’ button. +
    • +
+

+If there is a specific host you want to store the details of how to connect to, you should create a saved session, which will be separate from the Default Settings. +

+
  • +To save a session: first go through the rest of the configuration box setting up all the options you want. Then come back to the Session panel. Enter a name for the saved session in the ‘Saved Sessions’ input box. (The server name is often a good choice for a saved session name.) Then press the ‘Save’ button. Your saved session name should now appear in the list box. +

    +You can also save settings in mid-session, from the ‘Change Settings’ dialog. Settings changed since the start of the session will be saved with their current values; as well as settings changed through the dialog, this includes changes in window size, window title changes sent by the server, and so on. +

    + +
    • +
  • +To reload a saved session: single-click to select the session name in the list box, and then press the ‘Load’ button. Your saved settings should all appear in the configuration panel. +
    • +
  • +To modify a saved session: first load it as described above. Then make the changes you want. Come back to the Session panel, and press the ‘Save’ button. The new settings will be saved over the top of the old ones. +

    +To save the new settings under a different name, you can enter the new name in the ‘Saved Sessions’ box, or single-click to select a session name in the list box to overwrite that session. To save ‘Default Settings’, you must single-click the name before saving. +

    + +
    • +
  • +To start a saved session immediately: double-click on the session name in the list box. +
    • +
  • +To delete a saved session: single-click to select the session name in the list box, and then press the ‘Delete’ button. +
    • +
+

+Each saved session is independent of the Default Settings configuration. If you change your preferences and update Default Settings, you must also update every saved session separately. +

+

+Saved sessions are stored in the Registry, at the location +

+
HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions
+
+

+If you need to store them in a file, you could try the method described in section 4.30. +

+

4.1.3 ‘Close window on exit’

+

+Finally in the Session panel, there is an option labelled ‘Close window on exit’. This controls whether the PuTTY terminal window disappears as soon as the session inside it terminates. If you are likely to want to copy and paste text out of the session after it has terminated, or restart the session, you should arrange for this option to be off. +

+

+‘Close window on exit’ has three settings. ‘Always’ means always close the window on exit; ‘Never’ means never close on exit (always leave the window open, but inactive). The third setting, and the default one, is ‘Only on clean exit’. In this mode, a session which terminates normally will cause its window to close, but one which is aborted unexpectedly by network trouble or a confusing message from the server will leave the window up. +

+

4.2 The Logging panel

+

+The Logging configuration panel allows you to save log files of your PuTTY sessions, for debugging, analysis or future reference. +

+

+The main option is a radio-button set that specifies whether PuTTY will log anything at all. The options are: +

+
  • +‘None’. This is the default option; in this mode PuTTY will not create a log file at all. +
    • +
  • +‘Printable output’. In this mode, a log file will be created and written to, but only printable text will be saved into it. The various terminal control codes that are typically sent down an interactive session alongside the printable text will be omitted. This might be a useful mode if you want to read a log file in a text editor and hope to be able to make sense of it. +
    • +
  • +‘All session output’. In this mode, everything sent by the server into your terminal session is logged. If you view the log file in a text editor, therefore, you may well find it full of strange control characters. This is a particularly useful mode if you are experiencing problems with PuTTY's terminal handling: you can record everything that went to the terminal, so that someone else can replay the session later in slow motion and watch to see what went wrong. +
    • +
  • +‘SSH packets’. In this mode (which is only used by SSH connections), the SSH message packets sent over the encrypted connection are written to the log file (as well as Event Log entries). You might need this to debug a network-level problem, or more likely to send to the PuTTY authors as part of a bug report. BE WARNED that if you log in using a password, the password can appear in the log file; see section 4.2.5 for options that may help to remove sensitive material from the log file before you send it to anyone else. +
    • +
  • +‘SSH packets and raw data’. In this mode, as well as the decrypted packets (as in the previous mode), the raw (encrypted, compressed, etc) packets are also logged. This could be useful to diagnose corruption in transit. (The same caveats as the previous mode apply, of course.) +
    • +
+

+Note that the non-SSH logging options (‘Printable output’ and ‘All session output’) only work with PuTTY proper; in programs without terminal emulation (such as Plink), they will have no effect, even if enabled via saved settings. +

+

4.2.1 ‘Log file name’

+

+In this edit box you enter the name of the file you want to log the session to. The ‘Browse’ button will let you look around your file system to find the right place to put the file; or if you already know exactly where you want it to go, you can just type a pathname into the edit box. +

+

+There are a few special features in this box. If you use the & character in the file name box, PuTTY will insert details of the current session in the name of the file it actually opens. The precise replacements it will do are: +

+
  • +&Y will be replaced by the current year, as four digits. +
    • +
  • +&M will be replaced by the current month, as two digits. +
    • +
  • +&D will be replaced by the current day of the month, as two digits. +
    • +
  • +&T will be replaced by the current time, as six digits (HHMMSS) with no punctuation. +
    • +
  • +&H will be replaced by the host name you are connecting to. +
    • +
  • +&P will be replaced by the port number you are connecting to on the target host. +
    • +
+

+For example, if you enter the host name c:\puttylogs\log-&h-&y&m&d-&t.dat, you will end up with files looking like +

+
log-server1.example.com-20010528-110859.dat
+log-unixbox.somewhere.org-20010611-221001.dat
+
+

4.2.2 ‘What to do if the log file already exists’

+

+This control allows you to specify what PuTTY should do if it tries to start writing to a log file and it finds the file already exists. You might want to automatically destroy the existing log file and start a new one with the same name. Alternatively, you might want to open the existing log file and add data to the end of it. Finally (the default option), you might not want to have any automatic behaviour, but to ask the user every time the problem comes up. +

+

4.2.3 ‘Flush log file frequently’

+

+This option allows you to control how frequently logged data is flushed to disc. By default, PuTTY will flush data as soon as it is displayed, so that if you view the log file while a session is still open, it will be up to date; and if the client system crashes, there's a greater chance that the data will be preserved. +

+

+However, this can incur a performance penalty. If PuTTY is running slowly with logging enabled, you could try unchecking this option. Be warned that the log file may not always be up to date as a result (although it will of course be flushed when it is closed, for instance at the end of a session). +

+

4.2.4 ‘Include header’

+

+This option allows you to choose whether to include a header line with the date and time when the log file is opened. It may be useful to disable this if the log file is being used as realtime input to other programs that don't expect the header line. +

+

4.2.5 Options specific to SSH packet logging

+

+These options only apply if SSH packet data is being logged. +

+

+The following options allow particularly sensitive portions of unencrypted packets to be automatically left out of the log file. They are only intended to deter casual nosiness; an attacker could glean a lot of useful information from even these obfuscated logs (e.g., length of password). +

+

4.2.5.1 ‘Omit known password fields’

+

+When checked, decrypted password fields are removed from the log of transmitted packets. (This includes any user responses to challenge-response authentication methods such as ‘keyboard-interactive’.) This does not include X11 authentication data if using X11 forwarding. +

+

+Note that this will only omit data that PuTTY knows to be a password. However, if you start another login session within your PuTTY session, for instance, any password used will appear in the clear in the packet log. The next option may be of use to protect against this. +

+

+This option is enabled by default. +

+

4.2.5.2 ‘Omit session data’

+

+When checked, all decrypted ‘session data’ is omitted; this is defined as data in terminal sessions and in forwarded channels (TCP, X11, and authentication agent). This will usually substantially reduce the size of the resulting log file. +

+

+This option is disabled by default. +

+

4.3 The Terminal panel

+

+The Terminal configuration panel allows you to control the behaviour of PuTTY's terminal emulation. +

+

4.3.1 ‘Auto wrap mode initially on’

+

+Auto wrap mode controls what happens when text printed in a PuTTY window reaches the right-hand edge of the window. +

+

+With auto wrap mode on, if a long line of text reaches the right-hand edge, it will wrap over on to the next line so you can still see all the text. With auto wrap mode off, the cursor will stay at the right-hand edge of the screen, and all the characters in the line will be printed on top of each other. +

+

+If you are running a full-screen application and you occasionally find the screen scrolling up when it looks as if it shouldn't, you could try turning this option off. +

+

+Auto wrap mode can be turned on and off by control sequences sent by the server. This configuration option controls the default state, which will be restored when you reset the terminal (see section 3.1.3.6). However, if you modify this option in mid-session using ‘Change Settings’, it will take effect immediately. +

+

4.3.2 ‘DEC Origin Mode initially on’

+

+DEC Origin Mode is a minor option which controls how PuTTY interprets cursor-position control sequences sent by the server. +

+

+The server can send a control sequence that restricts the scrolling region of the display. For example, in an editor, the server might reserve a line at the top of the screen and a line at the bottom, and might send a control sequence that causes scrolling operations to affect only the remaining lines. +

+

+With DEC Origin Mode on, cursor coordinates are counted from the top of the scrolling region. With it turned off, cursor coordinates are counted from the top of the whole screen regardless of the scrolling region. +

+

+It is unlikely you would need to change this option, but if you find a full-screen application is displaying pieces of text in what looks like the wrong part of the screen, you could try turning DEC Origin Mode on to see whether that helps. +

+

+DEC Origin Mode can be turned on and off by control sequences sent by the server. This configuration option controls the default state, which will be restored when you reset the terminal (see section 3.1.3.6). However, if you modify this option in mid-session using ‘Change Settings’, it will take effect immediately. +

+

4.3.3 ‘Implicit CR in every LF’

+

+Most servers send two control characters, CR and LF, to start a new line of the screen. The CR character makes the cursor return to the left-hand side of the screen. The LF character makes the cursor move one line down (and might make the screen scroll). +

+

+Some servers only send LF, and expect the terminal to move the cursor over to the left automatically. If you come across a server that does this, you will see a stepped effect on the screen, like this: +

+
First line of text
+                  Second line
+                             Third line
+
+

+If this happens to you, try enabling the ‘Implicit CR in every LF’ option, and things might go back to normal: +

+
First line of text
+Second line
+Third line
+
+

4.3.4 ‘Implicit LF in every CR’

+

+Most servers send two control characters, CR and LF, to start a new line of the screen. The CR character makes the cursor return to the left-hand side of the screen. The LF character makes the cursor move one line down (and might make the screen scroll). +

+

+Some servers only send CR, and so the newly written line is overwritten by the following line. This option causes a line feed so that all lines are displayed. +

+

4.3.5 ‘Use background colour to erase screen’

+

+Not all terminals agree on what colour to turn the screen when the server sends a ‘clear screen’ sequence. Some terminals believe the screen should always be cleared to the default background colour. Others believe the screen should be cleared to whatever the server has selected as a background colour. +

+

+There exist applications that expect both kinds of behaviour. Therefore, PuTTY can be configured to do either. +

+

+With this option disabled, screen clearing is always done in the default background colour. With this option enabled, it is done in the current background colour. +

+

+Background-colour erase can be turned on and off by control sequences sent by the server. This configuration option controls the default state, which will be restored when you reset the terminal (see section 3.1.3.6). However, if you modify this option in mid-session using ‘Change Settings’, it will take effect immediately. +

+

4.3.6 ‘Enable blinking text’

+

+The server can ask PuTTY to display text that blinks on and off. This is very distracting, so PuTTY allows you to turn blinking text off completely. +

+

+When blinking text is disabled and the server attempts to make some text blink, PuTTY will instead display the text with a bolded background colour. +

+

+Blinking text can be turned on and off by control sequences sent by the server. This configuration option controls the default state, which will be restored when you reset the terminal (see section 3.1.3.6). However, if you modify this option in mid-session using ‘Change Settings’, it will take effect immediately. +

+

4.3.7 ‘Answerback to ^E’

+

+This option controls what PuTTY will send back to the server if the server sends it the ^E enquiry character. Normally it just sends the string ‘PuTTY’. +

+

+If you accidentally write the contents of a binary file to your terminal, you will probably find that it contains more than one ^E character, and as a result your next command line will probably read ‘PuTTYPuTTYPuTTY...’ as if you had typed the answerback string multiple times at the keyboard. If you set the answerback string to be empty, this problem should go away, but doing so might cause other problems. +

+

+Note that this is not the feature of PuTTY which the server will typically use to determine your terminal type. That feature is the ‘Terminal-type string’ in the Connection panel; see section 4.15.3 for details. +

+

+You can include control characters in the answerback string using ^C notation. (Use ^~ to get a literal ^.) +

+

4.3.8 ‘Local echo’

+

+With local echo disabled, characters you type into the PuTTY window are not echoed in the window by PuTTY. They are simply sent to the server. (The server might choose to echo them back to you; this can't be controlled from the PuTTY control panel.) +

+

+Some types of session need local echo, and many do not. In its default mode, PuTTY will automatically attempt to deduce whether or not local echo is appropriate for the session you are working in. If you find it has made the wrong decision, you can use this configuration option to override its choice: you can force local echo to be turned on, or force it to be turned off, instead of relying on the automatic detection. +

+

4.3.9 ‘Local line editing’

+

+Normally, every character you type into the PuTTY window is sent immediately to the server the moment you type it. +

+

+If you enable local line editing, this changes. PuTTY will let you edit a whole line at a time locally, and the line will only be sent to the server when you press Return. If you make a mistake, you can use the Backspace key to correct it before you press Return, and the server will never see the mistake. +

+

+Since it is hard to edit a line locally without being able to see it, local line editing is mostly used in conjunction with local echo (section 4.3.8). This makes it ideal for use in raw mode or when connecting to MUDs or talkers. (Although some more advanced MUDs do occasionally turn local line editing on and turn local echo off, in order to accept a password from the user.) +

+

+Some types of session need local line editing, and many do not. In its default mode, PuTTY will automatically attempt to deduce whether or not local line editing is appropriate for the session you are working in. If you find it has made the wrong decision, you can use this configuration option to override its choice: you can force local line editing to be turned on, or force it to be turned off, instead of relying on the automatic detection. +

+

4.3.10 Remote-controlled printing

+

+A lot of VT100-compatible terminals support printing under control of the remote server (sometimes called ‘passthrough printing’). PuTTY supports this feature as well, but it is turned off by default. +

+

+To enable remote-controlled printing, choose a printer from the ‘Printer to send ANSI printer output to’ drop-down list box. This should allow you to select from all the printers you have installed drivers for on your computer. Alternatively, you can type the network name of a networked printer (for example, \\printserver\printer1) even if you haven't already installed a driver for it on your own machine. +

+

+When the remote server attempts to print some data, PuTTY will send that data to the printer raw - without translating it, attempting to format it, or doing anything else to it. It is up to you to ensure your remote server knows what type of printer it is talking to. +

+

+Since PuTTY sends data to the printer raw, it cannot offer options such as portrait versus landscape, print quality, or paper tray selection. All these things would be done by your PC printer driver (which PuTTY bypasses); if you need them done, you will have to find a way to configure your remote server to do them. +

+

+To disable remote printing again, choose ‘None (printing disabled)’ from the printer selection list. This is the default state. +

+

4.4 The Keyboard panel

+

+The Keyboard configuration panel allows you to control the behaviour of the keyboard in PuTTY. The correct state for many of these settings depends on what the server to which PuTTY is connecting expects. With a Unix server, this is likely to depend on the termcap or terminfo entry it uses, which in turn is likely to be controlled by the ‘Terminal-type string’ setting in the Connection panel; see section 4.15.3 for details. If none of the settings here seems to help, you may find question A.7.13 to be useful. +

+

4.4.1 Changing the action of the Backspace key

+

+Some terminals believe that the Backspace key should send the same thing to the server as Control-H (ASCII code 8). Other terminals believe that the Backspace key should send ASCII code 127 (usually known as Control-?) so that it can be distinguished from Control-H. This option allows you to choose which code PuTTY generates when you press Backspace. +

+

+If you are connecting over SSH, PuTTY by default tells the server the value of this option (see section 4.25.2), so you may find that the Backspace key does the right thing either way. Similarly, if you are connecting to a Unix system, you will probably find that the Unix stty command lets you configure which the server expects to see, so again you might not need to change which one PuTTY generates. On other systems, the server's expectation might be fixed and you might have no choice but to configure PuTTY. +

+

+If you do have the choice, we recommend configuring PuTTY to generate Control-? and configuring the server to expect it, because that allows applications such as emacs to use Control-H for help. +

+

+(Typing Shift-Backspace will cause PuTTY to send whichever code isn't configured here as the default.) +

+

4.4.2 Changing the action of the Home and End keys

+

+The Unix terminal emulator rxvt disagrees with the rest of the world about what character sequences should be sent to the server by the Home and End keys. +

+

+xterm, and other terminals, send ESC [1~ for the Home key, and ESC [4~ for the End key. rxvt sends ESC [H for the Home key and ESC [Ow for the End key. +

+

+If you find an application on which the Home and End keys aren't working, you could try switching this option to see if it helps. +

+

4.4.3 Changing the action of the function keys and keypad

+

+This option affects the function keys (F1 to F12) and the top row of the numeric keypad. +

+
  • +In the default mode, labelled ESC [n~, the function keys generate sequences like ESC [11~, ESC [12~ and so on. This matches the general behaviour of Digital's terminals. +
    • +
  • +In Linux mode, F6 to F12 behave just like the default mode, but F1 to F5 generate ESC [[A through to ESC [[E. This mimics the Linux virtual console. +
    • +
  • +In Xterm R6 mode, F5 to F12 behave like the default mode, but F1 to F4 generate ESC OP through to ESC OS, which are the sequences produced by the top row of the keypad on Digital's terminals. +
    • +
  • +In VT400 mode, all the function keys behave like the default mode, but the actual top row of the numeric keypad generates ESC OP through to ESC OS. +
    • +
  • +In VT100+ mode, the function keys generate ESC OP through to ESC O[ +
    • +
  • +In SCO mode, the function keys F1 to F12 generate ESC [M through to ESC [X. Together with shift, they generate ESC [Y through to ESC [j. With control they generate ESC [k through to ESC [v, and with shift and control together they generate ESC [w through to ESC [{. +
    • +
+

+If you don't know what any of this means, you probably don't need to fiddle with it. +

+

4.4.4 Controlling Application Cursor Keys mode

+

+Application Cursor Keys mode is a way for the server to change the control sequences sent by the arrow keys. In normal mode, the arrow keys send ESC [A through to ESC [D. In application mode, they send ESC OA through to ESC OD. +

+

+Application Cursor Keys mode can be turned on and off by the server, depending on the application. PuTTY allows you to configure the initial state. +

+

+You can also disable application cursor keys mode completely, using the ‘Features’ configuration panel; see section 4.6.1. +

+

4.4.5 Controlling Application Keypad mode

+

+Application Keypad mode is a way for the server to change the behaviour of the numeric keypad. +

+

+In normal mode, the keypad behaves like a normal Windows keypad: with NumLock on, the number keys generate numbers, and with NumLock off they act like the arrow keys and Home, End etc. +

+

+In application mode, all the keypad keys send special control sequences, including Num Lock. Num Lock stops behaving like Num Lock and becomes another function key. +

+

+Depending on which version of Windows you run, you may find the Num Lock light still flashes on and off every time you press Num Lock, even when application mode is active and Num Lock is acting like a function key. This is unavoidable. +

+

+Application keypad mode can be turned on and off by the server, depending on the application. PuTTY allows you to configure the initial state. +

+

+You can also disable application keypad mode completely, using the ‘Features’ configuration panel; see section 4.6.1. +

+

4.4.6 Using NetHack keypad mode

+

+PuTTY has a special mode for playing NetHack. You can enable it by selecting ‘NetHack’ in the ‘Initial state of numeric keypad’ control. +

+

+In this mode, the numeric keypad keys 1-9 generate the NetHack movement commands (hjklyubn). The 5 key generates the . command (do nothing). +

+

+In addition, pressing Shift or Ctrl with the keypad keys generate the Shift- or Ctrl-keys you would expect (e.g. keypad-7 generates ‘y’, so Shift-keypad-7 generates ‘Y’ and Ctrl-keypad-7 generates Ctrl-Y); these commands tell NetHack to keep moving you in the same direction until you encounter something interesting. +

+

+For some reason, this feature only works properly when Num Lock is on. We don't know why. +

+

4.4.7 Enabling a DEC-like Compose key

+

+DEC terminals have a Compose key, which provides an easy-to-remember way of typing accented characters. You press Compose and then type two more characters. The two characters are ‘combined’ to produce an accented character. The choices of character are designed to be easy to remember; for example, composing ‘e’ and ‘`’ produces the ‘è’ character. +

+

+If your keyboard has a Windows Application key, it acts as a Compose key in PuTTY. Alternatively, if you enable the ‘AltGr acts as Compose key’ option, the AltGr key will become a Compose key. +

+

4.4.8 ‘Control-Alt is different from AltGr’

+

+Some old keyboards do not have an AltGr key, which can make it difficult to type some characters. PuTTY can be configured to treat the key combination Ctrl + Left Alt the same way as the AltGr key. +

+

+By default, this checkbox is checked, and the key combination Ctrl + Left Alt does something completely different. PuTTY's usual handling of the left Alt key is to prefix the Escape (Control-[) character to whatever character sequence the rest of the keypress would generate. For example, Alt-A generates Escape followed by a. So Alt-Ctrl-A would generate Escape, followed by Control-A. +

+

+If you uncheck this box, Ctrl-Alt will become a synonym for AltGr, so you can use it to type extra graphic characters if your keyboard has any. +

+

+(However, Ctrl-Alt will never act as a Compose key, regardless of the setting of ‘AltGr acts as Compose key’ described in section 4.4.7.) +

+

4.5 The Bell panel

+

+The Bell panel controls the terminal bell feature: the server's ability to cause PuTTY to beep at you. +

+

+In the default configuration, when the server sends the character with ASCII code 7 (Control-G), PuTTY will play the Windows Default Beep sound. This is not always what you want the terminal bell feature to do; the Bell panel allows you to configure alternative actions. +

+

4.5.1 ‘Set the style of bell’

+

+This control allows you to select various different actions to occur on a terminal bell: +

+
  • +Selecting ‘None’ disables the bell completely. In this mode, the server can send as many Control-G characters as it likes and nothing at all will happen. +
    • +
  • +‘Make default system alert sound’ is the default setting. It causes the Windows ‘Default Beep’ sound to be played. To change what this sound is, or to test it if nothing seems to be happening, use the Sound configurer in the Windows Control Panel. +
    • +
  • +‘Visual bell’ is a silent alternative to a beeping computer. In this mode, when the server sends a Control-G, the whole PuTTY window will flash white for a fraction of a second. +
    • +
  • +‘Beep using the PC speaker’ is self-explanatory. +
    • +
  • +‘Play a custom sound file’ allows you to specify a particular sound file to be used by PuTTY alone, or even by a particular individual PuTTY session. This allows you to distinguish your PuTTY beeps from any other beeps on the system. If you select this option, you will also need to enter the name of your sound file in the edit control ‘Custom sound file to play as a bell’. +
    • +
+

4.5.2 ‘Taskbar/caption indication on bell’

+

+This feature controls what happens to the PuTTY window's entry in the Windows Taskbar if a bell occurs while the window does not have the input focus. +

+

+In the default state (‘Disabled’) nothing unusual happens. +

+

+If you select ‘Steady’, then when a bell occurs and the window is not in focus, the window's Taskbar entry and its title bar will change colour to let you know that PuTTY session is asking for your attention. The change of colour will persist until you select the window, so you can leave several PuTTY windows minimised in your terminal, go away from your keyboard, and be sure not to have missed any important beeps when you get back. +

+

+‘Flashing’ is even more eye-catching: the Taskbar entry will continuously flash on and off until you select the window. +

+

4.5.3 ‘Control the bell overload behaviour’

+

+A common user error in a terminal session is to accidentally run the Unix command cat (or equivalent) on an inappropriate file type, such as an executable, image file, or ZIP file. This produces a huge stream of non-text characters sent to the terminal, which typically includes a lot of bell characters. As a result of this the terminal often doesn't stop beeping for ten minutes, and everybody else in the office gets annoyed. +

+

+To try to avoid this behaviour, or any other cause of excessive beeping, PuTTY includes a bell overload management feature. In the default configuration, receiving more than five bell characters in a two-second period will cause the overload feature to activate. Once the overload feature is active, further bells will have no effect at all, so the rest of your binary file will be sent to the screen in silence. After a period of five seconds during which no further bells are received, the overload feature will turn itself off again and bells will be re-enabled. +

+

+If you want this feature completely disabled, you can turn it off using the checkbox ‘Bell is temporarily disabled when over-used’. +

+

+Alternatively, if you like the bell overload feature but don't agree with the settings, you can configure the details: how many bells constitute an overload, how short a time period they have to arrive in to do so, and how much silent time is required before the overload feature will deactivate itself. +

+

+Bell overload mode is always deactivated by any keypress in the terminal. This means it can respond to large unexpected streams of data, but does not interfere with ordinary command-line activities that generate beeps (such as filename completion). +

+

4.6 The Features panel

+

+PuTTY's terminal emulation is very highly featured, and can do a lot of things under remote server control. Some of these features can cause problems due to buggy or strangely configured server applications. +

+

+The Features configuration panel allows you to disable some of PuTTY's more advanced terminal features, in case they cause trouble. +

+

4.6.1 Disabling application keypad and cursor keys

+

+Application keypad mode (see section 4.4.5) and application cursor keys mode (see section 4.4.4) alter the behaviour of the keypad and cursor keys. Some applications enable these modes but then do not deal correctly with the modified keys. You can force these modes to be permanently disabled no matter what the server tries to do. +

+

4.6.2 Disabling xterm-style mouse reporting

+

+PuTTY allows the server to send control codes that let it take over the mouse and use it for purposes other than copy and paste. Applications which use this feature include the text-mode web browser links, the Usenet newsreader trn version 4, and the file manager mc (Midnight Commander). +

+

+If you find this feature inconvenient, you can disable it using the ‘Disable xterm-style mouse reporting’ control. With this box ticked, the mouse will always do copy and paste in the normal way. +

+

+Note that even if the application takes over the mouse, you can still manage PuTTY's copy and paste by holding down the Shift key while you select and paste, unless you have deliberately turned this feature off (see section 4.11.2). +

+

4.6.3 Disabling remote terminal resizing

+

+PuTTY has the ability to change the terminal's size and position in response to commands from the server. If you find PuTTY is doing this unexpectedly or inconveniently, you can tell PuTTY not to respond to those server commands. +

+

4.6.4 Disabling switching to the alternate screen

+

+Many terminals, including PuTTY, support an ‘alternate screen’. This is the same size as the ordinary terminal screen, but separate. Typically a screen-based program such as a text editor might switch the terminal to the alternate screen before starting up. Then at the end of the run, it switches back to the primary screen, and you see the screen contents just as they were before starting the editor. +

+

+Some people prefer this not to happen. If you want your editor to run in the same screen as the rest of your terminal activity, you can disable the alternate screen feature completely. +

+

4.6.5 Disabling remote window title changing

+

+PuTTY has the ability to change the window title in response to commands from the server. If you find PuTTY is doing this unexpectedly or inconveniently, you can tell PuTTY not to respond to those server commands. +

+

4.6.6 Response to remote window title querying

+

+PuTTY can optionally provide the xterm service of allowing server applications to find out the local window title. This feature is disabled by default, but you can turn it on if you really want it. +

+

+NOTE that this feature is a potential security hazard. If a malicious application can write data to your terminal (for example, if you merely cat a file owned by someone else on the server machine), it can change your window title (unless you have disabled this as mentioned in section 4.6.5) and then use this service to have the new window title sent back to the server as if typed at the keyboard. This allows an attacker to fake keypresses and potentially cause your server-side applications to do things you didn't want. Therefore this feature is disabled by default, and we recommend you do not set it to ‘Window title’ unless you really know what you are doing. +

+

+There are three settings for this option: +

+
+‘None’ +
+
+PuTTY makes no response whatsoever to the relevant escape sequence. This may upset server-side software that is expecting some sort of response. +
+
+‘Empty string’ +
+
+PuTTY makes a well-formed response, but leaves it blank. Thus, server-side software that expects a response is kept happy, but an attacker cannot influence the response string. This is probably the setting you want if you have no better ideas. +
+
+‘Window title’ +
+
+PuTTY responds with the actual window title. This is dangerous for the reasons described above. +
+
+

4.6.7 Disabling remote scrollback clearing

+

+PuTTY has the ability to clear the terminal's scrollback buffer in response to a command from the server. If you find PuTTY is doing this unexpectedly or inconveniently, you can tell PuTTY not to respond to that server command. +

+

4.6.8 Disabling destructive backspace

+

+Normally, when PuTTY receives character 127 (^?) from the server, it will perform a ‘destructive backspace’: move the cursor one space left and delete the character under it. This can apparently cause problems in some applications, so PuTTY provides the ability to configure character 127 to perform a normal backspace (without deleting a character) instead. +

+

4.6.9 Disabling remote character set configuration

+

+PuTTY has the ability to change its character set configuration in response to commands from the server. Some programs send these commands unexpectedly or inconveniently. In particular, BitchX (an IRC client) seems to have a habit of reconfiguring the character set to something other than the user intended. +

+

+If you find that accented characters are not showing up the way you expect them to, particularly if you're running BitchX, you could try disabling the remote character set configuration commands. +

+

4.6.10 Disabling Arabic text shaping

+

+PuTTY supports shaping of Arabic text, which means that if your server sends text written in the basic Unicode Arabic alphabet then it will convert it to the correct display forms before printing it on the screen. +

+

+If you are using full-screen software which was not expecting this to happen (especially if you are not an Arabic speaker and you unexpectedly find yourself dealing with Arabic text files in applications which are not Arabic-aware), you might find that the display becomes corrupted. By ticking this box, you can disable Arabic text shaping so that PuTTY displays precisely the characters it is told to display. +

+

+You may also find you need to disable bidirectional text display; see section 4.6.11. +

+

4.6.11 Disabling bidirectional text display

+

+PuTTY supports bidirectional text display, which means that if your server sends text written in a language which is usually displayed from right to left (such as Arabic or Hebrew) then PuTTY will automatically flip it round so that it is displayed in the right direction on the screen. +

+

+If you are using full-screen software which was not expecting this to happen (especially if you are not an Arabic speaker and you unexpectedly find yourself dealing with Arabic text files in applications which are not Arabic-aware), you might find that the display becomes corrupted. By ticking this box, you can disable bidirectional text display, so that PuTTY displays text from left to right in all situations. +

+

+You may also find you need to disable Arabic text shaping; see section 4.6.10. +

+

4.7 The Window panel

+

+The Window configuration panel allows you to control aspects of the PuTTY window. +

+

4.7.1 Setting the size of the PuTTY window

+

+The ‘Columns’ and ‘Rows’ boxes let you set the PuTTY window to a precise size. Of course you can also drag the window to a new size while a session is running. +

+

4.7.2 What to do when the window is resized

+

+These options allow you to control what happens when the user tries to resize the PuTTY window using its window furniture. +

+

+There are four options here: +

+
  • +‘Change the number of rows and columns’: the font size will not change. (This is the default.) +
    • +
  • +‘Change the size of the font’: the number of rows and columns in the terminal will stay the same, and the font size will change. +
    • +
  • +‘Change font size when maximised’: when the window is resized, the number of rows and columns will change, except when the window is maximised (or restored), when the font size will change. (In this mode, holding down the Alt key while resizing will also cause the font size to change.) +
    • +
  • +‘Forbid resizing completely’: the terminal will refuse to be resized at all. +
    • +
+

4.7.3 Controlling scrollback

+

+These options let you configure the way PuTTY keeps text after it scrolls off the top of the screen (see section 3.1.2). +

+

+The ‘Lines of scrollback’ box lets you configure how many lines of text PuTTY keeps. The ‘Display scrollbar’ options allow you to hide the scrollbar (although you can still view the scrollback using the keyboard as described in section 3.1.2). You can separately configure whether the scrollbar is shown in full-screen mode and in normal modes. +

+

+If you are viewing part of the scrollback when the server sends more text to PuTTY, the screen will revert to showing the current terminal contents. You can disable this behaviour by turning off ‘Reset scrollback on display activity’. You can also make the screen revert when you press a key, by turning on ‘Reset scrollback on keypress’. +

+

4.7.4 ‘Push erased text into scrollback’

+

+When this option is enabled, the contents of the terminal screen will be pushed into the scrollback when a server-side application clears the screen, so that your scrollback will contain a better record of what was on your screen in the past. +

+

+If the application switches to the alternate screen (see section 4.6.4 for more about this), then the contents of the primary screen will be visible in the scrollback until the application switches back again. +

+

+This option is enabled by default. +

+

4.8 The Appearance panel

+

+The Appearance configuration panel allows you to control aspects of the appearance of PuTTY's window. +

+

4.8.1 Controlling the appearance of the cursor

+

+The ‘Cursor appearance’ option lets you configure the cursor to be a block, an underline, or a vertical line. A block cursor becomes an empty box when the window loses focus; an underline or a vertical line becomes dotted. +

+

+The ‘Cursor blinks’ option makes the cursor blink on and off. This works in any of the cursor modes. +

+

4.8.2 Controlling the font used in the terminal window

+

+This option allows you to choose what font, in what size, the PuTTY terminal window uses to display the text in the session. +

+

+By default, you will be offered a choice from all the fixed-width fonts installed on the system, since VT100-style terminal handling expects a fixed-width font. If you tick the box marked ‘Allow selection of variable-pitch fonts’, however, PuTTY will offer variable-width fonts as well: if you select one of these, the font will be coerced into fixed-size character cells, which will probably not look very good (but can work OK with some fonts). +

+

4.8.3 ‘Hide mouse pointer when typing in window’

+

+If you enable this option, the mouse pointer will disappear if the PuTTY window is selected and you press a key. This way, it will not obscure any of the text in the window while you work in your session. As soon as you move the mouse, the pointer will reappear. +

+

+This option is disabled by default, so the mouse pointer remains visible at all times. +

+

4.8.4 Controlling the window border

+

+PuTTY allows you to configure the appearance of the window border to some extent. +

+

+The checkbox marked ‘Sunken-edge border’ changes the appearance of the window border to something more like a DOS box: the inside edge of the border is highlighted as if it sank down to meet the surface inside the window. This makes the border a little bit thicker as well. It's hard to describe well. Try it and see if you like it. +

+

+You can also configure a completely blank gap between the text in the window and the border, using the ‘Gap between text and window edge’ control. By default this is set at one pixel. You can reduce it to zero, or increase it further. +

+

4.9 The Behaviour panel

+

+The Behaviour configuration panel allows you to control aspects of the behaviour of PuTTY's window. +

+

4.9.1 Controlling the window title

+

+The ‘Window title’ edit box allows you to set the title of the PuTTY window. By default the window title will contain the host name followed by ‘PuTTY’, for example server1.example.com - PuTTY. If you want a different window title, this is where to set it. +

+

+PuTTY allows the server to send xterm control sequences which modify the title of the window in mid-session (unless this is disabled - see section 4.6.5); the title string set here is therefore only the initial window title. +

+

+As well as the window title, there is also an xterm sequence to modify the title of the window's icon. This makes sense in a windowing system where the window becomes an icon when minimised, such as Windows 3.1 or most X Window System setups; but in the Windows 95-like user interface it isn't as applicable. +

+

+By default, PuTTY only uses the server-supplied window title, and ignores the icon title entirely. If for some reason you want to see both titles, check the box marked ‘Separate window and icon titles’. If you do this, PuTTY's window title and Taskbar caption will change into the server-supplied icon title if you minimise the PuTTY window, and change back to the server-supplied window title if you restore it. (If the server has not bothered to supply a window or icon title, none of this will happen.) +

+

4.9.2 ‘Warn before closing window’

+

+If you press the Close button in a PuTTY window that contains a running session, PuTTY will put up a warning window asking if you really meant to close the window. A window whose session has already terminated can always be closed without a warning. +

+

+If you want to be able to close a window quickly, you can disable the ‘Warn before closing window’ option. +

+

4.9.3 ‘Window closes on ALT-F4’

+

+By default, pressing ALT-F4 causes the window to close (or a warning box to appear; see section 4.9.2). If you disable the ‘Window closes on ALT-F4’ option, then pressing ALT-F4 will simply send a key sequence to the server. +

+

4.9.4 ‘System menu appears on ALT-Space’

+

+If this option is enabled, then pressing ALT-Space will bring up the PuTTY window's menu, like clicking on the top left corner. If it is disabled, then pressing ALT-Space will just send ESC SPACE to the server. +

+

+Some accessibility programs for Windows may need this option enabling to be able to control PuTTY's window successfully. For instance, Dragon NaturallySpeaking requires it both to open the system menu via voice, and to close, minimise, maximise and restore the window. +

+

4.9.5 ‘System menu appears on Alt alone’

+

+If this option is enabled, then pressing and releasing ALT will bring up the PuTTY window's menu, like clicking on the top left corner. If it is disabled, then pressing and releasing ALT will have no effect. +

+

4.9.6 ‘Ensure window is always on top’

+

+If this option is enabled, the PuTTY window will stay on top of all other windows. +

+

4.9.7 ‘Full screen on Alt-Enter’

+

+If this option is enabled, then pressing Alt-Enter will cause the PuTTY window to become full-screen. Pressing Alt-Enter again will restore the previous window size. +

+

+The full-screen feature is also available from the System menu, even when it is configured not to be available on the Alt-Enter key. See section 3.1.3.7. +

+

4.10 The Translation panel

+

+The Translation configuration panel allows you to control the translation between the character set understood by the server and the character set understood by PuTTY. +

+

4.10.1 Controlling character set translation

+

+During an interactive session, PuTTY receives a stream of 8-bit bytes from the server, and in order to display them on the screen it needs to know what character set to interpret them in. Similarly, PuTTY needs to know how to translate your keystrokes into the encoding the server expects. Unfortunately, there is no satisfactory mechanism for PuTTY and the server to communicate this information, so it must usually be manually configured. +

+

+There are a lot of character sets to choose from. The ‘Remote character set’ option lets you select one. +

+

+By default PuTTY will use the UTF-8 encoding of Unicode, which can represent pretty much any character; data coming from the server is interpreted as UTF-8, and keystrokes are sent UTF-8 encoded. This is what most modern distributions of Linux will expect by default. However, if this is wrong for your server, you can select a different character set using this control. +

+

+A few other notable character sets are: +

+
  • +The ISO-8859 series are all standard character sets that include various accented characters appropriate for different sets of languages. +
    • +
  • +The Win125x series are defined by Microsoft, for similar purposes. In particular Win1252 is almost equivalent to ISO-8859-1, but contains a few extra characters such as matched quotes and the Euro symbol. +
    • +
  • +If you want the old IBM PC character set with block graphics and line-drawing characters, you can select ‘CP437’. +
    • +
+

+If you need support for a numeric code page which is not listed in the drop-down list, such as code page 866, then you can try entering its name manually (CP866 for example) in the list box. If the underlying version of Windows has the appropriate translation table installed, PuTTY will use it. +

+

4.10.2 ‘Treat CJK ambiguous characters as wide’

+

+There are some Unicode characters whose width is not well-defined. In most contexts, such characters should be treated as single-width for the purposes of wrapping and so on; however, in some CJK contexts, they are better treated as double-width for historical reasons, and some server-side applications may expect them to be displayed as such. Setting this option will cause PuTTY to take the double-width interpretation. +

+

+If you use legacy CJK applications, and you find your lines are wrapping in the wrong places, or you are having other display problems, you might want to play with this setting. +

+

+This option only has any effect in UTF-8 mode (see section 4.10.1). +

+

4.10.3 ‘Caps Lock acts as Cyrillic switch’

+

+This feature allows you to switch between a US/UK keyboard layout and a Cyrillic keyboard layout by using the Caps Lock key, if you need to type (for example) Russian and English side by side in the same document. +

+

+Currently this feature is not expected to work properly if your native keyboard layout is not US or UK. +

+

4.10.4 Controlling display of line-drawing characters

+

+VT100-series terminals allow the server to send control sequences that shift temporarily into a separate character set for drawing simple lines and boxes. However, there are a variety of ways in which PuTTY can attempt to find appropriate characters, and the right one to use depends on the locally configured font. In general you should probably try lots of options until you find one that your particular font supports. +

+
  • +‘Use Unicode line drawing code points’ tries to use the box characters that are present in Unicode. For good Unicode-supporting fonts this is probably the most reliable and functional option. +
    • +
  • +‘Poor man's line drawing’ assumes that the font cannot generate the line and box characters at all, so it will use the +, - and | characters to draw approximations to boxes. You should use this option if none of the other options works. +
    • +
  • +‘Font has XWindows encoding’ is for use with fonts that have a special encoding, where the lowest 32 character positions (below the ASCII printable range) contain the line-drawing characters. This is unlikely to be the case with any standard Windows font; it will probably only apply to custom-built fonts or fonts that have been automatically converted from the X Window System. +
    • +
  • +‘Use font in both ANSI and OEM modes’ tries to use the same font in two different character sets, to obtain a wider range of characters. This doesn't always work; some fonts claim to be a different size depending on which character set you try to use. +
    • +
  • +‘Use font in OEM mode only’ is more reliable than that, but can miss out other characters from the main character set. +
    • +
+

4.10.5 Controlling copy and paste of line drawing characters

+

+By default, when you copy and paste a piece of the PuTTY screen that contains VT100 line and box drawing characters, PuTTY will paste them in the form they appear on the screen: either Unicode line drawing code points, or the ‘poor man's’ line-drawing characters +, - and |. The checkbox ‘Copy and paste VT100 line drawing chars as lqqqk’ disables this feature, so line-drawing characters will be pasted as the ASCII characters that were printed to produce them. This will typically mean they come out mostly as q and x, with a scattering of jklmntuvw at the corners. This might be useful if you were trying to recreate the same box layout in another program, for example. +

+

+Note that this option only applies to line-drawing characters which were printed by using the VT100 mechanism. Line-drawing characters that were received as Unicode code points will paste as Unicode always. +

+

4.10.6 Combining VT100 line-drawing with UTF-8

+

+If PuTTY is configured to treat data from the server as encoded in UTF-8, then by default it disables the older VT100-style system of control sequences that cause the lower-case letters to be temporarily replaced by line drawing characters. +

+

+The rationale is that in UTF-8 mode you don't need those control sequences anyway, because all the line-drawing characters they access are available as Unicode characters already, so there's no need for applications to put the terminal into a special state to get at them. +

+

+Also, it removes a risk of the terminal accidentally getting into that state: if you accidentally write uncontrolled binary data to a non-UTF-8 terminal, it can be surprisingly common to find that your next shell prompt appears as a sequence of line-drawing characters and then you have to remember or look up how to get out of that mode. So by default, UTF-8 mode simply doesn't have a confusing mode like that to get into, accidentally or on purpose. +

+

+However, not all applications will see it that way. Even UTF-8 terminal users will still sometimes have to run software that tries to print line-drawing characters in the old-fashioned way. So the configuration option ‘Enable VT100 line drawing even in UTF-8 mode’ puts PuTTY into a hybrid mode in which it understands the VT100-style control sequences that change the meaning of the ASCII lower case letters, and understands UTF-8. +

+

4.11 The Selection panel

+

+The Selection panel allows you to control the way copy and paste work in the PuTTY window. +

+

4.11.1 Changing the actions of the mouse buttons

+

+PuTTY's copy and paste mechanism is by default modelled on the Unix xterm application. The X Window System uses a three-button mouse, and the convention in that system is that the left button selects, the right button extends an existing selection, and the middle button pastes. +

+

+Windows often only has two mouse buttons, so when run on Windows, PuTTY is configurable. In PuTTY's default configuration (‘Compromise’), the right button pastes, and the middle button (if you have one) extends a selection. +

+

+If you have a three-button mouse and you are already used to the xterm arrangement, you can select it using the ‘Action of mouse buttons’ control. +

+

+Alternatively, with the ‘Windows’ option selected, the middle button extends, and the right button brings up a context menu (on which one of the options is ‘Paste’). (This context menu is always available by holding down Ctrl and right-clicking, regardless of the setting of this option.) +

+

+(When PuTTY iself is running on Unix, it follows the X Window System convention.) +

+

4.11.2 ‘Shift overrides application's use of mouse’

+

+PuTTY allows the server to send control codes that let it take over the mouse and use it for purposes other than copy and paste. Applications which use this feature include the text-mode web browser links, the Usenet newsreader trn version 4, and the file manager mc (Midnight Commander). +

+

+When running one of these applications, pressing the mouse buttons no longer performs copy and paste. If you do need to copy and paste, you can still do so if you hold down Shift while you do your mouse clicks. +

+

+However, it is possible in theory for applications to even detect and make use of Shift + mouse clicks. We don't know of any applications that do this, but in case someone ever writes one, unchecking the ‘Shift overrides application's use of mouse’ checkbox will cause Shift + mouse clicks to go to the server as well (so that mouse-driven copy and paste will be completely disabled). +

+

+If you want to prevent the application from taking over the mouse at all, you can do this using the Features control panel; see section 4.6.2. +

+

4.11.3 Default selection mode

+

+As described in section 3.1.1, PuTTY has two modes of selecting text to be copied to the clipboard. In the default mode (‘Normal’), dragging the mouse from point A to point B selects to the end of the line containing A, all the lines in between, and from the very beginning of the line containing B. In the other mode (‘Rectangular block’), dragging the mouse between two points defines a rectangle, and everything within that rectangle is copied. +

+

+Normally, you have to hold down Alt while dragging the mouse to select a rectangular block. Using the ‘Default selection mode’ control, you can set rectangular selection as the default, and then you have to hold down Alt to get the normal behaviour. +

+

4.11.4 Assigning copy and paste actions to clipboards

+

+Here you can configure which clipboard(s) are written or read by PuTTY's various copy and paste actions. +

+

+Most platforms, including Windows, have a single system clipboard. On these platforms, PuTTY provides a second clipboard-like facility by permitting you to paste the text you last selected in this window, whether or not it is currently also in the system clipboard. This is not enabled by default. +

+

+The X Window System (which underlies most Unix graphical interfaces) provides multiple clipboards (or ‘selections’), and many applications support more than one of them by a different user interface mechanism. When PuTTY itself is running on Unix, it has more configurability relating to these selections. +

+

+The two most commonly used selections are called ‘PRIMARY’ and ‘CLIPBOARD’; in applications supporting both, the usual behaviour is that PRIMARY is used by mouse-only actions (selecting text automatically copies it to PRIMARY, and middle-clicking pastes from PRIMARY), whereas CLIPBOARD is used by explicit Copy and Paste menu items or keypresses such as Ctrl-C and Ctrl-V. +

+

4.11.4.1 ‘Auto-copy selected text’

+

+The checkbox ‘Auto-copy selected text to system clipboard’ controls whether or not selecting text in the PuTTY terminal window automatically has the side effect of copying it to the system clipboard, without requiring a separate user interface action. +

+

+On X, the wording of this option is changed slightly so that ‘CLIPBOARD’ is mentioned in place of the ‘system clipboard’. Text selected in the terminal window will always be automatically placed in the PRIMARY selection, as is conventional, but if you tick this box, it will also be placed in ‘CLIPBOARD’ at the same time. +

+

4.11.4.2 Choosing a clipboard for UI actions

+

+PuTTY has three user-interface actions which can be configured to paste into the terminal (not counting menu items). You can click whichever mouse button (if any) is configured to paste (see section 4.11.1); you can press Shift-Ins; or you can press Ctrl-Shift-V, although that action is not enabled by default. +

+

+You can configure which of the available clipboards each of these actions pastes from (including turning the paste action off completely). On platforms with a single system clipboard (such as Windows), the available options are to paste from that clipboard or to paste from PuTTY's internal memory of the last selected text within that window. On X, the standard options are CLIPBOARD or PRIMARY. +

+

+(PRIMARY is conceptually similar in that it also refers to the last selected text – just across all applications instead of just this window.) +

+

+The two keyboard options each come with a corresponding key to copy to the same clipboard. Whatever you configure Shift-Ins to paste from, Ctrl-Ins will copy to the same location; similarly, Ctrl-Shift-C will copy to whatever Ctrl-Shift-V pastes from. +

+

+On X, you can also enter a selection name of your choice. For example, there is a rarely-used standard selection called ‘SECONDARY’, which Emacs (for example) can work with if you hold down the Meta key while dragging to select or clicking to paste; if you configure a PuTTY keyboard action to access this clipboard, then you can interoperate with other applications' use of it. Another thing you could do would be to invent a clipboard name yourself, to create a special clipboard shared only between instances of PuTTY, or between just instances configured in that particular way. +

+

4.11.5 ‘Permit control characters in pasted text’

+

+It is possible for the clipboard to contain not just text (with newlines and tabs) but also control characters such as ESC which could have surprising effects if pasted into a terminal session, depending on what program is running on the server side. Copying text from a mischievous web page could put such characters onto the clipboard. +

+

+By default, PuTTY filters out the more unusual control characters, only letting through the more obvious text-formatting characters (newlines, tab, backspace, and DEL). +

+

+Setting this option stops this filtering; on paste, any character on the clipboard is sent to the session uncensored. This might be useful if you are deliberately using control character pasting as a simple form of scripting, for instance. +

+

4.12 The Copy panel

+

+The Copy configuration panel controls behaviour specifically related to copying from the terminal window to the clipboard. +

+

4.12.1 Character classes

+

+PuTTY will select a word at a time in the terminal window if you double-click to begin the drag. This section allows you to control precisely what is considered to be a word. +

+

+Each character is given a class, which is a small number (typically 0, 1 or 2). PuTTY considers a single word to be any number of adjacent characters in the same class. So by modifying the assignment of characters to classes, you can modify the word-by-word selection behaviour. +

+

+In the default configuration, the character classes are: +

+
  • +Class 0 contains white space and control characters. +
    • +
  • +Class 1 contains most punctuation. +
    • +
  • +Class 2 contains letters, numbers and a few pieces of punctuation (the double quote, minus sign, period, forward slash and underscore). +
    • +
+

+So, for example, if you assign the @ symbol into character class 2, you will be able to select an e-mail address with just a double click. +

+

+In order to adjust these assignments, you start by selecting a group of characters in the list box. Then enter a class number in the edit box below, and press the ‘Set’ button. +

+

+This mechanism currently only covers ASCII characters, because it isn't feasible to expand the list to cover the whole of Unicode. +

+

+Character class definitions can be modified by control sequences sent by the server. This configuration option controls the default state, which will be restored when you reset the terminal (see section 3.1.3.6). However, if you modify this option in mid-session using ‘Change Settings’, it will take effect immediately. +

+

4.12.2 Copying in Rich Text Format

+

+If you enable ‘Copy to clipboard in RTF as well as plain text’, PuTTY will write formatting information to the clipboard as well as the actual text you copy. The effect of this is that if you paste into (say) a word processor, the text will appear in the word processor in the same font, colour, and style (e.g. bold, underline) PuTTY was using to display it. +

+

+This option can easily be inconvenient, so by default it is disabled. +

+

4.13 The Colours panel

+

+The Colours panel allows you to control PuTTY's use of colour. +

+

4.13.1 ‘Allow terminal to specify ANSI colours’

+

+This option is enabled by default. If it is disabled, PuTTY will ignore any control sequences sent by the server to request coloured text. +

+

+If you have a particularly garish application, you might want to turn this option off and make PuTTY only use the default foreground and background colours. +

+

4.13.2 ‘Allow terminal to use xterm 256-colour mode’

+

+This option is enabled by default. If it is disabled, PuTTY will ignore any control sequences sent by the server which use the extended 256-colour mode supported by recent versions of xterm. +

+

+If you have an application which is supposed to use 256-colour mode and it isn't working, you may find you need to tell your server that your terminal supports 256 colours. On Unix, you do this by ensuring that the setting of TERM describes a 256-colour-capable terminal. You can check this using a command such as infocmp: +

+
$ infocmp | grep colors
+        colors#256, cols#80, it#8, lines#24, pairs#256,
+
+

+If you do not see ‘colors#256’ in the output, you may need to change your terminal setting. On modern Linux machines, you could try ‘xterm-256color’. +

+

4.13.3 ‘Allow terminal to use 24-bit colour’

+

+This option is enabled by default. If it is disabled, PuTTY will ignore any control sequences sent by the server which use the control sequences supported by modern terminals to specify arbitrary 24-bit RGB colour value. +

+

4.13.4 ‘Indicate bolded text by changing...’

+

+When the server sends a control sequence indicating that some text should be displayed in bold, PuTTY can handle this in several ways. It can either change the font for a bold version, or use the same font in a brighter colour, or it can do both (brighten the colour and embolden the font). This control lets you choose which. +

+

+By default bold is indicated by colour, so non-bold text is displayed in light grey and bold text is displayed in bright white (and similarly in other colours). If you change the setting to ‘The font’ box, bold and non-bold text will be displayed in the same colour, and instead the font will change to indicate the difference. If you select ‘Both’, the font and the colour will both change. +

+

+Some applications rely on ‘bold black’ being distinguishable from a black background; if you choose ‘The font’, their text may become invisible. +

+

4.13.5 ‘Attempt to use logical palettes’

+

+Logical palettes are a mechanism by which a Windows application running on an 8-bit colour display can select precisely the colours it wants instead of going with the Windows standard defaults. +

+

+If you are not getting the colours you ask for on an 8-bit display, you can try enabling this option. However, be warned that it's never worked very well. +

+

4.13.6 ‘Use system colours’

+

+Enabling this option will cause PuTTY to ignore the configured colours for ‘Default Background/Foreground’ and ‘Cursor Colour/Text’ (see section 4.13.7), instead going with the system-wide defaults. +

+

+Note that non-bold and bold text will be the same colour if this option is enabled. You might want to change to indicating bold text by font changes (see section 4.13.4). +

+

4.13.7 Adjusting the colours in the terminal window

+

+The main colour control allows you to specify exactly what colours things should be displayed in. To modify one of the PuTTY colours, use the list box to select which colour you want to modify. The RGB values for that colour will appear on the right-hand side of the list box. Now, if you press the ‘Modify’ button, you will be presented with a colour selector, in which you can choose a new colour to go in place of the old one. (You may also edit the RGB values directly in the edit boxes, if you wish; each value is an integer from 0 to 255.) +

+

+PuTTY allows you to set the cursor colour, the default foreground and background, and the precise shades of all the ANSI configurable colours (black, red, green, yellow, blue, magenta, cyan, and white). You can also modify the precise shades used for the bold versions of these colours; these are used to display bold text if you have chosen to indicate that by colour (see section 4.13.4), and can also be used if the server asks specifically to use them. (Note that ‘Default Bold Background’ is not the background colour used for bold text; it is only used if the server specifically asks for a bold background.) +

+

4.14 The Connection panel

+

+The Connection panel allows you to configure options that apply to more than one type of connection. +

+

4.14.1 Using keepalives to prevent disconnection

+

+If you find your sessions are closing unexpectedly (most often with ‘Connection reset by peer’) after they have been idle for a while, you might want to try using this option. +

+

+Some network routers and firewalls need to keep track of all connections through them. Usually, these firewalls will assume a connection is dead if no data is transferred in either direction after a certain time interval. This can cause PuTTY sessions to be unexpectedly closed by the firewall if no traffic is seen in the session for some time. +

+

+The keepalive option (‘Seconds between keepalives’) allows you to configure PuTTY to send data through the session at regular intervals, in a way that does not disrupt the actual terminal session. If you find your firewall is cutting idle connections off, you can try entering a non-zero value in this field. The value is measured in seconds; so, for example, if your firewall cuts connections off after ten minutes then you might want to enter 300 seconds (5 minutes) in the box. +

+

+Note that keepalives are not always helpful. They help if you have a firewall which drops your connection after an idle period; but if the network between you and the server suffers from breaks in connectivity then keepalives can actually make things worse. If a session is idle, and connectivity is temporarily lost between the endpoints, but the connectivity is restored before either side tries to send anything, then there will be no problem - neither endpoint will notice that anything was wrong. However, if one side does send something during the break, it will repeatedly try to re-send, and eventually give up and abandon the connection. Then when connectivity is restored, the other side will find that the first side doesn't believe there is an open connection any more. Keepalives can make this sort of problem worse, because they increase the probability that PuTTY will attempt to send data during a break in connectivity. (Other types of periodic network activity can cause this behaviour; in particular, SSH-2 re-keys can have this effect. See section 4.20.2.) +

+

+Therefore, you might find that keepalives help connection loss, or you might find they make it worse, depending on what kind of network problems you have between you and the server. +

+

+Keepalives are only supported in Telnet and SSH; the Rlogin and Raw protocols offer no way of implementing them. (For an alternative, see section 4.14.3.) +

+

+Note that if you are using SSH-1 and the server has a bug that makes it unable to deal with SSH-1 ignore messages (see section 4.28.11), enabling keepalives will have no effect. +

+

4.14.2 ‘Disable Nagle's algorithm’

+

+Nagle's algorithm is a detail of TCP/IP implementations that tries to minimise the number of small data packets sent down a network connection. With Nagle's algorithm enabled, PuTTY's bandwidth usage will be slightly more efficient; with it disabled, you may find you get a faster response to your keystrokes when connecting to some types of server. +

+

+The Nagle algorithm is disabled by default for interactive connections. +

+

4.14.3 ‘Enable TCP keepalives’

+

+NOTE: TCP keepalives should not be confused with the application-level keepalives described in section 4.14.1. If in doubt, you probably want application-level keepalives; TCP keepalives are provided for completeness. +

+

+The idea of TCP keepalives is similar to application-level keepalives, and the same caveats apply. The main differences are: +

+
  • +TCP keepalives are available on all connection types, including Raw and Rlogin. +
    • +
  • +The interval between TCP keepalives is usually much longer, typically two hours; this is set by the operating system, and cannot be configured within PuTTY. +
    • +
  • +If the operating system does not receive a response to a keepalive, it may send out more in quick succession and terminate the connection if no response is received. +
    • +
+

+TCP keepalives may be more useful for ensuring that half-open connections are terminated than for keeping a connection alive. +

+

+TCP keepalives are disabled by default. +

+

4.14.4 ‘Internet protocol version’

+

+This option allows the user to select between the old and new Internet protocols and addressing schemes (IPv4 and IPv6). The selected protocol will be used for most outgoing network connections (including connections to proxies); however, tunnels have their own configuration, for which see section 4.27.2. +

+

+The default setting is ‘Auto’, which means PuTTY will do something sensible and try to guess which protocol you wanted. (If you specify a literal Internet address, it will use whichever protocol that address implies. If you provide a hostname, it will see what kinds of address exist for that hostname; it will use IPv6 if there is an IPv6 address available, and fall back to IPv4 if not.) +

+

+If you need to force PuTTY to use a particular protocol, you can explicitly set this to ‘IPv4’ or ‘IPv6’. +

+

4.14.5 ‘Logical name of remote host’

+

+This allows you to tell PuTTY that the host it will really end up connecting to is different from where it thinks it is making a network connection. +

+

+You might use this, for instance, if you had set up an SSH port forwarding in one PuTTY session so that connections to some arbitrary port (say, localhost port 10022) were forwarded to a second machine's SSH port (say, foovax port 22), and then started a second PuTTY connecting to the forwarded port. +

+

+In normal usage, the second PuTTY will access the host key cache under the host name and port it actually connected to (i.e. localhost port 10022 in this example). Using the logical host name option, however, you can configure the second PuTTY to cache the host key under the name of the host you know that it's really going to end up talking to (here foovax). +

+

+This can be useful if you expect to connect to the same actual server through many different channels (perhaps because your port forwarding arrangements keep changing): by consistently setting the logical host name, you can arrange that PuTTY will not keep asking you to reconfirm its host key. Conversely, if you expect to use the same local port number for port forwardings to lots of different servers, you probably didn't want any particular server's host key cached under that local port number. (For this latter case, you could instead explicitly configure host keys in the relevant sessions; see section 4.21.2.) +

+

+If you just enter a host name for this option, PuTTY will cache the SSH host key under the default SSH port for that host, irrespective of the port you really connected to (since the typical scenario is like the above example: you connect to a silly real port number and your connection ends up forwarded to the normal port-22 SSH server of some other machine). To override this, you can append a port number to the logical host name, separated by a colon. E.g. entering ‘foovax:2200’ as the logical host name will cause the host key to be cached as if you had connected to port 2200 of foovax. +

+

+If you provide a host name using this option, it is also displayed in other locations which contain the remote host name, such as the default window title and the default SSH password prompt. This reflects the fact that this is the host you're really connecting to, which is more important than the mere means you happen to be using to contact that host. (This applies even if you're using a protocol other than SSH.) +

+

4.15 The Data panel

+

+The Data panel allows you to configure various pieces of data which can be sent to the server to affect your connection at the far end. +

+

+Each option on this panel applies to more than one protocol. Options which apply to only one protocol appear on that protocol's configuration panels. +

+

4.15.1 ‘Auto-login username’

+

+All three of the SSH, Telnet and Rlogin protocols allow you to specify what user name you want to log in as, without having to type it explicitly every time. (Some Telnet servers don't support this.) +

+

+In this box you can type that user name. +

+

4.15.2 Use of system username

+

+When the previous box (section 4.15.1) is left blank, by default, PuTTY will prompt for a username at the time you make a connection. +

+

+In some environments, such as the networks of large organisations implementing single sign-on, a more sensible default may be to use the name of the user logged in to the local operating system (if any); this is particularly likely to be useful with GSSAPI key exchange and user authentication (see section 4.24 and section 4.20.1.1). This control allows you to change the default behaviour. +

+

+The current system username is displayed in the dialog as a convenience. It is not saved in the configuration; if a saved session is later used by a different user, that user's name will be used. +

+

4.15.3 ‘Terminal-type string’

+

+Most servers you might connect to with PuTTY are designed to be connected to from lots of different types of terminal. In order to send the right control sequences to each one, the server will need to know what type of terminal it is dealing with. Therefore, each of the SSH, Telnet and Rlogin protocols allow a text string to be sent down the connection describing the terminal. On a Unix server, this selects an entry from the termcap or terminfo database that tells applications what control sequences to send to the terminal, and what character sequences to expect the keyboard to generate. +

+

+PuTTY attempts to emulate the Unix xterm program, and by default it reflects this by sending xterm as a terminal-type string. If you find this is not doing what you want - perhaps the remote system reports ‘Unknown terminal type’ - you could try setting this to something different, such as vt220. +

+

+If you're not sure whether a problem is due to the terminal type setting or not, you probably need to consult the manual for your application or your server. +

+

4.15.4 ‘Terminal speeds’

+

+The Telnet, Rlogin, and SSH protocols allow the client to specify terminal speeds to the server. +

+

+This parameter does not affect the actual speed of the connection, which is always ‘as fast as possible’; it is just a hint that is sometimes used by server software to modify its behaviour. For instance, if a slow speed is indicated, the server may switch to a less bandwidth-hungry display mode. +

+

+The value is usually meaningless in a network environment, but PuTTY lets you configure it, in case you find the server is reacting badly to the default value. +

+

+The format is a pair of numbers separated by a comma, for instance, 38400,38400. The first number represents the output speed (from the server) in bits per second, and the second is the input speed (to the server). (Only the first is used in the Rlogin protocol.) +

+

+This option has no effect on Raw connections. +

+

4.15.5 Setting environment variables on the server

+

+The Telnet protocol provides a means for the client to pass environment variables to the server. Many Telnet servers have stopped supporting this feature due to security flaws, but PuTTY still supports it for the benefit of any servers which have found other ways around the security problems than just disabling the whole mechanism. +

+

+Version 2 of the SSH protocol also provides a similar mechanism, which is easier to implement without security flaws. Newer SSH-2 servers are more likely to support it than older ones. +

+

+This configuration data is not used in the SSH-1, rlogin or raw protocols. +

+

+To add an environment variable to the list transmitted down the connection, you enter the variable name in the ‘Variable’ box, enter its value in the ‘Value’ box, and press the ‘Add’ button. To remove one from the list, select it in the list box and press ‘Remove’. +

+

4.16 The Proxy panel

+

+The Proxy panel allows you to configure PuTTY to use various types of proxy in order to make its network connections. The settings in this panel affect the primary network connection forming your PuTTY session, and also any extra connections made as a result of SSH port forwarding (see section 3.5). +

+

+Note that unlike some software (such as web browsers), PuTTY does not attempt to automatically determine whether to use a proxy and (if so) which one to use for a given destination. If you need to use a proxy, it must always be explicitly configured. +

+

4.16.1 Setting the proxy type

+

+The ‘Proxy type’ radio buttons allow you to configure what type of proxy you want PuTTY to use for its network connections. The default setting is ‘None’; in this mode no proxy is used for any connection. +

+
  • +Selecting ‘HTTP’ allows you to proxy your connections through a web server supporting the HTTP CONNECT command, as documented in RFC 2817. +
    • +
  • +Selecting ‘SOCKS 4’ or ‘SOCKS 5’ allows you to proxy your connections through a SOCKS server. +
    • +
  • +Many firewalls implement a less formal type of proxy in which a user can make a Telnet connection directly to the firewall machine and enter a command such as connect myhost.com 22 to connect through to an external host. Selecting ‘Telnet’ allows you to tell PuTTY to use this type of proxy. +
    • +
  • +Selecting ‘Local’ allows you to specify an arbitrary command on the local machine to act as a proxy. When the session is started, instead of creating a TCP connection, PuTTY runs the command (specified in section 4.16.5), and uses its standard input and output streams. +

    +This could be used, for instance, to talk to some kind of network proxy that PuTTY does not natively support; or you could tunnel a connection over something other than TCP/IP entirely. +

    +

    +If you want your local proxy command to make a secondary SSH connection to a proxy host and then tunnel the primary connection over that, you might well want the -nc command-line option in Plink. See section 3.8.3.14 for more information. +

    +

    +You can also enable this mode on the command line; see section 3.8.3.24. +

    + +
    • +
+

4.16.2 Excluding parts of the network from proxying

+

+Typically you will only need to use a proxy to connect to non-local parts of your network; for example, your proxy might be required for connections outside your company's internal network. In the ‘Exclude Hosts/IPs’ box you can enter ranges of IP addresses, or ranges of DNS names, for which PuTTY will avoid using the proxy and make a direct connection instead. +

+

+The ‘Exclude Hosts/IPs’ box may contain more than one exclusion range, separated by commas. Each range can be an IP address or a DNS name, with a * character allowing wildcards. For example: +

+
*.example.com
+
+

+This excludes any host with a name ending in .example.com from proxying. +

+
192.168.88.*
+
+

+This excludes any host with an IP address starting with 192.168.88 from proxying. +

+
192.168.88.*,*.example.com
+
+

+This excludes both of the above ranges at once. +

+

+Connections to the local host (the host name localhost, and any loopback IP address) are never proxied, even if the proxy exclude list does not explicitly contain them. It is very unlikely that this behaviour would ever cause problems, but if it does you can change it by enabling ‘Consider proxying local host connections’. +

+

+Note that if you are doing DNS at the proxy (see section 4.16.3), you should make sure that your proxy exclusion settings do not depend on knowing the IP address of a host. If the name is passed on to the proxy without PuTTY looking it up, it will never know the IP address and cannot check it against your list. +

+

4.16.3 Name resolution when using a proxy

+

+If you are using a proxy to access a private network, it can make a difference whether DNS name resolution is performed by PuTTY itself (on the client machine) or performed by the proxy. +

+

+The ‘Do DNS name lookup at proxy end’ configuration option allows you to control this. If you set it to ‘No’, PuTTY will always do its own DNS, and will always pass an IP address to the proxy. If you set it to ‘Yes’, PuTTY will always pass host names straight to the proxy without trying to look them up first. +

+

+If you set this option to ‘Auto’ (the default), PuTTY will do something it considers appropriate for each type of proxy. Telnet, HTTP, and SOCKS5 proxies will have host names passed straight to them; SOCKS4 proxies will not. +

+

+Note that if you are doing DNS at the proxy, you should make sure that your proxy exclusion settings (see section 4.16.2) do not depend on knowing the IP address of a host. If the name is passed on to the proxy without PuTTY looking it up, it will never know the IP address and cannot check it against your list. +

+

+The original SOCKS 4 protocol does not support proxy-side DNS. There is a protocol extension (SOCKS 4A) which does support it, but not all SOCKS 4 servers provide this extension. If you enable proxy DNS and your SOCKS 4 server cannot deal with it, this might be why. +

+

4.16.4 Username and password

+

+If your proxy requires authentication, you can enter a username and a password in the ‘Username’ and ‘Password’ boxes. +

+

+Note that if you save your session, the proxy password will be saved in plain text, so anyone who can access your PuTTY configuration data will be able to discover it. +

+

+Authentication is not fully supported for all forms of proxy: +

+
  • +Username and password authentication is supported for HTTP proxies and SOCKS 5 proxies. +
    • +With SOCKS 5, authentication is via CHAP if the proxy supports it (this is not supported in PuTTYtel); otherwise the password is sent to the proxy in plain text. +
      • +
    • +With HTTP proxying, the only currently supported authentication method is ‘basic’, where the password is sent to the proxy in plain text. +
      • +
    + +
    • +
  • +SOCKS 4 can use the ‘Username’ field, but does not support passwords. +
    • +
  • +You can specify a way to include a username and password in the Telnet/Local proxy command (see section 4.16.5). +
    • +
+

4.16.5 Specifying the Telnet or Local proxy command

+

+If you are using the Telnet proxy type, the usual command required by the firewall's Telnet server is connect, followed by a host name and a port number. If your proxy needs a different command, you can enter an alternative here. +

+

+If you are using the Local proxy type, the local command to run is specified here. +

+

+In this string, you can use \n to represent a new-line, \r to represent a carriage return, \t to represent a tab character, and \x followed by two hex digits to represent any other character. \\ is used to encode the \ character itself. +

+

+Also, the special strings %host and %port will be replaced by the host name and port number you want to connect to. The strings %user and %pass will be replaced by the proxy username and password you specify. The strings %proxyhost and %proxyport will be replaced by the host details specified on the Proxy panel, if any (this is most likely to be useful for the Local proxy type). To get a literal % sign, enter %%. +

+

+If a Telnet proxy server prompts for a username and password before commands can be sent, you can use a command such as: +

+
%user\n%pass\nconnect %host %port\n
+
+

+This will send your username and password as the first two lines to the proxy, followed by a command to connect to the desired host and port. Note that if you do not include the %user or %pass tokens in the Telnet command, then the ‘Username’ and ‘Password’ configuration fields will be ignored. +

+

4.16.6 Controlling proxy logging

+

+Often the proxy interaction has its own diagnostic output; this is particularly the case for local proxy commands. +

+

+The setting ‘Print proxy diagnostics in the terminal window’ lets you control how much of the proxy's diagnostics are printed to the main terminal window, along with output from your main session. +

+

+By default (‘No’), proxy diagnostics are only sent to the Event Log; with ‘Yes’ they are also printed to the terminal, where they may get mixed up with your main session. ‘Only until session starts’ is a compromise; proxy messages will go to the terminal window until the main session is deemed to have started (in a protocol-dependent way), which is when they're most likely to be interesting; any further proxy-related messages during the session will only go to the Event Log. +

+

4.17 The Telnet panel

+

+The Telnet panel allows you to configure options that only apply to Telnet sessions. +

+

4.17.1 ‘Handling of OLD_ENVIRON ambiguity’

+

+The original Telnet mechanism for passing environment variables was badly specified. At the time the standard (RFC 1408) was written, BSD telnet implementations were already supporting the feature, and the intention of the standard was to describe the behaviour the BSD implementations were already using. +

+

+Sadly there was a typing error in the standard when it was issued, and two vital function codes were specified the wrong way round. BSD implementations did not change, and the standard was not corrected. Therefore, it's possible you might find either BSD or RFC-compliant implementations out there. This switch allows you to choose which one PuTTY claims to be. +

+

+The problem was solved by issuing a second standard, defining a new Telnet mechanism called NEW_ENVIRON, which behaved exactly like the original OLD_ENVIRON but was not encumbered by existing implementations. Most Telnet servers now support this, and it's unambiguous. This feature should only be needed if you have trouble passing environment variables to quite an old server. +

+

4.17.2 Passive and active Telnet negotiation modes

+

+In a Telnet connection, there are two types of data passed between the client and the server: actual text, and negotiations about which Telnet extra features to use. +

+

+PuTTY can use two different strategies for negotiation: +

+
  • +In active mode, PuTTY starts to send negotiations as soon as the connection is opened. +
    • +
  • +In passive mode, PuTTY will wait to negotiate until it sees a negotiation from the server. +
    • +
+

+The obvious disadvantage of passive mode is that if the server is also operating in a passive mode, then negotiation will never begin at all. For this reason PuTTY defaults to active mode. +

+

+However, sometimes passive mode is required in order to successfully get through certain types of firewall and Telnet proxy server. If you have confusing trouble with a firewall, you could try enabling passive mode to see if it helps. +

+

4.17.3 ‘Keyboard sends Telnet special commands’

+

+If this box is checked, several key sequences will have their normal actions modified: +

+
  • +the Backspace key on the keyboard will send the Telnet special backspace code; +
    • +
  • +Control-C will send the Telnet special Interrupt Process code; +
    • +
  • +Control-Z will send the Telnet special Suspend Process code. +
    • +
+

+You probably shouldn't enable this unless you know what you're doing. +

+

4.17.4 ‘Return key sends Telnet New Line instead of ^M’

+

+Unlike most other remote login protocols, the Telnet protocol has a special ‘new line’ code that is not the same as the usual line endings of Control-M or Control-J. By default, PuTTY sends the Telnet New Line code when you press Return, instead of sending Control-M as it does in most other protocols. +

+

+Most Unix-style Telnet servers don't mind whether they receive Telnet New Line or Control-M; some servers do expect New Line, and some servers prefer to see ^M. If you are seeing surprising behaviour when you press Return in a Telnet session, you might try turning this option off to see if it helps. +

+

4.18 The Rlogin panel

+

+The Rlogin panel allows you to configure options that only apply to Rlogin sessions. +

+

4.18.1 ‘Local username’

+

+Rlogin allows an automated (password-free) form of login by means of a file called .rhosts on the server. You put a line in your .rhosts file saying something like jbloggs@pc1.example.com, and then when you make an Rlogin connection the client transmits the username of the user running the Rlogin client. The server checks the username and hostname against .rhosts, and if they match it does not ask for a password. +

+

+This only works because Unix systems contain a safeguard to stop a user from pretending to be another user in an Rlogin connection. Rlogin connections have to come from port numbers below 1024, and Unix systems prohibit this to unprivileged processes; so when the server sees a connection from a low-numbered port, it assumes the client end of the connection is held by a privileged (and therefore trusted) process, so it believes the claim of who the user is. +

+

+Windows does not have this restriction: any user can initiate an outgoing connection from a low-numbered port. Hence, the Rlogin .rhosts mechanism is completely useless for securely distinguishing several different users on a Windows machine. If you have a .rhosts entry pointing at a Windows PC, you should assume that anyone using that PC can spoof your username in an Rlogin connection and access your account on the server. +

+

+The ‘Local username’ control allows you to specify what user name PuTTY should claim you have, in case it doesn't match your Windows user name (or in case you didn't bother to set up a Windows user name). +

+

4.19 The SSH panel

+

+The SSH panel allows you to configure options that only apply to SSH sessions. +

+

4.19.1 Executing a specific command on the server

+

+In SSH, you don't have to run a general shell session on the server. Instead, you can choose to run a single specific command (such as a mail user agent, for example). If you want to do this, enter the command in the ‘Remote command’ box. +

+

+Note that most servers will close the session after executing the command. +

+

4.19.2 ‘Don't start a shell or command at all’

+

+If you tick this box, PuTTY will not attempt to run a shell or command after connecting to the remote server. You might want to use this option if you are only using the SSH connection for port forwarding, and your user account on the server does not have the ability to run a shell. +

+

+This feature is only available in SSH protocol version 2 (since the version 1 protocol assumes you will always want to run a shell). +

+

+This feature can also be enabled using the -N command-line option; see section 3.8.3.13. +

+

+If you use this feature in Plink, you will not be able to terminate the Plink process by any graceful means; the only way to kill it will be by pressing Control-C or sending a kill signal from another program. +

+

4.19.3 ‘Enable compression’

+

+This enables data compression in the SSH connection: data sent by the server is compressed before sending, and decompressed at the client end. Likewise, data sent by PuTTY to the server is compressed first and the server decompresses it at the other end. This can help make the most of a low-bandwidth connection. +

+

4.19.4 ‘SSH protocol version’

+

+This allows you to select whether to use SSH protocol version 2 or the older version 1. +

+

+You should normally leave this at the default of ‘2’. As well as having fewer features, the older SSH-1 protocol is no longer developed, has many known cryptographic weaknesses, and is generally not considered to be secure. PuTTY's protocol 1 implementation is provided mainly for compatibility, and is no longer being enhanced. +

+

+If a server offers both versions, prefer ‘2’. If you have some server or piece of equipment that only talks SSH-1, select ‘1’ here, and do not treat the resulting connection as secure. +

+

+PuTTY will not automatically fall back to the other version of the protocol if the server turns out not to match your selection here; instead, it will put up an error message and abort the connection. This prevents an active attacker downgrading an intended SSH-2 connection to SSH-1. +

+

4.19.5 Sharing an SSH connection between PuTTY tools

+

+The controls in this box allow you to configure PuTTY to reuse an existing SSH connection, where possible. +

+

+The SSH-2 protocol permits you to run multiple data channels over the same SSH connection, so that you can log in just once (and do the expensive encryption setup just once) and then have more than one terminal window open. +

+

+Each instance of PuTTY can still run at most one terminal session, but using the controls in this box, you can configure PuTTY to check if another instance of itself has already connected to the target host, and if so, share that instance's SSH connection instead of starting a separate new one. +

+

+To enable this feature, just tick the box ‘Share SSH connections if possible’. Then, whenever you start up a PuTTY session connecting to a particular host, it will try to reuse an existing SSH connection if one is available. For example, selecting ‘Duplicate Session’ from the system menu will launch another session on the same host, and if sharing is enabled then it will reuse the existing SSH connection. +

+

+When this mode is in use, the first PuTTY that connected to a given server becomes the ‘upstream’, which means that it is the one managing the real SSH connection. All subsequent PuTTYs which reuse the connection are referred to as ‘downstreams’: they do not connect to the real server at all, but instead connect to the upstream PuTTY via local inter-process communication methods. +

+

+For this system to be activated, both the upstream and downstream instances of PuTTY must have the sharing option enabled. +

+

+The upstream PuTTY can therefore not terminate until all its downstreams have closed. This is similar to the effect you get with port forwarding or X11 forwarding, in which a PuTTY whose terminal session has already finished will still remain open so as to keep serving forwarded connections. +

+

+In case you need to configure this system in more detail, there are two additional checkboxes which allow you to specify whether a particular PuTTY can act as an upstream or a downstream or both. (These boxes only take effect if the main ‘Share SSH connections if possible’ box is also ticked.) By default both of these boxes are ticked, so that multiple PuTTYs started from the same configuration will designate one of themselves as the upstream and share a single connection; but if for some reason you need a particular PuTTY configuration not to be an upstream (e.g. because you definitely need it to close promptly) or not to be a downstream (e.g. because it needs to do its own authentication using a special private key) then you can untick one or the other of these boxes. +

+

+I have referred to ‘PuTTY’ throughout the above discussion, but all the other PuTTY tools which make SSH connections can use this mechanism too. For example, if PSCP or PSFTP loads a configuration with sharing enabled, then it can act as a downstream and use an existing SSH connection set up by an instance of GUI PuTTY. The one special case is that PSCP and PSFTP will never act as upstreams. +

+

+It is possible to test programmatically for the existence of a live upstream using Plink. See section 7.2.3.4. +

+

4.20 The Kex panel

+

+The Kex panel (short for ‘key exchange’) allows you to configure options related to SSH-2 key exchange. +

+

+Key exchange occurs at the start of an SSH connection (and occasionally thereafter); it establishes a shared secret that is used as the basis for all of SSH's security features. It is therefore very important for the security of the connection that the key exchange is secure. +

+

+Key exchange is a cryptographically intensive process; if either the client or the server is a relatively slow machine, the slower methods may take several tens of seconds to complete. +

+

+If connection startup is too slow, or the connection hangs periodically, you may want to try changing these settings. +

+

+If you don't understand what any of this means, it's safe to leave these settings alone. +

+

+This entire panel is only relevant to SSH protocol version 2; none of these settings affect SSH-1 at all. +

+

4.20.1 Key exchange algorithm selection

+

+PuTTY supports a variety of SSH-2 key exchange methods, and allows you to choose which one you prefer to use; configuration is similar to cipher selection (see section 4.22). +

+

+PuTTY currently supports the following key exchange methods: +

+
  • +‘ECDH’: elliptic curve Diffie-Hellman key exchange. +
    • +
  • +‘Group 14’: Diffie-Hellman key exchange with a well-known 2048-bit group. +
    • +
  • +‘Group 1’: Diffie-Hellman key exchange with a well-known 1024-bit group. We no longer recommend using this method, and it's not used by default in new installations; however, it may be the only method supported by very old server software. +
    • +
  • +‘Group exchange’: with this method, instead of using a fixed group, PuTTY requests that the server suggest a group to use for key exchange; the server can avoid groups known to be weak, and possibly invent new ones over time, without any changes required to PuTTY's configuration. We recommend use of this method instead of the well-known groups, if possible. +
    • +
  • +‘RSA key exchange’: this requires much less computational effort on the part of the client, and somewhat less on the part of the server, than Diffie-Hellman key exchange. +
    • +
  • +‘GSSAPI key exchange’: see section 4.20.1.1. +
    • +
+

+If the first algorithm PuTTY finds is below the ‘warn below here’ line, you will see a warning box when you make the connection, similar to that for cipher selection (see section 4.22). +

+

4.20.1.1 GSSAPI-based key exchange

+

+PuTTY supports a set of key exchange methods that also incorporates GSSAPI-based authentication. They are enabled with the ‘Attempt GSSAPI key exchange’ checkbox (which also appears on the ‘GSSAPI’ panel). +

+

+PuTTY can only perform the GSSAPI-authenticated key exchange methods when using Kerberos V5, and not other GSSAPI mechanisms. If the user running PuTTY has current Kerberos V5 credentials, then PuTTY will select the GSSAPI key exchange methods in preference to any of the ordinary SSH key exchange methods configured in the preference list. +

+

+The advantage of doing GSSAPI authentication as part of the SSH key exchange is apparent when you are using credential delegation (see section 4.24.1). The SSH key exchange can be repeated later in the session, and this allows your Kerberos V5 credentials (which are typically short-lived) to be automatically re-delegated to the server when they are refreshed on the client. (This feature is commonly referred to as ‘cascading credentials’.) +

+

+If your server doesn't support GSSAPI key exchange, it may still support GSSAPI in the SSH user authentication phase. This will still let you log in using your Kerberos credentials, but will only allow you to delegate the credentials that are active at the beginning of the session; they can't be refreshed automatically later, in a long-running session. +

+

+Another effect of GSSAPI key exchange is that it replaces the usual SSH mechanism of permanent host keys described in section 2.2. So if you use this method, then you won't be asked any interactive questions about whether to accept the server's host key. Instead, the Kerberos exchange will verify the identity of the host you connect to, at the same time as verifying your identity to it. +

+

4.20.2 Repeat key exchange

+

+If the session key negotiated at connection startup is used too much or for too long, it may become feasible to mount attacks against the SSH connection. Therefore, the SSH-2 protocol specifies that a new key exchange should take place every so often; this can be initiated by either the client or the server. +

+

+While this renegotiation is taking place, no data can pass through the SSH connection, so it may appear to ‘freeze’. (The occurrence of repeat key exchange is noted in the Event Log; see section 3.1.3.1.) Usually the same algorithm is used as at the start of the connection, with a similar overhead. +

+

+These options control how often PuTTY will initiate a repeat key exchange (‘rekey’). You can also force a key exchange at any time from the Special Commands menu (see section 3.1.3.2). +

+
  • +‘Max minutes before rekey’ specifies the amount of time that is allowed to elapse before a rekey is initiated. If this is set to zero, PuTTY will not rekey due to elapsed time. The SSH-2 protocol specification recommends a timeout of at most 60 minutes. +
    • +
+

+You might have a need to disable time-based rekeys completely for the same reasons that keepalives aren't always helpful. If you anticipate suffering a network dropout of several hours in the middle of an SSH connection, but were not actually planning to send data down that connection during those hours, then an attempted rekey in the middle of the dropout will probably cause the connection to be abandoned, whereas if rekeys are disabled then the connection should in principle survive (in the absence of interfering firewalls). See section 4.14.1 for more discussion of these issues; for these purposes, rekeys have much the same properties as keepalives. (Except that rekeys have cryptographic value in themselves, so you should bear that in mind when deciding whether to turn them off.) Note, however, the the SSH server can still initiate rekeys. +

+
  • +‘Minutes between GSSAPI checks’, if you're using GSSAPI key exchange, specifies how often the GSSAPI credential cache is checked to see whether new tickets are available for delegation, or current ones are near expiration. If forwarding of GSSAPI credentials is enabled, PuTTY will try to rekey as necessary to keep the delegated credentials from expiring. Frequent checks are recommended; rekeying only happens when needed. +
    • +
  • +‘Max data before rekey’ specifies the amount of data (in bytes) that is permitted to flow in either direction before a rekey is initiated. If this is set to zero, PuTTY will not rekey due to transferred data. The SSH-2 protocol specification recommends a limit of at most 1 gigabyte. +

    +As well as specifying a value in bytes, the following shorthand can be used: +

    +
    • +‘1k’ specifies 1 kilobyte (1024 bytes). +
      • +
    • +‘1M’ specifies 1 megabyte (1024 kilobytes). +
      • +
    • +‘1G’ specifies 1 gigabyte (1024 megabytes). +
      • +
    + +
    • +
+

+Disabling data-based rekeys entirely is a bad idea. The integrity, and to a lesser extent, confidentiality of the SSH-2 protocol depend in part on rekeys occurring before a 32-bit packet sequence number wraps around. Unlike time-based rekeys, data-based rekeys won't occur when the SSH connection is idle, so they shouldn't cause the same problems. The SSH-1 protocol, incidentally, has even weaker integrity protection than SSH-2 without rekeys. +

+

4.21 The Host Keys panel

+

+The Host Keys panel allows you to configure options related to SSH-2 host key management. +

+

+Host keys are used to prove the server's identity, and assure you that the server is not being spoofed (either by a man-in-the-middle attack or by completely replacing it on the network). See section 2.2 for a basic introduction to host keys. +

+

+This entire panel is only relevant to SSH protocol version 2; none of these settings affect SSH-1 at all. +

+

4.21.1 Host key type selection

+

+PuTTY supports a variety of SSH-2 host key types, and allows you to choose which one you prefer to use to identify the server. Configuration is similar to cipher selection (see section 4.22). +

+

+PuTTY currently supports the following host key types: +

+
  • +‘Ed25519’: Edwards-curve DSA using a twisted Edwards curve with modulus 2^255-19. +
    • +
  • +‘ECDSA’: elliptic curve DSA using one of the NIST-standardised elliptic curves. +
    • +
  • +‘DSA’: straightforward DSA using modular exponentiation. +
    • +
  • +‘RSA’: the ordinary RSA algorithm. +
    • +
+

+If PuTTY already has one or more host keys stored for the server, it will prefer to use one of those, even if the server has a key type that is higher in the preference order. You can add such a key to PuTTY's cache from within an existing session using the ‘Special Commands’ menu; see section 3.1.3.2. +

+

+Otherwise, PuTTY will choose a key type based purely on the preference order you specify in the configuration. +

+

+If the first key type PuTTY finds is below the ‘warn below here’ line, you will see a warning box when you make the connection, similar to that for cipher selection (see section 4.22). +

+

4.21.2 Manually configuring host keys

+

+In some situations, if PuTTY's automated host key management is not doing what you need, you might need to manually configure PuTTY to accept a specific host key, or one of a specific set of host keys. +

+

+One reason why you might want to do this is because the host name PuTTY is connecting to is using round-robin DNS to return one of multiple actual servers, and they all have different host keys. In that situation, you might need to configure PuTTY to accept any of a list of host keys for the possible servers, while still rejecting any key not in that list. +

+

+Another reason is if PuTTY's automated host key management is completely unavailable, e.g. because PuTTY (or Plink or PSFTP, etc) is running in a Windows environment without access to the Registry. In that situation, you will probably want to use the -hostkey command-line option to configure the expected host key(s); see section 3.8.3.20. +

+

+For situations where PuTTY's automated host key management simply picks the wrong host name to store a key under, you may want to consider setting a ‘logical host name’ instead; see section 4.14.5. +

+

+To configure manual host keys via the GUI, enter some text describing the host key into the edit box in the ‘Manually configure host keys for this connection’ container, and press the ‘Add’ button. The text will appear in the ‘Host keys or fingerprints to accept’ list box. You can remove keys again with the ‘Remove’ button. +

+

+The text describing a host key can be in one of the following formats: +

+
  • +An MD5-based host key fingerprint of the form displayed in PuTTY's Event Log and host key dialog boxes, i.e. sixteen 2-digit hex numbers separated by colons. +
    • +
  • +A base64-encoded blob describing an SSH-2 public key in OpenSSH's one-line public key format. How you acquire a public key in this format is server-dependent; on an OpenSSH server it can typically be found in a location like /etc/ssh/ssh_host_rsa_key.pub. +
    • +
+

+If this box contains at least one host key or fingerprint when PuTTY makes an SSH connection, then PuTTY's automated host key management is completely bypassed: the connection will be permitted if and only if the host key presented by the server is one of the keys listed in this box, and the host key store in the Registry will be neither read nor written, unless you explicitly do so. +

+

+If the box is empty (as it usually is), then PuTTY's automated host key management will work as normal. +

+

4.22 The Cipher panel

+

+PuTTY supports a variety of different encryption algorithms, and allows you to choose which one you prefer to use. You can do this by dragging the algorithms up and down in the list box (or moving them using the Up and Down buttons) to specify a preference order. When you make an SSH connection, PuTTY will search down the list from the top until it finds an algorithm supported by the server, and then use that. +

+

+PuTTY currently supports the following algorithms: +

+
  • +ChaCha20-Poly1305, a combined cipher and MAC (SSH-2 only) +
    • +
  • +AES (Rijndael) - 256, 192, or 128-bit SDCTR or CBC (SSH-2 only) +
    • +
  • +Arcfour (RC4) - 256 or 128-bit stream cipher (SSH-2 only) +
    • +
  • +Blowfish - 256-bit SDCTR (SSH-2 only) or 128-bit CBC +
    • +
  • +Triple-DES - 168-bit SDCTR (SSH-2 only) or CBC +
    • +
  • +Single-DES - 56-bit CBC (see below for SSH-2) +
    • +
+

+If the algorithm PuTTY finds is below the ‘warn below here’ line, you will see a warning box when you make the connection: +

+
The first cipher supported by the server
+is single-DES, which is below the configured
+warning threshold.
+Do you want to continue with this connection?
+
+

+This warns you that the first available encryption is not a very secure one. Typically you would put the ‘warn below here’ line between the encryptions you consider secure and the ones you consider substandard. By default, PuTTY supplies a preference order intended to reflect a reasonable preference in terms of security and speed. +

+

+In SSH-2, the encryption algorithm is negotiated independently for each direction of the connection, although PuTTY does not support separate configuration of the preference orders. As a result you may get two warnings similar to the one above, possibly with different encryptions. +

+

+Single-DES is not recommended in the SSH-2 protocol standards, but one or two server implementations do support it. PuTTY can use single-DES to interoperate with these servers if you enable the ‘Enable legacy use of single-DES in SSH-2’ option; by default this is disabled and PuTTY will stick to recommended ciphers. +

+

4.23 The Auth panel

+

+The Auth panel allows you to configure authentication options for SSH sessions. +

+

4.23.1 ‘Display pre-authentication banner’

+

+SSH-2 servers can provide a message for clients to display to the prospective user before the user logs in; this is sometimes known as a pre-authentication ‘banner’. Typically this is used to provide information about the server and legal notices. +

+

+By default, PuTTY displays this message before prompting for a password or similar credentials (although, unfortunately, not before prompting for a login name, due to the nature of the protocol design). By unchecking this option, display of the banner can be suppressed entirely. +

+

4.23.2 ‘Bypass authentication entirely’

+

+In SSH-2, it is in principle possible to establish a connection without using SSH's mechanisms to identify or prove who you are to the server. An SSH server could prefer to handle authentication in the data channel, for instance, or simply require no user authentication whatsoever. +

+

+By default, PuTTY assumes the server requires authentication (we've never heard of one that doesn't), and thus must start this process with a username. If you find you are getting username prompts that you cannot answer, you could try enabling this option. However, most SSH servers will reject this. +

+

+This is not the option you want if you have a username and just want PuTTY to remember it; for that see section 4.15.1. It's also probably not what if you're trying to set up passwordless login to a mainstream SSH server; depending on the server, you probably wanted public-key authentication (chapter 8) or perhaps GSSAPI authentication (section 4.24). (These are still forms of authentication, even if you don't have to interact with them.) +

+

+This option only affects SSH-2 connections. SSH-1 connections always require an authentication step. +

+

4.23.3 ‘Attempt authentication using Pageant’

+

+If this option is enabled, then PuTTY will look for Pageant (the SSH private-key storage agent) and attempt to authenticate with any suitable public keys Pageant currently holds. +

+

+This behaviour is almost always desirable, and is therefore enabled by default. In rare cases you might need to turn it off in order to force authentication by some non-public-key method such as passwords. +

+

+This option can also be controlled using the -noagent command-line option. See section 3.8.3.9. +

+

+See chapter 9 for more information about Pageant in general. +

+

4.23.4 ‘Attempt TIS or CryptoCard authentication’

+

+TIS and CryptoCard authentication are (despite their names) generic forms of simple challenge/response authentication available in SSH protocol version 1 only. You might use them if you were using S/Key one-time passwords, for example, or if you had a physical security token that generated responses to authentication challenges. They can even be used to prompt for simple passwords. +

+

+With this switch enabled, PuTTY will attempt these forms of authentication if the server is willing to try them. You will be presented with a challenge string (which may be different every time) and must supply the correct response in order to log in. If your server supports this, you should talk to your system administrator about precisely what form these challenges and responses take. +

+

4.23.5 ‘Attempt keyboard-interactive authentication’

+

+The SSH-2 equivalent of TIS authentication is called ‘keyboard-interactive’. It is a flexible authentication method using an arbitrary sequence of requests and responses; so it is not only useful for challenge/response mechanisms such as S/Key, but it can also be used for (for example) asking the user for a new password when the old one has expired. +

+

+PuTTY leaves this option enabled by default, but supplies a switch to turn it off in case you should have trouble with it. +

+

4.23.6 ‘Allow agent forwarding’

+

+This option allows the SSH server to open forwarded connections back to your local copy of Pageant. If you are not running Pageant, this option will do nothing. +

+

+See chapter 9 for general information on Pageant, and section 9.4 for information on agent forwarding. Note that there is a security risk involved with enabling this option; see section 9.5 for details. +

+

4.23.7 ‘Allow attempted changes of username in SSH-2’

+

+In the SSH-1 protocol, it is impossible to change username after failing to authenticate. So if you mis-type your username at the PuTTY ‘login as:’ prompt, you will not be able to change it except by restarting PuTTY. +

+

+The SSH-2 protocol does allow changes of username, in principle, but does not make it mandatory for SSH-2 servers to accept them. In particular, OpenSSH does not accept a change of username; once you have sent one username, it will reject attempts to try to authenticate as another user. (Depending on the version of OpenSSH, it may quietly return failure for all login attempts, or it may send an error message.) +

+

+For this reason, PuTTY will by default not prompt you for your username more than once, in case the server complains. If you know your server can cope with it, you can enable the ‘Allow attempted changes of username’ option to modify PuTTY's behaviour. +

+

4.23.8 ‘Private key file for authentication’

+

+This box is where you enter the name of your private key file if you are using public key authentication. See chapter 8 for information about public key authentication in SSH. +

+

+This key must be in PuTTY's native format (*.PPK). If you have a private key in another format that you want to use with PuTTY, see section 8.2.12. +

+

+You can use the authentication agent Pageant so that you do not need to explicitly configure a key here; see chapter 9. +

+

+If a private key file is specified here with Pageant running, PuTTY will first try asking Pageant to authenticate with that key, and ignore any other keys Pageant may have. If that fails, PuTTY will ask for a passphrase as normal. You can also specify a public key file in this case (in RFC 4716 or OpenSSH format), as that's sufficient to identify the key to Pageant, but of course if Pageant isn't present PuTTY can't fall back to using this file itself. +

+

4.24 The GSSAPI panel

+

+The ‘GSSAPI’ subpanel of the ‘Auth’ panel controls the use of GSSAPI authentication. This is a mechanism which delegates the authentication exchange to a library elsewhere on the client machine, which in principle can authenticate in many different ways but in practice is usually used with the Kerberos single sign-on protocol to implement passwordless login. +

+

+GSSAPI authentication is only available in the SSH-2 protocol. +

+

+PuTTY supports two forms of GSSAPI-based authentication. In one of them, the SSH key exchange happens in the normal way, and GSSAPI is only involved in authenticating the user. The checkbox labelled ‘Attempt GSSAPI authentication’ controls this form. +

+

+In the other method, GSSAPI-based authentication is combined with the SSH key exchange phase. If this succeeds, then the SSH authentication step has nothing left to do. See section 4.20.1.1 for more information about this method. The checkbox labelled ‘Attempt GSSAPI key exchange’ controls this form. (The same checkbox appears on the ‘Kex’ panel.) +

+

+If one or both of these controls is enabled, then GSSAPI authentication will be attempted in one form or the other, and (typically) if your client machine has valid Kerberos credentials loaded, then PuTTY should be able to authenticate automatically to servers that support Kerberos logins. +

+

+If both of those checkboxes are disabled, PuTTY will not try any form of GSSAPI at all, and the rest of this panel will be unused. +

+

4.24.1 ‘Allow GSSAPI credential delegation’

+

+GSSAPI credential delegation is a mechanism for passing on your Kerberos (or other) identity to the session on the SSH server. If you enable this option, then not only will PuTTY be able to log in automatically to a server that accepts your Kerberos credentials, but also you will be able to connect out from that server to other Kerberos-supporting services and use the same credentials just as automatically. +

+

+(This option is the Kerberos analogue of SSH agent forwarding; see section 9.4 for some information on that.) +

+

+Note that, like SSH agent forwarding, there is a security implication in the use of this option: the administrator of the server you connect to, or anyone else who has cracked the administrator account on that server, could fake your identity when connecting to further Kerberos-supporting services. However, Kerberos sites are typically run by a central authority, so the administrator of one server is likely to already have access to the other services too; so this would typically be less of a risk than SSH agent forwarding. +

+

+If your connection is not using GSSAPI key exchange, it is possible for the delegation to expire during your session. See section 4.20.1.1 for more information. +

+

4.24.2 Preference order for GSSAPI libraries

+

+GSSAPI is a mechanism which allows more than one authentication method to be accessed through the same interface. Therefore, more than one authentication library may exist on your system which can be accessed using GSSAPI. +

+

+PuTTY contains native support for a few well-known such libraries (including Windows' SSPI), and will look for all of them on your system and use whichever it finds. If more than one exists on your system and you need to use a specific one, you can adjust the order in which it will search using this preference list control. +

+

+One of the options in the preference list is to use a user-specified GSSAPI library. If the library you want to use is not mentioned by name in PuTTY's list of options, you can enter its full pathname in the ‘User-supplied GSSAPI library path’ field, and move the ‘User-supplied GSSAPI library’ option in the preference list to make sure it is selected before anything else. +

+

+On Windows, such libraries are files with a .dll extension, and must have been built in the same way as the PuTTY executable you're running; if you have a 32-bit DLL, you must run a 32-bit version of PuTTY, and the same with 64-bit (see question A.6.10). On Unix, shared libraries generally have a .so extension. +

+

4.25 The TTY panel

+

+The TTY panel lets you configure the remote pseudo-terminal. +

+

4.25.1 ‘Don't allocate a pseudo-terminal’

+

+When connecting to a Unix system, most interactive shell sessions are run in a pseudo-terminal, which allows the Unix system to pretend it's talking to a real physical terminal device but allows the SSH server to catch all the data coming from that fake device and send it back to the client. +

+

+Occasionally you might find you have a need to run a session not in a pseudo-terminal. In PuTTY, this is generally only useful for very specialist purposes; although in Plink (see chapter 7) it is the usual way of working. +

+

4.25.2 Sending terminal modes

+

+The SSH protocol allows the client to send ‘terminal modes’ for the remote pseudo-terminal. These usually control the server's expectation of the local terminal's behaviour. +

+

+If your server does not have sensible defaults for these modes, you may find that changing them here helps, although the server is at liberty to ignore your changes. If you don't understand any of this, it's safe to leave these settings alone. +

+

+(None of these settings will have any effect if no pseudo-terminal is requested or allocated.) +

+

+You can change what happens for a particular mode by selecting it in the list, choosing one of the options and specifying the exact value if necessary, and hitting ‘Set’. The effect of the options is as follows: +

+
  • +If the ‘Auto’ option is selected, the PuTTY tools will decide whether to specify that mode to the server, and if so, will send a sensible value. +

    +PuTTY proper will send modes that it has an opinion on (currently only the code for the Backspace key, ERASE, and whether the character set is UTF-8, IUTF8). Plink on Unix will propagate appropriate modes from the local terminal, if any. +

    + +
    • +
  • +If ‘Nothing’ is selected, no value for the mode will be specified to the server under any circumstances. +
    • +
  • +If a value is specified, it will be sent to the server under all circumstances. The precise syntax of the value box depends on the mode. +
    • +
+

+By default, all of the available modes are listed as ‘Auto’, which should do the right thing in most circumstances. +

+

+The precise effect of each setting, if any, is up to the server. Their names come from POSIX and other Unix systems, and they are most likely to have a useful effect on such systems. (These are the same settings that can usually be changed using the stty command once logged in to such servers.) +

+

+Some notable modes are described below; for fuller explanations, see your server documentation. +

+
  • +ERASE is the character that when typed by the user will delete one space to the left. When set to ‘Auto’ (the default setting), this follows the setting of the local Backspace key in PuTTY (see section 4.4.1). +

    +This and other special characters are specified using ^C notation for Ctrl-C, and so on. Use ^<27> or ^<0x1B> to specify a character numerically, and ^~ to get a literal ^. Other non-control characters are denoted by themselves. Leaving the box entirely blank indicates that no character should be assigned to the specified function, although this may not be supported by all servers. +

    + +
    • +
  • +QUIT is a special character that usually forcefully ends the current process on the server (SIGQUIT). On many servers its default setting is Ctrl-backslash (^\), which is easy to accidentally invoke on many keyboards. If this is getting in your way, you may want to change it to another character or turn it off entirely. +
    • +
  • +Boolean modes such as ECHO and ICANON can be specified in PuTTY in a variety of ways, such as true/false, yes/no, and 0/1. (Explicitly specifying a value of no is different from not sending the mode at all.) +
    • +
  • +The boolean mode IUTF8 signals to the server whether the terminal character set is UTF-8 or not, for purposes such as basic line editing; if this is set incorrectly, the backspace key may erase the wrong amount of text, for instance. However, simply setting this is not usually sufficient for the server to use UTF-8; POSIX servers will generally also require the locale to be set (by some server-dependent means), although many newer installations default to UTF-8. Also, since this mode was added to the SSH protocol much later than the others, many servers (particularly older servers) do not honour this mode sent over SSH; indeed, a few poorly-written servers object to its mere presence, so you may find you need to set it to not be sent at all. When set to ‘Auto’, this follows the local configured character set (see section 4.10.1). +
    • +
  • +Terminal speeds are configured elsewhere; see section 4.15.4. +
    • +
+

4.26 The X11 panel

+

+The X11 panel allows you to configure forwarding of X11 over an SSH connection. +

+

+If your server lets you run X Window System graphical applications, X11 forwarding allows you to securely give those applications access to a local X display on your PC. +

+

+To enable X11 forwarding, check the ‘Enable X11 forwarding’ box. If your X display is somewhere unusual, you will need to enter its location in the ‘X display location’ box; if this is left blank, PuTTY will try to find a sensible default in the environment, or use the primary local display (:0) if that fails. +

+

+See section 3.4 for more information about X11 forwarding. +

+

4.26.1 Remote X11 authentication

+

+If you are using X11 forwarding, the virtual X server created on the SSH server machine will be protected by authorisation data. This data is invented, and checked, by PuTTY. +

+

+The usual authorisation method used for this is called MIT-MAGIC-COOKIE-1. This is a simple password-style protocol: the X client sends some cookie data to the server, and the server checks that it matches the real cookie. The cookie data is sent over an unencrypted X11 connection; so if you allow a client on a third machine to access the virtual X server, then the cookie will be sent in the clear. +

+

+PuTTY offers the alternative protocol XDM-AUTHORIZATION-1. This is a cryptographically authenticated protocol: the data sent by the X client is different every time, and it depends on the IP address and port of the client's end of the connection and is also stamped with the current time. So an eavesdropper who captures an XDM-AUTHORIZATION-1 string cannot immediately re-use it for their own X connection. +

+

+PuTTY's support for XDM-AUTHORIZATION-1 is a somewhat experimental feature, and may encounter several problems: +

+
  • +Some X clients probably do not even support XDM-AUTHORIZATION-1, so they will not know what to do with the data PuTTY has provided. +
    • +
  • +This authentication mechanism will only work in SSH-2. In SSH-1, the SSH server does not tell the client the source address of a forwarded connection in a machine-readable format, so it's impossible to verify the XDM-AUTHORIZATION-1 data. +
    • +
  • +You may find this feature causes problems with some SSH servers, which will not clean up XDM-AUTHORIZATION-1 data after a session, so that if you then connect to the same server using a client which only does MIT-MAGIC-COOKIE-1 and are allocated the same remote display number, you might find that out-of-date authentication data is still present on your server and your X connections fail. +
    • +
+

+PuTTY's default is MIT-MAGIC-COOKIE-1. If you change it, you should be sure you know what you're doing. +

+

4.26.2 X authority file for local display

+

+If you are using X11 forwarding, the local X server to which your forwarded connections are eventually directed may itself require authorisation. +

+

+Some Windows X servers do not require this: they do authorisation by simpler means, such as accepting any connection from the local machine but not from anywhere else. However, if your X server does require authorisation, then PuTTY needs to know what authorisation is required. +

+

+One way in which this data might be made available is for the X server to store it somewhere in a file which has the same format as the Unix .Xauthority file. If this is how your Windows X server works, then you can tell PuTTY where to find this file by configuring this option. By default, PuTTY will not attempt to find any authorisation for your local display. +

+

4.27 The Tunnels panel

+

+The Tunnels panel allows you to configure tunnelling of arbitrary connection types through an SSH connection. +

+

+Port forwarding allows you to tunnel other types of network connection down an SSH session. See section 3.5 for a general discussion of port forwarding and how it works. +

+

+The port forwarding section in the Tunnels panel shows a list of all the port forwardings that PuTTY will try to set up when it connects to the server. By default no port forwardings are set up, so this list is empty. +

+

+To add a port forwarding: +

+
  • +Set one of the ‘Local’ or ‘Remote’ radio buttons, depending on whether you want to forward a local port to a remote destination (‘Local’) or forward a remote port to a local destination (‘Remote’). Alternatively, select ‘Dynamic’ if you want PuTTY to provide a local SOCKS 4/4A/5 proxy on a local port (note that this proxy only supports TCP connections; the SSH protocol does not support forwarding UDP). +
    • +
  • +Enter a source port number into the ‘Source port’ box. For local forwardings, PuTTY will listen on this port of your PC. For remote forwardings, your SSH server will listen on this port of the remote machine. Note that most servers will not allow you to listen on port numbers less than 1024. +
    • +
  • +If you have selected ‘Local’ or ‘Remote’ (this step is not needed with ‘Dynamic’), enter a hostname and port number separated by a colon, in the ‘Destination’ box. Connections received on the source port will be directed to this destination. For example, to connect to a POP-3 server, you might enter popserver.example.com:110. (If you need to enter a literal IPv6 address, enclose it in square brackets, for instance ‘[::1]:2200’.) +
    • +
  • +Click the ‘Add’ button. Your forwarding details should appear in the list box. +
    • +
+

+To remove a port forwarding, simply select its details in the list box, and click the ‘Remove’ button. +

+

+In the ‘Source port’ box, you can also optionally enter an IP address to listen on, by specifying (for instance) 127.0.0.5:79. See section 3.5 for more information on how this works and its restrictions. +

+

+In place of port numbers, you can enter service names, if they are known to the local system. For instance, in the ‘Destination’ box, you could enter popserver.example.com:pop3. +

+

+You can modify the currently active set of port forwardings in mid-session using ‘Change Settings’ (see section 3.1.3.4). If you delete a local or dynamic port forwarding in mid-session, PuTTY will stop listening for connections on that port, so it can be re-used by another program. If you delete a remote port forwarding, note that: +

+
  • +The SSH-1 protocol contains no mechanism for asking the server to stop listening on a remote port. +
    • +
  • +The SSH-2 protocol does contain such a mechanism, but not all SSH servers support it. (In particular, OpenSSH does not support it in any version earlier than 3.9.) +
    • +
+

+If you ask to delete a remote port forwarding and PuTTY cannot make the server actually stop listening on the port, it will instead just start refusing incoming connections on that port. Therefore, although the port cannot be reused by another program, you can at least be reasonably sure that server-side programs can no longer access the service at your end of the port forwarding. +

+

+If you delete a forwarding, any existing connections established using that forwarding remain open. Similarly, changes to global settings such as ‘Local ports accept connections from other hosts’ only take effect on new forwardings. +

+

+If the connection you are forwarding over SSH is itself a second SSH connection made by another copy of PuTTY, you might find the ‘logical host name’ configuration option useful to warn PuTTY of which host key it should be expecting. See section 4.14.5 for details of this. +

+

4.27.1 Controlling the visibility of forwarded ports

+

+The source port for a forwarded connection usually does not accept connections from any machine except the SSH client or server machine itself (for local and remote forwardings respectively). There are controls in the Tunnels panel to change this: +

+
  • +The ‘Local ports accept connections from other hosts’ option allows you to set up local-to-remote port forwardings in such a way that machines other than your client PC can connect to the forwarded port. (This also applies to dynamic SOCKS forwarding.) +
    • +
  • +The ‘Remote ports do the same’ option does the same thing for remote-to-local port forwardings (so that machines other than the SSH server machine can connect to the forwarded port.) Note that this feature is only available in the SSH-2 protocol, and not all SSH-2 servers support it (OpenSSH 3.0 does not, for example). +
    • +
+

4.27.2 Selecting Internet protocol version for forwarded ports

+

+This switch allows you to select a specific Internet protocol (IPv4 or IPv6) for the local end of a forwarded port. By default, it is set on ‘Auto’, which means that: +

+
  • +for a local-to-remote port forwarding, PuTTY will listen for incoming connections in both IPv4 and (if available) IPv6 +
    • +
  • +for a remote-to-local port forwarding, PuTTY will choose a sensible protocol for the outgoing connection. +
    • +
+

+This overrides the general Internet protocol version preference on the Connection panel (see section 4.14.4). +

+

+Note that some operating systems may listen for incoming connections in IPv4 even if you specifically asked for IPv6, because their IPv4 and IPv6 protocol stacks are linked together. Apparently Linux does this, and Windows does not. So if you're running PuTTY on Windows and you tick ‘IPv6’ for a local or dynamic port forwarding, it will only be usable by connecting to it using IPv6; whereas if you do the same on Linux, you can also use it with IPv4. However, ticking ‘Auto’ should always give you a port which you can connect to using either protocol. +

+

4.28 The Bugs and More Bugs panels

+

+Not all SSH servers work properly. Various existing servers have bugs in them, which can make it impossible for a client to talk to them unless it knows about the bug and works around it. +

+

+Since most servers announce their software version number at the beginning of the SSH connection, PuTTY will attempt to detect which bugs it can expect to see in the server and automatically enable workarounds. However, sometimes it will make mistakes; if the server has been deliberately configured to conceal its version number, or if the server is a version which PuTTY's bug database does not know about, then PuTTY will not know what bugs to expect. +

+

+The Bugs and More Bugs panels (there are two because we have so many bug compatibility modes) allow you to manually configure the bugs PuTTY expects to see in the server. Each bug can be configured in three states: +

+
  • +‘Off’: PuTTY will assume the server does not have the bug. +
    • +
  • +‘On’: PuTTY will assume the server does have the bug. +
    • +
  • +‘Auto’: PuTTY will use the server's version number announcement to try to guess whether or not the server has the bug. +
    • +
+

4.28.1 ‘Chokes on SSH-2 ignore messages’

+

+An ignore message (SSH_MSG_IGNORE) is a message in the SSH protocol which can be sent from the client to the server, or from the server to the client, at any time. Either side is required to ignore the message whenever it receives it. PuTTY uses ignore messages in SSH-2 to confuse the encrypted data stream and make it harder to cryptanalyse. It also uses ignore messages for connection keepalives (see section 4.14.1). +

+

+If it believes the server to have this bug, PuTTY will stop using ignore messages. If this bug is enabled when talking to a correct server, the session will succeed, but keepalives will not work and the session might be less cryptographically secure than it could be. +

+

4.28.2 ‘Handles SSH-2 key re-exchange badly’

+

+Some SSH servers cannot cope with repeat key exchange at all, and will ignore attempts by the client to start one. Since PuTTY pauses the session while performing a repeat key exchange, the effect of this would be to cause the session to hang after an hour (unless you have your rekey timeout set differently; see section 4.20.2 for more about rekeys). Other, very old, SSH servers handle repeat key exchange even more badly, and disconnect upon receiving a repeat key exchange request. +

+

+If this bug is detected, PuTTY will never initiate a repeat key exchange. If this bug is enabled when talking to a correct server, the session should still function, but may be less secure than you would expect. +

+

+This is an SSH-2-specific bug. +

+

4.28.3 ‘Chokes on PuTTY's SSH-2 ‘winadj’ requests’

+

+PuTTY sometimes sends a special request to SSH servers in the middle of channel data, with the name winadj@putty.projects.tartarus.org (see section F.1). The purpose of this request is to measure the round-trip time to the server, which PuTTY uses to tune its flow control. The server does not actually have to understand the message; it is expected to send back a SSH_MSG_CHANNEL_FAILURE message indicating that it didn't understand it. (All PuTTY needs for its timing calculations is some kind of response.) +

+

+It has been known for some SSH servers to get confused by this message in one way or another – because it has a long name, or because they can't cope with unrecognised request names even to the extent of sending back the correct failure response, or because they handle it sensibly but fill up the server's log file with pointless spam, or whatever. PuTTY therefore supports this bug-compatibility flag: if it believes the server has this bug, it will never send its ‘winadj@putty.projects.tartarus.org’ request, and will make do without its timing data. +

+

4.28.4 ‘Replies to requests on closed channels’

+

+The SSH protocol as published in RFC 4254 has an ambiguity which arises if one side of a connection tries to close a channel, while the other side simultaneously sends a request within the channel and asks for a reply. RFC 4254 leaves it unclear whether the closing side should reply to the channel request after having announced its intention to close the channel. +

+

+Discussion on the ietf-ssh mailing list in April 2014 formed a clear consensus that the right answer is no. However, because of the ambiguity in the specification, some SSH servers have implemented the other policy; for example, OpenSSH used to until it was fixed. +

+

+Because PuTTY sends channel requests with the ‘want reply’ flag throughout channels' lifetime (see section 4.28.3), it's possible that when connecting to such a server it might receive a reply to a request after it thinks the channel has entirely closed, and terminate with an error along the lines of ‘Received SSH2_MSG_CHANNEL_FAILURE for nonexistent channel 256’. +

+

4.28.5 ‘Ignores SSH-2 maximum packet size’

+

+When an SSH-2 channel is set up, each end announces the maximum size of data packet that it is willing to receive for that channel. Some servers ignore PuTTY's announcement and send packets larger than PuTTY is willing to accept, causing it to report ‘Incoming packet was garbled on decryption’. +

+

+If this bug is detected, PuTTY never allows the channel's flow-control window to grow large enough to allow the server to send an over-sized packet. If this bug is enabled when talking to a correct server, the session will work correctly, but download performance will be less than it could be. +

+

4.28.6 ‘Requires padding on SSH-2 RSA signatures’

+

+Versions below 3.3 of OpenSSH require SSH-2 RSA signatures to be padded with zero bytes to the same length as the RSA key modulus. The SSH-2 specification says that an unpadded signature MUST be accepted, so this is a bug. A typical symptom of this problem is that PuTTY mysteriously fails RSA authentication once in every few hundred attempts, and falls back to passwords. +

+

+If this bug is detected, PuTTY will pad its signatures in the way OpenSSH expects. If this bug is enabled when talking to a correct server, it is likely that no damage will be done, since correct servers usually still accept padded signatures because they're used to talking to OpenSSH. +

+

+This is an SSH-2-specific bug. +

+

4.28.7 ‘Only supports pre-RFC4419 SSH-2 DH GEX’

+

+The SSH key exchange method that uses Diffie-Hellman group exchange was redesigned after its original release, to use a slightly more sophisticated setup message. Almost all SSH implementations switched over to the new version. (PuTTY was one of the last.) A few old servers still only support the old one. +

+

+If this bug is detected, and the client and server negotiate Diffie-Hellman group exchange, then PuTTY will send the old message now known as SSH2_MSG_KEX_DH_GEX_REQUEST_OLD in place of the new SSH2_MSG_KEX_DH_GEX_REQUEST. +

+

+This is an SSH-2-specific bug. +

+

4.28.8 ‘Miscomputes SSH-2 HMAC keys’

+

+Versions 2.3.0 and below of the SSH server software from ssh.com compute the keys for their HMAC message authentication codes incorrectly. A typical symptom of this problem is that PuTTY dies unexpectedly at the beginning of the session, saying ‘Incorrect MAC received on packet’. +

+

+If this bug is detected, PuTTY will compute its HMAC keys in the same way as the buggy server, so that communication will still be possible. If this bug is enabled when talking to a correct server, communication will fail. +

+

+This is an SSH-2-specific bug. +

+

4.28.9 ‘Misuses the session ID in SSH-2 PK auth’

+

+Versions below 2.3 of OpenSSH require SSH-2 public-key authentication to be done slightly differently: the data to be signed by the client contains the session ID formatted in a different way. If public-key authentication mysteriously does not work but the Event Log (see section 3.1.3.1) thinks it has successfully sent a signature, it might be worth enabling the workaround for this bug to see if it helps. +

+

+If this bug is detected, PuTTY will sign data in the way OpenSSH expects. If this bug is enabled when talking to a correct server, SSH-2 public-key authentication will fail. +

+

+This is an SSH-2-specific bug. +

+

4.28.10 ‘Miscomputes SSH-2 encryption keys’

+

+Versions below 2.0.11 of the SSH server software from ssh.com compute the keys for the session encryption incorrectly. This problem can cause various error messages, such as ‘Incoming packet was garbled on decryption’, or possibly even ‘Out of memory’. +

+

+If this bug is detected, PuTTY will compute its encryption keys in the same way as the buggy server, so that communication will still be possible. If this bug is enabled when talking to a correct server, communication will fail. +

+

+This is an SSH-2-specific bug. +

+

4.28.11 ‘Chokes on SSH-1 ignore messages’

+

+An ignore message (SSH_MSG_IGNORE) is a message in the SSH protocol which can be sent from the client to the server, or from the server to the client, at any time. Either side is required to ignore the message whenever it receives it. PuTTY uses ignore messages to hide the password packet in SSH-1, so that a listener cannot tell the length of the user's password; it also uses ignore messages for connection keepalives (see section 4.14.1). +

+

+If this bug is detected, PuTTY will stop using ignore messages. This means that keepalives will stop working, and PuTTY will have to fall back to a secondary defence against SSH-1 password-length eavesdropping. See section 4.28.12. If this bug is enabled when talking to a correct server, the session will succeed, but keepalives will not work and the session might be more vulnerable to eavesdroppers than it could be. +

+

4.28.12 ‘Refuses all SSH-1 password camouflage’

+

+When talking to an SSH-1 server which cannot deal with ignore messages (see section 4.28.11), PuTTY will attempt to disguise the length of the user's password by sending additional padding within the password packet. This is technically a violation of the SSH-1 specification, and so PuTTY will only do it when it cannot use standards-compliant ignore messages as camouflage. In this sense, for a server to refuse to accept a padded password packet is not really a bug, but it does make life inconvenient if the server can also not handle ignore messages. +

+

+If this ‘bug’ is detected, PuTTY will assume that neither ignore messages nor padding are acceptable, and that it thus has no choice but to send the user's password with no form of camouflage, so that an eavesdropping user will be easily able to find out the exact length of the password. If this bug is enabled when talking to a correct server, the session will succeed, but will be more vulnerable to eavesdroppers than it could be. +

+

+This is an SSH-1-specific bug. SSH-2 is secure against this type of attack. +

+

4.28.13 ‘Chokes on SSH-1 RSA authentication’

+

+Some SSH-1 servers cannot deal with RSA authentication messages at all. If Pageant is running and contains any SSH-1 keys, PuTTY will normally automatically try RSA authentication before falling back to passwords, so these servers will crash when they see the RSA attempt. +

+

+If this bug is detected, PuTTY will go straight to password authentication. If this bug is enabled when talking to a correct server, the session will succeed, but of course RSA authentication will be impossible. +

+

+This is an SSH-1-specific bug. +

+

4.29 The Serial panel

+

+The Serial panel allows you to configure options that only apply when PuTTY is connecting to a local serial line. +

+

4.29.1 Selecting a serial line to connect to

+

+The ‘Serial line to connect to’ box allows you to choose which serial line you want PuTTY to talk to, if your computer has more than one serial port. +

+

+On Windows, the first serial line is called COM1, and if there is a second it is called COM2, and so on. +

+

+This configuration setting is also visible on the Session panel, where it replaces the ‘Host Name’ box (see section 4.1.1) if the connection type is set to ‘Serial’. +

+

4.29.2 Selecting the speed of your serial line

+

+The ‘Speed’ box allows you to choose the speed (or ‘baud rate’) at which to talk to the serial line. Typical values might be 9600, 19200, 38400 or 57600. Which one you need will depend on the device at the other end of the serial cable; consult the manual for that device if you are in doubt. +

+

+This configuration setting is also visible on the Session panel, where it replaces the ‘Port’ box (see section 4.1.1) if the connection type is set to ‘Serial’. +

+

4.29.3 Selecting the number of data bits

+

+The ‘Data bits’ box allows you to choose how many data bits are transmitted in each byte sent or received through the serial line. Typical values are 7 or 8. +

+

4.29.4 Selecting the number of stop bits

+

+The ‘Stop bits’ box allows you to choose how many stop bits are used in the serial line protocol. Typical values are 1, 1.5 or 2. +

+

4.29.5 Selecting the serial parity checking scheme

+

+The ‘Parity’ box allows you to choose what type of parity checking is used on the serial line. The settings are: +

+
  • +‘None’: no parity bit is sent at all. +
    • +
  • +‘Odd’: an extra parity bit is sent alongside each byte, and arranged so that the total number of 1 bits is odd. +
    • +
  • +‘Even’: an extra parity bit is sent alongside each byte, and arranged so that the total number of 1 bits is even. +
    • +
  • +‘Mark’: an extra parity bit is sent alongside each byte, and always set to 1. +
    • +
  • +‘Space’: an extra parity bit is sent alongside each byte, and always set to 0. +
    • +
+

4.29.6 Selecting the serial flow control scheme

+

+The ‘Flow control’ box allows you to choose what type of flow control checking is used on the serial line. The settings are: +

+
  • +‘None’: no flow control is done. Data may be lost if either side attempts to send faster than the serial line permits. +
    • +
  • +‘XON/XOFF’: flow control is done by sending XON and XOFF characters within the data stream. +
    • +
  • +‘RTS/CTS’: flow control is done using the RTS and CTS wires on the serial line. +
    • +
  • +‘DSR/DTR’: flow control is done using the DSR and DTR wires on the serial line. +
    • +
+

4.30 Storing configuration in a file

+

+PuTTY does not currently support storing its configuration in a file instead of the Registry. However, you can work around this with a couple of batch files. +

+

+You will need a file called (say) PUTTY.BAT which imports the contents of a file into the Registry, then runs PuTTY, exports the contents of the Registry back into the file, and deletes the Registry entries. This can all be done using the Regedit command line options, so it's all automatic. Here is what you need in PUTTY.BAT: +

+
@ECHO OFF
+regedit /s putty.reg
+regedit /s puttyrnd.reg
+start /w putty.exe
+regedit /ea new.reg HKEY_CURRENT_USER\Software\SimonTatham\PuTTY
+copy new.reg putty.reg
+del new.reg
+regedit /s puttydel.reg
+
+

+This batch file needs two auxiliary files: PUTTYRND.REG which sets up an initial safe location for the PUTTY.RND random seed file, and PUTTYDEL.REG which destroys everything in the Registry once it's been successfully saved back to the file. +

+

+Here is PUTTYDEL.REG: +

+
REGEDIT4
+ 
+[-HKEY_CURRENT_USER\Software\SimonTatham\PuTTY]
+
+

+Here is an example PUTTYRND.REG file: +

+
REGEDIT4
+ 
+[HKEY_CURRENT_USER\Software\SimonTatham\PuTTY]
+"RandSeedFile"="a:\\putty.rnd"
+
+

+You should replace a:\putty.rnd with the location where you want to store your random number data. If the aim is to carry around PuTTY and its settings on one USB stick, you probably want to store it on the USB stick. +

+ +

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/Chapter5.html b/doc/Chapter5.html new file mode 100644 index 0000000..5724a89 --- /dev/null +++ b/doc/Chapter5.html @@ -0,0 +1,268 @@ + + + + +Using PSCP to transfer files securely + + + + + + + +

Previous | Contents | Index | Next

+ + +

Chapter 5: Using PSCP to transfer files securely

+

+PSCP, the PuTTY Secure Copy client, is a tool for transferring files securely between computers using an SSH connection. +

+

+If you have an SSH-2 server, you might prefer PSFTP (see chapter 6) for interactive use. PSFTP does not in general work with SSH-1 servers, however. +

+

5.1 Starting PSCP

+

+PSCP is a command line application. This means that you cannot just double-click on its icon to run it and instead you have to bring up a console window. With Windows 95, 98, and ME, this is called an ‘MS-DOS Prompt’ and with Windows NT, 2000, and XP, it is called a ‘Command Prompt’. It should be available from the Programs section of your Start Menu. +

+

+To start PSCP it will need either to be on your PATH or in your current directory. To add the directory containing PSCP to your PATH environment variable, type into the console window: +

+
set PATH=C:\path\to\putty\directory;%PATH%
+
+

+This will only work for the lifetime of that particular console window. To set your PATH more permanently on Windows NT, 2000, and XP, use the Environment tab of the System Control Panel. On Windows 95, 98, and ME, you will need to edit your AUTOEXEC.BAT to include a set command like the one above. +

+

5.2 PSCP Usage

+

+Once you've got a console window to type into, you can just type pscp on its own to bring up a usage message. This tells you the version of PSCP you're using, and gives you a brief summary of how to use PSCP: +

+
Z:\owendadmin>pscp
+PuTTY Secure Copy client
+Release 0.72
+Usage: pscp [options] [user@]host:source target
+       pscp [options] source [source...] [user@]host:target
+       pscp [options] -ls [user@]host:filespec
+Options:
+  -V        print version information and exit
+  -pgpfp    print PGP key fingerprints and exit
+  -p        preserve file attributes
+  -q        quiet, don't show statistics
+  -r        copy directories recursively
+  -v        show verbose messages
+  -load sessname  Load settings from saved session
+  -P port   connect to specified port
+  -l user   connect with specified username
+  -pw passw login with specified password
+  -1 -2     force use of particular SSH protocol version
+  -4 -6     force use of IPv4 or IPv6
+  -C        enable compression
+  -i key    private key file for user authentication
+  -noagent  disable use of Pageant
+  -agent    enable use of Pageant
+  -hostkey aa:bb:cc:...
+            manually specify a host key (may be repeated)
+  -batch    disable all interactive prompts
+  -no-sanitise-stderr  don't strip control chars from standard error
+  -proxycmd command
+            use 'command' as local proxy
+  -unsafe   allow server-side wildcards (DANGEROUS)
+  -sftp     force use of SFTP protocol
+  -scp      force use of SCP protocol
+  -sshlog file
+  -sshrawlog file
+            log protocol details to a file
+
+

+(PSCP's interface is much like the Unix scp command, if you're familiar with that.) +

+

5.2.1 The basics

+

+To receive (a) file(s) from a remote server: +

+
pscp [options] [user@]host:source target
+
+

+So to copy the file /etc/hosts from the server example.com as user fred to the file c:\temp\example-hosts.txt, you would type: +

+
pscp fred@example.com:/etc/hosts c:\temp\example-hosts.txt
+
+

+To send (a) file(s) to a remote server: +

+
pscp [options] source [source...] [user@]host:target
+
+

+So to copy the local file c:\documents\foo.txt to the server example.com as user fred to the file /tmp/foo you would type: +

+
pscp c:\documents\foo.txt fred@example.com:/tmp/foo
+
+

+You can use wildcards to transfer multiple files in either direction, like this: +

+
pscp c:\documents\*.doc fred@example.com:docfiles
+pscp fred@example.com:source/*.c c:\source
+
+

+However, in the second case (using a wildcard for multiple remote files) you may see a warning saying something like ‘warning: remote host tried to write to a file called ‘terminal.c’ when we requested a file called ‘*.c’. If this is a wildcard, consider upgrading to SSH-2 or using the ‘-unsafe’ option. Renaming of this file has been disallowed’. +

+

+This is due to a fundamental insecurity in the old-style SCP protocol: the client sends the wildcard string (*.c) to the server, and the server sends back a sequence of file names that match the wildcard pattern. However, there is nothing to stop the server sending back a different pattern and writing over one of your other files: if you request *.c, the server might send back the file name AUTOEXEC.BAT and install a virus for you. Since the wildcard matching rules are decided by the server, the client cannot reliably verify that the filenames sent back match the pattern. +

+

+PSCP will attempt to use the newer SFTP protocol (part of SSH-2) where possible, which does not suffer from this security flaw. If you are talking to an SSH-2 server which supports SFTP, you will never see this warning. (You can force use of the SFTP protocol, if available, with -sftp - see section 5.2.2.6.) +

+

+If you really need to use a server-side wildcard with an SSH-1 server, you can use the -unsafe command line option with PSCP: +

+
pscp -unsafe fred@example.com:source/*.c c:\source
+
+

+This will suppress the warning message and the file transfer will happen. However, you should be aware that by using this option you are giving the server the ability to write to any file in the target directory, so you should only use this option if you trust the server administrator not to be malicious (and not to let the server machine be cracked by malicious people). Alternatively, do any such download in a newly created empty directory. (Even in ‘unsafe’ mode, PSCP will still protect you against the server trying to get out of that directory using pathnames including ‘..’.) +

+

5.2.1.1 user

+

+The login name on the remote server. If this is omitted, and host is a PuTTY saved session, PSCP will use any username specified by that saved session. Otherwise, PSCP will attempt to use the local Windows username. +

+

5.2.1.2 host

+

+The name of the remote server, or the name of an existing PuTTY saved session. In the latter case, the session's settings for hostname, port number, cipher type and username will be used. +

+

5.2.1.3 source

+

+One or more source files. Wildcards are allowed. The syntax of wildcards depends on the system to which they apply, so if you are copying from a Windows system to a UNIX system, you should use Windows wildcard syntax (e.g. *.*), but if you are copying from a UNIX system to a Windows system, you would use the wildcard syntax allowed by your UNIX shell (e.g. *). +

+

+If the source is a remote server and you do not specify a full pathname (in UNIX, a pathname beginning with a / (slash) character), what you specify as a source will be interpreted relative to your home directory on the remote server. +

+

5.2.1.4 target

+

+The filename or directory to put the file(s). When copying from a remote server to a local host, you may wish simply to place the file(s) in the current directory. To do this, you should specify a target of .. For example: +

+
pscp fred@example.com:/home/tom/.emacs .
+
+

+...would copy /home/tom/.emacs on the remote server to the current directory. +

+

+As with the source parameter, if the target is on a remote server and is not a full path name, it is interpreted relative to your home directory on the remote server. +

+

5.2.2 Options

+

+PSCP accepts all the general command line options supported by the PuTTY tools, except the ones which make no sense in a file transfer utility. See section 3.8.3 for a description of these options. (The ones not supported by PSCP are clearly marked.) +

+

+PSCP also supports some of its own options. The following sections describe PSCP's specific command-line options. +

+

5.2.2.1 -ls list remote files

+

+If the -ls option is given, no files are transferred; instead, remote files are listed. Only a hostname specification and optional remote file specification need be given. For example: +

+
pscp -ls fred@example.com:dir1
+
+

+The SCP protocol does not contain within itself a means of listing files. If SCP is in use, this option therefore assumes that the server responds appropriately to the command ls -la; this may not work with all servers. +

+

+If SFTP is in use, this option should work with all servers. +

+

5.2.2.2 -p preserve file attributes

+

+By default, files copied with PSCP are timestamped with the date and time they were copied. The -p option preserves the original timestamp on copied files. +

+

5.2.2.3 -q quiet, don't show statistics

+

+By default, PSCP displays a meter displaying the progress of the current transfer: +

+
mibs.tar          |   168 kB |  84.0 kB/s | ETA: 00:00:13 |  13%
+
+

+The fields in this display are (from left to right), filename, size (in kilobytes) of file transferred so far, estimate of how fast the file is being transferred (in kilobytes per second), estimated time that the transfer will be complete, and percentage of the file so far transferred. The -q option to PSCP suppresses the printing of these statistics. +

+

5.2.2.4 -r copies directories recursively

+

+By default, PSCP will only copy files. Any directories you specify to copy will be skipped, as will their contents. The -r option tells PSCP to descend into any directories you specify, and to copy them and their contents. This allows you to use PSCP to transfer whole directory structures between machines. +

+

5.2.2.5 -batch avoid interactive prompts

+

+If you use the -batch option, PSCP will never give an interactive prompt while establishing the connection. If the server's host key is invalid, for example (see section 2.2), then the connection will simply be abandoned instead of asking you what to do next. +

+

+This may help PSCP's behaviour when it is used in automated scripts: using -batch, if something goes wrong at connection time, the batch job will fail rather than hang. +

+

5.2.2.6 -sftp, -scp force use of particular protocol

+

+As mentioned in section 5.2.1, there are two different file transfer protocols in use with SSH. Despite its name, PSCP (like many other ostensible scp clients) can use either of these protocols. +

+

+The older SCP protocol does not have a written specification and leaves a lot of detail to the server platform. Wildcards are expanded on the server. The simple design means that any wildcard specification supported by the server platform (such as brace expansion) can be used, but also leads to interoperability issues such as with filename quoting (for instance, where filenames contain spaces), and also the security issue described in section 5.2.1. +

+

+The newer SFTP protocol, which is usually associated with SSH-2 servers, is specified in a more platform independent way, and leaves issues such as wildcard syntax up to the client. (PuTTY's SFTP wildcard syntax is described in section 6.2.2.) This makes it more consistent across platforms, more suitable for scripting and automation, and avoids security issues with wildcard matching. +

+

+Normally PSCP will attempt to use the SFTP protocol, and only fall back to the SCP protocol if SFTP is not available on the server. +

+

+The -scp option forces PSCP to use the SCP protocol or quit. +

+

+The -sftp option forces PSCP to use the SFTP protocol or quit. When this option is specified, PSCP looks harder for an SFTP server, which may allow use of SFTP with SSH-1 depending on server setup. +

+

5.2.2.7 -no-sanitise-stderr: control error message sanitisation

+

+The -no-sanitise-stderr option will cause PSCP to pass through the server's standard-error stream literally, without stripping control characters from it first. This might be useful if the server were sending coloured error messages, but it also gives the server the ability to have unexpected effects on your terminal display. For more discussion, see section 7.2.3.5. +

+

5.2.3 Return value

+

+PSCP returns an ERRORLEVEL of zero (success) only if the files were correctly transferred. You can test for this in a batch file, using code such as this: +

+
pscp file*.* user@hostname:
+if errorlevel 1 echo There was an error
+
+

5.2.4 Using public key authentication with PSCP

+

+Like PuTTY, PSCP can authenticate using a public key instead of a password. There are three ways you can do this. +

+

+Firstly, PSCP can use PuTTY saved sessions in place of hostnames (see section 5.2.1.2). So you would do this: +

+
  • +Run PuTTY, and create a PuTTY saved session (see section 4.1.2) which specifies your private key file (see section 4.23.8). You will probably also want to specify a username to log in as (see section 4.15.1). +
    • +
  • +In PSCP, you can now use the name of the session instead of a hostname: type pscp sessionname:file localfile, where sessionname is replaced by the name of your saved session. +
    • +
+

+Secondly, you can supply the name of a private key file on the command line, with the -i option. See section 3.8.3.18 for more information. +

+

+Thirdly, PSCP will attempt to authenticate using Pageant if Pageant is running (see chapter 9). So you would do this: +

+
  • +Ensure Pageant is running, and has your private key stored in it. +
    • +
  • +Specify a user and host name to PSCP as normal. PSCP will automatically detect Pageant and try to use the keys within it. +
    • +
+

+For more general information on public-key authentication, see chapter 8. +

+ +

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/Chapter6.html b/doc/Chapter6.html new file mode 100644 index 0000000..94621ad --- /dev/null +++ b/doc/Chapter6.html @@ -0,0 +1,539 @@ + + + + +Using PSFTP to transfer files securely + + + + + + + +

Previous | Contents | Index | Next

+ + +

Chapter 6: Using PSFTP to transfer files securely

+

+PSFTP, the PuTTY SFTP client, is a tool for transferring files securely between computers using an SSH connection. +

+

+PSFTP differs from PSCP in the following ways: +

+
  • +PSCP should work on virtually every SSH server. PSFTP uses the new SFTP protocol, which is a feature of SSH-2 only. (PSCP will also use this protocol if it can, but there is an SSH-1 equivalent it can fall back to if it cannot.) +
    • +
  • +PSFTP allows you to run an interactive file transfer session, much like the Windows ftp program. You can list the contents of directories, browse around the file system, issue multiple get and put commands, and eventually log out. By contrast, PSCP is designed to do a single file transfer operation and immediately terminate. +
    • +
+

6.1 Starting PSFTP

+

+The usual way to start PSFTP is from a command prompt, much like PSCP. To do this, it will need either to be on your PATH or in your current directory. To add the directory containing PSFTP to your PATH environment variable, type into the console window: +

+
set PATH=C:\path\to\putty\directory;%PATH%
+
+

+Unlike PSCP, however, PSFTP has no complex command-line syntax; you just specify a host name and perhaps a user name: +

+
psftp server.example.com
+
+

+or perhaps +

+
psftp fred@server.example.com
+
+

+Alternatively, if you just type psftp on its own (or double-click the PSFTP icon in the Windows GUI), you will see the PSFTP prompt, and a message telling you PSFTP has not connected to any server: +

+
C:\>psftp
+psftp: no hostname specified; use "open host.name" to connect
+psftp>
+
+

+At this point you can type open server.example.com or open fred@server.example.com to start a session. +

+

+PSFTP accepts all the general command line options supported by the PuTTY tools, except the ones which make no sense in a file transfer utility. See section 3.8.3 for a description of these options. (The ones not supported by PSFTP are clearly marked.) +

+

+PSFTP also supports some of its own options. The following sections describe PSFTP's specific command-line options. +

+

6.1.1 -b: specify a file containing batch commands

+

+In normal operation, PSFTP is an interactive program which displays a command line and accepts commands from the keyboard. +

+

+If you need to do automated tasks with PSFTP, you would probably prefer to specify a set of commands in advance and have them executed automatically. The -b option allows you to do this. You use it with a file name containing batch commands. For example, you might create a file called myscript.scr containing lines like this: +

+
cd /home/ftp/users/jeff
+del jam-old.tar.gz
+ren jam.tar.gz jam-old.tar.gz
+put jam.tar.gz
+chmod a+r jam.tar.gz
+
+

+and then you could run the script by typing +

+
psftp user@hostname -b myscript.scr
+
+

+When you run a batch script in this way, PSFTP will abort the script if any command fails to complete successfully. To change this behaviour, you can add the -be option (section 6.1.3). +

+

+PSFTP will terminate after it finishes executing the batch script. +

+

6.1.2 -bc: display batch commands as they are run

+

+The -bc option alters what PSFTP displays while processing a batch script specified with -b. With the -bc option, PSFTP will display prompts and commands just as if the commands had been typed at the keyboard. So instead of seeing this: +

+
C:\>psftp fred@hostname -b batchfile
+Sent username "fred"
+Remote working directory is /home/fred
+Listing directory /home/fred/lib
+drwxrwsr-x    4 fred     fred         1024 Sep  6 10:42 .
+drwxr-sr-x   25 fred     fred         2048 Dec 14 09:36 ..
+drwxrwsr-x    3 fred     fred         1024 Apr 17  2000 jed
+lrwxrwxrwx    1 fred     fred           24 Apr 17  2000 timber
+drwxrwsr-x    2 fred     fred         1024 Mar 13  2000 trn
+
+

+you might see this: +

+
C:\>psftp fred@hostname -bc -b batchfile
+Sent username "fred"
+Remote working directory is /home/fred
+psftp> dir lib
+Listing directory /home/fred/lib
+drwxrwsr-x    4 fred     fred         1024 Sep  6 10:42 .
+drwxr-sr-x   25 fred     fred         2048 Dec 14 09:36 ..
+drwxrwsr-x    3 fred     fred         1024 Apr 17  2000 jed
+lrwxrwxrwx    1 fred     fred           24 Apr 17  2000 timber
+drwxrwsr-x    2 fred     fred         1024 Mar 13  2000 trn
+psftp> quit
+
+

6.1.3 -be: continue batch processing on errors

+

+When running a batch file, this additional option causes PSFTP to continue processing even if a command fails to complete successfully. +

+

+You might want this to happen if you wanted to delete a file and didn't care if it was already not present, for example. +

+

6.1.4 -batch: avoid interactive prompts

+

+If you use the -batch option, PSFTP will never give an interactive prompt while establishing the connection. If the server's host key is invalid, for example (see section 2.2), then the connection will simply be abandoned instead of asking you what to do next. +

+

+This may help PSFTP's behaviour when it is used in automated scripts: using -batch, if something goes wrong at connection time, the batch job will fail rather than hang. +

+

6.1.4.1 -no-sanitise-stderr: control error message sanitisation

+

+The -no-sanitise-stderr option will cause PSFTP to pass through the server's standard-error stream literally, without stripping control characters from it first. This might be useful if the server were sending coloured error messages, but it also gives the server the ability to have unexpected effects on your terminal display. For more discussion, see section 7.2.3.5. +

+

6.2 Running PSFTP

+

+Once you have started your PSFTP session, you will see a psftp> prompt. You can now type commands to perform file-transfer functions. This section lists all the available commands. +

+

+Any line starting with a # will be treated as a comment and ignored. +

+

6.2.1 General quoting rules for PSFTP commands

+

+Most PSFTP commands are considered by the PSFTP command interpreter as a sequence of words, separated by spaces. For example, the command ren oldfilename newfilename splits up into three words: ren (the command name), oldfilename (the name of the file to be renamed), and newfilename (the new name to give the file). +

+

+Sometimes you will need to specify file names that contain spaces. In order to do this, you can surround the file name with double quotes. This works equally well for local file names and remote file names: +

+
psftp> get "spacey file name.txt" "save it under this name.txt"
+
+

+The double quotes themselves will not appear as part of the file names; they are removed by PSFTP and their only effect is to stop the spaces inside them from acting as word separators. +

+

+If you need to use a double quote (on some types of remote system, such as Unix, you are allowed to use double quotes in file names), you can do this by doubling it. This works both inside and outside double quotes. For example, this command +

+
psftp> ren ""this"" "a file with ""quotes"" in it"
+
+

+will take a file whose current name is "this" (with a double quote character at the beginning and the end) and rename it to a file whose name is a file with "quotes" in it. +

+

+(The one exception to the PSFTP quoting rules is the ! command, which passes its command line straight to Windows without splitting it up into words at all. See section 6.2.19.) +

+

6.2.2 Wildcards in PSFTP

+

+Several commands in PSFTP support ‘wildcards’ to select multiple files. +

+

+For local file specifications (such as the first argument to put), wildcard rules for the local operating system are used. For instance, PSFTP running on Windows might require the use of *.* where PSFTP on Unix would need *. +

+

+For remote file specifications (such as the first argument to get), PSFTP uses a standard wildcard syntax (similar to POSIX wildcards): +

+
  • +* matches any sequence of characters (including a zero-length sequence). +
    • +
  • +? matches exactly one character. +
    • +
  • +[abc] matches exactly one character which can be a, b, or c. +

    +[a-z] matches any character in the range a to z. +

    +

    +[^abc] matches a single character that is not a, b, or c. +

    +

    +Special cases: [-a] matches a literal hyphen (-) or a; [^-a] matches all other characters. [a^] matches a literal caret (^) or a. +

    + +
    • +
  • +\ (backslash) before any of the above characters (or itself) removes that character's special meaning. +
    • +
+

+A leading period (.) on a filename is not treated specially, unlike in some Unix contexts; get * will fetch all files, whether or not they start with a leading period. +

+

6.2.3 The open command: start a session

+

+If you started PSFTP by double-clicking in the GUI, or just by typing psftp at the command line, you will need to open a connection to an SFTP server before you can issue any other commands (except help and quit). +

+

+To create a connection, type open host.name, or if you need to specify a user name as well you can type open user@host.name. You can optionally specify a port as well: open user@host.name 22. +

+

+Once you have issued this command, you will not be able to issue it again, even if the command fails (for example, if you mistype the host name or the connection times out). So if the connection is not opened successfully, PSFTP will terminate immediately. +

+

6.2.4 The quit command: end your session

+

+When you have finished your session, type the command quit to close the connection, terminate PSFTP and return to the command line (or just close the PSFTP console window if you started it from the GUI). +

+

+You can also use the bye and exit commands, which have exactly the same effect. +

+

6.2.5 The close command: close your connection

+

+If you just want to close the network connection but keep PSFTP running, you can use the close command. You can then use the open command to open a new connection. +

+

6.2.6 The help command: get quick online help

+

+If you type help, PSFTP will give a short list of the available commands. +

+

+If you type help with a command name - for example, help get - then PSFTP will give a short piece of help on that particular command. +

+

6.2.7 The cd and pwd commands: changing the remote working directory

+

+PSFTP maintains a notion of your ‘working directory’ on the server. This is the default directory that other commands will operate on. For example, if you type get filename.dat then PSFTP will look for filename.dat in your remote working directory on the server. +

+

+To change your remote working directory, use the cd command. If you don't provide an argument, cd will return you to your home directory on the server (more precisely, the remote directory you were in at the start of the connection). +

+

+To display your current remote working directory, type pwd. +

+

6.2.8 The lcd and lpwd commands: changing the local working directory

+

+As well as having a working directory on the remote server, PSFTP also has a working directory on your local machine (just like any other Windows process). This is the default local directory that other commands will operate on. For example, if you type get filename.dat then PSFTP will save the resulting file as filename.dat in your local working directory. +

+

+To change your local working directory, use the lcd command. To display your current local working directory, type lpwd. +

+

6.2.9 The get command: fetch a file from the server

+

+To download a file from the server and store it on your local PC, you use the get command. +

+

+In its simplest form, you just use this with a file name: +

+
get myfile.dat
+
+

+If you want to store the file locally under a different name, specify the local file name after the remote one: +

+
get myfile.dat newname.dat
+
+

+This will fetch the file on the server called myfile.dat, but will save it to your local machine under the name newname.dat. +

+

+To fetch an entire directory recursively, you can use the -r option: +

+
get -r mydir
+get -r mydir newname
+
+

+(If you want to fetch a file whose name starts with a hyphen, you may have to use the -- special argument, which stops get from interpreting anything as a switch after it. For example, ‘get -- -silly-name-’.) +

+

6.2.10 The put command: send a file to the server

+

+To upload a file to the server from your local PC, you use the put command. +

+

+In its simplest form, you just use this with a file name: +

+
put myfile.dat
+
+

+If you want to store the file remotely under a different name, specify the remote file name after the local one: +

+
put myfile.dat newname.dat
+
+

+This will send the local file called myfile.dat, but will store it on the server under the name newname.dat. +

+

+To send an entire directory recursively, you can use the -r option: +

+
put -r mydir
+put -r mydir newname
+
+

+(If you want to send a file whose name starts with a hyphen, you may have to use the -- special argument, which stops put from interpreting anything as a switch after it. For example, ‘put -- -silly-name-’.) +

+

6.2.11 The mget and mput commands: fetch or send multiple files

+

+mget works almost exactly like get, except that it allows you to specify more than one file to fetch at once. You can do this in two ways: +

+
  • +by giving two or more explicit file names (‘mget file1.txt file2.txt’) +
    • +
  • +by using a wildcard (‘mget *.txt’). +
    • +
+

+Every argument to mget is treated as the name of a file to fetch (unlike get, which will interpret at most one argument like that, and a second argument will be treated as an alternative name under which to store the retrieved file), or a wildcard expression matching more than one file. +

+

+The -r and -- options from get are also available with mget. +

+

+mput is similar to put, with the same differences. +

+

6.2.12 The reget and reput commands: resuming file transfers

+

+If a file transfer fails half way through, and you end up with half the file stored on your disk, you can resume the file transfer using the reget and reput commands. These work exactly like the get and put commands, but they check for the presence of the half-written destination file and start transferring from where the last attempt left off. +

+

+The syntax of reget and reput is exactly the same as the syntax of get and put: +

+
reget myfile.dat
+reget myfile.dat newname.dat
+reget -r mydir
+
+

+These commands are intended mainly for resuming interrupted transfers. They assume that the remote file or directory structure has not changed in any way; if there have been changes, you may end up with corrupted files. In particular, the -r option will not pick up changes to files or directories already transferred in full. +

+

6.2.13 The dir command: list remote files

+

+To list the files in your remote working directory, just type dir. +

+

+You can also list the contents of a different directory by typing dir followed by the directory name: +

+
dir /home/fred
+dir sources
+
+

+And you can list a subset of the contents of a directory by providing a wildcard: +

+
dir /home/fred/*.txt
+dir sources/*.c
+
+

+The ls command works exactly the same way as dir. +

+

6.2.14 The chmod command: change permissions on remote files

+

+PSFTP allows you to modify the file permissions on files and directories on the server. You do this using the chmod command, which works very much like the Unix chmod command. +

+

+The basic syntax is chmod modes file, where modes represents a modification to the file permissions, and file is the filename to modify. You can specify multiple files or wildcards. For example: +

+
chmod go-rwx,u+w privatefile
+chmod a+r public*
+chmod 640 groupfile1 groupfile2
+
+

+The modes parameter can be a set of octal digits in the Unix style. (If you don't know what this means, you probably don't want to be using it!) Alternatively, it can be a list of permission modifications, separated by commas. Each modification consists of: +

+
  • +The people affected by the modification. This can be u (the owning user), g (members of the owning group), or o (everybody else - ‘others’), or some combination of those. It can also be a (‘all’) to affect everybody at once. +
    • +
  • +A + or - sign, indicating whether permissions are to be added or removed. +
    • +
  • +The actual permissions being added or removed. These can be r (permission to read the file), w (permission to write to the file), and x (permission to execute the file, or in the case of a directory, permission to access files within the directory). +
    • +
+

+So the above examples would do: +

+
  • +The first example: go-rwx removes read, write and execute permissions for members of the owning group and everybody else (so the only permissions left are the ones for the file owner). u+w adds write permission for the file owner. +
    • +
  • +The second example: a+r adds read permission for everybody to all files and directories starting with ‘public’. +
    • +
+

+In addition to all this, there are a few extra special cases for Unix systems. On non-Unix systems these are unlikely to be useful: +

+
  • +You can specify u+s and u-s to add or remove the Unix set-user-ID bit. This is typically only useful for special purposes; refer to your Unix documentation if you're not sure about it. +
    • +
  • +You can specify g+s and g-s to add or remove the Unix set-group-ID bit. On a file, this works similarly to the set-user-ID bit (see your Unix documentation again); on a directory it ensures that files created in the directory are accessible by members of the group that owns the directory. +
    • +
  • +You can specify +t and -t to add or remove the Unix ‘sticky bit’. When applied to a directory, this means that the owner of a file in that directory can delete the file (whereas normally only the owner of the directory would be allowed to). +
    • +
+

6.2.15 The del command: delete remote files

+

+To delete a file on the server, type del and then the filename or filenames: +

+
del oldfile.dat
+del file1.txt file2.txt
+del *.o
+
+

+Files will be deleted without further prompting, even if multiple files are specified. +

+

+del will only delete files. You cannot use it to delete directories; use rmdir for that. +

+

+The rm command works exactly the same way as del. +

+

6.2.16 The mkdir command: create remote directories

+

+To create a directory on the server, type mkdir and then the directory name: +

+
mkdir newstuff
+
+

+You can specify multiple directories to create at once: +

+
mkdir dir1 dir2 dir3
+
+

6.2.17 The rmdir command: remove remote directories

+

+To remove a directory on the server, type rmdir and then the directory name or names: +

+
rmdir oldstuff
+rmdir *.old ancient
+
+

+Directories will be deleted without further prompting, even if multiple directories are specified. +

+

+Most SFTP servers will probably refuse to remove a directory if the directory has anything in it, so you will need to delete the contents first. +

+

6.2.18 The mv command: move and rename remote files

+

+To rename a single file on the server, type mv, then the current file name, and then the new file name: +

+
mv oldfile newname
+
+

+You can also move the file into a different directory and change the name: +

+
mv oldfile dir/newname
+
+

+To move one or more files into an existing subdirectory, specify the files (using wildcards if desired), and then the destination directory: +

+
mv file dir
+mv file1 dir1/file2 dir2
+mv *.c *.h ..
+
+

+The rename and ren commands work exactly the same way as mv. +

+

6.2.19 The ! command: run a local Windows command

+

+You can run local Windows commands using the ! command. This is the only PSFTP command that is not subject to the command quoting rules given in section 6.2.1. If any command line begins with the ! character, then the rest of the line will be passed straight to Windows without further translation. +

+

+For example, if you want to move an existing copy of a file out of the way before downloading an updated version, you might type: +

+
psftp> !ren myfile.dat myfile.bak
+psftp> get myfile.dat
+
+

+using the Windows ren command to rename files on your local PC. +

+

6.3 Using public key authentication with PSFTP

+

+Like PuTTY, PSFTP can authenticate using a public key instead of a password. There are three ways you can do this. +

+

+Firstly, PSFTP can use PuTTY saved sessions in place of hostnames. So you might do this: +

+
  • +Run PuTTY, and create a PuTTY saved session (see section 4.1.2) which specifies your private key file (see section 4.23.8). You will probably also want to specify a username to log in as (see section 4.15.1). +
    • +
  • +In PSFTP, you can now use the name of the session instead of a hostname: type psftp sessionname, where sessionname is replaced by the name of your saved session. +
    • +
+

+Secondly, you can supply the name of a private key file on the command line, with the -i option. See section 3.8.3.18 for more information. +

+

+Thirdly, PSFTP will attempt to authenticate using Pageant if Pageant is running (see chapter 9). So you would do this: +

+
  • +Ensure Pageant is running, and has your private key stored in it. +
    • +
  • +Specify a user and host name to PSFTP as normal. PSFTP will automatically detect Pageant and try to use the keys within it. +
    • +
+

+For more general information on public-key authentication, see chapter 8. +

+ +

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/Chapter7.html b/doc/Chapter7.html new file mode 100644 index 0000000..e97e60b --- /dev/null +++ b/doc/Chapter7.html @@ -0,0 +1,379 @@ + + + + +Using the command-line connection tool Plink + + + + + + + +

Previous | Contents | Index | Next

+ + +

Chapter 7: Using the command-line connection tool Plink

+

+Plink is a command-line connection tool similar to UNIX ssh. It is mostly used for automated operations, such as making CVS access a repository on a remote server. +

+

+Plink is probably not what you want if you want to run an interactive session in a console window. +

+

7.1 Starting Plink

+

+Plink is a command line application. This means that you cannot just double-click on its icon to run it and instead you have to bring up a console window. In Windows 95, 98, and ME, this is called an ‘MS-DOS Prompt’, and in Windows NT, 2000, and XP, it is called a ‘Command Prompt’. It should be available from the Programs section of your Start Menu. +

+

+In order to use Plink, the file plink.exe will need either to be on your PATH or in your current directory. To add the directory containing Plink to your PATH environment variable, type into the console window: +

+
set PATH=C:\path\to\putty\directory;%PATH%
+
+

+This will only work for the lifetime of that particular console window. To set your PATH more permanently on Windows NT, 2000, and XP, use the Environment tab of the System Control Panel. On Windows 95, 98, and ME, you will need to edit your AUTOEXEC.BAT to include a set command like the one above. +

+

7.2 Using Plink

+

+This section describes the basics of how to use Plink for interactive logins and for automated processes. +

+

+Once you've got a console window to type into, you can just type plink on its own to bring up a usage message. This tells you the version of Plink you're using, and gives you a brief summary of how to use Plink: +

+
Z:\sysosd>plink
+Plink: command-line connection utility
+Release 0.72
+Usage: plink [options] [user@]host [command]
+       ("host" can also be a PuTTY saved session name)
+Options:
+  -V        print version information and exit
+  -pgpfp    print PGP key fingerprints and exit
+  -v        show verbose messages
+  -load sessname  Load settings from saved session
+  -ssh -telnet -rlogin -raw -serial
+            force use of a particular protocol
+  -P port   connect to specified port
+  -l user   connect with specified username
+  -batch    disable all interactive prompts
+  -proxycmd command
+            use 'command' as local proxy
+  -sercfg configuration-string (e.g. 19200,8,n,1,X)
+            Specify the serial configuration (serial only)
+The following options only apply to SSH connections:
+  -pw passw login with specified password
+  -D [listen-IP:]listen-port
+            Dynamic SOCKS-based port forwarding
+  -L [listen-IP:]listen-port:host:port
+            Forward local port to remote address
+  -R [listen-IP:]listen-port:host:port
+            Forward remote port to local address
+  -X -x     enable / disable X11 forwarding
+  -A -a     enable / disable agent forwarding
+  -t -T     enable / disable pty allocation
+  -1 -2     force use of particular protocol version
+  -4 -6     force use of IPv4 or IPv6
+  -C        enable compression
+  -i key    private key file for user authentication
+  -noagent  disable use of Pageant
+  -agent    enable use of Pageant
+  -noshare  disable use of connection sharing
+  -share    enable use of connection sharing
+  -hostkey aa:bb:cc:...
+            manually specify a host key (may be repeated)
+  -sanitise-stderr, -sanitise-stdout, -no-sanitise-stderr, -no-sanitise-stdout
+            do/don't strip control chars from standard output/error
+  -no-antispoof   omit anti-spoofing prompt after authentication
+  -m file   read remote command(s) from file
+  -s        remote command is an SSH subsystem (SSH-2 only)
+  -N        don't start a shell/command (SSH-2 only)
+  -nc host:port
+            open tunnel in place of session (SSH-2 only)
+  -sshlog file
+  -sshrawlog file
+            log protocol details to a file
+  -shareexists
+            test whether a connection-sharing upstream exists
+
+

+Once this works, you are ready to use Plink. +

+

7.2.1 Using Plink for interactive logins

+

+To make a simple interactive connection to a remote server, just type plink and then the host name: +

+
Z:\sysosd>plink login.example.com
+
+Debian GNU/Linux 2.2 flunky.example.com
+flunky login:
+
+

+You should then be able to log in as normal and run a session. The output sent by the server will be written straight to your command prompt window, which will most likely not interpret terminal control codes in the way the server expects it to. So if you run any full-screen applications, for example, you can expect to see strange characters appearing in your window. Interactive connections like this are not the main point of Plink. +

+

+In order to connect with a different protocol, you can give the command line options -ssh, -telnet, -rlogin or -raw. To make an SSH connection, for example: +

+
Z:\sysosd>plink -ssh login.example.com
+login as:
+
+

+If you have already set up a PuTTY saved session, then instead of supplying a host name, you can give the saved session name. This allows you to use public-key authentication, specify a user name, and use most of the other features of PuTTY: +

+
Z:\sysosd>plink my-ssh-session
+Sent username "fred"
+Authenticating with public key "fred@winbox"
+Last login: Thu Dec  6 19:25:33 2001 from :0.0
+fred@flunky:~$
+
+

+(You can also use the -load command-line option to load a saved session; see section 3.8.3.1. If you use -load, the saved session exists, and it specifies a hostname, you cannot also specify a host or user@host argument - it will be treated as part of the remote command.) +

+

7.2.2 Using Plink for automated connections

+

+More typically Plink is used with the SSH protocol, to enable you to talk directly to a program running on the server. To do this you have to ensure Plink is using the SSH protocol. You can do this in several ways: +

+
  • +Use the -ssh option as described in section 7.2.1. +
    • +
  • +Set up a PuTTY saved session that describes the server you are connecting to, and that also specifies the protocol as SSH. +
    • +
  • +Set the Windows environment variable PLINK_PROTOCOL to the word ssh. +
    • +
+

+Usually Plink is not invoked directly by a user, but run automatically by another process. Therefore you typically do not want Plink to prompt you for a user name or a password. +

+

+Next, you are likely to need to avoid the various interactive prompts Plink can produce. You might be prompted to verify the host key of the server you're connecting to, to enter a user name, or to enter a password. +

+

+To avoid being prompted for the server host key when using Plink for an automated connection, you should first make a manual connection (using either of PuTTY or Plink) to the same server, verify the host key (see section 2.2 for more information), and select Yes to add the host key to the Registry. After that, Plink commands connecting to that server should not give a host key prompt unless the host key changes. +

+

+To avoid being prompted for a user name, you can: +

+
  • +Use the -l option to specify a user name on the command line. For example, plink login.example.com -l fred. +
    • +
  • +Set up a PuTTY saved session that describes the server you are connecting to, and that also specifies the username to log in as (see section 4.15.1). +
    • +
+

+To avoid being prompted for a password, you should almost certainly set up public-key authentication. (See chapter 8 for a general introduction to public-key authentication.) Again, you can do this in two ways: +

+
  • +Set up a PuTTY saved session that describes the server you are connecting to, and that also specifies a private key file (see section 4.23.8). For this to work without prompting, your private key will need to have no passphrase. +
    • +
  • +Store the private key in Pageant. See chapter 9 for further information. +
    • +
+

+Once you have done all this, you should be able to run a remote command on the SSH server machine and have it execute automatically with no prompting: +

+
Z:\sysosd>plink login.example.com -l fred echo hello, world
+hello, world
+
+Z:\sysosd>
+
+

+Or, if you have set up a saved session with all the connection details: +

+
Z:\sysosd>plink mysession echo hello, world
+hello, world
+
+Z:\sysosd>
+
+

+Then you can set up other programs to run this Plink command and talk to it as if it were a process on the server machine. +

+

7.2.3 Plink command line options

+

+Plink accepts all the general command line options supported by the PuTTY tools. See section 3.8.3 for a description of these options. +

+

+Plink also supports some of its own options. The following sections describe Plink's specific command-line options. +

+

7.2.3.1 -batch: disable all interactive prompts

+

+If you use the -batch option, Plink will never give an interactive prompt while establishing the connection. If the server's host key is invalid, for example (see section 2.2), then the connection will simply be abandoned instead of asking you what to do next. +

+

+This may help Plink's behaviour when it is used in automated scripts: using -batch, if something goes wrong at connection time, the batch job will fail rather than hang. +

+

7.2.3.2 -s: remote command is SSH subsystem

+

+If you specify the -s option, Plink passes the specified command as the name of an SSH ‘subsystem’ rather than an ordinary command line. +

+

+(This option is only meaningful with the SSH-2 protocol.) +

+

7.2.3.3 -share: Test and try to share an existing connection.

+

+This option tris to detect if an existing connection can be shared (See section 4.19.5 for more information about SSH connection sharing.) and reuses that connection. +

+

+A Plink invocation of the form: +

+
plink -share <session>
+
+

+will test whether there is currently a viable ‘upstream’ for the session in question, which can be specified using any syntax you'd normally use with Plink to make an actual connection (a host/port number, a bare saved session name, -load, etc). If no ‘upstream’ viable session is found and -share is specified, this connection will be become the ‘upstream’ connection for subsequent connection sharing tries. +

+

+(This option is only meaningful with the SSH-2 protocol.) +

+

7.2.3.4 -shareexists: test for connection-sharing upstream

+

+This option does not make a new connection; instead it allows testing for the presence of an existing connection that can be shared. (See section 4.19.5 for more information about SSH connection sharing.) +

+

+A Plink invocation of the form: +

+
plink -shareexists <session>
+
+

+will test whether there is currently a viable ‘upstream’ for the session in question, which can be specified using any syntax you'd normally use with Plink to make an actual connection (a host/port number, a bare saved session name, -load, etc). It returns a zero exit status if a usable ‘upstream’ exists, nonzero otherwise. +

+

+(This option is only meaningful with the SSH-2 protocol.) +

+

7.2.3.5 -sanitise-stream: control output sanitisation

+

+In some situations, Plink applies a sanitisation pass to the output received from the server, to strip out control characters such as backspace and the escape character. +

+

+The idea of this is to prevent remote processes from sending confusing escape sequences through the standard error channel when Plink is being used as a transport for something like git or CVS. If the server actually wants to send an error message, it will probably be plain text; if the server abuses that channel to try to write over unexpected parts of your terminal display, Plink will try to stop it. +

+

+By default, this only happens for output channels which are sent to a Windows console device, or a Unix terminal device. (Any output stream going somewhere else is likely to be needed by an 8-bit protocol and must not be tampered with at all.) It also stops happening if you tell Plink to allocate a remote pseudo-terminal (see section 3.8.3.12 and section 4.25.1), on the basis that in that situation you often want escape sequences from the server to go to your terminal. +

+

+But in case Plink guesses wrong about whether you want this sanitisation, you can override it in either direction, using one of these options: +

+
+-sanitise-stderr +
+
+Sanitise server data written to Plink's standard error channel, regardless of terminals and consoles and remote ptys. +
+
+-no-sanitise-stderr +
+
+Do not sanitise server data written to Plink's standard error channel. +
+
+-sanitise-stdout +
+
+Sanitise server data written to Plink's standard output channel. +
+
+-no-sanitise-stdout +
+
+Do not sanitise server data written to Plink's standard output channel. +
+
+

7.2.3.6 : turn off authentication spoofing protection prompt

+

+In SSH, some possible server authentication methods require user input (for example, password authentication, or entering a private key passphrase), and others do not (e.g. a private key held in Pageant). +

+

+If you use Plink to run an interactive login session, and if Plink authenticates without needing any user interaction, and if the server is malicious or compromised, it could try to trick you into giving it authentication data that should not go to the server (such as your private key passphrase), by sending what looks like one of Plink's local prompts, as if Plink had not already authenticated. +

+

+To protect against this, Plink's default policy is to finish the authentication phase with a final trivial prompt looking like this: +

+
Access granted. Press Return to begin session.
+
+

+so that if you saw anything that looked like an authentication prompt after that line, you would know it was not from Plink. +

+

+That extra interactive step is inconvenient. So Plink will turn it off in as many situations as it can: +

+
  • +If Plink's standard input is not pointing at a console or terminal device – for example, if you're using Plink as a transport for some automated application like version control – then you can't type passphrases into the server anyway. In that situation, Plink won't try to protect you from the server trying to fool you into doing so. +
    • +
  • +If Plink is in batch mode (see section 7.2.2), then it never does any interactive authentication. So anything looking like an interactive authentication prompt is automatically suspect, and so Plink omits the anti-spoofing prompt. +
    • +
+

+But if you still find the protective prompt inconvenient, and you trust the server not to try a trick like this, you can turn it off using the ‘-no-antispoof’ option. +

+

7.3 Using Plink in batch files and scripts

+

+Once you have set up Plink to be able to log in to a remote server without any interactive prompting (see section 7.2.2), you can use it for lots of scripting and batch purposes. For example, to start a backup on a remote machine, you might use a command like: +

+
plink root@myserver /etc/backups/do-backup.sh
+
+

+Or perhaps you want to fetch all system log lines relating to a particular web area: +

+
plink mysession grep /~fred/ /var/log/httpd/access.log > fredlog
+
+

+Any non-interactive command you could usefully run on the server command line, you can run in a batch file using Plink in this way. +

+

7.4 Using Plink with CVS

+

+To use Plink with CVS, you need to set the environment variable CVS_RSH to point to Plink: +

+
set CVS_RSH=\path\to\plink.exe
+
+

+You also need to arrange to be able to connect to a remote host without any interactive prompts, as described in section 7.2.2. +

+

+You should then be able to run CVS as follows: +

+
cvs -d :ext:user@sessionname:/path/to/repository co module
+
+

+If you specified a username in your saved session, you don't even need to specify the ‘user’ part of this, and you can just say: +

+
cvs -d :ext:sessionname:/path/to/repository co module
+
+

7.5 Using Plink with WinCVS

+

+Plink can also be used with WinCVS. Firstly, arrange for Plink to be able to connect to a remote host non-interactively, as described in section 7.2.2. +

+

+Then, in WinCVS, bring up the ‘Preferences’ dialogue box from the Admin menu, and switch to the ‘Ports’ tab. Tick the box there labelled ‘Check for an alternate rsh name’ and in the text entry field to the right enter the full path to plink.exe. Select ‘OK’ on the ‘Preferences’ dialogue box. +

+

+Next, select ‘Command Line’ from the WinCVS ‘Admin’ menu, and type a CVS command as in section 7.4, for example: +

+
cvs -d :ext:user@hostname:/path/to/repository co module
+
+

+or (if you're using a saved session): +

+
cvs -d :ext:user@sessionname:/path/to/repository co module
+
+

+Select the folder you want to check out to with the ‘Change Folder’ button, and click ‘OK’ to check out your module. Once you've got modules checked out, WinCVS will happily invoke plink from the GUI for CVS operations. +

+ +

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/Chapter8.html b/doc/Chapter8.html new file mode 100644 index 0000000..c910b11 --- /dev/null +++ b/doc/Chapter8.html @@ -0,0 +1,275 @@ + + + + +Using public keys for SSH authentication + + + + + + + +

Previous | Contents | Index | Next

+ + +

Chapter 8: Using public keys for SSH authentication

+

8.1 Public key authentication - an introduction

+

+Public key authentication is an alternative means of identifying yourself to a login server, instead of typing a password. It is more secure and more flexible, but more difficult to set up. +

+

+In conventional password authentication, you prove you are who you claim to be by proving that you know the correct password. The only way to prove you know the password is to tell the server what you think the password is. This means that if the server has been hacked, or spoofed (see section 2.2), an attacker can learn your password. +

+

+Public key authentication solves this problem. You generate a key pair, consisting of a public key (which everybody is allowed to know) and a private key (which you keep secret and do not give to anybody). The private key is able to generate signatures. A signature created using your private key cannot be forged by anybody who does not have that key; but anybody who has your public key can verify that a particular signature is genuine. +

+

+So you generate a key pair on your own computer, and you copy the public key to the server. Then, when the server asks you to prove who you are, PuTTY can generate a signature using your private key. The server can verify that signature (since it has your public key) and allow you to log in. Now if the server is hacked or spoofed, the attacker does not gain your private key or password; they only gain one signature. And signatures cannot be re-used, so they have gained nothing. +

+

+There is a problem with this: if your private key is stored unprotected on your own computer, then anybody who gains access to that will be able to generate signatures as if they were you. So they will be able to log in to your server under your account. For this reason, your private key is usually encrypted when it is stored on your local machine, using a passphrase of your choice. In order to generate a signature, PuTTY must decrypt the key, so you have to type your passphrase. +

+

+This can make public-key authentication less convenient than password authentication: every time you log in to the server, instead of typing a short password, you have to type a longer passphrase. One solution to this is to use an authentication agent, a separate program which holds decrypted private keys and generates signatures on request. PuTTY's authentication agent is called Pageant. When you begin a Windows session, you start Pageant and load your private key into it (typing your passphrase once). For the rest of your session, you can start PuTTY any number of times and Pageant will automatically generate signatures without you having to do anything. When you close your Windows session, Pageant shuts down, without ever having stored your decrypted private key on disk. Many people feel this is a good compromise between security and convenience. See chapter 9 for further details. +

+

+There is more than one public-key algorithm available. The most common are RSA and ECDSA, but others exist, notably DSA (otherwise known as DSS), the USA's federal Digital Signature Standard. The key types supported by PuTTY are described in section 8.2.2. +

+

8.2 Using PuTTYgen, the PuTTY key generator

+

+PuTTYgen is a key generator. It generates pairs of public and private keys to be used with PuTTY, PSCP, and Plink, as well as the PuTTY authentication agent, Pageant (see chapter 9). PuTTYgen generates RSA, DSA, ECDSA, and Ed25519 keys. +

+

+When you run PuTTYgen you will see a window where you have two main choices: ‘Generate’, to generate a new public/private key pair, or ‘Load’ to load in an existing private key. +

+

8.2.1 Generating a new key

+

+This is a general outline of the procedure for generating a new key pair. The following sections describe the process in more detail. +

+
  • +First, you need to select which type of key you want to generate, and also select the strength of the key. This is described in more detail in section 8.2.2 and section 8.2.3. +
    • +
  • +Then press the ‘Generate’ button, to actually generate the key. Section 8.2.4 describes this step. +
    • +
  • +Once you have generated the key, select a comment field (section 8.2.6) and a passphrase (section 8.2.7). +
    • +
  • +Now you're ready to save the private key to disk; press the ‘Save private key’ button. (See section 8.2.8). +
    • +
+

+Your key pair is now ready for use. You may also want to copy the public key to your server, either by copying it out of the ‘Public key for pasting into OpenSSH authorized_keys file’ box (see section 8.2.10), or by using the ‘Save public key’ button (section 8.2.9). However, you don't need to do this immediately; if you want, you can load the private key back into PuTTYgen later (see section 8.2.11) and the public key will be available for copying and pasting again. +

+

+Section 8.3 describes the typical process of configuring PuTTY to attempt public-key authentication, and configuring your SSH server to accept it. +

+

8.2.2 Selecting the type of key

+

+Before generating a key pair using PuTTYgen, you need to select which type of key you need. +

+

+The current version of the SSH protocol, SSH-2, supports several different key types. PuTTYgen can generate: +

+
  • +An RSA key for use with the SSH-2 protocol. +
    • +
  • +A DSA key for use with the SSH-2 protocol. +
    • +
  • +An ECDSA (elliptic curve DSA) key for use with the SSH-2 protocol. +
    • +
  • +An Ed25519 key (another elliptic curve algorithm) for use with the SSH-2 protocol. +
    • +
+

+PuTTYgen can also generate an RSA key suitable for use with the old SSH-1 protocol (which only supports RSA); for this, you need to select the ‘SSH-1 (RSA)’ option. Since the SSH-1 protocol is no longer considered secure, it's rare to need this option. +

+

8.2.3 Selecting the size (strength) of the key

+

+The ‘Number of bits’ input box allows you to choose the strength of the key PuTTYgen will generate. +

+
  • +For RSA, 2048 bits should currently be sufficient for most purposes. +
    • +
  • +For ECDSA, only 256, 384, and 521 bits are supported. (ECDSA offers equivalent security to RSA with smaller key sizes.) +
    • +
  • +For Ed25519, the only valid size is 256 bits. +
    • +
+

8.2.4 The ‘Generate’ button

+

+Once you have chosen the type of key you want, and the strength of the key, press the ‘Generate’ button and PuTTYgen will begin the process of actually generating the key. +

+

+First, a progress bar will appear and PuTTYgen will ask you to move the mouse around to generate randomness. Wave the mouse in circles over the blank area in the PuTTYgen window, and the progress bar will gradually fill up as PuTTYgen collects enough randomness. You don't need to wave the mouse in particularly imaginative patterns (although it can't hurt); PuTTYgen will collect enough randomness just from the fine detail of exactly how far the mouse has moved each time Windows samples its position. +

+

+When the progress bar reaches the end, PuTTYgen will begin creating the key. The progress bar will reset to the start, and gradually move up again to track the progress of the key generation. It will not move evenly, and may occasionally slow down to a stop; this is unfortunately unavoidable, because key generation is a random process and it is impossible to reliably predict how long it will take. +

+

+When the key generation is complete, a new set of controls will appear in the window to indicate this. +

+

8.2.5 The ‘Key fingerprint’ box

+

+The ‘Key fingerprint’ box shows you a fingerprint value for the generated key. This is derived cryptographically from the public key value, so it doesn't need to be kept secret; it is supposed to be more manageable for human beings than the public key itself. +

+

+The fingerprint value is intended to be cryptographically secure, in the sense that it is computationally infeasible for someone to invent a second key with the same fingerprint, or to find a key with a particular fingerprint. So some utilities, such as the Pageant key list box (see section 9.2.1) and the Unix ssh-add utility, will list key fingerprints rather than the whole public key. +

+

8.2.6 Setting a comment for your key

+

+If you have more than one key and use them for different purposes, you don't need to memorise the key fingerprints in order to tell them apart. PuTTYgen allows you to enter a comment for your key, which will be displayed whenever PuTTY or Pageant asks you for the passphrase. +

+

+The default comment format, if you don't specify one, contains the key type and the date of generation, such as rsa-key-20011212. Another commonly used approach is to use your name and the name of the computer the key will be used on, such as simon@simons-pc. +

+

+To alter the key comment, just type your comment text into the ‘Key comment’ box before saving the private key. If you want to change the comment later, you can load the private key back into PuTTYgen, change the comment, and save it again. +

+

8.2.7 Setting a passphrase for your key

+

+The ‘Key passphrase’ and ‘Confirm passphrase’ boxes allow you to choose a passphrase for your key. The passphrase will be used to encrypt the key on disk, so you will not be able to use the key without first entering the passphrase. +

+

+When you save the key, PuTTYgen will check that the ‘Key passphrase’ and ‘Confirm passphrase’ boxes both contain exactly the same passphrase, and will refuse to save the key otherwise. +

+

+If you leave the passphrase fields blank, the key will be saved unencrypted. You should not do this without good reason; if you do, your private key file on disk will be all an attacker needs to gain access to any machine configured to accept that key. If you want to be able to log in without having to type a passphrase every time, you should consider using Pageant (chapter 9) so that your decrypted key is only held in memory rather than on disk. +

+

+Under special circumstances you may genuinely need to use a key with no passphrase; for example, if you need to run an automated batch script that needs to make an SSH connection, you can't be there to type the passphrase. In this case we recommend you generate a special key for each specific batch script (or whatever) that needs one, and on the server side you should arrange that each key is restricted so that it can only be used for that specific purpose. The documentation for your SSH server should explain how to do this (it will probably vary between servers). +

+

+Choosing a good passphrase is difficult. Just as you shouldn't use a dictionary word as a password because it's easy for an attacker to run through a whole dictionary, you should not use a song lyric, quotation or other well-known sentence as a passphrase. DiceWare (www.diceware.com) recommends using at least five words each generated randomly by rolling five dice, which gives over 2^64 possible passphrases and is probably not a bad scheme. If you want your passphrase to make grammatical sense, this cuts down the possibilities a lot and you should use a longer one as a result. +

+

+Do not forget your passphrase. There is no way to recover it. +

+

8.2.8 Saving your private key to a disk file

+

+Once you have generated a key, set a comment field and set a passphrase, you are ready to save your private key to disk. +

+

+Press the ‘Save private key’ button. PuTTYgen will put up a dialog box asking you where to save the file. Select a directory, type in a file name, and press ‘Save’. +

+

+This file is in PuTTY's native format (*.PPK); it is the one you will need to tell PuTTY to use for authentication (see section 4.23.8) or tell Pageant to load (see section 9.2.2). +

+

8.2.9 Saving your public key to a disk file

+

+RFC 4716 specifies a standard format for storing SSH-2 public keys on disk. Some SSH servers (such as ssh.com's) require a public key in this format in order to accept authentication with the corresponding private key. (Others, such as OpenSSH, use a different format; see section 8.2.10.) +

+

+To save your public key in the SSH-2 standard format, press the ‘Save public key’ button in PuTTYgen. PuTTYgen will put up a dialog box asking you where to save the file. Select a directory, type in a file name, and press ‘Save’. +

+

+You will then probably want to copy the public key file to your SSH server machine. See section 8.3 for general instructions on configuring public-key authentication once you have generated a key. +

+

+If you use this option with an SSH-1 key, the file PuTTYgen saves will contain exactly the same text that appears in the ‘Public key for pasting’ box. This is the only existing standard for SSH-1 public keys. +

+

8.2.10 ‘Public key for pasting into OpenSSH authorized_keys file’

+

+The OpenSSH server, among others, requires your public key to be given to it in a one-line format before it will accept authentication with your private key. (SSH-1 servers also used this method.) +

+

+The ‘Public key for pasting into OpenSSH authorized_keys file’ gives the public-key data in the correct one-line format. Typically you will want to select the entire contents of the box using the mouse, press Ctrl+C to copy it to the clipboard, and then paste the data into a PuTTY session which is already connected to the server. +

+

+See section 8.3 for general instructions on configuring public-key authentication once you have generated a key. +

+

8.2.11 Reloading a private key

+

+PuTTYgen allows you to load an existing private key file into memory. If you do this, you can then change the passphrase and comment before saving it again; you can also make extra copies of the public key. +

+

+To load an existing key, press the ‘Load’ button. PuTTYgen will put up a dialog box where you can browse around the file system and find your key file. Once you select the file, PuTTYgen will ask you for a passphrase (if necessary) and will then display the key details in the same way as if it had just generated the key. +

+

+If you use the Load command to load a foreign key format, it will work, but you will see a message box warning you that the key you have loaded is not a PuTTY native key. See section 8.2.12 for information about importing foreign key formats. +

+

8.2.12 Dealing with private keys in other formats

+

+SSH-2 private keys have no standard format. OpenSSH and ssh.com have different formats, and PuTTY's is different again. So a key generated with one client cannot immediately be used with another. +

+

+Using the ‘Import’ command from the ‘Conversions’ menu, PuTTYgen can load SSH-2 private keys in OpenSSH's format and ssh.com's format. Once you have loaded one of these key types, you can then save it back out as a PuTTY-format key (*.PPK) so that you can use it with the PuTTY suite. The passphrase will be unchanged by this process (unless you deliberately change it). You may want to change the key comment before you save the key, since some OpenSSH key formats contained no space for a comment, and ssh.com's default comment format is long and verbose. +

+

+PuTTYgen can also export private keys in OpenSSH format and in ssh.com format. To do so, select one of the ‘Export’ options from the ‘Conversions’ menu. Exporting a key works exactly like saving it (see section 8.2.8) - you need to have typed your passphrase in beforehand, and you will be warned if you are about to save a key without a passphrase. +

+

+For OpenSSH there are two options. Modern OpenSSH actually has two formats it uses for storing private keys. ‘Export OpenSSH key’ will automatically choose the oldest format supported for the key type, for maximum backward compatibility with older versions of OpenSSH; for newer key types like Ed25519, it will use the newer format as that is the only legal option. If you have some specific reason for wanting to use OpenSSH's newer format even for RSA, DSA, or ECDSA keys, you can choose ‘Export OpenSSH key (force new file format)’. +

+

+Most clients for the older SSH-1 protocol use a standard format for storing private keys on disk. PuTTY uses this format as well; so if you have generated an SSH-1 private key using OpenSSH or ssh.com's client, you can use it with PuTTY, and vice versa. Hence, the export options are not available if you have generated an SSH-1 key. +

+

8.3 Getting ready for public key authentication

+

+Connect to your SSH server using PuTTY with the SSH protocol. When the connection succeeds you will be prompted for your user name and password to login. Once logged in, you must configure the server to accept your public key for authentication: +

+
  • +If your server is OpenSSH, you should change into the .ssh directory under your home directory, and open the file authorized_keys with your favourite editor. (You may have to create this file, if this is the first key you have put in it.) Then switch to the PuTTYgen window, select all of the text in the ‘Public key for pasting into OpenSSH authorized_keys file’ box (see section 8.2.10), and copy it to the clipboard (Ctrl+C). Then, switch back to the PuTTY window and insert the data into the open file, making sure it ends up all on one line. Save the file. +

    +(In very old versions of OpenSSH, SSH-2 keys had to be put in a separate file called authorized_keys2. In all current versions, the same authorized_keys file is used for both SSH-1 and SSH-2 keys.) +

    + +
    • +
  • +If your server is ssh.com's product and is using SSH-2, you need to save a public key file from PuTTYgen (see section 8.2.9), and copy that into the .ssh2 directory on the server. Then you should go into that .ssh2 directory, and edit (or create) a file called authorization. In this file you should put a line like Key mykey.pub, with mykey.pub replaced by the name of your key file. +
    • +
  • +For other SSH server software, you should refer to the manual for that server. +
    • +
+

+You may also need to ensure that your home directory, your .ssh directory, and any other files involved (such as authorized_keys, authorized_keys2 or authorization) are not group-writable or world-writable; servers will typically ignore the keys unless this is done. You can typically do this by using a command such as +

+
chmod go-w $HOME $HOME/.ssh $HOME/.ssh/authorized_keys
+
+

+Your server should now be configured to accept authentication using your private key. Now you need to configure PuTTY to attempt authentication using your private key. You can do this in any of three ways: +

+
  • +Select the private key in PuTTY's configuration. See section 4.23.8 for details. +
    • +
  • +Specify the key file on the command line with the -i option. See section 3.8.3.18 for details. +
    • +
  • +Load the private key into Pageant (see chapter 9). In this case PuTTY will automatically try to use it for authentication if it can. +
    • +
+ +

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/Chapter9.html b/doc/Chapter9.html new file mode 100644 index 0000000..f285676 --- /dev/null +++ b/doc/Chapter9.html @@ -0,0 +1,221 @@ + + + + +Using Pageant for authentication + + + + + + + +

Previous | Contents | Index | Next

+ + +

Chapter 9: Using Pageant for authentication

+

+Pageant is an SSH authentication agent. It holds your private keys in memory, already decoded, so that you can use them often without needing to type a passphrase. +

+

9.1 Getting started with Pageant

+

+Before you run Pageant, you need to have a private key in *.PPK format. See chapter 8 to find out how to generate and use one. +

+

+When you run Pageant, it will put an icon of a computer wearing a hat into the System tray. It will then sit and do nothing, until you load a private key into it. +

+

+If you click the Pageant icon with the right mouse button, you will see a menu. Select ‘View Keys’ from this menu. The Pageant main window will appear. (You can also bring this window up by double-clicking on the Pageant icon.) +

+

+The Pageant window contains a list box. This shows the private keys Pageant is holding. When you start Pageant, it has no keys, so the list box will be empty. After you add one or more keys, they will show up in the list box. +

+

+To add a key to Pageant, press the ‘Add Key’ button. Pageant will bring up a file dialog, labelled ‘Select Private Key File’. Find your private key file in this dialog, and press ‘Open’. +

+

+Pageant will now load the private key. If the key is protected by a passphrase, Pageant will ask you to type the passphrase. When the key has been loaded, it will appear in the list in the Pageant window. +

+

+Now start PuTTY and open an SSH session to a site that accepts your key. PuTTY will notice that Pageant is running, retrieve the key automatically from Pageant, and use it to authenticate. You can now open as many PuTTY sessions as you like without having to type your passphrase again. +

+

+(PuTTY can be configured not to try to use Pageant, but it will try by default. See section 4.23.3 and section 3.8.3.9 for more information.) +

+

+When you want to shut down Pageant, click the right button on the Pageant icon in the System tray, and select ‘Exit’ from the menu. Closing the Pageant main window does not shut down Pageant. +

+

9.2 The Pageant main window

+

+The Pageant main window appears when you left-click on the Pageant system tray icon, or alternatively right-click and select ‘View Keys’ from the menu. You can use it to keep track of what keys are currently loaded into Pageant, and to add new ones or remove the existing keys. +

+

9.2.1 The key list box

+

+The large list box in the Pageant main window lists the private keys that are currently loaded into Pageant. The list might look something like this: +

+
ssh-rsa 2048 22:d6:69:c9:22:51:ac:cb:b9:15:67:47:f7:65:6d:d7 k1
+ssh-dss 2048 e4:6c:69:f3:4f:fc:cf:fc:96:c0:88:34:a7:1e:59:d7 k2
+
+

+For each key, the list box will tell you: +

+
  • +The type of the key. Currently, this can be ssh-rsa (an RSA key for use with the SSH-2 protocol), ssh-dss (a DSA key for use with the SSH-2 protocol), ecdsa-sha2-* (an ECDSA key for use with the SSH-2 protocol), ssh-ed25519 (an Ed25519 key for use with the SSH-2 protocol), or ssh1 (an RSA key for use with the old SSH-1 protocol). +
    • +
  • +The size (in bits) of the key. +
    • +
  • +The fingerprint for the public key. This should be the same fingerprint given by PuTTYgen, and (hopefully) also the same fingerprint shown by remote utilities such as ssh-keygen when applied to your authorized_keys file. +
    • +
  • +The comment attached to the key. +
    • +
+

9.2.2 The ‘Add Key’ button

+

+To add a key to Pageant by reading it out of a local disk file, press the ‘Add Key’ button in the Pageant main window, or alternatively right-click on the Pageant icon in the system tray and select ‘Add Key’ from there. +

+

+Pageant will bring up a file dialog, labelled ‘Select Private Key File’. Find your private key file in this dialog, and press ‘Open’. If you want to add more than one key at once, you can select multiple files using Shift-click (to select several adjacent files) or Ctrl-click (to select non-adjacent files). +

+

+Pageant will now load the private key(s). If a key is protected by a passphrase, Pageant will ask you to type the passphrase. +

+

+(This is not the only way to add a private key to Pageant. You can also add one from a remote system by using agent forwarding; see section 9.4 for details.) +

+

9.2.3 The ‘Remove Key’ button

+

+If you need to remove a key from Pageant, select that key in the list box, and press the ‘Remove Key’ button. Pageant will remove the key from its memory. +

+

+You can apply this to keys you added using the ‘Add Key’ button, or to keys you added remotely using agent forwarding (see section 9.4); it makes no difference. +

+

9.3 The Pageant command line

+

+Pageant can be made to do things automatically when it starts up, by specifying instructions on its command line. If you're starting Pageant from the Windows GUI, you can arrange this by editing the properties of the Windows shortcut that it was started from. +

+

+If Pageant is already running, invoking it again with the options below causes actions to be performed with the existing instance, not a new one. +

+

9.3.1 Making Pageant automatically load keys on startup

+

+Pageant can automatically load one or more private keys when it starts up, if you provide them on the Pageant command line. Your command line might then look like: +

+
C:\PuTTY\pageant.exe d:\main.ppk d:\secondary.ppk
+
+

+If the keys are stored encrypted, Pageant will request the passphrases on startup. +

+

+If Pageant is already running, this syntax loads keys into the existing Pageant. +

+

9.3.2 Making Pageant run another program

+

+You can arrange for Pageant to start another program once it has initialised itself and loaded any keys specified on its command line. This program (perhaps a PuTTY, or a WinCVS making use of Plink, or whatever) will then be able to use the keys Pageant has loaded. +

+

+You do this by specifying the -c option followed by the command, like this: +

+
C:\PuTTY\pageant.exe d:\main.ppk -c C:\PuTTY\putty.exe
+
+

9.3.3 Restricting the Windows process ACL

+

+Pageant supports the same -restrict-acl option as the other PuTTY utilities to lock down the Pageant process's access control; see section 3.8.3.25 for why you might want to do this. +

+

+By default, if Pageant is started with -restrict-acl, it won't pass this to any PuTTY sessions started from its System Tray submenu. Use -restrict-putty-acl to change this. (Again, see section 3.8.3.25 for details.) +

+

9.4 Using agent forwarding

+

+Agent forwarding is a mechanism that allows applications on your SSH server machine to talk to the agent on your client machine. +

+

+Note that at present, whether agent forwarding in SSH-2 is available depends on your server. Pageant's protocol is compatible with the OpenSSH server, but the ssh.com server uses a different agent protocol, which PuTTY does not yet support. +

+

+To enable agent forwarding, first start Pageant. Then set up a PuTTY SSH session in which ‘Allow agent forwarding’ is enabled (see section 4.23.6). Open the session as normal. (Alternatively, you can use the -A command line option; see section 3.8.3.10 for details.) +

+

+If this has worked, your applications on the server should now have access to a Unix domain socket which the SSH server will forward back to PuTTY, and PuTTY will forward on to the agent. To check that this has actually happened, you can try this command on Unix server machines: +

+
unixbox:~$ echo $SSH_AUTH_SOCK
+/tmp/ssh-XXNP18Jz/agent.28794
+unixbox:~$
+
+

+If the result line comes up blank, agent forwarding has not been enabled at all. +

+

+Now if you run ssh on the server and use it to connect through to another server that accepts one of the keys in Pageant, you should be able to log in without a password: +

+
unixbox:~$ ssh -v otherunixbox
+[...]
+debug: next auth method to try is publickey
+debug: userauth_pubkey_agent: trying agent key my-putty-key
+debug: ssh-userauth2 successful: method publickey
+[...]
+
+

+If you enable agent forwarding on that SSH connection as well (see the manual for your server-side SSH client to find out how to do this), your authentication keys will still be available on the next machine you connect to - two SSH connections away from where they're actually stored. +

+

+In addition, if you have a private key on one of the SSH servers, you can send it all the way back to Pageant using the local ssh-add command: +

+
unixbox:~$ ssh-add ~/.ssh/id_rsa
+Need passphrase for /home/fred/.ssh/id_rsa
+Enter passphrase for /home/fred/.ssh/id_rsa:
+Identity added: /home/fred/.ssh/id_rsa (/home/simon/.ssh/id_rsa)
+unixbox:~$
+
+

+and then it's available to every machine that has agent forwarding available (not just the ones downstream of the place you added it). +

+

9.5 Security considerations

+

+Using Pageant for public-key authentication gives you the convenience of being able to open multiple SSH sessions without having to type a passphrase every time, but also gives you the security benefit of never storing a decrypted private key on disk. Many people feel this is a good compromise between security and convenience. +

+

+It is a compromise, however. Holding your decrypted private keys in Pageant is better than storing them in easy-to-find disk files, but still less secure than not storing them anywhere at all. This is for two reasons: +

+
  • +Windows unfortunately provides no way to protect pieces of memory from being written to the system swap file. So if Pageant is holding your private keys for a long period of time, it's possible that decrypted private key data may be written to the system swap file, and an attacker who gained access to your hard disk later on might be able to recover that data. (However, if you stored an unencrypted key in a disk file they would certainly be able to recover it.) +
    • +
  • +Although, like most modern operating systems, Windows prevents programs from accidentally accessing one another's memory space, it does allow programs to access one another's memory space deliberately, for special purposes such as debugging. This means that if you allow a virus, trojan, or other malicious program on to your Windows system while Pageant is running, it could access the memory of the Pageant process, extract your decrypted authentication keys, and send them back to its master. +
    • +
+

+Similarly, use of agent forwarding is a security improvement on other methods of one-touch authentication, but not perfect. Holding your keys in Pageant on your Windows box has a security advantage over holding them on the remote server machine itself (either in an agent or just unencrypted on disk), because if the server machine ever sees your unencrypted private key then the sysadmin or anyone who cracks the machine can steal the keys and pretend to be you for as long as they want. +

+

+However, the sysadmin of the server machine can always pretend to be you on that machine. So if you forward your agent to a server machine, then the sysadmin of that machine can access the forwarded agent connection and request signatures from any of your private keys, and can therefore log in to other machines as you. They can only do this to a limited extent - when the agent forwarding disappears they lose the ability - but using Pageant doesn't actually prevent the sysadmin (or hackers) on the server from doing this. +

+

+Therefore, if you don't trust the sysadmin of a server machine, you should never use agent forwarding to that machine. (Of course you also shouldn't store private keys on that machine, type passphrases into it, or log into other machines from it in any way at all; Pageant is hardly unique in this respect.) +

+ +

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/IndexPage.html b/doc/IndexPage.html new file mode 100644 index 0000000..cbb04e7 --- /dev/null +++ b/doc/IndexPage.html @@ -0,0 +1,943 @@ + + + + + + + + + + +

Previous | Contents | Index | Next

+

Index

+-4: Section 3.8.3.17
+-6: Section 3.8.3.17
+Abort Output, Telnet special command: Section 3.1.3.2
+Abort Process, Telnet special command: Section 3.1.3.2
+accented characters: Section 3.3, Section 4.4.7
+accessibility: Section 4.9.4
+access to files, changing: Section 6.2.14
+account name: Section 2.3, Section 3.8.3.4, Section 5.2.1.1
+account name, for auto-login: Section 4.15.1
+account name, for proxy: Section 4.16.4
+account name, local, in Rlogin: Section 4.18.1
+account name, local, in Windows: Section 4.18.1
+account names, different: Section 2.3, Section 4.23.7
+ACL, process (Windows): Section 3.8.3.25, Section 9.3.3
+-A command-line option: Section 3.8.3.10
+-a command-line option: Section 3.8.3.10
+active Telnet negotiation: Section 4.17.2
+address, IP: Section 3.5, Section 4.1.1, Section 4.14.4
+ad-hoc proxy: Section 4.16.1, Section 4.16.5, Section 4.17.2
+adjusting a selection: Section 3.1.1, Section 4.11.1
+Advanced Encryption Standard: Section 4.22
+AES: Section 4.22
+-agent: Section 3.8.3.9
+agent, authentication: Section 8.1, Chapter 9
+agent forwarding: Section 3.8.3.10, Section 4.23.6, Section 9.4
+algorithm, encryption: Section 4.22
+algorithm, key exchange: Section 4.20.1
+algorithm, public-key: Section 8.1
+allocation, of pseudo-terminal: Section 3.8.3.12, Section 4.25.1
+alternate screen: Section 4.6.4, Section 4.7.4, Question A.7.16
+ALT-F4: Section 4.9.3
+‘AltGr’ key: Section 4.4.7, Section 4.4.8
+‘Alt’ key: Section 4.9.5
+ALT-Space: Section 4.9.4
+always on top: Section 4.9.6
+ANSI colours: Section 4.13.1, Section 4.13.7
+ANSI graphics: Section 3.3, Section 4.10.4
+ANSI printing: Section 4.3.10
+answerback string: Section 4.3.7
+Application Cursor Keys: Section 4.4.4, Section 4.6.1
+Application key: Section 4.4.7
+Application Keypad: Section 4.4.5, Section 4.6.1
+Arabic: Section 4.6.11
+Arabic text shaping: Section 4.6.10
+Arcfour: Section 4.22, Section 10.4
+Are You There, Telnet special command: Section 3.1.3.2
+arguments, command-line: Section 3.8, Section 9.3
+ASCII: Section 4.10.5, Question A.2.11
+assertion failed: Section 10.7
+asymmetric key algorithm: Section 8.1
+authentication: Section 4.23
+authentication agent: Section 8.1, Chapter 9
+authentication agent forwarding: Section 3.8.3.10, Section 4.23.6, Section 9.4
+authentication, challenge/response: Section 4.23.4, Section 4.23.5
+authentication, keyboard-interactive: Section 4.23.5
+authentication, public key: Section 3.8.3.18, Section 4.23.8, Section 4.28.9, Section 5.2.4, Section 6.3, Section 7.2.2, Section 8.1
+authentication, to proxy: Section 4.16.4
+authentication, X11: Section 4.26.1
+Authenticode: Appendix E
+authorized_keys file: Section 8.2.10, Section 8.3
+AUTOEXEC.BAT: Section 5.1, Section 7.1
+automated operations: Chapter 7
+auto wrap mode: Section 4.3.1, Question A.7.7
+background colour: Section 4.3.5, Question A.7.6
+background colour, bright: Section 4.3.6
+background colour, default: Section 4.13.6, Section 4.13.7
+backspace, destructive: Section 4.6.8
+backspace key: Section 4.4.1
+bandwidth: Section 4.14.2, Section 4.15.4, Section 4.19.3
+banner: Section 4.23.1
+‘basic’ authentication (HTTP): Section 4.16.4
+batch files: Section 4.30, Section 5.2.3, Section 7.3
+-batch Plink command-line option: Section 7.2.3.1
+-batch PSCP command-line option: Section 5.2.2.5
+-batch PSFTP command-line option: Section 6.1.4
+batch scripts in PSFTP: Section 6.1.1
+baud rate, of terminal: Section 4.15.4
+-bc PSFTP command-line option: Section 6.1.2
+beep, terminal: Section 4.5
+beep, with PC speaker: Section 4.5.1
+bell, disabling: Section 4.5.1, Section 4.5.3
+bell overload mode: Section 4.5.3
+bell, terminal: Section 4.5
+bell, visual: Section 4.5.1
+-be PSFTP command-line option: Section 6.1.3
+bidirectional text: Section 4.6.11
+bind address: Section 3.5, Section 3.8.3.5, Section 4.27
+BitchX: Section 4.6.9
+8-bit colour: Section 4.13.5
+32-bit Windows: Question A.6.10
+64-bit Windows: Question A.6.10, Question A.7.22
+black, bold: Section 4.13.4
+blinking cursor: Section 4.8.1
+blinking text: Section 4.3.6
+Blowfish: Section 4.22, Section 10.4
+bold black: Section 4.13.4
+bold text: Section 4.13.4, Section 4.13.6, Section 4.13.7
+box-drawing characters: Section 3.3, Section 4.10.4
+-b PSFTP command-line option: Section 6.1.1
+Break, serial special command: Section 3.1.3.2
+Break, SSH special command: Section 3.1.3.2
+Break, Telnet special command: Section 3.1.3.2
+bright black: Section 4.13.4
+BSD: Section 4.17.1
+bug reporting: Appendix B
+bugs, in SSH servers: Section 4.28
+bulletin board system: Section 1.1
+cache, of SSH host keys: Section 2.2, Section 3.1.3.2, Section 3.8.3.19, Section 3.8.3.20, Section 4.14.5, Section 4.21, Section 4.21.2
+Caps Lock: Section 4.10.3
+Carriage Return: Section 4.3.3, Section 4.3.4
+cascading credentials: Section 4.20.1.1
+cat: Question A.7.13
+-C command-line option: Section 3.8.3.15
+ChaCha20-Poly1305: Section 4.22
+challenge/response authentication: Section 4.23.4, Section 4.23.5
+‘Change Settings’: Section 3.1.3.4
+changing permissions on files: Section 6.2.14
+changing user names: Section 2.3, Section 4.23.7
+CHAP: Section 4.16.4
+character classes: Section 4.12.1
+characters, accented: Section 3.3, Section 4.4.7
+character set: Section 3.3, Section 4.6.9, Section 4.10
+characters, line-drawing: Section 3.3, Section 4.10.4
+character width: Section 4.10.2
+Chinese: Section 4.10.2
+choosing a protocol: Section 1.2, Section 3.8.3.2
+cipher algorithm: Section 4.22
+Cisco: Section 3.8.3.6
+CJK: Section 4.10.2
+CJK ambiguous characters: Section 4.10.2
+clean up after PuTTY: Question A.8.2
+-cleanup command-line option: Section 3.8.2
+clear screen: Section 4.3.5
+‘Clear Scrollback’: Section 3.1.3.6
+client: Section 1.1
+clipboard: Section 3.1.1, Section 3.1.3.1, Section 3.1.3.5
+CLIPBOARD selection: Section 4.11.4
+clipboards, multiple: Section 4.11.4
+Close button: Section 2.5, Section 4.9.2
+closing window: Section 4.1.3, Section 4.9.2, Section 4.9.3
+code page: Section 4.10.1
+colour: Section 4.12.2, Section 4.13, Question A.7.2
+colour, background, default: Section 4.13.6, Section 4.13.7
+colour, 8-bit: Section 4.13.5
+colour, foreground, default: Section 4.13.6, Section 4.13.7
+256-colour mode: Section 4.13.2
+colour, of cursor: Section 4.13.6, Section 4.13.7
+colours, ANSI: Section 4.13.1, Section 4.13.7
+colours, system: Section 4.13.6
+columns, in terminal window: Section 4.7.1
+COM1: Section 4.29.1
+command-line arguments: Section 3.8, Section 9.3
+command-line interface: Section 1.1
+command line, loading saved sessions from: Section 3.8.3.1
+-1 command-line option: Section 3.8.3.16
+-2 command-line option: Section 3.8.3.16
+Command Prompt: Section 1.1, Section 1.1, Section 3.8, Section 5.1, Section 7.1
+command, proxy: Section 3.8.3.24, Section 4.16.1, Section 4.16.5
+commands on the server: Section 2.4, Section 3.8.3.6, Section 4.19.1, Section 4.19.2, Question A.6.2
+commands, reading from a file: Section 3.8.3.6
+comment: Section 6.2
+Compose key: Section 4.4.7
+compression: Section 3.8.3.15, Section 4.19.3
+confidentiality: Section 4.20.2
+configuration: Section 3.8.3.22
+configuration options: Chapter 4
+connection, network: Section 3.5, Section 4.14, Section 4.27
+connections, half-open: Section 4.14.3
+connections, idle: Section 4.14.1, Question A.7.8
+connections, interactive: Section 4.14.2, Section 4.25.1, Chapter 7
+connectivity, breaks in: Section 4.14.1, Question A.7.9
+CONNECT proxy (HTTP): Section 4.16.1
+console window: Section 1.1, Section 1.1, Section 3.8, Section 5.1, Section 7.1
+context menu: Section 3.1.1, Section 3.1.3, Section 4.11.1
+Control-?: Section 4.4.1
+Control-H: Section 4.4.1
+control sequences: Section 3.2, Section 4.3.1, Section 4.3.2, Section 4.3.5, Section 4.3.6, Section 4.6.2, Section 4.9.1, Section 4.10.4, Section 4.11.2, Section 4.12.1, Section 4.13.1, Section 4.13.4, Section 4.15.3, Section 4.15.3, Section 7.2.1, Question A.5.1
+cookie, magic: Section 4.26.1
+coordinates, cursor: Section 4.3.2
+Copy All to Clipboard: Section 3.1.3.5
+copy and paste: Section 3.1.1, Section 4.6.2, Section 4.10.5, Section 4.11, Section 4.11.2, Question A.6.6
+copyright: Appendix C
+corruption, of display: Section 4.6.10, Section 4.6.11
+CP437: Section 4.10.1
+CP866: Section 4.10.1
+-c Pageant command-line option: Section 9.3.2
+CRC: Section 10.12
+CR (Carriage Return): Section 4.3.3, Section 4.3.4
+creating directories: Section 6.2.16
+creating key pairs: Section 8.2
+credential delegation, GSSAPI: Section 4.24.1
+credentials, cascading: Section 4.20.1.1
+CryptoCard authentication: Section 4.23.4
+Ctrl-?: Section 4.4.1
+Ctrl-Break: Section 3.1.3.2
+Ctrl-C: Section 3.1.1, Section 3.1.1, Section 4.11.4
+Ctrl-H: Section 4.4.1
+Ctrl-Ins: Section 3.1.1, Section 4.11.4.2
+Ctrl-PgDn: Section 3.1.2
+Ctrl-PgUp: Section 3.1.2
+Ctrl-Shift-C: Section 4.11.4.2
+Ctrl-Shift-PgDn: Section 3.1.2
+Ctrl-Shift-PgUp: Section 3.1.2
+Ctrl-Shift-V: Section 4.11.4.2
+Ctrl-V: Section 4.11.4
+Ctrl, with right mouse button: Section 3.1.1
+current working directory: Section 6.2.7, Section 6.2.8
+cursor: Section 4.8.1
+cursor, blinking: Section 4.8.1
+cursor colour: Section 4.13.6, Section 4.13.7
+cursor coordinates: Section 4.3.2
+cursor keys, ‘Application’ mode: Section 4.4.4, Section 4.6.1
+cut and paste: Section 3.1.1, Section 4.6.2, Section 4.10.5, Section 4.11, Section 4.11.2, Question A.6.6
+CVS: Section 7.4
+CVS_RSH environment variable: Section 7.4
+Cyrillic: Section 4.10.3
+-D command-line option: Section 3.8.3.5
+debugging Internet protocols: Section 3.6
+DEC Compose key: Section 4.4.7
+DEC Origin Mode: Section 4.3.2
+DECterm: Question A.5.1
+Default Beep sound, Windows: Section 4.5
+Default Settings: Section 3.8.1, Section 4.1.2
+delays, in SSH-2 sessions: Question A.7.20
+delegation, of GSSAPI credentials: Section 4.24.1
+deleting directories: Section 6.2.17
+deleting files: Section 6.2.15
+DES: Section 4.22, Section 10.4
+destructive backspace: Section 4.6.8
+development snapshots: Section B.2
+diagnostic, proxy: Section 4.16.6
+dialog box: Section 2.1
+DiceWare: Section 8.2.7
+differences between SSH, Telnet and Rlogin: Section 1.2
+different user names: Section 2.3, Section 4.23.7
+Diffie-Hellman group exchange: Section 4.20.1
+Diffie-Hellman key exchange: Section 4.20.1
+digital signature: Section 4.28.6, Section 8.1
+Digital Signature Standard: Section 4.21.1, Section 4.21.1, Section 4.21.1, Section 8.1, Section 8.2.2, Question A.8.3
+directories, creating: Section 6.2.16
+directories, removing: Section 6.2.17
+display corruption: Section 4.6.10, Section 4.6.11
+DISPLAY environment variable: Section 3.4
+DLL: Section 4.24.2, Question A.6.10
+DNS: Section 4.16.3
+DNS name: Section 2.1, Section 4.1.1, Section 4.9.1, Section 4.14.4, Section 5.2.1.2
+DNS resolution: Section 4.16.3
+DNS, with proxy: Section 4.16.2, Section 4.16.3
+Domain Name System: Section 4.16.3
+double-click: Section 3.1.1, Section 4.12.1
+double-width character: Section 4.10.2
+downloading files: Section 5.2.1, Section 6.2.9
+Dragon NaturallySpeaking: Section 4.9.4
+DSA: Section 4.21.1, Section 4.21.1, Section 4.21.1, Section 8.1, Section 8.2.2, Question A.8.3
+DSA authentication: Section 3.8.3.18, Section 4.23.8, Section 4.28.9, Section 5.2.4, Section 6.3, Section 7.2.2, Section 8.1
+‘Duplicate Session’: Section 3.1.3.3, Question A.7.22
+dynamic port forwarding: Section 3.5, Section 3.8.3.5, Section 4.27
+East Asian Ambiguous characters: Section 4.10.2
+ECDSA: Section 8.1, Section 8.2.2
+echo, local: Section 4.3.8, Section 4.3.9, Question A.2.4
+echo, remote: Section 4.3.8
+Ed25519: Section 8.2.2
+Edwards-curve: Section 4.21.1
+elliptic curve: Section 4.20.1, Section 4.21.1, Section 8.2.2
+emulation, terminal: Section 3.1.3.6, Section 4.3, Section 4.3.7, Section 4.4, Section 4.6, Section 4.15.3
+encryption: Section 4.28.10, Section 8.1, Section 8.2.7
+encryption algorithm: Section 4.22
+End key: Section 4.4.2
+End Of File, Telnet special command: Section 3.1.3.2
+End Of Record, Telnet special command: Section 3.1.3.2
+enquiry character: Section 4.3.7
+environment variables: Section 4.15.5, Section 4.17.1
+Erase Character, Telnet special command: Section 3.1.3.2, Section 4.17.3
+Erase Line, Telnet special command: Section 3.1.3.2
+erase screen: Section 4.3.5
+ERASE, special character: Section 4.25.2
+ERRORLEVEL: Section 5.2.3
+error messages: Chapter 10
+escape sequences: Section 3.2, Section 4.3.1, Section 4.3.2, Section 4.3.6, Section 4.6.2, Section 4.9.1, Section 4.10.4, Section 4.11.2, Section 4.12.1, Section 4.13.1, Section 4.13.4, Section 4.15.3, Section 7.2.1
+Event Log: Section 3.1.3.1, Section 4.2
+execute permission: Section 6.2.14
+exit value: Section 5.2.3
+expiry, of passwords: Section 4.23.5
+exporting private keys: Section 8.2.12
+extending a selection: Section 3.1.1, Section 4.11.1
+FAQ: Appendix A
+features, supported: Section A.2
+feedback: Appendix B
+feep: Section 4.5
+filenames containing spaces: Section 6.2.1, Question A.6.9
+files, changing permissions on: Section 6.2.14
+files, deleting: Section 6.2.15
+files, listing: Section 5.2.2.1, Section 6.2.13
+files, receiving: Section 5.2.1, Section 6.2.9
+files, renaming and moving: Section 6.2.18
+files, resuming transfer of: Section 6.2.12
+files, sending: Section 5.2.1, Section 6.2.10
+files, transferring: Chapter 5, Chapter 6
+finger: Section 3.5
+fingerprint, of PGP key: Section 3.8.3.21
+fingerprint, of SSH authentication key: Section 8.2.5, Section 9.2.1
+fingerprint, of SSH host key: Section 2.2
+firewalls: Section 4.14.1, Section 4.17.2, Section 4.20.2, Section 10.16, Question A.7.8
+flashing cursor: Section 4.8.1
+flashing text: Section 4.3.6
+flow-control window: Section 4.28.5
+font: Section 4.8.2, Section 4.10.4, Section 4.12.2, Section 4.13.4
+font size: Section 4.7.2, Section 4.8.2
+foreground colour, default: Section 4.13.6, Section 4.13.7
+forwarding, of X11: Section 3.4, Section 3.8.3.11, Section 4.26
+forwarding ports in SSH: Section 3.5, Section 3.8.3.5, Section 4.16, Section 4.19.2, Section 4.27
+forwarding ports in SSH, changing mid-session: Section 4.27
+forwarding, SSH agent: Section 3.8.3.10, Section 4.23.6, Section 9.4
+Frequently Asked Questions: Appendix A
+ftp: Chapter 6
+full-screen mode: Section 3.1.3.7, Section 4.7.3, Section 4.9.7
+function keys: Section 4.4.3, Question A.7.13
+generating key pairs: Section 8.2
+glob (wildcard): Section 5.2.1, Section 5.2.1.3, Section 5.2.2.6, Section 6.2.2, Section 6.2.11
+Go Ahead, Telnet special command: Section 3.1.3.2
+GPG signatures, of PuTTY binaries: Appendix E
+graphical applications: Section 3.4, Section 4.26
+group exchange, Diffie-Hellman: Section 4.20.1
+GSSAPI: Section 4.15.2, Section 4.24
+GSSAPI credential delegation: Section 4.24.1
+Gtk: Question A.3.2
+half-open connections: Section 4.14.3
+Hebrew: Section 4.6.11
+history: Section 3.1.2
+HMAC: Section 4.28.8
+home directory: Section 5.2.1.3
+Home key: Section 4.4.2
+-hostkey: Section 3.8.3.20
+host key fingerprint (SSH): Section 2.2
+host key management: Section 2.2, Section 3.1.3.2, Section 3.8.3.19, Section 3.8.3.20, Section 4.14.5, Section 4.21, Section 4.21.2
+host keys, manually configuring: Section 3.8.3.20, Section 4.21.2
+host keys, trusting: Section 2.2
+host keys, upgrading: Section 3.1.3.2
+host key type: Section 4.21.1
+host key, verifying: Section 2.2, Question A.2.9
+host name: Section 2.1, Section 4.1.1, Section 4.9.1, Section 4.14.4, Section 5.2.1.2
+host name, logical: Section 3.8.3.19, Section 4.14.5
+host name resolution: Section 4.16.3
+host name resolution, with proxy: Section 4.16.2, Section 4.16.3
+HTTP: Section 3.6
+HTTP ‘basic’ authentication: Section 4.16.4
+HTTP proxy: Section 4.16.1
+-i command-line option: Section 3.8.3.18
+icon, PuTTY's: Section 2.3, Section A.5.3
+icon title: Section 4.9.1
+idle connections: Section 4.14.1, Question A.7.8
+‘ignore’ messages, in SSH: Section 3.1.3.2, Section 4.28.1, Section 4.28.11
+IGNORE message, SSH special command: Section 3.1.3.2
+importing private keys: Section 8.2.12
+inactive window: Section 4.1.3
+indenting: Section 3.1.1
+integrity: Section 4.20.2
+interactive connections: Section 4.14.2, Section 4.25.1, Chapter 7
+intermittent connectivity: Section 4.14.1, Question A.7.9
+internal error: Section 10.7
+internal fault: Section 10.7
+Internet protocols, debugging: Section 3.6
+Internet Protocol version: Section 3.8.3.17, Section 4.14.4, Section 4.27.2
+Interrupt Process, Telnet special command: Section 3.1.3.2, Section 4.17.3
+IP address: Section 3.5, Section 4.1.1, Section 4.14.4
+IP address, loopback: Section 3.5, Section 4.16.2
+IP masquerading: Section 10.16, Question A.7.8
+IPv4: Section 3.8.3.17, Section 4.14.4, Section 4.27.2
+IPv6: Section 3.8.3.17, Section 4.14.4, Section 4.27.2
+IPv6 address: Section 4.27
+ISO-8859: Section 4.10.1
+ISO-10646 (Unicode): Section 4.6.10, Section 4.10.1, Section 4.10.4, Section 4.10.5
+IUTF8 terminal mode: Section 4.25.2
+Japanese: Section 4.10.2
+keepalives, application: Section 4.14.1, Section 4.20.2, Section 4.28.1, Section 4.28.11
+keepalives, TCP: Section 4.14.3
+Kerberos: Section 4.24
+kex: Section 4.20
+keyboard: Section 4.4, Section 4.15.3, Question A.7.12, Question A.7.13
+keyboard-interactive authentication: Section 4.23.5
+key exchange: Section 4.20
+key exchange algorithm: Section 4.20.1
+key exchange, Diffie-Hellman: Section 4.20.1
+key exchange, forcing repeat: Section 3.1.3.2
+key exchange, repeat: Section 3.1.3.2, Section 4.20.2, Section 4.28.2, Question A.7.20
+keypad, ‘Application’ mode: Section 4.4.5, Section 4.6.1
+keypad, NetHack mode: Section 4.4.6
+keypad, numeric: Section 4.4.3
+key pair: Section 8.1
+key pairs, generating: Section 8.2
+known_hosts: Question A.2.9
+Korean: Section 4.10.2
+last selected text: Section 4.11.4.2
+-L command-line option: Section 3.8.3.5
+-l command-line option: Section 3.8.3.4
+left mouse button: Section 3.1.1, Section 4.11.1
+LF (Line Feed): Section 4.3.3, Section 4.3.4
+licence: Appendix C
+line-drawing characters: Section 3.3, Section 4.10.4
+line editing, local: Section 4.3.9
+Line Feed: Section 4.3.3, Section 4.3.4
+lines, selecting: Section 3.1.1
+line wrapping, automatic: Section 4.3.1, Question A.7.7
+links (web browser): Section 4.6.2
+Linux: Section 4.4, Section 4.4.1, Section 4.15.3, Section 4.25.1, Section 4.27.2, Section 6.2.14, Section 10.18, Question A.7.13
+Linux, Red Hat: Question A.7.15
+Linux version of PuTTY tools: PuTTY User Manual, Question A.3.2
+Linux virtual console: Section 4.4.3
+listen address: Section 3.5, Section 3.8.3.5, Section 4.27
+listing files: Section 5.2.2.1, Section 6.2.13
+-load command-line option: Section 3.8.3.1
+loading private keys: Section 8.2.12
+loading saved sessions from command line: Section 3.8.3.1
+loading settings: Section 4.1.2
+loading settings from a file: Section 4.30
+local echo: Section 4.3.8, Section 4.3.9, Question A.2.4
+localhost: Section 3.5, Section 4.16.2, Section 4.27.1, Question A.7.17
+local line editing: Section 4.3.9
+local proxy: Section 3.8.3.24, Section 4.16.1, Section 4.16.5
+local-to-remote port forwarding: Section 3.5, Section 3.8.3.5, Section 4.27
+local user name, in Rlogin: Section 4.18.1
+local user name, in Windows: Section 4.18.1
+local Windows command: Section 6.2.19
+locking up, SSH-2 sessions: Question A.7.20
+Log, Event: Section 3.1.3.1, Section 4.2
+log file: Section 3.2, Section 3.8.3.23, Section 4.2
+log file, flushing: Section 4.2.3
+log file, header: Section 4.2.4
+logging in: Section 2.3
+logging out: Section 2.5
+logging, proxy: Section 4.16.6
+-loghost: Section 3.8.3.19
+logical host name: Section 3.8.3.19, Section 4.14.5
+logical palettes: Section 4.13.5
+login name: Section 2.3, Section 3.8.3.4, Section 5.2.1.1
+login name, for auto-login: Section 4.15.1
+login name, for proxy: Section 4.16.4
+login name, local, in Rlogin: Section 4.18.1
+login name, local, in Windows: Section 4.18.1
+login names, different: Section 2.3, Section 4.23.7
+login, passwordless: Section 1.2, Section 4.18.1, Section 4.24, Section 8.2.7, Chapter 9
+login scripts: Section 10.6, Question A.7.1, Question A.7.4
+logo, PuTTY's: Section 2.3, Section A.5.3
+loopback IP address: Section 3.5, Section 4.16.2
+low-numbered port: Section 3.5, Section 4.18.1, Section 4.27
+-ls PSCP command-line option: Section 5.2.2.1
+MAC (message authentication code): Section 4.22, Section 4.28.8, Section 10.12, Section 10.12
+Mac OS: Question A.3.6
+magic cookie: Section 4.26.1
+mailing list: Section B.1
+man pages for PuTTY tools: PuTTY User Manual
+manually configuring host keys: Section 3.8.3.20, Section 4.21.2
+maximise window: Section 4.7.2, Question A.6.3
+maximum packet size: Section 4.28.5
+mc: Section 4.6.2
+-m command-line option: Section 3.8.3.6, Section 3.8.3.6
+menu, context: Section 3.1.1, Section 3.1.3, Section 4.11.1
+menu, system: Section 3.1.3, Section 3.1.3.7, Section 4.9.4, Section 4.9.5, Section 4.9.7
+message authentication code (MAC): Section 4.22, Section 4.28.8, Section 10.12, Section 10.12
+middle mouse button: Section 3.1.1, Section 4.11.1, Section 4.11.4
+Midnight Commander: Section 4.6.2
+minimise window: Section 4.9.1
+mistyping a password: Section 2.3
+MIT-MAGIC-COOKIE-1: Section 4.26.1
+modes of files, changing: Section 6.2.14
+mouse: Section 3.1.1
+mouse pointer: Section 3.1.1, Section 4.8.3
+mouse reporting: Section 3.1.1, Section 4.6.2, Section 4.11.2
+mouse, three-button: Section 3.1.1, Section 4.11.1
+moving files: Section 6.2.18
+MS-DOS Prompt: Section 1.1, Section 1.1, Section 3.8, Section 5.1, Section 7.1
+MUDs: Section 1.1, Section 2.1, Section 4.3.9
+multi-user systems: Section 3.8.2, Question A.8.2
+Nagle's algorithm: Section 4.14.2
+name resolution: Section 4.16.3
+name resolution, with proxy: Section 4.16.2, Section 4.16.3
+NAT routers: Section 10.16, Question A.7.8
+NaturallySpeaking: Section 4.9.4
+-nc: Section 3.8.3.14
+-N command-line option: Section 3.8.3.13
+negotiation, of Telnet options: Section 4.17.2
+NetHack keypad mode: Section 4.4.6
+Network Address Translation: Section 10.16, Question A.7.8
+network connection: Section 3.5, Section 4.14, Section 4.27
+network protocols: Section 1.1
+NEW_ENVIRON: Section 4.17.1
+new line: Section 4.3.3, Section 4.3.4, Section 4.17.4
+new line, in Telnet: Section 4.17.4
+‘New Session’: Section 3.1.3.3, Question A.7.22
+new version, verifying: Section 3.8.3.21, Appendix E
+NNTP: Section 3.6
+-noagent: Section 3.8.3.9
+-no-antispoof: Section 7.2.3.6
+non-destructive backspace: Section 4.6.8
+No Operation, Telnet special command: Section 3.1.3.2
+No-op, in SSH: Section 3.1.3.2
+-no-sanitise-stderr: Section 5.2.2.7, Section 6.1.4.1, Section 7.2.3.5
+-no-sanitise-stdout: Section 7.2.3.5
+numeric keypad: Section 4.4.3
+numeric keypad, ‘Application’ mode: Section 4.4.5, Section 4.6.1
+Num Lock: Section 4.4.5, Section 4.4.6
+OLD_ENVIRON: Section 4.17.1
+one-time passwords: Section 4.23.4
+OpenSSH: Section 3.5, Section 4.23.7, Section 4.27, Section 4.27.1, Section 4.28.6, Section 4.28.9, Section 8.2.10, Section 8.3, Section 9.4, Section 10.5, Question A.7.18, Question A.10.1
+OpenSSH private key file format: Section 8.2.12
+option negotiation, Telnet: Section 4.17.2
+options, command-line: Section 3.8, Section 9.3
+out of memory: Section 10.6, Question A.7.3, Question A.7.4
+overriding host keys: Section 3.8.3.20, Section 4.21.2
+packet log, SSH: Section 4.2, Section 4.2.5
+Pageant: Section 3.8.3.9, Section 3.8.3.10, Section 4.23.6, Section 4.23.8, Section 4.28.13, Section 8.1, Chapter 9
+palettes, logical: Section 4.13.5
+passive Telnet negotiation: Section 4.17.2
+passphrase: Section 8.1, Section 8.2.7, Chapter 9
+passthrough printing: Section 4.3.10
+password: Section 2.3, Section 3.8.3.8
+password camouflage: Section 4.28.11, Section 4.28.12
+password expiry: Section 4.23.5
+password, for proxy: Section 4.16.4
+passwordless login: Section 1.2, Section 4.18.1, Section 4.24, Section 8.2.7, Chapter 9
+password, mistyping: Section 2.3
+password, one-time: Section 4.23.4
+password, plain text: Section 4.16.4, Section 4.16.4
+password prompt: Question A.7.12
+password, storing: Question A.2.8
+paste, copy and: Section 3.1.1, Section 4.6.2, Section 4.10.5, Section 4.11, Section 4.11.2, Question A.6.6
+patch: Section B.2
+PATH environment variable: Section 5.1, Section 6.1, Section 7.1
+-P command-line option: Section 3.8.3.7
+PC speaker: Section 4.5.1
+Pentium 4: Question A.3.1
+permissions on files, changing: Section 6.2.14
+-pgpfp command-line option: Section 3.8.3.21, Appendix E
+PGP key fingerprint: Section 3.8.3.21
+PGP signatures, of PuTTY binaries: Appendix E
+plain text password: Section 4.16.4, Section 4.16.4
+Plink: Chapter 7, Chapter 7
+PLINK_PROTOCOL environment variable: Section 7.2.2
+POP-3: Section 3.5
+port forwarding in SSH: Section 3.5, Section 3.8.3.5, Section 4.16, Section 4.19.2, Section 4.27
+port forwarding in SSH, changing mid-session: Section 4.27
+port number: Section 3.5, Section 3.8.3.7, Section 4.1.1, Section 4.27
+port, privileged: Section 3.5, Section 4.18.1, Section 4.27
+POSIX: Section 4.25.2, Section 6.2.2
+PPK file: Section 3.8.3.18, Section 4.23.8, Section 8.2.8, Section 8.2.12, Section 9.1
+-p PSCP command-line option: Section 5.2.2.2
+preserve file attributes: Section 5.2.2.2
+PRIMARY selection: Section 4.11.4
+printing, remote-controlled: Section 4.3.10
+private key: Section 3.8.3.18, Section 4.23.8, Section 8.1, Chapter 9
+private key file, OpenSSH: Section 8.2.12
+private key file, PuTTY: Section 3.8.3.18, Section 4.23.8, Section 8.2.8, Section 8.2.12, Section 9.1
+private key file, ssh.com: Section 8.2.12
+private keys, generating: Section 8.2
+privileged port: Section 3.5, Section 4.18.1, Section 4.27
+process ACL (Windows): Section 3.8.3.25, Section 9.3.3
+prompt: Section 2.4
+protocol: Section 2.1
+protocols, debugging: Section 3.6
+protocols, differences between: Section 1.2
+protocol selection: Section 3.8.3.2
+protocol version, SSH: Section 3.8.3.16, Section 4.19.4
+proxy authentication: Section 4.16.4
+-proxycmd: Section 3.8.3.24
+proxy command: Section 3.8.3.24, Section 4.16.1, Section 4.16.5
+proxy DNS: Section 4.16.2, Section 4.16.3
+proxy, HTTP: Section 4.16.1
+proxy logging: Section 4.16.6
+proxy password: Section 4.16.4
+proxy server: Section 4.14.4, Section 4.16
+proxy, SOCKS: Section 4.16.1
+proxy, Telnet: Section 4.16.1, Section 4.16.5, Section 4.17.2
+proxy user name: Section 4.16.4
+PSCP: Chapter 5, Chapter 5
+pseudo-terminal allocation: Section 3.8.3.12, Section 4.25.1
+PSFTP: Chapter 6, Chapter 6
+pterm: PuTTY User Manual, Question A.3.2
+pty allocation: Section 3.8.3.12, Section 4.25.1
+public key: Section 8.1
+public-key algorithm: Section 8.1
+public key authentication: Section 3.8.3.18, Section 4.23.8, Section 4.28.9, Section 5.2.4, Section 6.3, Section 7.2.2, Section 8.1
+public key file, SSH-2: Section 8.2.9
+public key fingerprint (SSH): Section 8.2.5, Section 9.2.1
+public keys, generating: Section 8.2
+punctuation: Section 4.12.1
+PuTTY Event Log: Section 3.1.3.1, Section 4.2
+PuTTYgen: Section 8.2
+PuTTY icon: Section 2.3, Section A.5.3
+putty.rnd (random seed file): Section 3.8.2, Question A.5.2
+putty @sessionname: Section 3.8.3.1
+PuTTYtel: Section 4.16.4
+PuTTY terminal window: Section 2.3, Section 3.1.1, Section 3.1.3, Section 4.1.3, Section 4.7, Section 4.8, Section 4.9, Section 4.13.7
+-pw command-line option: Section 3.8.3.8
+-q PSCP command-line option: Section 5.2.2.3
+QUIT, special character: Section 4.25.2
+quoting, in PSFTP: Section 6.2.1
+random seed file: Section 3.8.2
+-raw command-line option: Section 3.8.1, Section 3.8.3.2
+raw protocol: Section 2.1
+‘Raw’ protocol: Section 3.6
+raw TCP connections: Section 3.6, Section 4.1.1
+RC4: Section 4.22, Section 10.4
+-R command-line option: Section 3.8.3.5
+reading commands from a file: Section 3.8.3.6
+read permission: Section 6.2.14
+receiving files: Section 5.2.1, Section 6.2.9
+rectangular selection: Section 3.1.1, Section 4.11.3
+recursive: Section 5.2.2.4, Section 6.2.9, Section 6.2.10
+Red Hat Linux: Question A.7.15
+registry entries, removing: Section 3.8.2
+Registry (Windows): Section 2.2, Section 4.1.2, Section 4.30, Question A.5.2
+remote commands: Section 2.4, Section 3.8.3.6, Section 4.19.1, Section 4.19.2, Question A.6.2
+remote-controlled printing: Section 4.3.10
+remote echo: Section 4.3.8
+remote network connection: Section 3.8.3.14
+remote shell: Section 4.19.2
+remote shell, suppressing: Section 3.8.3.13
+remote-to-local port forwarding: Section 3.5, Section 3.8.3.5, Section 4.27
+removing directories: Section 6.2.17
+removing files: Section 6.2.15
+removing registry entries: Section 3.8.2
+renaming files: Section 6.2.18
+repeat key exchange: Section 3.1.3.2, Section 4.20.2, Section 4.28.2, Question A.7.20
+Repeat key exchange, SSH special command: Section 3.1.3.2
+‘Reset Terminal’: Section 3.1.3.6
+resizing, terminal: Section 4.6.3, Section 4.7.1, Section 4.7.2
+‘Restart Session’: Section 3.1.3.3
+-restrict-acl: Section 3.8.3.25, Section 9.3.3
+-restrict-putty-acl: Section 3.8.3.25
+resuming file transfers: Section 6.2.12
+return value: Section 5.2.3
+RFC: Section 4.17.1
+RGB values: Section 4.13.7
+.rhosts file: Section 4.18.1
+‘rhosts’ file: Section 4.18.1
+Rich Text Format: Section 4.12.2
+right mouse button: Section 3.1.1, Section 4.11.1
+right mouse button menu: Section 3.1.1, Section 3.1.3, Section 4.11.1
+right mouse button, with Ctrl: Section 3.1.1
+right-to-left text: Section 4.6.11
+Rijndael: Section 4.22
+Rlogin: Section 2.1, Section 4.1.1, Section 4.18
+-rlogin command-line option: Section 3.8.1, Section 3.8.3.2
+Rlogin, differences from SSH and Telnet: Section 1.2
+routers: Section 4.14.1
+routers, NAT: Section 10.16, Question A.7.8
+rows, in terminal window: Section 4.7.1
+-r PSCP command-line option: Section 5.2.2.4
+RSA: Section 4.21.1, Section 4.28.6, Section 4.28.13, Section 8.1, Section 8.2.2
+RSA authentication: Section 3.8.3.18, Section 4.23.8, Section 4.28.9, Section 5.2.4, Section 6.3, Section 7.2.2, Section 8.1
+RSA key exchange: Section 4.20.1
+RTF: Section 4.12.2
+Russian: Section 4.10.3
+rxvt: Section 4.4.2
+-sanitise-stderr: Section 5.2.2.7, Section 6.1.4.1, Section 7.2.3.5
+-sanitise-stdout: Section 7.2.3.5
+saved sessions, loading from command line: Section 3.8.3.1
+‘Saved Sessions’ submenu: Section 3.1.3.3
+saving private keys: Section 8.2.12
+saving settings: Section 4.1.2
+saving settings in a file: Section 4.30
+SCO: Section 4.4.3
+SCP protocol: Section 5.2.1, Section 5.2.2.6
+-scp PSCP command-line option: Section 5.2.2.6
+screen, clearing: Section 4.3.5
+scripts: Section 7.3
+scrollback: Section 3.1.2, Section 4.7.3
+scrollback clearing: Section 4.6.7
+scrollback, clearing: Section 3.1.3.6
+scrollbar: Section 3.1.2, Section 4.7.3
+scrolling region: Section 4.3.2
+SECONDARY selection: Section 4.11.4.2
+secret, shared: Section 4.20
+secure shell: Section 1.2
+security hazard: Section 4.6.6, Section 4.16.4, Section 5.2.1, Section 9.5
+security token: Section 4.23.4
+selecting a protocol: Section 1.2, Section 3.8.3.2
+selecting text: Section 3.1.1, Section 4.11.1
+selecting whole lines: Section 3.1.1
+selecting whole words: Section 3.1.1, Section 4.12.1
+selection, adjusting: Section 3.1.1, Section 4.11.1
+selection, CLIPBOARD: Section 4.11.4
+selection, PRIMARY: Section 4.11.4
+selection, rectangular: Section 3.1.1, Section 4.11.3
+selection, SECONDARY: Section 4.11.4.2
+selections, multiple: Section 4.11.4
+sending files: Section 5.2.1, Section 6.2.10
+-sercfg command-line option: Section 3.8.3.22
+Serial: Section 4.29
+-serial command-line option: Section 3.8.1, Section 3.8.3.2
+serial line: Section 4.1.1, Section 4.29
+serial port: Section 4.29
+server: Section 1.1
+server, commands on: Section 2.4, Section 3.8.3.6, Section 4.19.1, Section 4.19.2, Question A.6.2
+server, HTTP: Section 4.16.1
+server name: Section 2.1, Section 4.1.1, Section 4.9.1, Section 4.14.4, Section 5.2.1.2
+server name resolution: Section 4.16.3
+server name resolution, with proxy: Section 4.16.2, Section 4.16.3
+server, proxy: Section 4.14.4, Section 4.16
+server, SOCKS: Section 4.16.1
+service names: Section 4.27
+session ID: Section 4.28.9
+session log: Section 3.2
+-sessionlog: Section 3.8.3.23
+@sessionname command-line argument: Section 3.8.3.1
+sessions, loading and storing: Section 4.1.2
+session, starting: Section 2.1
+set-group-ID bit: Section 6.2.14
+settings, changing: Section 3.1.3.4
+settings, default: Section 3.8.1, Section 4.1.2
+settings, loading and storing: Section 4.1.2
+set-user-ID bit: Section 6.2.14
+SFTP: Section 5.2.1, Section 5.2.2.6, Chapter 6
+-sftp PSCP command-line option: Section 5.2.2.6
+shaping, of Arabic text: Section 4.6.10
+shared secret: Section 4.20
+-shareexists Plink command-line option: Section 7.2.3.4
+-share-plink: Section 7.2.3.3
+shell account: Section 1.1
+shell, remote: Section 4.19.2
+shell, remote, suppressing: Section 3.8.3.13
+Shift-Backspace: Section 4.4.1
+Shift-Ins: Section 3.1.1, Section 4.11.4.2
+Shift-PgDn: Section 3.1.2
+Shift-PgUp: Section 3.1.2
+shortcut, Windows: Section 3.8, Section 3.8.3.1, Section 9.3, Question A.6.4
+Signal, SSH special command: Section 3.1.3.2
+signature: Section 4.28.6, Section 8.1
+signatures, of PuTTY binaries: Appendix E
+single-DES: Section 4.22, Section 10.4
+single sign-on: Section 4.15.2, Section 4.24
+single-width character: Section 4.10.2
+size, of font: Section 4.7.2, Section 4.8.2
+size, of window: Section 4.7.1
+S/Key: Section 4.23.4, Section 4.23.5
+SMB: Question A.7.17
+SMTP: Section 3.6
+SOCKS port forwarding: Section 3.5, Section 3.8.3.5, Section 4.27
+SOCKS proxy: Section 4.16.1
+SO_KEEPALIVE: Section 4.14.3
+sound file: Section 4.5.1
+spaces in filenames: Section 6.2.1, Question A.6.9
+special character: Section 4.25.2
+special commands: Section 3.1.3.2
+special commands, in SSH: Section 3.1.3.2
+special commands, in Telnet: Section 3.1.3.2, Section 4.17.3
+speed, terminal: Section 4.15.4
+-s Plink command-line option: Section 7.2.3.2
+spoofing: Section 2.2, Section 4.18.1, Section 8.1
+SSH: Section 2.1, Section 2.2, Section 4.1.1, Section 4.19
+SSH-1: Section 3.8.3.16, Section 4.19.4
+SSH-2: Section 3.8.3.16, Section 4.15.5, Section 4.19.2, Section 4.19.4, Section 10.1, Section 10.3
+ssh-add: Section 9.4
+SSH agent forwarding: Section 3.8.3.10, Section 4.23.6, Section 9.4
+ssh.com: Section 4.28.10, Section 8.2.9, Section 8.3, Section 9.4
+-ssh command-line option: Section 3.8.1, Section 3.8.3.2
+ssh.com private key file format: Section 8.2.12
+SSH, differences from Telnet and Rlogin: Section 1.2
+.ssh directory: Section 8.3
+.ssh2 directory: Section 8.3
+SSH file transfer protocol: Section 5.2.1, Section 5.2.2.6, Chapter 6
+SSH host key fingerprint: Section 2.2
+SSH ‘ignore’ messages: Section 3.1.3.2, Section 4.28.1, Section 4.28.11
+SSH key exchange, forcing repeat: Section 3.1.3.2
+ssh-keygen: Section 9.2.1
+-sshlog: Section 3.8.3.23
+SSH packet log: Section 4.2, Section 4.2.5
+SSH port forwarding: Section 3.5, Section 3.8.3.5, Section 4.16, Section 4.19.2, Section 4.27
+SSH port forwarding, changing mid-session: Section 4.27
+SSH protocol version: Section 3.8.3.16, Section 4.19.4
+SSH-2 public key file format: Section 8.2.9
+SSH public key fingerprint: Section 8.2.5, Section 9.2.1
+-sshrawlog: Section 3.8.3.23
+SSH server bugs: Section 4.28
+SSH special commands: Section 3.1.3.2
+SSH subsystem: Section 7.2.3.2
+SSH tunnelling: Section 3.5, Section 3.8.3.5, Section 4.16, Section 4.19.2, Section 4.27
+SSH tunnelling, changing mid-session: Section 4.27
+SSH X11 forwarding: Section 3.4, Section 3.8.3.11, Section 4.26
+SSPI: Section 4.24.2
+stair-stepping: Section 4.3.3
+standard error, proxy: Section 4.16.6
+starting a session: Section 2.1
+Start Menu: Section 5.1
+startup scripts: Section 10.6, Question A.7.1, Question A.7.4
+statistics: Section 5.2.2.3
+sticky bit: Section 6.2.14
+storing passwords: Question A.2.8
+storing settings: Section 4.1.2
+storing settings in a file: Section 4.30
+stty: Section 4.4.1, Section 4.25.2
+subsystem, SSH: Section 7.2.3.2
+Sun SSH: Section 10.5
+supported features: Section A.2
+support requests: Section B.6
+Suspend Process, Telnet special command: Section 3.1.3.2, Section 4.17.3
+swap file: Section 9.5
+switches, command-line: Section 3.8, Section 9.3
+symmetric-key algorithm: Section 4.22
+Synch, Telnet special command: Section 3.1.3.2
+system colours: Section 4.13.6
+SYSTEM32 directory, on Windows: Question A.7.22
+system menu: Section 3.1.3, Section 3.1.3.7, Section 4.9.4, Section 4.9.5, Section 4.9.7
+system tray: Section 9.1
+talker systems: Section 1.1, Section 4.3.9
+taskbar: Section 4.5.2
+-T command-line option: Section 3.8.3.12
+-t command-line option: Section 3.8.3.12
+TCP connections, raw: Section 3.6, Section 4.1.1
+TCP keepalives: Section 4.14.3
+TCP_NODELAY: Section 4.14.2
+TCP proxy: Section 4.16.1, Section 4.16.5, Section 4.17.2
+Telnet: Section 2.1, Section 4.1.1, Section 4.17
+-telnet command-line option: Section 3.8.1, Section 3.8.3.2
+Telnet, differences from SSH and Rlogin: Section 1.2
+Telnet New Line: Section 4.17.4
+Telnet option negotiation: Section 4.17.2
+Telnet proxy: Section 4.16.1, Section 4.16.5, Section 4.17.2
+Telnet special commands: Section 3.1.3.2, Section 4.17.3
+Telnet URLs: Section 3.8.1
+termcap: Section 4.4, Section 4.15.3
+TERM environment variable: Section 4.13.2
+terminal bell: Section 4.5
+terminal bell, disabling: Section 4.5.1, Section 4.5.3
+terminal bell overload mode: Section 4.5.3
+terminal control sequences: Section 3.2, Section 4.3.1, Section 4.3.2, Section 4.3.6, Section 4.6.2, Section 4.9.1, Section 4.10.4, Section 4.11.2, Section 4.12.1, Section 4.13.1, Section 4.13.4, Section 4.15.3, Section 7.2.1
+terminal emulation: Section 3.1.3.6, Section 4.3, Section 4.3.7, Section 4.4, Section 4.6, Section 4.15.3
+terminal modes: Section 4.25.2
+terminal, resetting: Section 3.1.3.6
+terminal resizing: Section 4.6.3, Section 4.7.1, Section 4.7.2
+terminal speed: Section 4.15.4
+terminal type: Question A.5.1
+terminal window: Section 2.3, Section 3.1.1, Section 3.1.3, Section 4.1.3, Section 4.7, Section 4.8, Section 4.9, Section 4.13.7
+terminal window, inactive: Section 4.1.3
+terminfo: Section 4.4, Section 4.15.3
+three-button mouse: Section 3.1.1, Section 4.11.1
+timeout, of connections: Section 4.14.1, Question A.7.8
+timestamp: Section 5.2.2.2
+TIS authentication: Section 4.23.4
+token, security: Section 4.23.4
+transferring files: Chapter 5, Chapter 6
+triple-click: Section 3.1.1
+triple-DES: Section 4.22
+trn: Section 4.6.2
+trusting host keys: Section 2.2
+tunnelling using SSH: Section 3.5, Section 3.8.3.5, Section 4.16, Section 4.19.2, Section 4.27
+tunnelling using SSH, changing mid-session: Section 4.27
+typeface: Section 4.8.2, Section 4.10.4, Section 4.12.2, Section 4.13.4
+UDP: Section 4.27
+Unicode: Section 4.6.10, Section 4.10.1, Section 4.10.4, Section 4.10.5
+uninstalling: Question A.8.2
+Unix: Section 4.4, Section 4.4.1, Section 4.15.3, Section 4.25.1, Section 6.2.14, Section 10.18, Question A.7.13
+Unix version of PuTTY tools: PuTTY User Manual, Question A.3.2
+-unsafe PSCP command-line option: Section 5.2.1
+upgraded version, verifying: Section 3.8.3.21, Appendix E
+uploading files: Section 5.2.1, Section 6.2.10
+Uppity: Question A.2.10
+URLs, Telnet: Section 3.8.1
+US-ASCII: Section 4.10.5, Question A.2.11
+user name: Section 2.3, Section 3.8.3.4, Section 5.2.1.1
+user name, for auto-login: Section 4.15.1
+user name, for proxy: Section 4.16.4
+user name, local, in Rlogin: Section 4.18.1
+user name, local, in Windows: Section 4.18.1
+user names, different: Section 2.3, Section 4.23.7
+UTF-8: Section 4.10.1, Section 4.10.2, Section 4.25.2, Question A.7.15
+variables, environment: Section 4.15.5, Section 4.17.1
+-v command-line option: Section 3.8.3.3
+VERASE, special character: Section 4.25.2
+verbose mode: Section 3.8.3.3
+verifying new versions of PuTTY: Section 3.8.3.21, Appendix E
+verifying the host key: Section 2.2, Question A.2.9
+version, of Internet Protocol: Section 3.8.3.17, Section 4.14.4, Section 4.27.2
+version, of PuTTY: Section B.2
+version, of SSH protocol: Section 3.8.3.16, Section 4.19.4
+visual bell: Section 4.5.1
+VQUIT, special character: Section 4.25.2
+VT100+: Section 4.4.3
+VT400: Section 4.4.3
+vt220: Section 4.15.3
+WAV file: Section 4.5.1
+web browser: Section 3.5, Section 3.8.1
+web server: Section 1.1
+web site: Section B.7
+white space: Section 4.12.1
+wildcards: Section 5.2.1, Section 5.2.1.3, Section 5.2.2.6, Section 6.2.2, Section 6.2.11
+WinCVS: Section 7.5
+window border: Section 4.8.4
+window caption: Section 4.5.2, Section 4.9.1
+window, closing: Section 4.1.3, Section 4.9.2, Section 4.9.3
+window, inactive: Section 4.1.3
+window, maximising: Section 4.7.2, Question A.6.3
+window menu: Section 3.1.3, Section 3.1.3.7, Section 4.9.4, Section 4.9.5, Section 4.9.7
+window, minimising: Section 4.9.1
+window resizing: Section 4.6.3, Section 4.7.1, Section 4.7.2
+Windows 3.1: Question A.3.5
+Windows, 32-bit: Question A.6.10
+Windows, 64-bit: Question A.6.10, Question A.7.22
+Windows clipboard: Section 3.1.1
+Windows command: Section 6.2.19
+Windows Default Beep sound: Section 4.5
+Windows file sharing: Question A.7.17
+window size: Section 4.7.1
+Windows process ACL: Section 3.8.3.25, Section 9.3.3
+Windows Registry: Section 2.2, Section 4.1.2, Section 4.30, Question A.5.2
+Windows shortcut: Section 3.8, Section 3.8.3.1, Section 9.3, Question A.6.4
+Windows Terminal Services: Question A.7.17
+Windows XP: Question A.7.17, Question A.7.21
+window, terminal: Section 2.3, Section 3.1.1, Section 3.1.3, Section 4.1.3, Section 4.7, Section 4.8, Section 4.9, Section 4.13.7
+window title: Section 4.6.5, Section 4.6.6, Section 4.9.1, Question A.7.11
+Win32s: Question A.3.5
+Win125x: Section 4.10.1
+words, selecting: Section 3.1.1, Section 4.12.1
+working directory: Section 6.2.7, Section 6.2.8
+wrapping, automatic: Section 4.3.1, Question A.7.7
+wrapping, terminal: Section 4.10.2
+write permission: Section 6.2.14
+X11 authentication: Section 4.26.1
+x86 (32-bit processor architecture): Question A.6.10
+-X command-line option: Section 3.8.3.11
+-x command-line option: Section 3.8.3.11
+‘X display location’: Section 3.4
+XDM-AUTHORIZATION-1: Section 4.26.1
+X11 forwarding: Section 3.4, Section 3.8.3.11, Section 4.26
+X server: Section 3.4
+xterm: Section 3.1.1, Section 4.4.2, Section 4.4.3, Section 4.11.1, Section 4.15.3
+xterm mouse reporting: Section 3.1.1, Section 4.6.2, Section 4.11.2

+

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/blurb.but b/doc/blurb.but index e5e03a6..f980e9f 100644 --- a/doc/blurb.but +++ b/doc/blurb.but @@ -33,8 +33,8 @@ Plink, Pageant and PuTTYgen. Windows versions of the PuTTY utilities. Some options are therefore mentioned that are absent from the \i{Unix version}; the Unix version has features not described here; and the \i\cw{pterm} and command-line -\cw{puttygen} utilities are not described at all. The only -Unix-specific documentation that currently exists is the +\cw{puttygen} and \cw{pageant} utilities are not described at all. The +only Unix-specific documentation that currently exists is the \I{man pages for PuTTY tools}man pages. \copyright This manual is copyright \shortcopyrightdetails. All diff --git a/doc/config.but b/doc/config.but index 96323ce..58ed670 100644 --- a/doc/config.but +++ b/doc/config.but @@ -14,8 +14,6 @@ save your settings to be reloaded later. \S{config-hostname} The \i{host name} section -\cfg{winhelp-topic}{session.hostname} - The top box on the Session panel, labelled \q{Specify your connection by host name}, contains the details that need to be filled in before PuTTY can open a session at all. @@ -45,8 +43,6 @@ and \q{Speed}; see \k{config-serial} for more details of these. \S{config-saving} \ii{Loading and storing saved sessions} -\cfg{winhelp-topic}{session.saved} - The next part of the Session configuration panel allows you to save your preferred PuTTY options so they will appear automatically the next time you start PuTTY. It also allows you to create \e{saved @@ -111,18 +107,16 @@ Saved sessions are stored in the \i{Registry}, at the location If you need to store them in a file, you could try the method described in \k{config-file}. -\S{config-closeonexit} \q{\ii{Close Window} on Exit} - -\cfg{winhelp-topic}{session.coe} +\S{config-closeonexit} \q{\ii{Close window} on exit} Finally in the Session panel, there is an option labelled \q{Close -Window on Exit}. This controls whether the PuTTY \i{terminal window} +window on exit}. This controls whether the PuTTY \i{terminal window} disappears as soon as the session inside it terminates. If you are likely to want to copy and paste text out of the session after it has terminated, or restart the session, you should arrange for this option to be off. -\q{Close Window On Exit} has three settings. \q{Always} means always +\q{Close window on exit} has three settings. \q{Always} means always close the window on exit; \q{Never} means never close on exit (always leave the window open, but \I{inactive window}inactive). The third setting, and the default one, is \q{Only on clean exit}. In this @@ -132,8 +126,6 @@ confusing message from the server will leave the window up. \H{config-logging} The Logging panel -\cfg{winhelp-topic}{logging.main} - The Logging configuration panel allows you to save \i{log file}s of your PuTTY sessions, for debugging, analysis or future reference. @@ -182,8 +174,6 @@ even if enabled via saved settings. \S{config-logfilename} \q{Log file name} -\cfg{winhelp-topic}{logging.filename} - In this edit box you enter the name of the file you want to log the session to. The \q{Browse} button will let you look around your file system to find the right place to put the file; or if you already @@ -219,8 +209,6 @@ like \S{config-logfileexists} \q{What to do if the log file already exists} -\cfg{winhelp-topic}{logging.exists} - This control allows you to specify what PuTTY should do if it tries to start writing to a log file and it finds the file already exists. You might want to automatically destroy the existing log file and @@ -232,8 +220,6 @@ comes up. \S{config-logflush} \I{log file, flushing}\q{Flush log file frequently} -\cfg{winhelp-topic}{logging.flush} - This option allows you to control how frequently logged data is flushed to disc. By default, PuTTY will flush data as soon as it is displayed, so that if you view the log file while a session is still @@ -248,8 +234,6 @@ at the end of a session). \S{config-logheader} \I{log file, header}\q{Include header} -\cfg{winhelp-topic}{logging.header} - This option allows you to choose whether to include a header line with the date and time when the log file is opened. It may be useful to disable this if the log file is being used as realtime input to other @@ -267,8 +251,6 @@ glean a lot of useful information from even these obfuscated logs \S2{config-logssh-omitpw} \q{Omit known password fields} -\cfg{winhelp-topic}{logging.ssh.omitpassword} - When checked, decrypted password fields are removed from the log of transmitted packets. (This includes any user responses to challenge-response authentication methods such as @@ -285,8 +267,6 @@ This option is enabled by default. \S2{config-logssh-omitdata} \q{Omit session data} -\cfg{winhelp-topic}{logging.ssh.omitdata} - When checked, all decrypted \q{session data} is omitted; this is defined as data in terminal sessions and in forwarded channels (TCP, X11, and authentication agent). This will usually substantially reduce @@ -301,8 +281,6 @@ of PuTTY's \i{terminal emulation}. \S{config-autowrap} \q{Auto wrap mode initially on} -\cfg{winhelp-topic}{terminal.autowrap} - \ii{Auto wrap mode} controls what happens when text printed in a PuTTY window reaches the right-hand edge of the window. @@ -325,8 +303,6 @@ immediately. \S{config-decom} \q{DEC Origin Mode initially on} -\cfg{winhelp-topic}{terminal.decom} - \i{DEC Origin Mode} is a minor option which controls how PuTTY interprets cursor-position \i{control sequence}s sent by the server. @@ -355,8 +331,6 @@ immediately. \S{config-crlf} \q{Implicit CR in every LF} -\cfg{winhelp-topic}{terminal.lfhascr} - Most servers send two control characters, \i{CR} and \i{LF}, to start a \i{new line} of the screen. The CR character makes the cursor return to the left-hand side of the screen. The LF character makes the cursor move @@ -380,8 +354,6 @@ option, and things might go back to normal: \S{config-lfcr} \q{Implicit LF in every CR} -\cfg{winhelp-topic}{terminal.crhaslf} - Most servers send two control characters, \i{CR} and \i{LF}, to start a \i{new line} of the screen. The CR character makes the cursor return to the left-hand side of the screen. The LF character makes the cursor move @@ -393,8 +365,6 @@ a line feed so that all lines are displayed. \S{config-erase} \q{Use \i{background colour} to erase screen} -\cfg{winhelp-topic}{terminal.bce} - Not all terminals agree on what colour to turn the screen when the server sends a \q{\i{clear screen}} sequence. Some terminals believe the screen should always be cleared to the \e{default} background @@ -417,8 +387,6 @@ immediately. \S{config-blink} \q{Enable \i{blinking text}} -\cfg{winhelp-topic}{terminal.blink} - The server can ask PuTTY to display text that blinks on and off. This is very distracting, so PuTTY allows you to turn blinking text off completely. @@ -436,8 +404,6 @@ immediately. \S{config-answerback} \q{\ii{Answerback} to ^E} -\cfg{winhelp-topic}{terminal.answerback} - This option controls what PuTTY will send back to the server if the server sends it the ^E \i{enquiry character}. Normally it just sends the string \q{PuTTY}. @@ -460,8 +426,6 @@ You can include control characters in the answerback string using \S{config-localecho} \q{\ii{Local echo}} -\cfg{winhelp-topic}{terminal.localecho} - With local echo disabled, characters you type into the PuTTY window are not echoed in the window \e{by PuTTY}. They are simply sent to the server. (The \e{server} might choose to \I{remote echo}echo them @@ -477,8 +441,6 @@ relying on the automatic detection. \S{config-localedit} \q{\ii{Local line editing}} -\cfg{winhelp-topic}{terminal.localedit} - Normally, every character you type into the PuTTY window is sent immediately to the server the moment you type it. @@ -505,8 +467,6 @@ instead of relying on the automatic detection. \S{config-printing} \ii{Remote-controlled printing} -\cfg{winhelp-topic}{terminal.printing} - A lot of VT100-compatible terminals support printing under control of the remote server (sometimes called \q{passthrough printing}). PuTTY supports this feature as well, but it is turned off by default. @@ -548,8 +508,6 @@ seems to help, you may find \k{faq-keyboard} to be useful. \S{config-backspace} Changing the action of the \ii{Backspace key} -\cfg{winhelp-topic}{keyboard.backspace} - Some terminals believe that the Backspace key should send the same thing to the server as \i{Control-H} (ASCII code 8). Other terminals believe that the Backspace key should send ASCII code 127 (usually @@ -576,8 +534,6 @@ isn't configured here as the default.) \S{config-homeend} Changing the action of the \i{Home and End keys} -\cfg{winhelp-topic}{keyboard.homeend} - The Unix terminal emulator \i\c{rxvt} disagrees with the rest of the world about what character sequences should be sent to the server by the Home and End keys. @@ -592,8 +548,6 @@ working, you could try switching this option to see if it helps. \S{config-funkeys} Changing the action of the \i{function keys} and \i{keypad} -\cfg{winhelp-topic}{keyboard.funkeys} - This option affects the function keys (F1 to F12) and the top row of the numeric keypad. @@ -628,8 +582,6 @@ fiddle with it. \S{config-appcursor} Controlling \i{Application Cursor Keys} mode -\cfg{winhelp-topic}{keyboard.appcursor} - Application Cursor Keys mode is a way for the server to change the control sequences sent by the arrow keys. In normal mode, the arrow keys send \c{ESC [A} through to \c{ESC [D}. In application mode, @@ -645,8 +597,6 @@ the \q{Features} configuration panel; see \S{config-appkeypad} Controlling \i{Application Keypad} mode -\cfg{winhelp-topic}{keyboard.appkeypad} - Application Keypad mode is a way for the server to change the behaviour of the numeric keypad. @@ -673,8 +623,6 @@ You can also disable application keypad mode completely, using the \S{config-nethack} Using \i{NetHack keypad mode} -\cfg{winhelp-topic}{keyboard.nethack} - PuTTY has a special mode for playing NetHack. You can enable it by selecting \q{NetHack} in the \q{Initial state of numeric keypad} control. @@ -694,8 +642,6 @@ on. We don't know why. \S{config-compose} Enabling a DEC-like \ii{Compose key} -\cfg{winhelp-topic}{keyboard.compose} - DEC terminals have a Compose key, which provides an easy-to-remember way of typing \i{accented characters}. You press Compose and then type two more characters. The two characters are \q{combined} to produce @@ -709,8 +655,6 @@ Compose key} option, the AltGr key will become a Compose key. \S{config-ctrlalt} \q{Control-Alt is different from \i{AltGr}} -\cfg{winhelp-topic}{keyboard.ctrlalt} - Some old keyboards do not have an AltGr key, which can make it difficult to type some characters. PuTTY can be configured to treat the key combination Ctrl + Left Alt the same way as the AltGr key. @@ -743,8 +687,6 @@ actions. \S{config-bellstyle} \q{Set the style of bell} -\cfg{winhelp-topic}{bell.style} - This control allows you to select various different actions to occur on a terminal bell: @@ -773,8 +715,6 @@ control \q{Custom sound file to play as a bell}. \S{config-belltaskbar} \q{\ii{Taskbar}/\I{window caption}caption indication on bell} -\cfg{winhelp-topic}{bell.taskbar} - This feature controls what happens to the PuTTY window's entry in the Windows Taskbar if a bell occurs while the window does not have the input focus. @@ -794,8 +734,6 @@ continuously flash on and off until you select the window. \S{config-bellovl} \q{Control the \i{bell overload} behaviour} -\cfg{winhelp-topic}{bell.overload} - A common user error in a terminal session is to accidentally run the Unix command \c{cat} (or equivalent) on an inappropriate file type, such as an executable, image file, or ZIP file. This produces a huge @@ -840,8 +778,6 @@ PuTTY's more advanced terminal features, in case they cause trouble. \S{config-features-application} Disabling application keypad and cursor keys -\cfg{winhelp-topic}{features.application} - \I{Application Keypad}Application keypad mode (see \k{config-appkeypad}) and \I{Application Cursor Keys}application cursor keys mode (see \k{config-appcursor}) alter the behaviour of @@ -852,8 +788,6 @@ tries to do. \S{config-features-mouse} Disabling \cw{xterm}-style \i{mouse reporting} -\cfg{winhelp-topic}{features.mouse} - PuTTY allows the server to send \i{control codes} that let it take over the mouse and use it for purposes other than \i{copy and paste}. Applications which use this feature include the text-mode web @@ -872,8 +806,6 @@ feature off (see \k{config-mouseshift}). \S{config-features-resize} Disabling remote \i{terminal resizing} -\cfg{winhelp-topic}{features.resize} - PuTTY has the ability to change the terminal's size and position in response to commands from the server. If you find PuTTY is doing this unexpectedly or inconveniently, you can tell PuTTY not to @@ -881,8 +813,6 @@ respond to those server commands. \S{config-features-altscreen} Disabling switching to the \i{alternate screen} -\cfg{winhelp-topic}{features.altscreen} - Many terminals, including PuTTY, support an \q{alternate screen}. This is the same size as the ordinary terminal screen, but separate. Typically a screen-based program such as a text editor might switch @@ -896,8 +826,6 @@ can disable the alternate screen feature completely. \S{config-features-retitle} Disabling remote \i{window title} changing -\cfg{winhelp-topic}{features.retitle} - PuTTY has the ability to change the window title in response to commands from the server. If you find PuTTY is doing this unexpectedly or inconveniently, you can tell PuTTY not to respond to @@ -905,8 +833,6 @@ those server commands. \S{config-features-qtitle} Response to remote \i{window title} querying -\cfg{winhelp-topic}{features.qtitle} - PuTTY can optionally provide the xterm service of allowing server applications to find out the local window title. This feature is disabled by default, but you can turn it on if you really want it. @@ -945,8 +871,6 @@ the reasons described above. \S{config-features-clearscroll} Disabling remote \i{scrollback clearing} -\cfg{winhelp-topic}{features.clearscroll} - PuTTY has the ability to clear the terminal's scrollback buffer in response to a command from the server. If you find PuTTY is doing this unexpectedly or inconveniently, you can tell PuTTY not to respond to @@ -954,8 +878,6 @@ that server command. \S{config-features-dbackspace} Disabling \i{destructive backspace} -\cfg{winhelp-topic}{features.dbackspace} - Normally, when PuTTY receives character 127 (^?) from the server, it will perform a \q{destructive backspace}: move the cursor one space left and delete the character under it. This can apparently cause @@ -966,8 +888,6 @@ deleting a character) instead. \S{config-features-charset} Disabling remote \i{character set} configuration -\cfg{winhelp-topic}{features.charset} - PuTTY has the ability to change its character set configuration in response to commands from the server. Some programs send these commands unexpectedly or inconveniently. In particular, \i{BitchX} (an @@ -980,8 +900,6 @@ disabling the remote character set configuration commands. \S{config-features-shaping} Disabling \i{Arabic text shaping} -\cfg{winhelp-topic}{features.arabicshaping} - PuTTY supports shaping of Arabic text, which means that if your server sends text written in the basic \i{Unicode} Arabic alphabet then it will convert it to the correct display forms before printing it @@ -1000,8 +918,6 @@ see \k{config-features-bidi}. \S{config-features-bidi} Disabling \i{bidirectional text} display -\cfg{winhelp-topic}{features.bidi} - PuTTY supports bidirectional text display, which means that if your server sends text written in a language which is usually displayed from right to left (such as \i{Arabic} or \i{Hebrew}) then PuTTY will @@ -1026,16 +942,12 @@ The Window configuration panel allows you to control aspects of the \S{config-winsize} Setting the \I{window size}size of the PuTTY window -\cfg{winhelp-topic}{window.size} - The \q{\ii{Columns}} and \q{\ii{Rows}} boxes let you set the PuTTY window to a precise size. Of course you can also \I{window resizing}drag the window to a new size while a session is running. \S{config-winsizelock} What to do when the window is resized -\cfg{winhelp-topic}{window.resize} - These options allow you to control what happens when the user tries to \I{window resizing}resize the PuTTY window using its window furniture. @@ -1058,8 +970,6 @@ resized at all. \S{config-scrollback} Controlling \i{scrollback} -\cfg{winhelp-topic}{window.scrollback} - These options let you configure the way PuTTY keeps text after it scrolls off the top of the screen (see \k{using-scrollback}). @@ -1079,8 +989,6 @@ scrollback on keypress}. \S{config-erasetoscrollback} \q{Push erased text into scrollback} -\cfg{winhelp-topic}{window.erased} - When this option is enabled, the contents of the terminal screen will be pushed into the scrollback when a server-side application clears the screen, so that your scrollback will contain a better @@ -1100,8 +1008,6 @@ the appearance of \I{PuTTY window}PuTTY's window. \S{config-cursor} Controlling the appearance of the \i{cursor} -\cfg{winhelp-topic}{appearance.cursor} - The \q{Cursor appearance} option lets you configure the cursor to be a block, an underline, or a vertical line. A block cursor becomes an empty box when the window loses focus; an underline or a vertical @@ -1112,8 +1018,6 @@ works in any of the cursor modes. \S{config-font} Controlling the \i{font} used in the terminal window -\cfg{winhelp-topic}{appearance.font} - This option allows you to choose what font, in what \I{font size}size, the PuTTY terminal window uses to display the text in the session. @@ -1127,8 +1031,6 @@ not look very good (but can work OK with some fonts). \S{config-mouseptr} \q{Hide \i{mouse pointer} when typing in window} -\cfg{winhelp-topic}{appearance.hidemouse} - If you enable this option, the mouse pointer will disappear if the PuTTY window is selected and you press a key. This way, it will not obscure any of the text in the window while you work in your @@ -1139,8 +1041,6 @@ visible at all times. \S{config-winborder} Controlling the \i{window border} -\cfg{winhelp-topic}{appearance.border} - PuTTY allows you to configure the appearance of the window border to some extent. @@ -1162,8 +1062,6 @@ the behaviour of \I{PuTTY window}PuTTY's window. \S{config-title} Controlling the \i{window title} -\cfg{winhelp-topic}{appearance.title} - The \q{Window title} edit box allows you to set the title of the PuTTY window. By default the window title will contain the \i{host name} followed by \q{PuTTY}, for example \c{server1.example.com - PuTTY}. @@ -1192,8 +1090,6 @@ icon title, none of this will happen.) \S{config-warnonclose} \q{Warn before \i{closing window}} -\cfg{winhelp-topic}{behaviour.closewarn} - If you press the \i{Close button} in a PuTTY window that contains a running session, PuTTY will put up a warning window asking if you really meant to close the window. A window whose session has already @@ -1204,8 +1100,6 @@ the \q{Warn before closing window} option. \S{config-altf4} \q{Window closes on \i{ALT-F4}} -\cfg{winhelp-topic}{behaviour.altf4} - By default, pressing ALT-F4 causes the \I{closing window}window to close (or a warning box to appear; see \k{config-warnonclose}). If you disable the \q{Window closes on ALT-F4} option, then pressing ALT-F4 @@ -1213,8 +1107,6 @@ will simply send a key sequence to the server. \S{config-altspace} \q{\ii{System menu} appears on \i{ALT-Space}} -\cfg{winhelp-topic}{behaviour.altspace} - If this option is enabled, then pressing ALT-Space will bring up the PuTTY window's menu, like clicking on the top left corner. If it is disabled, then pressing ALT-Space will just send \c{ESC SPACE} to @@ -1228,8 +1120,6 @@ the window. \S{config-altonly} \q{\ii{System menu} appears on \i{Alt} alone} -\cfg{winhelp-topic}{behaviour.altonly} - If this option is enabled, then pressing and releasing ALT will bring up the PuTTY window's menu, like clicking on the top left corner. If it is disabled, then pressing and releasing ALT will have @@ -1237,15 +1127,11 @@ no effect. \S{config-alwaysontop} \q{Ensure window is \i{always on top}} -\cfg{winhelp-topic}{behaviour.alwaysontop} - If this option is enabled, the PuTTY window will stay on top of all other windows. \S{config-fullscreen} \q{\ii{Full screen} on Alt-Enter} -\cfg{winhelp-topic}{behaviour.altenter} - If this option is enabled, then pressing Alt-Enter will cause the PuTTY window to become full-screen. Pressing Alt-Enter again will restore the previous window size. @@ -1262,8 +1148,6 @@ the character set understood by PuTTY. \S{config-charset} Controlling character set translation -\cfg{winhelp-topic}{translation.codepage} - During an interactive session, PuTTY receives a stream of 8-bit bytes from the server, and in order to display them on the screen it needs to know what character set to interpret them in. Similarly, @@ -1304,8 +1188,6 @@ installed, PuTTY will use it. \S{config-cjk-ambig-wide} \q{Treat \i{CJK} ambiguous characters as wide} -\cfg{winhelp-topic}{translation.cjkambigwide} - There are \I{East Asian Ambiguous characters}some Unicode characters whose \I{character width}width is not well-defined. In most contexts, such characters should be treated as single-width for the purposes of \I{wrapping, @@ -1322,8 +1204,6 @@ This option only has any effect in \i{UTF-8} mode (see \k{config-charset}). \S{config-cyr} \q{\i{Caps Lock} acts as \i{Cyrillic} switch} -\cfg{winhelp-topic}{translation.cyrillic} - This feature allows you to switch between a US/UK keyboard layout and a Cyrillic keyboard layout by using the Caps Lock key, if you need to type (for example) \i{Russian} and English side by side in the @@ -1334,8 +1214,6 @@ native keyboard layout is not US or UK. \S{config-linedraw} Controlling display of \i{line-drawing characters} -\cfg{winhelp-topic}{translation.linedraw} - VT100-series terminals allow the server to send \i{control sequence}s that shift temporarily into a separate character set for drawing simple lines and boxes. However, there are a variety of ways in which PuTTY @@ -1371,8 +1249,6 @@ miss out other characters from the main character set. \S{config-linedrawpaste} Controlling \i{copy and paste} of line drawing characters -\cfg{winhelp-topic}{selection.linedraw} - By default, when you copy and paste a piece of the PuTTY screen that contains VT100 line and box drawing characters, PuTTY will paste them in the form they appear on the screen: either \i{Unicode} line @@ -1392,8 +1268,6 @@ Unicode always. \S{config-utf8linedraw} Combining VT100 line-drawing with UTF-8 -\cfg{winhelp-topic}{translation.utf8linedraw} - If PuTTY is configured to treat data from the server as encoded in UTF-8, then by default it disables the older VT100-style system of control sequences that cause the lower-case letters to be temporarily @@ -1427,18 +1301,17 @@ work in the PuTTY window. \S{config-mouse} Changing the actions of the mouse buttons -\cfg{winhelp-topic}{selection.buttons} - PuTTY's copy and paste mechanism is by default modelled on the Unix \i\c{xterm} application. The X Window System uses a three-button mouse, -and the convention is that the \i{left button} \I{selecting text}selects, -the \i{right button} extends an existing selection, and the -\i{middle button} pastes. +and the convention in that system is that the \i{left button} +\I{selecting text}selects, the \i{right button} extends an existing +selection, and the \i{middle button} pastes. -Windows often only has two mouse buttons, so in PuTTY's default -configuration (\q{Compromise}), the \e{right} button pastes, and the -\e{middle} button (if you have one) \I{adjusting a selection}extends -a selection. +Windows often only has two mouse buttons, so when run on Windows, +PuTTY is configurable. In PuTTY's default configuration +(\q{Compromise}), the \e{right} button pastes, and the \e{middle} +button (if you have one) \I{adjusting a selection}extends a +selection. If you have a \i{three-button mouse} and you are already used to the \c{xterm} arrangement, you can select it using the \q{Action of @@ -1450,9 +1323,10 @@ which one of the options is \q{Paste}). (This context menu is always available by holding down Ctrl and right-clicking, regardless of the setting of this option.) -\S{config-mouseshift} \q{Shift overrides application's use of mouse} +(When PuTTY iself is running on Unix, it follows the X Window System +convention.) -\cfg{winhelp-topic}{selection.shiftdrag} +\S{config-mouseshift} \q{Shift overrides application's use of mouse} PuTTY allows the server to send \i{control codes} that let it \I{mouse reporting}take over the mouse and use it for purposes other @@ -1479,8 +1353,6 @@ all, you can do this using the Features control panel; see \S{config-rectselect} Default selection mode -\cfg{winhelp-topic}{selection.rect} - As described in \k{using-selection}, PuTTY has two modes of selecting text to be copied to the clipboard. In the default mode (\q{Normal}), dragging the mouse from point A to point B selects to @@ -1499,10 +1371,17 @@ you have to hold down Alt to get the \e{normal} behaviour. Here you can configure which clipboard(s) are written or read by PuTTY's various copy and paste actions. +Most platforms, including Windows, have a single system clipboard. +On these platforms, PuTTY provides a second clipboard-like facility by +permitting you to paste the text you last selected in \e{this window}, +whether or not it is currently also in the system clipboard. This is +not enabled by default. + The X Window System (which underlies most Unix graphical interfaces) provides multiple clipboards (or \q{\i{selections}}), and many applications support more than one of them by a different user -interface mechanism. +interface mechanism. When PuTTY itself is running on Unix, it has +more configurability relating to these selections. The two most commonly used selections are called \cq{\i{PRIMARY}} and \cq{\I{CLIPBOARD selection}CLIPBOARD}; in applications supporting both, @@ -1512,16 +1391,8 @@ the usual behaviour is that \cw{PRIMARY} is used by mouse-only actions is used by explicit Copy and Paste menu items or keypresses such as \i{Ctrl-C} and \i{Ctrl-V}. -On other platforms such as Windows, where there is a single system -clipboard, PuTTY provides a second clipboard-like facility by permitting -you to paste the text you last selected in \e{this window}, whether or -not it is currently also in the system clipboard. This is not enabled -by default. - \S2{config-selection-autocopy} \q{Auto-copy selected text} -\cfg{winhelp-topic}{selection.autocopy} - The checkbox \q{Auto-copy selected text to system clipboard} controls whether or not selecting text in the PuTTY terminal window automatically has the side effect of copying it to the system @@ -1530,13 +1401,12 @@ clipboard, without requiring a separate user interface action. On X, the wording of this option is changed slightly so that \cq{CLIPBOARD} is mentioned in place of the \q{system clipboard}. Text selected in the terminal window will \e{always} be automatically -placed in the \cw{PRIMARY} selection, but if you tick this box, it -will \e{also} be placed in \cq{CLIPBOARD} at the same time. +placed in the \cw{PRIMARY} selection, as is conventional, but if you +tick this box, it will \e{also} be placed in \cq{CLIPBOARD} at the +same time. \S2{config-selection-clipactions} Choosing a clipboard for UI actions -\cfg{winhelp-topic}{selection.clipactions} - PuTTY has three user-interface actions which can be configured to paste into the terminal (not counting menu items). You can click whichever mouse button (if any) is configured to paste (see @@ -1545,10 +1415,11 @@ whichever mouse button (if any) is configured to paste (see You can configure which of the available clipboards each of these actions pastes from (including turning the paste action off -completely). On platforms with a single system clipboard, the -available options are to paste from that clipboard or to paste from -PuTTY's internal memory of the \i{last selected text} within that -window. On X, the standard options are \cw{CLIPBOARD} or \cw{PRIMARY}. +completely). On platforms with a single system clipboard (such as +Windows), the available options are to paste from that clipboard or +to paste from PuTTY's internal memory of the \i{last selected text} +within that window. On X, the standard options are \cw{CLIPBOARD} or +\cw{PRIMARY}. (\cw{PRIMARY} is conceptually similar in that it \e{also} refers to the last selected text \dash just across all applications instead of @@ -1571,8 +1442,6 @@ configured in that particular way. \S{config-paste-ctrl-char} \q{Permit control characters in pasted text} -\cfg{winhelp-topic}{selection.pastectrl} - It is possible for the clipboard to contain not just text (with newlines and tabs) but also control characters such as ESC which could have surprising effects if pasted into a terminal session, depending @@ -1595,8 +1464,6 @@ copying from the terminal window to the clipboard. \S{config-charclasses} Character classes -\cfg{winhelp-topic}{copy.charclasses} - PuTTY will \I{word-by-word selection}select a word at a time in the terminal window if you \i{double-click} to begin the drag. This section allows you to control precisely what is considered to be a word. @@ -1637,8 +1504,6 @@ immediately. \S{config-rtfcopy} Copying in \i{Rich Text Format} -\cfg{winhelp-topic}{copy.rtf} - If you enable \q{Copy to clipboard in RTF as well as plain text}, PuTTY will write formatting information to the clipboard as well as the actual text you copy. The effect of this is @@ -1655,8 +1520,6 @@ The Colours panel allows you to control PuTTY's use of \i{colour}. \S{config-ansicolour} \q{Allow terminal to specify \i{ANSI colours}} -\cfg{winhelp-topic}{colours.ansi} - This option is enabled by default. If it is disabled, PuTTY will ignore any \i{control sequence}s sent by the server to request coloured text. @@ -1667,8 +1530,6 @@ and background colours. \S{config-xtermcolour} \q{Allow terminal to use xterm \i{256-colour mode}} -\cfg{winhelp-topic}{colours.xterm256} - This option is enabled by default. If it is disabled, PuTTY will ignore any control sequences sent by the server which use the extended 256-colour mode supported by recent versions of \cw{xterm}. @@ -1689,8 +1550,6 @@ try \cq{xterm-256color}. \S{config-truecolour} \q{Allow terminal to use 24-bit colour} -\cfg{winhelp-topic}{colours.truecolour} - This option is enabled by default. If it is disabled, PuTTY will ignore any control sequences sent by the server which use the control sequences supported by modern terminals to specify arbitrary 24-bit @@ -1698,8 +1557,6 @@ RGB colour value. \S{config-boldcolour} \q{Indicate bolded text by changing...} -\cfg{winhelp-topic}{colours.bold} - When the server sends a \i{control sequence} indicating that some text should be displayed in \i{bold}, PuTTY can handle this in several ways. It can either change the \i{font} for a bold version, or use the @@ -1719,8 +1576,6 @@ become invisible. \S{config-logpalette} \q{Attempt to use \i{logical palettes}} -\cfg{winhelp-topic}{colours.logpal} - Logical palettes are a mechanism by which a Windows application running on an \i{8-bit colour} display can select precisely the colours it wants instead of going with the Windows standard defaults. @@ -1731,8 +1586,6 @@ worked very well. \S{config-syscolour} \q{Use \i{system colours}} -\cfg{winhelp-topic}{colours.system} - Enabling this option will cause PuTTY to ignore the configured colours for \I{default background}\I{default foreground}\q{Default Background/Foreground} and \I{cursor colour}\q{Cursor Colour/Text} (see @@ -1744,8 +1597,6 @@ by font changes (see \k{config-boldcolour}). \S{config-colourcfg} Adjusting the colours in the \i{terminal window} -\cfg{winhelp-topic}{colours.config} - The main colour control allows you to specify exactly what colours things should be displayed in. To modify one of the PuTTY colours, use the list box to select which colour you want to modify. The \i{RGB @@ -1774,8 +1625,6 @@ more than one type of \i{connection}. \S{config-keepalive} Using \i{keepalives} to prevent disconnection -\cfg{winhelp-topic}{connection.keepalive} - If you find your sessions are closing unexpectedly (most often with \q{Connection reset by peer}) after they have been idle for a while, you might want to try using this option. @@ -1829,8 +1678,6 @@ it unable to deal with SSH-1 ignore messages (see \S{config-nodelay} \q{Disable \i{Nagle's algorithm}} -\cfg{winhelp-topic}{connection.nodelay} - Nagle's algorithm is a detail of TCP/IP implementations that tries to minimise the number of small data packets sent down a network connection. With Nagle's algorithm enabled, PuTTY's \i{bandwidth} usage @@ -1842,8 +1689,6 @@ The Nagle algorithm is disabled by default for \i{interactive connections}. \S{config-tcp-keepalives} \q{Enable \i{TCP keepalives}} -\cfg{winhelp-topic}{connection.tcpkeepalive} - \e{NOTE:} TCP keepalives should not be confused with the application-level keepalives described in \k{config-keepalive}. If in doubt, you probably want application-level keepalives; TCP keepalives @@ -1868,9 +1713,7 @@ are terminated than for keeping a connection alive. TCP keepalives are disabled by default. -\S{config-address-family} \I{Internet protocol version}\q{Internet protocol} - -\cfg{winhelp-topic}{connection.ipversion} +\S{config-address-family} \q{\i{Internet protocol version}} This option allows the user to select between the old and new Internet protocols and addressing schemes (\i{IPv4} and \i{IPv6}). @@ -1891,8 +1734,6 @@ explicitly set this to \q{IPv4} or \q{IPv6}. \S{config-loghost} \I{logical host name}\q{Logical name of remote host} -\cfg{winhelp-topic}{connection.loghost} - This allows you to tell PuTTY that the host it will really end up connecting to is different from where it thinks it is making a network connection. @@ -1950,8 +1791,6 @@ configuration panels. \S{config-username} \q{\ii{Auto-login username}} -\cfg{winhelp-topic}{connection.username} - All three of the SSH, Telnet and Rlogin protocols allow you to specify what user name you want to log in as, without having to type it explicitly every time. (Some Telnet servers don't support this.) @@ -1960,8 +1799,6 @@ In this box you can type that user name. \S{config-username-from-env} Use of system username -\cfg{winhelp-topic}{connection.usernamefromenv} - When the previous box (\k{config-username}) is left blank, by default, PuTTY will prompt for a username at the time you make a connection. @@ -1979,8 +1816,6 @@ is later used by a different user, that user's name will be used. \S{config-termtype} \q{\ii{Terminal-type} string} -\cfg{winhelp-topic}{connection.termtype} - Most servers you might connect to with PuTTY are designed to be connected to from lots of different types of terminal. In order to send the right \i{control sequence}s to each one, the server will need @@ -2004,8 +1839,6 @@ application or your server. \S{config-termspeed} \q{\ii{Terminal speed}s} -\cfg{winhelp-topic}{connection.termspeed} - The Telnet, Rlogin, and SSH protocols allow the client to specify terminal speeds to the server. @@ -2029,8 +1862,6 @@ This option has no effect on Raw connections. \S{config-environ} Setting \i{environment variables} on the server -\cfg{winhelp-topic}{telnet.environ} - The Telnet protocol provides a means for the client to pass environment variables to the server. Many Telnet servers have stopped supporting this feature due to security flaws, but PuTTY @@ -2053,8 +1884,6 @@ To remove one from the list, select it in the list box and press \H{config-proxy} The Proxy panel -\cfg{winhelp-topic}{proxy.main} - The \ii{Proxy} panel allows you to configure PuTTY to use various types of proxy in order to make its network connections. The settings in this panel affect the primary network connection forming your PuTTY @@ -2068,8 +1897,6 @@ it must always be explicitly configured. \S{config-proxy-type} Setting the proxy type -\cfg{winhelp-topic}{proxy.type} - The \q{Proxy type} radio buttons allow you to configure what type of proxy you want PuTTY to use for its network connections. The default setting is \q{None}; in this mode no proxy is used for any @@ -2110,8 +1937,6 @@ You can also enable this mode on the command line; see \S{config-proxy-exclude} Excluding parts of the network from proxying -\cfg{winhelp-topic}{proxy.exclude} - Typically you will only need to use a proxy to connect to non-local parts of your network; for example, your proxy might be required for connections outside your company's internal network. In the @@ -2152,8 +1977,6 @@ your list. \S{config-proxy-dns} \I{proxy DNS}\ii{Name resolution} when using a proxy -\cfg{winhelp-topic}{proxy.dns} - If you are using a proxy to access a private network, it can make a difference whether \i{DNS} name resolution is performed by PuTTY itself (on the client machine) or performed by the proxy. @@ -2182,8 +2005,6 @@ and your SOCKS 4 server cannot deal with it, this might be why. \S{config-proxy-auth} \I{proxy username}Username and \I{proxy password}password -\cfg{winhelp-topic}{proxy.auth} - If your proxy requires \I{proxy authentication}authentication, you can enter a username and a password in the \q{Username} and \q{Password} boxes. @@ -2216,8 +2037,6 @@ Telnet/Local proxy command (see \k{config-proxy-command}). \S{config-proxy-command} Specifying the Telnet or Local proxy command -\cfg{winhelp-topic}{proxy.command} - If you are using the \i{Telnet proxy} type, the usual command required by the firewall's Telnet server is \c{connect}, followed by a host name and a port number. If your proxy needs a different command, @@ -2253,8 +2072,6 @@ configuration fields will be ignored. \S{config-proxy-logging} Controlling \i{proxy logging} -\cfg{winhelp-topic}{proxy.logging} - Often the proxy interaction has its own diagnostic output; this is particularly the case for local proxy commands. @@ -2277,8 +2094,6 @@ Telnet sessions. \S{config-oldenviron} \q{Handling of OLD_ENVIRON ambiguity} -\cfg{winhelp-topic}{telnet.oldenviron} - The original Telnet mechanism for passing \i{environment variables} was badly specified. At the time the standard (RFC 1408) was written, BSD telnet implementations were already supporting the feature, and @@ -2301,8 +2116,6 @@ passing environment variables to quite an old server. \S{config-ptelnet} Passive and active \i{Telnet negotiation} modes -\cfg{winhelp-topic}{telnet.passive} - In a Telnet connection, there are two types of data passed between the client and the server: actual text, and \e{negotiations} about which Telnet extra features to use. @@ -2326,8 +2139,6 @@ passive mode to see if it helps. \S{config-telnetkey} \q{Keyboard sends \i{Telnet special commands}} -\cfg{winhelp-topic}{telnet.specialkeys} - If this box is checked, several key sequences will have their normal actions modified: @@ -2345,8 +2156,6 @@ unless you know what you're doing. \S{config-telnetnl} \q{Return key sends \i{Telnet New Line} instead of ^M} -\cfg{winhelp-topic}{telnet.newline} - Unlike most other remote login protocols, the Telnet protocol has a special \q{\i{new line}} code that is not the same as the usual line endings of Control-M or Control-J. By default, PuTTY sends the @@ -2366,8 +2175,6 @@ Rlogin sessions. \S{config-rlogin-localuser} \I{local username in Rlogin}\q{Local username} -\cfg{winhelp-topic}{rlogin.localuser} - Rlogin allows an automated (password-free) form of login by means of a file called \i\c{.rhosts} on the server. You put a line in your \c{.rhosts} file saying something like \c{jbloggs@pc1.example.com}, @@ -2404,8 +2211,6 @@ SSH sessions. \S{config-command} Executing a specific command on the server -\cfg{winhelp-topic}{ssh.command} - In SSH, you don't have to run a general shell session on the server. Instead, you can choose to run a single specific command (such as a mail user agent, for example). If you want to do this, enter the @@ -2417,8 +2222,6 @@ command. \S{config-ssh-noshell} \q{Don't start a \I{remote shell}shell or \I{remote command}command at all} -\cfg{winhelp-topic}{ssh.noshell} - If you tick this box, PuTTY will not attempt to run a shell or command after connecting to the remote server. You might want to use this option if you are only using the SSH connection for \i{port @@ -2438,8 +2241,6 @@ program. \S{config-ssh-comp} \q{Enable \i{compression}} -\cfg{winhelp-topic}{ssh.compress} - This enables data compression in the SSH connection: data sent by the server is compressed before sending, and decompressed at the client end. Likewise, data sent by PuTTY to the server is compressed @@ -2448,8 +2249,6 @@ make the most of a low-\i{bandwidth} connection. \S{config-ssh-prot} \q{\i{SSH protocol version}} -\cfg{winhelp-topic}{ssh.protocol} - This allows you to select whether to use \i{SSH protocol version 2} or the older \I{SSH-1}version 1. @@ -2471,8 +2270,6 @@ connection to SSH-1. \S{config-ssh-sharing} Sharing an SSH connection between PuTTY tools -\cfg{winhelp-topic}{ssh.sharing} - The controls in this box allow you to configure PuTTY to reuse an existing SSH connection, where possible. @@ -2559,8 +2356,6 @@ these settings affect SSH-1 at all. \S{config-ssh-kex-order} \ii{Key exchange algorithm} selection -\cfg{winhelp-topic}{ssh.kex.order} - PuTTY supports a variety of SSH-2 key exchange methods, and allows you to choose which one you prefer to use; configuration is similar to cipher selection (see \k{config-ssh-encryption}). @@ -2631,8 +2426,6 @@ at the same time as verifying your identity to it. \S{config-ssh-kex-rekey} \ii{Repeat key exchange} -\cfg{winhelp-topic}{ssh.kex.repeat} - If the session key negotiated at connection startup is used too much or for too long, it may become feasible to mount attacks against the SSH connection. Therefore, the SSH-2 protocol specifies that a new key @@ -2721,8 +2514,6 @@ these settings affect SSH-1 at all. \S{config-ssh-hostkey-order} \ii{Host key type} selection -\cfg{winhelp-topic}{ssh.hostkey.order} - PuTTY supports a variety of SSH-2 host key types, and allows you to choose which one you prefer to use to identify the server. Configuration is similar to cipher selection (see @@ -2755,8 +2546,6 @@ to that for cipher selection (see \k{config-ssh-encryption}). \S{config-ssh-kex-manual-hostkeys} \ii{Manually configuring host keys} -\cfg{winhelp-topic}{ssh.kex.manualhostkeys} - In some situations, if PuTTY's automated host key management is not doing what you need, you might need to manually configure PuTTY to accept a specific host key, or one of a specific set of host keys. @@ -2809,8 +2598,6 @@ key management will work as normal. \H{config-ssh-encryption} The Cipher panel -\cfg{winhelp-topic}{ssh.ciphers} - PuTTY supports a variety of different \i{encryption algorithm}s, and allows you to choose which one you prefer to use. You can do this by dragging the algorithms up and down in the list box (or moving them @@ -2868,8 +2655,6 @@ SSH sessions. \S{config-ssh-banner} \q{Display pre-authentication banner} -\cfg{winhelp-topic}{ssh.auth.banner} - SSH-2 servers can provide a message for clients to display to the prospective user before the user logs in; this is sometimes known as a pre-authentication \q{\i{banner}}. Typically this is used to provide @@ -2883,8 +2668,6 @@ entirely. \S{config-ssh-noauth} \q{Bypass authentication entirely} -\cfg{winhelp-topic}{ssh.auth.bypass} - In SSH-2, it is in principle possible to establish a connection without using SSH's mechanisms to identify or prove who you are to the server. An SSH server could prefer to handle authentication @@ -2911,8 +2694,6 @@ require an authentication step. \S{config-ssh-tryagent} \q{Attempt authentication using Pageant} -\cfg{winhelp-topic}{ssh.auth.pageant} - If this option is enabled, then PuTTY will look for Pageant (the SSH private-key storage agent) and attempt to authenticate with any suitable public keys Pageant currently holds. @@ -2930,8 +2711,6 @@ See \k{pageant} for more information about Pageant in general. \S{config-ssh-tis} \q{Attempt \I{TIS authentication}TIS or \i{CryptoCard authentication}} -\cfg{winhelp-topic}{ssh.auth.tis} - TIS and CryptoCard authentication are (despite their names) generic forms of simple \I{challenge/response authentication}challenge/response authentication available in SSH protocol version 1 only. You might use @@ -2950,8 +2729,6 @@ responses take. \S{config-ssh-ki} \q{Attempt \i{keyboard-interactive authentication}} -\cfg{winhelp-topic}{ssh.auth.ki} - The SSH-2 equivalent of TIS authentication is called \q{keyboard-interactive}. It is a flexible authentication method using an arbitrary sequence of requests and responses; so it is not @@ -2965,8 +2742,6 @@ to turn it off in case you should have trouble with it. \S{config-ssh-agentfwd} \q{Allow \i{agent forwarding}} -\cfg{winhelp-topic}{ssh.auth.agentfwd} - This option allows the SSH server to open forwarded connections back to your local copy of \i{Pageant}. If you are not running Pageant, this option will do nothing. @@ -2978,8 +2753,6 @@ there is a security risk involved with enabling this option; see \S{config-ssh-changeuser} \q{Allow attempted \i{changes of username} in SSH-2} -\cfg{winhelp-topic}{ssh.auth.changeuser} - In the SSH-1 protocol, it is impossible to change username after failing to authenticate. So if you mis-type your username at the PuTTY \q{login as:} prompt, you will not be able to change it except @@ -3000,8 +2773,6 @@ changes of username} option to modify PuTTY's behaviour. \S{config-ssh-privkey} \q{\ii{Private key} file for authentication} -\cfg{winhelp-topic}{ssh.auth.privkey} - This box is where you enter the name of your private key file if you are using \i{public key authentication}. See \k{pubkey} for information about public key authentication in SSH. @@ -3023,8 +2794,6 @@ PuTTY can't fall back to using this file itself. \H{config-ssh-auth-gssapi} The \i{GSSAPI} panel -\cfg{winhelp-topic}{ssh.auth.gssapi} - The \q{GSSAPI} subpanel of the \q{Auth} panel controls the use of GSSAPI authentication. This is a mechanism which delegates the authentication exchange to a library elsewhere on the client @@ -3058,8 +2827,6 @@ of GSSAPI at all, and the rest of this panel will be unused. \S{config-ssh-auth-gssapi-delegation} \q{Allow GSSAPI credential delegation} -\cfg{winhelp-topic}{ssh.auth.gssapi.delegation} - \i{GSSAPI credential delegation} is a mechanism for passing on your Kerberos (or other) identity to the session on the SSH server. If you enable this option, then not only will PuTTY be able to log in @@ -3088,8 +2855,6 @@ for the delegation to expire during your session. See \S{config-ssh-auth-gssapi-libraries} Preference order for GSSAPI libraries -\cfg{winhelp-topic}{ssh.auth.gssapi.libraries} - GSSAPI is a mechanism which allows more than one authentication method to be accessed through the same interface. Therefore, more than one authentication library may exist on your system which can @@ -3122,8 +2887,6 @@ The TTY panel lets you configure the remote pseudo-terminal. \S{config-ssh-pty} \I{pseudo-terminal allocation}\q{Don't allocate a pseudo-terminal} -\cfg{winhelp-topic}{ssh.nopty} - When connecting to a \i{Unix} system, most \I{interactive connections}interactive shell sessions are run in a \e{pseudo-terminal}, which allows the Unix system to pretend it's talking to a real physical @@ -3137,8 +2900,6 @@ the usual way of working. \S{config-ttymodes} Sending \i{terminal modes} -\cfg{winhelp-topic}{ssh.ttymodes} - The SSH protocol allows the client to send \q{terminal modes} for the remote pseudo-terminal. These usually control the server's expectation of the local terminal's behaviour. @@ -3234,8 +2995,6 @@ you may find you need to set it to not be sent at all. When set to \H{config-ssh-x11} The X11 panel -\cfg{winhelp-topic}{ssh.tunnels.x11} - The X11 panel allows you to configure \i{forwarding of X11} over an SSH connection. @@ -3254,8 +3013,6 @@ forwarding. \S{config-ssh-x11auth} Remote \i{X11 authentication} -\cfg{winhelp-topic}{ssh.tunnels.x11auth} - If you are using X11 forwarding, the virtual X server created on the SSH server machine will be protected by authorisation data. This data is invented, and checked, by PuTTY. @@ -3301,8 +3058,6 @@ should be sure you know what you're doing. \S{config-ssh-xauthority} X authority file for local display -\cfg{winhelp-topic}{ssh.tunnels.xauthority} - If you are using X11 forwarding, the local X server to which your forwarded connections are eventually directed may itself require authorisation. @@ -3322,8 +3077,6 @@ any authorisation for your local display. \H{config-ssh-portfwd} \I{port forwarding}The Tunnels panel -\cfg{winhelp-topic}{ssh.tunnels.portfwd} - The Tunnels panel allows you to configure tunnelling of arbitrary connection types through an SSH connection. @@ -3413,8 +3166,6 @@ details of this. \S{config-ssh-portfwd-localhost} Controlling the visibility of forwarded ports -\cfg{winhelp-topic}{ssh.tunnels.portfwd.localhost} - The source port for a forwarded connection usually does not accept connections from any machine except the \I{localhost}SSH client or server machine itself (for local and remote forwardings respectively). @@ -3434,8 +3185,6 @@ SSH-2 servers support it (\i{OpenSSH} 3.0 does not, for example). \S{config-ssh-portfwd-address-family} Selecting \i{Internet protocol version} for forwarded ports -\cfg{winhelp-topic}{ssh.tunnels.portfwd.ipversion} - This switch allows you to select a specific Internet protocol (\i{IPv4} or \i{IPv6}) for the local end of a forwarded port. By default, it is set on \q{Auto}, which means that: @@ -3485,72 +3234,8 @@ three states: \b \q{Auto}: PuTTY will use the server's version number announcement to try to guess whether or not the server has the bug. -\S{config-ssh-bug-ignore1} \q{Chokes on SSH-1 \i{ignore message}s} - -\cfg{winhelp-topic}{ssh.bugs.ignore1} - -An ignore message (SSH_MSG_IGNORE) is a message in the SSH protocol -which can be sent from the client to the server, or from the server -to the client, at any time. Either side is required to ignore the -message whenever it receives it. PuTTY uses ignore messages to -\I{password camouflage}hide the password packet in SSH-1, so that -a listener cannot tell the length of the user's password; it also -uses ignore messages for connection \i{keepalives} (see -\k{config-keepalive}). - -If this bug is detected, PuTTY will stop using ignore messages. This -means that keepalives will stop working, and PuTTY will have to fall -back to a secondary defence against SSH-1 password-length -eavesdropping. See \k{config-ssh-bug-plainpw1}. If this bug is -enabled when talking to a correct server, the session will succeed, -but keepalives will not work and the session might be more -vulnerable to eavesdroppers than it could be. - -\S{config-ssh-bug-plainpw1} \q{Refuses all SSH-1 \i{password camouflage}} - -\cfg{winhelp-topic}{ssh.bugs.plainpw1} - -When talking to an SSH-1 server which cannot deal with ignore -messages (see \k{config-ssh-bug-ignore1}), PuTTY will attempt to -disguise the length of the user's password by sending additional -padding \e{within} the password packet. This is technically a -violation of the SSH-1 specification, and so PuTTY will only do it -when it cannot use standards-compliant ignore messages as -camouflage. In this sense, for a server to refuse to accept a padded -password packet is not really a bug, but it does make life -inconvenient if the server can also not handle ignore messages. - -If this \q{bug} is detected, PuTTY will assume that neither ignore -messages nor padding are acceptable, and that it thus has no choice -but to send the user's password with no form of camouflage, so that -an eavesdropping user will be easily able to find out the exact length -of the password. If this bug is enabled when talking to a correct -server, the session will succeed, but will be more vulnerable to -eavesdroppers than it could be. - -This is an SSH-1-specific bug. SSH-2 is secure against this type of -attack. - -\S{config-ssh-bug-rsa1} \q{Chokes on SSH-1 \i{RSA} authentication} - -\cfg{winhelp-topic}{ssh.bugs.rsa1} - -Some SSH-1 servers cannot deal with RSA authentication messages at -all. If \i{Pageant} is running and contains any SSH-1 keys, PuTTY will -normally automatically try RSA authentication before falling back to -passwords, so these servers will crash when they see the RSA attempt. - -If this bug is detected, PuTTY will go straight to password -authentication. If this bug is enabled when talking to a correct -server, the session will succeed, but of course RSA authentication -will be impossible. - -This is an SSH-1-specific bug. - \S{config-ssh-bug-ignore2} \q{Chokes on SSH-2 \i{ignore message}s} -\cfg{winhelp-topic}{ssh.bugs.ignore2} - An ignore message (SSH_MSG_IGNORE) is a message in the SSH protocol which can be sent from the client to the server, or from the server to the client, at any time. Either side is required to ignore the @@ -3564,9 +3249,25 @@ ignore messages. If this bug is enabled when talking to a correct server, the session will succeed, but keepalives will not work and the session might be less cryptographically secure than it could be. -\S{config-ssh-bug-winadj} \q{Chokes on PuTTY's SSH-2 \cq{winadj} requests} +\S{config-ssh-bug-rekey} \q{Handles SSH-2 key re-exchange badly} + +Some SSH servers cannot cope with \i{repeat key exchange} at +all, and will ignore attempts by the client to start one. Since +PuTTY pauses the session while performing a repeat key exchange, the +effect of this would be to cause the session to hang after an hour +(unless you have your rekey timeout set differently; see +\k{config-ssh-kex-rekey} for more about rekeys). +Other, very old, SSH servers handle repeat key exchange even more +badly, and disconnect upon receiving a repeat key exchange request. -\cfg{winhelp-topic}{ssh.bugs.winadj} +If this bug is detected, PuTTY will never initiate a repeat key +exchange. If this bug is enabled when talking to a correct server, +the session should still function, but may be less secure than you +would expect. + +This is an SSH-2-specific bug. + +\S{config-ssh-bug-winadj} \q{Chokes on PuTTY's SSH-2 \cq{winadj} requests} PuTTY sometimes sends a special request to SSH servers in the middle of channel data, with the name \cw{winadj@putty.projects.tartarus.org} @@ -3587,43 +3288,45 @@ believes the server has this bug, it will never send its \cq{winadj@putty.projects.tartarus.org} request, and will make do without its timing data. -\S{config-ssh-bug-hmac2} \q{Miscomputes SSH-2 HMAC keys} - -\cfg{winhelp-topic}{ssh.bugs.hmac2} - -Versions 2.3.0 and below of the SSH server software from -\cw{ssh.com} compute the keys for their \i{HMAC} \i{message authentication -code}s incorrectly. A typical symptom of this problem is that PuTTY -dies unexpectedly at the beginning of the session, saying -\q{Incorrect MAC received on packet}. - -If this bug is detected, PuTTY will compute its HMAC keys in the -same way as the buggy server, so that communication will still be -possible. If this bug is enabled when talking to a correct server, -communication will fail. +\S{config-ssh-bug-chanreq} \q{Replies to requests on closed channels} -This is an SSH-2-specific bug. +The SSH protocol as published in RFC 4254 has an ambiguity which +arises if one side of a connection tries to close a channel, while the +other side simultaneously sends a request within the channel and asks +for a reply. RFC 4254 leaves it unclear whether the closing side +should reply to the channel request after having announced its +intention to close the channel. -\S{config-ssh-bug-derivekey2} \q{Miscomputes SSH-2 \i{encryption} keys} +Discussion on the \cw{ietf-ssh} mailing list in April 2014 formed a +clear consensus that the right answer is no. However, because of the +ambiguity in the specification, some SSH servers have implemented the +other policy; for example, +\W{https://bugzilla.mindrot.org/show_bug.cgi?id=1818}{OpenSSH used to} +until it was fixed. -\cfg{winhelp-topic}{ssh.bugs.derivekey2} +Because PuTTY sends channel requests with the \q{want reply} flag +throughout channels' lifetime (see \k{config-ssh-bug-winadj}), it's +possible that when connecting to such a server it might receive a +reply to a request after it thinks the channel has entirely closed, +and terminate with an error along the lines of \q{Received +\cw{SSH2_MSG_CHANNEL_FAILURE} for nonexistent channel 256}. -Versions below 2.0.11 of the SSH server software from \i\cw{ssh.com} -compute the keys for the session encryption incorrectly. This -problem can cause various error messages, such as \q{Incoming packet -was garbled on decryption}, or possibly even \q{Out of memory}. +\S{config-ssh-bug-maxpkt2} \q{Ignores SSH-2 \i{maximum packet size}} -If this bug is detected, PuTTY will compute its encryption keys in -the same way as the buggy server, so that communication will still -be possible. If this bug is enabled when talking to a correct -server, communication will fail. +When an SSH-2 channel is set up, each end announces the maximum size +of data packet that it is willing to receive for that channel. Some +servers ignore PuTTY's announcement and send packets larger than PuTTY +is willing to accept, causing it to report \q{Incoming packet was +garbled on decryption}. -This is an SSH-2-specific bug. +If this bug is detected, PuTTY never allows the channel's +\i{flow-control window} to grow large enough to allow the server to +send an over-sized packet. If this bug is enabled when talking to a +correct server, the session will work correctly, but download +performance will be less than it could be. \S{config-ssh-bug-sig} \q{Requires padding on SSH-2 \i{RSA} \i{signatures}} -\cfg{winhelp-topic}{ssh.bugs.rsapad2} - Versions below 3.3 of \i{OpenSSH} require SSH-2 RSA signatures to be padded with zero bytes to the same length as the RSA key modulus. The SSH-2 specification says that an unpadded signature MUST be @@ -3639,9 +3342,37 @@ to talking to OpenSSH. This is an SSH-2-specific bug. -\S{config-ssh-bug-pksessid2} \q{Misuses the \i{session ID} in SSH-2 PK auth} +\S{config-ssh-bug-oldgex2} \q{Only supports pre-RFC4419 SSH-2 DH GEX} + +The SSH key exchange method that uses Diffie-Hellman group exchange +was redesigned after its original release, to use a slightly more +sophisticated setup message. Almost all SSH implementations switched +over to the new version. (PuTTY was one of the last.) A few old +servers still only support the old one. + +If this bug is detected, and the client and server negotiate +Diffie-Hellman group exchange, then PuTTY will send the old message +now known as \cw{SSH2_MSG_KEX_DH_GEX_REQUEST_OLD} in place of the new +\cw{SSH2_MSG_KEX_DH_GEX_REQUEST}. + +This is an SSH-2-specific bug. + +\S{config-ssh-bug-hmac2} \q{Miscomputes SSH-2 HMAC keys} + +Versions 2.3.0 and below of the SSH server software from +\cw{ssh.com} compute the keys for their \i{HMAC} \i{message authentication +code}s incorrectly. A typical symptom of this problem is that PuTTY +dies unexpectedly at the beginning of the session, saying +\q{Incorrect MAC received on packet}. -\cfg{winhelp-topic}{ssh.bugs.pksessid2} +If this bug is detected, PuTTY will compute its HMAC keys in the +same way as the buggy server, so that communication will still be +possible. If this bug is enabled when talking to a correct server, +communication will fail. + +This is an SSH-2-specific bug. + +\S{config-ssh-bug-pksessid2} \q{Misuses the \i{session ID} in SSH-2 PK auth} Versions below 2.3 of \i{OpenSSH} require SSH-2 \i{public-key authentication} to be done slightly differently: the data to be signed by the client @@ -3657,83 +3388,75 @@ SSH-2 public-key authentication will fail. This is an SSH-2-specific bug. -\S{config-ssh-bug-rekey} \q{Handles SSH-2 key re-exchange badly} - -\cfg{winhelp-topic}{ssh.bugs.rekey2} +\S{config-ssh-bug-derivekey2} \q{Miscomputes SSH-2 \i{encryption} keys} -Some SSH servers cannot cope with \i{repeat key exchange} at -all, and will ignore attempts by the client to start one. Since -PuTTY pauses the session while performing a repeat key exchange, the -effect of this would be to cause the session to hang after an hour -(unless you have your rekey timeout set differently; see -\k{config-ssh-kex-rekey} for more about rekeys). -Other, very old, SSH servers handle repeat key exchange even more -badly, and disconnect upon receiving a repeat key exchange request. +Versions below 2.0.11 of the SSH server software from \i\cw{ssh.com} +compute the keys for the session encryption incorrectly. This +problem can cause various error messages, such as \q{Incoming packet +was garbled on decryption}, or possibly even \q{Out of memory}. -If this bug is detected, PuTTY will never initiate a repeat key -exchange. If this bug is enabled when talking to a correct server, -the session should still function, but may be less secure than you -would expect. +If this bug is detected, PuTTY will compute its encryption keys in +the same way as the buggy server, so that communication will still +be possible. If this bug is enabled when talking to a correct +server, communication will fail. This is an SSH-2-specific bug. -\S{config-ssh-bug-maxpkt2} \q{Ignores SSH-2 \i{maximum packet size}} - -\cfg{winhelp-topic}{ssh.bugs.maxpkt2} - -When an SSH-2 channel is set up, each end announces the maximum size -of data packet that it is willing to receive for that channel. Some -servers ignore PuTTY's announcement and send packets larger than PuTTY -is willing to accept, causing it to report \q{Incoming packet was -garbled on decryption}. - -If this bug is detected, PuTTY never allows the channel's -\i{flow-control window} to grow large enough to allow the server to -send an over-sized packet. If this bug is enabled when talking to a -correct server, the session will work correctly, but download -performance will be less than it could be. +\S{config-ssh-bug-ignore1} \q{Chokes on SSH-1 \i{ignore message}s} -\S{config-ssh-bug-chanreq} \q{Replies to requests on closed channels} +An ignore message (SSH_MSG_IGNORE) is a message in the SSH protocol +which can be sent from the client to the server, or from the server +to the client, at any time. Either side is required to ignore the +message whenever it receives it. PuTTY uses ignore messages to +\I{password camouflage}hide the password packet in SSH-1, so that +a listener cannot tell the length of the user's password; it also +uses ignore messages for connection \i{keepalives} (see +\k{config-keepalive}). -\cfg{winhelp-topic}{ssh.bugs.chanreq} +If this bug is detected, PuTTY will stop using ignore messages. This +means that keepalives will stop working, and PuTTY will have to fall +back to a secondary defence against SSH-1 password-length +eavesdropping. See \k{config-ssh-bug-plainpw1}. If this bug is +enabled when talking to a correct server, the session will succeed, +but keepalives will not work and the session might be more +vulnerable to eavesdroppers than it could be. -The SSH protocol as published in RFC 4254 has an ambiguity which -arises if one side of a connection tries to close a channel, while the -other side simultaneously sends a request within the channel and asks -for a reply. RFC 4254 leaves it unclear whether the closing side -should reply to the channel request after having announced its -intention to close the channel. +\S{config-ssh-bug-plainpw1} \q{Refuses all SSH-1 \i{password camouflage}} -Discussion on the \cw{ietf-ssh} mailing list in April 2014 formed a -clear consensus that the right answer is no. However, because of the -ambiguity in the specification, some SSH servers have implemented the -other policy; for example, -\W{https://bugzilla.mindrot.org/show_bug.cgi?id=1818}{OpenSSH used to} -until it was fixed. +When talking to an SSH-1 server which cannot deal with ignore +messages (see \k{config-ssh-bug-ignore1}), PuTTY will attempt to +disguise the length of the user's password by sending additional +padding \e{within} the password packet. This is technically a +violation of the SSH-1 specification, and so PuTTY will only do it +when it cannot use standards-compliant ignore messages as +camouflage. In this sense, for a server to refuse to accept a padded +password packet is not really a bug, but it does make life +inconvenient if the server can also not handle ignore messages. -Because PuTTY sends channel requests with the \q{want reply} flag -throughout channels' lifetime (see \k{config-ssh-bug-winadj}), it's -possible that when connecting to such a server it might receive a -reply to a request after it thinks the channel has entirely closed, -and terminate with an error along the lines of \q{Received -\cw{SSH2_MSG_CHANNEL_FAILURE} for nonexistent channel 256}. +If this \q{bug} is detected, PuTTY will assume that neither ignore +messages nor padding are acceptable, and that it thus has no choice +but to send the user's password with no form of camouflage, so that +an eavesdropping user will be easily able to find out the exact length +of the password. If this bug is enabled when talking to a correct +server, the session will succeed, but will be more vulnerable to +eavesdroppers than it could be. -\S{config-ssh-bug-oldgex2} \q{Only supports pre-RFC4419 SSH-2 DH GEX} +This is an SSH-1-specific bug. SSH-2 is secure against this type of +attack. -\cfg{winhelp-topic}{ssh.bugs.oldgex2} +\S{config-ssh-bug-rsa1} \q{Chokes on SSH-1 \i{RSA} authentication} -The SSH key exchange method that uses Diffie-Hellman group exchange -was redesigned after its original release, to use a slightly more -sophisticated setup message. Almost all SSH implementations switched -over to the new version. (PuTTY was one of the last.) A few old -servers still only support the old one. +Some SSH-1 servers cannot deal with RSA authentication messages at +all. If \i{Pageant} is running and contains any SSH-1 keys, PuTTY will +normally automatically try RSA authentication before falling back to +passwords, so these servers will crash when they see the RSA attempt. -If this bug is detected, and the client and server negotiate -Diffie-Hellman group exchange, then PuTTY will send the old message -now known as \cw{SSH2_MSG_KEX_DH_GEX_REQUEST_OLD} in place of the new -\cw{SSH2_MSG_KEX_DH_GEX_REQUEST}. +If this bug is detected, PuTTY will go straight to password +authentication. If this bug is enabled when talking to a correct +server, the session will succeed, but of course RSA authentication +will be impossible. -This is an SSH-2-specific bug. +This is an SSH-1-specific bug. \H{config-serial} The Serial panel @@ -3742,8 +3465,6 @@ when PuTTY is connecting to a local \I{serial port}\i{serial line}. \S{config-serial-line} Selecting a serial line to connect to -\cfg{winhelp-topic}{serial.line} - The \q{Serial line to connect to} box allows you to choose which serial line you want PuTTY to talk to, if your computer has more than one serial port. @@ -3757,8 +3478,6 @@ the connection type is set to \q{Serial}. \S{config-serial-speed} Selecting the speed of your serial line -\cfg{winhelp-topic}{serial.speed} - The \q{Speed} box allows you to choose the speed (or \q{baud rate}) at which to talk to the serial line. Typical values might be 9600, 19200, 38400 or 57600. Which one you need will depend on the device @@ -3771,23 +3490,17 @@ connection type is set to \q{Serial}. \S{config-serial-databits} Selecting the number of data bits -\cfg{winhelp-topic}{serial.databits} - The \q{Data bits} box allows you to choose how many data bits are transmitted in each byte sent or received through the serial line. Typical values are 7 or 8. \S{config-serial-stopbits} Selecting the number of stop bits -\cfg{winhelp-topic}{serial.stopbits} - The \q{Stop bits} box allows you to choose how many stop bits are used in the serial line protocol. Typical values are 1, 1.5 or 2. \S{config-serial-parity} Selecting the serial parity checking scheme -\cfg{winhelp-topic}{serial.parity} - The \q{Parity} box allows you to choose what type of parity checking is used on the serial line. The settings are: @@ -3807,8 +3520,6 @@ always set to 0. \S{config-serial-flow} Selecting the serial flow control scheme -\cfg{winhelp-topic}{serial.flow} - The \q{Flow control} box allows you to choose what type of flow control checking is used on the serial line. The settings are: diff --git a/doc/copy.but b/doc/copy.but new file mode 100644 index 0000000..29ad643 --- /dev/null +++ b/doc/copy.but @@ -0,0 +1,5 @@ +\# Generated by licence.pl from LICENCE. +\# You should edit those files rather than editing this one. + +\define{shortcopyrightdetails} 1997-2019 Simon Tatham + diff --git a/doc/errors.but b/doc/errors.but index 8e353fb..a9c15c1 100644 --- a/doc/errors.but +++ b/doc/errors.but @@ -13,8 +13,6 @@ bug (see \k{feedback}) and we will add documentation for it. \H{errors-hostkey-absent} \q{The server's host key is not cached in the registry} -\cfg{winhelp-topic}{errors.hostkey.absent} - This error message occurs when PuTTY connects to a new SSH server. Every server identifies itself by means of a host key; once PuTTY knows the host key for a server, it will be able to detect if a @@ -36,8 +34,6 @@ See \k{gs-hostkey} for more information on host keys. \H{errors-hostkey-wrong} \q{WARNING - POTENTIAL SECURITY BREACH!} -\cfg{winhelp-topic}{errors.hostkey.changed} - This message, followed by \q{The server's host key does not match the one PuTTY has cached in the registry}, means that PuTTY has connected to the SSH server before, knows what its host key @@ -57,7 +53,7 @@ in the same way as you would if it was new. See \k{gs-hostkey} for more information on host keys. \H{errors-ssh-protocol} \q{SSH protocol version 2 required by our -configuration but server only provides (old, insecure) SSH-1} +configuration but remote only provides (old, insecure) SSH-1} By default, PuTTY only supports connecting to SSH servers that implement \i{SSH protocol version 2}. If you see this message, the @@ -80,11 +76,15 @@ attack. This occurs when the SSH server does not offer any ciphers which you have configured PuTTY to consider strong enough. By default, PuTTY -puts up this warning only for \ii{single-DES} and \i{Arcfour} encryption. +puts up this warning only for \i{Blowfish}, \ii{single-DES}, and +\i{Arcfour} encryption. See \k{config-ssh-encryption} for more information on this message. -\H{errors-toomanyauth} \q{Server sent disconnect message type 2 +(There are similar messages for other cryptographic primitives, such +as host key algorithms.) + +\H{errors-toomanyauth} \q{Remote side sent disconnect message type 2 (protocol error): "Too many authentication failures for root"} This message is produced by an \i{OpenSSH} (or \i{Sun SSH}) server if it @@ -141,10 +141,8 @@ Similarly, any error message starting with \q{Assertion failed} is a bug in PuTTY. Please report it to us, and include the exact text from the error message box. -\H{errors-cant-load-key} \q{Unable to use this private key file}, -\q{Couldn't load private key}, \q{Key is of wrong type} - -\cfg{winhelp-topic}{errors.cantloadkey} +\H{errors-cant-load-key} \q{Unable to use key file}, +\q{Couldn't load private key}, \q{Couldn't load this key} Various forms of this error are printed in the PuTTY window, or written to the PuTTY Event Log (see \k{using-eventlog}) when trying @@ -155,18 +153,18 @@ If you see one of these messages, it often indicates that you've tried to load a key of an inappropriate type into PuTTY, Plink, PSCP, PSFTP, or Pageant. -You may have specified a key that's inappropriate for the connection -you're making. The SSH-1 and SSH-2 protocols require different private -key formats, and a SSH-1 key can't be used for a SSH-2 connection (or -vice versa). - -Alternatively, you may have tried to load an SSH-2 key in a \q{foreign} +You may have tried to load an SSH-2 key in a \q{foreign} format (OpenSSH or \cw{ssh.com}) directly into one of the PuTTY tools, in which case you need to import it into PuTTY's native format -(\c{*.PPK}) using PuTTYgen - see \k{puttygen-conversions}. +(\c{*.PPK}) using PuTTYgen \dash see \k{puttygen-conversions}. + +Alternatively, you may have specified a key that's inappropriate for +the connection you're making. The SSH-2 and the old SSH-1 protocols +require different private key formats, and a SSH-1 key can't be used +for a SSH-2 connection (or vice versa). -\H{errors-refused} \q{Server refused our public key} or \q{Key -refused} +\H{errors-refused} \q{Server refused our key}, +\q{Server refused our public key}, \q{Key refused} Various forms of this error are printed in the PuTTY window, or written to the PuTTY Event Log (see \k{using-eventlog}) when trying @@ -211,11 +209,11 @@ Upgrade your server, or use the workarounds described in This error indicates that PuTTY has run out of ways to authenticate you to an SSH server. This may be because PuTTY has TIS or -keyboard-interactive authentication disabled, in which case +keyboard-interactive authentication disabled, in which case see \k{config-ssh-tis} and \k{config-ssh-ki}. -\H{errors-crc} \q{Incorrect \i{CRC} received on packet} or \q{Incorrect -\i{MAC} received on packet} +\H{errors-crc} \q{Incorrect \i{MAC} received on packet} or +\q{Incorrect \i{CRC} received on packet} This error occurs when PuTTY decrypts an SSH packet and its checksum is not correct. This probably means something has gone wrong in the diff --git a/doc/faq.but b/doc/faq.but index 6fc174a..a790c18 100644 --- a/doc/faq.but +++ b/doc/faq.but @@ -45,10 +45,11 @@ implemented. \S{faq-ssh2}{Question} Does PuTTY support SSH-2? -Yes. SSH-2 support has been available in PuTTY since version 0.50. +Yes. SSH-2 support has been available in PuTTY since version 0.50 in +2000. -Public key authentication (both RSA and DSA) in SSH-2 is new in -version 0.52. +Public key authentication (both RSA and DSA) in SSH-2 was new in +version 0.52 in 2002. \S{faq-ssh2-keyfmt}{Question} Does PuTTY support reading OpenSSH or \cw{ssh.com} SSH-2 private key files? @@ -102,7 +103,7 @@ a method of achieving the same effect. \S{faq-fullscreen}{Question} Does PuTTY support full-screen mode, like a DOS box? -Yes; this is a new feature in version 0.52. +Yes; this was added in version 0.52, in 2002. \S{faq-password-remember}{Question} Does PuTTY have the ability to \i{remember my password} so I don't have to type it every time? @@ -194,9 +195,9 @@ available if anyone else wants to try it. Unfortunately not. -Until recently, this was a limitation of the file transfer protocols: -the SCP and SFTP protocols had no notion of transferring a file in -anything other than binary mode. (This is still true of SCP.) +This was a limitation of the file transfer protocols as originally +specified: the SCP and SFTP protocols had no notion of transferring +a file in anything other than binary mode. (This is still true of SCP.) The current draft protocol spec of SFTP proposes a means of implementing ASCII transfer. At some point PSCP/PSFTP may implement @@ -207,12 +208,11 @@ this proposal. The eventual goal is for PuTTY to be a multi-platform program, able to run on at least Windows, Mac OS and Unix. -Porting will become easier once PuTTY has a generalised porting -layer, drawing a clear line between platform-dependent and -platform-independent code. The general intention was for this -porting layer to evolve naturally as part of the process of doing -the first port; a Unix port has now been released and the plan -seems to be working so far. +PuTTY has been gaining a generalised porting layer, drawing a clear +line between platform-dependent and platform-independent code. The +general intention was for this porting layer to evolve naturally as +part of the process of doing the first port; a Unix port has now been +released and the plan seems to be working so far. \S{faq-ports-general}{Question} What ports of PuTTY exist? @@ -222,9 +222,11 @@ systems and Unix. As of 0.68, the supplied PuTTY executables run on versions of Windows from XP onwards, up to and including Windows 10; and we know of no reason why PuTTY should not continue to work on future versions of -Windows. We provide 32-bit and 64-bit Windows executables; see -\k{faq-32bit-64bit} for discussion of the compatibility issues around -that. +Windows. We provide 32-bit and 64-bit Windows executables for the +common x86 processor family; see \k{faq-32bit-64bit} for discussion +of the compatibility issues around that. The 32-bit executables +require a \i{Pentium 4} or newer processor. We also provide +executables for Windows on Arm processors. (We used to also provide executables for Windows for the Alpha processor, but stopped after 0.58 due to lack of interest.) @@ -244,15 +246,21 @@ on the \S{faq-unix}{Question} \I{Unix version}Is there a port to Unix? -As of 0.54, there are Unix ports of most of the traditional PuTTY -tools, and also one entirely new application. +There are Unix ports of most of the traditional PuTTY tools, and also +one entirely new application. If you look at the source release, you should find a \c{unix} subdirectory. There are a couple of ways of building it, including the usual \c{configure}/\c{make}; see the file \c{README} -in the source distribution. This should build you Unix -ports of Plink, PuTTY itself, PuTTYgen, PSCP, PSFTP, Pageant, and also -\i\c{pterm} - an \cw{xterm}-type program which supports the same +in the source distribution. This should build you: + +\b Unix ports of PuTTY, Plink, PSCP, and PSFTP, which work pretty much +the same as their Windows counterparts; + +\b Command-line versions of PuTTYgen and Pageant, whose user interface +is quite different to the Windows GUI versions; + +\b \i\c{pterm} - an \cw{xterm}-type program which supports the same terminal emulation as PuTTY. If you don't have \i{Gtk}, you should still be able to build the @@ -317,7 +325,7 @@ unfinished. If any OS X and/or GTK programming experts are keen to have a finished version of this, we urge them to help out with some of the remaining -problems! +problems! See the TODO list in \c{unix/gtkapp.c} in the source code. \S{faq-epoc}{Question} Will there be a port to EPOC? @@ -423,7 +431,7 @@ You can ask PuTTY to delete all this data; see \k{faq-cleanup}. On Unix, PuTTY stores all of this data in a directory \cw{~/.putty} by default. -\S{faq-trust-sigils} Why do small PuTTY icons appear next to the login +\S{faq-trust-sigils} Why do small \i{PuTTY icon}s appear next to the login prompts? As of PuTTY 0.71, some lines of text in the terminal window are marked @@ -1535,7 +1543,14 @@ a mismatch. Similarly, the development snapshot binaries go with the development snapshot checksums, and so on. (We've colour-coded the download page in an effort to reduce this confusion a bit.) -If you have double-checked that, and you still think there's a real +Another thing to watch out for: as of 0.71, executables like +\c{putty.exe} come in two flavours for each platform: the standalone +versions on the website, each of which contains embedded help, and the +versions installed by the installer, which use a separate help file +also in the installer. We provide checksums for both; the latter are +indicated with \cq{(installer version)} after the filename. + +If you have double-checked all that, and you still think there's a real mismatch, then please send us a report carefully quoting everything relevant: diff --git a/doc/feedback.but b/doc/feedback.but index b8428e4..2d8867e 100644 --- a/doc/feedback.but +++ b/doc/feedback.but @@ -152,11 +152,11 @@ the time you sent the message. \b PuTTY is a multi-platform application; tell us what version of what OS you are running PuTTY on. (If you're running on Unix, or Windows -for Alpha, tell us, or we'll assume you're running on Windows for +for Arm, tell us, or we'll assume you're running on Windows for Intel as this is overwhelmingly the case.) \b Tell us what protocol you are connecting with: SSH, Telnet, -Rlogin or Raw mode. +Rlogin, or Raw mode, or a serial connection. \b Tell us what kind of server you are connecting to; what OS, and if possible what SSH server (if you're using SSH). You can get some diff --git a/doc/gs.but b/doc/gs.but index 56ab282..fb33f3d 100644 --- a/doc/gs.but +++ b/doc/gs.but @@ -113,10 +113,26 @@ changes to this section! After you have connected, and perhaps verified the server's host key, you will be asked to log in, probably using a \i{username} and a \i{password}. Your system administrator should have provided you -with these. Enter the username and the password, and the server -should grant you access and begin your session. If you have -\I{mistyping a password}mistyped your password, most servers will -give you several chances to get it right. +with these. (If, instead, your system administrator has asked you to +provide, or provided you with, a \q{public key} or \q{key file}, see +\k{pubkey}.) + +PuTTY will display a text window (the \q{\i{terminal window}} \dash it +will have a black background unless you've changed the defaults), and +prompt you to type your username and password into that window. (These +prompts will include the \i{PuTTY icon}, to distinguish them from any +text sent by the server in the same window.) + +Enter the username and the password, and the server should grant you +access and begin your session. If you have +\I{mistyping a password}mistyped your password, most servers will give +you several chances to get it right. + +While you are typing your password, you will not usually see the +cursor moving in the window, but PuTTY \e{is} registering what you +type, and will send it when you press Return. (It works this way to +avoid revealing the length of your password to anyone watching your +screen.) If you are using SSH, be careful not to type your username wrongly, because you will not have a chance to correct it after you press diff --git a/doc/index.but b/doc/index.but index debd2ab..cd68d50 100644 --- a/doc/index.but +++ b/doc/index.but @@ -893,3 +893,7 @@ saved sessions from \IM{proxy logging} logging, proxy \IM{proxy logging} diagnostic, proxy \IM{proxy logging} standard error, proxy + +\IM{PuTTY icon} PuTTY icon +\IM{PuTTY icon} icon, PuTTY's +\IM{PuTTY icon} logo, PuTTY's diff --git a/doc/index.html b/doc/index.html new file mode 100644 index 0000000..8c0881e --- /dev/null +++ b/doc/index.html @@ -0,0 +1,198 @@ + + + + +PuTTY User Manual + + + + +

Previous | Contents | Index | Next

+

PuTTY User Manual

+

+PuTTY is a free (MIT-licensed) Windows Telnet and SSH client. This manual documents PuTTY, and its companion utilities PSCP, PSFTP, Plink, Pageant and PuTTYgen. +

+

+Note to Unix users: this manual currently primarily documents the Windows versions of the PuTTY utilities. Some options are therefore mentioned that are absent from the Unix version; the Unix version has features not described here; and the pterm and command-line puttygen and pageant utilities are not described at all. The only Unix-specific documentation that currently exists is the man pages. +

+

+This manual is copyright 1997-2019 Simon Tatham. All rights reserved. You may distribute this documentation under the MIT licence. See appendix C for the licence text in full. +

+ + + +

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

+[PuTTY release 0.72]
+ diff --git a/doc/man-pag.but b/doc/man-pag.but index 098d332..575b729 100644 --- a/doc/man-pag.but +++ b/doc/man-pag.but @@ -20,6 +20,8 @@ \e bbbbbbb bb \c pageant -l \e bbbbbbb bb +\c pageant --askpass prompt +\e bbbbbbb bbbbbbbbb iiiiii \S{pageant-manpage-description} DESCRIPTION @@ -76,8 +78,9 @@ extra command-line arguments, e.g. in which case Pageant will prompt for the keys' passphrases (if any) and start the agent with those keys already loaded. Passphrase prompts will use the controlling terminal if one is available, or failing that -the GUI if one of those is available. If neither is available, no -passphrase prompting can be done. +the GUI if one of those is available. (The prompt method can be +overridden with the \cw{--gui-prompt} or \cw{--tty-prompt} options.) +If neither is available, no passphrase prompting can be done. To use Pageant to talk to an existing agent, you can add new keys using \cw{-a}, list the current set of keys' fingerprints and comments @@ -173,8 +176,8 @@ already have set. \dt \cw{-a} \e{key-files} \dd Load the specified private key file(s), decrypt them if necessary -by prompting for their passphrases, and add them to the -already-running agent. +by prompting for their passphrases (with the same choice of user +interfaces as in agent mode), and add them to the already-running agent. \lcont{ @@ -217,7 +220,7 @@ fingerprint prefix respectively. } -\dt \cw{--public-openssh} \e{key-identifiers} +\dt \cw{--public-openssh} \e{key-identifiers}, \cw{-L} \e{key-identifiers} \dd Print the public half of each specified key, in the one-line format used by OpenSSH, suitable for putting in @@ -234,6 +237,27 @@ using \cw{pageant -a}. \dd Delete all keys from the agent's memory, leaving it completely empty. +\S{pageant-manpage-askpass} SSH-ASKPASS REPLACEMENT + +\dt \cw{--askpass} \e{prompt} + +\dd With this option, \c{pageant} acts as an \e{ssh-askpass(1)} +replacement, rather than performing any SSH agent functionality. This +may be useful if you prefer Pageant's GUI prompt style, which +minimises information leakage about your passphrase length in its +visual feedback, compared to other \e{ssh-askpass(1)} implementations. + +\lcont{ + +\c{pageant --askpass} implements the standard \e{ssh-askpass(1)} +interface: it can be passed a prompt to display (as a single argument) +and, if successful, prints the passphrase on standard output and +returns a zero exit status. Typically you would use the environment +variable \cw{SSH_ASKPASS} to tell other programs to use \c{pageant} in +this way. + +} + \S{pageant-manpage-options} OPTIONS \dt \cw{-v} @@ -268,11 +292,19 @@ respectively. If neither option is given, Pageant will guess based on whether the environment variable \cw{SHELL} has a value ending in \cq{csh}. +\dt \cw{--gui-prompt}, \cw{--tty-prompt} + +\dd Force Pageant to prompt for key passphrases with a particular +method (GUI or terminal) rather than trying to guess the most +appropriate method as described above. (These options are relevant +whenever an encrypted key filename is specified to \c{pageant}, +and in \c{--askpass} mode.) + \dt \cw{--help} \dd Print a brief summary of command-line options and terminate. -\dt \cw{--version} +\dt \cw{--version}, \cw{-V} \dd Print the version of Pageant. diff --git a/doc/man-pg.but b/doc/man-pg.but index fec3724..7e244d1 100644 --- a/doc/man-pg.but +++ b/doc/man-pg.but @@ -83,7 +83,8 @@ on a temporary filesystem or else securely erased after use. \dt \cw{\-\-random\-device} \e{device} -\dd Specify device to read entropy from (default \c{/dev/random}). +\dd Specify device to read entropy from. By default, \c{puttygen} +uses \c{/dev/urandom}, falling back to \c{/dev/random} if it has to. In the second phase, \c{puttygen} optionally alters properties of the key it has loaded or generated. The options to control this are: diff --git a/doc/pageant.1 b/doc/pageant.1 new file mode 100644 index 0000000..9ff31c8 --- /dev/null +++ b/doc/pageant.1 @@ -0,0 +1,146 @@ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.TH "pageant" "1" "2015\(hy05\(hy19" "PuTTY\ tool\ suite" "PuTTY\ tool\ suite" +.SH "NAME" +.PP +\fBpageant\fP - PuTTY SSH authentication agent +.SH "SYNOPSIS" +.PP +.nf +\fBpageant\fP\ (\ \fB\-X\fP\ |\ \fB\-T\fP\ |\ \fB\-\-permanent\fP\ |\ \fB\-\-debug\fP\ )\ [\ \fIkey\-file\fP...\ ] +\fBpageant\fP\ [\ \fIkey\-file\fP...\ ]\ \fB\-\-exec\fP\ \fIcommand\fP\ [\ \fIargs\fP...\ ] +\fBpageant\fP\ \fB\-a\fP\ \fIkey\-file\fP... +\fBpageant\fP\ (\ \fB\-d\fP\ |\ \fB\-\-public\fP\ |\ \fB\-\-public\-openssh\fP\ )\ \fIkey\-identifier\fP... +\fBpageant\fP\ \fB\-D\fP +\fBpageant\fP\ \fB\-l\fP +\fBpageant\fP\ \fB\-\-askpass\fP\ \fIprompt\fP +.fi +.SH "DESCRIPTION" +.PP +\fBpageant\fP is both an SSH authentication agent, and also a tool for communicating with an already-running agent. +.PP +When running as an SSH agent, it listens on a Unix-domain socket for connections from client processes running under your user id. Clients can load SSH private keys into the agent, or request signatures on a given message from a key already in the agent. This permits one-touch authentication by SSH client programs, if Pageant is holding a key that the server they are connecting to will accept. +.PP +\fBpageant\fP can also act as a client program itself, communicating with an already-running agent to add or remove keys, list the keys, or extract their public half. +.PP +The agent protocol used by \fBpageant\fP is compatible with the PuTTY tools and also with other implementations such as OpenSSH\*(Aqs SSH client and \fIssh-agent(1)\fP. +.PP +To run \fBpageant\fP as an agent, you must provide an option to tell it what its \fIlifetime\fP should be. Typically you would probably want Pageant to last for the duration of a login session, in which case you should use either \fB-X\fP or \fB-T\fP, depending on whether your login session is GUI or purely terminal-based respectively. For example, in your X session startup script you might write +.PP +.nf +\fBeval\ $(pageant\ \-X)\fP +.fi +.PP +which will cause Pageant to start running, monitor the X server to notice when your session terminates (and then it will terminate too), and print on standard output some shell commands to set environment variables that client processes will need to find the running agent. +.PP +In a terminal-based login, you could do almost exactly the same thing but with \fB-T\fP: +.PP +.nf +\fBeval\ $(pageant\ \-T)\fP +.fi +.PP +This will cause Pageant to tie its lifetime to that of your controlling terminal: when you log out, and the terminal device ceases to be associated with your session, Pageant will notice that it has no controlling terminal any more, and will terminate automatically. +.PP +In either of these modes, you can also add one or more private keys as extra command-line arguments, e.g. +.PP +.nf +\fBeval\ $(pageant\ \-T\ ~/.ssh/key.ppk)\fP +.fi +.PP +in which case Pageant will prompt for the keys' passphrases (if any) and start the agent with those keys already loaded. Passphrase prompts will use the controlling terminal if one is available, or failing that the GUI if one of those is available. (The prompt method can be overridden with the \fB--gui-prompt\fP or \fB--tty-prompt\fP options.) If neither is available, no passphrase prompting can be done. +.PP +To use Pageant to talk to an existing agent, you can add new keys using \fB-a\fP, list the current set of keys\*(Aq fingerprints and comments with \fB-l\fP, extract the full public half of any key using \fB--public\fP or \fB--public-openssh\fP, delete a key using \fB-d\fP, or delete all keys using \fB-D\fP. +.SH "LIFETIME" +.PP +The following options are called \fIlifetime modes\fP. They all request Pageant to operate in agent mode; each one specifies a different method for Pageant to start up and know when to shut down. +.IP "\fB-X\fP" +Pageant will open a connection to your X display, and when that connection is lost, it will terminate. This gives it the same lifetime as your GUI login session, so in this mode it is suitable for running from a startup script such as \fB.xsession\fP. The actual agent will be a subprocess; the main Pageant process will terminate immediately, after printing environment-variable setting commands on standard output which should be installed in any process wanting to communicate with the agent. +.RS +.PP +The usual approach would be to run +.PP +.nf +\fBeval\ $(pageant\ \-X)\fP +.fi +.PP +in an X session startup script. However, other possibilities exist, such as directing the standard output of `\fBpageant -X\fP' to a file which is then sourced by any new shell. +.RE +.IP "\fB-T\fP" +Pageant will tie its lifetime to that of the login session running on its controlling terminal, by noticing when it ceases to have a controlling terminal (which will automatically happen as a side effect of the session leader process terminating). Like \fB-X\fP, Pageant will print environment-variable commands on standard output. +.IP "\fB--exec\fP \fIcommand\fP" +Pageant will run the provided command as a subprocess, preloaded with the appropriate environment variables to access the agent it starts up. When the subprocess terminates, Pageant will terminate as well. +.RS +.PP +All arguments on Pageant's command line after \fB--exec\fP will be treated as part of the command to run, even if they look like other valid Pageant options or key files. +.RE +.IP "\fB--permanent\fP" +Pageant will fork off a subprocess to be the agent, and print environment-variable commands on standard output, like \fB-X\fP and \fB-T\fP. However, in this case, it will make no effort to limit its lifetime in any way; it will simply run permanently, unless manually killed. The environment variable \fBSSH_AGENT_PID\fP, set by the commands printed by Pageant, permits the agent process to be found for this purpose. +.RS +.PP +This option is not recommended, because any method of manually killing the agent carries the risk of the session terminating unexpectedly before it manages to happen. +.RE +.IP "\fB--debug\fP" +Pageant will run in the foreground, without forking. It will print its environment variable setup commands on standard output, and then it will log all agent activity to standard output as well. This is useful for debugging what Pageant itself is doing, or what another process is doing to it. +.SH "CLIENT OPTIONS" +.PP +The following options tell Pageant to operate in client mode, contacting an existing agent via environment variables that it should already have set. +.IP "\fB-a\fP \fIkey-files\fP" +Load the specified private key file(s), decrypt them if necessary by prompting for their passphrases (with the same choice of user interfaces as in agent mode), and add them to the already-running agent. +.RS +.PP +The private key files must be in PuTTY's \fB.ppk\fP file format. +.RE +.IP "\fB-l\fP" +List the keys currently in the running agent. Each key's fingerprint and comment string will be shown. +.IP "\fB--public\fP \fIkey-identifiers\fP" +Print the public half of each specified key, in the RFC 4716 standard format (multiple lines, starting with `\fB---- BEGIN SSH2 PUBLIC KEY ----\fP'). +.RS +.PP +Each \fIkey-identifier\fP can be any of the following: +.IP "\fB\(bu\fP" +The name of a file containing the key, either the whole key (again in \fB.ppk\fP format) or just its public half. +.IP "\fB\(bu\fP" +The key's comment string, as shown by \fBpageant -l\fP. +.IP "\fB\(bu\fP" +Enough hex digits of the key's fingerprint to be unique among keys currently loaded into the agent. +.PP +If Pageant can uniquely identify one key by interpreting the \fIkey-identifier\fP in any of these ways, it will assume that key was the one you meant. If it cannot, you will have to specify more detail. +.PP +If you find that your desired \fIkey-identifier\fP string can be validly interpreted as more than one of the above \fIkinds\fP of identification, you can disambiguate by prefixing it with `\fBfile:\fP', `\fBcomment:\fP' or `\fBfp:\fP' to indicate that it is a filename, comment string or fingerprint prefix respectively. +.RE +.IP "\fB--public-openssh\fP \fIkey-identifiers\fP, \fB-L\fP \fIkey-identifiers\fP" +Print the public half of each specified key, in the one-line format used by OpenSSH, suitable for putting in \fB.ssh/authorized_keys\fP files. +.IP "\fB-d\fP \fIkey-identifiers\fP" +Delete each specified key from the agent's memory, so that the agent will no longer serve it to clients unless it is loaded in again using \fBpageant -a\fP. +.IP "\fB-D\fP" +Delete all keys from the agent's memory, leaving it completely empty. +.SH "SSH-ASKPASS REPLACEMENT" +.IP "\fB--askpass\fP \fIprompt\fP" +With this option, \fBpageant\fP acts as an \fIssh-askpass(1)\fP replacement, rather than performing any SSH agent functionality. This may be useful if you prefer Pageant\*(Aqs GUI prompt style, which minimises information leakage about your passphrase length in its visual feedback, compared to other \fIssh-askpass(1)\fP implementations. +.RS +.PP +\fBpageant --askpass\fP implements the standard \fIssh-askpass(1)\fP interface: it can be passed a prompt to display (as a single argument) and, if successful, prints the passphrase on standard output and returns a zero exit status. Typically you would use the environment variable \fBSSH_ASKPASS\fP to tell other programs to use \fBpageant\fP in this way. +.RE +.SH "OPTIONS" +.IP "\fB-v\fP" +Verbose mode. When Pageant runs in agent mode, this option causes it to log all agent activity to its standard error. For example, you might run +.RS +.PP +.nf +\fBeval\ $(pageant\ \-X\ \-v\ 2>~/.pageant.log)\fP +.fi +.PP +and expect a list of all signatures requested by agent clients to build up in that log file. +.PP +The log information is the same as that produced by the \fB--debug\fP lifetime option, but \fB--debug\fP sends it to standard output (since that is the main point of debugging mode) whereas \fB-v\fP in all other lifetime modes sends the same log data to standard error (being a by-product of the program\*(Aqs main purpose). Using \fB-v\fP in \fB--debug\fP mode has no effect: the log still goes to standard output. +.RE +.IP "\fB-s\fP, \fB-c\fP" +Force Pageant to output its environment setup commands in the style of POSIX / Bourne shells (\fB-s\fP) or C shells (\fB-c\fP) respectively. If neither option is given, Pageant will guess based on whether the environment variable \fBSHELL\fP has a value ending in `\fBcsh\fP'. +.IP "\fB--gui-prompt\fP, \fB--tty-prompt\fP" +Force Pageant to prompt for key passphrases with a particular method (GUI or terminal) rather than trying to guess the most appropriate method as described above. (These options are relevant whenever an encrypted key filename is specified to \fBpageant\fP, and in \fB--askpass\fP mode.) +.IP "\fB--help\fP" +Print a brief summary of command-line options and terminate. +.IP "\fB--version\fP, \fB-V\fP" +Print the version of Pageant. +.IP "\fB--\fP" +Cause all subsequent arguments to be treated as key file names, even if they look like options. diff --git a/doc/pageant.but b/doc/pageant.but index f25119d..df8a151 100644 --- a/doc/pageant.but +++ b/doc/pageant.but @@ -1,7 +1,5 @@ \C{pageant} Using \i{Pageant} for authentication -\cfg{winhelp-topic}{pageant.general} - Pageant is an SSH \i{authentication agent}. It holds your \i{private key}s in memory, already decoded, so that you can use them often \I{passwordless login}without needing to type a \i{passphrase}. @@ -58,8 +56,6 @@ existing keys. \S{pageant-mainwin-keylist} The key list box -\cfg{winhelp-topic}{pageant.keylist} - The large list box in the Pageant main window lists the private keys that are currently loaded into Pageant. The list might look something like this: @@ -69,12 +65,12 @@ something like this: For each key, the list box will tell you: -\b The type of the key. Currently, this can be \c{ssh1} (an RSA key -for use with the SSH-1 protocol), \c{ssh-rsa} (an RSA key for use -with the SSH-2 protocol), \c{ssh-dss} (a DSA key for use with -the SSH-2 protocol), \c{ecdsa-sha2-*} (an ECDSA key for use with -the SSH-2 protocol), or \c{ssh-ed25519} (an Ed25519 key for use with -the SSH-2 protocol). +\b The type of the key. Currently, this can be +\c{ssh-rsa} (an RSA key for use with the SSH-2 protocol), +\c{ssh-dss} (a DSA key for use with the SSH-2 protocol), +\c{ecdsa-sha2-*} (an ECDSA key for use with the SSH-2 protocol), +\c{ssh-ed25519} (an Ed25519 key for use with the SSH-2 protocol), +or \c{ssh1} (an RSA key for use with the old SSH-1 protocol). \b The size (in bits) of the key. @@ -87,8 +83,6 @@ applied to your \c{authorized_keys} file. \S{pageant-mainwin-addkey} The \q{Add Key} button -\cfg{winhelp-topic}{pageant.addkey} - To add a key to Pageant by reading it out of a local disk file, press the \q{Add Key} button in the Pageant main window, or alternatively right-click on the Pageant icon in the system tray and @@ -109,8 +103,6 @@ also add one from a remote system by using agent forwarding; see \S{pageant-mainwin-remkey} The \q{Remove Key} button -\cfg{winhelp-topic}{pageant.remkey} - If you need to remove a key from Pageant, select that key in the list box, and press the \q{Remove Key} button. Pageant will remove the key from its memory. @@ -159,14 +151,26 @@ by the command, like this: \c C:\PuTTY\pageant.exe d:\main.ppk -c C:\PuTTY\putty.exe +\S{pageant-cmdline-restrict-acl} Restricting the \i{Windows process ACL} + +Pageant supports the same \i\c{-restrict-acl} option as the other +PuTTY utilities to lock down the Pageant process's access control; +see \k{using-cmdline-restrict-acl} for why you might want to do this. + +By default, if Pageant is started with \c{-restrict-acl}, it won't +pass this to any PuTTY sessions started from its System Tray submenu. +Use \c{-restrict-putty-acl} to change this. (Again, see +\k{using-cmdline-restrict-acl} for details.) + \H{pageant-forward} Using \i{agent forwarding} Agent forwarding is a mechanism that allows applications on your SSH server machine to talk to the agent on your client machine. -Note that at present, agent forwarding in SSH-2 is only available -when your SSH server is \i{OpenSSH}. The \i\cw{ssh.com} server uses a -different agent protocol, which PuTTY does not yet support. +Note that at present, whether agent forwarding in SSH-2 is available +depends on your server. Pageant's protocol is compatible with the +\i{OpenSSH} server, but the \i\cw{ssh.com} server uses a different +agent protocol, which PuTTY does not yet support. To enable agent forwarding, first start Pageant. Then set up a PuTTY SSH session in which \q{Allow agent forwarding} is enabled (see diff --git a/doc/pgpkeys.but b/doc/pgpkeys.but index 2206849..8fab615 100644 --- a/doc/pgpkeys.but +++ b/doc/pgpkeys.but @@ -1,7 +1,5 @@ \A{pgpkeys} PuTTY download keys and signatures -\cfg{winhelp-topic}{pgpfingerprints} - \I{verifying new versions}We create \i{GPG signatures} for all the PuTTY files distributed from our web site, so that users can be confident that the files have not been tampered with. Here we identify diff --git a/doc/plink.1 b/doc/plink.1 new file mode 100644 index 0000000..37a84b2 --- /dev/null +++ b/doc/plink.1 @@ -0,0 +1,151 @@ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.TH "plink" "1" "2004\(hy03\(hy24" "PuTTY\ tool\ suite" "PuTTY\ tool\ suite" +.SH "NAME" +.PP +\fBplink\fP \- PuTTY link, command line network connection tool +.SH "SYNOPSIS" +.PP +.nf +\fBplink\fP\ [\fIoptions\fP]\ [\fIuser\fP\fB@\fP]\fIhost\fP\ [\fIcommand\fP] +.fi +.SH "DESCRIPTION" +.PP +\fBplink\fP is a network connection tool supporting several protocols. +.SH "OPTIONS" +.PP +The command-line options supported by \fBplink\fP are: +.IP "\fB-V\fP" +Show version information and exit. +.IP "\fB-pgpfp\fP" +Display the fingerprints of the PuTTY PGP Master Keys and exit, to aid in verifying new files released by the PuTTY team. +.IP "\fB-v\fP" +Show verbose messages. +.IP "\fB-load\fP \fIsession\fP" +Load settings from saved session. +.IP "\fB-ssh\fP" +Force use of SSH protocol (default). +.IP "\fB-telnet\fP" +Force use of Telnet protocol. +.IP "\fB-rlogin\fP" +Force use of rlogin protocol. +.IP "\fB-raw\fP" +Force raw mode. +.IP "\fB-serial\fP" +Force serial mode. +.IP "\fB\-proxycmd\fP \fIcommand\fP" +Instead of making a TCP connection, use \fIcommand\fP as a proxy; network traffic will be redirected to the standard input and output of \fIcommand\fP. \fIcommand\fP must be a single word, so is likely to need quoting by the shell. +.RS +.PP +The special strings \fB%host\fP and \fB%port\fP in \fIcommand\fP will be replaced by the hostname and port number you want to connect to; to get a literal \fB%\fP sign, enter \fB%%\fP. +.PP +Backslash escapes are also supported, such as sequences like \fB\en\fP being replaced by a literal newline; to get a literal backslash, enter \fB\e\e\fP. (Further escaping may be required by the shell.) +.PP +(See the main PuTTY manual for full details of the supported \fB%\fP- and backslash-delimited tokens, although most of them are probably not very useful in this context.) +.RE +.IP "\fB-P\fP \fIport\fP" +Connect to port \fIport\fP. +.IP "\fB-l\fP \fIuser\fP" +Set remote username to \fIuser\fP. +.IP "\fB-m\fP \fIpath\fP" +Read remote command(s) from local file \fIpath\fP. +.IP "\fB-batch\fP" +Disable interactive prompts. +.IP "\fB-sanitise-stderr\fP" + +.IP "\fB-sanitise-stdout\fP" + +.IP "\fB-no-sanitise-stderr\fP" + +.IP "\fB-no-sanitise-stdout\fP" +By default, Plink can choose to filter control characters if that seems appropriate, to prevent remote processes sending confusing escape sequences. These options override Plink's default behaviour to enable or disabling such filtering on the standard error and standard output channels. +.IP "\fB-pw\fP \fIpassword\fP" +Set remote password to \fIpassword\fP. \fICAUTION:\fP this will likely make the password visible to other users of the local machine (via commands such as `\fBw\fP'). +.IP "\fB\-L\fP \fB[\fP\fIsrcaddr\fP\fB:]\fP\fIsrcport\fP\fB:\fP\fIdesthost\fP\fB:\fP\fIdestport\fP" +Set up a local port forwarding: listen on \fIsrcport\fP (or \fIsrcaddr\fP:\fIsrcport\fP if specified), and forward any connections over the SSH connection to the destination address \fIdesthost\fP:\fIdestport\fP. Only works in SSH. +.IP "\fB\-R\fP \fB[\fP\fIsrcaddr\fP\fB:]\fP\fIsrcport\fP\fB:\fP\fIdesthost\fP\fB:\fP\fIdestport\fP" +Set up a remote port forwarding: ask the SSH server to listen on \fIsrcport\fP (or \fIsrcaddr\fP:\fIsrcport\fP if specified), and to forward any connections back over the SSH connection where the client will pass them on to the destination address \fIdesthost\fP:\fIdestport\fP. Only works in SSH. +.IP "\fB\-D\fP [\fIsrcaddr\fP:]\fIsrcport\fP" +Set up dynamic port forwarding. The client listens on \fIsrcport\fP (or \fIsrcaddr\fP:\fIsrcport\fP if specified), and implements a SOCKS server. So you can point SOCKS-aware applications at this port and they will automatically use the SSH connection to tunnel all their connections. Only works in SSH. +.IP "\fB-X\fP" +Enable X11 forwarding. +.IP "\fB-x\fP" +Disable X11 forwarding (default). +.IP "\fB-A\fP" +Enable agent forwarding. +.IP "\fB-a\fP" +Disable agent forwarding (default). +.IP "\fB-t\fP" +Enable pty allocation (default if a command is NOT specified). +.IP "\fB-T\fP" +Disable pty allocation (default if a command is specified). +.IP "\fB-1\fP" +Force use of SSH protocol version 1. +.IP "\fB-2\fP" +Force use of SSH protocol version 2. +.IP "\fB-4\fP, \fB-6\fP" +Force use of IPv4 or IPv6 for network connections. +.IP "\fB-C\fP" +Enable SSH compression. +.IP "\fB-i\fP \fIkeyfile\fP" +Private key file for user authentication. For SSH-2 keys, this key file must be in PuTTY's PPK format, not OpenSSH's format or anyone else's. +.RS +.PP +If you are using an authentication agent, you can also specify a \fIpublic\fP key here (in RFC 4716 or OpenSSH format), to identify which of the agent's keys to use. +.RE +.IP "\fB\-noagent\fP" +Don't try to use an authentication agent for local authentication. (This doesn't affect agent forwarding.) +.IP "\fB\-agent\fP" +Allow use of an authentication agent. (This option is only necessary to override a setting in a saved session.) +.IP "\fB\-noshare\fP" +Don't test and try to share an existing connection, always make a new connection. +.IP "\fB\-share\fP" +Test and try to share an existing connection. +.IP "\fB\-hostkey\fP \fIkey\fP" +Specify an acceptable host public key. This option may be specified multiple times; each key can be either a fingerprint (\fB99:aa:bb:...\fP) or a base64-encoded blob in OpenSSH\*(Aqs one-line format. +.RS +.PP +Specifying this option overrides automated host key management; \fIonly\fP the key(s) specified on the command-line will be accepted (unless a saved session also overrides host keys, in which case those will be added to), and the host key cache will not be written. +.RE +.IP "\fB-s\fP" +Remote command is SSH subsystem (SSH-2 only). +.IP "\fB-N\fP" +Don't start a remote command or shell at all (SSH-2 only). +.IP "\fB\-nc\fP \fIhost\fP:\fIport\fP" +Make a remote network connection from the server instead of starting a shell or command. +.IP "\fB\-sercfg\fP \fIconfiguration-string\fP" +Specify the configuration parameters for the serial port, in \fB-serial\fP mode. \fIconfiguration-string\fP should be a comma-separated list of configuration parameters as follows: +.RS +.IP "\fB\(bu\fP" +Any single digit from 5 to 9 sets the number of data bits. +.IP "\fB\(bu\fP" +`\fB1\fP', `\fB1.5\fP' or `\fB2\fP' sets the number of stop bits. +.IP "\fB\(bu\fP" +Any other numeric string is interpreted as a baud rate. +.IP "\fB\(bu\fP" +A single lower-case letter specifies the parity: `\fBn\fP' for none, `\fBo\fP' for odd, `\fBe\fP' for even, `\fBm\fP' for mark and `\fBs\fP' for space. +.IP "\fB\(bu\fP" +A single upper-case letter specifies the flow control: `\fBN\fP' for none, `\fBX\fP' for XON/XOFF, `\fBR\fP' for RTS/CTS and `\fBD\fP' for DSR/DTR. +.RE +.IP "\fB\-sshlog\fP \fIlogfile\fP" + +.IP "\fB\-sshrawlog\fP \fIlogfile\fP" +For SSH connections, these options make \fBplink\fP log protocol details to a file. (Some of these may be sensitive, although by default an effort is made to suppress obvious passwords.) +.RS +.PP +\fB\-sshlog\fP logs decoded SSH packets and other events (those that \fB\-v\fP would print). \fB\-sshrawlog\fP additionally logs the raw encrypted packet data. +.RE +.IP "\fB\-shareexists\fP" +Instead of making a new connection, test for the presence of an existing connection that can be shared. The desired session can be specified in any of the usual ways. +.RS +.PP +Returns immediately with a zero exit status if a suitable `upstream' exists, nonzero otherwise. +.RE +.SH "MORE INFORMATION" +.PP +For more information on plink, it's probably best to go and look at the manual on the PuTTY web page: +.PP +\fBhttps://www.chiark.greenend.org.uk/~sgtatham/putty/\fP +.SH "BUGS" +.PP +This man page isn't terribly complete. See the above web link for better documentation. diff --git a/doc/plink.but b/doc/plink.but index f9af18d..d83495f 100644 --- a/doc/plink.but +++ b/doc/plink.but @@ -41,7 +41,7 @@ use Plink: \c Z:\sysosd>plink \c Plink: command-line connection utility -\c Release 0.71 +\c Release 0.72 \c Usage: plink [options] [user@]host [command] \c ("host" can also be a PuTTY saved session name) \c Options: diff --git a/doc/pscp.1 b/doc/pscp.1 new file mode 100644 index 0000000..fa78453 --- /dev/null +++ b/doc/pscp.1 @@ -0,0 +1,101 @@ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.TH "pscp" "1" "2004\(hy03\(hy24" "PuTTY\ tool\ suite" "PuTTY\ tool\ suite" +.SH "NAME" +.PP +\fBpscp\fP \- command-line SCP (secure copy) / SFTP client +.SH "SYNOPSIS" +.PP +.nf +\fBpscp\fP\ [\fIoptions\fP]\ [\fIuser\fP\fB@\fP]\fIhost\fP\fB:\fP\fIsource\fP\ \fItarget\fP +\fBpscp\fP\ [\fIoptions\fP]\ \fIsource\fP\ [\fIsource\fP...]\ [\fIuser\fP\fB@\fP]\fIhost\fP\fB:\fP\fItarget\fP +\fBpscp\fP\ [\fIoptions\fP]\ \fB\-ls\fP\ [\fIuser\fP\fB@\fP]\fIhost\fP\fB:\fP\fIfilespec\fP +.fi +.SH "DESCRIPTION" +.PP +\fBpscp\fP is a command-line client for the SSH-based SCP (secure copy) and SFTP (secure file transfer protocol) protocols. +.SH "OPTIONS" +.PP +The command-line options supported by \fIpscp\fP are: +.IP "\fB-V\fP" +Show version information and exit. +.IP "\fB-pgpfp\fP" +Display the fingerprints of the PuTTY PGP Master Keys and exit, to aid in verifying new files released by the PuTTY team. +.IP "\fB-ls\fP" +Remote directory listing. +.IP "\fB-p\fP" +Preserve file attributes. +.IP "\fB-q\fP" +Quiet, don't show statistics. +.IP "\fB-r\fP" +Copy directories recursively. +.IP "\fB-unsafe\fP" +Allow server-side wildcards (DANGEROUS). +.IP "\fB-v\fP" +Show verbose messages. +.IP "\fB-load\fP \fIsession\fP" +Load settings from saved session. +.IP "\fB-P\fP \fIport\fP" +Connect to port \fIport\fP. +.IP "\fB\-proxycmd\fP \fIcommand\fP" +Instead of making a TCP connection, use \fIcommand\fP as a proxy; network traffic will be redirected to the standard input and output of \fIcommand\fP. \fIcommand\fP must be a single word, so is likely to need quoting by the shell. +.RS +.PP +The special strings \fB%host\fP and \fB%port\fP in \fIcommand\fP will be replaced by the hostname and port number you want to connect to; to get a literal \fB%\fP sign, enter \fB%%\fP. +.PP +Backslash escapes are also supported, such as sequences like \fB\en\fP being replaced by a literal newline; to get a literal backslash, enter \fB\e\e\fP. (Further escaping may be required by the shell.) +.PP +(See the main PuTTY manual for full details of the supported \fB%\fP- and backslash-delimited tokens, although most of them are probably not very useful in this context.) +.RE +.IP "\fB-l\fP \fIuser\fP" +Set remote username to \fIuser\fP. +.IP "\fB-batch\fP" +Disable interactive prompts. +.IP "\fB-no-sanitise-stderr\fP" +By default, PSCP will filter control characters from the standard error channel from the server, to prevent remote processes sending confusing escape sequences. This option forces the standard error channel to not be filtered. +.IP "\fB-pw\fP \fIpassword\fP" +Set remote password to \fIpassword\fP. \fICAUTION:\fP this will likely make the password visible to other users of the local machine (via commands such as `\fBw\fP'). +.IP "\fB-1\fP" +Force use of SSH protocol version 1. +.IP "\fB-2\fP" +Force use of SSH protocol version 2. +.IP "\fB-4\fP, \fB-6\fP" +Force use of IPv4 or IPv6 for network connections. +.IP "\fB-C\fP" +Enable SSH compression. +.IP "\fB-i\fP \fIkeyfile\fP" +Private key file for user authentication. For SSH-2 keys, this key file must be in PuTTY's PPK format, not OpenSSH's format or anyone else's. +.RS +.PP +If you are using an authentication agent, you can also specify a \fIpublic\fP key here (in RFC 4716 or OpenSSH format), to identify which of the agent's keys to use. +.RE +.IP "\fB\-noagent\fP" +Don't try to use an authentication agent. +.IP "\fB\-agent\fP" +Allow use of an authentication agent. (This option is only necessary to override a setting in a saved session.) +.IP "\fB\-hostkey\fP \fIkey\fP" +Specify an acceptable host public key. This option may be specified multiple times; each key can be either a fingerprint (\fB99:aa:bb:...\fP) or a base64-encoded blob in OpenSSH\*(Aqs one-line format. +.RS +.PP +Specifying this option overrides automated host key management; \fIonly\fP the key(s) specified on the command-line will be accepted (unless a saved session also overrides host keys, in which case those will be added to), and the host key cache will not be written. +.RE +.IP "\fB-scp\fP" +Force use of SCP protocol. +.IP "\fB-sftp\fP" +Force use of SFTP protocol. +.IP "\fB\-sshlog\fP \fIlogfile\fP" + +.IP "\fB\-sshrawlog\fP \fIlogfile\fP" +These options make \fBpscp\fP log protocol details to a file. (Some of these may be sensitive, although by default an effort is made to suppress obvious passwords.) +.RS +.PP +\fB\-sshlog\fP logs decoded SSH packets and other events (those that \fB\-v\fP would print). \fB\-sshrawlog\fP additionally logs the raw encrypted packet data. +.RE +.SH "MORE INFORMATION" +.PP +For more information on \fBpscp\fP it\*(Aqs probably best to go and look at the manual on the PuTTY web page: +.PP +\fBhttps://www.chiark.greenend.org.uk/~sgtatham/putty/\fP +.SH "BUGS" +.PP +This man page isn't terribly complete. See the above web link for better documentation. diff --git a/doc/pscp.but b/doc/pscp.but index 0ab4b73..dbd2a99 100644 --- a/doc/pscp.but +++ b/doc/pscp.but @@ -39,7 +39,7 @@ use PSCP: \c Z:\owendadmin>pscp \c PuTTY Secure Copy client -\c Release 0.71 +\c Release 0.72 \c Usage: pscp [options] [user@]host:source target \c pscp [options] source [source...] [user@]host:target \c pscp [options] -ls [user@]host:filespec diff --git a/doc/psftp.1 b/doc/psftp.1 new file mode 100644 index 0000000..2bbb764 --- /dev/null +++ b/doc/psftp.1 @@ -0,0 +1,94 @@ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.TH "psftp" "1" "2004\(hy03\(hy24" "PuTTY\ tool\ suite" "PuTTY\ tool\ suite" +.SH "NAME" +.PP +\fBpsftp\fP \- interactive SFTP (secure file transfer protocol) client +.SH "SYNOPSIS" +.PP +.nf +\fBpsftp\fP\ [\fIoptions\fP]\ [\fIuser\fP\fB@\fP]\fIhost\fP +.fi +.SH "DESCRIPTION" +.PP +\fBpsftp\fP is an interactive text-based client for the SSH-based SFTP (secure file transfer) protocol. +.SH "OPTIONS" +.PP +The command-line options supported by \fBpsftp\fP are: +.IP "\fB-V\fP" +Show version information and exit. +.IP "\fB-pgpfp\fP" +Display the fingerprints of the PuTTY PGP Master Keys and exit, to aid in verifying new files released by the PuTTY team. +.IP "\fB-b\fP \fIbatchfile\fP" +Use specified batchfile. +.IP "\fB-bc\fP" +Output batchfile commands. +.IP "\fB-be\fP" +Don't stop batchfile processing on errors. +.IP "\fB-v\fP" +Show verbose messages. +.IP "\fB-load\fP \fIsession\fP" +Load settings from saved session. +.IP "\fB-P\fP \fIport\fP" +Connect to port \fIport\fP. +.IP "\fB\-proxycmd\fP \fIcommand\fP" +Instead of making a TCP connection, use \fIcommand\fP as a proxy; network traffic will be redirected to the standard input and output of \fIcommand\fP. \fIcommand\fP must be a single word, so is likely to need quoting by the shell. +.RS +.PP +The special strings \fB%host\fP and \fB%port\fP in \fIcommand\fP will be replaced by the hostname and port number you want to connect to; to get a literal \fB%\fP sign, enter \fB%%\fP. +.PP +Backslash escapes are also supported, such as sequences like \fB\en\fP being replaced by a literal newline; to get a literal backslash, enter \fB\e\e\fP. (Further escaping may be required by the shell.) +.PP +(See the main PuTTY manual for full details of the supported \fB%\fP- and backslash-delimited tokens, although most of them are probably not very useful in this context.) +.RE +.IP "\fB-l\fP \fIuser\fP" +Set remote username to \fIuser\fP. +.IP "\fB-batch\fP" +Disable interactive prompts. +.IP "\fB-no-sanitise-stderr\fP" +By default, PSFTP will filter control characters from the standard error channel from the server, to prevent remote processes sending confusing escape sequences. This option forces the standard error channel to not be filtered. +.IP "\fB-pw\fP \fIpassword\fP" +Set remote password to \fIpassword\fP. \fICAUTION:\fP this will likely make the password visible to other users of the local machine (via commands such as `\fBw\fP'). +.IP "\fB-1\fP" +Force use of SSH protocol version 1. +.IP "\fB-2\fP" +Force use of SSH protocol version 2. +.IP "\fB-4\fP, \fB-6\fP" +Force use of IPv4 or IPv6 for network connections. +.IP "\fB-C\fP" +Enable SSH compression. +.IP "\fB-i\fP \fIkeyfile\fP" +Private key file for user authentication. For SSH-2 keys, this key file must be in PuTTY's PPK format, not OpenSSH's format or anyone else's. +.RS +.PP +If you are using an authentication agent, you can also specify a \fIpublic\fP key here (in RFC 4716 or OpenSSH format), to identify which of the agent's keys to use. +.RE +.IP "\fB\-noagent\fP" +Don't try to use an authentication agent. +.IP "\fB\-agent\fP" +Allow use of an authentication agent. (This option is only necessary to override a setting in a saved session.) +.IP "\fB\-hostkey\fP \fIkey\fP" +Specify an acceptable host public key. This option may be specified multiple times; each key can be either a fingerprint (\fB99:aa:bb:...\fP) or a base64-encoded blob in OpenSSH\*(Aqs one-line format. +.RS +.PP +Specifying this option overrides automated host key management; \fIonly\fP the key(s) specified on the command-line will be accepted (unless a saved session also overrides host keys, in which case those will be added to), and the host key cache will not be written. +.RE +.IP "\fB\-sshlog\fP \fIlogfile\fP" + +.IP "\fB\-sshrawlog\fP \fIlogfile\fP" +These options make \fBpsftp\fP log protocol details to a file. (Some of these may be sensitive, although by default an effort is made to suppress obvious passwords.) +.RS +.PP +\fB\-sshlog\fP logs decoded SSH packets and other events (those that \fB\-v\fP would print). \fB\-sshrawlog\fP additionally logs the raw encrypted packet data. +.RE +.SH "COMMANDS" +.PP +For a list of commands available inside \fBpsftp\fP, type \fBhelp\fP at the \fBpsftp>\fP prompt. +.SH "MORE INFORMATION" +.PP +For more information on \fBpsftp\fP it\*(Aqs probably best to go and look at the manual on the PuTTY web page: +.PP +\fBhttps://www.chiark.greenend.org.uk/~sgtatham/putty/\fP +.SH "BUGS" +.PP +This man page isn't terribly complete. See the above web link for better documentation. diff --git a/doc/pterm.1 b/doc/pterm.1 new file mode 100644 index 0000000..b9c65c0 --- /dev/null +++ b/doc/pterm.1 @@ -0,0 +1,250 @@ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.TH "pterm" "1" "2004\(hy03\(hy24" "PuTTY\ tool\ suite" "PuTTY\ tool\ suite" +.SH "NAME" +.PP +pterm \(hy yet another X terminal emulator +.SH "SYNOPSIS" +.PP +.nf +\fBpterm\fP\ [\ \fIoptions\fP\ ] +.fi +.SH "DESCRIPTION" +.PP +\fBpterm\fP is a terminal emulator for X. It is based on a port of the terminal emulation engine in the Windows SSH client PuTTY. +.SH "OPTIONS" +.PP +The command-line options supported by \fBpterm\fP are: +.IP "\fB\-e\fP \fIcommand\fP [ \fIarguments\fP ]" +Specify a command to be executed in the new terminal. Everything on the command line after this option will be passed straight to the \fBexecvp\fP system call; so if you need the command to redirect its input or output, you will have to use \fBsh\fP: +.RS +.PP +.nf +pterm\ \-e\ sh\ \-c\ \*(Aqmycommand\ <\ inputfile\*(Aq +.fi +.RE +.IP "\fB\-\-display\fP \fIdisplay\-name\fP" +Specify the X display on which to open \fBpterm\fP. (Note this option has a double minus sign, even though none of the others do. This is because this option is supplied automatically by GTK. Sorry.) +.IP "\fB\-name\fP \fIname\fP" +Specify the name under which \fBpterm\fP looks up X resources. Normally it will look them up as (for example) \fBpterm.Font\fP. If you specify `\fB\-name xyz\fP', it will look them up as \fBxyz.Font\fP instead. This allows you to set up several different sets of defaults and choose between them. +.IP "\fB\-fn\fP \fIfont-name\fP" +Specify the font to use for normal text displayed in the terminal. For example, \fB\-fn\ fixed\fP, \fB\-fn\ "Monospace\ 12"\fP. +.IP "\fB\-fb\fP \fIfont-name\fP" +Specify the font to use for bold text displayed in the terminal. If the \fBBoldAsColour\fP resource is set to 1 (the default), bold text will be displayed in different colours instead of a different font, so this option will be ignored. If \fBBoldAsColour\fP is set to 0 or 2 and you do not specify a bold font, \fBpterm\fP will overprint the normal font to make it look bolder. +.IP "\fB\-fw\fP \fIfont-name\fP" +Specify the font to use for double-width characters (typically Chinese, Japanese and Korean text) displayed in the terminal. +.IP "\fB\-fwb\fP \fIfont-name\fP" +Specify the font to use for bold double-width characters (typically Chinese, Japanese and Korean text). Like \fB-fb\fP, this will be ignored unless the \fBBoldAsColour\fP resource is set to 0 or 2. +.IP "\fB\-geometry\fP \fIgeometry\fP" +Specify the size of the terminal, in rows and columns of text. See \fIX(7)\fP for more information on the syntax of geometry specifications. +.IP "\fB\-sl\fP \fIlines\fP" +Specify the number of lines of scrollback to save off the top of the terminal. +.IP "\fB\-fg\fP \fIcolour\fP" +Specify the foreground colour to use for normal text. +.IP "\fB\-bg\fP \fIcolour\fP" +Specify the background colour to use for normal text. +.IP "\fB\-bfg\fP \fIcolour\fP" +Specify the foreground colour to use for bold text, if the \fBBoldAsColour\fP resource is set to 1 (the default) or 2. +.IP "\fB\-bbg\fP \fIcolour\fP" +Specify the foreground colour to use for bold reverse-video text, if the \fBBoldAsColour\fP resource is set to 1 (the default) or 2. (This colour is best thought of as the bold version of the background colour; so it only appears when text is displayed \fIin\fP the background colour.) +.IP "\fB\-cfg\fP \fIcolour\fP" +Specify the foreground colour to use for text covered by the cursor. +.IP "\fB\-cbg\fP \fIcolour\fP" +Specify the background colour to use for text covered by the cursor. In other words, this is the main colour of the cursor. +.IP "\fB\-title\fP \fItitle\fP" +Specify the initial title of the terminal window. (This can be changed under control of the server.) +.IP "\fB\-ut\-\fP or \fB+ut\fP" +Tells \fBpterm\fP not to record your login in the \fButmp\fP, \fBwtmp\fP and \fBlastlog\fP system log files; so you will not show up on \fBfinger\fP or \fBwho\fP listings, for example. +.IP "\fB\-ut\fP" +Tells \fBpterm\fP to record your login in \fButmp\fP, \fBwtmp\fP and \fBlastlog\fP: this is the opposite of \fB\-ut\-\fP. This is the default option: you will probably only need to specify it explicitly if you have changed the default using the \fBStampUtmp\fP resource. +.IP "\fB\-ls\-\fP or \fB+ls\fP" +Tells \fBpterm\fP not to execute your shell as a login shell. +.IP "\fB\-ls\fP" +Tells \fBpterm\fP to execute your shell as a login shell: this is the opposite of \fB\-ls\-\fP. This is the default option: you will probably only need to specify it explicitly if you have changed the default using the \fBLoginShell\fP resource. +.IP "\fB\-sb\-\fP or \fB+sb\fP" +Tells \fBpterm\fP not to display a scroll bar. +.IP "\fB\-sb\fP" +Tells \fBpterm\fP to display a scroll bar: this is the opposite of \fB\-sb\-\fP. This is the default option: you will probably only need to specify it explicitly if you have changed the default using the \fBScrollBar\fP resource. +.IP "\fB\-log\fP \fIlogfile\fP, \fB\-sessionlog\fP \fIlogfile\fP" +This option makes \fBpterm\fP log all the terminal output to a file as well as displaying it in the terminal. +.IP "\fB\-cs\fP \fIcharset\fP" +This option specifies the character set in which \fBpterm\fP should assume the session is operating. This character set will be used to interpret all the data received from the session, and all input you type or paste into \fBpterm\fP will be converted into this character set before being sent to the session. +.RS +.PP +Any character set name which is valid in a MIME header (and supported by \fBpterm\fP) should be valid here (examples are `\fBISO-8859-1\fP', `\fBwindows-1252\fP' or `\fBUTF-8\fP'). Also, any character encoding which is valid in an X logical font description should be valid (`\fBibm-cp437\fP', for example). +.PP +\fBpterm\fP\*(Aqs default behaviour is to use the same character encoding as its primary font. If you supply a Unicode (\fBiso10646-1\fP) font, it will default to the UTF-8 character set. +.PP +Character set names are case-insensitive. +.RE +.IP "\fB\-nethack\fP" +Tells \fBpterm\fP to enable NetHack keypad mode, in which the numeric keypad generates the NetHack \fBhjklyubn\fP direction keys. This enables you to play NetHack with the numeric keypad without having to use the NetHack \fBnumber_pad\fP option (which requires you to press `\fBn\fP' before any repeat count). So you can move with the numeric keypad, and enter repeat counts with the normal number keys. +.IP "\fB\-xrm\fP \fIresource-string\fP" +This option specifies an X resource string. Useful for setting resources which do not have their own command-line options. For example: +.RS +.PP +.nf +pterm\ \-xrm\ \*(AqScrollbarOnLeft:\ 1\*(Aq +.fi +.RE +.IP "\fB\-help\fP, \fB\-\-help\fP" +Display a message summarizing the available options. +.IP "\fB\-pgpfp\fP" +Display the fingerprints of the PuTTY PGP Master Keys, to aid in verifying new files released by the PuTTY team. +.SH "X RESOURCES" +.PP +\fBpterm\fP can be more completely configured by means of X resources. All of these resources are of the form \fBpterm.FOO\fP for some \fBFOO\fP; you can make \fBpterm\fP look them up under another name, such as \fBxyz.FOO\fP, by specifying the command-line option `\fB\-name xyz\fP'. +.IP "\fBpterm.CloseOnExit\fP" +This option should be set to 0, 1 or 2; the default is 2. It controls what \fBpterm\fP does when the process running inside it terminates. When set to 2 (the default), \fBpterm\fP will close its window as soon as the process inside it terminates. When set to 0, \fBpterm\fP will print the process\*(Aqs exit status, and the window will remain present until a key is pressed (allowing you to inspect the scrollback, and copy and paste text out of it). +.RS +.PP +When this setting is set to 1, \fBpterm\fP will close immediately if the process exits cleanly (with an exit status of zero), but the window will stay around if the process exits with a non-zero code or on a signal. This enables you to see what went wrong if the process suffers an error, but not to have to bother closing the window in normal circumstances. +.RE +.IP "\fBpterm.WarnOnClose\fP" +This option should be set to either 0 or 1; the default is 1. When set to 1, \fBpterm\fP will ask for confirmation before closing its window when you press the close button. +.IP "\fBpterm.TerminalType\fP" +This controls the value set in the \fBTERM\fP environment variable inside the new terminal. The default is `\fBxterm\fP'. +.IP "\fBpterm.BackspaceIsDelete\fP" +This option should be set to either 0 or 1; the default is 1. When set to 0, the ordinary Backspace key generates the Backspace character (\fB^H\fP); when set to 1, it generates the Delete character (\fB^?\fP). Whichever one you set, the terminal device inside \fBpterm\fP will be set up to expect it. +.IP "\fBpterm.RXVTHomeEnd\fP" +This option should be set to either 0 or 1; the default is 0. When it is set to 1, the Home and End keys generate the control sequences they would generate in the \fBrxvt\fP terminal emulator, instead of the more usual ones generated by other emulators. +.IP "\fBpterm.LinuxFunctionKeys\fP" +This option can be set to any number between 0 and 5 inclusive; the default is 0. The modes vary the control sequences sent by the function keys; for more complete documentation, it is probably simplest to try each option in `\fBpterm \-e cat\fP', and press the keys to see what they generate. +.IP "\fBpterm.NoApplicationKeys\fP" +This option should be set to either 0 or 1; the default is 0. When set to 1, it stops the server from ever switching the numeric keypad into application mode (where the keys send function-key-like sequences instead of numbers or arrow keys). You probably only need this if some application is making a nuisance of itself. +.IP "\fBpterm.NoApplicationCursors\fP" +This option should be set to either 0 or 1; the default is 0. When set to 1, it stops the server from ever switching the cursor keys into application mode (where the keys send slightly different sequences). You probably only need this if some application is making a nuisance of itself. +.IP "\fBpterm.NoMouseReporting\fP" +This option should be set to either 0 or 1; the default is 0. When set to 1, it stops the server from ever enabling mouse reporting mode (where mouse clicks are sent to the application instead of controlling cut and paste). +.IP "\fBpterm.NoRemoteResize\fP" +This option should be set to either 0 or 1; the default is 0. When set to 1, it stops the server from being able to remotely control the size of the \fBpterm\fP window. +.IP "\fBpterm.NoAltScreen\fP" +This option should be set to either 0 or 1; the default is 0. When set to 1, it stops the server from using the `alternate screen' terminal feature, which lets full-screen applications leave the screen exactly the way they found it. +.IP "\fBpterm.NoRemoteWinTitle\fP" +This option should be set to either 0 or 1; the default is 0. When set to 1, it stops the server from remotely controlling the title of the \fBpterm\fP window. +.IP "\fBpterm.NoRemoteQTitle\fP" +This option should be set to either 0 or 1; the default is 1. When set to 1, it stops the server from remotely requesting the title of the \fBpterm\fP window. +.RS +.PP +This feature is a \fIPOTENTIAL SECURITY HAZARD\fP. If a malicious application can write data to your terminal (for example, if you merely \fBcat\fP a file owned by someone else on the server machine), it can change your window title (unless you have disabled this using the \fBNoRemoteWinTitle\fP resource) and then use this service to have the new window title sent back to the server as if typed at the keyboard. This allows an attacker to fake keypresses and potentially cause your server-side applications to do things you didn\*(Aqt want. Therefore this feature is disabled by default, and we recommend you do not turn it on unless you \fIreally\fP know what you are doing. +.RE +.IP "\fBpterm.NoDBackspace\fP" +This option should be set to either 0 or 1; the default is 0. When set to 1, it disables the normal action of the Delete (\fB^?\fP) character when sent from the server to the terminal, which is to move the cursor left by one space and erase the character now under it. +.IP "\fBpterm.ApplicationCursorKeys\fP" +This option should be set to either 0 or 1; the default is 0. When set to 1, the default initial state of the cursor keys are application mode (where the keys send function-key-like sequences instead of numbers or arrow keys). When set to 0, the default state is the normal one. +.IP "\fBpterm.ApplicationKeypad\fP" +This option should be set to either 0 or 1; the default is 0. When set to 1, the default initial state of the numeric keypad is application mode (where the keys send function-key-like sequences instead of numbers or arrow keys). When set to 0, the default state is the normal one. +.IP "\fBpterm.NetHackKeypad\fP" +This option should be set to either 0 or 1; the default is 0. When set to 1, the numeric keypad operates in NetHack mode. This is equivalent to the \fB\-nethack\fP command-line option. +.IP "\fBpterm.Answerback\fP" +This option controls the string which the terminal sends in response to receiving the \fB^E\fP character (`tell me about yourself'). By default this string is `\fBPuTTY\fP'. +.IP "\fBpterm.HideMousePtr\fP" +This option should be set to either 0 or 1; the default is 0. When it is set to 1, the mouse pointer will disappear if it is over the \fBpterm\fP window and you press a key. It will reappear as soon as you move it. +.IP "\fBpterm.WindowBorder\fP" +This option controls the number of pixels of space between the text in the \fBpterm\fP window and the window frame. The default is 1. You can increase this value, but decreasing it to 0 is not recommended because it can cause the window manager\*(Aqs size hints to work incorrectly. +.IP "\fBpterm.CurType\fP" +This option should be set to either 0, 1 or 2; the default is 0. When set to 0, the text cursor displayed in the window is a rectangular block. When set to 1, the cursor is an underline; when set to 2, it is a vertical line. +.IP "\fBpterm.BlinkCur\fP" +This option should be set to either 0 or 1; the default is 0. When it is set to 1, the text cursor will blink when the window is active. +.IP "\fBpterm.Beep\fP" +This option should be set to either 0 or 2 (yes, 2); the default is 0. When it is set to 2, \fBpterm\fP will respond to a bell character (\fB^G\fP) by flashing the window instead of beeping. +.IP "\fBpterm.BellOverload\fP" +This option should be set to either 0 or 1; the default is 0. When it is set to 1, \fBpterm\fP will watch out for large numbers of bells arriving in a short time and will temporarily disable the bell until they stop. The idea is that if you \fBcat\fP a binary file, the frantic beeping will mostly be silenced by this feature and will not drive you crazy. +.RS +.PP +The bell overload mode is activated by receiving N bells in time T; after a further time S without any bells, overload mode will turn itself off again. +.PP +Bell overload mode is always deactivated by any keypress in the terminal. This means it can respond to large unexpected streams of data, but does not interfere with ordinary command-line activities that generate beeps (such as filename completion). +.RE +.IP "\fBpterm.BellOverloadN\fP" +This option counts the number of bell characters which will activate bell overload if they are received within a length of time T. The default is 5. +.IP "\fBpterm.BellOverloadT\fP" +This option specifies the time period in which receiving N or more bells will activate bell overload mode. It is measured in microseconds, so (for example) set it to 1000000 for one second. The default is 2000000 (two seconds). +.IP "\fBpterm.BellOverloadS\fP" +This option specifies the time period of silence required to turn off bell overload mode. It is measured in microseconds, so (for example) set it to 1000000 for one second. The default is 5000000 (five seconds of silence). +.IP "\fBpterm.ScrollbackLines\fP" +This option specifies how many lines of scrollback to save above the visible terminal screen. The default is 200. This resource is equivalent to the \fB\-sl\fP command-line option. +.IP "\fBpterm.DECOriginMode\fP" +This option should be set to either 0 or 1; the default is 0. It specifies the default state of DEC Origin Mode. (If you don't know what that means, you probably don't need to mess with it.) +.IP "\fBpterm.AutoWrapMode\fP" +This option should be set to either 0 or 1; the default is 1. It specifies the default state of auto wrap mode. When set to 1, very long lines will wrap over to the next line on the terminal; when set to 0, long lines will be squashed against the right-hand edge of the screen. +.IP "\fBpterm.LFImpliesCR\fP" +This option should be set to either 0 or 1; the default is 0. When set to 1, the terminal will return the cursor to the left side of the screen when it receives a line feed character. +.IP "\fBpterm.WinTitle\fP" +This resource is the same as the \fB\-T\fP command-line option: it controls the initial title of the window. The default is `\fBpterm\fP'. +.IP "\fBpterm.TermWidth\fP" +This resource is the same as the width part of the \fB\-geometry\fP command-line option: it controls the number of columns of text in the window. The default is 80. +.IP "\fBpterm.TermHeight\fP" +This resource is the same as the width part of the \fB\-geometry\fP command-line option: it controls the number of columns of text in the window. The defaults is 24. +.IP "\fBpterm.Font\fP" +This resource is the same as the \fB\-fn\fP command-line option: it controls the font used to display normal text. The default is `\fBfixed\fP'. +.IP "\fBpterm.BoldFont\fP" +This resource is the same as the \fB\-fb\fP command-line option: it controls the font used to display bold text when \fBBoldAsColour\fP is set to 0 or 2. The default is unset (the font will be bolded by printing it twice at a one-pixel offset). +.IP "\fBpterm.WideFont\fP" +This resource is the same as the \fB\-fw\fP command-line option: it controls the font used to display double-width characters. The default is unset (double-width characters cannot be displayed). +.IP "\fBpterm.WideBoldFont\fP" +This resource is the same as the \fB\-fwb\fP command-line option: it controls the font used to display double-width characters in bold, when \fBBoldAsColour\fP is set to 0 or 2. The default is unset (double-width characters are displayed in bold by printing them twice at a one-pixel offset). +.IP "\fBpterm.ShadowBoldOffset\fP" +This resource can be set to an integer; the default is \(hy1. It specifies the offset at which text is overprinted when using `shadow bold' mode. The default (1) means that the text will be printed in the normal place, and also one character to the right; this seems to work well for most X bitmap fonts, which have a blank line of pixels down the right-hand side. For some fonts, you may need to set this to \(hy1, so that the text is overprinted one pixel to the left; for really large fonts, you may want to set it higher than 1 (in one direction or the other). +.IP "\fBpterm.BoldAsColour\fP" +This option should be set to either 0, 1, or 2; the default is 1. It specifies how bold text should be displayed. When set to 1, bold text is shown by displaying it in a brighter colour; when set to 0, bold text is shown by displaying it in a heavier font; when set to 2, both effects happen at once (a heavy font \fIand\fP a brighter colour). +.IP "\fBpterm.Colour0\fP, \fBpterm.Colour1\fP, ..., \fBpterm.Colour21\fP" +These options control the various colours used to display text in the \fBpterm\fP window. Each one should be specified as a triple of decimal numbers giving red, green and blue values: so that black is `\fB0,0,0\fP', white is `\fB255,255,255\fP', red is `\fB255,0,0\fP' and so on. +.RS +.PP +Colours 0 and 1 specify the foreground colour and its bold equivalent (the \fB\-fg\fP and \fB\-bfg\fP command-line options). Colours 2 and 3 specify the background colour and its bold equivalent (the \fB\-bg\fP and \fB\-bbg\fP command-line options). Colours 4 and 5 specify the text and block colours used for the cursor (the \fB\-cfg\fP and \fB\-cbg\fP command-line options). Each even number from 6 to 20 inclusive specifies the colour to be used for one of the ANSI primary colour specifications (black, red, green, yellow, blue, magenta, cyan, white, in that order); the odd numbers from 7 to 21 inclusive specify the bold version of each colour, in the same order. The defaults are: +.PP +.nf +pterm.Colour0:\ 187,187,187 +pterm.Colour1:\ 255,255,255 +pterm.Colour2:\ 0,0,0 +pterm.Colour3:\ 85,85,85 +pterm.Colour4:\ 0,0,0 +pterm.Colour5:\ 0,255,0 +pterm.Colour6:\ 0,0,0 +pterm.Colour7:\ 85,85,85 +pterm.Colour8:\ 187,0,0 +pterm.Colour9:\ 255,85,85 +pterm.Colour10:\ 0,187,0 +pterm.Colour11:\ 85,255,85 +pterm.Colour12:\ 187,187,0 +pterm.Colour13:\ 255,255,85 +pterm.Colour14:\ 0,0,187 +pterm.Colour15:\ 85,85,255 +pterm.Colour16:\ 187,0,187 +pterm.Colour17:\ 255,85,255 +pterm.Colour18:\ 0,187,187 +pterm.Colour19:\ 85,255,255 +pterm.Colour20:\ 187,187,187 +pterm.Colour21:\ 255,255,255 +.fi +.RE +.IP "\fBpterm.RectSelect\fP" +This option should be set to either 0 or 1; the default is 0. When set to 0, dragging the mouse over several lines selects to the end of each line and from the beginning of the next; when set to 1, dragging the mouse over several lines selects a rectangular region. In each case, holding down Alt while dragging gives the other behaviour. +.IP "\fBpterm.MouseOverride\fP" +This option should be set to either 0 or 1; the default is 1. When set to 1, if the application requests mouse tracking (so that mouse clicks are sent to it instead of doing selection), holding down Shift will revert the mouse to normal selection. When set to 0, mouse tracking completely disables selection. +.IP "\fBpterm.Printer\fP" +This option is unset by default. If you set it, then server-controlled printing is enabled: the server can send control sequences to request data to be sent to a printer. That data will be piped into the command you specify here; so you might want to set it to `\fBlpr\fP', for example, or `\fBlpr \-Pmyprinter\fP'. +.IP "\fBpterm.ScrollBar\fP" +This option should be set to either 0 or 1; the default is 1. When set to 0, the scrollbar is hidden (although Shift-PageUp and Shift-PageDown still work). This is the same as the \fB\-sb\fP command-line option. +.IP "\fBpterm.ScrollbarOnLeft\fP" +This option should be set to either 0 or 1; the default is 0. When set to 1, the scrollbar will be displayed on the left of the terminal instead of on the right. +.IP "\fBpterm.ScrollOnKey\fP" +This option should be set to either 0 or 1; the default is 0. When set to 1, any keypress causes the position of the scrollback to be reset to the very bottom. +.IP "\fBpterm.ScrollOnDisp\fP" +This option should be set to either 0 or 1; the default is 1. When set to 1, any activity in the display causes the position of the scrollback to be reset to the very bottom. +.IP "\fBpterm.LineCodePage\fP" +This option specifies the character set to be used for the session. This is the same as the \fB\-cs\fP command-line option. +.IP "\fBpterm.NoRemoteCharset\fP" +This option disables the terminal's ability to change its character set when it receives escape sequences telling it to. You might need to do this to interoperate with programs which incorrectly change the character set to something they think is sensible. +.IP "\fBpterm.BCE\fP" +This option should be set to either 0 or 1; the default is 1. When set to 1, the various control sequences that erase parts of the terminal display will erase in whatever the current background colour is; when set to 0, they will erase in black always. +.IP "\fBpterm.BlinkText\fP" +This option should be set to either 0 or 1; the default is 0. When set to 1, text specified as blinking by the server will actually blink on and off; when set to 0, \fBpterm\fP will use the less distracting approach of making the text\*(Aqs background colour bold. +.IP "\fBpterm.StampUtmp\fP" +This option should be set to either 0 or 1; the default is 1. When set to 1, \fBpterm\fP will log the login in the various system log files. This resource is equivalent to the \fB\-ut\fP command-line option. +.IP "\fBpterm.LoginShell\fP" +This option should be set to either 0 or 1; the default is 1. When set to 1, \fBpterm\fP will execute your shell as a login shell. This resource is equivalent to the \fB\-ls\fP command-line option. +.SH "BUGS" +.PP +Most of the X resources have silly names. (Historical reasons from PuTTY, mostly.) diff --git a/doc/pubkey.but b/doc/pubkey.but index f9f894f..9a360e7 100644 --- a/doc/pubkey.but +++ b/doc/pubkey.but @@ -61,14 +61,12 @@ The key types supported by PuTTY are described in \k{puttygen-keytype}. \H{pubkey-puttygen} Using \i{PuTTYgen}, the PuTTY key generator -\cfg{winhelp-topic}{puttygen.general} - PuTTYgen is a key generator. It \I{generating keys}generates pairs of public and private keys to be used with PuTTY, PSCP, and Plink, as well as the PuTTY authentication agent, Pageant (see \k{pageant}). PuTTYgen generates RSA, DSA, ECDSA, and Ed25519 keys. -When you run PuTTYgen you will see a window where you have two +When you run PuTTYgen you will see a window where you have two main choices: \q{Generate}, to generate a new public/private key pair, or \q{Load} to load in an existing private key. @@ -93,7 +91,7 @@ detail in \k{puttygen-keytype} and Your key pair is now ready for use. You may also want to copy the public key to your server, either by copying it out of the \q{Public -key for pasting into authorized_keys file} box (see +key for pasting into OpenSSH authorized_keys file} box (see \k{puttygen-pastekey}), or by using the \q{Save public key} button (\k{puttygen-savepub}). However, you don't need to do this immediately; if you want, you can load the private key back into @@ -106,15 +104,13 @@ server to accept it. \S{puttygen-keytype} Selecting the type of key -\cfg{winhelp-topic}{puttygen.keytype} - Before generating a key pair using PuTTYgen, you need to select -which type of key you need. PuTTYgen currently supports these types -of key: +which type of key you need. -\b An \i{RSA} key for use with the SSH-1 protocol. +The current version of the SSH protocol, SSH-2, supports several +different key types. PuTTYgen can generate: -\b An RSA key for use with the SSH-2 protocol. +\b An \i{RSA} key for use with the SSH-2 protocol. \b A \i{DSA} key for use with the SSH-2 protocol. @@ -124,17 +120,13 @@ SSH-2 protocol. \b An \i{Ed25519} key (another elliptic curve algorithm) for use with the SSH-2 protocol. -The SSH-1 protocol only supports RSA keys; if you will be connecting -using the SSH-1 protocol, you must select the first key type or your -key will be completely useless. - -The SSH-2 protocol supports more than one key type. The types -supported by PuTTY are RSA, DSA, ECDSA, and Ed25519. +PuTTYgen can also generate an RSA key suitable for use with the old +SSH-1 protocol (which only supports RSA); for this, you need to select +the \q{SSH-1 (RSA)} option. Since the SSH-1 protocol is no longer +considered secure, it's rare to need this option. \S{puttygen-strength} Selecting the size (strength) of the key -\cfg{winhelp-topic}{puttygen.bits} - The \q{Number of bits} input box allows you to choose the strength of the key PuTTYgen will generate. @@ -149,8 +141,6 @@ equivalent security to RSA with smaller key sizes.) \S{puttygen-generate} The \q{Generate} button -\cfg{winhelp-topic}{puttygen.generate} - Once you have chosen the type of key you want, and the strength of the key, press the \q{Generate} button and PuTTYgen will begin the process of actually generating the key. @@ -177,8 +167,6 @@ appear in the window to indicate this. \S{puttygen-fingerprint} The \q{\ii{Key fingerprint}} box -\cfg{winhelp-topic}{puttygen.fingerprint} - The \q{Key fingerprint} box shows you a fingerprint value for the generated key. This is derived cryptographically from the \e{public} key value, so it doesn't need to be kept secret; it is supposed to @@ -193,8 +181,6 @@ utility, will list key fingerprints rather than the whole public key. \S{puttygen-comment} Setting a comment for your key -\cfg{winhelp-topic}{puttygen.comment} - If you have more than one key and use them for different purposes, you don't need to memorise the key fingerprints in order to tell them apart. PuTTYgen allows you to enter a \e{comment} for your key, @@ -213,8 +199,6 @@ PuTTYgen, change the comment, and save it again. \S{puttygen-passphrase} Setting a \i{passphrase} for your key -\cfg{winhelp-topic}{puttygen.passphrase} - The \q{Key passphrase} and \q{Confirm passphrase} boxes allow you to choose a passphrase for your key. The passphrase will be used to \i{encrypt} the key on disk, so you will not be able to use the key @@ -258,8 +242,6 @@ a result. \S{puttygen-savepriv} Saving your private key to a disk file -\cfg{winhelp-topic}{puttygen.savepriv} - Once you have generated a key, set a comment field and set a passphrase, you are ready to save your private key to disk. @@ -274,8 +256,6 @@ will need to tell PuTTY to use for authentication (see \S{puttygen-savepub} Saving your public key to a disk file -\cfg{winhelp-topic}{puttygen.savepub} - RFC 4716 specifies a \I{SSH-2 public key format}standard format for storing SSH-2 public keys on disk. Some SSH servers (such as \i\cw{ssh.com}'s) require a public key in this format in order to accept @@ -297,16 +277,14 @@ will contain exactly the same text that appears in the \q{Public key for pasting} box. This is the only existing standard for SSH-1 public keys. -\S{puttygen-pastekey} \q{Public key for pasting into \i{authorized_keys -file}} - -\cfg{winhelp-topic}{puttygen.pastekey} +\S{puttygen-pastekey} \q{Public key for pasting into OpenSSH +\i{authorized_keys file}} -All SSH-1 servers require your public key to be given to it in a -one-line format before it will accept authentication with your -private key. The \i{OpenSSH} server also requires this for SSH-2. +The \i{OpenSSH} server, among others, requires your public key to be +given to it in a one-line format before it will accept authentication +with your private key. (SSH-1 servers also used this method.) -The \q{Public key for pasting into authorized_keys file} gives the +The \q{Public key for pasting into OpenSSH authorized_keys file} gives the public-key data in the correct one-line format. Typically you will want to select the entire contents of the box using the mouse, press Ctrl+C to copy it to the clipboard, and then paste the data into a @@ -317,8 +295,6 @@ public-key authentication once you have generated a key. \S{puttygen-load} Reloading a private key -\cfg{winhelp-topic}{puttygen.load} - PuTTYgen allows you to load an existing private key file into memory. If you do this, you can then change the passphrase and comment before saving it again; you can also make extra copies of @@ -337,14 +313,7 @@ for information about importing foreign key formats. \S{puttygen-conversions} Dealing with private keys in other formats -\cfg{winhelp-topic}{puttygen.conversions} - -Most SSH-1 clients use a standard format for storing private keys on -disk. PuTTY uses this format as well; so if you have generated an -SSH-1 private key using OpenSSH or \cw{ssh.com}'s client, you can use -it with PuTTY, and vice versa. - -However, SSH-2 private keys have no standard format. \I{OpenSSH private +SSH-2 private keys have no standard format. \I{OpenSSH private key format}OpenSSH and \I{ssh.com private key format}\cw{ssh.com} have different formats, and PuTTY's is different again. So a key generated with one client cannot immediately be used with @@ -356,8 +325,8 @@ menu, PuTTYgen can load SSH-2 private keys in OpenSSH's format and can then save it back out as a PuTTY-format key (\c{*.\i{PPK}}) so that you can use it with the PuTTY suite. The passphrase will be unchanged by this process (unless you deliberately change it). You may want to change -the key comment before you save the key, since OpenSSH's SSH-2 key -format contains no space for a comment and \cw{ssh.com}'s default +the key comment before you save the key, since some OpenSSH key +formats contained no space for a comment, and \cw{ssh.com}'s default comment format is long and verbose. PuTTYgen can also \i{export private keys} in OpenSSH format and in @@ -377,8 +346,12 @@ reason for wanting to use OpenSSH's newer format even for RSA, DSA, or ECDSA keys, you can choose \q{Export OpenSSH key (force new file format)}. -Note that since only SSH-2 keys come in different formats, the export -options are not available if you have generated an SSH-1 key. +Most clients for the older SSH-1 protocol use a standard format for +storing private keys on disk. PuTTY uses this format as well; so if +you have generated an SSH-1 private key using OpenSSH or +\cw{ssh.com}'s client, you can use it with PuTTY, and vice versa. +Hence, the export options are not available if you have generated an +SSH-1 key. \H{pubkey-gettingready} Getting ready for public key authentication @@ -387,21 +360,21 @@ connection succeeds you will be prompted for your user name and password to login. Once logged in, you must configure the server to accept your public key for authentication: -\b If your server is using the SSH-1 protocol, you should change -into the \i\c{.ssh} directory and open the file \i\c{authorized_keys} -with your favourite editor. (You may have to create this file if -this is the first key you have put in it). Then switch to the -PuTTYgen window, select all of the text in the \q{Public key for -pasting into authorized_keys file} box (see \k{puttygen-pastekey}), -and copy it to the clipboard (\c{Ctrl+C}). Then, switch back to the -PuTTY window and insert the data into the open file, making sure it -ends up all on one line. Save the file. - -\b If your server is \i{OpenSSH} and is using the SSH-2 protocol, you -should follow the same instructions, except that in earlier versions -of OpenSSH 2 the file might be called \c{authorized_keys2}. (In -modern versions the same \c{authorized_keys} file is used for both -SSH-1 and SSH-2 keys.) +\b If your server is \i{OpenSSH}, you should change into the +\i\c{.ssh} directory under your home directory, and open the file +\i\c{authorized_keys} with your favourite editor. (You may have to +create this file, if this is the first key you have put in it.) Then +switch to the PuTTYgen window, select all of the text in the \q{Public +key for pasting into OpenSSH authorized_keys file} box (see +\k{puttygen-pastekey}), and copy it to the clipboard (\c{Ctrl+C}). +Then, switch back to the PuTTY window and insert the data into the +open file, making sure it ends up all on one line. Save the file. + +\lcont{ +(In very old versions of OpenSSH, SSH-2 keys had to be put in a +separate file called \c{authorized_keys2}. In all current versions, +the same \c{authorized_keys} file is used for both SSH-1 and SSH-2 keys.) +} \b If your server is \i\cw{ssh.com}'s product and is using SSH-2, you need to save a \e{public} key file from PuTTYgen (see @@ -417,8 +390,9 @@ that server. You may also need to ensure that your home directory, your \c{.ssh} directory, and any other files involved (such as \c{authorized_keys}, \c{authorized_keys2} or \c{authorization}) are -not group-writable or world-writable. You can typically do this by -using a command such as +not group-writable or world-writable; servers will typically ignore +the keys unless this is done. You can typically do this by using a +command such as \c chmod go-w $HOME $HOME/.ssh $HOME/.ssh/authorized_keys diff --git a/doc/putty.1 b/doc/putty.1 new file mode 100644 index 0000000..5902ebf --- /dev/null +++ b/doc/putty.1 @@ -0,0 +1,152 @@ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.TH "putty" "1" "2004\(hy03\(hy24" "PuTTY\ tool\ suite" "PuTTY\ tool\ suite" +.SH "NAME" +.PP +\fBputty\fP - GUI SSH, Telnet and Rlogin client for X +.SH "SYNOPSIS" +.PP +.nf +\fBputty\fP\ [\ \fIoptions\fP\ ]\ [\ \fIhost\fP\ ] +.fi +.SH "DESCRIPTION" +.PP +\fBputty\fP is a graphical SSH, Telnet and Rlogin client for X. It is a direct port of the Windows SSH client of the same name. +.SH "OPTIONS" +.PP +The command-line options supported by \fBputty\fP are: +.IP "\fB\-\-display\fP \fIdisplay\-name\fP" +Specify the X display on which to open \fBputty\fP. (Note this option has a double minus sign, even though none of the others do. This is because this option is supplied automatically by GTK. Sorry.) +.IP "\fB\-fn\fP \fIfont-name\fP" +Specify the font to use for normal text displayed in the terminal. For example, \fB\-fn\ fixed\fP, \fB\-fn\ "Monospace\ 12"\fP. +.IP "\fB\-fb\fP \fIfont-name\fP" +Specify the font to use for bold text displayed in the terminal. If the \fBBoldAsColour\fP resource is set to 1 (the default), bold text will be displayed in different colours instead of a different font, so this option will be ignored. If \fBBoldAsColour\fP is set to 0 or 2 and you do not specify a bold font, \fBputty\fP will overprint the normal font to make it look bolder. +.IP "\fB\-fw\fP \fIfont-name\fP" +Specify the font to use for double-width characters (typically Chinese, Japanese and Korean text) displayed in the terminal. +.IP "\fB\-fwb\fP \fIfont-name\fP" +Specify the font to use for bold double-width characters (typically Chinese, Japanese and Korean text). Like \fB-fb\fP, this will be ignored unless the \fBBoldAsColour\fP resource is set to 0 or 2. +.IP "\fB\-geometry\fP \fIgeometry\fP" +Specify the size of the terminal, in rows and columns of text. See \fIX(7)\fP for more information on the syntax of geometry specifications. +.IP "\fB\-sl\fP \fIlines\fP" +Specify the number of lines of scrollback to save off the top of the terminal. +.IP "\fB\-fg\fP \fIcolour\fP" +Specify the foreground colour to use for normal text. +.IP "\fB\-bg\fP \fIcolour\fP" +Specify the background colour to use for normal text. +.IP "\fB\-bfg\fP \fIcolour\fP" +Specify the foreground colour to use for bold text, if the \fBBoldAsColour\fP resource is set to 1 (the default) or 2. +.IP "\fB\-bbg\fP \fIcolour\fP" +Specify the foreground colour to use for bold reverse-video text, if the \fBBoldAsColour\fP resource is set to 1 (the default) or 2. (This colour is best thought of as the bold version of the background colour; so it only appears when text is displayed \fIin\fP the background colour.) +.IP "\fB\-cfg\fP \fIcolour\fP" +Specify the foreground colour to use for text covered by the cursor. +.IP "\fB\-cbg\fP \fIcolour\fP" +Specify the background colour to use for text covered by the cursor. In other words, this is the main colour of the cursor. +.IP "\fB\-title\fP \fItitle\fP" +Specify the initial title of the terminal window. (This can be changed under control of the server.) +.IP "\fB\-sb\-\fP or \fB+sb\fP" +Tells \fBputty\fP not to display a scroll bar. +.IP "\fB\-sb\fP" +Tells \fBputty\fP to display a scroll bar: this is the opposite of \fB\-sb\-\fP. This is the default option: you will probably only need to specify it explicitly if you have changed the default using the \fBScrollBar\fP resource. +.IP "\fB\-log\fP \fIlogfile\fP, \fB\-sessionlog\fP \fIlogfile\fP" +This option makes \fBputty\fP log all the terminal output to a file as well as displaying it in the terminal. +.IP "\fB\-sshlog\fP \fIlogfile\fP" + +.IP "\fB\-sshrawlog\fP \fIlogfile\fP" +For SSH connections, these options make \fBputty\fP log protocol details to a file. (Some of these may be sensitive, although by default an effort is made to suppress obvious passwords.) +.RS +.PP +\fB\-sshlog\fP logs decoded SSH packets and other events (those that \fB\-v\fP would print). \fB\-sshrawlog\fP additionally logs the raw encrypted packet data. +.RE +.IP "\fB\-cs\fP \fIcharset\fP" +This option specifies the character set in which \fBputty\fP should assume the session is operating. This character set will be used to interpret all the data received from the session, and all input you type or paste into \fBputty\fP will be converted into this character set before being sent to the session. +.RS +.PP +Any character set name which is valid in a MIME header (and supported by \fBputty\fP) should be valid here (examples are `\fBISO-8859-1\fP', `\fBwindows-1252\fP' or `\fBUTF-8\fP'). Also, any character encoding which is valid in an X logical font description should be valid (`\fBibm-cp437\fP', for example). +.PP +\fBputty\fP\*(Aqs default behaviour is to use the same character encoding as its primary font. If you supply a Unicode (\fBiso10646-1\fP) font, it will default to the UTF-8 character set. +.PP +Character set names are case-insensitive. +.RE +.IP "\fB\-nethack\fP" +Tells \fBputty\fP to enable NetHack keypad mode, in which the numeric keypad generates the NetHack \fBhjklyubn\fP direction keys. This enables you to play NetHack with the numeric keypad without having to use the NetHack \fBnumber_pad\fP option (which requires you to press `\fBn\fP' before any repeat count). So you can move with the numeric keypad, and enter repeat counts with the normal number keys. +.IP "\fB\-help\fP, \fB\-\-help\fP" +Display a message summarizing the available options. +.IP "\fB\-pgpfp\fP" +Display the fingerprints of the PuTTY PGP Master Keys, to aid in verifying new files released by the PuTTY team. +.IP "\fB\-load\fP \fIsession\fP" +Load a saved session by name. This allows you to run a saved session straight from the command line without having to go through the configuration box first. +.IP "\fB\-ssh\fP, \fB\-telnet\fP, \fB\-rlogin\fP, \fB\-raw\fP, \fB\-serial\fP" +Select the protocol \fBputty\fP will use to make the connection. +.IP "\fB\-proxycmd\fP \fIcommand\fP" +Instead of making a TCP connection, use \fIcommand\fP as a proxy; network traffic will be redirected to the standard input and output of \fIcommand\fP. \fIcommand\fP must be a single word, so is likely to need quoting by the shell. +.RS +.PP +The special strings \fB%host\fP and \fB%port\fP in \fIcommand\fP will be replaced by the hostname and port number you want to connect to; to get a literal \fB%\fP sign, enter \fB%%\fP. +.PP +Backslash escapes are also supported, such as sequences like \fB\en\fP being replaced by a literal newline; to get a literal backslash, enter \fB\e\e\fP. (Further escaping may be required by the shell.) +.PP +(See the main PuTTY manual for full details of the supported \fB%\fP- and backslash-delimited tokens, although most of them are probably not very useful in this context.) +.RE +.IP "\fB\-l\fP \fIusername\fP" +Specify the username to use when logging in to the server. +.IP "\fB\-L\fP \fB[\fP\fIsrcaddr\fP\fB:]\fP\fIsrcport\fP\fB:\fP\fIdesthost\fP\fB:\fP\fIdestport\fP" +Set up a local port forwarding: listen on \fIsrcport\fP (or \fIsrcaddr\fP:\fIsrcport\fP if specified), and forward any connections over the SSH connection to the destination address \fIdesthost\fP:\fIdestport\fP. Only works in SSH. +.IP "\fB\-R\fP \fB[\fP\fIsrcaddr\fP\fB:]\fP\fIsrcport\fP\fB:\fP\fIdesthost\fP\fB:\fP\fIdestport\fP" +Set up a remote port forwarding: ask the SSH server to listen on \fIsrcport\fP (or \fIsrcaddr\fP:\fIsrcport\fP if specified), and to forward any connections back over the SSH connection where the client will pass them on to the destination address \fIdesthost\fP:\fIdestport\fP. Only works in SSH. +.IP "\fB\-D\fP [\fIsrcaddr\fP:]\fIsrcport\fP" +Set up dynamic port forwarding. The client listens on \fIsrcport\fP (or \fIsrcaddr\fP:\fIsrcport\fP if specified), and implements a SOCKS server. So you can point SOCKS-aware applications at this port and they will automatically use the SSH connection to tunnel all their connections. Only works in SSH. +.IP "\fB\-P\fP \fIport\fP" +Specify the port to connect to the server on. +.IP "\fB\-A\fP, \fB\-a\fP" +Enable (\fB\-A\fP) or disable (\fB\-a\fP) SSH agent forwarding. Currently this only works with OpenSSH and SSH-1. +.IP "\fB\-X\fP, \fB\-x\fP" +Enable (\fB\-X\fP) or disable (\fB\-x\fP) X11 forwarding. +.IP "\fB\-T\fP, \fB\-t\fP" +Enable (\fB\-t\fP) or disable (\fB\-T\fP) the allocation of a pseudo-terminal at the server end. +.IP "\fB\-C\fP" +Enable zlib-style compression on the connection. +.IP "\fB\-1\fP, \fB\-2\fP" +Select SSH protocol version 1 or 2. +.IP "\fB-4\fP, \fB-6\fP" +Force use of IPv4 or IPv6 for network connections. +.IP "\fB\-i\fP \fIkeyfile\fP" +Private key file for user authentication. For SSH-2 keys, this key file must be in PuTTY's PPK format, not OpenSSH's format or anyone else's. +.RS +.PP +If you are using an authentication agent, you can also specify a \fIpublic\fP key here (in RFC 4716 or OpenSSH format), to identify which of the agent's keys to use. +.RE +.IP "\fB\-noagent\fP" +Don't try to use an authentication agent for local authentication. (This doesn't affect agent forwarding.) +.IP "\fB\-agent\fP" +Allow use of an authentication agent. (This option is only necessary to override a setting in a saved session.) +.IP "\fB\-hostkey\fP \fIkey\fP" +Specify an acceptable host public key. This option may be specified multiple times; each key can be either a fingerprint (\fB99:aa:bb:...\fP) or a base64-encoded blob in OpenSSH\*(Aqs one-line format. +.RS +.PP +Specifying this option overrides automated host key management; \fIonly\fP the key(s) specified on the command-line will be accepted (unless a saved session also overrides host keys, in which case those will be added to), and the host key cache will not be written. +.RE +.IP "\fB\-sercfg\fP \fIconfiguration-string\fP" +Specify the configuration parameters for the serial port, in \fB-serial\fP mode. \fIconfiguration-string\fP should be a comma-separated list of configuration parameters as follows: +.RS +.IP "\fB\(bu\fP" +Any single digit from 5 to 9 sets the number of data bits. +.IP "\fB\(bu\fP" +`\fB1\fP', `\fB1.5\fP' or `\fB2\fP' sets the number of stop bits. +.IP "\fB\(bu\fP" +Any other numeric string is interpreted as a baud rate. +.IP "\fB\(bu\fP" +A single lower-case letter specifies the parity: `\fBn\fP' for none, `\fBo\fP' for odd, `\fBe\fP' for even, `\fBm\fP' for mark and `\fBs\fP' for space. +.IP "\fB\(bu\fP" +A single upper-case letter specifies the flow control: `\fBN\fP' for none, `\fBX\fP' for XON/XOFF, `\fBR\fP' for RTS/CTS and `\fBD\fP' for DSR/DTR. +.RE +.SH "SAVED SESSIONS" +.PP +Saved sessions are stored in a \fB.putty/sessions\fP subdirectory in your home directory. +.SH "MORE INFORMATION" +.PP +For more information on PuTTY, it's probably best to go and look at the manual on the web page: +.PP +\fBhttps://www.chiark.greenend.org.uk/~sgtatham/putty/\fP +.SH "BUGS" +.PP +This man page isn't terribly complete. diff --git a/doc/puttydoc.txt b/doc/puttydoc.txt new file mode 100644 index 0000000..807f3f7 --- /dev/null +++ b/doc/puttydoc.txt @@ -0,0 +1,9950 @@ + PuTTY User Manual + ================= + +PuTTY is a free (MIT-licensed) Windows Telnet and SSH client. This manual +documents PuTTY, and its companion utilities PSCP, PSFTP, Plink, Pageant +and PuTTYgen. + +_Note to Unix users:_ this manual currently primarily documents the Windows +versions of the PuTTY utilities. Some options are therefore mentioned +that are absent from the Unix version; the Unix version has features +not described here; and the pterm and command-line puttygen and pageant +utilities are not described at all. The only Unix-specific documentation +that currently exists is the man pages. + +This manual is copyright 1997-2019 Simon Tatham. All rights reserved. You +may distribute this documentation under the MIT licence. See appendix C for +the licence text in full. + +Chapter 1: Introduction to PuTTY +-------------------------------- + + PuTTY is a free SSH, Telnet and Rlogin client for Windows systems. + + 1.1 What are SSH, Telnet and Rlogin? + + If you already know what SSH, Telnet and Rlogin are, you can safely + skip on to the next section. + + SSH, Telnet and Rlogin are three ways of doing the same thing: + logging in to a multi-user computer from another computer, over a + network. + + Multi-user operating systems, such as Unix and VMS, usually present + a command-line interface to the user, much like the `Command Prompt' + or `MS-DOS Prompt' in Windows. The system prints a prompt, and you + type commands which the system will obey. + + Using this type of interface, there is no need for you to be sitting + at the same machine you are typing commands to. The commands, + and responses, can be sent over a network, so you can sit at one + computer and give commands to another one, or even to more than one. + + SSH, Telnet and Rlogin are _network protocols_ that allow you to do + this. On the computer you sit at, you run a _client_, which makes a + network connection to the other computer (the _server_). The network + connection carries your keystrokes and commands from the client to + the server, and carries the server's responses back to you. + + These protocols can also be used for other types of keyboard-based + interactive session. In particular, there are a lot of bulletin + boards, talker systems and MUDs (Multi-User Dungeons) which support + access using Telnet. There are even a few that support SSH. + + You might want to use SSH, Telnet or Rlogin if: + + - you have an account on a Unix or VMS system which you want to be + able to access from somewhere else + + - your Internet Service Provider provides you with a login account + on a web server. (This might also be known as a _shell account_. + A _shell_ is the program that runs on the server and interprets + your commands for you.) + + - you want to use a bulletin board system, talker or MUD which can + be accessed using Telnet. + + You probably do _not_ want to use SSH, Telnet or Rlogin if: + + - you only use Windows. Windows computers have their own ways + of networking between themselves, and unless you are doing + something fairly unusual, you will not need to use any of these + remote login protocols. + + 1.2 How do SSH, Telnet and Rlogin differ? + + This list summarises some of the differences between SSH, Telnet and + Rlogin. + + - SSH (which stands for `secure shell') is a recently designed, + high-security protocol. It uses strong cryptography to protect + your connection against eavesdropping, hijacking and other + attacks. Telnet and Rlogin are both older protocols offering + minimal security. + + - SSH and Rlogin both allow you to log in to the server without + having to type a password. (Rlogin's method of doing this is + insecure, and can allow an attacker to access your account on + the server. SSH's method is much more secure, and typically + breaking the security requires the attacker to have gained + access to your actual client machine.) + + - SSH allows you to connect to the server and automatically send + a command, so that the server will run that command and then + disconnect. So you can use it in automated processing. + + The Internet is a hostile environment and security is everybody's + responsibility. If you are connecting across the open Internet, + then we recommend you use SSH. If the server you want to connect + to doesn't support SSH, it might be worth trying to persuade the + administrator to install it. + + If your client and server are both behind the same (good) firewall, + it is more likely to be safe to use Telnet or Rlogin, but we still + recommend you use SSH. + +Chapter 2: Getting started with PuTTY +------------------------------------- + + This chapter gives a quick guide to the simplest types of + interactive login session using PuTTY. + + 2.1 Starting a session + + When you start PuTTY, you will see a dialog box. This dialog box + allows you to control everything PuTTY can do. See chapter 4 for + details of all the things you can control. + + You don't usually need to change most of the configuration options. + To start the simplest kind of session, all you need to do is to + enter a few basic parameters. + + In the `Host Name' box, enter the Internet host name of the server + you want to connect to. You should have been told this by the + provider of your login account. + + Now select a login protocol to use, from the `Connection type' + buttons. For a login session, you should select Telnet, Rlogin or + SSH. See section 1.2 for a description of the differences between + the three protocols, and advice on which one to use. The fourth + protocol, _Raw_, is not used for interactive login sessions; you + would usually use this for debugging other Internet services (see + section 3.6). The fifth option, _Serial_, is used for connecting to + a local serial line, and works somewhat differently: see section 3.7 + for more information on this. + + When you change the selected protocol, the number in the `Port' + box will change. This is normal: it happens because the various + login services are usually provided on different network ports + by the server machine. Most servers will use the standard port + numbers, so you will not need to change the port setting. If your + server provides login services on a non-standard port, your system + administrator should have told you which one. (For example, many + MUDs run Telnet service on a port other than 23.) + + Once you have filled in the `Host Name', `Protocol', and possibly + `Port' settings, you are ready to connect. Press the `Open' button + at the bottom of the dialog box, and PuTTY will begin trying to + connect you to the server. + + 2.2 Verifying the host key (SSH only) + + If you are not using the SSH protocol, you can skip this section. + + If you are using SSH to connect to a server for the first time, you + will probably see a message looking something like this: + + The server's host key is not cached in the registry. You + have no guarantee that the server is the computer you + think it is. + The server's rsa2 key fingerprint is: + ssh-rsa 1024 7b:e5:6f:a7:f4:f9:81:62:5c:e3:1f:bf:8b:57:6c:5a + If you trust this host, hit Yes to add the key to + PuTTY's cache and carry on connecting. + If you want to carry on connecting just once, without + adding the key to the cache, hit No. + If you do not trust this host, hit Cancel to abandon the + connection. + + This is a feature of the SSH protocol. It is designed to protect you + against a network attack known as _spoofing_: secretly redirecting + your connection to a different computer, so that you send your + password to the wrong machine. Using this technique, an attacker + would be able to learn the password that guards your login account, + and could then log in as if they were you and use the account for + their own purposes. + + To prevent this attack, each server has a unique identifying code, + called a _host key_. These keys are created in a way that prevents + one server from forging another server's key. So if you connect to a + server and it sends you a different host key from the one you were + expecting, PuTTY can warn you that the server may have been switched + and that a spoofing attack might be in progress. + + PuTTY records the host key for each server you connect to, in the + Windows Registry. Every time you connect to a server, it checks that + the host key presented by the server is the same host key as it was + the last time you connected. If it is not, you will see a warning, + and you will have the chance to abandon your connection before you + type any private information (such as a password) into it. + + However, when you connect to a server you have not connected to + before, PuTTY has no way of telling whether the host key is the + right one or not. So it gives the warning shown above, and asks you + whether you want to trust this host key or not. + + Whether or not to trust the host key is your choice. If you are + connecting within a company network, you might feel that all + the network users are on the same side and spoofing attacks are + unlikely, so you might choose to trust the key without checking + it. If you are connecting across a hostile network (such as the + Internet), you should check with your system administrator, + perhaps by telephone or in person. (Many servers have more than + one host key. If the system administrator sends you more than one + fingerprint, you should make sure the one PuTTY shows you is on the + list, but it doesn't matter which one it is.) + + See section 4.21 for advanced options for managing host keys. + + 2.3 Logging in + + After you have connected, and perhaps verified the server's host + key, you will be asked to log in, probably using a username and a + password. Your system administrator should have provided you with + these. (If, instead, your system administrator has asked you to + provide, or provided you with, a `public key' or `key file', see + chapter 8.) + + PuTTY will display a text window (the `terminal window' - it will + have a black background unless you've changed the defaults), and + prompt you to type your username and password into that window. + (These prompts will include the PuTTY icon, to distinguish them from + any text sent by the server in the same window.) + + Enter the username and the password, and the server should grant you + access and begin your session. If you have mistyped your password, + most servers will give you several chances to get it right. + + While you are typing your password, you will not usually see the + cursor moving in the window, but PuTTY _is_ registering what you + type, and will send it when you press Return. (It works this way to + avoid revealing the length of your password to anyone watching your + screen.) + + If you are using SSH, be careful not to type your username wrongly, + because you will not have a chance to correct it after you press + Return; many SSH servers do not permit you to make two login + attempts using different usernames. If you type your username + wrongly, you must close PuTTY and start again. + + If your password is refused but you are sure you have typed it + correctly, check that Caps Lock is not enabled. Many login servers, + particularly Unix computers, treat upper case and lower case as + different when checking your password; so if Caps Lock is on, your + password will probably be refused. + + 2.4 After logging in + + After you log in to the server, what happens next is up to the + server! Most servers will print some sort of login message and then + present a prompt, at which you can type commands which the server + will carry out. Some servers will offer you on-line help; others + might not. If you are in doubt about what to do next, consult your + system administrator. + + 2.5 Logging out + + When you have finished your session, you should log out by typing + the server's own logout command. This might vary between servers; if + in doubt, try `logout' or `exit', or consult a manual or your system + administrator. When the server processes your logout command, the + PuTTY window should close itself automatically. + + You _can_ close a PuTTY session using the Close button in the window + border, but this might confuse the server - a bit like hanging up a + telephone unexpectedly in the middle of a conversation. We recommend + you do not do this unless the server has stopped responding to you + and you cannot close the window any other way. + +Chapter 3: Using PuTTY +---------------------- + + This chapter provides a general introduction to some more advanced + features of PuTTY. For extreme detail and reference purposes, + chapter 4 is likely to contain more information. + + 3.1 During your session + + A lot of PuTTY's complexity and features are in the configuration + panel. Once you have worked your way through that and started + a session, things should be reasonably simple after that. + Nevertheless, there are a few more useful features available. + + 3.1.1 Copying and pasting text + + Often in a PuTTY session you will find text on your terminal screen + which you want to type in again. Like most other terminal emulators, + PuTTY allows you to copy and paste the text rather than having to + type it again. Also, copy and paste uses the Windows clipboard, so + that you can paste (for example) URLs into a web browser, or paste + from a word processor or spreadsheet into your terminal session. + + By default, PuTTY's copy and paste works entirely with the mouse. + (This will be familiar to people who have used `xterm' on Unix.) In + order to copy text to the clipboard, you just click the left mouse + button in the terminal window, and drag to select text. When you + let go of the button, the text is _automatically_ copied to the + clipboard. You do not need to press Ctrl-C or Ctrl-Ins; in fact, if + you do press Ctrl-C, PuTTY will send a Ctrl-C character down your + session to the server where it will probably cause a process to be + interrupted. + + Pasting into PuTTY is done using the right button (or the middle + mouse button, if you have a three-button mouse and have set it up; + see section 4.11.1). (Pressing Shift-Ins, or selecting `Paste' from + the Ctrl+right-click context menu, have the same effect.) When you + click the right mouse button, PuTTY will read whatever is in the + Windows clipboard and paste it into your session. By default, this + behaves _exactly_ as if the clipboard contents had been typed at + the keyboard; therefore, be careful of pasting formatted text into + an editor that does automatic indenting, as you may find that the + spaces pasted from the clipboard plus the spaces added by the editor + add up to too many spaces and ruin the formatting. (Some remote + applications can ask PuTTY to identify text that is being pasted, to + avoid this sort of problem; but if your application does not, there + is nothing PuTTY can do to avoid this.) + + If you double-click the left mouse button, PuTTY will select a whole + word. If you double-click, hold down the second click, and drag the + mouse, PuTTY will select a sequence of whole words. (You can adjust + precisely what PuTTY considers to be part of a word; see section + 4.12.1.) If you _triple_-click, or triple-click and drag, then PuTTY + will select a whole line or sequence of lines. + + If you want to select a rectangular region instead of selecting to + the end of each line, you can do this by holding down Alt when you + make your selection. You can also configure rectangular selection to + be the default, and then holding down Alt gives the normal behaviour + instead: see section 4.11.3 for details. + + (In some Unix environments, Alt+drag is intercepted by the window + manager. Shift+Alt+drag should work for rectangular selection as + well, so you could try that instead.) + + If you have a middle mouse button, then you can use it to adjust an + existing selection if you selected something slightly wrong. (If you + have configured the middle mouse button to paste, then the right + mouse button does this instead.) Click the button on the screen, + and you can pick up the nearest end of the selection and drag it to + somewhere else. + + If you are running PuTTY itself on Unix (not just using it to + connect to a Unix system from Windows), by default you will likely + have to use similar mouse actions in other applications to paste the + text you copied from PuTTY, and to copy text for pasting into PuTTY; + actions like Ctrl-C and Ctrl-V will likely not behave as you expect. + Section 4.11.4 explains why this is, and how you can change the + behaviour. (On Windows there is only a single selection shared with + other applications, so this confusion does not arise.) + + It's possible for the server to ask to handle mouse clicks in the + PuTTY window itself. If this happens, the mouse pointer will turn + into an arrow, and using the mouse to copy and paste will only work + if you hold down Shift. See section 4.6.2 and section 4.11.2 for + details of this feature and how to configure it. + + You can customise much of this behaviour, for instance to enable + copy and paste from the keyboard; see section 4.11. + + 3.1.2 Scrolling the screen back + + PuTTY keeps track of text that has scrolled up off the top of the + terminal. So if something appears on the screen that you want to + read, but it scrolls too fast and it's gone by the time you try to + look for it, you can use the scrollbar on the right side of the + window to look back up the session history and find it again. + + As well as using the scrollbar, you can also page the scrollback up + and down by pressing Shift-PgUp and Shift-PgDn. You can scroll a + line at a time using Ctrl-PgUp and Ctrl-PgDn, or to the top/bottom + of the scrollback with Ctrl-Shift-PgUp and Ctrl-Shift-PgDn. These + are still available if you configure the scrollbar to be invisible. + + By default the last 2000 lines scrolled off the top are preserved + for you to look at. You can increase (or decrease) this value using + the configuration box; see section 4.7.3. + + 3.1.3 The System menu + + If you click the left mouse button on the icon in the top left + corner of PuTTY's terminal window, or click the right mouse button + on the title bar, you will see the standard Windows system menu + containing items like Minimise, Move, Size and Close. + + PuTTY's system menu contains extra program features in addition + to the Windows standard options. These extra menu commands are + described below. + + (These options are also available in a context menu brought up by + holding Ctrl and clicking with the right mouse button anywhere in + the PuTTY window.) + +3.1.3.1 The PuTTY Event Log + + If you choose `Event Log' from the system menu, a small window will + pop up in which PuTTY logs significant events during the connection. + Most of the events in the log will probably take place during + session startup, but a few can occur at any point in the session, + and one or two occur right at the end. + + You can use the mouse to select one or more lines of the Event Log, + and hit the Copy button to copy them to the clipboard. If you are + reporting a bug, it's often useful to paste the contents of the + Event Log into your bug report. + + (The Event Log is not the same as the facility to create a log file + of your session; that's described in section 3.2.) + +3.1.3.2 Special commands + + Depending on the protocol used for the current session, there may + be a submenu of `special commands'. These are protocol-specific + tokens, such as a `break' signal, that can be sent down a connection + in addition to normal data. Their precise effect is usually up to + the server. Currently only Telnet, SSH, and serial connections have + special commands. + + The `break' signal can also be invoked from the keyboard with Ctrl- + Break. + + In an SSH connection, the following special commands are available: + + - IGNORE message + + Should have no effect. + + - Repeat key exchange + + Only available in SSH-2. Forces a repeat key exchange + immediately (and resets associated timers and counters). For + more information about repeat key exchanges, see section 4.20.2. + + - Cache new host key type + + Only available in SSH-2. This submenu appears only if the server + has host keys of a type that PuTTY doesn't already have cached, + and so won't consider. Selecting a key here will allow PuTTY + to use that key now and in future: PuTTY will do a fresh key- + exchange with the selected key, and immediately add that key to + its permanent cache (relying on the host key used at the start + of the connection to cross-certify the new key). That key will + be used for the rest of the current session; it may not actually + be used for future sessions, depending on your preferences (see + section 4.21.1). + + Normally, PuTTY will carry on using a host key it already knows, + even if the server offers key formats that PuTTY would otherwise + prefer, to avoid host key prompts. As a result, if you've been + using a server for some years, you may still be using an older + key than a new user would use, due to server upgrades in the + meantime. The SSH protocol unfortunately does not have organised + facilities for host key migration and rollover, but this allows + you to manually upgrade. + + - Break + + Only available in SSH-2, and only during a session. Optional + extension; may not be supported by server. PuTTY requests the + server's default break length. + + - Signals (SIGINT, SIGTERM etc) + + Only available in SSH-2, and only during a session. Sends + various POSIX signals. Not honoured by all servers. + + The following special commands are available in Telnet: + + - Are You There + + - Break + + - Synch + + - Erase Character + + PuTTY can also be configured to send this when the Backspace key + is pressed; see section 4.17.3. + + - Erase Line + + - Go Ahead + + - No Operation + + Should have no effect. + + - Abort Process + + - Abort Output + + - Interrupt Process + + PuTTY can also be configured to send this when Ctrl-C is typed; + see section 4.17.3. + + - Suspend Process + + PuTTY can also be configured to send this when Ctrl-Z is typed; + see section 4.17.3. + + - End Of Record + + - End Of File + + With a serial connection, the only available special command is + `Break'. + +3.1.3.3 Starting new sessions + + PuTTY's system menu provides some shortcut ways to start new + sessions: + + - Selecting `New Session' will start a completely new instance of + PuTTY, and bring up the configuration box as normal. + + - Selecting `Duplicate Session' will start a session in a new + window with precisely the same options as your current one - + connecting to the same host using the same protocol, with all + the same terminal settings and everything. + + - In an inactive window, selecting `Restart Session' will do the + same as `Duplicate Session', but in the current window. + + - The `Saved Sessions' submenu gives you quick access to any sets + of stored session details you have previously saved. See section + 4.1.2 for details of how to create saved sessions. + +3.1.3.4 Changing your session settings + + If you select `Change Settings' from the system menu, PuTTY will + display a cut-down version of its initial configuration box. This + allows you to adjust most properties of your current session. You + can change the terminal size, the font, the actions of various + keypresses, the colours, and so on. + + Some of the options that are available in the main configuration box + are not shown in the cut-down Change Settings box. These are usually + options which don't make sense to change in the middle of a session + (for example, you can't switch from SSH to Telnet in mid-session). + + You can save the current settings to a saved session for future use + from this dialog box. See section 4.1.2 for more on saved sessions. + +3.1.3.5 Copy All to Clipboard + + This system menu option provides a convenient way to copy the whole + contents of the terminal screen (up to the last nonempty line) and + scrollback to the clipboard in one go. + +3.1.3.6 Clearing and resetting the terminal + + The `Clear Scrollback' option on the system menu tells PuTTY to + discard all the lines of text that have been kept after they + scrolled off the top of the screen. This might be useful, for + example, if you displayed sensitive information and wanted to make + sure nobody could look over your shoulder and see it. (Note that + this only prevents a casual user from using the scrollbar to view + the information; the text is not guaranteed not to still be in + PuTTY's memory.) + + The `Reset Terminal' option causes a full reset of the terminal + emulation. A VT-series terminal is a complex piece of software and + can easily get into a state where all the text printed becomes + unreadable. (This can happen, for example, if you accidentally + output a binary file to your terminal.) If this happens, selecting + Reset Terminal should sort it out. + +3.1.3.7 Full screen mode + + If you find the title bar on a maximised window to be ugly or + distracting, you can select Full Screen mode to maximise PuTTY `even + more'. When you select this, PuTTY will expand to fill the whole + screen and its borders, title bar and scrollbar will disappear. (You + can configure the scrollbar not to disappear in full-screen mode if + you want to keep it; see section 4.7.3.) + + When you are in full-screen mode, you can still access the system + menu if you click the left mouse button in the _extreme_ top left + corner of the screen. + + 3.2 Creating a log file of your session + + For some purposes you may find you want to log everything that + appears on your screen. You can do this using the `Logging' panel in + the configuration box. + + To begin a session log, select `Change Settings' from the system + menu and go to the Logging panel. Enter a log file name, and select + a logging mode. (You can log all session output including the + terminal control sequences, or you can just log the printable text. + It depends what you want the log for.) Click `Apply' and your log + will be started. Later on, you can go back to the Logging panel and + select `Logging turned off completely' to stop logging; then PuTTY + will close the log file and you can safely read it. + + See section 4.2 for more details and options. + + 3.3 Altering your character set configuration + + If you find that special characters (accented characters, for + example, or line-drawing characters) are not being displayed + correctly in your PuTTY session, it may be that PuTTY is + interpreting the characters sent by the server according to the + wrong _character set_. There are a lot of different character sets + available, and no good way for PuTTY to know which to use, so it's + entirely possible for this to happen. + + If you click `Change Settings' and look at the `Translation' panel, + you should see a large number of character sets which you can + select, and other related options. Now all you need is to find out + which of them you want! (See section 4.10 for more information.) + + 3.4 Using X11 forwarding in SSH + + The SSH protocol has the ability to securely forward X Window System + graphical applications over your encrypted SSH connection, so that + you can run an application on the SSH server machine and have it put + its windows up on your local machine without sending any X network + traffic in the clear. + + In order to use this feature, you will need an X display server + for your Windows machine, such as Cygwin/X, X-Win32, or Exceed. + This will probably install itself as display number 0 on your local + machine; if it doesn't, the manual for the X server should tell you + what it does do. + + You should then tick the `Enable X11 forwarding' box in the X11 + panel (see section 4.26) before starting your SSH session. The `X + display location' box is blank by default, which means that PuTTY + will try to use a sensible default such as `:0', which is the usual + display location where your X server will be installed. If that + needs changing, then change it. + + Now you should be able to log in to the SSH server as normal. To + check that X forwarding has been successfully negotiated during + connection startup, you can check the PuTTY Event Log (see section + 3.1.3.1). It should say something like this: + + 2001-12-05 17:22:01 Requesting X11 forwarding + 2001-12-05 17:22:02 X11 forwarding enabled + + If the remote system is Unix or Unix-like, you should also be able + to see that the `DISPLAY' environment variable has been set to point + at display 10 or above on the SSH server machine itself: + + fred@unixbox:~$ echo $DISPLAY + unixbox:10.0 + + If this works, you should then be able to run X applications in the + remote session and have them display their windows on your PC. + + For more options relating to X11 forwarding, see section 4.26. + + 3.5 Using port forwarding in SSH + + The SSH protocol has the ability to forward arbitrary network + (TCP) connections over your encrypted SSH connection, to avoid the + network traffic being sent in clear. For example, you could use + this to connect from your home computer to a POP-3 server on a + remote machine without your POP-3 password being visible to network + sniffers. + + In order to use port forwarding to connect from your local machine + to a port on a remote server, you need to: + + - Choose a port number on your local machine where PuTTY should + listen for incoming connections. There are likely to be plenty + of unused port numbers above 3000. (You can also use a local + loopback address here; see below for more details.) + + - Now, before you start your SSH connection, go to the Tunnels + panel (see section 4.27). Make sure the `Local' radio button + is set. Enter the local port number into the `Source port' + box. Enter the destination host name and port number into + the `Destination' box, separated by a colon (for example, + `popserver.example.com:110' to connect to a POP-3 server). + + - Now click the `Add' button. The details of your port forwarding + should appear in the list box. + + Now start your session and log in. (Port forwarding will not be + enabled until after you have logged in; otherwise it would be easy + to perform completely anonymous network attacks, and gain access to + anyone's virtual private network.) To check that PuTTY has set up + the port forwarding correctly, you can look at the PuTTY Event Log + (see section 3.1.3.1). It should say something like this: + + 2001-12-05 17:22:10 Local port 3110 forwarding to + popserver.example.com:110 + + Now if you connect to the source port number on your local PC, you + should find that it answers you exactly as if it were the service + running on the destination machine. So in this example, you could + then configure an e-mail client to use `localhost:3110' as a POP- + 3 server instead of `popserver.example.com:110'. (Of course, the + forwarding will stop happening when your PuTTY session closes down.) + + You can also forward ports in the other direction: arrange for a + particular port number on the _server_ machine to be forwarded back + to your PC as a connection to a service on your PC or near it. To do + this, just select the `Remote' radio button instead of the `Local' + one. The `Source port' box will now specify a port number on the + _server_ (note that most servers will not allow you to use port + numbers under 1024 for this purpose). + + An alternative way to forward local connections to remote hosts + is to use dynamic SOCKS proxying. In this mode, PuTTY acts as a + SOCKS server, which SOCKS-aware programs can connect to and open + forwarded connections to the destination of their choice, so this + can be an alternative to long lists of static forwardings. To use + this mode, you will need to select the `Dynamic' radio button + instead of `Local', and then you should not enter anything into the + `Destination' box (it will be ignored). PuTTY will then listen for + SOCKS connections on the port you have specified. Most web browsers + can be configured to connect to this SOCKS proxy service; also, you + can forward other PuTTY connections through it by setting up the + Proxy control panel (see section 4.16 for details). + + The source port for a forwarded connection usually does not accept + connections from any machine except the SSH client or server machine + itself (for local and remote forwardings respectively). There are + controls in the Tunnels panel to change this: + + - The `Local ports accept connections from other hosts' option + allows you to set up local-to-remote port forwardings (including + dynamic port forwardings) in such a way that machines other than + your client PC can connect to the forwarded port. + + - The `Remote ports do the same' option does the same thing for + remote-to-local port forwardings (so that machines other than + the SSH server machine can connect to the forwarded port.) Note + that this feature is only available in the SSH-2 protocol, and + not all SSH-2 servers honour it (in OpenSSH, for example, it's + usually disabled by default). + + You can also specify an IP address to listen on. Typically a + Windows machine can be asked to listen on any single IP address + in the 127.*.*.* range, and all of these are loopback addresses + available only to the local machine. So if you forward (for example) + `127.0.0.5:79' to a remote machine's finger port, then you should be + able to run commands such as `finger fred@127.0.0.5'. This can be + useful if the program connecting to the forwarded port doesn't allow + you to change the port number it uses. This feature is available + for local-to-remote forwarded ports; SSH-1 is unable to support it + for remote-to-local ports, while SSH-2 can support it in theory but + servers will not necessarily cooperate. + + (Note that if you're using Windows XP Service Pack 2, you may need + to obtain a fix from Microsoft in order to use addresses like + 127.0.0.5 - see question A.7.17.) + + For more options relating to port forwarding, see section 4.27. + + If the connection you are forwarding over SSH is itself a second + SSH connection made by another copy of PuTTY, you might find the + `logical host name' configuration option useful to warn PuTTY of + which host key it should be expecting. See section 4.14.5 for + details of this. + + 3.6 Making raw TCP connections + + A lot of Internet protocols are composed of commands and responses + in plain text. For example, SMTP (the protocol used to transfer e- + mail), NNTP (the protocol used to transfer Usenet news), and HTTP + (the protocol used to serve Web pages) all consist of commands in + readable plain text. + + Sometimes it can be useful to connect directly to one of these + services and speak the protocol `by hand', by typing protocol + commands and watching the responses. On Unix machines, you can do + this using the system's `telnet' command to connect to the right + port number. For example, `telnet mailserver.example.com 25' might + enable you to talk directly to the SMTP service running on a mail + server. + + Although the Unix `telnet' program provides this functionality, the + protocol being used is not really Telnet. Really there is no actual + protocol at all; the bytes sent down the connection are exactly the + ones you type, and the bytes shown on the screen are exactly the + ones sent by the server. Unix `telnet' will attempt to detect or + guess whether the service it is talking to is a real Telnet service + or not; PuTTY prefers to be told for certain. + + In order to make a debugging connection to a service of this + type, you simply select the fourth protocol name, `Raw', from the + `Protocol' buttons in the `Session' configuration panel. (See + section 4.1.1.) You can then enter a host name and a port number, + and make the connection. + + 3.7 Connecting to a local serial line + + PuTTY can connect directly to a local serial line as an alternative + to making a network connection. In this mode, text typed into the + PuTTY window will be sent straight out of your computer's serial + port, and data received through that port will be displayed in the + PuTTY window. You might use this mode, for example, if your serial + port is connected to another computer which has a serial connection. + + To make a connection of this type, simply select `Serial' from the + `Connection type' radio buttons on the `Session' configuration panel + (see section 4.1.1). The `Host Name' and `Port' boxes will transform + into `Serial line' and `Speed', allowing you to specify which serial + line to use (if your computer has more than one) and what speed + (baud rate) to use when transferring data. For further configuration + options (data bits, stop bits, parity, flow control), you can use + the `Serial' configuration panel (see section 4.29). + + After you start up PuTTY in serial mode, you might find that you + have to make the first move, by sending some data out of the serial + line in order to notify the device at the other end that someone is + there for it to talk to. This probably depends on the device. If you + start up a PuTTY serial session and nothing appears in the window, + try pressing Return a few times and see if that helps. + + A serial line provides no well defined means for one end of the + connection to notify the other that the connection is finished. + Therefore, PuTTY in serial mode will remain connected until you + close the window using the close button. + + 3.8 The PuTTY command line + + PuTTY can be made to do various things without user intervention + by supplying command-line arguments (e.g., from a command prompt + window, or a Windows shortcut). + + 3.8.1 Starting a session from the command line + + These options allow you to bypass the configuration window and + launch straight into a session. + + To start a connection to a server called `host': + + putty.exe [-ssh | -telnet | -rlogin | -raw] [user@]host + + If this syntax is used, settings are taken from the Default Settings + (see section 4.1.2); `user' overrides these settings if supplied. + Also, you can specify a protocol, which will override the default + protocol (see section 3.8.3.2). + + For telnet sessions, the following alternative syntax is supported + (this makes PuTTY suitable for use as a URL handler for telnet URLs + in web browsers): + + putty.exe telnet://host[:port]/ + + To start a connection to a serial port, e.g. COM1: + + putty.exe -serial com1 + + In order to start an existing saved session called `sessionname', + use the `-load' option (described in section 3.8.3.1). + + putty.exe -load "session name" + + 3.8.2 `-cleanup' + + If invoked with the `-cleanup' option, rather than running as + normal, PuTTY will remove its registry entries and random seed file + from the local machine (after confirming with the user). It will + also attempt to remove information about recently launched sessions + stored in the `jump list' on Windows 7 and up. + + Note that on multi-user systems, `-cleanup' only removes registry + entries and files associated with the currently logged-in user. + + 3.8.3 Standard command-line options + + PuTTY and its associated tools support a range of command-line + options, most of which are consistent across all the tools. This + section lists the available options in all tools. Options which are + specific to a particular tool are covered in the chapter about that + tool. + +3.8.3.1 `-load': load a saved session + + The `-load' option causes PuTTY to load configuration details out + of a saved session. If these details include a host name, then this + option is all you need to make PuTTY start a session. + + You need double quotes around the session name if it contains + spaces. + + If you want to create a Windows shortcut to start a PuTTY saved + session, this is the option you should use: your shortcut should + call something like + + d:\path\to\putty.exe -load "my session" + + (Note that PuTTY itself supports an alternative form of this option, + for backwards compatibility. If you execute `putty @sessionname' it + will have the same effect as `putty -load "sessionname"'. With the + `@' form, no double quotes are required, and the `@' sign must be + the very first thing on the command line. This form of the option is + deprecated.) + +3.8.3.2 Selecting a protocol: `-ssh', `-telnet', `-rlogin', `-raw' `- + serial' + + To choose which protocol you want to connect with, you can use one + of these options: + + - `-ssh' selects the SSH protocol. + + - `-telnet' selects the Telnet protocol. + + - `-rlogin' selects the Rlogin protocol. + + - `-raw' selects the raw protocol. + + - `-serial' selects a serial connection. + + These options are not available in the file transfer tools PSCP and + PSFTP (which only work with the SSH protocol). + + These options are equivalent to the protocol selection buttons + in the Session panel of the PuTTY configuration box (see section + 4.1.1). + +3.8.3.3 `-v': increase verbosity + + Most of the PuTTY tools can be made to tell you more about what they + are doing by supplying the `-v' option. If you are having trouble + when making a connection, or you're simply curious, you can turn + this switch on and hope to find out more about what is happening. + +3.8.3.4 `-l': specify a login name + + You can specify the user name to log in as on the remote server + using the `-l' option. For example, `plink login.example.com - + l fred'. + + These options are equivalent to the username selection box in + the Connection panel of the PuTTY configuration box (see section + 4.15.1). + +3.8.3.5 `-L', `-R' and `-D': set up port forwardings + + As well as setting up port forwardings in the PuTTY configuration + (see section 4.27), you can also set up forwardings on the command + line. The command-line options work just like the ones in Unix `ssh' + programs. + + To forward a local port (say 5110) to a remote destination (say + popserver.example.com port 110), you can write something like one of + these: + + putty -L 5110:popserver.example.com:110 -load mysession + plink mysession -L 5110:popserver.example.com:110 + + To forward a remote port to a local destination, just use the `-R' + option instead of `-L': + + putty -R 5023:mytelnetserver.myhouse.org:23 -load mysession + plink mysession -R 5023:mytelnetserver.myhouse.org:23 + + To specify an IP address for the listening end of the tunnel, + prepend it to the argument: + + plink -L 127.0.0.5:23:localhost:23 myhost + + To set up SOCKS-based dynamic port forwarding on a local port, use + the `-D' option. For this one you only have to pass the port number: + + putty -D 4096 -load mysession + + For general information on port forwarding, see section 3.5. + + These options are not available in the file transfer tools PSCP and + PSFTP. + +3.8.3.6 `-m': read a remote command or script from a file + + The `-m' option performs a similar function to the `Remote command' + box in the SSH panel of the PuTTY configuration box (see section + 4.19.1). However, the `-m' option expects to be given a local file + name, and it will read a command from that file. + + With some servers (particularly Unix systems), you can even put + multiple lines in this file and execute more than one command in + sequence, or a whole shell script; but this is arguably an abuse, + and cannot be expected to work on all servers. In particular, it is + known _not_ to work with certain `embedded' servers, such as Cisco + routers. + + This option is not available in the file transfer tools PSCP and + PSFTP. + +3.8.3.7 `-P': specify a port number + + The `-P' option is used to specify the port number to connect to. If + you have a Telnet server running on port 9696 of a machine instead + of port 23, for example: + + putty -telnet -P 9696 host.name + plink -telnet -P 9696 host.name + + (Note that this option is more useful in Plink than in PuTTY, + because in PuTTY you can write `putty -telnet host.name 9696' in any + case.) + + This option is equivalent to the port number control in the Session + panel of the PuTTY configuration box (see section 4.1.1). + +3.8.3.8 `-pw': specify a password + + A simple way to automate a remote login is to supply your password + on the command line. This is _not recommended_ for reasons of + security. If you possibly can, we recommend you set up public-key + authentication instead. See chapter 8 for details. + + Note that the `-pw' option only works when you are using the SSH + protocol. Due to fundamental limitations of Telnet and Rlogin, these + protocols do not support automated password authentication. + +3.8.3.9 `-agent' and `-noagent': control use of Pageant for authentication + + The `-agent' option turns on SSH authentication using Pageant, and + `-noagent' turns it off. These options are only meaningful if you + are using SSH. + + See chapter 9 for general information on Pageant. + + These options are equivalent to the agent authentication checkbox in + the Auth panel of the PuTTY configuration box (see section 4.23.3). + +3.8.3.10 `-A' and `-a': control agent forwarding + + The `-A' option turns on SSH agent forwarding, and `-a' turns it + off. These options are only meaningful if you are using SSH. + + See chapter 9 for general information on Pageant, and section 9.4 + for information on agent forwarding. Note that there is a security + risk involved with enabling this option; see section 9.5 for + details. + + These options are equivalent to the agent forwarding checkbox in the + Auth panel of the PuTTY configuration box (see section 4.23.6). + + These options are not available in the file transfer tools PSCP and + PSFTP. + +3.8.3.11 `-X' and `-x': control X11 forwarding + + The `-X' option turns on X11 forwarding in SSH, and `-x' turns it + off. These options are only meaningful if you are using SSH. + + For information on X11 forwarding, see section 3.4. + + These options are equivalent to the X11 forwarding checkbox in the + X11 panel of the PuTTY configuration box (see section 4.26). + + These options are not available in the file transfer tools PSCP and + PSFTP. + +3.8.3.12 `-t' and `-T': control pseudo-terminal allocation + + The `-t' option ensures PuTTY attempts to allocate a pseudo-terminal + at the server, and `-T' stops it from allocating one. These options + are only meaningful if you are using SSH. + + These options are equivalent to the `Don't allocate a pseudo- + terminal' checkbox in the SSH panel of the PuTTY configuration box + (see section 4.25.1). + + These options are not available in the file transfer tools PSCP and + PSFTP. + +3.8.3.13 `-N': suppress starting a shell or command + + The `-N' option prevents PuTTY from attempting to start a shell or + command on the remote server. You might want to use this option if + you are only using the SSH connection for port forwarding, and your + user account on the server does not have the ability to run a shell. + + This feature is only available in SSH protocol version 2 (since the + version 1 protocol assumes you will always want to run a shell). + + This option is equivalent to the `Don't start a shell or command at + all' checkbox in the SSH panel of the PuTTY configuration box (see + section 4.19.2). + + This option is not available in the file transfer tools PSCP and + PSFTP. + +3.8.3.14 `-nc': make a remote network connection in place of a remote shell + or command + + The `-nc' option prevents Plink (or PuTTY) from attempting to start + a shell or command on the remote server. Instead, it will instruct + the remote server to open a network connection to a host name and + port number specified by you, and treat that network connection as + if it were the main session. + + You specify a host and port as an argument to the `-nc' option, with + a colon separating the host name from the port number, like this: + + plink host1.example.com -nc host2.example.com:1234 + + You might want to use this feature if you needed to make an SSH + connection to a target host which you can only reach by going + through a proxy host, and rather than using port forwarding you + prefer to use the local proxy feature (see section 4.16.1 for more + about local proxies). In this situation you might select `Local' + proxy type, set your local proxy command to be `plink %proxyhost - + nc %host:%port', enter the target host name on the Session panel, + and enter the directly reachable proxy host name on the Proxy panel. + + This feature is only available in SSH protocol version 2 (since the + version 1 protocol assumes you will always want to run a shell). It + is not available in the file transfer tools PSCP and PSFTP. It is + available in PuTTY itself, although it is unlikely to be very useful + in any tool other than Plink. Also, `-nc' uses the same server + functionality as port forwarding, so it will not work if your server + administrator has disabled port forwarding. + + (The option is named `-nc' after the Unix program `nc', short for + `netcat'. The command `plink host1 -nc host2:port' is very similar + in functionality to `plink host1 nc host2 port', which invokes `nc' + on the server and tells it to connect to the specified destination. + However, Plink's built-in `-nc' option does not depend on the `nc' + program being installed on the server.) + +3.8.3.15 `-C': enable compression + + The `-C' option enables compression of the data sent across the + network. This option is only meaningful if you are using SSH. + + This option is equivalent to the `Enable compression' checkbox in + the SSH panel of the PuTTY configuration box (see section 4.19.3). + +3.8.3.16 `-1' and `-2': specify an SSH protocol version + + The `-1' and `-2' options force PuTTY to use version 1 or version 2 + of the SSH protocol. These options are only meaningful if you are + using SSH. + + These options are equivalent to selecting the SSH protocol version + in the SSH panel of the PuTTY configuration box (see section + 4.19.4). + +3.8.3.17 `-4' and `-6': specify an Internet protocol version + + The `-4' and `-6' options force PuTTY to use the older Internet + protocol IPv4 or the newer IPv6 for most outgoing connections. + + These options are equivalent to selecting your preferred Internet + protocol version as `IPv4' or `IPv6' in the Connection panel of the + PuTTY configuration box (see section 4.14.4). + +3.8.3.18 `-i': specify an SSH private key + + The `-i' option allows you to specify the name of a private key file + in `*.PPK' format which PuTTY will use to authenticate with the + server. This option is only meaningful if you are using SSH. + + If you are using Pageant, you can also specify a _public_ key file + (in RFC 4716 or OpenSSH format) to identify a specific key file to + use. (This won't work if you're not running Pageant, of course.) + + For general information on public-key authentication, see chapter 8. + + This option is equivalent to the `Private key file for + authentication' box in the Auth panel of the PuTTY configuration box + (see section 4.23.8). + +3.8.3.19 `-loghost': specify a logical host name + + This option overrides PuTTY's normal SSH host key caching policy by + telling it the name of the host you expect your connection to end up + at (in cases where this differs from the location PuTTY thinks it's + connecting to). It can be a plain host name, or a host name followed + by a colon and a port number. See section 4.14.5 for more detail on + this. + +3.8.3.20 `-hostkey': manually specify an expected host key + + This option overrides PuTTY's normal SSH host key caching policy + by telling it exactly what host key to expect, which can be + useful if the normal automatic host key store in the Registry is + unavailable. The argument to this option should be either a host key + fingerprint, or an SSH-2 public key blob. See section 4.21.2 for + more information. + + You can specify this option more than once if you want to configure + more than one key to be accepted. + +3.8.3.21 `-pgpfp': display PGP key fingerprints + + This option causes the PuTTY tools not to run as normal, but instead + to display the fingerprints of the PuTTY PGP Master Keys, in + order to aid with verifying new versions. See appendix E for more + information. + +3.8.3.22 `-sercfg': specify serial port configuration + + This option specifies the configuration parameters for the serial + port (baud rate, stop bits etc). Its argument is interpreted as + a comma-separated list of configuration options, which can be as + follows: + + - Any single digit from 5 to 9 sets the number of data bits. + + - `1', `1.5' or `2' sets the number of stop bits. + + - Any other numeric string is interpreted as a baud rate. + + - A single lower-case letter specifies the parity: `n' for none, + `o' for odd, `e' for even, `m' for mark and `s' for space. + + - A single upper-case letter specifies the flow control: `N' for + none, `X' for XON/XOFF, `R' for RTS/CTS and `D' for DSR/DTR. + + For example, `-sercfg 19200,8,n,1,N' denotes a baud rate of 19200, 8 + data bits, no parity, 1 stop bit and no flow control. + +3.8.3.23 `-sessionlog', `-sshlog', `-sshrawlog': specify session logging + + These options cause the PuTTY network tools to write out a log + file. Each of them expects a file name as an argument, e.g. `- + sshlog putty.log' causes an SSH packet log to be written to a file + called `putty.log'. The three different options select different + logging modes, all available from the GUI too: + + - `-sessionlog' selects `All session output' logging mode. + + - `-sshlog' selects `SSH packets' logging mode. + + - `-sshrawlog' selects `SSH packets and raw data' logging mode. + + For more information on logging configuration, see section 4.2. + +3.8.3.24 `-proxycmd': specify a local proxy command + + This option enables PuTTY's mode for running a command on the local + machine and using it as a proxy for the network connection. It + expects a shell command string as an argument. + + See section 4.16.1 for more information on this, and on other proxy + settings. In particular, note that since the special sequences + described there are understood in the argument string, literal + backslashes must be doubled (if you want `\' in your command, you + must put `\\' on the command line). + +3.8.3.25 `-restrict-acl': restrict the Windows process ACL + + This option (on Windows only) causes PuTTY (or another PuTTY tool) + to try to lock down the operating system's access control on its own + process. If this succeeds, it should present an extra obstacle to + malware that has managed to run under the same user id as the PuTTY + process, by preventing it from attaching to PuTTY using the same + interfaces debuggers use and either reading sensitive information + out of its memory or hijacking its network session. + + This option is not enabled by default, because this form of + interaction between Windows programs has many legitimate uses, + including accessibility software such as screen readers. Also, + it cannot provide full security against this class of attack in + any case, because PuTTY can only lock down its own ACL _after_ it + has started up, and malware could still get in if it attacks the + process between startup and lockdown. So it trades away noticeable + convenience, and delivers less real security than you might want. + However, if you do want to make that tradeoff anyway, the option is + available. + + A PuTTY process started with `-restrict-acl' will pass that on to + any processes started with Duplicate Session, New Session etc. + (However, if you're invoking PuTTY tools explicitly, for instance as + a proxy command, you'll need to arrange to pass them the `-restrict- + acl' option yourself, if that's what you want.) + + If Pageant is started with the `-restrict-acl' option, and you use + it to launch a PuTTY session from its System Tray submenu, then + Pageant will _not_ default to starting the PuTTY subprocess with + a restricted ACL. This is because PuTTY is more likely to suffer + reduced functionality as a result of restricted ACLs (e.g. screen + reader software will have a greater need to interact with it), + whereas Pageant stores the more critical information (hence benefits + more from the extra protection), so it's reasonable to want to run + Pageant but not PuTTY with the ACL restrictions. You can force + Pageant to start subsidiary PuTTY processes with a restricted ACL if + you also pass the `-restrict-putty-acl' option. + +Chapter 4: Configuring PuTTY +---------------------------- + + This chapter describes all the configuration options in PuTTY. + + PuTTY is configured using the control panel that comes up before you + start a session. Some options can also be changed in the middle of a + session, by selecting `Change Settings' from the window menu. + + 4.1 The Session panel + + The Session configuration panel contains the basic options you need + to specify in order to open a session at all, and also allows you to + save your settings to be reloaded later. + + 4.1.1 The host name section + + The top box on the Session panel, labelled `Specify your connection + by host name', contains the details that need to be filled in before + PuTTY can open a session at all. + + - The `Host Name' box is where you type the name, or the IP + address, of the server you want to connect to. + + - The `Connection type' radio buttons let you choose what type + of connection you want to make: a raw connection, a Telnet + connection, an Rlogin connection, an SSH connection, or a + connection to a local serial line. (See section 1.2 for a + summary of the differences between SSH, Telnet and rlogin; see + section 3.6 for an explanation of `raw' connections; see section + 3.7 for information about using a serial line.) + + - The `Port' box lets you specify which port number on the server + to connect to. If you select Telnet, Rlogin, or SSH, this box + will be filled in automatically to the usual value, and you will + only need to change it if you have an unusual server. If you + select Raw mode, you will almost certainly need to fill in the + `Port' box yourself. + + If you select `Serial' from the `Connection type' radio buttons, + the `Host Name' and `Port' boxes are replaced by `Serial line' and + `Speed'; see section 4.29 for more details of these. + + 4.1.2 Loading and storing saved sessions + + The next part of the Session configuration panel allows you to save + your preferred PuTTY options so they will appear automatically the + next time you start PuTTY. It also allows you to create _saved + sessions_, which contain a full set of configuration options plus a + host name and protocol. A saved session contains all the information + PuTTY needs to start exactly the session you want. + + - To save your default settings: first set up the settings the way + you want them saved. Then come back to the Session panel. Select + the `Default Settings' entry in the saved sessions list, with a + single click. Then press the `Save' button. + + If there is a specific host you want to store the details of how + to connect to, you should create a saved session, which will be + separate from the Default Settings. + + - To save a session: first go through the rest of the + configuration box setting up all the options you want. Then come + back to the Session panel. Enter a name for the saved session in + the `Saved Sessions' input box. (The server name is often a good + choice for a saved session name.) Then press the `Save' button. + Your saved session name should now appear in the list box. + + You can also save settings in mid-session, from the `Change + Settings' dialog. Settings changed since the start of the + session will be saved with their current values; as well as + settings changed through the dialog, this includes changes in + window size, window title changes sent by the server, and so on. + + - To reload a saved session: single-click to select the session + name in the list box, and then press the `Load' button. Your + saved settings should all appear in the configuration panel. + + - To modify a saved session: first load it as described above. + Then make the changes you want. Come back to the Session panel, + and press the `Save' button. The new settings will be saved over + the top of the old ones. + + To save the new settings under a different name, you can enter + the new name in the `Saved Sessions' box, or single-click to + select a session name in the list box to overwrite that session. + To save `Default Settings', you must single-click the name + before saving. + + - To start a saved session immediately: double-click on the + session name in the list box. + + - To delete a saved session: single-click to select the session + name in the list box, and then press the `Delete' button. + + Each saved session is independent of the Default Settings + configuration. If you change your preferences and update Default + Settings, you must also update every saved session separately. + + Saved sessions are stored in the Registry, at the location + + HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions + + If you need to store them in a file, you could try the method + described in section 4.30. + + 4.1.3 `Close window on exit' + + Finally in the Session panel, there is an option labelled `Close + window on exit'. This controls whether the PuTTY terminal window + disappears as soon as the session inside it terminates. If you are + likely to want to copy and paste text out of the session after it + has terminated, or restart the session, you should arrange for this + option to be off. + + `Close window on exit' has three settings. `Always' means always + close the window on exit; `Never' means never close on exit (always + leave the window open, but inactive). The third setting, and the + default one, is `Only on clean exit'. In this mode, a session which + terminates normally will cause its window to close, but one which is + aborted unexpectedly by network trouble or a confusing message from + the server will leave the window up. + + 4.2 The Logging panel + + The Logging configuration panel allows you to save log files of your + PuTTY sessions, for debugging, analysis or future reference. + + The main option is a radio-button set that specifies whether PuTTY + will log anything at all. The options are: + + - `None'. This is the default option; in this mode PuTTY will not + create a log file at all. + + - `Printable output'. In this mode, a log file will be created + and written to, but only printable text will be saved into it. + The various terminal control codes that are typically sent down + an interactive session alongside the printable text will be + omitted. This might be a useful mode if you want to read a log + file in a text editor and hope to be able to make sense of it. + + - `All session output'. In this mode, _everything_ sent by the + server into your terminal session is logged. If you view the log + file in a text editor, therefore, you may well find it full of + strange control characters. This is a particularly useful mode + if you are experiencing problems with PuTTY's terminal handling: + you can record everything that went to the terminal, so that + someone else can replay the session later in slow motion and + watch to see what went wrong. + + - `SSH packets'. In this mode (which is only used by SSH + connections), the SSH message packets sent over the encrypted + connection are written to the log file (as well as Event Log + entries). You might need this to debug a network-level problem, + or more likely to send to the PuTTY authors as part of a bug + report. _BE WARNED_ that if you log in using a password, the + password can appear in the log file; see section 4.2.5 for + options that may help to remove sensitive material from the log + file before you send it to anyone else. + + - `SSH packets and raw data'. In this mode, as well as the + decrypted packets (as in the previous mode), the _raw_ + (encrypted, compressed, etc) packets are _also_ logged. This + could be useful to diagnose corruption in transit. (The same + caveats as the previous mode apply, of course.) + + Note that the non-SSH logging options (`Printable output' and `All + session output') only work with PuTTY proper; in programs without + terminal emulation (such as Plink), they will have no effect, even + if enabled via saved settings. + + 4.2.1 `Log file name' + + In this edit box you enter the name of the file you want to log the + session to. The `Browse' button will let you look around your file + system to find the right place to put the file; or if you already + know exactly where you want it to go, you can just type a pathname + into the edit box. + + There are a few special features in this box. If you use the `&' + character in the file name box, PuTTY will insert details of the + current session in the name of the file it actually opens. The + precise replacements it will do are: + + - `&Y' will be replaced by the current year, as four digits. + + - `&M' will be replaced by the current month, as two digits. + + - `&D' will be replaced by the current day of the month, as two + digits. + + - `&T' will be replaced by the current time, as six digits + (HHMMSS) with no punctuation. + + - `&H' will be replaced by the host name you are connecting to. + + - `&P' will be replaced by the port number you are connecting to + on the target host. + + For example, if you enter the host name `c:\puttylogs\log-&h-&y&m&d- + &t.dat', you will end up with files looking like + + log-server1.example.com-20010528-110859.dat + log-unixbox.somewhere.org-20010611-221001.dat + + 4.2.2 `What to do if the log file already exists' + + This control allows you to specify what PuTTY should do if it tries + to start writing to a log file and it finds the file already exists. + You might want to automatically destroy the existing log file and + start a new one with the same name. Alternatively, you might want to + open the existing log file and add data to the _end_ of it. Finally + (the default option), you might not want to have any automatic + behaviour, but to ask the user every time the problem comes up. + + 4.2.3 `Flush log file frequently' + + This option allows you to control how frequently logged data is + flushed to disc. By default, PuTTY will flush data as soon as it + is displayed, so that if you view the log file while a session is + still open, it will be up to date; and if the client system crashes, + there's a greater chance that the data will be preserved. + + However, this can incur a performance penalty. If PuTTY is running + slowly with logging enabled, you could try unchecking this option. + Be warned that the log file may not always be up to date as a result + (although it will of course be flushed when it is closed, for + instance at the end of a session). + + 4.2.4 `Include header' + + This option allows you to choose whether to include a header line + with the date and time when the log file is opened. It may be useful + to disable this if the log file is being used as realtime input to + other programs that don't expect the header line. + + 4.2.5 Options specific to SSH packet logging + + These options only apply if SSH packet data is being logged. + + The following options allow particularly sensitive portions of + unencrypted packets to be automatically left out of the log file. + They are only intended to deter casual nosiness; an attacker could + glean a lot of useful information from even these obfuscated logs + (e.g., length of password). + +4.2.5.1 `Omit known password fields' + + When checked, decrypted password fields are removed from the log of + transmitted packets. (This includes any user responses to challenge- + response authentication methods such as `keyboard-interactive'.) + This does not include X11 authentication data if using X11 + forwarding. + + Note that this will only omit data that PuTTY _knows_ to be a + password. However, if you start another login session within your + PuTTY session, for instance, any password used will appear in the + clear in the packet log. The next option may be of use to protect + against this. + + This option is enabled by default. + +4.2.5.2 `Omit session data' + + When checked, all decrypted `session data' is omitted; this is + defined as data in terminal sessions and in forwarded channels (TCP, + X11, and authentication agent). This will usually substantially + reduce the size of the resulting log file. + + This option is disabled by default. + + 4.3 The Terminal panel + + The Terminal configuration panel allows you to control the behaviour + of PuTTY's terminal emulation. + + 4.3.1 `Auto wrap mode initially on' + + Auto wrap mode controls what happens when text printed in a PuTTY + window reaches the right-hand edge of the window. + + With auto wrap mode on, if a long line of text reaches the right- + hand edge, it will wrap over on to the next line so you can still + see all the text. With auto wrap mode off, the cursor will stay at + the right-hand edge of the screen, and all the characters in the + line will be printed on top of each other. + + If you are running a full-screen application and you occasionally + find the screen scrolling up when it looks as if it shouldn't, you + could try turning this option off. + + Auto wrap mode can be turned on and off by control sequences sent by + the server. This configuration option controls the _default_ state, + which will be restored when you reset the terminal (see section + 3.1.3.6). However, if you modify this option in mid-session using + `Change Settings', it will take effect immediately. + + 4.3.2 `DEC Origin Mode initially on' + + DEC Origin Mode is a minor option which controls how PuTTY + interprets cursor-position control sequences sent by the server. + + The server can send a control sequence that restricts the scrolling + region of the display. For example, in an editor, the server might + reserve a line at the top of the screen and a line at the bottom, + and might send a control sequence that causes scrolling operations + to affect only the remaining lines. + + With DEC Origin Mode on, cursor coordinates are counted from the top + of the scrolling region. With it turned off, cursor coordinates are + counted from the top of the whole screen regardless of the scrolling + region. + + It is unlikely you would need to change this option, but if you find + a full-screen application is displaying pieces of text in what looks + like the wrong part of the screen, you could try turning DEC Origin + Mode on to see whether that helps. + + DEC Origin Mode can be turned on and off by control sequences sent + by the server. This configuration option controls the _default_ + state, which will be restored when you reset the terminal (see + section 3.1.3.6). However, if you modify this option in mid-session + using `Change Settings', it will take effect immediately. + + 4.3.3 `Implicit CR in every LF' + + Most servers send two control characters, CR and LF, to start a new + line of the screen. The CR character makes the cursor return to the + left-hand side of the screen. The LF character makes the cursor move + one line down (and might make the screen scroll). + + Some servers only send LF, and expect the terminal to move the + cursor over to the left automatically. If you come across a server + that does this, you will see a stepped effect on the screen, like + this: + + First line of text + Second line + Third line + + If this happens to you, try enabling the `Implicit CR in every LF' + option, and things might go back to normal: + + First line of text + Second line + Third line + + 4.3.4 `Implicit LF in every CR' + + Most servers send two control characters, CR and LF, to start a new + line of the screen. The CR character makes the cursor return to the + left-hand side of the screen. The LF character makes the cursor move + one line down (and might make the screen scroll). + + Some servers only send CR, and so the newly written line is + overwritten by the following line. This option causes a line feed so + that all lines are displayed. + + 4.3.5 `Use background colour to erase screen' + + Not all terminals agree on what colour to turn the screen when the + server sends a `clear screen' sequence. Some terminals believe the + screen should always be cleared to the _default_ background colour. + Others believe the screen should be cleared to whatever the server + has selected as a background colour. + + There exist applications that expect both kinds of behaviour. + Therefore, PuTTY can be configured to do either. + + With this option disabled, screen clearing is always done in the + default background colour. With this option enabled, it is done in + the _current_ background colour. + + Background-colour erase can be turned on and off by control + sequences sent by the server. This configuration option controls the + _default_ state, which will be restored when you reset the terminal + (see section 3.1.3.6). However, if you modify this option in mid- + session using `Change Settings', it will take effect immediately. + + 4.3.6 `Enable blinking text' + + The server can ask PuTTY to display text that blinks on and off. + This is very distracting, so PuTTY allows you to turn blinking text + off completely. + + When blinking text is disabled and the server attempts to make + some text blink, PuTTY will instead display the text with a bolded + background colour. + + Blinking text can be turned on and off by control sequences sent by + the server. This configuration option controls the _default_ state, + which will be restored when you reset the terminal (see section + 3.1.3.6). However, if you modify this option in mid-session using + `Change Settings', it will take effect immediately. + + 4.3.7 `Answerback to ^E' + + This option controls what PuTTY will send back to the server if the + server sends it the ^E enquiry character. Normally it just sends the + string `PuTTY'. + + If you accidentally write the contents of a binary file to your + terminal, you will probably find that it contains more than one ^E + character, and as a result your next command line will probably + read `PuTTYPuTTYPuTTY...' as if you had typed the answerback string + multiple times at the keyboard. If you set the answerback string + to be empty, this problem should go away, but doing so might cause + other problems. + + Note that this is _not_ the feature of PuTTY which the server will + typically use to determine your terminal type. That feature is the + `Terminal-type string' in the Connection panel; see section 4.15.3 + for details. + + You can include control characters in the answerback string using + `^C' notation. (Use `^~' to get a literal `^'.) + + 4.3.8 `Local echo' + + With local echo disabled, characters you type into the PuTTY window + are not echoed in the window _by PuTTY_. They are simply sent to the + server. (The _server_ might choose to echo them back to you; this + can't be controlled from the PuTTY control panel.) + + Some types of session need local echo, and many do not. In its + default mode, PuTTY will automatically attempt to deduce whether + or not local echo is appropriate for the session you are working + in. If you find it has made the wrong decision, you can use this + configuration option to override its choice: you can force local + echo to be turned on, or force it to be turned off, instead of + relying on the automatic detection. + + 4.3.9 `Local line editing' + + Normally, every character you type into the PuTTY window is sent + immediately to the server the moment you type it. + + If you enable local line editing, this changes. PuTTY will let you + edit a whole line at a time locally, and the line will only be sent + to the server when you press Return. If you make a mistake, you can + use the Backspace key to correct it before you press Return, and the + server will never see the mistake. + + Since it is hard to edit a line locally without being able to see + it, local line editing is mostly used in conjunction with local echo + (section 4.3.8). This makes it ideal for use in raw mode or when + connecting to MUDs or talkers. (Although some more advanced MUDs do + occasionally turn local line editing on and turn local echo off, in + order to accept a password from the user.) + + Some types of session need local line editing, and many do not. In + its default mode, PuTTY will automatically attempt to deduce whether + or not local line editing is appropriate for the session you are + working in. If you find it has made the wrong decision, you can use + this configuration option to override its choice: you can force + local line editing to be turned on, or force it to be turned off, + instead of relying on the automatic detection. + +4.3.10 Remote-controlled printing + + A lot of VT100-compatible terminals support printing under control + of the remote server (sometimes called `passthrough printing'). + PuTTY supports this feature as well, but it is turned off by + default. + + To enable remote-controlled printing, choose a printer from + the `Printer to send ANSI printer output to' drop-down list + box. This should allow you to select from all the printers you + have installed drivers for on your computer. Alternatively, you + can type the network name of a networked printer (for example, + `\\printserver\printer1') even if you haven't already installed a + driver for it on your own machine. + + When the remote server attempts to print some data, PuTTY will send + that data to the printer _raw_ - without translating it, attempting + to format it, or doing anything else to it. It is up to you to + ensure your remote server knows what type of printer it is talking + to. + + Since PuTTY sends data to the printer raw, it cannot offer options + such as portrait versus landscape, print quality, or paper tray + selection. All these things would be done by your PC printer driver + (which PuTTY bypasses); if you need them done, you will have to find + a way to configure your remote server to do them. + + To disable remote printing again, choose `None (printing disabled)' + from the printer selection list. This is the default state. + + 4.4 The Keyboard panel + + The Keyboard configuration panel allows you to control the behaviour + of the keyboard in PuTTY. The correct state for many of these + settings depends on what the server to which PuTTY is connecting + expects. With a Unix server, this is likely to depend on the + `termcap' or `terminfo' entry it uses, which in turn is likely to be + controlled by the `Terminal-type string' setting in the Connection + panel; see section 4.15.3 for details. If none of the settings here + seems to help, you may find question A.7.13 to be useful. + + 4.4.1 Changing the action of the Backspace key + + Some terminals believe that the Backspace key should send the same + thing to the server as Control-H (ASCII code 8). Other terminals + believe that the Backspace key should send ASCII code 127 (usually + known as Control-?) so that it can be distinguished from Control-H. + This option allows you to choose which code PuTTY generates when you + press Backspace. + + If you are connecting over SSH, PuTTY by default tells the server + the value of this option (see section 4.25.2), so you may find that + the Backspace key does the right thing either way. Similarly, if + you are connecting to a Unix system, you will probably find that + the Unix `stty' command lets you configure which the server expects + to see, so again you might not need to change which one PuTTY + generates. On other systems, the server's expectation might be fixed + and you might have no choice but to configure PuTTY. + + If you do have the choice, we recommend configuring PuTTY to + generate Control-? and configuring the server to expect it, because + that allows applications such as `emacs' to use Control-H for help. + + (Typing Shift-Backspace will cause PuTTY to send whichever code + isn't configured here as the default.) + + 4.4.2 Changing the action of the Home and End keys + + The Unix terminal emulator `rxvt' disagrees with the rest of the + world about what character sequences should be sent to the server by + the Home and End keys. + + `xterm', and other terminals, send `ESC [1~' for the Home key, and + `ESC [4~' for the End key. `rxvt' sends `ESC [H' for the Home key + and `ESC [Ow' for the End key. + + If you find an application on which the Home and End keys aren't + working, you could try switching this option to see if it helps. + + 4.4.3 Changing the action of the function keys and keypad + + This option affects the function keys (F1 to F12) and the top row of + the numeric keypad. + + - In the default mode, labelled `ESC [n~', the function keys + generate sequences like `ESC [11~', `ESC [12~' and so on. This + matches the general behaviour of Digital's terminals. + + - In Linux mode, F6 to F12 behave just like the default mode, but + F1 to F5 generate `ESC [[A' through to `ESC [[E'. This mimics + the Linux virtual console. + + - In Xterm R6 mode, F5 to F12 behave like the default mode, but + F1 to F4 generate `ESC OP' through to `ESC OS', which are the + sequences produced by the top row of the _keypad_ on Digital's + terminals. + + - In VT400 mode, all the function keys behave like the default + mode, but the actual top row of the numeric keypad generates + `ESC OP' through to `ESC OS'. + + - In VT100+ mode, the function keys generate `ESC OP' through to + `ESC O[' + + - In SCO mode, the function keys F1 to F12 generate `ESC [M' + through to `ESC [X'. Together with shift, they generate `ESC [Y' + through to `ESC [j'. With control they generate `ESC [k' through + to `ESC [v', and with shift and control together they generate + `ESC [w' through to `ESC [{'. + + If you don't know what any of this means, you probably don't need to + fiddle with it. + + 4.4.4 Controlling Application Cursor Keys mode + + Application Cursor Keys mode is a way for the server to change the + control sequences sent by the arrow keys. In normal mode, the arrow + keys send `ESC [A' through to `ESC [D'. In application mode, they + send `ESC OA' through to `ESC OD'. + + Application Cursor Keys mode can be turned on and off by the server, + depending on the application. PuTTY allows you to configure the + initial state. + + You can also disable application cursor keys mode completely, using + the `Features' configuration panel; see section 4.6.1. + + 4.4.5 Controlling Application Keypad mode + + Application Keypad mode is a way for the server to change the + behaviour of the numeric keypad. + + In normal mode, the keypad behaves like a normal Windows keypad: + with NumLock on, the number keys generate numbers, and with NumLock + off they act like the arrow keys and Home, End etc. + + In application mode, all the keypad keys send special control + sequences, _including_ Num Lock. Num Lock stops behaving like Num + Lock and becomes another function key. + + Depending on which version of Windows you run, you may find the Num + Lock light still flashes on and off every time you press Num Lock, + even when application mode is active and Num Lock is acting like a + function key. This is unavoidable. + + Application keypad mode can be turned on and off by the server, + depending on the application. PuTTY allows you to configure the + initial state. + + You can also disable application keypad mode completely, using the + `Features' configuration panel; see section 4.6.1. + + 4.4.6 Using NetHack keypad mode + + PuTTY has a special mode for playing NetHack. You can enable it + by selecting `NetHack' in the `Initial state of numeric keypad' + control. + + In this mode, the numeric keypad keys 1-9 generate the NetHack + movement commands (hjklyubn). The 5 key generates the `.' command + (do nothing). + + In addition, pressing Shift or Ctrl with the keypad keys generate + the Shift- or Ctrl-keys you would expect (e.g. keypad-7 generates + `y', so Shift-keypad-7 generates `Y' and Ctrl-keypad-7 generates + Ctrl-Y); these commands tell NetHack to keep moving you in the same + direction until you encounter something interesting. + + For some reason, this feature only works properly when Num Lock is + on. We don't know why. + + 4.4.7 Enabling a DEC-like Compose key + + DEC terminals have a Compose key, which provides an easy-to-remember + way of typing accented characters. You press Compose and then type + two more characters. The two characters are `combined' to produce + an accented character. The choices of character are designed to be + easy to remember; for example, composing `e' and ``' produces the + `e-grave' character. + + If your keyboard has a Windows Application key, it acts as a Compose + key in PuTTY. Alternatively, if you enable the `AltGr acts as + Compose key' option, the AltGr key will become a Compose key. + + 4.4.8 `Control-Alt is different from AltGr' + + Some old keyboards do not have an AltGr key, which can make it + difficult to type some characters. PuTTY can be configured to treat + the key combination Ctrl + Left Alt the same way as the AltGr key. + + By default, this checkbox is checked, and the key combination Ctrl + + Left Alt does something completely different. PuTTY's usual handling + of the left Alt key is to prefix the Escape (Control-[) character to + whatever character sequence the rest of the keypress would generate. + For example, Alt-A generates Escape followed by `a'. So Alt-Ctrl-A + would generate Escape, followed by Control-A. + + If you uncheck this box, Ctrl-Alt will become a synonym for AltGr, + so you can use it to type extra graphic characters if your keyboard + has any. + + (However, Ctrl-Alt will never act as a Compose key, regardless of + the setting of `AltGr acts as Compose key' described in section + 4.4.7.) + + 4.5 The Bell panel + + The Bell panel controls the terminal bell feature: the server's + ability to cause PuTTY to beep at you. + + In the default configuration, when the server sends the character + with ASCII code 7 (Control-G), PuTTY will play the Windows Default + Beep sound. This is not always what you want the terminal bell + feature to do; the Bell panel allows you to configure alternative + actions. + + 4.5.1 `Set the style of bell' + + This control allows you to select various different actions to occur + on a terminal bell: + + - Selecting `None' disables the bell completely. In this mode, the + server can send as many Control-G characters as it likes and + nothing at all will happen. + + - `Make default system alert sound' is the default setting. + It causes the Windows `Default Beep' sound to be played. To + change what this sound is, or to test it if nothing seems to + be happening, use the Sound configurer in the Windows Control + Panel. + + - `Visual bell' is a silent alternative to a beeping computer. In + this mode, when the server sends a Control-G, the whole PuTTY + window will flash white for a fraction of a second. + + - `Beep using the PC speaker' is self-explanatory. + + - `Play a custom sound file' allows you to specify a particular + sound file to be used by PuTTY alone, or even by a particular + individual PuTTY session. This allows you to distinguish your + PuTTY beeps from any other beeps on the system. If you select + this option, you will also need to enter the name of your sound + file in the edit control `Custom sound file to play as a bell'. + + 4.5.2 `Taskbar/caption indication on bell' + + This feature controls what happens to the PuTTY window's entry in + the Windows Taskbar if a bell occurs while the window does not have + the input focus. + + In the default state (`Disabled') nothing unusual happens. + + If you select `Steady', then when a bell occurs and the window is + not in focus, the window's Taskbar entry and its title bar will + change colour to let you know that PuTTY session is asking for your + attention. The change of colour will persist until you select the + window, so you can leave several PuTTY windows minimised in your + terminal, go away from your keyboard, and be sure not to have missed + any important beeps when you get back. + + `Flashing' is even more eye-catching: the Taskbar entry will + continuously flash on and off until you select the window. + + 4.5.3 `Control the bell overload behaviour' + + A common user error in a terminal session is to accidentally run the + Unix command `cat' (or equivalent) on an inappropriate file type, + such as an executable, image file, or ZIP file. This produces a huge + stream of non-text characters sent to the terminal, which typically + includes a lot of bell characters. As a result of this the terminal + often doesn't stop beeping for ten minutes, and everybody else in + the office gets annoyed. + + To try to avoid this behaviour, or any other cause of excessive + beeping, PuTTY includes a bell overload management feature. In the + default configuration, receiving more than five bell characters in a + two-second period will cause the overload feature to activate. Once + the overload feature is active, further bells will have no effect + at all, so the rest of your binary file will be sent to the screen + in silence. After a period of five seconds during which no further + bells are received, the overload feature will turn itself off again + and bells will be re-enabled. + + If you want this feature completely disabled, you can turn it off + using the checkbox `Bell is temporarily disabled when over-used'. + + Alternatively, if you like the bell overload feature but don't + agree with the settings, you can configure the details: how many + bells constitute an overload, how short a time period they have to + arrive in to do so, and how much silent time is required before the + overload feature will deactivate itself. + + Bell overload mode is always deactivated by any keypress in the + terminal. This means it can respond to large unexpected streams of + data, but does not interfere with ordinary command-line activities + that generate beeps (such as filename completion). + + 4.6 The Features panel + + PuTTY's terminal emulation is very highly featured, and can do a + lot of things under remote server control. Some of these features + can cause problems due to buggy or strangely configured server + applications. + + The Features configuration panel allows you to disable some of + PuTTY's more advanced terminal features, in case they cause trouble. + + 4.6.1 Disabling application keypad and cursor keys + + Application keypad mode (see section 4.4.5) and application cursor + keys mode (see section 4.4.4) alter the behaviour of the keypad and + cursor keys. Some applications enable these modes but then do not + deal correctly with the modified keys. You can force these modes to + be permanently disabled no matter what the server tries to do. + + 4.6.2 Disabling xterm-style mouse reporting + + PuTTY allows the server to send control codes that let it take + over the mouse and use it for purposes other than copy and paste. + Applications which use this feature include the text-mode web + browser `links', the Usenet newsreader `trn' version 4, and the file + manager `mc' (Midnight Commander). + + If you find this feature inconvenient, you can disable it using the + `Disable xterm-style mouse reporting' control. With this box ticked, + the mouse will _always_ do copy and paste in the normal way. + + Note that even if the application takes over the mouse, you can + still manage PuTTY's copy and paste by holding down the Shift key + while you select and paste, unless you have deliberately turned this + feature off (see section 4.11.2). + + 4.6.3 Disabling remote terminal resizing + + PuTTY has the ability to change the terminal's size and position in + response to commands from the server. If you find PuTTY is doing + this unexpectedly or inconveniently, you can tell PuTTY not to + respond to those server commands. + + 4.6.4 Disabling switching to the alternate screen + + Many terminals, including PuTTY, support an `alternate screen'. This + is the same size as the ordinary terminal screen, but separate. + Typically a screen-based program such as a text editor might switch + the terminal to the alternate screen before starting up. Then at the + end of the run, it switches back to the primary screen, and you see + the screen contents just as they were before starting the editor. + + Some people prefer this not to happen. If you want your editor to + run in the same screen as the rest of your terminal activity, you + can disable the alternate screen feature completely. + + 4.6.5 Disabling remote window title changing + + PuTTY has the ability to change the window title in response + to commands from the server. If you find PuTTY is doing this + unexpectedly or inconveniently, you can tell PuTTY not to respond to + those server commands. + + 4.6.6 Response to remote window title querying + + PuTTY can optionally provide the xterm service of allowing server + applications to find out the local window title. This feature is + disabled by default, but you can turn it on if you really want it. + + NOTE that this feature is a _potential security hazard_. If a + malicious application can write data to your terminal (for example, + if you merely `cat' a file owned by someone else on the server + machine), it can change your window title (unless you have disabled + this as mentioned in section 4.6.5) and then use this service to + have the new window title sent back to the server as if typed at the + keyboard. This allows an attacker to fake keypresses and potentially + cause your server-side applications to do things you didn't want. + Therefore this feature is disabled by default, and we recommend you + do not set it to `Window title' unless you _really_ know what you + are doing. + + There are three settings for this option: + + `None' + + PuTTY makes no response whatsoever to the relevant escape + sequence. This may upset server-side software that is expecting + some sort of response. + + `Empty string' + + PuTTY makes a well-formed response, but leaves it blank. Thus, + server-side software that expects a response is kept happy, + but an attacker cannot influence the response string. This is + probably the setting you want if you have no better ideas. + + `Window title' + + PuTTY responds with the actual window title. This is dangerous + for the reasons described above. + + 4.6.7 Disabling remote scrollback clearing + + PuTTY has the ability to clear the terminal's scrollback buffer in + response to a command from the server. If you find PuTTY is doing + this unexpectedly or inconveniently, you can tell PuTTY not to + respond to that server command. + + 4.6.8 Disabling destructive backspace + + Normally, when PuTTY receives character 127 (^?) from the server, + it will perform a `destructive backspace': move the cursor one + space left and delete the character under it. This can apparently + cause problems in some applications, so PuTTY provides the ability + to configure character 127 to perform a normal backspace (without + deleting a character) instead. + + 4.6.9 Disabling remote character set configuration + + PuTTY has the ability to change its character set configuration + in response to commands from the server. Some programs send these + commands unexpectedly or inconveniently. In particular, BitchX (an + IRC client) seems to have a habit of reconfiguring the character set + to something other than the user intended. + + If you find that accented characters are not showing up the way you + expect them to, particularly if you're running BitchX, you could try + disabling the remote character set configuration commands. + +4.6.10 Disabling Arabic text shaping + + PuTTY supports shaping of Arabic text, which means that if your + server sends text written in the basic Unicode Arabic alphabet then + it will convert it to the correct display forms before printing it + on the screen. + + If you are using full-screen software which was not expecting + this to happen (especially if you are not an Arabic speaker and + you unexpectedly find yourself dealing with Arabic text files in + applications which are not Arabic-aware), you might find that the + display becomes corrupted. By ticking this box, you can disable + Arabic text shaping so that PuTTY displays precisely the characters + it is told to display. + + You may also find you need to disable bidirectional text display; + see section 4.6.11. + +4.6.11 Disabling bidirectional text display + + PuTTY supports bidirectional text display, which means that if your + server sends text written in a language which is usually displayed + from right to left (such as Arabic or Hebrew) then PuTTY will + automatically flip it round so that it is displayed in the right + direction on the screen. + + If you are using full-screen software which was not expecting + this to happen (especially if you are not an Arabic speaker and + you unexpectedly find yourself dealing with Arabic text files in + applications which are not Arabic-aware), you might find that the + display becomes corrupted. By ticking this box, you can disable + bidirectional text display, so that PuTTY displays text from left to + right in all situations. + + You may also find you need to disable Arabic text shaping; see + section 4.6.10. + + 4.7 The Window panel + + The Window configuration panel allows you to control aspects of the + PuTTY window. + + 4.7.1 Setting the size of the PuTTY window + + The `Columns' and `Rows' boxes let you set the PuTTY window to a + precise size. Of course you can also drag the window to a new size + while a session is running. + + 4.7.2 What to do when the window is resized + + These options allow you to control what happens when the user tries + to resize the PuTTY window using its window furniture. + + There are four options here: + + - `Change the number of rows and columns': the font size will not + change. (This is the default.) + + - `Change the size of the font': the number of rows and columns in + the terminal will stay the same, and the font size will change. + + - `Change font size when maximised': when the window is resized, + the number of rows and columns will change, _except_ when the + window is maximised (or restored), when the font size will + change. (In this mode, holding down the Alt key while resizing + will also cause the font size to change.) + + - `Forbid resizing completely': the terminal will refuse to be + resized at all. + + 4.7.3 Controlling scrollback + + These options let you configure the way PuTTY keeps text after it + scrolls off the top of the screen (see section 3.1.2). + + The `Lines of scrollback' box lets you configure how many lines of + text PuTTY keeps. The `Display scrollbar' options allow you to hide + the scrollbar (although you can still view the scrollback using + the keyboard as described in section 3.1.2). You can separately + configure whether the scrollbar is shown in full-screen mode and in + normal modes. + + If you are viewing part of the scrollback when the server sends + more text to PuTTY, the screen will revert to showing the current + terminal contents. You can disable this behaviour by turning off + `Reset scrollback on display activity'. You can also make the screen + revert when you press a key, by turning on `Reset scrollback on + keypress'. + + 4.7.4 `Push erased text into scrollback' + + When this option is enabled, the contents of the terminal screen + will be pushed into the scrollback when a server-side application + clears the screen, so that your scrollback will contain a better + record of what was on your screen in the past. + + If the application switches to the alternate screen (see section + 4.6.4 for more about this), then the contents of the primary screen + will be visible in the scrollback until the application switches + back again. + + This option is enabled by default. + + 4.8 The Appearance panel + + The Appearance configuration panel allows you to control aspects of + the appearance of PuTTY's window. + + 4.8.1 Controlling the appearance of the cursor + + The `Cursor appearance' option lets you configure the cursor to be a + block, an underline, or a vertical line. A block cursor becomes an + empty box when the window loses focus; an underline or a vertical + line becomes dotted. + + The `Cursor blinks' option makes the cursor blink on and off. This + works in any of the cursor modes. + + 4.8.2 Controlling the font used in the terminal window + + This option allows you to choose what font, in what size, the PuTTY + terminal window uses to display the text in the session. + + By default, you will be offered a choice from all the fixed-width + fonts installed on the system, since VT100-style terminal handling + expects a fixed-width font. If you tick the box marked `Allow + selection of variable-pitch fonts', however, PuTTY will offer + variable-width fonts as well: if you select one of these, the font + will be coerced into fixed-size character cells, which will probably + not look very good (but can work OK with some fonts). + + 4.8.3 `Hide mouse pointer when typing in window' + + If you enable this option, the mouse pointer will disappear if the + PuTTY window is selected and you press a key. This way, it will + not obscure any of the text in the window while you work in your + session. As soon as you move the mouse, the pointer will reappear. + + This option is disabled by default, so the mouse pointer remains + visible at all times. + + 4.8.4 Controlling the window border + + PuTTY allows you to configure the appearance of the window border to + some extent. + + The checkbox marked `Sunken-edge border' changes the appearance of + the window border to something more like a DOS box: the inside edge + of the border is highlighted as if it sank down to meet the surface + inside the window. This makes the border a little bit thicker as + well. It's hard to describe well. Try it and see if you like it. + + You can also configure a completely blank gap between the text in + the window and the border, using the `Gap between text and window + edge' control. By default this is set at one pixel. You can reduce + it to zero, or increase it further. + + 4.9 The Behaviour panel + + The Behaviour configuration panel allows you to control aspects of + the behaviour of PuTTY's window. + + 4.9.1 Controlling the window title + + The `Window title' edit box allows you to set the title of the PuTTY + window. By default the window title will contain the host name + followed by `PuTTY', for example `server1.example.com - PuTTY'. If + you want a different window title, this is where to set it. + + PuTTY allows the server to send `xterm' control sequences which + modify the title of the window in mid-session (unless this is + disabled - see section 4.6.5); the title string set here is + therefore only the _initial_ window title. + + As well as the _window_ title, there is also an `xterm' sequence + to modify the title of the window's _icon_. This makes sense in a + windowing system where the window becomes an icon when minimised, + such as Windows 3.1 or most X Window System setups; but in the + Windows 95-like user interface it isn't as applicable. + + By default, PuTTY only uses the server-supplied _window_ title, + and ignores the icon title entirely. If for some reason you want + to see both titles, check the box marked `Separate window and icon + titles'. If you do this, PuTTY's window title and Taskbar caption + will change into the server-supplied icon title if you minimise the + PuTTY window, and change back to the server-supplied window title if + you restore it. (If the server has not bothered to supply a window + or icon title, none of this will happen.) + + 4.9.2 `Warn before closing window' + + If you press the Close button in a PuTTY window that contains a + running session, PuTTY will put up a warning window asking if you + really meant to close the window. A window whose session has already + terminated can always be closed without a warning. + + If you want to be able to close a window quickly, you can disable + the `Warn before closing window' option. + + 4.9.3 `Window closes on ALT-F4' + + By default, pressing ALT-F4 causes the window to close (or a warning + box to appear; see section 4.9.2). If you disable the `Window closes + on ALT-F4' option, then pressing ALT-F4 will simply send a key + sequence to the server. + + 4.9.4 `System menu appears on ALT-Space' + + If this option is enabled, then pressing ALT-Space will bring up the + PuTTY window's menu, like clicking on the top left corner. If it is + disabled, then pressing ALT-Space will just send `ESC SPACE' to the + server. + + Some accessibility programs for Windows may need this option + enabling to be able to control PuTTY's window successfully. For + instance, Dragon NaturallySpeaking requires it both to open the + system menu via voice, and to close, minimise, maximise and restore + the window. + + 4.9.5 `System menu appears on Alt alone' + + If this option is enabled, then pressing and releasing ALT will + bring up the PuTTY window's menu, like clicking on the top left + corner. If it is disabled, then pressing and releasing ALT will have + no effect. + + 4.9.6 `Ensure window is always on top' + + If this option is enabled, the PuTTY window will stay on top of all + other windows. + + 4.9.7 `Full screen on Alt-Enter' + + If this option is enabled, then pressing Alt-Enter will cause the + PuTTY window to become full-screen. Pressing Alt-Enter again will + restore the previous window size. + + The full-screen feature is also available from the System menu, even + when it is configured not to be available on the Alt-Enter key. See + section 3.1.3.7. + + 4.10 The Translation panel + + The Translation configuration panel allows you to control the + translation between the character set understood by the server and + the character set understood by PuTTY. + +4.10.1 Controlling character set translation + + During an interactive session, PuTTY receives a stream of 8-bit + bytes from the server, and in order to display them on the screen it + needs to know what character set to interpret them in. Similarly, + PuTTY needs to know how to translate your keystrokes into the + encoding the server expects. Unfortunately, there is no satisfactory + mechanism for PuTTY and the server to communicate this information, + so it must usually be manually configured. + + There are a lot of character sets to choose from. The `Remote + character set' option lets you select one. + + By default PuTTY will use the UTF-8 encoding of Unicode, which can + represent pretty much any character; data coming from the server + is interpreted as UTF-8, and keystrokes are sent UTF-8 encoded. + This is what most modern distributions of Linux will expect by + default. However, if this is wrong for your server, you can select a + different character set using this control. + + A few other notable character sets are: + + - The ISO-8859 series are all standard character sets that include + various accented characters appropriate for different sets of + languages. + + - The Win125x series are defined by Microsoft, for similar + purposes. In particular Win1252 is almost equivalent to ISO- + 8859-1, but contains a few extra characters such as matched + quotes and the Euro symbol. + + - If you want the old IBM PC character set with block graphics and + line-drawing characters, you can select `CP437'. + + If you need support for a numeric code page which is not listed in + the drop-down list, such as code page 866, then you can try entering + its name manually (`CP866' for example) in the list box. If the + underlying version of Windows has the appropriate translation table + installed, PuTTY will use it. + +4.10.2 `Treat CJK ambiguous characters as wide' + + There are some Unicode characters whose width is not well-defined. + In most contexts, such characters should be treated as single- + width for the purposes of wrapping and so on; however, in some CJK + contexts, they are better treated as double-width for historical + reasons, and some server-side applications may expect them to be + displayed as such. Setting this option will cause PuTTY to take the + double-width interpretation. + + If you use legacy CJK applications, and you find your lines are + wrapping in the wrong places, or you are having other display + problems, you might want to play with this setting. + + This option only has any effect in UTF-8 mode (see section 4.10.1). + +4.10.3 `Caps Lock acts as Cyrillic switch' + + This feature allows you to switch between a US/UK keyboard layout + and a Cyrillic keyboard layout by using the Caps Lock key, if you + need to type (for example) Russian and English side by side in the + same document. + + Currently this feature is not expected to work properly if your + native keyboard layout is not US or UK. + +4.10.4 Controlling display of line-drawing characters + + VT100-series terminals allow the server to send control sequences + that shift temporarily into a separate character set for drawing + simple lines and boxes. However, there are a variety of ways in + which PuTTY can attempt to find appropriate characters, and the + right one to use depends on the locally configured font. In general + you should probably try lots of options until you find one that your + particular font supports. + + - `Use Unicode line drawing code points' tries to use the box + characters that are present in Unicode. For good Unicode- + supporting fonts this is probably the most reliable and + functional option. + + - `Poor man's line drawing' assumes that the font _cannot_ + generate the line and box characters at all, so it will use the + `+', `-' and `|' characters to draw approximations to boxes. You + should use this option if none of the other options works. + + - `Font has XWindows encoding' is for use with fonts that have a + special encoding, where the lowest 32 character positions (below + the ASCII printable range) contain the line-drawing characters. + This is unlikely to be the case with any standard Windows font; + it will probably only apply to custom-built fonts or fonts that + have been automatically converted from the X Window System. + + - `Use font in both ANSI and OEM modes' tries to use the same font + in two different character sets, to obtain a wider range of + characters. This doesn't always work; some fonts claim to be a + different size depending on which character set you try to use. + + - `Use font in OEM mode only' is more reliable than that, but can + miss out other characters from the main character set. + +4.10.5 Controlling copy and paste of line drawing characters + + By default, when you copy and paste a piece of the PuTTY screen that + contains VT100 line and box drawing characters, PuTTY will paste + them in the form they appear on the screen: either Unicode line + drawing code points, or the `poor man's' line-drawing characters + `+', `-' and `|'. The checkbox `Copy and paste VT100 line drawing + chars as lqqqk' disables this feature, so line-drawing characters + will be pasted as the ASCII characters that were printed to produce + them. This will typically mean they come out mostly as `q' and `x', + with a scattering of `jklmntuvw' at the corners. This might be + useful if you were trying to recreate the same box layout in another + program, for example. + + Note that this option only applies to line-drawing characters which + _were_ printed by using the VT100 mechanism. Line-drawing characters + that were received as Unicode code points will paste as Unicode + always. + +4.10.6 Combining VT100 line-drawing with UTF-8 + + If PuTTY is configured to treat data from the server as encoded in + UTF-8, then by default it disables the older VT100-style system + of control sequences that cause the lower-case letters to be + temporarily replaced by line drawing characters. + + The rationale is that in UTF-8 mode you don't need those control + sequences anyway, because all the line-drawing characters they + access are available as Unicode characters already, so there's no + need for applications to put the terminal into a special state to + get at them. + + Also, it removes a risk of the terminal _accidentally_ getting into + that state: if you accidentally write uncontrolled binary data to a + non-UTF-8 terminal, it can be surprisingly common to find that your + next shell prompt appears as a sequence of line-drawing characters + and then you have to remember or look up how to get out of that + mode. So by default, UTF-8 mode simply doesn't _have_ a confusing + mode like that to get into, accidentally or on purpose. + + However, not all applications will see it that way. Even UTF-8 + terminal users will still sometimes have to run software that tries + to print line-drawing characters in the old-fashioned way. So the + configuration option `Enable VT100 line drawing even in UTF-8 mode' + puts PuTTY into a hybrid mode in which it understands the VT100- + style control sequences that change the meaning of the ASCII lower + case letters, _and_ understands UTF-8. + + 4.11 The Selection panel + + The Selection panel allows you to control the way copy and paste + work in the PuTTY window. + +4.11.1 Changing the actions of the mouse buttons + + PuTTY's copy and paste mechanism is by default modelled on the Unix + `xterm' application. The X Window System uses a three-button mouse, + and the convention in that system is that the left button selects, + the right button extends an existing selection, and the middle + button pastes. + + Windows often only has two mouse buttons, so when run on + Windows, PuTTY is configurable. In PuTTY's default configuration + (`Compromise'), the _right_ button pastes, and the _middle_ button + (if you have one) extends a selection. + + If you have a three-button mouse and you are already used to the + `xterm' arrangement, you can select it using the `Action of mouse + buttons' control. + + Alternatively, with the `Windows' option selected, the middle button + extends, and the right button brings up a context menu (on which one + of the options is `Paste'). (This context menu is always available + by holding down Ctrl and right-clicking, regardless of the setting + of this option.) + + (When PuTTY iself is running on Unix, it follows the X Window System + convention.) + +4.11.2 `Shift overrides application's use of mouse' + + PuTTY allows the server to send control codes that let it take + over the mouse and use it for purposes other than copy and paste. + Applications which use this feature include the text-mode web + browser `links', the Usenet newsreader `trn' version 4, and the file + manager `mc' (Midnight Commander). + + When running one of these applications, pressing the mouse buttons + no longer performs copy and paste. If you do need to copy and paste, + you can still do so if you hold down Shift while you do your mouse + clicks. + + However, it is possible in theory for applications to even detect + and make use of Shift + mouse clicks. We don't know of any + applications that do this, but in case someone ever writes one, + unchecking the `Shift overrides application's use of mouse' checkbox + will cause Shift + mouse clicks to go to the server as well (so that + mouse-driven copy and paste will be completely disabled). + + If you want to prevent the application from taking over the mouse at + all, you can do this using the Features control panel; see section + 4.6.2. + +4.11.3 Default selection mode + + As described in section 3.1.1, PuTTY has two modes of selecting + text to be copied to the clipboard. In the default mode (`Normal'), + dragging the mouse from point A to point B selects to the end of + the line containing A, all the lines in between, and from the very + beginning of the line containing B. In the other mode (`Rectangular + block'), dragging the mouse between two points defines a rectangle, + and everything within that rectangle is copied. + + Normally, you have to hold down Alt while dragging the mouse to + select a rectangular block. Using the `Default selection mode' + control, you can set rectangular selection as the default, and then + you have to hold down Alt to get the _normal_ behaviour. + +4.11.4 Assigning copy and paste actions to clipboards + + Here you can configure which clipboard(s) are written or read by + PuTTY's various copy and paste actions. + + Most platforms, including Windows, have a single system clipboard. + On these platforms, PuTTY provides a second clipboard-like + facility by permitting you to paste the text you last selected in + _this window_, whether or not it is currently also in the system + clipboard. This is not enabled by default. + + The X Window System (which underlies most Unix graphical + interfaces) provides multiple clipboards (or `selections'), and + many applications support more than one of them by a different user + interface mechanism. When PuTTY itself is running on Unix, it has + more configurability relating to these selections. + + The two most commonly used selections are called `PRIMARY' and + `CLIPBOARD'; in applications supporting both, the usual behaviour + is that PRIMARY is used by mouse-only actions (selecting text + automatically copies it to PRIMARY, and middle-clicking pastes from + PRIMARY), whereas CLIPBOARD is used by explicit Copy and Paste menu + items or keypresses such as Ctrl-C and Ctrl-V. + +4.11.4.1 `Auto-copy selected text' + + The checkbox `Auto-copy selected text to system clipboard' controls + whether or not selecting text in the PuTTY terminal window + automatically has the side effect of copying it to the system + clipboard, without requiring a separate user interface action. + + On X, the wording of this option is changed slightly so that + `CLIPBOARD' is mentioned in place of the `system clipboard'. Text + selected in the terminal window will _always_ be automatically + placed in the PRIMARY selection, as is conventional, but if you tick + this box, it will _also_ be placed in `CLIPBOARD' at the same time. + +4.11.4.2 Choosing a clipboard for UI actions + + PuTTY has three user-interface actions which can be configured to + paste into the terminal (not counting menu items). You can click + whichever mouse button (if any) is configured to paste (see section + 4.11.1); you can press Shift-Ins; or you can press Ctrl-Shift-V, + although that action is not enabled by default. + + You can configure which of the available clipboards each of these + actions pastes from (including turning the paste action off + completely). On platforms with a single system clipboard (such as + Windows), the available options are to paste from that clipboard + or to paste from PuTTY's internal memory of the last selected text + within that window. On X, the standard options are CLIPBOARD or + PRIMARY. + + (PRIMARY is conceptually similar in that it _also_ refers to the + last selected text - just across all applications instead of just + this window.) + + The two keyboard options each come with a corresponding key to copy + _to_ the same clipboard. Whatever you configure Shift-Ins to paste + from, Ctrl-Ins will copy to the same location; similarly, Ctrl- + Shift-C will copy to whatever Ctrl-Shift-V pastes from. + + On X, you can also enter a selection name of your choice. For + example, there is a rarely-used standard selection called + `SECONDARY', which Emacs (for example) can work with if you hold + down the Meta key while dragging to select or clicking to paste; if + you configure a PuTTY keyboard action to access this clipboard, then + you can interoperate with other applications' use of it. Another + thing you could do would be to invent a clipboard name yourself, to + create a special clipboard shared _only_ between instances of PuTTY, + or between just instances configured in that particular way. + +4.11.5 `Permit control characters in pasted text' + + It is possible for the clipboard to contain not just text (with + newlines and tabs) but also control characters such as ESC which + could have surprising effects if pasted into a terminal session, + depending on what program is running on the server side. Copying + text from a mischievous web page could put such characters onto the + clipboard. + + By default, PuTTY filters out the more unusual control characters, + only letting through the more obvious text-formatting characters + (newlines, tab, backspace, and DEL). + + Setting this option stops this filtering; on paste, any character + on the clipboard is sent to the session uncensored. This might be + useful if you are deliberately using control character pasting as a + simple form of scripting, for instance. + + 4.12 The Copy panel + + The Copy configuration panel controls behaviour specifically related + to copying from the terminal window to the clipboard. + +4.12.1 Character classes + + PuTTY will select a word at a time in the terminal window if you + double-click to begin the drag. This section allows you to control + precisely what is considered to be a word. + + Each character is given a _class_, which is a small number + (typically 0, 1 or 2). PuTTY considers a single word to be any + number of adjacent characters in the same class. So by modifying the + assignment of characters to classes, you can modify the word-by-word + selection behaviour. + + In the default configuration, the character classes are: + + - Class 0 contains white space and control characters. + + - Class 1 contains most punctuation. + + - Class 2 contains letters, numbers and a few pieces of + punctuation (the double quote, minus sign, period, forward slash + and underscore). + + So, for example, if you assign the `@' symbol into character class + 2, you will be able to select an e-mail address with just a double + click. + + In order to adjust these assignments, you start by selecting a group + of characters in the list box. Then enter a class number in the edit + box below, and press the `Set' button. + + This mechanism currently only covers ASCII characters, because it + isn't feasible to expand the list to cover the whole of Unicode. + + Character class definitions can be modified by control sequences + sent by the server. This configuration option controls the _default_ + state, which will be restored when you reset the terminal (see + section 3.1.3.6). However, if you modify this option in mid-session + using `Change Settings', it will take effect immediately. + +4.12.2 Copying in Rich Text Format + + If you enable `Copy to clipboard in RTF as well as plain text', + PuTTY will write formatting information to the clipboard as well + as the actual text you copy. The effect of this is that if you + paste into (say) a word processor, the text will appear in the word + processor in the same font, colour, and style (e.g. bold, underline) + PuTTY was using to display it. + + This option can easily be inconvenient, so by default it is + disabled. + + 4.13 The Colours panel + + The Colours panel allows you to control PuTTY's use of colour. + +4.13.1 `Allow terminal to specify ANSI colours' + + This option is enabled by default. If it is disabled, PuTTY will + ignore any control sequences sent by the server to request coloured + text. + + If you have a particularly garish application, you might want to + turn this option off and make PuTTY only use the default foreground + and background colours. + +4.13.2 `Allow terminal to use xterm 256-colour mode' + + This option is enabled by default. If it is disabled, PuTTY will + ignore any control sequences sent by the server which use the + extended 256-colour mode supported by recent versions of xterm. + + If you have an application which is supposed to use 256-colour mode + and it isn't working, you may find you need to tell your server that + your terminal supports 256 colours. On Unix, you do this by ensuring + that the setting of TERM describes a 256-colour-capable terminal. + You can check this using a command such as `infocmp': + + $ infocmp | grep colors + colors#256, cols#80, it#8, lines#24, pairs#256, + + If you do not see `colors#256' in the output, you may need to change + your terminal setting. On modern Linux machines, you could try + `xterm-256color'. + +4.13.3 `Allow terminal to use 24-bit colour' + + This option is enabled by default. If it is disabled, PuTTY will + ignore any control sequences sent by the server which use the + control sequences supported by modern terminals to specify arbitrary + 24-bit RGB colour value. + +4.13.4 `Indicate bolded text by changing...' + + When the server sends a control sequence indicating that some text + should be displayed in bold, PuTTY can handle this in several ways. + It can either change the font for a bold version, or use the same + font in a brighter colour, or it can do both (brighten the colour + _and_ embolden the font). This control lets you choose which. + + By default bold is indicated by colour, so non-bold text is + displayed in light grey and bold text is displayed in bright white + (and similarly in other colours). If you change the setting to `The + font' box, bold and non-bold text will be displayed in the same + colour, and instead the font will change to indicate the difference. + If you select `Both', the font and the colour will both change. + + Some applications rely on `bold black' being distinguishable from a + black background; if you choose `The font', their text may become + invisible. + +4.13.5 `Attempt to use logical palettes' + + Logical palettes are a mechanism by which a Windows application + running on an 8-bit colour display can select precisely the colours + it wants instead of going with the Windows standard defaults. + + If you are not getting the colours you ask for on an 8-bit display, + you can try enabling this option. However, be warned that it's never + worked very well. + +4.13.6 `Use system colours' + + Enabling this option will cause PuTTY to ignore the configured + colours for `Default Background/Foreground' and `Cursor Colour/Text' + (see section 4.13.7), instead going with the system-wide defaults. + + Note that non-bold and bold text will be the same colour if this + option is enabled. You might want to change to indicating bold text + by font changes (see section 4.13.4). + +4.13.7 Adjusting the colours in the terminal window + + The main colour control allows you to specify exactly what colours + things should be displayed in. To modify one of the PuTTY colours, + use the list box to select which colour you want to modify. The + RGB values for that colour will appear on the right-hand side of + the list box. Now, if you press the `Modify' button, you will be + presented with a colour selector, in which you can choose a new + colour to go in place of the old one. (You may also edit the RGB + values directly in the edit boxes, if you wish; each value is an + integer from 0 to 255.) + + PuTTY allows you to set the cursor colour, the default foreground + and background, and the precise shades of all the ANSI configurable + colours (black, red, green, yellow, blue, magenta, cyan, and white). + You can also modify the precise shades used for the bold versions + of these colours; these are used to display bold text if you have + chosen to indicate that by colour (see section 4.13.4), and can also + be used if the server asks specifically to use them. (Note that + `Default Bold Background' is _not_ the background colour used for + bold text; it is only used if the server specifically asks for a + bold background.) + + 4.14 The Connection panel + + The Connection panel allows you to configure options that apply to + more than one type of connection. + +4.14.1 Using keepalives to prevent disconnection + + If you find your sessions are closing unexpectedly (most often with + `Connection reset by peer') after they have been idle for a while, + you might want to try using this option. + + Some network routers and firewalls need to keep track of all + connections through them. Usually, these firewalls will assume a + connection is dead if no data is transferred in either direction + after a certain time interval. This can cause PuTTY sessions to be + unexpectedly closed by the firewall if no traffic is seen in the + session for some time. + + The keepalive option (`Seconds between keepalives') allows you + to configure PuTTY to send data through the session at regular + intervals, in a way that does not disrupt the actual terminal + session. If you find your firewall is cutting idle connections off, + you can try entering a non-zero value in this field. The value + is measured in seconds; so, for example, if your firewall cuts + connections off after ten minutes then you might want to enter 300 + seconds (5 minutes) in the box. + + Note that keepalives are not always helpful. They help if you have + a firewall which drops your connection after an idle period; but + if the network between you and the server suffers from breaks in + connectivity then keepalives can actually make things worse. If a + session is idle, and connectivity is temporarily lost between the + endpoints, but the connectivity is restored before either side + tries to send anything, then there will be no problem - neither + endpoint will notice that anything was wrong. However, if one side + does send something during the break, it will repeatedly try to + re-send, and eventually give up and abandon the connection. Then + when connectivity is restored, the other side will find that the + first side doesn't believe there is an open connection any more. + Keepalives can make this sort of problem worse, because they + increase the probability that PuTTY will attempt to send data during + a break in connectivity. (Other types of periodic network activity + can cause this behaviour; in particular, SSH-2 re-keys can have this + effect. See section 4.20.2.) + + Therefore, you might find that keepalives help connection loss, + or you might find they make it worse, depending on what _kind_ of + network problems you have between you and the server. + + Keepalives are only supported in Telnet and SSH; the Rlogin and Raw + protocols offer no way of implementing them. (For an alternative, + see section 4.14.3.) + + Note that if you are using SSH-1 and the server has a bug that makes + it unable to deal with SSH-1 ignore messages (see section 4.28.11), + enabling keepalives will have no effect. + +4.14.2 `Disable Nagle's algorithm' + + Nagle's algorithm is a detail of TCP/IP implementations that tries + to minimise the number of small data packets sent down a network + connection. With Nagle's algorithm enabled, PuTTY's bandwidth usage + will be slightly more efficient; with it disabled, you may find you + get a faster response to your keystrokes when connecting to some + types of server. + + The Nagle algorithm is disabled by default for interactive + connections. + +4.14.3 `Enable TCP keepalives' + + _NOTE:_ TCP keepalives should not be confused with the application- + level keepalives described in section 4.14.1. If in doubt, you + probably want application-level keepalives; TCP keepalives are + provided for completeness. + + The idea of TCP keepalives is similar to application-level + keepalives, and the same caveats apply. The main differences are: + + - TCP keepalives are available on _all_ connection types, + including Raw and Rlogin. + + - The interval between TCP keepalives is usually much longer, + typically two hours; this is set by the operating system, and + cannot be configured within PuTTY. + + - If the operating system does not receive a response to a + keepalive, it may send out more in quick succession and + terminate the connection if no response is received. + + TCP keepalives may be more useful for ensuring that half-open + connections are terminated than for keeping a connection alive. + + TCP keepalives are disabled by default. + +4.14.4 `Internet protocol version' + + This option allows the user to select between the old and new + Internet protocols and addressing schemes (IPv4 and IPv6). The + selected protocol will be used for most outgoing network connections + (including connections to proxies); however, tunnels have their own + configuration, for which see section 4.27.2. + + The default setting is `Auto', which means PuTTY will do something + sensible and try to guess which protocol you wanted. (If you specify + a literal Internet address, it will use whichever protocol that + address implies. If you provide a hostname, it will see what kinds + of address exist for that hostname; it will use IPv6 if there is an + IPv6 address available, and fall back to IPv4 if not.) + + If you need to force PuTTY to use a particular protocol, you can + explicitly set this to `IPv4' or `IPv6'. + +4.14.5 `Logical name of remote host' + + This allows you to tell PuTTY that the host it will really end up + connecting to is different from where it thinks it is making a + network connection. + + You might use this, for instance, if you had set up an SSH port + forwarding in one PuTTY session so that connections to some + arbitrary port (say, localhost port 10022) were forwarded to a + second machine's SSH port (say, foovax port 22), and then started a + second PuTTY connecting to the forwarded port. + + In normal usage, the second PuTTY will access the host key cache + under the host name and port it actually connected to (i.e. + localhost port 10022 in this example). Using the logical host name + option, however, you can configure the second PuTTY to cache the + host key under the name of the host _you_ know that it's _really_ + going to end up talking to (here `foovax'). + + This can be useful if you expect to connect to the same actual + server through many different channels (perhaps because your port + forwarding arrangements keep changing): by consistently setting the + logical host name, you can arrange that PuTTY will not keep asking + you to reconfirm its host key. Conversely, if you expect to use the + same local port number for port forwardings to lots of different + servers, you probably didn't want any particular server's host + key cached under that local port number. (For this latter case, + you could instead explicitly configure host keys in the relevant + sessions; see section 4.21.2.) + + If you just enter a host name for this option, PuTTY will cache the + SSH host key under the default SSH port for that host, irrespective + of the port you really connected to (since the typical scenario is + like the above example: you connect to a silly real port number and + your connection ends up forwarded to the normal port-22 SSH server + of some other machine). To override this, you can append a port + number to the logical host name, separated by a colon. E.g. entering + `foovax:2200' as the logical host name will cause the host key to be + cached as if you had connected to port 2200 of `foovax'. + + If you provide a host name using this option, it is also displayed + in other locations which contain the remote host name, such as the + default window title and the default SSH password prompt. This + reflects the fact that this is the host you're _really_ connecting + to, which is more important than the mere means you happen to be + using to contact that host. (This applies even if you're using a + protocol other than SSH.) + + 4.15 The Data panel + + The Data panel allows you to configure various pieces of data which + can be sent to the server to affect your connection at the far end. + + Each option on this panel applies to more than one protocol. + Options which apply to only one protocol appear on that protocol's + configuration panels. + +4.15.1 `Auto-login username' + + All three of the SSH, Telnet and Rlogin protocols allow you to + specify what user name you want to log in as, without having to type + it explicitly every time. (Some Telnet servers don't support this.) + + In this box you can type that user name. + +4.15.2 Use of system username + + When the previous box (section 4.15.1) is left blank, by default, + PuTTY will prompt for a username at the time you make a connection. + + In some environments, such as the networks of large organisations + implementing single sign-on, a more sensible default may be to use + the name of the user logged in to the local operating system (if + any); this is particularly likely to be useful with GSSAPI key + exchange and user authentication (see section 4.24 and section + 4.20.1.1). This control allows you to change the default behaviour. + + The current system username is displayed in the dialog as a + convenience. It is not saved in the configuration; if a saved + session is later used by a different user, that user's name will be + used. + +4.15.3 `Terminal-type string' + + Most servers you might connect to with PuTTY are designed to be + connected to from lots of different types of terminal. In order to + send the right control sequences to each one, the server will need + to know what type of terminal it is dealing with. Therefore, each + of the SSH, Telnet and Rlogin protocols allow a text string to be + sent down the connection describing the terminal. On a Unix server, + this selects an entry from the `termcap' or `terminfo' database that + tells applications what control sequences to send to the terminal, + and what character sequences to expect the keyboard to generate. + + PuTTY attempts to emulate the Unix `xterm' program, and by default + it reflects this by sending `xterm' as a terminal-type string. If + you find this is not doing what you want - perhaps the remote system + reports `Unknown terminal type' - you could try setting this to + something different, such as `vt220'. + + If you're not sure whether a problem is due to the terminal type + setting or not, you probably need to consult the manual for your + application or your server. + +4.15.4 `Terminal speeds' + + The Telnet, Rlogin, and SSH protocols allow the client to specify + terminal speeds to the server. + + This parameter does _not_ affect the actual speed of the connection, + which is always `as fast as possible'; it is just a hint that is + sometimes used by server software to modify its behaviour. For + instance, if a slow speed is indicated, the server may switch to a + less bandwidth-hungry display mode. + + The value is usually meaningless in a network environment, but PuTTY + lets you configure it, in case you find the server is reacting badly + to the default value. + + The format is a pair of numbers separated by a comma, for instance, + `38400,38400'. The first number represents the output speed (_from_ + the server) in bits per second, and the second is the input speed + (_to_ the server). (Only the first is used in the Rlogin protocol.) + + This option has no effect on Raw connections. + +4.15.5 Setting environment variables on the server + + The Telnet protocol provides a means for the client to pass + environment variables to the server. Many Telnet servers have + stopped supporting this feature due to security flaws, but PuTTY + still supports it for the benefit of any servers which have found + other ways around the security problems than just disabling the + whole mechanism. + + Version 2 of the SSH protocol also provides a similar mechanism, + which is easier to implement without security flaws. Newer SSH-2 + servers are more likely to support it than older ones. + + This configuration data is not used in the SSH-1, rlogin or raw + protocols. + + To add an environment variable to the list transmitted down the + connection, you enter the variable name in the `Variable' box, enter + its value in the `Value' box, and press the `Add' button. To remove + one from the list, select it in the list box and press `Remove'. + + 4.16 The Proxy panel + + The Proxy panel allows you to configure PuTTY to use various types + of proxy in order to make its network connections. The settings in + this panel affect the primary network connection forming your PuTTY + session, and also any extra connections made as a result of SSH port + forwarding (see section 3.5). + + Note that unlike some software (such as web browsers), PuTTY does + not attempt to automatically determine whether to use a proxy and + (if so) which one to use for a given destination. If you need to use + a proxy, it must always be explicitly configured. + +4.16.1 Setting the proxy type + + The `Proxy type' radio buttons allow you to configure what type of + proxy you want PuTTY to use for its network connections. The default + setting is `None'; in this mode no proxy is used for any connection. + + - Selecting `HTTP' allows you to proxy your connections through a + web server supporting the HTTP CONNECT command, as documented in + RFC 2817. + + - Selecting `SOCKS 4' or `SOCKS 5' allows you to proxy your + connections through a SOCKS server. + + - Many firewalls implement a less formal type of proxy in which + a user can make a Telnet connection directly to the firewall + machine and enter a command such as `connect myhost.com 22' to + connect through to an external host. Selecting `Telnet' allows + you to tell PuTTY to use this type of proxy. + + - Selecting `Local' allows you to specify an arbitrary command + on the local machine to act as a proxy. When the session is + started, instead of creating a TCP connection, PuTTY runs the + command (specified in section 4.16.5), and uses its standard + input and output streams. + + This could be used, for instance, to talk to some kind of + network proxy that PuTTY does not natively support; or you could + tunnel a connection over something other than TCP/IP entirely. + + If you want your local proxy command to make a secondary + SSH connection to a proxy host and then tunnel the primary + connection over that, you might well want the `-nc' command-line + option in Plink. See section 3.8.3.14 for more information. + + You can also enable this mode on the command line; see section + 3.8.3.24. + +4.16.2 Excluding parts of the network from proxying + + Typically you will only need to use a proxy to connect to non-local + parts of your network; for example, your proxy might be required for + connections outside your company's internal network. In the `Exclude + Hosts/IPs' box you can enter ranges of IP addresses, or ranges of + DNS names, for which PuTTY will avoid using the proxy and make a + direct connection instead. + + The `Exclude Hosts/IPs' box may contain more than one exclusion + range, separated by commas. Each range can be an IP address or a DNS + name, with a `*' character allowing wildcards. For example: + + *.example.com + + This excludes any host with a name ending in `.example.com' from + proxying. + + 192.168.88.* + + This excludes any host with an IP address starting with 192.168.88 + from proxying. + + 192.168.88.*,*.example.com + + This excludes both of the above ranges at once. + + Connections to the local host (the host name `localhost', and any + loopback IP address) are never proxied, even if the proxy exclude + list does not explicitly contain them. It is very unlikely that this + behaviour would ever cause problems, but if it does you can change + it by enabling `Consider proxying local host connections'. + + Note that if you are doing DNS at the proxy (see section 4.16.3), + you should make sure that your proxy exclusion settings do not + depend on knowing the IP address of a host. If the name is passed on + to the proxy without PuTTY looking it up, it will never know the IP + address and cannot check it against your list. + +4.16.3 Name resolution when using a proxy + + If you are using a proxy to access a private network, it can make a + difference whether DNS name resolution is performed by PuTTY itself + (on the client machine) or performed by the proxy. + + The `Do DNS name lookup at proxy end' configuration option allows + you to control this. If you set it to `No', PuTTY will always do its + own DNS, and will always pass an IP address to the proxy. If you set + it to `Yes', PuTTY will always pass host names straight to the proxy + without trying to look them up first. + + If you set this option to `Auto' (the default), PuTTY will do + something it considers appropriate for each type of proxy. Telnet, + HTTP, and SOCKS5 proxies will have host names passed straight to + them; SOCKS4 proxies will not. + + Note that if you are doing DNS at the proxy, you should make sure + that your proxy exclusion settings (see section 4.16.2) do not + depend on knowing the IP address of a host. If the name is passed on + to the proxy without PuTTY looking it up, it will never know the IP + address and cannot check it against your list. + + The original SOCKS 4 protocol does not support proxy-side DNS. There + is a protocol extension (SOCKS 4A) which does support it, but not + all SOCKS 4 servers provide this extension. If you enable proxy DNS + and your SOCKS 4 server cannot deal with it, this might be why. + +4.16.4 Username and password + + If your proxy requires authentication, you can enter a username and + a password in the `Username' and `Password' boxes. + + Note that if you save your session, the proxy password will be saved + in plain text, so anyone who can access your PuTTY configuration + data will be able to discover it. + + Authentication is not fully supported for all forms of proxy: + + - Username and password authentication is supported for HTTP + proxies and SOCKS 5 proxies. + + - With SOCKS 5, authentication is via CHAP if the proxy + supports it (this is not supported in PuTTYtel); otherwise + the password is sent to the proxy in plain text. + + - With HTTP proxying, the only currently supported + authentication method is `basic', where the password is sent + to the proxy in plain text. + + - SOCKS 4 can use the `Username' field, but does not support + passwords. + + - You can specify a way to include a username and password in the + Telnet/Local proxy command (see section 4.16.5). + +4.16.5 Specifying the Telnet or Local proxy command + + If you are using the Telnet proxy type, the usual command required + by the firewall's Telnet server is `connect', followed by a host + name and a port number. If your proxy needs a different command, you + can enter an alternative here. + + If you are using the Local proxy type, the local command to run is + specified here. + + In this string, you can use `\n' to represent a new-line, `\r' to + represent a carriage return, `\t' to represent a tab character, and + `\x' followed by two hex digits to represent any other character. + `\\' is used to encode the `\' character itself. + + Also, the special strings `%host' and `%port' will be replaced by + the host name and port number you want to connect to. The strings + `%user' and `%pass' will be replaced by the proxy username and + password you specify. The strings `%proxyhost' and `%proxyport' will + be replaced by the host details specified on the _Proxy_ panel, if + any (this is most likely to be useful for the Local proxy type). To + get a literal `%' sign, enter `%%'. + + If a Telnet proxy server prompts for a username and password before + commands can be sent, you can use a command such as: + + %user\n%pass\nconnect %host %port\n + + This will send your username and password as the first two lines + to the proxy, followed by a command to connect to the desired host + and port. Note that if you do not include the `%user' or `%pass' + tokens in the Telnet command, then the `Username' and `Password' + configuration fields will be ignored. + +4.16.6 Controlling proxy logging + + Often the proxy interaction has its own diagnostic output; this is + particularly the case for local proxy commands. + + The setting `Print proxy diagnostics in the terminal window' lets + you control how much of the proxy's diagnostics are printed to the + main terminal window, along with output from your main session. + + By default (`No'), proxy diagnostics are only sent to the Event Log; + with `Yes' they are also printed to the terminal, where they may + get mixed up with your main session. `Only until session starts' is + a compromise; proxy messages will go to the terminal window until + the main session is deemed to have started (in a protocol-dependent + way), which is when they're most likely to be interesting; any + further proxy-related messages during the session will only go to + the Event Log. + + 4.17 The Telnet panel + + The Telnet panel allows you to configure options that only apply to + Telnet sessions. + +4.17.1 `Handling of OLD_ENVIRON ambiguity' + + The original Telnet mechanism for passing environment variables was + badly specified. At the time the standard (RFC 1408) was written, + BSD telnet implementations were already supporting the feature, and + the intention of the standard was to describe the behaviour the BSD + implementations were already using. + + Sadly there was a typing error in the standard when it was issued, + and two vital function codes were specified the wrong way round. BSD + implementations did not change, and the standard was not corrected. + Therefore, it's possible you might find either BSD or RFC-compliant + implementations out there. This switch allows you to choose which + one PuTTY claims to be. + + The problem was solved by issuing a second standard, defining a + new Telnet mechanism called NEW_ENVIRON, which behaved exactly + like the original OLD_ENVIRON but was not encumbered by existing + implementations. Most Telnet servers now support this, and it's + unambiguous. This feature should only be needed if you have trouble + passing environment variables to quite an old server. + +4.17.2 Passive and active Telnet negotiation modes + + In a Telnet connection, there are two types of data passed between + the client and the server: actual text, and _negotiations_ about + which Telnet extra features to use. + + PuTTY can use two different strategies for negotiation: + + - In _active_ mode, PuTTY starts to send negotiations as soon as + the connection is opened. + + - In _passive_ mode, PuTTY will wait to negotiate until it sees a + negotiation from the server. + + The obvious disadvantage of passive mode is that if the server is + also operating in a passive mode, then negotiation will never begin + at all. For this reason PuTTY defaults to active mode. + + However, sometimes passive mode is required in order to successfully + get through certain types of firewall and Telnet proxy server. If + you have confusing trouble with a firewall, you could try enabling + passive mode to see if it helps. + +4.17.3 `Keyboard sends Telnet special commands' + + If this box is checked, several key sequences will have their normal + actions modified: + + - the Backspace key on the keyboard will send the Telnet special + backspace code; + + - Control-C will send the Telnet special Interrupt Process code; + + - Control-Z will send the Telnet special Suspend Process code. + + You probably shouldn't enable this unless you know what you're + doing. + +4.17.4 `Return key sends Telnet New Line instead of ^M' + + Unlike most other remote login protocols, the Telnet protocol has + a special `new line' code that is not the same as the usual line + endings of Control-M or Control-J. By default, PuTTY sends the + Telnet New Line code when you press Return, instead of sending + Control-M as it does in most other protocols. + + Most Unix-style Telnet servers don't mind whether they receive + Telnet New Line or Control-M; some servers do expect New Line, + and some servers prefer to see ^M. If you are seeing surprising + behaviour when you press Return in a Telnet session, you might try + turning this option off to see if it helps. + + 4.18 The Rlogin panel + + The Rlogin panel allows you to configure options that only apply to + Rlogin sessions. + +4.18.1 `Local username' + + Rlogin allows an automated (password-free) form of login by means + of a file called `.rhosts' on the server. You put a line in your + `.rhosts' file saying something like `jbloggs@pc1.example.com', and + then when you make an Rlogin connection the client transmits the + username of the user running the Rlogin client. The server checks + the username and hostname against `.rhosts', and if they match it + does not ask for a password. + + This only works because Unix systems contain a safeguard to stop a + user from pretending to be another user in an Rlogin connection. + Rlogin connections have to come from port numbers below 1024, and + Unix systems prohibit this to unprivileged processes; so when the + server sees a connection from a low-numbered port, it assumes the + client end of the connection is held by a privileged (and therefore + trusted) process, so it believes the claim of who the user is. + + Windows does not have this restriction: _any_ user can initiate + an outgoing connection from a low-numbered port. Hence, the + Rlogin `.rhosts' mechanism is completely useless for securely + distinguishing several different users on a Windows machine. If you + have a `.rhosts' entry pointing at a Windows PC, you should assume + that _anyone_ using that PC can spoof your username in an Rlogin + connection and access your account on the server. + + The `Local username' control allows you to specify what user name + PuTTY should claim you have, in case it doesn't match your Windows + user name (or in case you didn't bother to set up a Windows user + name). + + 4.19 The SSH panel + + The SSH panel allows you to configure options that only apply to SSH + sessions. + +4.19.1 Executing a specific command on the server + + In SSH, you don't have to run a general shell session on the server. + Instead, you can choose to run a single specific command (such as + a mail user agent, for example). If you want to do this, enter the + command in the `Remote command' box. + + Note that most servers will close the session after executing the + command. + +4.19.2 `Don't start a shell or command at all' + + If you tick this box, PuTTY will not attempt to run a shell or + command after connecting to the remote server. You might want to + use this option if you are only using the SSH connection for port + forwarding, and your user account on the server does not have the + ability to run a shell. + + This feature is only available in SSH protocol version 2 (since the + version 1 protocol assumes you will always want to run a shell). + + This feature can also be enabled using the `-N' command-line option; + see section 3.8.3.13. + + If you use this feature in Plink, you will not be able to terminate + the Plink process by any graceful means; the only way to kill it + will be by pressing Control-C or sending a kill signal from another + program. + +4.19.3 `Enable compression' + + This enables data compression in the SSH connection: data sent by + the server is compressed before sending, and decompressed at the + client end. Likewise, data sent by PuTTY to the server is compressed + first and the server decompresses it at the other end. This can help + make the most of a low-bandwidth connection. + +4.19.4 `SSH protocol version' + + This allows you to select whether to use SSH protocol version 2 or + the older version 1. + + You should normally leave this at the default of `2'. As well + as having fewer features, the older SSH-1 protocol is no longer + developed, has many known cryptographic weaknesses, and is generally + not considered to be secure. PuTTY's protocol 1 implementation is + provided mainly for compatibility, and is no longer being enhanced. + + If a server offers both versions, prefer `2'. If you have some + server or piece of equipment that only talks SSH-1, select `1' here, + and do not treat the resulting connection as secure. + + PuTTY will not automatically fall back to the other version of the + protocol if the server turns out not to match your selection here; + instead, it will put up an error message and abort the connection. + This prevents an active attacker downgrading an intended SSH-2 + connection to SSH-1. + +4.19.5 Sharing an SSH connection between PuTTY tools + + The controls in this box allow you to configure PuTTY to reuse an + existing SSH connection, where possible. + + The SSH-2 protocol permits you to run multiple data channels over + the same SSH connection, so that you can log in just once (and do + the expensive encryption setup just once) and then have more than + one terminal window open. + + Each instance of PuTTY can still run at most one terminal session, + but using the controls in this box, you can configure PuTTY to check + if another instance of itself has already connected to the target + host, and if so, share that instance's SSH connection instead of + starting a separate new one. + + To enable this feature, just tick the box `Share SSH connections if + possible'. Then, whenever you start up a PuTTY session connecting to + a particular host, it will try to reuse an existing SSH connection + if one is available. For example, selecting `Duplicate Session' from + the system menu will launch another session on the same host, and if + sharing is enabled then it will reuse the existing SSH connection. + + When this mode is in use, the first PuTTY that connected to a given + server becomes the `upstream', which means that it is the one + managing the real SSH connection. All subsequent PuTTYs which reuse + the connection are referred to as `downstreams': they do not connect + to the real server at all, but instead connect to the upstream PuTTY + via local inter-process communication methods. + + For this system to be activated, _both_ the upstream and downstream + instances of PuTTY must have the sharing option enabled. + + The upstream PuTTY can therefore not terminate until all its + downstreams have closed. This is similar to the effect you get with + port forwarding or X11 forwarding, in which a PuTTY whose terminal + session has already finished will still remain open so as to keep + serving forwarded connections. + + In case you need to configure this system in more detail, there + are two additional checkboxes which allow you to specify whether a + particular PuTTY can act as an upstream or a downstream or both. + (These boxes only take effect if the main `Share SSH connections if + possible' box is also ticked.) By default both of these boxes are + ticked, so that multiple PuTTYs started from the same configuration + will designate one of themselves as the upstream and share a single + connection; but if for some reason you need a particular PuTTY + configuration _not_ to be an upstream (e.g. because you definitely + need it to close promptly) or not to be a downstream (e.g. because + it needs to do its own authentication using a special private key) + then you can untick one or the other of these boxes. + + I have referred to `PuTTY' throughout the above discussion, but + all the other PuTTY tools which make SSH connections can use this + mechanism too. For example, if PSCP or PSFTP loads a configuration + with sharing enabled, then it can act as a downstream and use an + existing SSH connection set up by an instance of GUI PuTTY. The one + special case is that PSCP and PSFTP will _never_ act as upstreams. + + It is possible to test programmatically for the existence of a live + upstream using Plink. See section 7.2.3.4. + + 4.20 The Kex panel + + The Kex panel (short for `key exchange') allows you to configure + options related to SSH-2 key exchange. + + Key exchange occurs at the start of an SSH connection (and + occasionally thereafter); it establishes a shared secret that + is used as the basis for all of SSH's security features. It is + therefore very important for the security of the connection that the + key exchange is secure. + + Key exchange is a cryptographically intensive process; if either + the client or the server is a relatively slow machine, the slower + methods may take several tens of seconds to complete. + + If connection startup is too slow, or the connection hangs + periodically, you may want to try changing these settings. + + If you don't understand what any of this means, it's safe to leave + these settings alone. + + This entire panel is only relevant to SSH protocol version 2; none + of these settings affect SSH-1 at all. + +4.20.1 Key exchange algorithm selection + + PuTTY supports a variety of SSH-2 key exchange methods, and allows + you to choose which one you prefer to use; configuration is similar + to cipher selection (see section 4.22). + + PuTTY currently supports the following key exchange methods: + + - `ECDH': elliptic curve Diffie-Hellman key exchange. + + - `Group 14': Diffie-Hellman key exchange with a well-known 2048- + bit group. + + - `Group 1': Diffie-Hellman key exchange with a well-known 1024- + bit group. We no longer recommend using this method, and it's + not used by default in new installations; however, it may be the + only method supported by very old server software. + + - `Group exchange': with this method, instead of using a fixed + group, PuTTY requests that the server suggest a group to use for + key exchange; the server can avoid groups known to be weak, and + possibly invent new ones over time, without any changes required + to PuTTY's configuration. We recommend use of this method + instead of the well-known groups, if possible. + + - `RSA key exchange': this requires much less computational effort + on the part of the client, and somewhat less on the part of the + server, than Diffie-Hellman key exchange. + + - `GSSAPI key exchange': see section 4.20.1.1. + + If the first algorithm PuTTY finds is below the `warn below here' + line, you will see a warning box when you make the connection, + similar to that for cipher selection (see section 4.22). + +4.20.1.1 GSSAPI-based key exchange + + PuTTY supports a set of key exchange methods that also incorporates + GSSAPI-based authentication. They are enabled with the `Attempt + GSSAPI key exchange' checkbox (which also appears on the `GSSAPI' + panel). + + PuTTY can only perform the GSSAPI-authenticated key exchange methods + when using Kerberos V5, and not other GSSAPI mechanisms. If the user + running PuTTY has current Kerberos V5 credentials, then PuTTY will + select the GSSAPI key exchange methods in preference to any of the + ordinary SSH key exchange methods configured in the preference list. + + The advantage of doing GSSAPI authentication as part of the SSH + key exchange is apparent when you are using credential delegation + (see section 4.24.1). The SSH key exchange can be repeated later in + the session, and this allows your Kerberos V5 credentials (which + are typically short-lived) to be automatically re-delegated to the + server when they are refreshed on the client. (This feature is + commonly referred to as `cascading credentials'.) + + If your server doesn't support GSSAPI key exchange, it may still + support GSSAPI in the SSH user authentication phase. This will still + let you log in using your Kerberos credentials, but will only allow + you to delegate the credentials that are active at the beginning of + the session; they can't be refreshed automatically later, in a long- + running session. + + Another effect of GSSAPI key exchange is that it replaces the usual + SSH mechanism of permanent host keys described in section 2.2. So + if you use this method, then you won't be asked any interactive + questions about whether to accept the server's host key. Instead, + the Kerberos exchange will verify the identity of the host you + connect to, at the same time as verifying your identity to it. + +4.20.2 Repeat key exchange + + If the session key negotiated at connection startup is used too much + or for too long, it may become feasible to mount attacks against the + SSH connection. Therefore, the SSH-2 protocol specifies that a new + key exchange should take place every so often; this can be initiated + by either the client or the server. + + While this renegotiation is taking place, no data can pass through + the SSH connection, so it may appear to `freeze'. (The occurrence + of repeat key exchange is noted in the Event Log; see section + 3.1.3.1.) Usually the same algorithm is used as at the start of the + connection, with a similar overhead. + + These options control how often PuTTY will initiate a repeat key + exchange (`rekey'). You can also force a key exchange at any time + from the Special Commands menu (see section 3.1.3.2). + + - `Max minutes before rekey' specifies the amount of time that + is allowed to elapse before a rekey is initiated. If this is + set to zero, PuTTY will not rekey due to elapsed time. The SSH- + 2 protocol specification recommends a timeout of at most 60 + minutes. + + You might have a need to disable time-based rekeys completely + for the same reasons that keepalives aren't always helpful. If + you anticipate suffering a network dropout of several hours in + the middle of an SSH connection, but were not actually planning + to send _data_ down that connection during those hours, then an + attempted rekey in the middle of the dropout will probably cause + the connection to be abandoned, whereas if rekeys are disabled + then the connection should in principle survive (in the absence + of interfering firewalls). See section 4.14.1 for more discussion + of these issues; for these purposes, rekeys have much the same + properties as keepalives. (Except that rekeys have cryptographic + value in themselves, so you should bear that in mind when deciding + whether to turn them off.) Note, however, the the SSH _server_ can + still initiate rekeys. + + - `Minutes between GSSAPI checks', if you're using GSSAPI key + exchange, specifies how often the GSSAPI credential cache is + checked to see whether new tickets are available for delegation, + or current ones are near expiration. If forwarding of GSSAPI + credentials is enabled, PuTTY will try to rekey as necessary to + keep the delegated credentials from expiring. Frequent checks + are recommended; rekeying only happens when needed. + + - `Max data before rekey' specifies the amount of data (in bytes) + that is permitted to flow in either direction before a rekey is + initiated. If this is set to zero, PuTTY will not rekey due to + transferred data. The SSH-2 protocol specification recommends a + limit of at most 1 gigabyte. + + As well as specifying a value in bytes, the following shorthand + can be used: + + - `1k' specifies 1 kilobyte (1024 bytes). + + - `1M' specifies 1 megabyte (1024 kilobytes). + + - `1G' specifies 1 gigabyte (1024 megabytes). + + Disabling data-based rekeys entirely is a bad idea. The integrity, + and to a lesser extent, confidentiality of the SSH-2 protocol depend + in part on rekeys occurring before a 32-bit packet sequence number + wraps around. Unlike time-based rekeys, data-based rekeys won't + occur when the SSH connection is idle, so they shouldn't cause the + same problems. The SSH-1 protocol, incidentally, has even weaker + integrity protection than SSH-2 without rekeys. + + 4.21 The Host Keys panel + + The Host Keys panel allows you to configure options related to SSH-2 + host key management. + + Host keys are used to prove the server's identity, and assure you + that the server is not being spoofed (either by a man-in-the-middle + attack or by completely replacing it on the network). See section + 2.2 for a basic introduction to host keys. + + This entire panel is only relevant to SSH protocol version 2; none + of these settings affect SSH-1 at all. + +4.21.1 Host key type selection + + PuTTY supports a variety of SSH-2 host key types, and allows you + to choose which one you prefer to use to identify the server. + Configuration is similar to cipher selection (see section 4.22). + + PuTTY currently supports the following host key types: + + - `Ed25519': Edwards-curve DSA using a twisted Edwards curve with + modulus 2^255-19. + + - `ECDSA': elliptic curve DSA using one of the NIST-standardised + elliptic curves. + + - `DSA': straightforward DSA using modular exponentiation. + + - `RSA': the ordinary RSA algorithm. + + If PuTTY already has one or more host keys stored for the server, + it will prefer to use one of those, even if the server has a key + type that is higher in the preference order. You can add such a key + to PuTTY's cache from within an existing session using the `Special + Commands' menu; see section 3.1.3.2. + + Otherwise, PuTTY will choose a key type based purely on the + preference order you specify in the configuration. + + If the first key type PuTTY finds is below the `warn below here' + line, you will see a warning box when you make the connection, + similar to that for cipher selection (see section 4.22). + +4.21.2 Manually configuring host keys + + In some situations, if PuTTY's automated host key management is not + doing what you need, you might need to manually configure PuTTY to + accept a specific host key, or one of a specific set of host keys. + + One reason why you might want to do this is because the host name + PuTTY is connecting to is using round-robin DNS to return one of + multiple actual servers, and they all have different host keys. In + that situation, you might need to configure PuTTY to accept any of + a list of host keys for the possible servers, while still rejecting + any key not in that list. + + Another reason is if PuTTY's automated host key management is + completely unavailable, e.g. because PuTTY (or Plink or PSFTP, etc) + is running in a Windows environment without access to the Registry. + In that situation, you will probably want to use the -hostkey + command-line option to configure the expected host key(s); see + section 3.8.3.20. + + For situations where PuTTY's automated host key management simply + picks the wrong host name to store a key under, you may want to + consider setting a `logical host name' instead; see section 4.14.5. + + To configure manual host keys via the GUI, enter some text + describing the host key into the edit box in the `Manually configure + host keys for this connection' container, and press the `Add' + button. The text will appear in the `Host keys or fingerprints + to accept' list box. You can remove keys again with the `Remove' + button. + + The text describing a host key can be in one of the following + formats: + + - An MD5-based host key fingerprint of the form displayed in + PuTTY's Event Log and host key dialog boxes, i.e. sixteen 2- + digit hex numbers separated by colons. + + - A base64-encoded blob describing an SSH-2 public key in + OpenSSH's one-line public key format. How you acquire + a public key in this format is server-dependent; on an + OpenSSH server it can typically be found in a location like + `/etc/ssh/ssh_host_rsa_key.pub'. + + If this box contains at least one host key or fingerprint when PuTTY + makes an SSH connection, then PuTTY's automated host key management + is completely bypassed: the connection will be permitted if and only + if the host key presented by the server is one of the keys listed + in this box, and the host key store in the Registry will be neither + read _nor written_, unless you explicitly do so. + + If the box is empty (as it usually is), then PuTTY's automated host + key management will work as normal. + + 4.22 The Cipher panel + + PuTTY supports a variety of different encryption algorithms, and + allows you to choose which one you prefer to use. You can do this by + dragging the algorithms up and down in the list box (or moving them + using the Up and Down buttons) to specify a preference order. When + you make an SSH connection, PuTTY will search down the list from the + top until it finds an algorithm supported by the server, and then + use that. + + PuTTY currently supports the following algorithms: + + - ChaCha20-Poly1305, a combined cipher and MAC (SSH-2 only) + + - AES (Rijndael) - 256, 192, or 128-bit SDCTR or CBC (SSH-2 only) + + - Arcfour (RC4) - 256 or 128-bit stream cipher (SSH-2 only) + + - Blowfish - 256-bit SDCTR (SSH-2 only) or 128-bit CBC + + - Triple-DES - 168-bit SDCTR (SSH-2 only) or CBC + + - Single-DES - 56-bit CBC (see below for SSH-2) + + If the algorithm PuTTY finds is below the `warn below here' line, + you will see a warning box when you make the connection: + + The first cipher supported by the server + is single-DES, which is below the configured + warning threshold. + Do you want to continue with this connection? + + This warns you that the first available encryption is not a very + secure one. Typically you would put the `warn below here' line + between the encryptions you consider secure and the ones you + consider substandard. By default, PuTTY supplies a preference order + intended to reflect a reasonable preference in terms of security and + speed. + + In SSH-2, the encryption algorithm is negotiated independently for + each direction of the connection, although PuTTY does not support + separate configuration of the preference orders. As a result you may + get two warnings similar to the one above, possibly with different + encryptions. + + Single-DES is not recommended in the SSH-2 protocol standards, but + one or two server implementations do support it. PuTTY can use + single-DES to interoperate with these servers if you enable the + `Enable legacy use of single-DES in SSH-2' option; by default this + is disabled and PuTTY will stick to recommended ciphers. + + 4.23 The Auth panel + + The Auth panel allows you to configure authentication options for + SSH sessions. + +4.23.1 `Display pre-authentication banner' + + SSH-2 servers can provide a message for clients to display to the + prospective user before the user logs in; this is sometimes known + as a pre-authentication `banner'. Typically this is used to provide + information about the server and legal notices. + + By default, PuTTY displays this message before prompting for a + password or similar credentials (although, unfortunately, not before + prompting for a login name, due to the nature of the protocol + design). By unchecking this option, display of the banner can be + suppressed entirely. + +4.23.2 `Bypass authentication entirely' + + In SSH-2, it is in principle possible to establish a connection + without using SSH's mechanisms to identify or prove who you are to + the server. An SSH server could prefer to handle authentication + in the data channel, for instance, or simply require no user + authentication whatsoever. + + By default, PuTTY assumes the server requires authentication (we've + never heard of one that doesn't), and thus must start this process + with a username. If you find you are getting username prompts that + you cannot answer, you could try enabling this option. However, most + SSH servers will reject this. + + This is not the option you want if you have a username and just + want PuTTY to remember it; for that see section 4.15.1. It's + also probably not what if you're trying to set up passwordless + login to a mainstream SSH server; depending on the server, you + probably wanted public-key authentication (chapter 8) or perhaps + GSSAPI authentication (section 4.24). (These are still forms of + authentication, even if you don't have to interact with them.) + + This option only affects SSH-2 connections. SSH-1 connections always + require an authentication step. + +4.23.3 `Attempt authentication using Pageant' + + If this option is enabled, then PuTTY will look for Pageant (the + SSH private-key storage agent) and attempt to authenticate with any + suitable public keys Pageant currently holds. + + This behaviour is almost always desirable, and is therefore enabled + by default. In rare cases you might need to turn it off in order + to force authentication by some non-public-key method such as + passwords. + + This option can also be controlled using the `-noagent' command-line + option. See section 3.8.3.9. + + See chapter 9 for more information about Pageant in general. + +4.23.4 `Attempt TIS or CryptoCard authentication' + + TIS and CryptoCard authentication are (despite their names) generic + forms of simple challenge/response authentication available in SSH + protocol version 1 only. You might use them if you were using S/Key + one-time passwords, for example, or if you had a physical security + token that generated responses to authentication challenges. They + can even be used to prompt for simple passwords. + + With this switch enabled, PuTTY will attempt these forms of + authentication if the server is willing to try them. You will be + presented with a challenge string (which may be different every + time) and must supply the correct response in order to log in. + If your server supports this, you should talk to your system + administrator about precisely what form these challenges and + responses take. + +4.23.5 `Attempt keyboard-interactive authentication' + + The SSH-2 equivalent of TIS authentication is called `keyboard- + interactive'. It is a flexible authentication method using an + arbitrary sequence of requests and responses; so it is not only + useful for challenge/response mechanisms such as S/Key, but it can + also be used for (for example) asking the user for a new password + when the old one has expired. + + PuTTY leaves this option enabled by default, but supplies a switch + to turn it off in case you should have trouble with it. + +4.23.6 `Allow agent forwarding' + + This option allows the SSH server to open forwarded connections back + to your local copy of Pageant. If you are not running Pageant, this + option will do nothing. + + See chapter 9 for general information on Pageant, and section 9.4 + for information on agent forwarding. Note that there is a security + risk involved with enabling this option; see section 9.5 for + details. + +4.23.7 `Allow attempted changes of username in SSH-2' + + In the SSH-1 protocol, it is impossible to change username after + failing to authenticate. So if you mis-type your username at the + PuTTY `login as:' prompt, you will not be able to change it except + by restarting PuTTY. + + The SSH-2 protocol _does_ allow changes of username, in principle, + but does not make it mandatory for SSH-2 servers to accept them. + In particular, OpenSSH does not accept a change of username; once + you have sent one username, it will reject attempts to try to + authenticate as another user. (Depending on the version of OpenSSH, + it may quietly return failure for all login attempts, or it may send + an error message.) + + For this reason, PuTTY will by default not prompt you for your + username more than once, in case the server complains. If you know + your server can cope with it, you can enable the `Allow attempted + changes of username' option to modify PuTTY's behaviour. + +4.23.8 `Private key file for authentication' + + This box is where you enter the name of your private key file if you + are using public key authentication. See chapter 8 for information + about public key authentication in SSH. + + This key must be in PuTTY's native format (`*.PPK'). If you have a + private key in another format that you want to use with PuTTY, see + section 8.2.12. + + You can use the authentication agent Pageant so that you do not need + to explicitly configure a key here; see chapter 9. + + If a private key file is specified here with Pageant running, PuTTY + will first try asking Pageant to authenticate with that key, and + ignore any other keys Pageant may have. If that fails, PuTTY will + ask for a passphrase as normal. You can also specify a _public_ + key file in this case (in RFC 4716 or OpenSSH format), as that's + sufficient to identify the key to Pageant, but of course if Pageant + isn't present PuTTY can't fall back to using this file itself. + + 4.24 The GSSAPI panel + + The `GSSAPI' subpanel of the `Auth' panel controls the use of + GSSAPI authentication. This is a mechanism which delegates the + authentication exchange to a library elsewhere on the client + machine, which in principle can authenticate in many different ways + but in practice is usually used with the Kerberos single sign-on + protocol to implement passwordless login. + + GSSAPI authentication is only available in the SSH-2 protocol. + + PuTTY supports two forms of GSSAPI-based authentication. In one of + them, the SSH key exchange happens in the normal way, and GSSAPI + is only involved in authenticating the user. The checkbox labelled + `Attempt GSSAPI authentication' controls this form. + + In the other method, GSSAPI-based authentication is combined + with the SSH key exchange phase. If this succeeds, then the SSH + authentication step has nothing left to do. See section 4.20.1.1 for + more information about this method. The checkbox labelled `Attempt + GSSAPI key exchange' controls this form. (The same checkbox appears + on the `Kex' panel.) + + If one or both of these controls is enabled, then GSSAPI + authentication will be attempted in one form or the other, and + (typically) if your client machine has valid Kerberos credentials + loaded, then PuTTY should be able to authenticate automatically to + servers that support Kerberos logins. + + If both of those checkboxes are disabled, PuTTY will not try any + form of GSSAPI at all, and the rest of this panel will be unused. + +4.24.1 `Allow GSSAPI credential delegation' + + GSSAPI credential delegation is a mechanism for passing on your + Kerberos (or other) identity to the session on the SSH server. If + you enable this option, then not only will PuTTY be able to log in + automatically to a server that accepts your Kerberos credentials, + but also you will be able to connect out from that server to other + Kerberos-supporting services and use the same credentials just as + automatically. + + (This option is the Kerberos analogue of SSH agent forwarding; see + section 9.4 for some information on that.) + + Note that, like SSH agent forwarding, there is a security + implication in the use of this option: the administrator of + the server you connect to, or anyone else who has cracked the + administrator account on that server, could fake your identity + when connecting to further Kerberos-supporting services. However, + Kerberos sites are typically run by a central authority, so the + administrator of one server is likely to already have access to the + other services too; so this would typically be less of a risk than + SSH agent forwarding. + + If your connection is not using GSSAPI key exchange, it is possible + for the delegation to expire during your session. See section + 4.20.1.1 for more information. + +4.24.2 Preference order for GSSAPI libraries + + GSSAPI is a mechanism which allows more than one authentication + method to be accessed through the same interface. Therefore, more + than one authentication library may exist on your system which can + be accessed using GSSAPI. + + PuTTY contains native support for a few well-known such libraries + (including Windows' SSPI), and will look for all of them on your + system and use whichever it finds. If more than one exists on your + system and you need to use a specific one, you can adjust the order + in which it will search using this preference list control. + + One of the options in the preference list is to use a user-specified + GSSAPI library. If the library you want to use is not mentioned by + name in PuTTY's list of options, you can enter its full pathname in + the `User-supplied GSSAPI library path' field, and move the `User- + supplied GSSAPI library' option in the preference list to make sure + it is selected before anything else. + + On Windows, such libraries are files with a .dll extension, and + must have been built in the same way as the PuTTY executable you're + running; if you have a 32-bit DLL, you must run a 32-bit version + of PuTTY, and the same with 64-bit (see question A.6.10). On Unix, + shared libraries generally have a .so extension. + + 4.25 The TTY panel + + The TTY panel lets you configure the remote pseudo-terminal. + +4.25.1 `Don't allocate a pseudo-terminal' + + When connecting to a Unix system, most interactive shell sessions + are run in a _pseudo-terminal_, which allows the Unix system to + pretend it's talking to a real physical terminal device but allows + the SSH server to catch all the data coming from that fake device + and send it back to the client. + + Occasionally you might find you have a need to run a session _not_ + in a pseudo-terminal. In PuTTY, this is generally only useful for + very specialist purposes; although in Plink (see chapter 7) it is + the usual way of working. + +4.25.2 Sending terminal modes + + The SSH protocol allows the client to send `terminal modes' for + the remote pseudo-terminal. These usually control the server's + expectation of the local terminal's behaviour. + + If your server does not have sensible defaults for these modes, you + may find that changing them here helps, although the server is at + liberty to ignore your changes. If you don't understand any of this, + it's safe to leave these settings alone. + + (None of these settings will have any effect if no pseudo-terminal + is requested or allocated.) + + You can change what happens for a particular mode by selecting it in + the list, choosing one of the options and specifying the exact value + if necessary, and hitting `Set'. The effect of the options is as + follows: + + - If the `Auto' option is selected, the PuTTY tools will decide + whether to specify that mode to the server, and if so, will send + a sensible value. + + PuTTY proper will send modes that it has an opinion on + (currently only the code for the Backspace key, ERASE, and + whether the character set is UTF-8, IUTF8). Plink on Unix will + propagate appropriate modes from the local terminal, if any. + + - If `Nothing' is selected, no value for the mode will be + specified to the server under any circumstances. + + - If a value is specified, it will be sent to the server under all + circumstances. The precise syntax of the value box depends on + the mode. + + By default, all of the available modes are listed as `Auto', which + should do the right thing in most circumstances. + + The precise effect of each setting, if any, is up to the server. + Their names come from POSIX and other Unix systems, and they are + most likely to have a useful effect on such systems. (These are the + same settings that can usually be changed using the `stty' command + once logged in to such servers.) + + Some notable modes are described below; for fuller explanations, see + your server documentation. + + - ERASE is the character that when typed by the user will delete + one space to the left. When set to `Auto' (the default setting), + this follows the setting of the local Backspace key in PuTTY + (see section 4.4.1). + + This and other special characters are specified using `^C' + notation for Ctrl-C, and so on. Use `^<27>' or `^<0x1B>' to + specify a character numerically, and `^~' to get a literal `^'. + Other non-control characters are denoted by themselves. Leaving + the box entirely blank indicates that _no_ character should be + assigned to the specified function, although this may not be + supported by all servers. + + - QUIT is a special character that usually forcefully ends the + current process on the server (SIGQUIT). On many servers its + default setting is Ctrl-backslash (`^\'), which is easy to + accidentally invoke on many keyboards. If this is getting in + your way, you may want to change it to another character or turn + it off entirely. + + - Boolean modes such as ECHO and ICANON can be specified in PuTTY + in a variety of ways, such as true/false, yes/no, and 0/1. + (Explicitly specifying a value of no is different from not + sending the mode at all.) + + - The boolean mode IUTF8 signals to the server whether the + terminal character set is UTF-8 or not, for purposes such as + basic line editing; if this is set incorrectly, the backspace + key may erase the wrong amount of text, for instance. However, + simply setting this is not usually sufficient for the server to + use UTF-8; POSIX servers will generally also require the locale + to be set (by some server-dependent means), although many newer + installations default to UTF-8. Also, since this mode was added + to the SSH protocol much later than the others, many servers + (particularly older servers) do not honour this mode sent over + SSH; indeed, a few poorly-written servers object to its mere + presence, so you may find you need to set it to not be sent + at all. When set to `Auto', this follows the local configured + character set (see section 4.10.1). + + - Terminal speeds are configured elsewhere; see section 4.15.4. + + 4.26 The X11 panel + + The X11 panel allows you to configure forwarding of X11 over an SSH + connection. + + If your server lets you run X Window System graphical applications, + X11 forwarding allows you to securely give those applications access + to a local X display on your PC. + + To enable X11 forwarding, check the `Enable X11 forwarding' box. + If your X display is somewhere unusual, you will need to enter its + location in the `X display location' box; if this is left blank, + PuTTY will try to find a sensible default in the environment, or use + the primary local display (`:0') if that fails. + + See section 3.4 for more information about X11 forwarding. + +4.26.1 Remote X11 authentication + + If you are using X11 forwarding, the virtual X server created on the + SSH server machine will be protected by authorisation data. This + data is invented, and checked, by PuTTY. + + The usual authorisation method used for this is called MIT-MAGIC- + COOKIE-1. This is a simple password-style protocol: the X client + sends some cookie data to the server, and the server checks that it + matches the real cookie. The cookie data is sent over an unencrypted + X11 connection; so if you allow a client on a third machine to + access the virtual X server, then the cookie will be sent in the + clear. + + PuTTY offers the alternative protocol XDM-AUTHORIZATION-1. This is + a cryptographically authenticated protocol: the data sent by the X + client is different every time, and it depends on the IP address + and port of the client's end of the connection and is also stamped + with the current time. So an eavesdropper who captures an XDM- + AUTHORIZATION-1 string cannot immediately re-use it for their own X + connection. + + PuTTY's support for XDM-AUTHORIZATION-1 is a somewhat experimental + feature, and may encounter several problems: + + - Some X clients probably do not even support XDM-AUTHORIZATION- + 1, so they will not know what to do with the data PuTTY has + provided. + + - This authentication mechanism will only work in SSH-2. In SSH- + 1, the SSH server does not tell the client the source address + of a forwarded connection in a machine-readable format, so it's + impossible to verify the XDM-AUTHORIZATION-1 data. + + - You may find this feature causes problems with some SSH servers, + which will not clean up XDM-AUTHORIZATION-1 data after a + session, so that if you then connect to the same server using + a client which only does MIT-MAGIC-COOKIE-1 and are allocated + the same remote display number, you might find that out-of-date + authentication data is still present on your server and your X + connections fail. + + PuTTY's default is MIT-MAGIC-COOKIE-1. If you change it, you should + be sure you know what you're doing. + +4.26.2 X authority file for local display + + If you are using X11 forwarding, the local X server to which your + forwarded connections are eventually directed may itself require + authorisation. + + Some Windows X servers do not require this: they do authorisation + by simpler means, such as accepting any connection from the local + machine but not from anywhere else. However, if your X server does + require authorisation, then PuTTY needs to know what authorisation + is required. + + One way in which this data might be made available is for the X + server to store it somewhere in a file which has the same format + as the Unix `.Xauthority' file. If this is how your Windows X + server works, then you can tell PuTTY where to find this file by + configuring this option. By default, PuTTY will not attempt to find + any authorisation for your local display. + + 4.27 The Tunnels panel + + The Tunnels panel allows you to configure tunnelling of arbitrary + connection types through an SSH connection. + + Port forwarding allows you to tunnel other types of network + connection down an SSH session. See section 3.5 for a general + discussion of port forwarding and how it works. + + The port forwarding section in the Tunnels panel shows a list of all + the port forwardings that PuTTY will try to set up when it connects + to the server. By default no port forwardings are set up, so this + list is empty. + + To add a port forwarding: + + - Set one of the `Local' or `Remote' radio buttons, depending on + whether you want to forward a local port to a remote destination + (`Local') or forward a remote port to a local destination + (`Remote'). Alternatively, select `Dynamic' if you want PuTTY to + provide a local SOCKS 4/4A/5 proxy on a local port (note that + this proxy only supports TCP connections; the SSH protocol does + not support forwarding UDP). + + - Enter a source port number into the `Source port' box. For local + forwardings, PuTTY will listen on this port of your PC. For + remote forwardings, your SSH server will listen on this port of + the remote machine. Note that most servers will not allow you to + listen on port numbers less than 1024. + + - If you have selected `Local' or `Remote' (this step is not + needed with `Dynamic'), enter a hostname and port number + separated by a colon, in the `Destination' box. Connections + received on the source port will be directed to this + destination. For example, to connect to a POP-3 server, you + might enter `popserver.example.com:110'. (If you need to enter + a literal IPv6 address, enclose it in square brackets, for + instance `[::1]:2200'.) + + - Click the `Add' button. Your forwarding details should appear in + the list box. + + To remove a port forwarding, simply select its details in the list + box, and click the `Remove' button. + + In the `Source port' box, you can also optionally enter an IP + address to listen on, by specifying (for instance) `127.0.0.5:79'. + See section 3.5 for more information on how this works and its + restrictions. + + In place of port numbers, you can enter service names, if they are + known to the local system. For instance, in the `Destination' box, + you could enter `popserver.example.com:pop3'. + + You can modify the currently active set of port forwardings in mid- + session using `Change Settings' (see section 3.1.3.4). If you delete + a local or dynamic port forwarding in mid-session, PuTTY will stop + listening for connections on that port, so it can be re-used by + another program. If you delete a remote port forwarding, note that: + + - The SSH-1 protocol contains no mechanism for asking the server + to stop listening on a remote port. + + - The SSH-2 protocol does contain such a mechanism, but not all + SSH servers support it. (In particular, OpenSSH does not support + it in any version earlier than 3.9.) + + If you ask to delete a remote port forwarding and PuTTY cannot make + the server actually stop listening on the port, it will instead + just start refusing incoming connections on that port. Therefore, + although the port cannot be reused by another program, you can at + least be reasonably sure that server-side programs can no longer + access the service at your end of the port forwarding. + + If you delete a forwarding, any existing connections established + using that forwarding remain open. Similarly, changes to global + settings such as `Local ports accept connections from other hosts' + only take effect on new forwardings. + + If the connection you are forwarding over SSH is itself a second + SSH connection made by another copy of PuTTY, you might find the + `logical host name' configuration option useful to warn PuTTY of + which host key it should be expecting. See section 4.14.5 for + details of this. + +4.27.1 Controlling the visibility of forwarded ports + + The source port for a forwarded connection usually does not accept + connections from any machine except the SSH client or server machine + itself (for local and remote forwardings respectively). There are + controls in the Tunnels panel to change this: + + - The `Local ports accept connections from other hosts' option + allows you to set up local-to-remote port forwardings in such a + way that machines other than your client PC can connect to the + forwarded port. (This also applies to dynamic SOCKS forwarding.) + + - The `Remote ports do the same' option does the same thing for + remote-to-local port forwardings (so that machines other than + the SSH server machine can connect to the forwarded port.) Note + that this feature is only available in the SSH-2 protocol, and + not all SSH-2 servers support it (OpenSSH 3.0 does not, for + example). + +4.27.2 Selecting Internet protocol version for forwarded ports + + This switch allows you to select a specific Internet protocol (IPv4 + or IPv6) for the local end of a forwarded port. By default, it is + set on `Auto', which means that: + + - for a local-to-remote port forwarding, PuTTY will listen for + incoming connections in both IPv4 and (if available) IPv6 + + - for a remote-to-local port forwarding, PuTTY will choose a + sensible protocol for the outgoing connection. + + This overrides the general Internet protocol version preference on + the Connection panel (see section 4.14.4). + + Note that some operating systems may listen for incoming connections + in IPv4 even if you specifically asked for IPv6, because their IPv4 + and IPv6 protocol stacks are linked together. Apparently Linux does + this, and Windows does not. So if you're running PuTTY on Windows + and you tick `IPv6' for a local or dynamic port forwarding, it will + _only_ be usable by connecting to it using IPv6; whereas if you do + the same on Linux, you can also use it with IPv4. However, ticking + `Auto' should always give you a port which you can connect to using + either protocol. + + 4.28 The Bugs and More Bugs panels + + Not all SSH servers work properly. Various existing servers have + bugs in them, which can make it impossible for a client to talk to + them unless it knows about the bug and works around it. + + Since most servers announce their software version number at the + beginning of the SSH connection, PuTTY will attempt to detect which + bugs it can expect to see in the server and automatically enable + workarounds. However, sometimes it will make mistakes; if the server + has been deliberately configured to conceal its version number, or + if the server is a version which PuTTY's bug database does not know + about, then PuTTY will not know what bugs to expect. + + The Bugs and More Bugs panels (there are two because we have so many + bug compatibility modes) allow you to manually configure the bugs + PuTTY expects to see in the server. Each bug can be configured in + three states: + + - `Off': PuTTY will assume the server does not have the bug. + + - `On': PuTTY will assume the server _does_ have the bug. + + - `Auto': PuTTY will use the server's version number announcement + to try to guess whether or not the server has the bug. + +4.28.1 `Chokes on SSH-2 ignore messages' + + An ignore message (SSH_MSG_IGNORE) is a message in the SSH protocol + which can be sent from the client to the server, or from the server + to the client, at any time. Either side is required to ignore the + message whenever it receives it. PuTTY uses ignore messages in + SSH-2 to confuse the encrypted data stream and make it harder to + cryptanalyse. It also uses ignore messages for connection keepalives + (see section 4.14.1). + + If it believes the server to have this bug, PuTTY will stop using + ignore messages. If this bug is enabled when talking to a correct + server, the session will succeed, but keepalives will not work and + the session might be less cryptographically secure than it could be. + +4.28.2 `Handles SSH-2 key re-exchange badly' + + Some SSH servers cannot cope with repeat key exchange at all, and + will ignore attempts by the client to start one. Since PuTTY pauses + the session while performing a repeat key exchange, the effect of + this would be to cause the session to hang after an hour (unless + you have your rekey timeout set differently; see section 4.20.2 for + more about rekeys). Other, very old, SSH servers handle repeat key + exchange even more badly, and disconnect upon receiving a repeat key + exchange request. + + If this bug is detected, PuTTY will never initiate a repeat key + exchange. If this bug is enabled when talking to a correct server, + the session should still function, but may be less secure than you + would expect. + + This is an SSH-2-specific bug. + +4.28.3 `Chokes on PuTTY's SSH-2 `winadj' requests' + + PuTTY sometimes sends a special request to SSH servers in the middle + of channel data, with the name winadj@putty.projects.tartarus.org + (see section F.1). The purpose of this request is to measure the + round-trip time to the server, which PuTTY uses to tune its flow + control. The server does not actually have to _understand_ the + message; it is expected to send back a SSH_MSG_CHANNEL_FAILURE + message indicating that it didn't understand it. (All PuTTY needs + for its timing calculations is _some_ kind of response.) + + It has been known for some SSH servers to get confused by this + message in one way or another - because it has a long name, or + because they can't cope with unrecognised request names even to the + extent of sending back the correct failure response, or because they + handle it sensibly but fill up the server's log file with pointless + spam, or whatever. PuTTY therefore supports this bug-compatibility + flag: if it believes the server has this bug, it will never send + its `winadj@putty.projects.tartarus.org' request, and will make do + without its timing data. + +4.28.4 `Replies to requests on closed channels' + + The SSH protocol as published in RFC 4254 has an ambiguity which + arises if one side of a connection tries to close a channel, while + the other side simultaneously sends a request within the channel and + asks for a reply. RFC 4254 leaves it unclear whether the closing + side should reply to the channel request after having announced its + intention to close the channel. + + Discussion on the ietf-ssh mailing list in April 2014 formed a clear + consensus that the right answer is no. However, because of the + ambiguity in the specification, some SSH servers have implemented + the other policy; for example, OpenSSH used to until it was fixed. + + Because PuTTY sends channel requests with the `want reply' + flag throughout channels' lifetime (see section 4.28.3), it's + possible that when connecting to such a server it might receive + a reply to a request after it thinks the channel has entirely + closed, and terminate with an error along the lines of `Received + SSH2_MSG_CHANNEL_FAILURE for nonexistent channel 256'. + +4.28.5 `Ignores SSH-2 maximum packet size' + + When an SSH-2 channel is set up, each end announces the maximum size + of data packet that it is willing to receive for that channel. Some + servers ignore PuTTY's announcement and send packets larger than + PuTTY is willing to accept, causing it to report `Incoming packet + was garbled on decryption'. + + If this bug is detected, PuTTY never allows the channel's flow- + control window to grow large enough to allow the server to send an + over-sized packet. If this bug is enabled when talking to a correct + server, the session will work correctly, but download performance + will be less than it could be. + +4.28.6 `Requires padding on SSH-2 RSA signatures' + + Versions below 3.3 of OpenSSH require SSH-2 RSA signatures to be + padded with zero bytes to the same length as the RSA key modulus. + The SSH-2 specification says that an unpadded signature MUST be + accepted, so this is a bug. A typical symptom of this problem is + that PuTTY mysteriously fails RSA authentication once in every few + hundred attempts, and falls back to passwords. + + If this bug is detected, PuTTY will pad its signatures in the way + OpenSSH expects. If this bug is enabled when talking to a correct + server, it is likely that no damage will be done, since correct + servers usually still accept padded signatures because they're used + to talking to OpenSSH. + + This is an SSH-2-specific bug. + +4.28.7 `Only supports pre-RFC4419 SSH-2 DH GEX' + + The SSH key exchange method that uses Diffie-Hellman group exchange + was redesigned after its original release, to use a slightly more + sophisticated setup message. Almost all SSH implementations switched + over to the new version. (PuTTY was one of the last.) A few old + servers still only support the old one. + + If this bug is detected, and the client and server negotiate Diffie- + Hellman group exchange, then PuTTY will send the old message now + known as SSH2_MSG_KEX_DH_GEX_REQUEST_OLD in place of the new + SSH2_MSG_KEX_DH_GEX_REQUEST. + + This is an SSH-2-specific bug. + +4.28.8 `Miscomputes SSH-2 HMAC keys' + + Versions 2.3.0 and below of the SSH server software from ssh.com + compute the keys for their HMAC message authentication codes + incorrectly. A typical symptom of this problem is that PuTTY dies + unexpectedly at the beginning of the session, saying `Incorrect MAC + received on packet'. + + If this bug is detected, PuTTY will compute its HMAC keys in the + same way as the buggy server, so that communication will still be + possible. If this bug is enabled when talking to a correct server, + communication will fail. + + This is an SSH-2-specific bug. + +4.28.9 `Misuses the session ID in SSH-2 PK auth' + + Versions below 2.3 of OpenSSH require SSH-2 public-key + authentication to be done slightly differently: the data to be + signed by the client contains the session ID formatted in a + different way. If public-key authentication mysteriously does + not work but the Event Log (see section 3.1.3.1) thinks it has + successfully sent a signature, it might be worth enabling the + workaround for this bug to see if it helps. + + If this bug is detected, PuTTY will sign data in the way OpenSSH + expects. If this bug is enabled when talking to a correct server, + SSH-2 public-key authentication will fail. + + This is an SSH-2-specific bug. + +4.28.10 `Miscomputes SSH-2 encryption keys' + + Versions below 2.0.11 of the SSH server software from ssh.com + compute the keys for the session encryption incorrectly. This + problem can cause various error messages, such as `Incoming packet + was garbled on decryption', or possibly even `Out of memory'. + + If this bug is detected, PuTTY will compute its encryption keys + in the same way as the buggy server, so that communication will + still be possible. If this bug is enabled when talking to a correct + server, communication will fail. + + This is an SSH-2-specific bug. + +4.28.11 `Chokes on SSH-1 ignore messages' + + An ignore message (SSH_MSG_IGNORE) is a message in the SSH protocol + which can be sent from the client to the server, or from the server + to the client, at any time. Either side is required to ignore the + message whenever it receives it. PuTTY uses ignore messages to hide + the password packet in SSH-1, so that a listener cannot tell the + length of the user's password; it also uses ignore messages for + connection keepalives (see section 4.14.1). + + If this bug is detected, PuTTY will stop using ignore messages. + This means that keepalives will stop working, and PuTTY will + have to fall back to a secondary defence against SSH-1 password- + length eavesdropping. See section 4.28.12. If this bug is enabled + when talking to a correct server, the session will succeed, but + keepalives will not work and the session might be more vulnerable to + eavesdroppers than it could be. + +4.28.12 `Refuses all SSH-1 password camouflage' + + When talking to an SSH-1 server which cannot deal with ignore + messages (see section 4.28.11), PuTTY will attempt to disguise the + length of the user's password by sending additional padding _within_ + the password packet. This is technically a violation of the SSH- + 1 specification, and so PuTTY will only do it when it cannot use + standards-compliant ignore messages as camouflage. In this sense, + for a server to refuse to accept a padded password packet is not + really a bug, but it does make life inconvenient if the server can + also not handle ignore messages. + + If this `bug' is detected, PuTTY will assume that neither ignore + messages nor padding are acceptable, and that it thus has no choice + but to send the user's password with no form of camouflage, so + that an eavesdropping user will be easily able to find out the + exact length of the password. If this bug is enabled when talking + to a correct server, the session will succeed, but will be more + vulnerable to eavesdroppers than it could be. + + This is an SSH-1-specific bug. SSH-2 is secure against this type of + attack. + +4.28.13 `Chokes on SSH-1 RSA authentication' + + Some SSH-1 servers cannot deal with RSA authentication messages at + all. If Pageant is running and contains any SSH-1 keys, PuTTY will + normally automatically try RSA authentication before falling back + to passwords, so these servers will crash when they see the RSA + attempt. + + If this bug is detected, PuTTY will go straight to password + authentication. If this bug is enabled when talking to a correct + server, the session will succeed, but of course RSA authentication + will be impossible. + + This is an SSH-1-specific bug. + + 4.29 The Serial panel + + The Serial panel allows you to configure options that only apply + when PuTTY is connecting to a local serial line. + +4.29.1 Selecting a serial line to connect to + + The `Serial line to connect to' box allows you to choose which + serial line you want PuTTY to talk to, if your computer has more + than one serial port. + + On Windows, the first serial line is called COM1, and if there is a + second it is called COM2, and so on. + + This configuration setting is also visible on the Session panel, + where it replaces the `Host Name' box (see section 4.1.1) if the + connection type is set to `Serial'. + +4.29.2 Selecting the speed of your serial line + + The `Speed' box allows you to choose the speed (or `baud rate') at + which to talk to the serial line. Typical values might be 9600, + 19200, 38400 or 57600. Which one you need will depend on the device + at the other end of the serial cable; consult the manual for that + device if you are in doubt. + + This configuration setting is also visible on the Session panel, + where it replaces the `Port' box (see section 4.1.1) if the + connection type is set to `Serial'. + +4.29.3 Selecting the number of data bits + + The `Data bits' box allows you to choose how many data bits are + transmitted in each byte sent or received through the serial line. + Typical values are 7 or 8. + +4.29.4 Selecting the number of stop bits + + The `Stop bits' box allows you to choose how many stop bits are used + in the serial line protocol. Typical values are 1, 1.5 or 2. + +4.29.5 Selecting the serial parity checking scheme + + The `Parity' box allows you to choose what type of parity checking + is used on the serial line. The settings are: + + - `None': no parity bit is sent at all. + + - `Odd': an extra parity bit is sent alongside each byte, and + arranged so that the total number of 1 bits is odd. + + - `Even': an extra parity bit is sent alongside each byte, and + arranged so that the total number of 1 bits is even. + + - `Mark': an extra parity bit is sent alongside each byte, and + always set to 1. + + - `Space': an extra parity bit is sent alongside each byte, and + always set to 0. + +4.29.6 Selecting the serial flow control scheme + + The `Flow control' box allows you to choose what type of flow + control checking is used on the serial line. The settings are: + + - `None': no flow control is done. Data may be lost if either side + attempts to send faster than the serial line permits. + + - `XON/XOFF': flow control is done by sending XON and XOFF + characters within the data stream. + + - `RTS/CTS': flow control is done using the RTS and CTS wires on + the serial line. + + - `DSR/DTR': flow control is done using the DSR and DTR wires on + the serial line. + + 4.30 Storing configuration in a file + + PuTTY does not currently support storing its configuration in a file + instead of the Registry. However, you can work around this with a + couple of batch files. + + You will need a file called (say) `PUTTY.BAT' which imports the + contents of a file into the Registry, then runs PuTTY, exports + the contents of the Registry back into the file, and deletes the + Registry entries. This can all be done using the Regedit command + line options, so it's all automatic. Here is what you need in + `PUTTY.BAT': + + @ECHO OFF + regedit /s putty.reg + regedit /s puttyrnd.reg + start /w putty.exe + regedit /ea new.reg HKEY_CURRENT_USER\Software\SimonTatham\PuTTY + copy new.reg putty.reg + del new.reg + regedit /s puttydel.reg + + This batch file needs two auxiliary files: `PUTTYRND.REG' which sets + up an initial safe location for the `PUTTY.RND' random seed file, + and `PUTTYDEL.REG' which destroys everything in the Registry once + it's been successfully saved back to the file. + + Here is `PUTTYDEL.REG': + + REGEDIT4 + + [-HKEY_CURRENT_USER\Software\SimonTatham\PuTTY] + + Here is an example `PUTTYRND.REG' file: + + REGEDIT4 + + [HKEY_CURRENT_USER\Software\SimonTatham\PuTTY] + "RandSeedFile"="a:\\putty.rnd" + + You should replace `a:\putty.rnd' with the location where you want + to store your random number data. If the aim is to carry around + PuTTY and its settings on one USB stick, you probably want to store + it on the USB stick. + +Chapter 5: Using PSCP to transfer files securely +------------------------------------------------ + + PSCP, the PuTTY Secure Copy client, is a tool for transferring files + securely between computers using an SSH connection. + + If you have an SSH-2 server, you might prefer PSFTP (see chapter + 6) for interactive use. PSFTP does not in general work with SSH-1 + servers, however. + + 5.1 Starting PSCP + + PSCP is a command line application. This means that you cannot just + double-click on its icon to run it and instead you have to bring up + a console window. With Windows 95, 98, and ME, this is called an + `MS-DOS Prompt' and with Windows NT, 2000, and XP, it is called a + `Command Prompt'. It should be available from the Programs section + of your Start Menu. + + To start PSCP it will need either to be on your `PATH' or in your + current directory. To add the directory containing PSCP to your + `PATH' environment variable, type into the console window: + + set PATH=C:\path\to\putty\directory;%PATH% + + This will only work for the lifetime of that particular console + window. To set your `PATH' more permanently on Windows NT, 2000, and + XP, use the Environment tab of the System Control Panel. On Windows + 95, 98, and ME, you will need to edit your `AUTOEXEC.BAT' to include + a `set' command like the one above. + + 5.2 PSCP Usage + + Once you've got a console window to type into, you can just type + `pscp' on its own to bring up a usage message. This tells you the + version of PSCP you're using, and gives you a brief summary of how + to use PSCP: + + Z:\owendadmin>pscp + PuTTY Secure Copy client + Release 0.72 + Usage: pscp [options] [user@]host:source target + pscp [options] source [source...] [user@]host:target + pscp [options] -ls [user@]host:filespec + Options: + -V print version information and exit + -pgpfp print PGP key fingerprints and exit + -p preserve file attributes + -q quiet, don't show statistics + -r copy directories recursively + -v show verbose messages + -load sessname Load settings from saved session + -P port connect to specified port + -l user connect with specified username + -pw passw login with specified password + -1 -2 force use of particular SSH protocol version + -4 -6 force use of IPv4 or IPv6 + -C enable compression + -i key private key file for user authentication + -noagent disable use of Pageant + -agent enable use of Pageant + -hostkey aa:bb:cc:... + manually specify a host key (may be repeated) + -batch disable all interactive prompts + -no-sanitise-stderr don't strip control chars from standard error + -proxycmd command + use 'command' as local proxy + -unsafe allow server-side wildcards (DANGEROUS) + -sftp force use of SFTP protocol + -scp force use of SCP protocol + -sshlog file + -sshrawlog file + log protocol details to a file + + (PSCP's interface is much like the Unix `scp' command, if you're + familiar with that.) + + 5.2.1 The basics + + To receive (a) file(s) from a remote server: + + pscp [options] [user@]host:source target + + So to copy the file `/etc/hosts' from the server `example.com' as + user `fred' to the file `c:\temp\example-hosts.txt', you would type: + + pscp fred@example.com:/etc/hosts c:\temp\example-hosts.txt + + To send (a) file(s) to a remote server: + + pscp [options] source [source...] [user@]host:target + + So to copy the local file `c:\documents\foo.txt' to the server + `example.com' as user `fred' to the file `/tmp/foo' you would type: + + pscp c:\documents\foo.txt fred@example.com:/tmp/foo + + You can use wildcards to transfer multiple files in either + direction, like this: + + pscp c:\documents\*.doc fred@example.com:docfiles + pscp fred@example.com:source/*.c c:\source + + However, in the second case (using a wildcard for multiple remote + files) you may see a warning saying something like `warning: remote + host tried to write to a file called `terminal.c' when we requested + a file called `*.c'. If this is a wildcard, consider upgrading to + SSH-2 or using the `-unsafe' option. Renaming of this file has been + disallowed'. + + This is due to a fundamental insecurity in the old-style SCP + protocol: the client sends the wildcard string (`*.c') to the + server, and the server sends back a sequence of file names that + match the wildcard pattern. However, there is nothing to stop the + server sending back a _different_ pattern and writing over one of + your other files: if you request `*.c', the server might send back + the file name `AUTOEXEC.BAT' and install a virus for you. Since the + wildcard matching rules are decided by the server, the client cannot + reliably verify that the filenames sent back match the pattern. + + PSCP will attempt to use the newer SFTP protocol (part of SSH-2) + where possible, which does not suffer from this security flaw. If + you are talking to an SSH-2 server which supports SFTP, you will + never see this warning. (You can force use of the SFTP protocol, if + available, with `-sftp' - see section 5.2.2.6.) + + If you really need to use a server-side wildcard with an SSH-1 + server, you can use the `-unsafe' command line option with PSCP: + + pscp -unsafe fred@example.com:source/*.c c:\source + + This will suppress the warning message and the file transfer will + happen. However, you should be aware that by using this option you + are giving the server the ability to write to _any_ file in the + target directory, so you should only use this option if you trust + the server administrator not to be malicious (and not to let the + server machine be cracked by malicious people). Alternatively, do + any such download in a newly created empty directory. (Even in + `unsafe' mode, PSCP will still protect you against the server trying + to get out of that directory using pathnames including `..'.) + +5.2.1.1 `user' + + The login name on the remote server. If this is omitted, and `host' + is a PuTTY saved session, PSCP will use any username specified by + that saved session. Otherwise, PSCP will attempt to use the local + Windows username. + +5.2.1.2 `host' + + The name of the remote server, or the name of an existing PuTTY + saved session. In the latter case, the session's settings for + hostname, port number, cipher type and username will be used. + +5.2.1.3 `source' + + One or more source files. Wildcards are allowed. The syntax of + wildcards depends on the system to which they apply, so if you are + copying _from_ a Windows system _to_ a UNIX system, you should use + Windows wildcard syntax (e.g. `*.*'), but if you are copying _from_ + a UNIX system _to_ a Windows system, you would use the wildcard + syntax allowed by your UNIX shell (e.g. `*'). + + If the source is a remote server and you do not specify a full + pathname (in UNIX, a pathname beginning with a `/' (slash) + character), what you specify as a source will be interpreted + relative to your home directory on the remote server. + +5.2.1.4 `target' + + The filename or directory to put the file(s). When copying from a + remote server to a local host, you may wish simply to place the + file(s) in the current directory. To do this, you should specify a + target of `.'. For example: + + pscp fred@example.com:/home/tom/.emacs . + + ...would copy `/home/tom/.emacs' on the remote server to the current + directory. + + As with the `source' parameter, if the target is on a remote server + and is not a full path name, it is interpreted relative to your home + directory on the remote server. + + 5.2.2 Options + + PSCP accepts all the general command line options supported by the + PuTTY tools, except the ones which make no sense in a file transfer + utility. See section 3.8.3 for a description of these options. (The + ones not supported by PSCP are clearly marked.) + + PSCP also supports some of its own options. The following sections + describe PSCP's specific command-line options. + +5.2.2.1 `-ls' list remote files + + If the `-ls' option is given, no files are transferred; instead, + remote files are listed. Only a hostname specification and optional + remote file specification need be given. For example: + + pscp -ls fred@example.com:dir1 + + The SCP protocol does not contain within itself a means of listing + files. If SCP is in use, this option therefore assumes that the + server responds appropriately to the command `ls -la'; this may not + work with all servers. + + If SFTP is in use, this option should work with all servers. + +5.2.2.2 `-p' preserve file attributes + + By default, files copied with PSCP are timestamped with the date + and time they were copied. The `-p' option preserves the original + timestamp on copied files. + +5.2.2.3 `-q' quiet, don't show statistics + + By default, PSCP displays a meter displaying the progress of the + current transfer: + + mibs.tar | 168 kB | 84.0 kB/s | ETA: 00:00:13 | 13% + + The fields in this display are (from left to right), filename, size + (in kilobytes) of file transferred so far, estimate of how fast the + file is being transferred (in kilobytes per second), estimated time + that the transfer will be complete, and percentage of the file so + far transferred. The `-q' option to PSCP suppresses the printing of + these statistics. + +5.2.2.4 `-r' copies directories recursively + + By default, PSCP will only copy files. Any directories you specify + to copy will be skipped, as will their contents. The `-r' option + tells PSCP to descend into any directories you specify, and to copy + them and their contents. This allows you to use PSCP to transfer + whole directory structures between machines. + +5.2.2.5 `-batch' avoid interactive prompts + + If you use the `-batch' option, PSCP will never give an interactive + prompt while establishing the connection. If the server's host key + is invalid, for example (see section 2.2), then the connection will + simply be abandoned instead of asking you what to do next. + + This may help PSCP's behaviour when it is used in automated scripts: + using `-batch', if something goes wrong at connection time, the + batch job will fail rather than hang. + +5.2.2.6 `-sftp', `-scp' force use of particular protocol + + As mentioned in section 5.2.1, there are two different file transfer + protocols in use with SSH. Despite its name, PSCP (like many other + ostensible scp clients) can use either of these protocols. + + The older SCP protocol does not have a written specification and + leaves a lot of detail to the server platform. Wildcards are + expanded on the server. The simple design means that any wildcard + specification supported by the server platform (such as brace + expansion) can be used, but also leads to interoperability issues + such as with filename quoting (for instance, where filenames contain + spaces), and also the security issue described in section 5.2.1. + + The newer SFTP protocol, which is usually associated with SSH- + 2 servers, is specified in a more platform independent way, and + leaves issues such as wildcard syntax up to the client. (PuTTY's + SFTP wildcard syntax is described in section 6.2.2.) This makes it + more consistent across platforms, more suitable for scripting and + automation, and avoids security issues with wildcard matching. + + Normally PSCP will attempt to use the SFTP protocol, and only fall + back to the SCP protocol if SFTP is not available on the server. + + The `-scp' option forces PSCP to use the SCP protocol or quit. + + The `-sftp' option forces PSCP to use the SFTP protocol or quit. + When this option is specified, PSCP looks harder for an SFTP server, + which may allow use of SFTP with SSH-1 depending on server setup. + +5.2.2.7 `-no-sanitise-stderr': control error message sanitisation + + The `-no-sanitise-stderr' option will cause PSCP to pass through the + server's standard-error stream literally, without stripping control + characters from it first. This might be useful if the server were + sending coloured error messages, but it also gives the server the + ability to have unexpected effects on your terminal display. For + more discussion, see section 7.2.3.5. + + 5.2.3 Return value + + PSCP returns an ERRORLEVEL of zero (success) only if the files were + correctly transferred. You can test for this in a batch file, using + code such as this: + + pscp file*.* user@hostname: + if errorlevel 1 echo There was an error + + 5.2.4 Using public key authentication with PSCP + + Like PuTTY, PSCP can authenticate using a public key instead of a + password. There are three ways you can do this. + + Firstly, PSCP can use PuTTY saved sessions in place of hostnames + (see section 5.2.1.2). So you would do this: + + - Run PuTTY, and create a PuTTY saved session (see section 4.1.2) + which specifies your private key file (see section 4.23.8). You + will probably also want to specify a username to log in as (see + section 4.15.1). + + - In PSCP, you can now use the name of the session instead of + a hostname: type `pscp sessionname:file localfile', where + `sessionname' is replaced by the name of your saved session. + + Secondly, you can supply the name of a private key file on the + command line, with the `-i' option. See section 3.8.3.18 for more + information. + + Thirdly, PSCP will attempt to authenticate using Pageant if Pageant + is running (see chapter 9). So you would do this: + + - Ensure Pageant is running, and has your private key stored in + it. + + - Specify a user and host name to PSCP as normal. PSCP will + automatically detect Pageant and try to use the keys within it. + + For more general information on public-key authentication, see + chapter 8. + +Chapter 6: Using PSFTP to transfer files securely +------------------------------------------------- + + PSFTP, the PuTTY SFTP client, is a tool for transferring files + securely between computers using an SSH connection. + + PSFTP differs from PSCP in the following ways: + + - PSCP should work on virtually every SSH server. PSFTP uses the + new SFTP protocol, which is a feature of SSH-2 only. (PSCP + will also use this protocol if it can, but there is an SSH-1 + equivalent it can fall back to if it cannot.) + + - PSFTP allows you to run an interactive file transfer session, + much like the Windows `ftp' program. You can list the contents + of directories, browse around the file system, issue multiple + `get' and `put' commands, and eventually log out. By contrast, + PSCP is designed to do a single file transfer operation and + immediately terminate. + + 6.1 Starting PSFTP + + The usual way to start PSFTP is from a command prompt, much like + PSCP. To do this, it will need either to be on your `PATH' or in + your current directory. To add the directory containing PSFTP to + your `PATH' environment variable, type into the console window: + + set PATH=C:\path\to\putty\directory;%PATH% + + Unlike PSCP, however, PSFTP has no complex command-line syntax; you + just specify a host name and perhaps a user name: + + psftp server.example.com + + or perhaps + + psftp fred@server.example.com + + Alternatively, if you just type `psftp' on its own (or double-click + the PSFTP icon in the Windows GUI), you will see the PSFTP prompt, + and a message telling you PSFTP has not connected to any server: + + C:\>psftp + psftp: no hostname specified; use "open host.name" to connect + psftp> + + At this point you can type `open server.example.com' or + `open fred@server.example.com' to start a session. + + PSFTP accepts all the general command line options supported by the + PuTTY tools, except the ones which make no sense in a file transfer + utility. See section 3.8.3 for a description of these options. (The + ones not supported by PSFTP are clearly marked.) + + PSFTP also supports some of its own options. The following sections + describe PSFTP's specific command-line options. + + 6.1.1 `-b': specify a file containing batch commands + + In normal operation, PSFTP is an interactive program which displays + a command line and accepts commands from the keyboard. + + If you need to do automated tasks with PSFTP, you would probably + prefer to specify a set of commands in advance and have them + executed automatically. The `-b' option allows you to do this. You + use it with a file name containing batch commands. For example, you + might create a file called `myscript.scr' containing lines like + this: + + cd /home/ftp/users/jeff + del jam-old.tar.gz + ren jam.tar.gz jam-old.tar.gz + put jam.tar.gz + chmod a+r jam.tar.gz + + and then you could run the script by typing + + psftp user@hostname -b myscript.scr + + When you run a batch script in this way, PSFTP will abort the script + if any command fails to complete successfully. To change this + behaviour, you can add the `-be' option (section 6.1.3). + + PSFTP will terminate after it finishes executing the batch script. + + 6.1.2 `-bc': display batch commands as they are run + + The `-bc' option alters what PSFTP displays while processing a + batch script specified with `-b'. With the `-bc' option, PSFTP will + display prompts and commands just as if the commands had been typed + at the keyboard. So instead of seeing this: + + C:\>psftp fred@hostname -b batchfile + Sent username "fred" + Remote working directory is /home/fred + Listing directory /home/fred/lib + drwxrwsr-x 4 fred fred 1024 Sep 6 10:42 . + drwxr-sr-x 25 fred fred 2048 Dec 14 09:36 .. + drwxrwsr-x 3 fred fred 1024 Apr 17 2000 jed + lrwxrwxrwx 1 fred fred 24 Apr 17 2000 timber + drwxrwsr-x 2 fred fred 1024 Mar 13 2000 trn + + you might see this: + + C:\>psftp fred@hostname -bc -b batchfile + Sent username "fred" + Remote working directory is /home/fred + psftp> dir lib + Listing directory /home/fred/lib + drwxrwsr-x 4 fred fred 1024 Sep 6 10:42 . + drwxr-sr-x 25 fred fred 2048 Dec 14 09:36 .. + drwxrwsr-x 3 fred fred 1024 Apr 17 2000 jed + lrwxrwxrwx 1 fred fred 24 Apr 17 2000 timber + drwxrwsr-x 2 fred fred 1024 Mar 13 2000 trn + psftp> quit + + 6.1.3 `-be': continue batch processing on errors + + When running a batch file, this additional option causes PSFTP + to continue processing even if a command fails to complete + successfully. + + You might want this to happen if you wanted to delete a file and + didn't care if it was already not present, for example. + + 6.1.4 `-batch': avoid interactive prompts + + If you use the `-batch' option, PSFTP will never give an interactive + prompt while establishing the connection. If the server's host key + is invalid, for example (see section 2.2), then the connection will + simply be abandoned instead of asking you what to do next. + + This may help PSFTP's behaviour when it is used in automated + scripts: using `-batch', if something goes wrong at connection time, + the batch job will fail rather than hang. + +6.1.4.1 `-no-sanitise-stderr': control error message sanitisation + + The `-no-sanitise-stderr' option will cause PSFTP to pass through + the server's standard-error stream literally, without stripping + control characters from it first. This might be useful if the server + were sending coloured error messages, but it also gives the server + the ability to have unexpected effects on your terminal display. For + more discussion, see section 7.2.3.5. + + 6.2 Running PSFTP + + Once you have started your PSFTP session, you will see a `psftp>' + prompt. You can now type commands to perform file-transfer + functions. This section lists all the available commands. + + Any line starting with a # will be treated as a comment and ignored. + + 6.2.1 General quoting rules for PSFTP commands + + Most PSFTP commands are considered by the PSFTP command interpreter + as a sequence of words, separated by spaces. For example, the + command `ren oldfilename newfilename' splits up into three words: + `ren' (the command name), `oldfilename' (the name of the file to be + renamed), and `newfilename' (the new name to give the file). + + Sometimes you will need to specify file names that _contain_ spaces. + In order to do this, you can surround the file name with double + quotes. This works equally well for local file names and remote file + names: + + psftp> get "spacey file name.txt" "save it under this name.txt" + + The double quotes themselves will not appear as part of the file + names; they are removed by PSFTP and their only effect is to stop + the spaces inside them from acting as word separators. + + If you need to _use_ a double quote (on some types of remote system, + such as Unix, you are allowed to use double quotes in file names), + you can do this by doubling it. This works both inside and outside + double quotes. For example, this command + + psftp> ren ""this"" "a file with ""quotes"" in it" + + will take a file whose current name is `"this"' (with a double quote + character at the beginning and the end) and rename it to a file + whose name is `a file with "quotes" in it'. + + (The one exception to the PSFTP quoting rules is the `!' command, + which passes its command line straight to Windows without splitting + it up into words at all. See section 6.2.19.) + + 6.2.2 Wildcards in PSFTP + + Several commands in PSFTP support `wildcards' to select multiple + files. + + For _local_ file specifications (such as the first argument to + `put'), wildcard rules for the local operating system are used. For + instance, PSFTP running on Windows might require the use of `*.*' + where PSFTP on Unix would need `*'. + + For _remote_ file specifications (such as the first argument to + `get'), PSFTP uses a standard wildcard syntax (similar to POSIX + wildcards): + + - `*' matches any sequence of characters (including a zero-length + sequence). + + - `?' matches exactly one character. + + - `[abc]' matches exactly one character which can be a, b, or c. + + `[a-z]' matches any character in the range a to z. + + `[^abc]' matches a single character that is _not_ a, b, or c. + + Special cases: `[-a]' matches a literal hyphen (-) or a; `[^-a]' + matches all other characters. `[a^]' matches a literal caret (^) + or a. + + - `\' (backslash) before any of the above characters (or itself) + removes that character's special meaning. + + A leading period (.) on a filename is not treated specially, unlike + in some Unix contexts; `get *' will fetch all files, whether or not + they start with a leading period. + + 6.2.3 The `open' command: start a session + + If you started PSFTP by double-clicking in the GUI, or just by + typing `psftp' at the command line, you will need to open a + connection to an SFTP server before you can issue any other commands + (except `help' and `quit'). + + To create a connection, type `open host.name', or if you need to + specify a user name as well you can type `open user@host.name'. You + can optionally specify a port as well: `open user@host.name 22'. + + Once you have issued this command, you will not be able to issue it + again, _even_ if the command fails (for example, if you mistype the + host name or the connection times out). So if the connection is not + opened successfully, PSFTP will terminate immediately. + + 6.2.4 The `quit' command: end your session + + When you have finished your session, type the command `quit' to + close the connection, terminate PSFTP and return to the command line + (or just close the PSFTP console window if you started it from the + GUI). + + You can also use the `bye' and `exit' commands, which have exactly + the same effect. + + 6.2.5 The `close' command: close your connection + + If you just want to close the network connection but keep PSFTP + running, you can use the `close' command. You can then use the + `open' command to open a new connection. + + 6.2.6 The `help' command: get quick online help + + If you type `help', PSFTP will give a short list of the available + commands. + + If you type `help' with a command name - for example, `help get' + - then PSFTP will give a short piece of help on that particular + command. + + 6.2.7 The `cd' and `pwd' commands: changing the remote working directory + + PSFTP maintains a notion of your `working directory' on the server. + This is the default directory that other commands will operate on. + For example, if you type `get filename.dat' then PSFTP will look for + `filename.dat' in your remote working directory on the server. + + To change your remote working directory, use the `cd' command. If + you don't provide an argument, `cd' will return you to your home + directory on the server (more precisely, the remote directory you + were in at the start of the connection). + + To display your current remote working directory, type `pwd'. + + 6.2.8 The `lcd' and `lpwd' commands: changing the local working directory + + As well as having a working directory on the remote server, PSFTP + also has a working directory on your local machine (just like + any other Windows process). This is the default local directory + that other commands will operate on. For example, if you type + `get filename.dat' then PSFTP will save the resulting file as + `filename.dat' in your local working directory. + + To change your local working directory, use the `lcd' command. To + display your current local working directory, type `lpwd'. + + 6.2.9 The `get' command: fetch a file from the server + + To download a file from the server and store it on your local PC, + you use the `get' command. + + In its simplest form, you just use this with a file name: + + get myfile.dat + + If you want to store the file locally under a different name, + specify the local file name after the remote one: + + get myfile.dat newname.dat + + This will fetch the file on the server called `myfile.dat', but will + save it to your local machine under the name `newname.dat'. + + To fetch an entire directory recursively, you can use the `-r' + option: + + get -r mydir + get -r mydir newname + + (If you want to fetch a file whose name starts with a hyphen, you + may have to use the `--' special argument, which stops `get' from + interpreting anything as a switch after it. For example, `get -- - + silly-name-'.) + +6.2.10 The `put' command: send a file to the server + + To upload a file to the server from your local PC, you use the `put' + command. + + In its simplest form, you just use this with a file name: + + put myfile.dat + + If you want to store the file remotely under a different name, + specify the remote file name after the local one: + + put myfile.dat newname.dat + + This will send the local file called `myfile.dat', but will store it + on the server under the name `newname.dat'. + + To send an entire directory recursively, you can use the `-r' + option: + + put -r mydir + put -r mydir newname + + (If you want to send a file whose name starts with a hyphen, you + may have to use the `--' special argument, which stops `put' from + interpreting anything as a switch after it. For example, `put -- - + silly-name-'.) + +6.2.11 The `mget' and `mput' commands: fetch or send multiple files + + `mget' works almost exactly like `get', except that it allows you to + specify more than one file to fetch at once. You can do this in two + ways: + + - by giving two or more explicit file names + (`mget file1.txt file2.txt') + + - by using a wildcard (`mget *.txt'). + + Every argument to `mget' is treated as the name of a file to fetch + (unlike `get', which will interpret at most one argument like + that, and a second argument will be treated as an alternative name + under which to store the retrieved file), or a wildcard expression + matching more than one file. + + The `-r' and `--' options from `get' are also available with `mget'. + + `mput' is similar to `put', with the same differences. + +6.2.12 The `reget' and `reput' commands: resuming file transfers + + If a file transfer fails half way through, and you end up with half + the file stored on your disk, you can resume the file transfer using + the `reget' and `reput' commands. These work exactly like the `get' + and `put' commands, but they check for the presence of the half- + written destination file and start transferring from where the last + attempt left off. + + The syntax of `reget' and `reput' is exactly the same as the syntax + of `get' and `put': + + reget myfile.dat + reget myfile.dat newname.dat + reget -r mydir + + These commands are intended mainly for resuming interrupted + transfers. They assume that the remote file or directory structure + has not changed in any way; if there have been changes, you may end + up with corrupted files. In particular, the `-r' option will not + pick up changes to files or directories already transferred in full. + +6.2.13 The `dir' command: list remote files + + To list the files in your remote working directory, just type `dir'. + + You can also list the contents of a different directory by typing + `dir' followed by the directory name: + + dir /home/fred + dir sources + + And you can list a subset of the contents of a directory by + providing a wildcard: + + dir /home/fred/*.txt + dir sources/*.c + + The `ls' command works exactly the same way as `dir'. + +6.2.14 The `chmod' command: change permissions on remote files + + PSFTP allows you to modify the file permissions on files and + directories on the server. You do this using the `chmod' command, + which works very much like the Unix `chmod' command. + + The basic syntax is `chmod modes file', where `modes' represents a + modification to the file permissions, and `file' is the filename to + modify. You can specify multiple files or wildcards. For example: + + chmod go-rwx,u+w privatefile + chmod a+r public* + chmod 640 groupfile1 groupfile2 + + The `modes' parameter can be a set of octal digits in the Unix + style. (If you don't know what this means, you probably don't want + to be using it!) Alternatively, it can be a list of permission + modifications, separated by commas. Each modification consists of: + + - The people affected by the modification. This can be `u' + (the owning user), `g' (members of the owning group), or `o' + (everybody else - `others'), or some combination of those. It + can also be `a' (`all') to affect everybody at once. + + - A `+' or `-' sign, indicating whether permissions are to be + added or removed. + + - The actual permissions being added or removed. These can be + `r' (permission to read the file), `w' (permission to write + to the file), and `x' (permission to execute the file, or in + the case of a directory, permission to access files within the + directory). + + So the above examples would do: + + - The first example: `go-rwx' removes read, write and execute + permissions for members of the owning group and everybody else + (so the only permissions left are the ones for the file owner). + `u+w' adds write permission for the file owner. + + - The second example: `a+r' adds read permission for everybody to + all files and directories starting with `public'. + + In addition to all this, there are a few extra special cases for + Unix systems. On non-Unix systems these are unlikely to be useful: + + - You can specify `u+s' and `u-s' to add or remove the Unix set- + user-ID bit. This is typically only useful for special purposes; + refer to your Unix documentation if you're not sure about it. + + - You can specify `g+s' and `g-s' to add or remove the Unix set- + group-ID bit. On a file, this works similarly to the set-user- + ID bit (see your Unix documentation again); on a directory it + ensures that files created in the directory are accessible by + members of the group that owns the directory. + + - You can specify `+t' and `-t' to add or remove the Unix `sticky + bit'. When applied to a directory, this means that the owner of + a file in that directory can delete the file (whereas normally + only the owner of the _directory_ would be allowed to). + +6.2.15 The `del' command: delete remote files + + To delete a file on the server, type `del' and then the filename or + filenames: + + del oldfile.dat + del file1.txt file2.txt + del *.o + + Files will be deleted without further prompting, even if multiple + files are specified. + + `del' will only delete files. You cannot use it to delete + directories; use `rmdir' for that. + + The `rm' command works exactly the same way as `del'. + +6.2.16 The `mkdir' command: create remote directories + + To create a directory on the server, type `mkdir' and then the + directory name: + + mkdir newstuff + + You can specify multiple directories to create at once: + + mkdir dir1 dir2 dir3 + +6.2.17 The `rmdir' command: remove remote directories + + To remove a directory on the server, type `rmdir' and then the + directory name or names: + + rmdir oldstuff + rmdir *.old ancient + + Directories will be deleted without further prompting, even if + multiple directories are specified. + + Most SFTP servers will probably refuse to remove a directory if + the directory has anything in it, so you will need to delete the + contents first. + +6.2.18 The `mv' command: move and rename remote files + + To rename a single file on the server, type `mv', then the current + file name, and then the new file name: + + mv oldfile newname + + You can also move the file into a different directory and change the + name: + + mv oldfile dir/newname + + To move one or more files into an existing subdirectory, specify + the files (using wildcards if desired), and then the destination + directory: + + mv file dir + mv file1 dir1/file2 dir2 + mv *.c *.h .. + + The `rename' and `ren' commands work exactly the same way as `mv'. + +6.2.19 The `!' command: run a local Windows command + + You can run local Windows commands using the `!' command. This is + the only PSFTP command that is not subject to the command quoting + rules given in section 6.2.1. If any command line begins with the + `!' character, then the rest of the line will be passed straight to + Windows without further translation. + + For example, if you want to move an existing copy of a file out of + the way before downloading an updated version, you might type: + + psftp> !ren myfile.dat myfile.bak + psftp> get myfile.dat + + using the Windows `ren' command to rename files on your local PC. + + 6.3 Using public key authentication with PSFTP + + Like PuTTY, PSFTP can authenticate using a public key instead of a + password. There are three ways you can do this. + + Firstly, PSFTP can use PuTTY saved sessions in place of hostnames. + So you might do this: + + - Run PuTTY, and create a PuTTY saved session (see section 4.1.2) + which specifies your private key file (see section 4.23.8). You + will probably also want to specify a username to log in as (see + section 4.15.1). + + - In PSFTP, you can now use the name of the session instead of + a hostname: type `psftp sessionname', where `sessionname' is + replaced by the name of your saved session. + + Secondly, you can supply the name of a private key file on the + command line, with the `-i' option. See section 3.8.3.18 for more + information. + + Thirdly, PSFTP will attempt to authenticate using Pageant if Pageant + is running (see chapter 9). So you would do this: + + - Ensure Pageant is running, and has your private key stored in + it. + + - Specify a user and host name to PSFTP as normal. PSFTP will + automatically detect Pageant and try to use the keys within it. + + For more general information on public-key authentication, see + chapter 8. + +Chapter 7: Using the command-line connection tool Plink +------------------------------------------------------- + + Plink is a command-line connection tool similar to UNIX `ssh'. It is + mostly used for automated operations, such as making CVS access a + repository on a remote server. + + Plink is probably not what you want if you want to run an + interactive session in a console window. + + 7.1 Starting Plink + + Plink is a command line application. This means that you cannot just + double-click on its icon to run it and instead you have to bring + up a console window. In Windows 95, 98, and ME, this is called an + `MS-DOS Prompt', and in Windows NT, 2000, and XP, it is called a + `Command Prompt'. It should be available from the Programs section + of your Start Menu. + + In order to use Plink, the file `plink.exe' will need either to be + on your `PATH' or in your current directory. To add the directory + containing Plink to your `PATH' environment variable, type into the + console window: + + set PATH=C:\path\to\putty\directory;%PATH% + + This will only work for the lifetime of that particular console + window. To set your `PATH' more permanently on Windows NT, 2000, and + XP, use the Environment tab of the System Control Panel. On Windows + 95, 98, and ME, you will need to edit your `AUTOEXEC.BAT' to include + a `set' command like the one above. + + 7.2 Using Plink + + This section describes the basics of how to use Plink for + interactive logins and for automated processes. + + Once you've got a console window to type into, you can just type + `plink' on its own to bring up a usage message. This tells you the + version of Plink you're using, and gives you a brief summary of how + to use Plink: + + Z:\sysosd>plink + Plink: command-line connection utility + Release 0.72 + Usage: plink [options] [user@]host [command] + ("host" can also be a PuTTY saved session name) + Options: + -V print version information and exit + -pgpfp print PGP key fingerprints and exit + -v show verbose messages + -load sessname Load settings from saved session + -ssh -telnet -rlogin -raw -serial + force use of a particular protocol + -P port connect to specified port + -l user connect with specified username + -batch disable all interactive prompts + -proxycmd command + use 'command' as local proxy + -sercfg configuration-string (e.g. 19200,8,n,1,X) + Specify the serial configuration (serial only) + The following options only apply to SSH connections: + -pw passw login with specified password + -D [listen-IP:]listen-port + Dynamic SOCKS-based port forwarding + -L [listen-IP:]listen-port:host:port + Forward local port to remote address + -R [listen-IP:]listen-port:host:port + Forward remote port to local address + -X -x enable / disable X11 forwarding + -A -a enable / disable agent forwarding + -t -T enable / disable pty allocation + -1 -2 force use of particular protocol version + -4 -6 force use of IPv4 or IPv6 + -C enable compression + -i key private key file for user authentication + -noagent disable use of Pageant + -agent enable use of Pageant + -noshare disable use of connection sharing + -share enable use of connection sharing + -hostkey aa:bb:cc:... + manually specify a host key (may be repeated) + -sanitise-stderr, -sanitise-stdout, -no-sanitise-stderr, -no-sanitise-stdout + do/don't strip control chars from standard output/error + -no-antispoof omit anti-spoofing prompt after authentication + -m file read remote command(s) from file + -s remote command is an SSH subsystem (SSH-2 only) + -N don't start a shell/command (SSH-2 only) + -nc host:port + open tunnel in place of session (SSH-2 only) + -sshlog file + -sshrawlog file + log protocol details to a file + -shareexists + test whether a connection-sharing upstream exists + + Once this works, you are ready to use Plink. + + 7.2.1 Using Plink for interactive logins + + To make a simple interactive connection to a remote server, just + type `plink' and then the host name: + + Z:\sysosd>plink login.example.com + + Debian GNU/Linux 2.2 flunky.example.com + flunky login: + + You should then be able to log in as normal and run a session. The + output sent by the server will be written straight to your command + prompt window, which will most likely not interpret terminal control + codes in the way the server expects it to. So if you run any full- + screen applications, for example, you can expect to see strange + characters appearing in your window. Interactive connections like + this are not the main point of Plink. + + In order to connect with a different protocol, you can give the + command line options `-ssh', `-telnet', `-rlogin' or `-raw'. To make + an SSH connection, for example: + + Z:\sysosd>plink -ssh login.example.com + login as: + + If you have already set up a PuTTY saved session, then instead of + supplying a host name, you can give the saved session name. This + allows you to use public-key authentication, specify a user name, + and use most of the other features of PuTTY: + + Z:\sysosd>plink my-ssh-session + Sent username "fred" + Authenticating with public key "fred@winbox" + Last login: Thu Dec 6 19:25:33 2001 from :0.0 + fred@flunky:~$ + + (You can also use the `-load' command-line option to load a saved + session; see section 3.8.3.1. If you use `-load', the saved session + exists, and it specifies a hostname, you cannot also specify a + `host' or `user@host' argument - it will be treated as part of the + remote command.) + + 7.2.2 Using Plink for automated connections + + More typically Plink is used with the SSH protocol, to enable you + to talk directly to a program running on the server. To do this you + have to ensure Plink is _using_ the SSH protocol. You can do this in + several ways: + + - Use the `-ssh' option as described in section 7.2.1. + + - Set up a PuTTY saved session that describes the server you are + connecting to, and that also specifies the protocol as SSH. + + - Set the Windows environment variable `PLINK_PROTOCOL' to the + word `ssh'. + + Usually Plink is not invoked directly by a user, but run + automatically by another process. Therefore you typically do not + want Plink to prompt you for a user name or a password. + + Next, you are likely to need to avoid the various interactive + prompts Plink can produce. You might be prompted to verify the host + key of the server you're connecting to, to enter a user name, or to + enter a password. + + To avoid being prompted for the server host key when using Plink for + an automated connection, you should first make a _manual_ connection + (using either of PuTTY or Plink) to the same server, verify the host + key (see section 2.2 for more information), and select Yes to add + the host key to the Registry. After that, Plink commands connecting + to that server should not give a host key prompt unless the host key + changes. + + To avoid being prompted for a user name, you can: + + - Use the `-l' option to specify a user name on the command line. + For example, `plink login.example.com -l fred'. + + - Set up a PuTTY saved session that describes the server you are + connecting to, and that also specifies the username to log in as + (see section 4.15.1). + + To avoid being prompted for a password, you should almost certainly + set up public-key authentication. (See chapter 8 for a general + introduction to public-key authentication.) Again, you can do this + in two ways: + + - Set up a PuTTY saved session that describes the server you + are connecting to, and that also specifies a private key file + (see section 4.23.8). For this to work without prompting, your + private key will need to have no passphrase. + + - Store the private key in Pageant. See chapter 9 for further + information. + + Once you have done all this, you should be able to run a remote + command on the SSH server machine and have it execute automatically + with no prompting: + + Z:\sysosd>plink login.example.com -l fred echo hello, world + hello, world + + Z:\sysosd> + + Or, if you have set up a saved session with all the connection + details: + + Z:\sysosd>plink mysession echo hello, world + hello, world + + Z:\sysosd> + + Then you can set up other programs to run this Plink command and + talk to it as if it were a process on the server machine. + + 7.2.3 Plink command line options + + Plink accepts all the general command line options supported by the + PuTTY tools. See section 3.8.3 for a description of these options. + + Plink also supports some of its own options. The following sections + describe Plink's specific command-line options. + +7.2.3.1 `-batch': disable all interactive prompts + + If you use the `-batch' option, Plink will never give an interactive + prompt while establishing the connection. If the server's host key + is invalid, for example (see section 2.2), then the connection will + simply be abandoned instead of asking you what to do next. + + This may help Plink's behaviour when it is used in automated + scripts: using `-batch', if something goes wrong at connection time, + the batch job will fail rather than hang. + +7.2.3.2 `-s': remote command is SSH subsystem + + If you specify the `-s' option, Plink passes the specified command + as the name of an SSH `subsystem' rather than an ordinary command + line. + + (This option is only meaningful with the SSH-2 protocol.) + +7.2.3.3 `-share': Test and try to share an existing connection. + + This option tris to detect if an existing connection can be shared + (See section 4.19.5 for more information about SSH connection + sharing.) and reuses that connection. + + A Plink invocation of the form: + + plink -share + + will test whether there is currently a viable `upstream' for the + session in question, which can be specified using any syntax you'd + normally use with Plink to make an actual connection (a host/port + number, a bare saved session name, `-load', etc). If no `upstream' + viable session is found and `-share' is specified, this connection + will be become the `upstream' connection for subsequent connection + sharing tries. + + (This option is only meaningful with the SSH-2 protocol.) + +7.2.3.4 `-shareexists': test for connection-sharing upstream + + This option does not make a new connection; instead it allows + testing for the presence of an existing connection that can + be shared. (See section 4.19.5 for more information about SSH + connection sharing.) + + A Plink invocation of the form: + + plink -shareexists + + will test whether there is currently a viable `upstream' for the + session in question, which can be specified using any syntax you'd + normally use with Plink to make an actual connection (a host/port + number, a bare saved session name, `-load', etc). It returns a zero + exit status if a usable `upstream' exists, nonzero otherwise. + + (This option is only meaningful with the SSH-2 protocol.) + +7.2.3.5 `-sanitise-'_stream_: control output sanitisation + + In some situations, Plink applies a sanitisation pass to the output + received from the server, to strip out control characters such as + backspace and the escape character. + + The idea of this is to prevent remote processes from sending + confusing escape sequences through the standard error channel when + Plink is being used as a transport for something like git or CVS. If + the server actually wants to send an error message, it will probably + be plain text; if the server abuses that channel to try to write + over unexpected parts of your terminal display, Plink will try to + stop it. + + By default, this only happens for output channels which are sent + to a Windows console device, or a Unix terminal device. (Any + output stream going somewhere else is likely to be needed by an 8- + bit protocol and must not be tampered with at all.) It also stops + happening if you tell Plink to allocate a remote pseudo-terminal + (see section 3.8.3.12 and section 4.25.1), on the basis that in that + situation you often _want_ escape sequences from the server to go to + your terminal. + + But in case Plink guesses wrong about whether you want this + sanitisation, you can override it in either direction, using one of + these options: + + `-sanitise-stderr' + + Sanitise server data written to Plink's standard error channel, + regardless of terminals and consoles and remote ptys. + + `-no-sanitise-stderr' + + Do not sanitise server data written to Plink's standard error + channel. + + `-sanitise-stdout' + + Sanitise server data written to Plink's standard output channel. + + `-no-sanitise-stdout' + + Do not sanitise server data written to Plink's standard output + channel. + +7.2.3.6 : turn off authentication spoofing protection prompt + + In SSH, some possible server authentication methods require user + input (for example, password authentication, or entering a private + key passphrase), and others do not (e.g. a private key held in + Pageant). + + If you use Plink to run an interactive login session, and if Plink + authenticates without needing any user interaction, and if the + server is malicious or compromised, it could try to trick you into + giving it authentication data that should not go to the server (such + as your private key passphrase), by sending what _looks_ like one of + Plink's local prompts, as if Plink had not already authenticated. + + To protect against this, Plink's default policy is to finish the + authentication phase with a final trivial prompt looking like this: + + Access granted. Press Return to begin session. + + so that if you saw anything that looked like an authentication + prompt _after_ that line, you would know it was not from Plink. + + That extra interactive step is inconvenient. So Plink will turn it + off in as many situations as it can: + + - If Plink's standard input is not pointing at a console or + terminal device - for example, if you're using Plink as a + transport for some automated application like version control + - then you _can't_ type passphrases into the server anyway. In + that situation, Plink won't try to protect you from the server + trying to fool you into doing so. + + - If Plink is in batch mode (see section 7.2.2), then it _never_ + does any interactive authentication. So anything looking like an + interactive authentication prompt is automatically suspect, and + so Plink omits the anti-spoofing prompt. + + But if you still find the protective prompt inconvenient, and you + trust the server not to try a trick like this, you can turn it off + using the `-no-antispoof' option. + + 7.3 Using Plink in batch files and scripts + + Once you have set up Plink to be able to log in to a remote server + without any interactive prompting (see section 7.2.2), you can use + it for lots of scripting and batch purposes. For example, to start a + backup on a remote machine, you might use a command like: + + plink root@myserver /etc/backups/do-backup.sh + + Or perhaps you want to fetch all system log lines relating to a + particular web area: + + plink mysession grep /~fred/ /var/log/httpd/access.log > fredlog + + Any non-interactive command you could usefully run on the server + command line, you can run in a batch file using Plink in this way. + + 7.4 Using Plink with CVS + + To use Plink with CVS, you need to set the environment variable + `CVS_RSH' to point to Plink: + + set CVS_RSH=\path\to\plink.exe + + You also need to arrange to be able to connect to a remote host + without any interactive prompts, as described in section 7.2.2. + + You should then be able to run CVS as follows: + + cvs -d :ext:user@sessionname:/path/to/repository co module + + If you specified a username in your saved session, you don't even + need to specify the `user' part of this, and you can just say: + + cvs -d :ext:sessionname:/path/to/repository co module + + 7.5 Using Plink with WinCVS + + Plink can also be used with WinCVS. Firstly, arrange for Plink to be + able to connect to a remote host non-interactively, as described in + section 7.2.2. + + Then, in WinCVS, bring up the `Preferences' dialogue box from the + _Admin_ menu, and switch to the `Ports' tab. Tick the box there + labelled `Check for an alternate rsh name' and in the text entry + field to the right enter the full path to `plink.exe'. Select `OK' + on the `Preferences' dialogue box. + + Next, select `Command Line' from the WinCVS `Admin' menu, and type a + CVS command as in section 7.4, for example: + + cvs -d :ext:user@hostname:/path/to/repository co module + + or (if you're using a saved session): + + cvs -d :ext:user@sessionname:/path/to/repository co module + + Select the folder you want to check out to with the `Change Folder' + button, and click `OK' to check out your module. Once you've got + modules checked out, WinCVS will happily invoke plink from the GUI + for CVS operations. + +Chapter 8: Using public keys for SSH authentication +--------------------------------------------------- + + 8.1 Public key authentication - an introduction + + Public key authentication is an alternative means of identifying + yourself to a login server, instead of typing a password. It is more + secure and more flexible, but more difficult to set up. + + In conventional password authentication, you prove you are who you + claim to be by proving that you know the correct password. The + only way to prove you know the password is to tell the server what + you think the password is. This means that if the server has been + hacked, or _spoofed_ (see section 2.2), an attacker can learn your + password. + + Public key authentication solves this problem. You generate a _key + pair_, consisting of a public key (which everybody is allowed to + know) and a private key (which you keep secret and do not give + to anybody). The private key is able to generate _signatures_. A + signature created using your private key cannot be forged by anybody + who does not have that key; but anybody who has your public key can + verify that a particular signature is genuine. + + So you generate a key pair on your own computer, and you copy the + public key to the server. Then, when the server asks you to prove + who you are, PuTTY can generate a signature using your private key. + The server can verify that signature (since it has your public key) + and allow you to log in. Now if the server is hacked or spoofed, the + attacker does not gain your private key or password; they only gain + one signature. And signatures cannot be re-used, so they have gained + nothing. + + There is a problem with this: if your private key is stored + unprotected on your own computer, then anybody who gains access to + _that_ will be able to generate signatures as if they were you. So + they will be able to log in to your server under your account. For + this reason, your private key is usually _encrypted_ when it is + stored on your local machine, using a passphrase of your choice. In + order to generate a signature, PuTTY must decrypt the key, so you + have to type your passphrase. + + This can make public-key authentication less convenient than + password authentication: every time you log in to the server, + instead of typing a short password, you have to type a longer + passphrase. One solution to this is to use an _authentication + agent_, a separate program which holds decrypted private keys and + generates signatures on request. PuTTY's authentication agent is + called Pageant. When you begin a Windows session, you start Pageant + and load your private key into it (typing your passphrase once). + For the rest of your session, you can start PuTTY any number of + times and Pageant will automatically generate signatures without you + having to do anything. When you close your Windows session, Pageant + shuts down, without ever having stored your decrypted private key on + disk. Many people feel this is a good compromise between security + and convenience. See chapter 9 for further details. + + There is more than one public-key algorithm available. The most + common are RSA and ECDSA, but others exist, notably DSA (otherwise + known as DSS), the USA's federal Digital Signature Standard. The key + types supported by PuTTY are described in section 8.2.2. + + 8.2 Using PuTTYgen, the PuTTY key generator + + PuTTYgen is a key generator. It generates pairs of public and + private keys to be used with PuTTY, PSCP, and Plink, as well as + the PuTTY authentication agent, Pageant (see chapter 9). PuTTYgen + generates RSA, DSA, ECDSA, and Ed25519 keys. + + When you run PuTTYgen you will see a window where you have two main + choices: `Generate', to generate a new public/private key pair, or + `Load' to load in an existing private key. + + 8.2.1 Generating a new key + + This is a general outline of the procedure for generating a new key + pair. The following sections describe the process in more detail. + + - First, you need to select which type of key you want to + generate, and also select the strength of the key. This is + described in more detail in section 8.2.2 and section 8.2.3. + + - Then press the `Generate' button, to actually generate the key. + Section 8.2.4 describes this step. + + - Once you have generated the key, select a comment field (section + 8.2.6) and a passphrase (section 8.2.7). + + - Now you're ready to save the private key to disk; press the + `Save private key' button. (See section 8.2.8). + + Your key pair is now ready for use. You may also want to copy the + public key to your server, either by copying it out of the `Public + key for pasting into OpenSSH authorized_keys file' box (see section + 8.2.10), or by using the `Save public key' button (section 8.2.9). + However, you don't need to do this immediately; if you want, you can + load the private key back into PuTTYgen later (see section 8.2.11) + and the public key will be available for copying and pasting again. + + Section 8.3 describes the typical process of configuring PuTTY to + attempt public-key authentication, and configuring your SSH server + to accept it. + + 8.2.2 Selecting the type of key + + Before generating a key pair using PuTTYgen, you need to select + which type of key you need. + + The current version of the SSH protocol, SSH-2, supports several + different key types. PuTTYgen can generate: + + - An RSA key for use with the SSH-2 protocol. + + - A DSA key for use with the SSH-2 protocol. + + - An ECDSA (elliptic curve DSA) key for use with the SSH-2 + protocol. + + - An Ed25519 key (another elliptic curve algorithm) for use with + the SSH-2 protocol. + + PuTTYgen can also generate an RSA key suitable for use with the + old SSH-1 protocol (which only supports RSA); for this, you need + to select the `SSH-1 (RSA)' option. Since the SSH-1 protocol is no + longer considered secure, it's rare to need this option. + + 8.2.3 Selecting the size (strength) of the key + + The `Number of bits' input box allows you to choose the strength of + the key PuTTYgen will generate. + + - For RSA, 2048 bits should currently be sufficient for most + purposes. + + - For ECDSA, only 256, 384, and 521 bits are supported. (ECDSA + offers equivalent security to RSA with smaller key sizes.) + + - For Ed25519, the only valid size is 256 bits. + + 8.2.4 The `Generate' button + + Once you have chosen the type of key you want, and the strength of + the key, press the `Generate' button and PuTTYgen will begin the + process of actually generating the key. + + First, a progress bar will appear and PuTTYgen will ask you to move + the mouse around to generate randomness. Wave the mouse in circles + over the blank area in the PuTTYgen window, and the progress bar + will gradually fill up as PuTTYgen collects enough randomness. You + don't need to wave the mouse in particularly imaginative patterns + (although it can't hurt); PuTTYgen will collect enough randomness + just from the fine detail of _exactly_ how far the mouse has moved + each time Windows samples its position. + + When the progress bar reaches the end, PuTTYgen will begin creating + the key. The progress bar will reset to the start, and gradually + move up again to track the progress of the key generation. It will + not move evenly, and may occasionally slow down to a stop; this + is unfortunately unavoidable, because key generation is a random + process and it is impossible to reliably predict how long it will + take. + + When the key generation is complete, a new set of controls will + appear in the window to indicate this. + + 8.2.5 The `Key fingerprint' box + + The `Key fingerprint' box shows you a fingerprint value for the + generated key. This is derived cryptographically from the _public_ + key value, so it doesn't need to be kept secret; it is supposed to + be more manageable for human beings than the public key itself. + + The fingerprint value is intended to be cryptographically secure, + in the sense that it is computationally infeasible for someone to + invent a second key with the same fingerprint, or to find a key with + a particular fingerprint. So some utilities, such as the Pageant key + list box (see section 9.2.1) and the Unix `ssh-add' utility, will + list key fingerprints rather than the whole public key. + + 8.2.6 Setting a comment for your key + + If you have more than one key and use them for different purposes, + you don't need to memorise the key fingerprints in order to tell + them apart. PuTTYgen allows you to enter a _comment_ for your key, + which will be displayed whenever PuTTY or Pageant asks you for the + passphrase. + + The default comment format, if you don't specify one, contains the + key type and the date of generation, such as `rsa-key-20011212'. + Another commonly used approach is to use your name and the name of + the computer the key will be used on, such as `simon@simons-pc'. + + To alter the key comment, just type your comment text into the `Key + comment' box before saving the private key. If you want to change + the comment later, you can load the private key back into PuTTYgen, + change the comment, and save it again. + + 8.2.7 Setting a passphrase for your key + + The `Key passphrase' and `Confirm passphrase' boxes allow you to + choose a passphrase for your key. The passphrase will be used to + encrypt the key on disk, so you will not be able to use the key + without first entering the passphrase. + + When you save the key, PuTTYgen will check that the `Key passphrase' + and `Confirm passphrase' boxes both contain exactly the same + passphrase, and will refuse to save the key otherwise. + + If you leave the passphrase fields blank, the key will be saved + unencrypted. You should _not_ do this without good reason; if you + do, your private key file on disk will be all an attacker needs to + gain access to any machine configured to accept that key. If you + want to be able to log in without having to type a passphrase every + time, you should consider using Pageant (chapter 9) so that your + decrypted key is only held in memory rather than on disk. + + Under special circumstances you may genuinely _need_ to use a key + with no passphrase; for example, if you need to run an automated + batch script that needs to make an SSH connection, you can't be + there to type the passphrase. In this case we recommend you generate + a special key for each specific batch script (or whatever) that + needs one, and on the server side you should arrange that each + key is _restricted_ so that it can only be used for that specific + purpose. The documentation for your SSH server should explain how to + do this (it will probably vary between servers). + + Choosing a good passphrase is difficult. Just as you shouldn't use + a dictionary word as a password because it's easy for an attacker + to run through a whole dictionary, you should not use a song + lyric, quotation or other well-known sentence as a passphrase. + DiceWare (www.diceware.com) recommends using at least five words + each generated randomly by rolling five dice, which gives over + 2^64 possible passphrases and is probably not a bad scheme. If you + want your passphrase to make grammatical sense, this cuts down the + possibilities a lot and you should use a longer one as a result. + + _Do not forget your passphrase_. There is no way to recover it. + + 8.2.8 Saving your private key to a disk file + + Once you have generated a key, set a comment field and set a + passphrase, you are ready to save your private key to disk. + + Press the `Save private key' button. PuTTYgen will put up a dialog + box asking you where to save the file. Select a directory, type in a + file name, and press `Save'. + + This file is in PuTTY's native format (`*.PPK'); it is the one you + will need to tell PuTTY to use for authentication (see section + 4.23.8) or tell Pageant to load (see section 9.2.2). + + 8.2.9 Saving your public key to a disk file + + RFC 4716 specifies a standard format for storing SSH-2 public keys + on disk. Some SSH servers (such as ssh.com's) require a public + key in this format in order to accept authentication with the + corresponding private key. (Others, such as OpenSSH, use a different + format; see section 8.2.10.) + + To save your public key in the SSH-2 standard format, press the + `Save public key' button in PuTTYgen. PuTTYgen will put up a dialog + box asking you where to save the file. Select a directory, type in a + file name, and press `Save'. + + You will then probably want to copy the public key file to your + SSH server machine. See section 8.3 for general instructions on + configuring public-key authentication once you have generated a key. + + If you use this option with an SSH-1 key, the file PuTTYgen saves + will contain exactly the same text that appears in the `Public key + for pasting' box. This is the only existing standard for SSH-1 + public keys. + +8.2.10 `Public key for pasting into OpenSSH authorized_keys file' + + The OpenSSH server, among others, requires your public key + to be given to it in a one-line format before it will accept + authentication with your private key. (SSH-1 servers also used this + method.) + + The `Public key for pasting into OpenSSH authorized_keys file' gives + the public-key data in the correct one-line format. Typically you + will want to select the entire contents of the box using the mouse, + press Ctrl+C to copy it to the clipboard, and then paste the data + into a PuTTY session which is already connected to the server. + + See section 8.3 for general instructions on configuring public-key + authentication once you have generated a key. + +8.2.11 Reloading a private key + + PuTTYgen allows you to load an existing private key file into + memory. If you do this, you can then change the passphrase and + comment before saving it again; you can also make extra copies of + the public key. + + To load an existing key, press the `Load' button. PuTTYgen will put + up a dialog box where you can browse around the file system and find + your key file. Once you select the file, PuTTYgen will ask you for a + passphrase (if necessary) and will then display the key details in + the same way as if it had just generated the key. + + If you use the Load command to load a foreign key format, it will + work, but you will see a message box warning you that the key you + have loaded is not a PuTTY native key. See section 8.2.12 for + information about importing foreign key formats. + +8.2.12 Dealing with private keys in other formats + + SSH-2 private keys have no standard format. OpenSSH and ssh.com + have different formats, and PuTTY's is different again. So a key + generated with one client cannot immediately be used with another. + + Using the `Import' command from the `Conversions' menu, PuTTYgen can + load SSH-2 private keys in OpenSSH's format and ssh.com's format. + Once you have loaded one of these key types, you can then save it + back out as a PuTTY-format key (`*.PPK') so that you can use it with + the PuTTY suite. The passphrase will be unchanged by this process + (unless you deliberately change it). You may want to change the key + comment before you save the key, since some OpenSSH key formats + contained no space for a comment, and ssh.com's default comment + format is long and verbose. + + PuTTYgen can also export private keys in OpenSSH format and in + ssh.com format. To do so, select one of the `Export' options from + the `Conversions' menu. Exporting a key works exactly like saving + it (see section 8.2.8) - you need to have typed your passphrase in + beforehand, and you will be warned if you are about to save a key + without a passphrase. + + For OpenSSH there are two options. Modern OpenSSH actually has two + formats it uses for storing private keys. `Export OpenSSH key' will + automatically choose the oldest format supported for the key type, + for maximum backward compatibility with older versions of OpenSSH; + for newer key types like Ed25519, it will use the newer format as + that is the only legal option. If you have some specific reason for + wanting to use OpenSSH's newer format even for RSA, DSA, or ECDSA + keys, you can choose `Export OpenSSH key (force new file format)'. + + Most clients for the older SSH-1 protocol use a standard format for + storing private keys on disk. PuTTY uses this format as well; so if + you have generated an SSH-1 private key using OpenSSH or ssh.com's + client, you can use it with PuTTY, and vice versa. Hence, the export + options are not available if you have generated an SSH-1 key. + + 8.3 Getting ready for public key authentication + + Connect to your SSH server using PuTTY with the SSH protocol. When + the connection succeeds you will be prompted for your user name and + password to login. Once logged in, you must configure the server to + accept your public key for authentication: + + - If your server is OpenSSH, you should change into the `.ssh' + directory under your home directory, and open the file + `authorized_keys' with your favourite editor. (You may have + to create this file, if this is the first key you have put in + it.) Then switch to the PuTTYgen window, select all of the text + in the `Public key for pasting into OpenSSH authorized_keys + file' box (see section 8.2.10), and copy it to the clipboard + (`Ctrl+C'). Then, switch back to the PuTTY window and insert the + data into the open file, making sure it ends up all on one line. + Save the file. + + (In very old versions of OpenSSH, SSH-2 keys had to be put + in a separate file called `authorized_keys2'. In all current + versions, the same `authorized_keys' file is used for both SSH-1 + and SSH-2 keys.) + + - If your server is ssh.com's product and is using SSH-2, you need + to save a _public_ key file from PuTTYgen (see section 8.2.9), + and copy that into the `.ssh2' directory on the server. Then you + should go into that `.ssh2' directory, and edit (or create) a + file called `authorization'. In this file you should put a line + like `Key mykey.pub', with `mykey.pub' replaced by the name of + your key file. + + - For other SSH server software, you should refer to the manual + for that server. + + You may also need to ensure that your home directory, your `.ssh' + directory, and any other files involved (such as `authorized_keys', + `authorized_keys2' or `authorization') are not group-writable or + world-writable; servers will typically ignore the keys unless this + is done. You can typically do this by using a command such as + + chmod go-w $HOME $HOME/.ssh $HOME/.ssh/authorized_keys + + Your server should now be configured to accept authentication using + your private key. Now you need to configure PuTTY to _attempt_ + authentication using your private key. You can do this in any of + three ways: + + - Select the private key in PuTTY's configuration. See section + 4.23.8 for details. + + - Specify the key file on the command line with the `-i' option. + See section 3.8.3.18 for details. + + - Load the private key into Pageant (see chapter 9). In this case + PuTTY will automatically try to use it for authentication if it + can. + +Chapter 9: Using Pageant for authentication +------------------------------------------- + + Pageant is an SSH authentication agent. It holds your private keys + in memory, already decoded, so that you can use them often without + needing to type a passphrase. + + 9.1 Getting started with Pageant + + Before you run Pageant, you need to have a private key in `*.PPK' + format. See chapter 8 to find out how to generate and use one. + + When you run Pageant, it will put an icon of a computer wearing a + hat into the System tray. It will then sit and do nothing, until you + load a private key into it. + + If you click the Pageant icon with the right mouse button, you will + see a menu. Select `View Keys' from this menu. The Pageant main + window will appear. (You can also bring this window up by double- + clicking on the Pageant icon.) + + The Pageant window contains a list box. This shows the private keys + Pageant is holding. When you start Pageant, it has no keys, so the + list box will be empty. After you add one or more keys, they will + show up in the list box. + + To add a key to Pageant, press the `Add Key' button. Pageant will + bring up a file dialog, labelled `Select Private Key File'. Find + your private key file in this dialog, and press `Open'. + + Pageant will now load the private key. If the key is protected by + a passphrase, Pageant will ask you to type the passphrase. When + the key has been loaded, it will appear in the list in the Pageant + window. + + Now start PuTTY and open an SSH session to a site that accepts your + key. PuTTY will notice that Pageant is running, retrieve the key + automatically from Pageant, and use it to authenticate. You can now + open as many PuTTY sessions as you like without having to type your + passphrase again. + + (PuTTY can be configured not to try to use Pageant, but it will + try by default. See section 4.23.3 and section 3.8.3.9 for more + information.) + + When you want to shut down Pageant, click the right button on the + Pageant icon in the System tray, and select `Exit' from the menu. + Closing the Pageant main window does _not_ shut down Pageant. + + 9.2 The Pageant main window + + The Pageant main window appears when you left-click on the Pageant + system tray icon, or alternatively right-click and select `View + Keys' from the menu. You can use it to keep track of what keys are + currently loaded into Pageant, and to add new ones or remove the + existing keys. + + 9.2.1 The key list box + + The large list box in the Pageant main window lists the private + keys that are currently loaded into Pageant. The list might look + something like this: + + ssh-rsa 2048 22:d6:69:c9:22:51:ac:cb:b9:15:67:47:f7:65:6d:d7 k1 + ssh-dss 2048 e4:6c:69:f3:4f:fc:cf:fc:96:c0:88:34:a7:1e:59:d7 k2 + + For each key, the list box will tell you: + + - The type of the key. Currently, this can be `ssh-rsa' (an RSA + key for use with the SSH-2 protocol), `ssh-dss' (a DSA key for + use with the SSH-2 protocol), `ecdsa-sha2-*' (an ECDSA key for + use with the SSH-2 protocol), `ssh-ed25519' (an Ed25519 key for + use with the SSH-2 protocol), or `ssh1' (an RSA key for use with + the old SSH-1 protocol). + + - The size (in bits) of the key. + + - The fingerprint for the public key. This should be the same + fingerprint given by PuTTYgen, and (hopefully) also the same + fingerprint shown by remote utilities such as `ssh-keygen' when + applied to your `authorized_keys' file. + + - The comment attached to the key. + + 9.2.2 The `Add Key' button + + To add a key to Pageant by reading it out of a local disk file, + press the `Add Key' button in the Pageant main window, or + alternatively right-click on the Pageant icon in the system tray and + select `Add Key' from there. + + Pageant will bring up a file dialog, labelled `Select Private Key + File'. Find your private key file in this dialog, and press `Open'. + If you want to add more than one key at once, you can select + multiple files using Shift-click (to select several adjacent files) + or Ctrl-click (to select non-adjacent files). + + Pageant will now load the private key(s). If a key is protected by a + passphrase, Pageant will ask you to type the passphrase. + + (This is not the only way to add a private key to Pageant. You can + also add one from a remote system by using agent forwarding; see + section 9.4 for details.) + + 9.2.3 The `Remove Key' button + + If you need to remove a key from Pageant, select that key in the + list box, and press the `Remove Key' button. Pageant will remove the + key from its memory. + + You can apply this to keys you added using the `Add Key' button, or + to keys you added remotely using agent forwarding (see section 9.4); + it makes no difference. + + 9.3 The Pageant command line + + Pageant can be made to do things automatically when it starts up, + by specifying instructions on its command line. If you're starting + Pageant from the Windows GUI, you can arrange this by editing the + properties of the Windows shortcut that it was started from. + + If Pageant is already running, invoking it again with the options + below causes actions to be performed with the existing instance, not + a new one. + + 9.3.1 Making Pageant automatically load keys on startup + + Pageant can automatically load one or more private keys when it + starts up, if you provide them on the Pageant command line. Your + command line might then look like: + + C:\PuTTY\pageant.exe d:\main.ppk d:\secondary.ppk + + If the keys are stored encrypted, Pageant will request the + passphrases on startup. + + If Pageant is already running, this syntax loads keys into the + existing Pageant. + + 9.3.2 Making Pageant run another program + + You can arrange for Pageant to start another program once it has + initialised itself and loaded any keys specified on its command + line. This program (perhaps a PuTTY, or a WinCVS making use of + Plink, or whatever) will then be able to use the keys Pageant has + loaded. + + You do this by specifying the `-c' option followed by the command, + like this: + + C:\PuTTY\pageant.exe d:\main.ppk -c C:\PuTTY\putty.exe + + 9.3.3 Restricting the Windows process ACL + + Pageant supports the same `-restrict-acl' option as the other PuTTY + utilities to lock down the Pageant process's access control; see + section 3.8.3.25 for why you might want to do this. + + By default, if Pageant is started with `-restrict-acl', it won't + pass this to any PuTTY sessions started from its System Tray + submenu. Use `-restrict-putty-acl' to change this. (Again, see + section 3.8.3.25 for details.) + + 9.4 Using agent forwarding + + Agent forwarding is a mechanism that allows applications on your SSH + server machine to talk to the agent on your client machine. + + Note that at present, whether agent forwarding in SSH-2 is available + depends on your server. Pageant's protocol is compatible with the + OpenSSH server, but the ssh.com server uses a different agent + protocol, which PuTTY does not yet support. + + To enable agent forwarding, first start Pageant. Then set up a + PuTTY SSH session in which `Allow agent forwarding' is enabled (see + section 4.23.6). Open the session as normal. (Alternatively, you can + use the `-A' command line option; see section 3.8.3.10 for details.) + + If this has worked, your applications on the server should now have + access to a Unix domain socket which the SSH server will forward + back to PuTTY, and PuTTY will forward on to the agent. To check that + this has actually happened, you can try this command on Unix server + machines: + + unixbox:~$ echo $SSH_AUTH_SOCK + /tmp/ssh-XXNP18Jz/agent.28794 + unixbox:~$ + + If the result line comes up blank, agent forwarding has not been + enabled at all. + + Now if you run `ssh' on the server and use it to connect through to + another server that accepts one of the keys in Pageant, you should + be able to log in without a password: + + unixbox:~$ ssh -v otherunixbox + [...] + debug: next auth method to try is publickey + debug: userauth_pubkey_agent: trying agent key my-putty-key + debug: ssh-userauth2 successful: method publickey + [...] + + If you enable agent forwarding on _that_ SSH connection as well (see + the manual for your server-side SSH client to find out how to do + this), your authentication keys will still be available on the next + machine you connect to - two SSH connections away from where they're + actually stored. + + In addition, if you have a private key on one of the SSH servers, + you can send it all the way back to Pageant using the local `ssh- + add' command: + + unixbox:~$ ssh-add ~/.ssh/id_rsa + Need passphrase for /home/fred/.ssh/id_rsa + Enter passphrase for /home/fred/.ssh/id_rsa: + Identity added: /home/fred/.ssh/id_rsa (/home/simon/.ssh/id_rsa) + unixbox:~$ + + and then it's available to every machine that has agent forwarding + available (not just the ones downstream of the place you added it). + + 9.5 Security considerations + + Using Pageant for public-key authentication gives you the + convenience of being able to open multiple SSH sessions without + having to type a passphrase every time, but also gives you the + security benefit of never storing a decrypted private key on disk. + Many people feel this is a good compromise between security and + convenience. + + It _is_ a compromise, however. Holding your decrypted private keys + in Pageant is better than storing them in easy-to-find disk files, + but still less secure than not storing them anywhere at all. This is + for two reasons: + + - Windows unfortunately provides no way to protect pieces of + memory from being written to the system swap file. So if Pageant + is holding your private keys for a long period of time, it's + possible that decrypted private key data may be written to the + system swap file, and an attacker who gained access to your hard + disk later on might be able to recover that data. (However, + if you stored an unencrypted key in a disk file they would + _certainly_ be able to recover it.) + + - Although, like most modern operating systems, Windows prevents + programs from accidentally accessing one another's memory space, + it does allow programs to access one another's memory space + deliberately, for special purposes such as debugging. This means + that if you allow a virus, trojan, or other malicious program + on to your Windows system while Pageant is running, it could + access the memory of the Pageant process, extract your decrypted + authentication keys, and send them back to its master. + + Similarly, use of agent _forwarding_ is a security improvement on + other methods of one-touch authentication, but not perfect. Holding + your keys in Pageant on your Windows box has a security advantage + over holding them on the remote server machine itself (either in an + agent or just unencrypted on disk), because if the server machine + ever sees your unencrypted private key then the sysadmin or anyone + who cracks the machine can steal the keys and pretend to be you for + as long as they want. + + However, the sysadmin of the server machine can always pretend to + be you _on that machine_. So if you forward your agent to a server + machine, then the sysadmin of that machine can access the forwarded + agent connection and request signatures from any of your private + keys, and can therefore log in to other machines as you. They + can only do this to a limited extent - when the agent forwarding + disappears they lose the ability - but using Pageant doesn't + actually _prevent_ the sysadmin (or hackers) on the server from + doing this. + + Therefore, if you don't trust the sysadmin of a server machine, you + should _never_ use agent forwarding to that machine. (Of course you + also shouldn't store private keys on that machine, type passphrases + into it, or log into other machines from it in any way at all; + Pageant is hardly unique in this respect.) + +Chapter 10: Common error messages +--------------------------------- + + This chapter lists a number of common error messages which PuTTY and + its associated tools can produce, and explains what they mean in + more detail. + + We do not attempt to list _all_ error messages here: there are many + which should never occur, and some which should be self-explanatory. + If you get an error message which is not listed in this chapter and + which you don't understand, report it to us as a bug (see appendix + B) and we will add documentation for it. + + 10.1 `The server's host key is not cached in the registry' + + This error message occurs when PuTTY connects to a new SSH server. + Every server identifies itself by means of a host key; once PuTTY + knows the host key for a server, it will be able to detect if a + malicious attacker redirects your connection to another machine. + + If you see this message, it means that PuTTY has not seen this host + key before, and has no way of knowing whether it is correct or not. + You should attempt to verify the host key by other means, such as + asking the machine's administrator. + + If you see this message and you know that your installation of PuTTY + _has_ connected to the same server before, it may have been recently + upgraded to SSH protocol version 2. SSH protocols 1 and 2 use + separate host keys, so when you first use SSH-2 with a server you + have only used SSH-1 with before, you will see this message again. + You should verify the correctness of the key as before. + + See section 2.2 for more information on host keys. + + 10.2 `WARNING - POTENTIAL SECURITY BREACH!' + + This message, followed by `The server's host key does not match + the one PuTTY has cached in the registry', means that PuTTY has + connected to the SSH server before, knows what its host key _should_ + be, but has found a different one. + + This may mean that a malicious attacker has replaced your server + with a different one, or has redirected your network connection + to their own machine. On the other hand, it may simply mean that + the administrator of your server has accidentally changed the key + while upgrading the SSH software; this _shouldn't_ happen but it is + unfortunately possible. + + You should contact your server's administrator and see whether they + expect the host key to have changed. If so, verify the new host key + in the same way as you would if it was new. + + See section 2.2 for more information on host keys. + + 10.3 `SSH protocol version 2 required by our configuration but remote + only provides (old, insecure) SSH-1' + + By default, PuTTY only supports connecting to SSH servers that + implement SSH protocol version 2. If you see this message, the + server you're trying to connect to only supports the older SSH-1 + protocol. + + If the server genuinely only supports SSH-1, then you need to either + change the `SSH protocol version' setting (see section 4.19.4), or + use the `-1' command-line option; in any case, you should not treat + the resulting connection as secure. + + You might start seeing this message with new versions of PuTTY + (from 0.68 onwards) where you didn't before, because it used to be + possible to configure PuTTY to automatically fall back from SSH-2 to + SSH-1. This is no longer supported, to prevent the possibility of a + downgrade attack. + + 10.4 `The first cipher supported by the server is ... below the + configured warning threshold' + + This occurs when the SSH server does not offer any ciphers which you + have configured PuTTY to consider strong enough. By default, PuTTY + puts up this warning only for Blowfish, single-DES, and Arcfour + encryption. + + See section 4.22 for more information on this message. + + (There are similar messages for other cryptographic primitives, such + as host key algorithms.) + + 10.5 `Remote side sent disconnect message type 2 (protocol error): "Too + many authentication failures for root"' + + This message is produced by an OpenSSH (or Sun SSH) server if it + receives more failed authentication attempts than it is willing to + tolerate. + + This can easily happen if you are using Pageant and have a large + number of keys loaded into it, since these servers count each offer + of a public key as an authentication attempt. This can be worked + around by specifying the key that's required for the authentication + in the PuTTY configuration (see section 4.23.8); PuTTY will ignore + any other keys Pageant may have, but will ask Pageant to do the + authentication, so that you don't have to type your passphrase. + + On the server, this can be worked around by disabling public-key + authentication or (for Sun SSH only) by increasing `MaxAuthTries' in + `sshd_config'. + + 10.6 `Out of memory' + + This occurs when PuTTY tries to allocate more memory than the system + can give it. This _may_ happen for genuine reasons: if the computer + really has run out of memory, or if you have configured an extremely + large number of lines of scrollback in your terminal. PuTTY is + not able to recover from running out of memory; it will terminate + immediately after giving this error. + + However, this error can also occur when memory is not running out at + all, because PuTTY receives data in the wrong format. In SSH-2 and + also in SFTP, the server sends the length of each message before the + message itself; so PuTTY will receive the length, try to allocate + space for the message, and then receive the rest of the message. + If the length PuTTY receives is garbage, it will try to allocate + a ridiculous amount of memory, and will terminate with an `Out of + memory' error. + + This can happen in SSH-2, if PuTTY and the server have not enabled + encryption in the same way (see question A.7.3 in the FAQ). + + This can also happen in PSCP or PSFTP, if your login scripts on the + server generate output: the client program will be expecting an + SFTP message starting with a length, and if it receives some text + from your login scripts instead it will try to interpret them as a + message length. See question A.7.4 for details of this. + + 10.7 `Internal error', `Internal fault', `Assertion failed' + + Any error beginning with the word `Internal' should _never_ occur. + If it does, there is a bug in PuTTY by definition; please see + appendix B and report it to us. + + Similarly, any error message starting with `Assertion failed' is a + bug in PuTTY. Please report it to us, and include the exact text + from the error message box. + + 10.8 `Unable to use key file', `Couldn't load private key', `Couldn't + load this key' + + Various forms of this error are printed in the PuTTY window, or + written to the PuTTY Event Log (see section 3.1.3.1) when trying + public-key authentication, or given by Pageant when trying to load a + private key. + + If you see one of these messages, it often indicates that you've + tried to load a key of an inappropriate type into PuTTY, Plink, + PSCP, PSFTP, or Pageant. + + You may have tried to load an SSH-2 key in a `foreign' format + (OpenSSH or ssh.com) directly into one of the PuTTY tools, in which + case you need to import it into PuTTY's native format (`*.PPK') + using PuTTYgen - see section 8.2.12. + + Alternatively, you may have specified a key that's inappropriate for + the connection you're making. The SSH-2 and the old SSH-1 protocols + require different private key formats, and a SSH-1 key can't be used + for a SSH-2 connection (or vice versa). + + 10.9 `Server refused our key', `Server refused our public key', `Key + refused' + + Various forms of this error are printed in the PuTTY window, or + written to the PuTTY Event Log (see section 3.1.3.1) when trying + public-key authentication. + + If you see one of these messages, it means that PuTTY has sent a + public key to the server and offered to authenticate with it, and + the server has refused to accept authentication. This usually means + that the server is not configured to accept this key to authenticate + this user. + + This is almost certainly not a problem with PuTTY. If you see + this type of message, the first thing you should do is check your + _server_ configuration carefully. Common errors include having the + wrong permissions or ownership set on the public key or the user's + home directory on the server. Also, read the PuTTY Event Log; the + server may have sent diagnostic messages explaining exactly what + problem it had with your setup. + + Section 8.3 has some hints on server-side public key setup. + + 10.10 `Access denied', `Authentication refused' + + Various forms of this error are printed in the PuTTY window, + or written to the PuTTY Event Log (see section 3.1.3.1) during + authentication. + + If you see one of these messages, it means that the server has + refused all the forms of authentication PuTTY has tried and it has + no further ideas. + + It may be worth checking the Event Log for diagnostic messages from + the server giving more detail. + + This error can be caused by buggy SSH-1 servers that fail to cope + with the various strategies we use for camouflaging passwords in + transit. Upgrade your server, or use the workarounds described in + section 4.28.11 and possibly section 4.28.12. + + 10.11 `No supported authentication methods available' + + This error indicates that PuTTY has run out of ways to authenticate + you to an SSH server. This may be because PuTTY has TIS or keyboard- + interactive authentication disabled, in which case see section + 4.23.4 and section 4.23.5. + + 10.12 `Incorrect MAC received on packet' or `Incorrect CRC received on + packet' + + This error occurs when PuTTY decrypts an SSH packet and its checksum + is not correct. This probably means something has gone wrong in the + encryption or decryption process. It's difficult to tell from this + error message whether the problem is in the client, in the server, + or in between. + + In particular, if the network is corrupting data at the TCP level, + it may only be obvious with cryptographic protocols such as SSH, + which explicitly check the integrity of the transferred data and + complain loudly if the checks fail. Corruption of protocols without + integrity protection (such as HTTP) will manifest in more subtle + failures (such as misdisplayed text or images in a web browser) + which may not be noticed. + + Occasionally this has been caused by server bugs. An example is the + bug described at section 4.28.8, although you're very unlikely to + encounter that one these days. + + In this context MAC stands for Message Authentication Code. It's a + cryptographic term, and it has nothing at all to do with Ethernet + MAC (Media Access Control) addresses, or with the Apple computer. + + 10.13 `Incoming packet was garbled on decryption' + + This error occurs when PuTTY decrypts an SSH packet and the + decrypted data makes no sense. This probably means something has + gone wrong in the encryption or decryption process. It's difficult + to tell from this error message whether the problem is in the + client, in the server, or in between. + + If you get this error, one thing you could try would be to fiddle + with the setting of `Miscomputes SSH-2 encryption keys' (see section + 4.28.10) or `Ignores SSH-2 maximum packet size' (see section 4.28.5) + on the Bugs panel. + + 10.14 `PuTTY X11 proxy: _various errors_' + + This family of errors are reported when PuTTY is doing X forwarding. + They are sent back to the X application running on the SSH server, + which will usually report the error to the user. + + When PuTTY enables X forwarding (see section 3.4) it creates a + virtual X display running on the SSH server. This display requires + authentication to connect to it (this is how PuTTY prevents other + users on your server machine from connecting through the PuTTY proxy + to your real X display). PuTTY also sends the server the details it + needs to enable clients to connect, and the server should put this + mechanism in place automatically, so your X applications should just + work. + + A common reason why people see one of these messages is because they + used SSH to log in as one user (let's say `fred'), and then used + the Unix `su' command to become another user (typically `root'). + The original user, `fred', has access to the X authentication data + provided by the SSH server, and can run X applications which are + forwarded over the SSH connection. However, the second user (`root') + does not automatically have the authentication data passed on to it, + so attempting to run an X application as that user often fails with + this error. + + If this happens, _it is not a problem with PuTTY_. You need to + arrange for your X authentication data to be passed from the user + you logged in as to the user you used `su' to become. How you do + this depends on your particular system; in fact many modern versions + of `su' do it automatically. + + 10.15 `Network error: Software caused connection abort' + + This is a generic error produced by the Windows network code when + it kills an established connection for some reason. For example, it + might happen if you pull the network cable out of the back of an + Ethernet-connected computer, or if Windows has any other similar + reason to believe the entire network has become unreachable. + + Windows also generates this error if it has given up on the machine + at the other end of the connection ever responding to it. If the + network between your client and server goes down and your client + then tries to send some data, Windows will make several attempts + to send the data and will then give up and kill the connection. In + particular, this can occur even if you didn't type anything, if you + are using SSH-2 and PuTTY attempts a key re-exchange. (See section + 4.20.2 for more about key re-exchange.) + + (It can also occur if you are using keepalives in your connection. + Other people have reported that keepalives _fix_ this error for + them. See section 4.14.1 for a discussion of the pros and cons of + keepalives.) + + We are not aware of any reason why this error might occur that would + represent a bug in PuTTY. The problem is between you, your Windows + system, your network and the remote system. + + 10.16 `Network error: Connection reset by peer' + + This error occurs when the machines at each end of a network + connection lose track of the state of the connection between them. + For example, you might see it if your SSH server crashes, and + manages to reboot fully before you next attempt to send data to it. + + However, the most common reason to see this message is if you are + connecting through a firewall or a NAT router which has timed the + connection out. See question A.7.8 in the FAQ for more details. + You may be able to improve the situation by using keepalives; see + section 4.14.1 for details on this. + + Note that Windows can produce this error in some circumstances + without seeing a connection reset from the server, for instance if + the connection to the network is lost. + + 10.17 `Network error: Connection refused' + + This error means that the network connection PuTTY tried to make to + your server was rejected by the server. Usually this happens because + the server does not provide the service which PuTTY is trying to + access. + + Check that you are connecting with the correct protocol (SSH, Telnet + or Rlogin), and check that the port number is correct. If that + fails, consult the administrator of your server. + + 10.18 `Network error: Connection timed out' + + This error means that the network connection PuTTY tried to make to + your server received no response at all from the server. Usually + this happens because the server machine is completely isolated from + the network, or because it is turned off. + + Check that you have correctly entered the host name or IP address + of your server machine. If that fails, consult the administrator of + your server. + + Unix also generates this error when it tries to send data down a + connection and contact with the server has been completely lost + during a connection. (There is a delay of minutes before Unix gives + up on receiving a reply from the server.) This can occur if you type + things into PuTTY while the network is down, but it can also occur + if PuTTY decides of its own accord to send data: due to a repeat key + exchange in SSH-2 (see section 4.20.2) or due to keepalives (section + 4.14.1). + + 10.19 `Network error: Cannot assign requested address' + + This means that the operating system rejected the parameters of the + network connection PuTTY tried to make, usually without actually + trying to connect to anything, because they were simply invalid. + + A common way to provoke this error is to accidentally try to connect + to port 0, which is not a valid port number. + +Appendix A: PuTTY FAQ +--------------------- + + This FAQ is published on the PuTTY web site, and also provided as an + appendix in the manual. + + A.1 Introduction + + A.1.1 What is PuTTY? + + PuTTY is a client program for the SSH, Telnet and Rlogin network + protocols. + + These protocols are all used to run a remote session on a computer, + over a network. PuTTY implements the client end of that session: the + end at which the session is displayed, rather than the end at which + it runs. + + In really simple terms: you run PuTTY on a Windows machine, and + tell it to connect to (for example) a Unix machine. PuTTY opens a + window. Then, anything you type into that window is sent straight + to the Unix machine, and everything the Unix machine sends back is + displayed in the window. So you can work on the Unix machine as if + you were sitting at its console, while actually sitting somewhere + else. + + A.2 Features supported in PuTTY + + In general, if you want to know if PuTTY supports a particular + feature, you should look for it on the PuTTY web site. In + particular: + + - try the changes page, and see if you can find the feature on + there. If a feature is listed there, it's been implemented. If + it's listed as a change made _since_ the latest version, it + should be available in the development snapshots, in which case + testing will be very welcome. + + - try the Wishlist page, and see if you can find the feature + there. If it's on there, and not in the `Recently fixed' + section, it probably _hasn't_ been implemented. + + A.2.1 Does PuTTY support SSH-2? + + Yes. SSH-2 support has been available in PuTTY since version 0.50 in + 2000. + + Public key authentication (both RSA and DSA) in SSH-2 was new in + version 0.52 in 2002. + + A.2.2 Does PuTTY support reading OpenSSH or ssh.com SSH-2 private key + files? + + PuTTY doesn't support this natively (see the wishlist entry for + reasons why not), but as of 0.53 PuTTYgen can convert both OpenSSH + and ssh.com private key files into PuTTY's format. + + A.2.3 Does PuTTY support SSH-1? + + Yes. SSH-1 support has always been available in PuTTY. + + However, the SSH-1 protocol has many weaknesses and is no longer + considered secure; you should use SSH-2 instead if at all possible. + + As of 0.68, PuTTY will no longer fall back to SSH-1 if the server + doesn't appear to support SSH-2; you must explicitly ask for SSH-1. + + A.2.4 Does PuTTY support local echo? + + Yes. Version 0.52 has proper support for local echo. + + In version 0.51 and before, local echo could not be separated from + local line editing (where you type a line of text locally, and it + is not sent to the server until you press Return, so you have the + chance to edit it and correct mistakes _before_ the server sees it). + New in version 0.52, local echo and local line editing are separate + options, and by default PuTTY will try to determine automatically + whether to enable them or not, based on which protocol you have + selected and also based on hints from the server. If you have a + problem with PuTTY's default choice, you can force each option to be + enabled or disabled as you choose. The controls are in the Terminal + panel, in the section marked `Line discipline options'. + + A.2.5 Does PuTTY support storing settings, so I don't have to change them + every time? + + Yes, all of PuTTY's settings can be saved in named session profiles. + You can also change the default settings that are used for new + sessions. See section 4.1.2 in the documentation for how to do this. + + A.2.6 Does PuTTY support storing its settings in a disk file? + + Not at present, although section 4.30 in the documentation gives a + method of achieving the same effect. + + A.2.7 Does PuTTY support full-screen mode, like a DOS box? + + Yes; this was added in version 0.52, in 2002. + + A.2.8 Does PuTTY have the ability to remember my password so I don't have + to type it every time? + + No, it doesn't. + + Remembering your password is a bad plan for obvious security + reasons: anyone who gains access to your machine while you're away + from your desk can find out the remembered password, and use it, + abuse it or change it. + + In addition, it's not even _possible_ for PuTTY to automatically + send your password in a Telnet session, because Telnet doesn't + give the client software any indication of which part of the login + process is the password prompt. PuTTY would have to guess, by + looking for words like `password' in the session data; and if your + login program is written in something other than English, this won't + work. + + In SSH, remembering your password would be possible in theory, + but there doesn't seem to be much point since SSH supports public + key authentication, which is more flexible and more secure. See + chapter 8 in the documentation for a full discussion of public key + authentication. + + A.2.9 Is there an option to turn off the annoying host key prompts? + + No, there isn't. And there won't be. Even if you write it yourself + and send us the patch, we won't accept it. + + Those annoying host key prompts are the _whole point_ of SSH. + Without them, all the cryptographic technology SSH uses to secure + your session is doing nothing more than making an attacker's job + slightly harder; instead of sitting between you and the server with + a packet sniffer, the attacker must actually subvert a router and + start modifying the packets going back and forth. But that's not all + that much harder than just sniffing; and without host key checking, + it will go completely undetected by client or server. + + Host key checking is your guarantee that the encryption you put + on your data at the client end is the _same_ encryption taken off + the data at the server end; it's your guarantee that it hasn't + been removed and replaced somewhere on the way. Host key checking + makes the attacker's job _astronomically_ hard, compared to packet + sniffing, and even compared to subverting a router. Instead of + applying a little intelligence and keeping an eye on Bugtraq, the + attacker must now perform a brute-force attack against at least one + military-strength cipher. That insignificant host key prompt really + does make _that_ much difference. + + If you're having a specific problem with host key checking - perhaps + you want an automated batch job to make use of PSCP or Plink, and + the interactive host key prompt is hanging the batch process - + then the right way to fix it is to add the correct host key to the + Registry in advance, or if the Registry is not available, to use the + -hostkey command-line option. That way, you retain the _important_ + feature of host key checking: the right key will be accepted and the + wrong ones will not. Adding an option to turn host key checking off + completely is the wrong solution and we will not do it. + + If you have host keys available in the common `known_hosts' format, + we have a script called `kh2reg.py' to convert them to a Windows + .REG file, which can be installed ahead of time by double-clicking + or using `REGEDIT'. + +A.2.10 Will you write an SSH server for the PuTTY suite, to go with the + client? + + Not one that you'd want to use. + + While much of the protocol and networking code can be made common + between a client and server, to make a _useful_ general-purpose + server requires all sorts of fiddly new code like interacting with + OS authentication databases and the like. + + A special-purpose SSH server (called Uppity) can now be built from + the PuTTY source code, and indeed it is not usable as a general- + purpose server; it exists mainly as a test harness. + + If someone else wants to use this as a basis for writing a general- + purpose SSH server, they'd be perfectly welcome to of course; but we + don't have time, and we don't have motivation. The code is available + if anyone else wants to try it. + +A.2.11 Can PSCP or PSFTP transfer files in ASCII mode? + + Unfortunately not. + + This was a limitation of the file transfer protocols as originally + specified: the SCP and SFTP protocols had no notion of transferring + a file in anything other than binary mode. (This is still true of + SCP.) + + The current draft protocol spec of SFTP proposes a means of + implementing ASCII transfer. At some point PSCP/PSFTP may implement + this proposal. + + A.3 Ports to other operating systems + + The eventual goal is for PuTTY to be a multi-platform program, able + to run on at least Windows, Mac OS and Unix. + + PuTTY has been gaining a generalised porting layer, drawing a clear + line between platform-dependent and platform-independent code. The + general intention was for this porting layer to evolve naturally as + part of the process of doing the first port; a Unix port has now + been released and the plan seems to be working so far. + + A.3.1 What ports of PuTTY exist? + + Currently, release versions of PuTTY tools only run on Windows + systems and Unix. + + As of 0.68, the supplied PuTTY executables run on versions of + Windows from XP onwards, up to and including Windows 10; and + we know of no reason why PuTTY should not continue to work on + future versions of Windows. We provide 32-bit and 64-bit Windows + executables for the common x86 processor family; see question A.6.10 + for discussion of the compatibility issues around that. The 32-bit + executables require a Pentium 4 or newer processor. We also provide + executables for Windows on Arm processors. + + (We used to also provide executables for Windows for the Alpha + processor, but stopped after 0.58 due to lack of interest.) + + In the development code, a partial port to Mac OS exists (see + question A.3.6). + + Currently PuTTY does _not_ run on Windows CE (see question A.3.4). + + We do not have release-quality ports for any other systems at the + present time. If anyone told you we had an Android port, or an iOS + port, or any other port of PuTTY, they were mistaken. We don't. + + There are some third-party ports to various platforms, mentioned on + the Links page of our website. + + A.3.2 Is there a port to Unix? + + There are Unix ports of most of the traditional PuTTY tools, and + also one entirely new application. + + If you look at the source release, you should find a `unix' + subdirectory. There are a couple of ways of building it, including + the usual `configure'/`make'; see the file `README' in the source + distribution. This should build you: + + - Unix ports of PuTTY, Plink, PSCP, and PSFTP, which work pretty + much the same as their Windows counterparts; + + - Command-line versions of PuTTYgen and Pageant, whose user + interface is quite different to the Windows GUI versions; + + - `pterm' - an xterm-type program which supports the same terminal + emulation as PuTTY. + + If you don't have Gtk, you should still be able to build the + command-line tools. + + A.3.3 What's the point of the Unix port? Unix has OpenSSH. + + All sorts of little things. `pterm' is directly useful to anyone who + prefers PuTTY's terminal emulation to `xterm''s, which at least some + people do. Unix Plink has apparently found a niche among people who + find the complexity of OpenSSL makes OpenSSH hard to install (and + who don't mind Plink not having as many features). Some users want + to generate a large number of SSH keys on Unix and then copy them + all into PuTTY, and the Unix PuTTYgen should allow them to automate + that conversion process. + + There were development advantages as well; porting PuTTY to Unix + was a valuable path-finding effort for other future ports, and also + allowed us to use the excellent Linux tool Valgrind to help with + debugging, which has already improved PuTTY's stability on _all_ + platforms. + + However, if you're a Unix user and you can see no reason to switch + from OpenSSH to PuTTY/Plink, then you're probably right. We don't + expect our Unix port to be the right thing for everybody. + + A.3.4 Will there be a port to Windows CE or PocketPC? + + We once did some work on such a port, but it only reached an early + stage, and certainly not a useful one. It's no longer being actively + worked on. + + A.3.5 Is there a port to Windows 3.1? + + PuTTY is a 32-bit application from the ground up, so it won't run on + Windows 3.1 as a native 16-bit program; and it would be _very_ hard + to port it to do so, because of Windows 3.1's vile memory allocation + mechanisms. + + However, it is possible in theory to compile the existing PuTTY + source in such a way that it will run under Win32s (an extension to + Windows 3.1 to let you run 32-bit programs). In order to do this + you'll need the right kind of C compiler - modern versions of Visual + C at least have stopped being backwards compatible to Win32s. Also, + the last time we tried this it didn't work very well. + + A.3.6 Will there be a port to the Mac? + + We hope so! + + We attempted one around 2005, written as a native Cocoa application, + but it turned out to be very slow to redraw its window for some + reason we never got to the bottom of. + + In 2015, after porting the GTK front end to work with GTK 3, we + began another attempt based on making small changes to the GTK + code and building it against the OS X Quartz version of GTK 3. + This doesn't seem to have the window redrawing problem any more, + so it's already got further than the last effort, but it is still + substantially unfinished. + + If any OS X and/or GTK programming experts are keen to have a + finished version of this, we urge them to help out with some of the + remaining problems! See the TODO list in `unix/gtkapp.c' in the + source code. + + A.3.7 Will there be a port to EPOC? + + I hope so, but given that ports aren't really progressing very fast + even on systems the developers _do_ already know how to program for, + it might be a long time before any of us get round to learning a new + system and doing the port for that. + + However, some of the work has been done by other people; see the + Links page of our website for various third-party ports. + + A.3.8 Will there be a port to the iPhone? + + We have no plans to write such a port ourselves; none of us has an + iPhone, and developing and publishing applications for it looks + awkward and expensive. + + However, there is a third-party SSH client for the iPhone and + iPod Touch called pTerm, which is apparently based on PuTTY. (This + is nothing to do with our similarly-named `pterm', which is a + standalone terminal emulator for Unix systems; see question A.3.2.) + + A.4 Embedding PuTTY in other programs + + A.4.1 Is the SSH or Telnet code available as a DLL? + + No, it isn't. It would take a reasonable amount of rewriting for + this to be possible, and since the PuTTY project itself doesn't + believe in DLLs (they make installation more error-prone) none of us + has taken the time to do it. + + Most of the code cleanup work would be a good thing to happen in + general, so if anyone feels like helping, we wouldn't say no. + + See also the wishlist entry. + + A.4.2 Is the SSH or Telnet code available as a Visual Basic component? + + No, it isn't. None of the PuTTY team uses Visual Basic, and none of + us has any particular need to make SSH connections from a Visual + Basic application. In addition, all the preliminary work to turn it + into a DLL would be necessary first; and furthermore, we don't even + know how to write VB components. + + If someone offers to do some of this work for us, we might consider + it, but unless that happens I can't see VB integration being + anywhere other than the very bottom of our priority list. + + A.4.3 How can I use PuTTY to make an SSH connection from within another + program? + + Probably your best bet is to use Plink, the command-line connection + tool. If you can start Plink as a second Windows process, and + arrange for your primary process to be able to send data to the + Plink process, and receive data from it, through pipes, then you + should be able to make SSH connections from your program. + + This is what CVS for Windows does, for example. + + A.5 Details of PuTTY's operation + + A.5.1 What terminal type does PuTTY use? + + For most purposes, PuTTY can be considered to be an xterm terminal. + + PuTTY also supports some terminal control sequences not supported by + the real xterm: notably the Linux console sequences that reconfigure + the colour palette, and the title bar control sequences used by + DECterm (which are different from the xterm ones; PuTTY supports + both). + + By default, PuTTY announces its terminal type to the server as + `xterm'. If you have a problem with this, you can reconfigure it to + say something else; `vt220' might help if you have trouble. + + A.5.2 Where does PuTTY store its data? + + On Windows, PuTTY stores most of its data (saved sessions, SSH host + keys) in the Registry. The precise location is + + HKEY_CURRENT_USER\Software\SimonTatham\PuTTY + + and within that area, saved sessions are stored under `Sessions' + while host keys are stored under `SshHostKeys'. + + PuTTY also requires a random number seed file, to improve the + unpredictability of randomly chosen data needed as part of the + SSH cryptography. This is stored by default in a file called + `PUTTY.RND'; this is stored by default in the `Application Data' + directory, or failing that, one of a number of fallback locations. + If you want to change the location of the random number seed file, + you can put your chosen pathname in the Registry, at + + HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\RandSeedFile + + You can ask PuTTY to delete all this data; see question A.8.2. + + On Unix, PuTTY stores all of this data in a directory ~/.putty by + default. + + A.5.3 Why do small PuTTY icons appear next to the login prompts? + + As of PuTTY 0.71, some lines of text in the terminal window are + marked with a small copy of the PuTTY icon (as far as pixels allow). + + This is to show trustworthiness. When the PuTTY icon appears next to + a line of text, it indicates that that line of text was generated by + PuTTY itself, and not generated by the server and sent to PuTTY. + + Text that comes from the server does not have this icon, and we've + arranged that the server should not be able to fake it. (There's + no control sequence the server can send which will make PuTTY draw + its own icon, and if the server tries to move the cursor back up to + a line that _already_ has an icon and overwrite the text, the icon + will disappear.) + + This lets you tell the difference between (for example) a legitimate + prompt in which PuTTY itself asks you for your private key + passphrase, and a fake prompt in which the server tries to send + the identical text to trick you into telling _it_ your private key + passphrase. + + A.5.4 Why has Plink started saying `Press Return to begin session'? + + As of PuTTY 0.71, if you use Plink for an interactive SSH session, + then after the login phase has finished, it will present a final + interactive prompt saying `Access granted. Press Return to begin + session'. + + This is another defence against servers trying to mimic the real + authentication prompts after the session has started. When you pass + through that prompt, you know that everything after it is generated + by the server and not by Plink itself, so any request for your + private key passphrase should be treated with suspicion. + + In Plink, we can't use the defence described in section A.5.3: Plink + is running _in_ the terminal, so anything it can write into the + terminal, the server could write in the same way after the session + starts. And we can't just print a separator line without a pause, + because then the server could simply move the cursor back up to + it and overwrite it (probably with a brief flicker, but you might + easily miss that). The only robust defence anyone has come up with + involves this pause. + + If you trust your server not to be abusive, you can turn this + off. It will also not appear in various other circumstances where + Plink can be confident it isn't necessary. See section 7.2.3.6 for + details. + + A.6 HOWTO questions + + A.6.1 What login name / password should I use? + + This is not a question you should be asking _us_. + + PuTTY is a communications tool, for making connections to other + computers. We maintain the tool; we _don't_ administer any computers + that you're likely to be able to use, in the same way that the + people who make web browsers aren't responsible for most of the + content you can view in them. We cannot help with questions of this + sort. + + If you know the name of the computer you want to connect to, but + don't know what login name or password to use, you should talk to + whoever administers that computer. If you don't know who that is, + see the next question for some possible ways to find out. + + A.6.2 What commands can I type into my PuTTY terminal window? + + Again, this is not a question you should be asking _us_. You need + to read the manuals, or ask the administrator, of _the computer you + have connected to_. + + PuTTY does not process the commands you type into it. It's only a + communications tool. It makes a connection to another computer; it + passes the commands you type to that other computer; and it passes + the other computer's responses back to you. Therefore, the precise + range of commands you can use will not depend on PuTTY, but on what + kind of computer you have connected to and what software is running + on it. The PuTTY team cannot help you with that. + + (Think of PuTTY as being a bit like a telephone. If you phone + somebody up and you don't know what language to speak to make them + understand you, it isn't _the telephone company_'s job to find that + out for you. We just provide the means for you to get in touch; + making yourself understood is somebody else's problem.) + + If you are unsure of where to start looking for the administrator + of your server, a good place to start might be to remember how you + found out the host name in the PuTTY configuration. If you were + given that host name by e-mail, for example, you could try asking + the person who sent you that e-mail. If your company's IT department + provided you with ready-made PuTTY saved sessions, then that IT + department can probably also tell you something about what commands + you can type during those sessions. But the PuTTY maintainer team + does not administer any server you are likely to be connecting to, + and cannot help you with questions of this type. + + A.6.3 How can I make PuTTY start up maximised? + + Create a Windows shortcut to start PuTTY from, and set it as `Run + Maximized'. + + A.6.4 How can I create a Windows shortcut to start a particular saved + session directly? + + To run a PuTTY session saved under the name `mysession', create a + Windows shortcut that invokes PuTTY with a command line like + + \path\name\to\putty.exe -load "mysession" + + (Note: prior to 0.53, the syntax was `@session'. This is now + deprecated and may be removed at some point.) + + A.6.5 How can I start an SSH session straight from the command line? + + Use the command line `putty -ssh host.name'. Alternatively, create a + saved session that specifies the SSH protocol, and start the saved + session as shown in question A.6.4. + + A.6.6 How do I copy and paste between PuTTY and other Windows + applications? + + Copy and paste works similarly to the X Window System. You use the + left mouse button to select text in the PuTTY window. The act of + selection _automatically_ copies the text to the clipboard: there + is no need to press Ctrl-Ins or Ctrl-C or anything else. In fact, + pressing Ctrl-C will send a Ctrl-C character to the other end of + your connection (just like it does the rest of the time), which may + have unpleasant effects. The _only_ thing you need to do, to copy + text to the clipboard, is to select it. + + To paste the clipboard contents into a PuTTY window, by default you + click the right mouse button. If you have a three-button mouse and + are used to X applications, you can configure pasting to be done by + the middle button instead, but this is not the default because most + Windows users don't have a middle button at all. + + You can also paste by pressing Shift-Ins. + + A.6.7 How do I use all PuTTY's features (public keys, proxying, cipher + selection, etc.) in PSCP, PSFTP and Plink? + + Most major features (e.g., public keys, port forwarding) are + available through command line options. See the documentation. + + Not all features are accessible from the command line yet, although + we'd like to fix this. In the meantime, you can use most of PuTTY's + features if you create a PuTTY saved session, and then use the name + of the saved session on the command line in place of a hostname. + This works for PSCP, PSFTP and Plink (but don't expect port + forwarding in the file transfer applications!). + + A.6.8 How do I use PSCP.EXE? When I double-click it gives me a command + prompt window which then closes instantly. + + PSCP is a command-line application, not a GUI application. If you + run it without arguments, it will simply print a help message and + terminate. + + To use PSCP properly, run it from a Command Prompt window. See + chapter 5 in the documentation for more details. + + A.6.9 How do I use PSCP to copy a file whose name has spaces in? + + If PSCP is using the traditional SCP protocol, this is confusing. If + you're specifying a file at the local end, you just use one set of + quotes as you would normally do: + + pscp "local filename with spaces" user@host: + pscp user@host:myfile "local filename with spaces" + + But if the filename you're specifying is on the _remote_ side, you + have to use backslashes and two sets of quotes: + + pscp user@host:"\"remote filename with spaces\"" local_filename + pscp local_filename user@host:"\"remote filename with spaces\"" + + Worse still, in a remote-to-local copy you have to specify the local + file name explicitly, otherwise PSCP will complain that they don't + match (unless you specified the `-unsafe' option). The following + command will give an error message: + + c:\>pscp user@host:"\"oo er\"" . + warning: remote host tried to write to a file called 'oo er' + when we requested a file called '"oo er"'. + + Instead, you need to specify the local file name in full: + + c:\>pscp user@host:"\"oo er\"" "oo er" + + If PSCP is using the newer SFTP protocol, none of this is a problem, + and all filenames with spaces in are specified using a single pair + of quotes in the obvious way: + + pscp "local file" user@host: + pscp user@host:"remote file" . + +A.6.10 Should I run the 32-bit or the 64-bit version? + + If you're not sure, the 32-bit version is generally the safe option. + It will run perfectly well on all processors and on all versions of + Windows that PuTTY supports. PuTTY doesn't require to run as a 64- + bit application to work well, and having a 32-bit PuTTY on a 64-bit + system isn't likely to cause you any trouble. + + The 64-bit version (first released in 0.68) will only run if you + have a 64-bit processor _and_ a 64-bit edition of Windows (both of + these things are likely to be true of any recent Windows PC). It + will run somewhat faster (in particular, the cryptography will be + faster, especially during link setup), but it will consume slightly + more memory. + + If you need to use an external DLL for GSSAPI authentication, that + DLL may only be available in a 32-bit or 64-bit form, and that will + dictate the version of PuTTY you need to use. (You will probably + know if you're doing this; see section 4.24.2 in the documentation.) + + A.7 Troubleshooting + + A.7.1 Why do I see `Fatal: Protocol error: Expected control record' in + PSCP? + + This happens because PSCP was expecting to see data from the server + that was part of the PSCP protocol exchange, and instead it saw data + that it couldn't make any sense of at all. + + This almost always happens because the startup scripts in your + account on the server machine are generating output. This is + impossible for PSCP, or any other SCP client, to work around. You + should never use startup files (`.bashrc', `.cshrc' and so on) which + generate output in non-interactive sessions. + + This is not actually a PuTTY problem. If PSCP fails in this way, + then all other SCP clients are likely to fail in exactly the same + way. The problem is at the server end. + + A.7.2 I clicked on a colour in the Colours panel, and the colour didn't + change in my terminal. + + That isn't how you're supposed to use the Colours panel. + + During the course of a session, PuTTY potentially uses _all_ the + colours listed in the Colours panel. It's not a question of using + only one of them and you choosing which one; PuTTY will use them + _all_. The purpose of the Colours panel is to let you adjust the + appearance of all the colours. So to change the colour of the + cursor, for example, you would select `Cursor Colour', press the + `Modify' button, and select a new colour from the dialog box that + appeared. Similarly, if you want your session to appear in green, + you should select `Default Foreground' and press `Modify'. Clicking + on `ANSI Green' won't turn your session green; it will only allow + you to adjust the _shade_ of green used when PuTTY is instructed by + the server to display green text. + + A.7.3 After trying to establish an SSH-2 connection, PuTTY says `Out of + memory' and dies. + + If this happens just while the connection is starting up, this often + indicates that for some reason the client and server have failed to + establish a session encryption key. Somehow, they have performed + calculations that should have given each of them the same key, but + have ended up with different keys; so data encrypted by one and + decrypted by the other looks like random garbage. + + This causes an `out of memory' error because the first encrypted + data PuTTY expects to see is the length of an SSH message. Normally + this will be something well under 100 bytes. If the decryption has + failed, PuTTY will see a completely random length in the region of + two _gigabytes_, and will try to allocate enough memory to store + this non-existent message. This will immediately lead to it thinking + it doesn't have enough memory, and panicking. + + If this happens to you, it is quite likely to still be a PuTTY bug + and you should report it (although it might be a bug in your SSH + server instead); but it doesn't necessarily mean you've actually run + out of memory. + + A.7.4 When attempting a file transfer, either PSCP or PSFTP says `Out of + memory' and dies. + + This is almost always caused by your login scripts on the server + generating output. PSCP or PSFTP will receive that output when they + were expecting to see the start of a file transfer protocol, and + they will attempt to interpret the output as file-transfer protocol. + This will usually lead to an `out of memory' error for much the same + reasons as given in question A.7.3. + + This is a setup problem in your account on your server, _not_ a + PSCP/PSFTP bug. Your login scripts should _never_ generate output + during non-interactive sessions; secure file transfer is not the + only form of remote access that will break if they do. + + On Unix, a simple fix is to ensure that all the parts of your login + script that might generate output are in `.profile' (if you use a + Bourne shell derivative) or `.login' (if you use a C shell). Putting + them in more general files such as `.bashrc' or `.cshrc' is liable + to lead to problems. + + A.7.5 PSFTP transfers files much slower than PSCP. + + The throughput of PSFTP 0.54 should be much better than 0.53b and + prior; we've added code to the SFTP backend to queue several blocks + of data rather than waiting for an acknowledgement for each. (The + SCP backend did not suffer from this performance issue because SCP + is a much simpler protocol.) + + A.7.6 When I run full-colour applications, I see areas of black space + where colour ought to be, or vice versa. + + You almost certainly need to change the `Use background colour to + erase screen' setting in the Terminal panel. If there is too much + black space (the commoner situation), you should enable it, while + if there is too much colour, you should disable it. (See section + 4.3.5.) + + In old versions of PuTTY, this was disabled by default, and would + not take effect until you reset the terminal (see question A.7.7). + Since 0.54, it is enabled by default, and changes take effect + immediately. + + A.7.7 When I change some terminal settings, nothing happens. + + Some of the terminal options (notably Auto Wrap and background- + colour screen erase) actually represent the _default_ setting, + rather than the currently active setting. The server can send + sequences that modify these options in mid-session, but when the + terminal is reset (by server action, or by you choosing `Reset + Terminal' from the System menu) the defaults are restored. + + In versions 0.53b and prior, if you change one of these options in + the middle of a session, you will find that the change does not + immediately take effect. It will only take effect once you reset the + terminal. + + In version 0.54, the behaviour has changed - changes to these + settings take effect immediately. + + A.7.8 My PuTTY sessions unexpectedly close after they are idle for a + while. + + Some types of firewall, and almost any router doing Network Address + Translation (NAT, also known as IP masquerading), will forget about + a connection through them if the connection does nothing for too + long. This will cause the connection to be rudely cut off when + contact is resumed. + + You can try to combat this by telling PuTTY to send _keepalives_: + packets of data which have no effect on the actual session, but + which reassure the router or firewall that the network connection is + still active and worth remembering about. + + Keepalives don't solve everything, unfortunately; although they + cause greater robustness against this sort of router, they can also + cause a _loss_ of robustness against network dropouts. See section + 4.14.1 in the documentation for more discussion of this. + + A.7.9 PuTTY's network connections time out too quickly when network + connectivity is temporarily lost. + + This is a Windows problem, not a PuTTY problem. The timeout value + can't be set on per application or per session basis. To increase + the TCP timeout globally, you need to tinker with the Registry. + + On Windows 95, 98 or ME, the registry key you need to create or + change is + + HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\ + MSTCP\MaxDataRetries + + (it must be of type DWORD in Win95, or String in Win98/ME). (See MS + Knowledge Base article 158474 for more information.) + + On Windows NT, 2000, or XP, the registry key to create or change is + + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\ + Parameters\TcpMaxDataRetransmissions + + and it must be of type DWORD. (See MS Knowledge Base articles 120642 + and 314053 for more information.) + + Set the key's value to something like 10. This will cause Windows to + try harder to keep connections alive instead of abandoning them. + +A.7.10 When I cat a binary file, I get `PuTTYPuTTYPuTTY' on my command + line. + + Don't do that, then. + + This is designed behaviour; when PuTTY receives the character + Control-E from the remote server, it interprets it as a request + to identify itself, and so it sends back the string `PuTTY' as if + that string had been entered at the keyboard. Control-E should only + be sent by programs that are prepared to deal with the response. + Writing a binary file to your terminal is likely to output many + Control-E characters, and cause this behaviour. Don't do it. It's a + bad plan. + + To mitigate the effects, you could configure the answerback string + to be empty (see section 4.3.7); but writing binary files to your + terminal is likely to cause various other unpleasant behaviour, so + this is only a small remedy. + +A.7.11 When I cat a binary file, my window title changes to a nonsense + string. + + Don't do that, then. + + It is designed behaviour that PuTTY should have the ability + to adjust the window title on instructions from the server. + Normally the control sequence that does this should only be sent + deliberately, by programs that know what they are doing and intend + to put meaningful text in the window title. Writing a binary file to + your terminal runs the risk of sending the same control sequence by + accident, and cause unexpected changes in the window title. Don't do + it. + +A.7.12 My keyboard stops working once PuTTY displays the password prompt. + + No, it doesn't. PuTTY just doesn't display the password you type, so + that someone looking at your screen can't see what it is. + + Unlike the Windows login prompts, PuTTY doesn't display the password + as a row of asterisks either. This is so that someone looking at + your screen can't even tell how _long_ your password is, which might + be valuable information. + +A.7.13 One or more function keys don't do what I expected in a server-side + application. + + If you've already tried all the relevant options in the PuTTY + Keyboard panel, you may need to mail the PuTTY maintainers and ask. + + It is _not_ usually helpful just to tell us which application, + which server operating system, and which key isn't working; in + order to replicate the problem we would need to have a copy of + every operating system, and every application, that anyone has ever + complained about. + + PuTTY responds to function key presses by sending a sequence of + control characters to the server. If a function key isn't doing what + you expect, it's likely that the character sequence your application + is expecting to receive is not the same as the one PuTTY is sending. + Therefore what we really need to know is _what_ sequence the + application is expecting. + + The simplest way to investigate this is to find some other terminal + environment, in which that function key _does_ work; and then + investigate what sequence the function key is sending in that + situation. One reasonably easy way to do this on a Unix system is + to type the command `cat', and then press the function key. This is + likely to produce output of the form `^[[11~'. You can also do this + in PuTTY, to find out what sequence the function key is producing in + that. Then you can mail the PuTTY maintainers and tell us `I wanted + the F1 key to send `^[[11~', but instead it's sending `^[OP', can + this be done?', or something similar. + + You should still read the Feedback page on the PuTTY website (also + provided as appendix B in the manual), and follow the guidelines + contained in that. + +A.7.14 Why do I see `Couldn't load private key from ...'? Why can PuTTYgen + load my key but not PuTTY? + + It's likely that you've generated an SSH protocol 2 key with + PuTTYgen, but you're trying to use it in an SSH-1 connection. SSH- + 1 and SSH-2 keys have different formats, and (at least in 0.52) + PuTTY's reporting of a key in the wrong format isn't optimal. + + To connect using SSH-2 to a server that supports both versions, you + need to change the configuration from the default (see question + A.2.1). + +A.7.15 When I'm connected to a Red Hat Linux 8.0 system, some characters + don't display properly. + + A common complaint is that hyphens in man pages show up as a-acute. + + With release 8.0, Red Hat appear to have made UTF-8 the default + character set. There appears to be no way for terminal emulators + such as PuTTY to know this (as far as we know, the appropriate + escape sequence to switch into UTF-8 mode isn't sent). + + A fix is to configure sessions to RH8 systems to use UTF-8 + translation - see section 4.10.1 in the documentation. (Note that if + you use `Change Settings', changes may not take place immediately - + see question A.7.7.) + + If you really want to change the character set used by the server, + the right place is `/etc/sysconfig/i18n', but this shouldn't be + necessary. + +A.7.16 Since I upgraded to PuTTY 0.54, the scrollback has stopped working + when I run `screen'. + + PuTTY's terminal emulator has always had the policy that when the + `alternate screen' is in use, nothing is added to the scrollback. + This is because the usual sorts of programs which use the alternate + screen are things like text editors, which tend to scroll back and + forth in the same document a lot; so (a) they would fill up the + scrollback with a large amount of unhelpfully disordered text, and + (b) they contain their _own_ method for the user to scroll back to + the bit they were interested in. We have generally found this policy + to do the Right Thing in almost all situations. + + Unfortunately, `screen' is one exception: it uses the alternate + screen, but it's still usually helpful to have PuTTY's scrollback + continue working. The simplest solution is to go to the Features + control panel and tick `Disable switching to alternate terminal + screen'. (See section 4.6.4 for more details.) Alternatively, you + can tell `screen' itself not to use the alternate screen: the + `screen' FAQ suggests adding the line `termcapinfo xterm ti@:te@' to + your .screenrc file. + + The reason why this only started to be a problem in 0.54 is because + `screen' typically uses an unusual control sequence to switch to the + alternate screen, and previous versions of PuTTY did not support + this sequence. + +A.7.17 Since I upgraded Windows XP to Service Pack 2, I can't use addresses + like 127.0.0.2. + + Some people who ask PuTTY to listen on localhost addresses other + than 127.0.0.1 to forward services such as SMB and Windows Terminal + Services have found that doing so no longer works since they + upgraded to WinXP SP2. + + This is apparently an issue with SP2 that is acknowledged by + Microsoft in MS Knowledge Base article 884020. The article links to + a fix you can download. + + (_However_, we've been told that SP2 _also_ fixes the bug that means + you need to use non-127.0.0.1 addresses to forward Terminal Services + in the first place.) + +A.7.18 PSFTP commands seem to be missing a directory separator (slash). + + Some people have reported the following incorrect behaviour with + PSFTP: + + psftp> pwd + Remote directory is /dir1/dir2 + psftp> get filename.ext + /dir1/dir2filename.ext: no such file or directory + + This is not a bug in PSFTP. There is a known bug in some versions of + portable OpenSSH (bug 697) that causes these symptoms; it appears + to have been introduced around 3.7.x. It manifests only on certain + platforms (AIX is what has been reported to us). + + There is a patch for OpenSSH attached to that bug; it's also fixed + in recent versions of portable OpenSSH (from around 3.8). + +A.7.19 Do you want to hear about `Software caused connection abort'? + + In the documentation for PuTTY 0.53 and 0.53b, we mentioned that + we'd like to hear about any occurrences of this error. Since the + release of PuTTY 0.54, however, we've been convinced that this error + doesn't indicate that PuTTY's doing anything wrong, and we don't + need to hear about further occurrences. See section 10.15 for our + current documentation of this error. + +A.7.20 My SSH-2 session locks up for a few seconds every so often. + + Recent versions of PuTTY automatically initiate repeat key exchange + once per hour, to improve session security. If your client or server + machine is slow, you may experience this as a delay of anything up + to thirty seconds or so. + + These delays are inconvenient, but they are there for your + protection. If they really cause you a problem, you can choose to + turn off periodic rekeying using the `Kex' configuration panel (see + section 4.20), but be aware that you will be sacrificing security + for this. (Falling back to SSH-1 would also remove the delays, but + would lose a _lot_ more security still. We do not recommend it.) + +A.7.21 PuTTY fails to start up. Windows claims that `the application + configuration is incorrect'. + + This is caused by a bug in certain versions of Windows XP which is + triggered by PuTTY 0.58. This was fixed in 0.59. The `xp-wont-run' + entry in PuTTY's wishlist has more details. + +A.7.22 When I put 32-bit PuTTY in C:\WINDOWS\SYSTEM32 on my 64-bit Windows + system, `Duplicate Session' doesn't work. + + The short answer is not to put the PuTTY executables in that + location. + + On 64-bit systems, C:\WINDOWS\SYSTEM32 is intended to contain + only 64-bit binaries; Windows' 32-bit binaries live in + C:\WINDOWS\SYSWOW64. When a 32-bit PuTTY executable runs on a 64- + bit system, it cannot by default see the `real' C:\WINDOWS\SYSTEM32 + at all, because the File System Redirector arranges that the running + program sees the appropriate kind of binaries in SYSTEM32. Thus, + operations in the PuTTY suite that involve it accessing its own + executables, such as `New Session' and `Duplicate Session', will not + work. + +A.7.23 After I upgraded PuTTY to 0.68, I can no longer connect to my + embedded device or appliance. + + If your SSH server has started unexpectedly closing SSH connections + after you enter your password, and it worked before 0.68, you may + have a buggy server that objects to certain SSH protocol extensions. + + The SSH protocol recently gained a new `terminal mode', IUTF8, which + PuTTY sends by default; see section 4.25.2. This is the first new + terminal mode since the SSH-2 protocol was defined. While servers + are supposed to ignore modes they don't know about, some buggy + servers will unceremoniously close the connection if they see + anything they don't recognise. SSH servers in embedded devices, + network appliances, and the like seem to disproportionately have + this bug. + + If you think you have such a server, from 0.69 onwards you can + disable sending of the IUTF8 mode: on the SSH / TTY panel, select + IUTF8 on the list, select `Nothing', and press `Set'. (It's not + possible to disable sending this mode in 0.68.) + + A.8 Security questions + + A.8.1 Is it safe for me to download PuTTY and use it on a public PC? + + It depends on whether you trust that PC. If you don't trust the + public PC, don't use PuTTY on it, and don't use any other software + you plan to type passwords into either. It might be watching your + keystrokes, or it might tamper with the PuTTY binary you download. + There is _no_ program safe enough that you can run it on an actively + malicious PC and get away with typing passwords into it. + + If you do trust the PC, then it's probably OK to use PuTTY on it + (but if you don't trust the network, then the PuTTY download might + be tampered with, so it would be better to carry PuTTY with you on a + USB stick). + + A.8.2 What does PuTTY leave on a system? How can I clean up after it? + + PuTTY will leave some Registry entries, and a random seed file, on + the PC (see question A.5.2). Windows 7 and up also remember some + information about recently launched sessions for the `jump list' + feature. + + If you are using PuTTY on a public PC, or somebody else's PC, you + might want to clean this information up when you leave. You can do + that automatically, by running the command `putty -cleanup'. See + section 3.8.2 in the documentation for more detail. (Note that this + only removes settings for the currently logged-in user on multi-user + systems.) + + If PuTTY was installed from the installer package, it will also + appear in `Add/Remove Programs'. Current versions of the installer + do not offer to remove the above-mentioned items, so if you want + them removed you should run `putty -cleanup' before uninstalling. + + A.8.3 How come PuTTY now supports DSA, when the website used to say how + insecure it was? + + DSA has a major weakness _if badly implemented_: it relies on a + random number generator to far too great an extent. If the random + number generator produces a number an attacker can predict, the DSA + private key is exposed - meaning that the attacker can log in as you + on all systems that accept that key. + + The PuTTY policy changed because the developers were informed of + ways to implement DSA which do not suffer nearly as badly from this + weakness, and indeed which don't need to rely on random numbers at + all. For this reason we now believe PuTTY's DSA implementation is + probably OK. + + The recently added elliptic-curve signature methods are also DSA- + style algorithms, so they have this same weakness in principle. Our + ECDSA implementation uses the same defence as DSA, while our Ed25519 + implementation uses the similar system (but different in details) + that the Ed25519 spec mandates. + + A.8.4 Couldn't Pageant use VirtualLock() to stop private keys being + written to disk? + + Unfortunately not. The VirtualLock() function in the Windows API + doesn't do a proper job: it may prevent small pieces of a process's + memory from being paged to disk while the process is running, but + it doesn't stop the process's memory as a whole from being swapped + completely out to disk when the process is long-term inactive. And + Pageant spends most of its time inactive. + + A.9 Administrative questions + + A.9.1 Would you like me to register you a nicer domain name? + + No, thank you. Even if you can find one (most of them seem to + have been registered already, by people who didn't ask whether we + actually wanted it before they applied), we're happy with the PuTTY + web site being exactly where it is. It's not hard to find (just type + `putty' into google.com and we're the first link returned), and we + don't believe the administrative hassle of moving the site would be + worth the benefit. + + In addition, if we _did_ want a custom domain name, we would want to + run it ourselves, so we knew for certain that it would continue to + point where we wanted it, and wouldn't suddenly change or do strange + things. Having it registered for us by a third party who we don't + even know is not the best way to achieve this. + + A.9.2 Would you like free web hosting for the PuTTY web site? + + We already have some, thanks. + + A.9.3 Would you link to my web site from the PuTTY web site? + + Only if the content of your web page is of definite direct interest + to PuTTY users. If your content is unrelated, or only tangentially + related, to PuTTY, then the link would simply be advertising for + you. + + One very nice effect of the Google ranking mechanism is that by and + large, the most popular web sites get the highest rankings. This + means that when an ordinary person does a search, the top item in + the search is very likely to be a high-quality site or the site they + actually wanted, rather than the site which paid the most money for + its ranking. + + The PuTTY web site is held in high esteem by Google, for precisely + this reason: lots of people have linked to it simply because they + like PuTTY, without us ever having to ask anyone to link to us. We + feel that it would be an abuse of this esteem to use it to boost the + ranking of random advertisers' web sites. If you want your web site + to have a high Google ranking, we'd prefer that you achieve this the + way we did - by being good enough at what you do that people will + link to you simply because they like you. + + In particular, we aren't interested in trading links for money + (see above), and we _certainly_ aren't interested in trading links + for other links (since we have no advertising on our web site, our + Google ranking is not even directly worth anything to us). If we + don't want to link to you for free, then we probably won't want to + link to you at all. + + If you have software based on PuTTY, or specifically designed to + interoperate with PuTTY, or in some other way of genuine interest to + PuTTY users, then we will probably be happy to add a link to you on + our Links page. And if you're running a particularly valuable mirror + of the PuTTY web site, we might be interested in linking to you from + our Mirrors page. + + A.9.4 Why don't you move PuTTY to SourceForge? + + Partly, because we don't want to move the web site location (see + question A.9.1). + + Also, security reasons. PuTTY is a security product, and as such it + is particularly important to guard the code and the web site against + unauthorised modifications which might introduce subtle security + flaws. Therefore, we prefer that the Git repository, web site and + FTP site remain where they are, under the direct control of system + administrators we know and trust personally, rather than being run + by a large organisation full of people we've never met and which is + known to have had breakins in the past. + + No offence to SourceForge; I think they do a wonderful job. But + they're not ideal for everyone, and in particular they're not ideal + for us. + + A.9.5 Why can't I subscribe to the putty-bugs mailing list? + + Because you're not a member of the PuTTY core development team. The + putty-bugs mailing list is not a general newsgroup-like discussion + forum; it's a contact address for the core developers, and an + _internal_ mailing list for us to discuss things among ourselves. + If we opened it up for everybody to subscribe to, it would turn + into something more like a newsgroup and we would be completely + overwhelmed by the volume of traffic. It's hard enough to keep up + with the list as it is. + + A.9.6 If putty-bugs isn't a general-subscription mailing list, what is? + + There isn't one, that we know of. + + If someone else wants to set up a mailing list or other forum for + PuTTY users to help each other with common problems, that would + be fine with us, though the PuTTY team would almost certainly not + have the time to read it. It's probably better to use one of the + established newsgroups for this purpose (see section B.1.2). + + A.9.7 How can I donate to PuTTY development? + + Please, _please_ don't feel you have to. PuTTY is completely free + software, and not shareware. We think it's very important that + _everybody_ who wants to use PuTTY should be able to, whether they + have any money or not; so the last thing we would want is for a + PuTTY user to feel guilty because they haven't paid us any money. If + you want to keep your money, please do keep it. We wouldn't dream of + asking for any. + + Having said all that, if you still really _want_ to give us money, + we won't argue :-) The easiest way for us to accept donations is if + you send money to using PayPal (www.paypal.com). + If you don't like PayPal, talk to us; we can probably arrange some + alternative means. + + Small donations (tens of dollars or tens of euros) will probably + be spent on beer or curry, which helps motivate our volunteer team + to continue doing this for the world. Larger donations will be + spent on something that actually helps development, if we can find + anything (perhaps new hardware, or a copy of Windows XP), but if we + can't find anything then we'll just distribute the money among the + developers. If you want to be sure your donation is going towards + something worthwhile, ask us first. If you don't like these terms, + feel perfectly free not to donate. We don't mind. + + A.9.8 Can I have permission to put PuTTY on a cover disk / distribute it + with other software / etc? + + Yes. For most things, you need not bother asking us explicitly for + permission; our licence already grants you permission. + + See section B.8 for more details. + + A.9.9 Can you sign an agreement indemnifying us against security problems + in PuTTY? + + No! + + A vendor of physical security products (e.g. locks) might plausibly + be willing to accept financial liability for a product that failed + to perform as advertised and resulted in damage (e.g. valuables + being stolen). The reason they can afford to do this is because they + sell a _lot_ of units, and only a small proportion of them will + fail; so they can meet their financial liability out of the income + from all the rest of their sales, and still have enough left over + to make a profit. Financial liability is intrinsically linked to + selling your product for money. + + There are two reasons why PuTTY is not analogous to a physical + lock in this context. One is that software products don't exhibit + random variation: _if_ PuTTY has a security hole (which does happen, + although we do our utmost to prevent it and to respond quickly + when it does), every copy of PuTTY will have the same hole, so + it's likely to affect all the users at the same time. So even if + our users were all paying us to use PuTTY, we wouldn't be able to + _simultaneously_ pay every affected user compensation in excess of + the amount they had paid us in the first place. It just wouldn't + work. + + The second, much more important, reason is that PuTTY users _don't_ + pay us. The PuTTY team does not have an income; it's a volunteer + effort composed of people spending their spare time to try to write + useful software. We aren't even a company or any kind of legally + recognised organisation. We're just a bunch of people who happen to + do some stuff in our spare time. + + Therefore, to ask us to assume financial liability is to ask us to + assume a risk of having to pay it out of our own _personal_ pockets: + out of the same budget from which we buy food and clothes and pay + our rent. That's more than we're willing to give. We're already + giving a lot of our spare _time_ to developing software for free; if + we had to pay our own _money_ to do it as well, we'd start to wonder + why we were bothering. + + Free software fundamentally does not work on the basis of financial + guarantees. Your guarantee of the software functioning correctly is + simply that you have the source code and can check it before you + use it. If you want to be sure there aren't any security holes, do + a security audit of the PuTTY code, or hire a security engineer if + you don't have the necessary skills yourself: instead of trying to + ensure you can get compensation in the event of a disaster, try to + ensure there isn't a disaster in the first place. + + If you _really_ want financial security, see if you can find a + security engineer who will take financial responsibility for the + correctness of their review. (This might be less likely to suffer + from the everything-failing-at-once problem mentioned above, because + such an engineer would probably be reviewing a lot of _different_ + products which would tend to fail independently.) Failing that, + see if you can persuade an insurance company to insure you against + security incidents, and if the insurer demands it as a condition + then get our code reviewed by a security engineer they're happy + with. + +A.9.10 Can you sign this form granting us permission to use/distribute + PuTTY? + + If your form contains any clause along the lines of `the undersigned + represents and warrants', we're not going to sign it. This is + particularly true if it asks us to warrant that PuTTY is secure; + see question A.9.9 for more discussion of this. But it doesn't + really matter what we're supposed to be warranting: even if it's + something we already believe is true, such as that we don't infringe + any third-party copyright, we will not sign a document accepting + any legal or financial liability. This is simply because the PuTTY + development project has no income out of which to satisfy that + liability, or pay legal costs, should it become necessary. We cannot + afford to be sued. We are assuring you that _we have done our best_; + if that isn't good enough for you, tough. + + The existing PuTTY licence document already gives you permission + to use or distribute PuTTY in pretty much any way which does not + involve pretending you wrote it or suing us if it goes wrong. We + think that really ought to be enough for anybody. + + See also question A.9.12 for another reason why we don't want to do + this sort of thing. + +A.9.11 Can you write us a formal notice of permission to use PuTTY? + + We could, in principle, but it isn't clear what use it would be. If + you think there's a serious chance of one of the PuTTY copyright + holders suing you (which we don't!), you would presumably want a + signed notice from _all_ of them; and we couldn't provide that even + if we wanted to, because many of the copyright holders are people + who contributed some code in the past and with whom we subsequently + lost contact. Therefore the best we would be able to do _even + in theory_ would be to have the core development team sign the + document, which wouldn't guarantee you that some other copyright + holder might not sue. + + See also question A.9.12 for another reason why we don't want to do + this sort of thing. + +A.9.12 Can you sign _anything_ for us? + + Not unless there's an incredibly good reason. + + We are generally unwilling to set a precedent that involves us + having to enter into individual agreements with PuTTY users. + We estimate that we have literally _millions_ of users, and we + absolutely would not have time to go round signing specific + agreements with every one of them. So if you want us to sign + something specific for you, you might usefully stop to consider + whether there's anything special that distinguishes you from 999,999 + other users, and therefore any reason we should be willing to sign + something for you without it setting such a precedent. + + If your company policy requires you to have an individual agreement + with the supplier of any software you use, then your company policy + is simply not well suited to using popular free software, and we + urge you to consider this as a flaw in your policy. + +A.9.13 If you won't sign anything, can you give us some sort of assurance + that you won't make PuTTY closed-source in future? + + Yes and no. + + If what you want is an assurance that some _current version_ of + PuTTY which you've already downloaded will remain free, then you + already have that assurance: it's called the PuTTY Licence. It + grants you permission to use, distribute and copy the software to + which it applies; once we've granted that permission (which we + have), we can't just revoke it. + + On the other hand, if you want an assurance that _future_ versions + of PuTTY won't be closed-source, that's more difficult. We could + in principle sign a document stating that we would never release a + closed-source PuTTY, but that wouldn't assure you that we _would_ + keep releasing _open_-source PuTTYs: we would still have the option + of ceasing to develop PuTTY at all, which would surely be even worse + for you than making it closed-source! (And we almost certainly + wouldn't _want_ to sign a document guaranteeing that we would + actually continue to do development work on PuTTY; we certainly + wouldn't sign it for free. Documents like that are called contracts + of employment, and are generally not signed except in return for a + sizeable salary.) + + If we _were_ to stop developing PuTTY, or to decide to make all + future releases closed-source, then you would still be free to copy + the last open release in accordance with the current licence, and in + particular you could start your own fork of the project from that + release. If this happened, I confidently predict that _somebody_ + would do that, and that some kind of a free PuTTY would continue + to be developed. There's already precedent for that sort of thing + happening in free software. We can't guarantee that somebody _other + than you_ would do it, of course; you might have to do it yourself. + But we can assure you that there would be nothing _preventing_ + anyone from continuing free development if we stopped. + + (Finally, we can also confidently predict that if we made PuTTY + closed-source and someone made an open-source fork, most people + would switch to the latter. Therefore, it would be pretty stupid of + us to try it.) + +A.9.14 Can you provide us with export control information / FIPS + certification for PuTTY? + + Some people have asked us for an Export Control Classification + Number (ECCN) for PuTTY. We don't know whether we have one, and as a + team of free software developers based in the UK we don't have the + time, money, or effort to deal with US bureaucracy to investigate + any further. We believe that PuTTY falls under 5D002 on the US + Commerce Control List, but that shouldn't be taken as definitive. + If you need to know more you should seek professional legal advice. + The same applies to any other country's legal requirements and + restrictions. + + Similarly, some people have asked us for FIPS certification of the + PuTTY tools. Unless someone else is prepared to do the necessary + work and pay any costs, we can't provide this. + +A.9.15 As one of our existing software vendors, can you just fill in this + questionnaire for us? + + We periodically receive requests like this, from organisations + which have apparently sent out a form letter to everyone listed in + their big spreadsheet of `software vendors' requiring them all to + answer some long list of questions about supported OS versions, paid + support arrangements, compliance with assorted local regulations + we haven't heard of, contact phone numbers, and other such + administrivia. Many of the questions are obviously meaningless when + applied to PuTTY (we don't provide any paid support in the first + place!), most of the rest could have been answered with only a very + quick look at our website, and some we are actively unwilling to + answer (we are private individuals, why would we want to give out + our home phone numbers to large corporations?). + + We don't make a habit of responding in full to these questionnaires, + because _we are not a software vendor_. + + A software _vendor_ is a company to which you are paying lots of + money in return for some software. They know who you are, and they + know you're paying them money; so they have an incentive to fill in + your forms and questionnaires, to research any local regulations you + cite if they don't already know about them, and generally to provide + every scrap of information you might possibly need in the most + convenient manner for you, because they want to keep being paid. + + But we are a team of free software developers, and that means your + relationship with us is nothing like that at all. If you once + downloaded our software from our website, that's great and we hope + you found it useful, but it doesn't mean we have the least idea who + you are, or any incentive to do lots of unpaid work to support our + `relationship' with you. + + It's not that we are unwilling to _provide information_. We put as + much of it as we can on our website for your convenience, and if you + actually need to know some fact about PuTTY which you haven't been + able to find on the website (and which is not obviously inapplicable + to free software in the first place) then please do ask us, and + we'll try to answer as best we can. But we put up the website and + this FAQ precisely so that we _don't_ have to keep answering the + same questions over and over again, so we aren't prepared to fill in + completely generic form-letter questionnaires for people who haven't + done their best to find the answers here first. + + If you work for an organisation which you think might be at risk of + making this mistake, we urge you to reorganise your list of software + suppliers so that it clearly distinguishes paid vendors who know + about you from free software developers who don't have any idea who + you are. Then, only send out these mass mailings to the former. + +A.9.16 The `sha1sums' / `sha256sums' / etc files on your download page + don't match the binaries. + + People report this every so often, and usually the reason turns out + to be that they've matched up the wrong checksums file with the + wrong binaries. + + The PuTTY download page contains more than one version of the + software. There's a _latest release_ version; there are the + _development snapshots_; and when we're in the run-up to making a + release, there are also _pre-release_ builds of the upcoming new + version. Each one has its own collection of binaries, and its own + collection of checksums files to go with them. + + So if you've downloaded the release version of the actual program, + you need the release version of the checksums too, otherwise you + will see a mismatch. Similarly, the development snapshot binaries go + with the development snapshot checksums, and so on. (We've colour- + coded the download page in an effort to reduce this confusion a + bit.) + + Another thing to watch out for: as of 0.71, executables like + `putty.exe' come in two flavours for each platform: the standalone + versions on the website, each of which contains embedded help, and + the versions installed by the installer, which use a separate help + file also in the installer. We provide checksums for both; the + latter are indicated with `(installer version)' after the filename. + + If you have double-checked all that, and you still think there's + a real mismatch, then please send us a report carefully quoting + everything relevant: + + - the exact URL you got your binary from + + - the checksum of the binary after you downloaded + + - the exact URL you got your checksums file from + + - the checksum that file says the binary should have. + + A.10 Miscellaneous questions + +A.10.1 Is PuTTY a port of OpenSSH, or based on OpenSSH or OpenSSL? + + No, it isn't. PuTTY is almost completely composed of code written + from scratch for PuTTY. The only code we share with OpenSSH is the + detector for SSH-1 CRC compensation attacks, written by CORE SDI + S.A; we share no code at all with OpenSSL. + +A.10.2 Where can I buy silly putty? + + You're looking at the wrong web site; the only PuTTY we know about + here is the name of a computer program. + + If you want the kind of putty you can buy as an executive toy, the + PuTTY team can personally recommend Thinking Putty, which you can + buy from Crazy Aaron's Putty World, at www.puttyworld.com. + +A.10.3 What does `PuTTY' mean? + + It's the name of a popular SSH and Telnet client. Any other meaning + is in the eye of the beholder. It's been rumoured that `PuTTY' is + the antonym of `getty', or that it's the stuff that makes your + Windows useful, or that it's a kind of plutonium Teletype. We + couldn't possibly comment on such allegations. + +A.10.4 How do I pronounce `PuTTY'? + + Exactly like the English word `putty', which we pronounce /'pVti/. + +Appendix B: Feedback and bug reporting +-------------------------------------- + + This is a guide to providing feedback to the PuTTY development team. + It is provided as both a web page on the PuTTY site, and an appendix + in the PuTTY manual. + + Section B.1 gives some general guidelines for sending any kind of e- + mail to the development team. Following sections give more specific + guidelines for particular types of e-mail, such as bug reports and + feature requests. + + B.1 General guidelines + + The PuTTY development team gets a _lot_ of mail. If you can possibly + solve your own problem by reading the manual, reading the FAQ, + reading the web site, asking a fellow user, perhaps posting to a + newsgroup (see section B.1.2), or some other means, then it would + make our lives much easier. + + We get so much e-mail that we literally do not have time to answer + it all. We regret this, but there's nothing we can do about it. + So if you can _possibly_ avoid sending mail to the PuTTY team, we + recommend you do so. In particular, support requests (section B.6) + are probably better sent to newsgroups, or passed to a local expert + if possible. + + The PuTTY contact email address is a private mailing list containing + four or five core developers. Don't be put off by it being a mailing + list: if you need to send confidential data as part of a bug report, + you can trust the people on the list to respect that confidence. + Also, the archives aren't publicly available, so you shouldn't be + letting yourself in for any spam by sending us mail. + + Please use a meaningful subject line on your message. We get a lot + of mail, and it's hard to find the message we're looking for if they + all have subject lines like `PuTTY bug'. + + B.1.1 Sending large attachments + + Since the PuTTY contact address is a mailing list, e-mails larger + than 40Kb will be held for inspection by the list administrator, and + will not be allowed through unless they really appear to be worth + their large size. + + If you are considering sending any kind of large data file to the + PuTTY team, it's almost always a bad idea, or at the very least it + would be better to ask us first whether we actually need the file. + Alternatively, you could put the file on a web site and just send us + the URL; that way, we don't have to download it unless we decide we + actually need it, and only one of us needs to download it instead of + it being automatically copied to all the developers. + + (If the file contains confidential information, then you could + encrypt it with our Secure Contact Key; see section E.1 for + details.) + + Some people like to send mail in MS Word format. Please _don't_ + send us bug reports, or any other mail, as a Word document. Word + documents are roughly fifty times larger than writing the same + report in plain text. In addition, most of the PuTTY team read their + e-mail on Unix machines, so copying the file to a Windows box to run + Word is very inconvenient. Not only that, but several of us don't + even _have_ a copy of Word! + + Some people like to send us screen shots when demonstrating a + problem. Please don't do this without checking with us first + - we almost never actually need the information in the screen + shot. Sending a screen shot of an error box is almost certainly + unnecessary when you could just tell us in plain text what the + error was. (On some versions of Windows, pressing Ctrl-C when the + error box is displayed will copy the text of the message to the + clipboard.) Sending a full-screen shot is _occasionally_ useful, but + it's probably still wise to check whether we need it before sending + it. + + If you _must_ mail a screen shot, don't send it as a .BMP file. BMPs + have no compression and they are _much_ larger than other image + formats such as PNG, TIFF and GIF. Convert the file to a properly + compressed image format before sending it. + + Please don't mail us executables, at all. Our mail server blocks all + incoming e-mail containing executables, as a defence against the + vast numbers of e-mail viruses we receive every day. If you mail us + an executable, it will just bounce. + + If you have made a tiny modification to the PuTTY code, please + send us a _patch_ to the source code if possible, rather than + sending us a huge .ZIP file containing the complete sources plus + your modification. If you've only changed 10 lines, we'd prefer to + receive a mail that's 30 lines long than one containing multiple + megabytes of data we already have. + + B.1.2 Other places to ask for help + + There are two Usenet newsgroups that are particularly relevant to + the PuTTY tools: + + - `comp.security.ssh', for questions specific to using the SSH + protocol; + + - `comp.terminals', for issues relating to terminal emulation (for + instance, keyboard problems). + + Please use the newsgroup most appropriate to your query, and + remember that these are general newsgroups, not specifically about + PuTTY. + + If you don't have direct access to Usenet, you can access these + newsgroups through Google Groups (groups.google.com). + + B.2 Reporting bugs + + If you think you have found a bug in PuTTY, your first steps should + be: + + - Check the Wishlist page on the PuTTY website, and see if we + already know about the problem. If we do, it is almost certainly + not necessary to mail us about it, unless you think you have + extra information that might be helpful to us in fixing it. (Of + course, if we actually _need_ specific extra information about a + particular bug, the Wishlist page will say so.) + + - Check the Change Log on the PuTTY website, and see if we have + already fixed the bug in the development snapshots. + + - Check the FAQ on the PuTTY website (also provided as appendix + A in the manual), and see if it answers your question. The FAQ + lists the most common things which people think are bugs, but + which aren't bugs. + + - Download the latest development snapshot and see if the problem + still happens with that. This really is worth doing. As a + general rule we aren't very interested in bugs that appear in + the release version but not in the development version, because + that usually means they are bugs we have _already fixed_. On the + other hand, if you can find a bug in the development version + that doesn't appear in the release, that's likely to be a new + bug we've introduced since the release and we're definitely + interested in it. + + If none of those options solved your problem, and you still need + to report a bug to us, it is useful if you include some general + information: + + - Tell us what version of PuTTY you are running. To find this + out, use the `About PuTTY' option from the System menu. Please + _do not_ just tell us `I'm running the latest version'; e-mail + can be delayed and it may not be obvious which version was the + latest at the time you sent the message. + + - PuTTY is a multi-platform application; tell us what version of + what OS you are running PuTTY on. (If you're running on Unix, + or Windows for Arm, tell us, or we'll assume you're running on + Windows for Intel as this is overwhelmingly the case.) + + - Tell us what protocol you are connecting with: SSH, Telnet, + Rlogin, or Raw mode, or a serial connection. + + - Tell us what kind of server you are connecting to; what OS, and + if possible what SSH server (if you're using SSH). You can get + some of this information from the PuTTY Event Log (see section + 3.1.3.1 in the manual). + + - Send us the contents of the PuTTY Event Log, unless you have a + specific reason not to (for example, if it contains confidential + information that you think we should be able to solve your + problem without needing to know). + + - Try to give us as much information as you can to help us see + the problem for ourselves. If possible, give us a step-by-step + sequence of _precise_ instructions for reproducing the fault. + + - Don't just tell us that PuTTY `does the wrong thing'; tell us + exactly and precisely what it did, and also tell us exactly + and precisely what you think it should have done instead. Some + people tell us PuTTY does the wrong thing, and it turns out that + it was doing the right thing and their expectations were wrong. + Help to avoid this problem by telling us exactly what you think + it should have done, and exactly what it did do. + + - If you think you can, you're welcome to try to fix the + problem yourself. A patch to the code which fixes a bug is an + excellent addition to a bug report. However, a patch is never a + _substitute_ for a good bug report; if your patch is wrong or + inappropriate, and you haven't supplied us with full information + about the actual bug, then we won't be able to find a better + solution. + + - https://www.chiark.greenend.org.uk/~sgtatham/bugs.html is an + article on how to report bugs effectively in general. If your + bug report is _particularly_ unclear, we may ask you to go away, + read this article, and then report the bug again. + + It is reasonable to report bugs in PuTTY's documentation, if you + think the documentation is unclear or unhelpful. But we do need + to be given exact details of _what_ you think the documentation + has failed to tell you, or _how_ you think it could be made + clearer. If your problem is simply that you don't _understand_ the + documentation, we suggest posting to a newsgroup (see section B.1.2) + and seeing if someone will explain what you need to know. _Then_, if + you think the documentation could usefully have told you that, send + us a bug report and explain how you think we should change it. + + B.3 Reporting security vulnerabilities + + If you've found a security vulnerability in PuTTY, you might well + want to notify us using an encrypted communications channel, to + avoid disclosing information about the vulnerability before a fixed + release is available. + + For this purpose, we provide a GPG key suitable for encryption: the + Secure Contact Key. See section E.1 for details of this. + + (Of course, vulnerabilities are also bugs, so please do include as + much information as possible about them, the same way you would with + any other bug report.) + + B.4 Requesting extra features + + If you want to request a new feature in PuTTY, the very first things + you should do are: + + - Check the Wishlist page on the PuTTY website, and see if your + feature is already on the list. If it is, it probably won't + achieve very much to repeat the request. (But see section B.5 if + you want to persuade us to give your particular feature higher + priority.) + + - Check the Wishlist and Change Log on the PuTTY website, and + see if we have already added your feature in the development + snapshots. If it isn't clear, download the latest development + snapshot and see if the feature is present. If it is, then it + will also be in the next release and there is no need to mail us + at all. + + If you can't find your feature in either the development snapshots + _or_ the Wishlist, then you probably do need to submit a feature + request. Since the PuTTY authors are very busy, it helps if you try + to do some of the work for us: + + - Do as much of the design as you can. Think about `corner cases'; + think about how your feature interacts with other existing + features. Think about the user interface; if you can't come + up with a simple and intuitive interface to your feature, you + shouldn't be surprised if we can't either. Always imagine + whether it's possible for there to be more than one, or less + than one, of something you'd assumed there would be one of. + (For example, if you were to want PuTTY to put an icon in the + System tray rather than the Taskbar, you should think about what + happens if there's more than one PuTTY active; how would the + user tell which was which?) + + - If you can program, it may be worth offering to write the + feature yourself and send us a patch. However, it is likely to + be helpful if you confer with us first; there may be design + issues you haven't thought of, or we may be about to make big + changes to the code which your patch would clash with, or + something. If you check with the maintainers first, there is a + better chance of your code actually being usable. Also, read the + design principles listed in appendix D: if you do not conform to + them, we will probably not be able to accept your patch. + + B.5 Requesting features that have already been requested + + If a feature is already listed on the Wishlist, then it usually + means we would like to add it to PuTTY at some point. However, this + may not be in the near future. If there's a feature on the Wishlist + which you would like to see in the _near_ future, there are several + things you can do to try to increase its priority level: + + - Mail us and vote for it. (Be sure to mention that you've seen + it on the Wishlist, or we might think you haven't even _read_ + the Wishlist). This probably won't have very _much_ effect; if + a huge number of people vote for something then it may make a + difference, but one or two extra votes for a particular feature + are unlikely to change our priority list immediately. Offering a + new and compelling justification might help. Also, don't expect + a reply. + + - Offer us money if we do the work sooner rather than later. This + sometimes works, but not always. The PuTTY team all have full- + time jobs and we're doing all of this work in our free time; we + may sometimes be willing to give up some more of our free time + in exchange for some money, but if you try to bribe us for a + _big_ feature it's entirely possible that we simply won't have + the time to spare - whether you pay us or not. (Also, we don't + accept bribes to add _bad_ features to the Wishlist, because + our desire to provide high-quality software to the users comes + first.) + + - Offer to help us write the code. This is probably the _only_ way + to get a feature implemented quickly, if it's a big one that we + don't have time to do ourselves. + + B.6 Support requests + + If you're trying to make PuTTY do something for you and it isn't + working, but you're not sure whether it's a bug or not, then + _please_ consider looking for help somewhere else. This is one of + the most common types of mail the PuTTY team receives, and we simply + don't have time to answer all the questions. Questions of this type + include: + + - If you want to do something with PuTTY but have no idea where to + start, and reading the manual hasn't helped, try posting to a + newsgroup (see section B.1.2) and see if someone can explain it + to you. + + - If you have tried to do something with PuTTY but it hasn't + worked, and you aren't sure whether it's a bug in PuTTY or a bug + in your SSH server or simply that you're not doing it right, + then try posting to a newsgroup (see section B.1.2) and see if + someone can solve your problem. Or try doing the same thing with + a different SSH client and see if it works with that. Please do + not report it as a PuTTY bug unless you are really sure it _is_ + a bug in PuTTY. + + - If someone else installed PuTTY for you, or you're using PuTTY + on someone else's computer, try asking them for help first. + They're more likely to understand how they installed it and what + they expected you to use it for than we are. + + - If you have successfully made a connection to your server and + now need to know what to type at the server's command prompt, + or other details of how to use the server-end software, talk to + your server's system administrator. This is not the PuTTY team's + problem. PuTTY is only a communications tool, like a telephone; + if you can't speak the same language as the person at the other + end of the phone, it isn't the telephone company's job to teach + it to you. + + If you absolutely cannot get a support question answered any other + way, you can try mailing it to us, but we can't guarantee to have + time to answer it. + + B.7 Web server administration + + If the PuTTY web site is down (Connection Timed Out), please don't + bother mailing us to tell us about it. Most of us read our e-mail on + the same machines that host the web site, so if those machines are + down then we will notice _before_ we read our e-mail. So there's no + point telling us our servers are down. + + Of course, if the web site has some other error (Connection Refused, + 404 Not Found, 403 Forbidden, or something else) then we might _not_ + have noticed and it might still be worth telling us about it. + + If you want to report a problem with our web site, check that you're + looking at our _real_ web site and not a mirror. The real web site + is at `https://www.chiark.greenend.org.uk/~sgtatham/putty/'; if + that's not where you're reading this, then don't report the problem + to us until you've checked that it's really a problem with the + main site. If it's only a problem with the mirror, you should try + to contact the administrator of that mirror site first, and only + contact us if that doesn't solve the problem (in case we need to + remove the mirror from our list). + + B.8 Asking permission for things + + PuTTY is distributed under the MIT Licence (see appendix C for + details). This means you can do almost _anything_ you like with our + software, our source code, and our documentation. The only things + you aren't allowed to do are to remove our copyright notices or the + licence text itself, or to hold us legally responsible if something + goes wrong. + + So if you want permission to include PuTTY on a magazine cover disk, + or as part of a collection of useful software on a CD or a web site, + then _permission is already granted_. You don't have to mail us and + ask. Just go ahead and do it. We don't mind. + + (If you want to distribute PuTTY alongside your own application for + use with that application, or if you want to distribute PuTTY within + your own organisation, then we recommend, but do not insist, that + you offer your own first-line technical support, to answer questions + about the interaction of PuTTY with your environment. If your users + mail us directly, we won't be able to tell them anything useful + about your specific setup.) + + If you want to use parts of the PuTTY source code in another + program, then it might be worth mailing us to talk about technical + details, but if all you want is to ask permission then you don't + need to bother. You already have permission. + + If you just want to link to our web site, just go ahead. (It's not + clear that we _could_ stop you doing this, even if we wanted to!) + + B.9 Mirroring the PuTTY web site + + If you want to set up a mirror of the PuTTY website, go ahead and + set one up. Please don't bother asking us for permission before + setting up a mirror. You already have permission. + + If the mirror is in a country where we don't already have plenty + of mirrors, we may be willing to add it to the list on our mirrors + page. Read the guidelines on that page, make sure your mirror works, + and email us the information listed at the bottom of the page. + + Note that we do not _promise_ to list your mirror: we get a lot of + mirror notifications and yours may not happen to find its way to the + top of the list. + + Also note that we link to all our mirror sites using the + `rel="nofollow"' attribute. Running a PuTTY mirror is not intended + to be a cheap way to gain search rankings. + + If you have technical questions about the process of mirroring, then + you might want to mail us before setting up the mirror (see also the + guidelines on the Mirrors page); but if you just want to ask for + permission, you don't need to. You already have permission. + + B.10 Praise and compliments + + One of the most rewarding things about maintaining free software + is getting e-mails that just say `thanks'. We are always happy to + receive e-mails of this type. + + Regrettably we don't have time to answer them all in person. If you + mail us a compliment and don't receive a reply, _please_ don't think + we've ignored you. We did receive it and we were happy about it; we + just didn't have time to tell you so personally. + + To everyone who's ever sent us praise and compliments, in the past + and the future: _you're welcome_! + + B.11 E-mail address + + The actual address to mail is . + +Appendix C: PuTTY Licence +------------------------- + + PuTTY is copyright 1997-2019 Simon Tatham. + + Portions copyright Robert de Bath, Joris van Rantwijk, Delian + Delchev, Andreas Schultz, Jeroen Massar, Wez Furlong, Nicolas Barry, + Justin Bradford, Ben Harris, Malcolm Smith, Ahmad Khalifa, Markus + Kuhn, Colin Watson, Christopher Staite, Lorenz Diener, Christian + Brabandt, Jeff Smith, Pavel Kryukov, Maxim Kuznetsov, Svyatoslav + Kuzmich, Nico Williams, Viktor Dukhovni, and CORE SDI S.A. + + Permission is hereby granted, free of charge, to any person + obtaining a copy of this software and associated documentation files + (the `Software'), to deal in the Software without restriction, + including without limitation the rights to use, copy, modify, merge, + publish, distribute, sublicense, and/or sell copies of the Software, + and to permit persons to whom the Software is furnished to do so, + subject to the following conditions: + + The above copyright notice and this permission notice shall be + included in all copies or substantial portions of the Software. + + THE SOFTWARE IS PROVIDED `AS IS', WITHOUT WARRANTY OF ANY KIND, + EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES + OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND + NONINFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE + FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF + CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION + WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + +Appendix D: PuTTY hacking guide +------------------------------- + + This appendix lists a selection of the design principles applying + to the PuTTY source code. If you are planning to send code + contributions, you should read this first. + + D.1 Cross-OS portability + + Despite Windows being its main area of fame, PuTTY is no longer a + Windows-only application suite. It has a working Unix port; a Mac + port is in progress; more ports may or may not happen at a later + date. + + Therefore, embedding Windows-specific code in core modules such as + ssh.c is not acceptable. We went to great lengths to _remove_ all + the Windows-specific stuff from our core modules, and to shift it + out into Windows-specific modules. Adding large amounts of Windows- + specific stuff in parts of the code that should be portable is + almost guaranteed to make us reject a contribution. + + The PuTTY source base is divided into platform-specific modules + and platform-generic modules. The Unix-specific modules are all in + the `unix' subdirectory; the Windows-specific modules are in the + `windows' subdirectory. + + All the modules in the main source directory - notably _all_ of the + code for the various back ends - are platform-generic. We want to + keep them that way. + + This also means you should stick to the C semantics guaranteed by + the C standard: try not to make assumptions about the precise size + of basic types such as `int' and `long int'; don't use pointer casts + to do endianness-dependent operations, and so on. + + (Even _within_ a platform front end you should still be careful of + some of these portability issues. The Windows front end compiles on + both 32- and 64-bit x86 and also Arm.) + + Our current choice of C standards version is _mostly_ C99. With a + couple of exceptions, you can assume that C99 features are available + (in particular , and `inline'), but you + shouldn't use things that are new in C11 (such as or + _Generic). + + The exceptions to that rule are due to the need for Visual Studio + compatibility: + + - Don't use variable-length arrays. Visual Studio doesn't support + them even now that it's adopted the rest of C99. We use -Wvla + when building with gcc and clang, to make it easier to avoid + accidentally breaking that rule. + + - For historical reasons, we still build with one older VS version + which lacks . So that file is included centrally + in `defs.h', and has a set of workaround definitions for the + PRIx64-type macros we use. If you need to use another one + of those macros, you need to add a workaround definition in + `defs.h', and don't casually re-include anywhere + else in the source file. + + Here are a few portability assumptions that we _do_ currently allow + (because we'd already have to thoroughly vet the existing code if + they ever needed to change, and it doesn't seem worth doing that + unless we really have to): + + - You can assume `int' is _at least_ 32 bits wide. (We've never + tried to port PuTTY to a platform with 16-bit int, and it + doesn't look likely to be necessary in future.) + + - Similarly, you can assume `char' is exactly 8 bits. (Exceptions + to that are even less likely to be relevant to us than short + int.) + + - You can assume that using `memset' to write zero bytes over a + whole structure will have the effect of setting all its pointer + fields to NULL. (The standard itself guarantees this for + _integer_ fields, but not for pointers.) + + - You can assume that `time_t' has POSIX semantics, i.e. that + it represents an integer number of non-leap seconds since + 1970-01-01 00:00:00 UTC. (Times in this format are used in + X authorisation, but we could work around that by carefully + distinguishing local `time_t' from time values used in the wire + protocol; but these semantics of `time_t' are also baked into + the shared library API used by the GSSAPI authentication code, + which would be much harder to change.) + + - You can assume that the execution character encoding is a + superset of the printable characters of ASCII. (In particular, + it's fine to do arithmetic on a `char' value representing a + Latin alphabetic character, without bothering to allow for + EBCDIC or other non-consecutive encodings of the alphabet.) + + On the other hand, here are some particular things _not_ to assume: + + - Don't assume anything about the _signedness_ of `char'. In + particular, you _must_ cast `char' values to `unsigned char' + before passing them to any function (because those + expect a non-negative character value, or EOF). If you need + a particular signedness, explicitly specify `signed char' or + `unsigned char', or use C99 int8_t or uint8_t. + + - From past experience with MacOS, we're still a bit nervous about + '\n' and '\r' potentially having unusual meanings on a given + platform. So it's fine to say `\n' in a string you're passing to + `printf', but in any context where those characters appear in a + standardised wire protocol or a binary file format, they should + be spelled '\012' and '\015' respectively. + + D.2 Multiple backends treated equally + + PuTTY is not an SSH client with some other stuff tacked on the side. + PuTTY is a generic, multiple-backend, remote VT-terminal client + which happens to support one backend which is larger, more popular + and more useful than the rest. Any extra feature which can possibly + be general across all backends should be so: localising features + unnecessarily into the SSH back end is a design error. (For example, + we had several code submissions for proxy support which worked by + hacking ssh.c. Clearly this is completely wrong: the network.h + abstraction is the place to put it, so that it will apply to all + back ends equally, and indeed we eventually put it there after + another contributor sent a better patch.) + + The rest of PuTTY should try to avoid knowing anything about + specific back ends if at all possible. To support a feature which is + only available in one network protocol, for example, the back end + interface should be extended in a general manner such that _any_ + back end which is able to provide that feature can do so. If it so + happens that only one back end actually does, that's just the way it + is, but it shouldn't be relied upon by any code. + + D.3 Multiple sessions per process on some platforms + + Some ports of PuTTY - notably the in-progress Mac port - are + constrained by the operating system to run as a single process + potentially managing multiple sessions. + + Therefore, the platform-independent parts of PuTTY never use global + variables to store per-session data. The global variables that do + exist are tolerated because they are not specific to a particular + login session: `flags' defines properties that are expected to apply + equally to _all_ the sessions run by a single PuTTY process, the + random number state in sshrand.c and the timer list in timing.c + serve all sessions equally, and so on. But most data is specific to + a particular network session, and is therefore stored in dynamically + allocated data structures, and pointers to these structures are + passed around between functions. + + Platform-specific code can reverse this decision if it likes. The + Windows code, for historical reasons, stores most of its data as + global variables. That's OK, because _on Windows_ we know there is + only one session per PuTTY process, so it's safe to do that. But + changes to the platform-independent code should avoid introducing + global variables, unless they are genuinely cross-session. + + D.4 C, not C++ + + PuTTY is written entirely in C, not in C++. + + We have made _some_ effort to make it easy to compile our code using + a C++ compiler: notably, our `snew', `snewn' and `sresize' macros + explicitly cast the return values of malloc and realloc to the + target type. (This has type checking advantages even in C: it means + you never accidentally allocate the wrong size piece of memory for + the pointer type you're assigning it to. C++ friendliness is really + a side benefit.) + + We want PuTTY to continue being pure C, at least in the platform- + independent parts and the currently existing ports. Patches which + switch the Makefiles to compile it as C++ and start using classes + will not be accepted. Also, in particular, we disapprove of // + comments, at least for the moment. (Perhaps once C99 becomes + genuinely widespread we might be more lenient.) + + The one exception: a port to a new platform may use languages other + than C if they are necessary to code on that platform. If your + favourite PDA has a GUI with a C++ API, then there's no way you can + do a port of PuTTY without using C++, so go ahead and use it. But + keep the C++ restricted to that platform's subdirectory; if your + changes force the Unix or Windows ports to be compiled as C++, they + will be unacceptable to us. + + D.5 Security-conscious coding + + PuTTY is a network application and a security application. Assume + your code will end up being fed deliberately malicious data by + attackers, and try to code in a way that makes it unlikely to be a + security risk. + + In particular, try not to use fixed-size buffers for variable-size + data such as strings received from the network (or even the user). + We provide functions such as dupcat and dupprintf, which dynamically + allocate buffers of the right size for the string they construct. + Use these wherever possible. + + D.6 Independence of specific compiler + + Windows PuTTY can currently be compiled with any of three Windows + compilers: MS Visual C, the Cygwin / mingw32 GNU tools, and clang + (in MS compatibility mode). + + This is a really useful property of PuTTY, because it means people + who want to contribute to the coding don't depend on having a + specific compiler; so they don't have to fork out money for MSVC if + they don't already have it, but on the other hand if they _do_ have + it they also don't have to spend effort installing gcc alongside it. + They can use whichever compiler they happen to have available, or + install whichever is cheapest and easiest if they don't have one. + + Therefore, we don't want PuTTY to start depending on which compiler + you're using. Using GNU extensions to the C language, for example, + would ruin this useful property (not that anyone's ever tried + it!); and more realistically, depending on an MS-specific library + function supplied by the MSVC C library (_snprintf, for example) + is a mistake, because that function won't be available under the + other compilers. Any function supplied in an official Windows DLL + as part of the Windows API is fine, and anything defined in the C + library standard is also fine, because those should be available + irrespective of compilation environment. But things in between, + available as non-standard library and language extensions in only + one compiler, are disallowed. + + (_snprintf in particular should be unnecessary, since we provide + dupprintf; see section D.5.) + + Compiler independence should apply on all platforms, of course, not + just on Windows. + + D.7 Small code size + + PuTTY is tiny, compared to many other Windows applications. And + it's easy to install: it depends on no DLLs, no other applications, + no service packs or system upgrades. It's just one executable. You + install that executable wherever you want to, and run it. + + We want to keep both these properties - the small size, and the ease + of installation - if at all possible. So code contributions that + depend critically on external DLLs, or that add a huge amount to the + code size for a feature which is only useful to a small minority of + users, are likely to be thrown out immediately. + + We do vaguely intend to introduce a DLL plugin interface for PuTTY, + whereby seriously large extra features can be implemented in plugin + modules. The important thing, though, is that those DLLs will be + _optional_; if PuTTY can't find them on startup, it should run + perfectly happily and just won't provide those particular features. + A full installation of PuTTY might one day contain ten or twenty + little DLL plugins, which would cut down a little on the ease of + installation - but if you really needed ease of installation you + _could_ still just install the one PuTTY binary, or just the DLLs + you really needed, and it would still work fine. + + Depending on _external_ DLLs is something we'd like to avoid if + at all possible (though for some purposes, such as complex SSH + authentication mechanisms, it may be unavoidable). If it can't be + avoided, the important thing is to follow the same principle of + graceful degradation: if a DLL can't be found, then PuTTY should run + happily and just not supply the feature that depended on it. + + D.8 Single-threaded code + + PuTTY and its supporting tools, or at least the vast majority of + them, run in only one OS thread. + + This means that if you're devising some piece of internal mechanism, + there's no need to use locks to make sure it doesn't get called by + two threads at once. The only way code can be called re-entrantly is + by recursion. + + That said, most of Windows PuTTY's network handling is triggered + off Windows messages requested by WSAAsyncSelect(), so if you call + MessageBox() deep within some network event handling code you should + be aware that you might be re-entered if a network event comes in + and is passed on to our window procedure by the MessageBox() message + loop. + + Also, the front ends (in particular Windows Plink) can use multiple + threads if they like. However, Windows Plink keeps _very_ tight + control of its auxiliary threads, and uses them pretty much + exclusively as a form of select(). Pretty much all the code outside + windows/winplink.c is _only_ ever called from the one primary + thread; the others just loop round blocking on file handles and + send messages to the main thread when some real work needs doing. + This is not considered a portability hazard because that bit of + windows/winplink.c will need rewriting on other platforms in any + case. + + One important consequence of this: PuTTY has only one thread in + which to do everything. That `everything' may include managing + more than one login session (section D.3), managing multiple data + channels within an SSH session, responding to GUI events even when + nothing is happening on the network, and responding to network + requests from the server (such as repeat key exchange) even when the + program is dealing with complex user interaction such as the re- + configuration dialog box. This means that _almost none_ of the PuTTY + code can safely block. + + D.9 Keystrokes sent to the server wherever possible + + In almost all cases, PuTTY sends keystrokes to the server. Even + weird keystrokes that you think should be hot keys controlling + PuTTY. Even Alt-F4 or Alt-Space, for example. If a keystroke has a + well-defined escape sequence that it could usefully be sending to + the server, then it should do so, or at the very least it should be + configurably able to do so. + + To unconditionally turn a key combination into a hot key to control + PuTTY is almost always a design error. If a hot key is really truly + required, then try to find a key combination for it which _isn't_ + already used in existing PuTTYs (either it sends nothing to the + server, or it sends the same thing as some other combination). + Even then, be prepared for the possibility that one day that key + combination might end up being needed to send something to the + server - so make sure that there's an alternative way to invoke + whatever PuTTY feature it controls. + + D.10 640x480 friendliness in configuration panels + + There's a reason we have lots of tiny configuration panels instead + of a few huge ones, and that reason is that not everyone has a + 1600x1200 desktop. 640x480 is still a viable resolution for running + Windows (and indeed it's still the default if you start up in safe + mode), so it's still a resolution we care about. + + Accordingly, the PuTTY configuration box, and the PuTTYgen control + window, are deliberately kept just small enough to fit comfortably + on a 640x480 display. If you're adding controls to either of these + boxes and you find yourself wanting to increase the size of the + whole box, _don't_. Split it into more panels instead. + + D.11 Automatically generated Makefiles + + PuTTY is intended to compile on multiple platforms, and with + multiple compilers. It would be horrifying to try to maintain a + single Makefile which handled all possible situations, and just as + painful to try to directly maintain a set of matching Makefiles for + each different compilation environment. + + Therefore, we have moved the problem up by one level. In the PuTTY + source archive is a file called `Recipe', which lists which source + files combine to produce which binaries; and there is also a script + called mkfiles.pl, which reads `Recipe' and writes out the real + Makefiles. (The script also reads all the source files and analyses + their dependencies on header files, so we get an extra benefit from + doing it this way, which is that we can supply correct dependency + information even in environments where it's difficult to set up an + automated `make depend' phase.) + + You should _never_ edit any of the PuTTY Makefiles directly. + They are not stored in our source repository at all. They are + automatically generated by mkfiles.pl from the file `Recipe'. + + If you need to add a new object file to a particular binary, the + right thing to do is to edit `Recipe' and re-run mkfiles.pl. This + will cause the new object file to be added in every tool that + requires it, on every platform where it matters, in every Makefile + to which it is relevant, _and_ to get all the dependency data right. + + If you send us a patch that modifies one of the Makefiles, you just + waste our time, because we will have to convert it into a change + to `Recipe'. If you send us a patch that modifies _all_ of the + Makefiles, you will have wasted a lot of _your_ time as well! + + (There is a comment at the top of every Makefile in the PuTTY source + archive saying this, but many people don't seem to read it, so it's + worth repeating here.) + + D.12 Coroutines in the SSH code + + Large parts of the code in the various SSH modules (in fact most + of the protocol layers) are structured using a set of macros that + implement (something close to) Donald Knuth's `coroutines' concept + in C. + + Essentially, the purpose of these macros are to arrange that a + function can call crReturn() to return to its caller, and the next + time it is called control will resume from just after that crReturn + statement. + + This means that any local (automatic) variables declared in such a + function will be corrupted every time you call crReturn. If you need + a variable to persist for longer than that, you _must_ make it a + field in some appropriate structure containing the persistent state + of the coroutine - typically the main state structure for an SSH + protocol layer. + + See `https://www.chiark.greenend.org.uk/~sgtatham/coroutines.html' + for a more in-depth discussion of what these macros are for and how + they work. + + Another caveat: most of these coroutines are not _guaranteed_ to run + to completion, because the SSH connection (or whatever) that they're + part of might be interrupted at any time by an unexpected network + event or user action. So whenever a coroutine-managed variable + refers to a resource that needs releasing, you should also ensure + that the cleanup function for its containing state structure can + reliably release it even if the coroutine is aborted at an arbitrary + point. + + For example, if an SSH packet protocol layer has to have a field + that sometimes points to a piece of allocated memory, then you + should ensure that when you free that memory you reset the pointer + field to NULL. Then, no matter when the protocol layer's cleanup + function is called, it can reliably free the memory if there is any, + and not crash if there isn't. + + D.13 Single compilation of each source file + + The PuTTY build system for any given platform works on the following + very simple model: + + - Each source file is compiled precisely once, to produce a single + object file. + + - Each binary is created by linking together some combination of + those object files. + + Therefore, if you need to introduce functionality to a particular + module which is only available in some of the tool binaries (for + example, a cryptographic proxy authentication mechanism which needs + to be left out of PuTTYtel to maintain its usability in crypto- + hostile jurisdictions), the _wrong_ way to do it is by adding + #ifdefs in (say) proxy.c. This would require separate compilation + of proxy.c for PuTTY and PuTTYtel, which means that the entire + Makefile-generation architecture (see section D.11) would have to + be significantly redesigned. Unless you are prepared to do that + redesign yourself, _and_ guarantee that it will still port to any + future platforms we might decide to run on, you should not attempt + this! + + The _right_ way to introduce a feature like this is to put the + new code in a separate source file, and (if necessary) introduce + a second new source file defining the same set of functions, but + defining them as stubs which don't provide the feature. Then the + module whose behaviour needs to vary (proxy.c in this example) can + call the functions defined in these two modules, and it will either + provide the new feature or not provide it according to which of your + new modules it is linked with. + + Of course, object files are never shared _between_ platforms; so it + is allowable to use #ifdef to select between platforms. This happens + in puttyps.h (choosing which of the platform-specific include files + to use), and also in misc.c (the Windows-specific `Minefield' memory + diagnostic system). It should be used sparingly, though, if at all. + + D.14 Do as we say, not as we do + + The current PuTTY code probably does not conform strictly to _all_ + of the principles listed above. There may be the occasional SSH- + specific piece of code in what should be a backend-independent + module, or the occasional dependence on a non-standard X library + function under Unix. + + This should not be taken as a licence to go ahead and violate the + rules. Where we violate them ourselves, we're not happy about it, + and we would welcome patches that fix any existing problems. Please + try to help us make our code better, not worse! + +Appendix E: PuTTY download keys and signatures +---------------------------------------------- + + We create GPG signatures for all the PuTTY files distributed from + our web site, so that users can be confident that the files have not + been tampered with. Here we identify our public keys, and explain + our signature policy so you can have an accurate idea of what each + signature guarantees. This description is provided as both a web + page on the PuTTY site, and an appendix in the PuTTY manual. + + As of release 0.58, all of the PuTTY executables contain fingerprint + material (usually accessed via the `-pgpfp' command-line option), + such that if you have an executable you trust, you can use it to + establish a trust path, for instance to a newer version downloaded + from the Internet. + + As of release 0.67, the Windows executables and installer also + contain built-in signatures that are automatically verified by + Windows' own mechanism (`Authenticode'). The keys used for that are + different, and are not covered here. + + (Note that none of the keys, signatures, etc mentioned here have + anything to do with keys used with SSH - they are purely for + verifying the origin of files distributed by the PuTTY team.) + + E.1 Public keys + + We maintain multiple keys, stored with different levels of security + due to being used in different ways. See section E.2 below for + details. + + The keys we provide are: + + Snapshot Key + + Used to sign routine development builds of PuTTY: nightly + snapshots, pre-releases, and sometimes also custom diagnostic + builds we send to particular users. + + Release Key + + Used to sign manually released versions of PuTTY. + + Secure Contact Key + + An encryption-capable key suitable for people to send + confidential messages to the PuTTY team, e.g. reports of + vulnerabilities. + + Master Key + + Used to tie all the above keys into the GPG web of trust. The + Master Key signs all the other keys, and other GPG users have + signed it in turn. + + The current issue of those keys are available for download from the + PuTTY website, and are also available on PGP keyservers using the + key IDs listed below. + + *Master Key* (2018) + + RSA, 4096-bit. Key ID: 76BC7FE4EBFD2D9E. Fingerprint: + 24E1 B1C5 75EA 3C9F F752 A922 76BC 7FE4 EBFD 2D9E + + *Release Key* (2018) + + RSA, 3072-bit. Key ID: 6289A25F4AE8DA82. Fingerprint: + E273 94AC A3F9 D904 9522 E054 6289 A25F 4AE8 DA82 + + *Snapshot Key* (2018) + + RSA, 3072-bit. Key ID: 38BA7229B7588FD1. Fingerprint: + C92B 52E9 9AB6 1DDA 33DB 2B7A 38BA 7229 B758 8FD1 + + *Secure Contact Key* (2018) + + RSA, 3072-bit. Key ID: 657D487977F95C98. Fingerprint: + A680 0082 2998 6E46 22CA 0E43 657D 4879 77F9 5C98 + + E.2 Security details + + The various keys have various different security levels. This + section explains what those security levels are, and how far you can + expect to trust each key. + + E.2.1 The Development Snapshots key + + The Development Snapshots private key is stored _without a + passphrase_. This is necessary, because the snapshots are generated + every night without human intervention, so nobody would be able to + type a passphrase. + + The snapshots are built and signed on a team member's home + computers, before being uploaded to the web server from which you + download them. + + Therefore, a signature from the Development Snapshots key _DOES_ + protect you against: + + - People tampering with the PuTTY binaries between the PuTTY web + site and you. + + - The maintainers of our web server attempting to abuse their root + privilege to tamper with the binaries. + + But it _DOES NOT_ protect you against: + + - People tampering with the binaries before they are uploaded to + our download servers. + + - People tampering with the build machines so that the next set of + binaries they build will be malicious in some way. + + - People stealing the unencrypted private key from the build + machine it lives on. + + Of course, we take all reasonable precautions to guard the build + machines. But when you see a signature, you should always be certain + of precisely what it guarantees and precisely what it does not. + + E.2.2 The Releases key + + The Releases key is more secure: because it is only used at release + time, to sign each release by hand, we can store it encrypted. + + The Releases private key is kept encrypted on the developers' own + local machines. So an attacker wanting to steal it would have to + also steal the passphrase. + + E.2.3 The Secure Contact Key + + The Secure Contact Key is stored with a similar level of security to + the Release Key: it is stored with a passphrase, and no automated + script has access to it. + + E.2.4 The Master Keys + + The Master Key signs almost nothing. Its purpose is to bind the + other keys together and certify that they are all owned by the same + people and part of the same integrated setup. The only signatures + produced by the Master Key, _ever_, should be the signatures on the + other keys. + + The Master Key is especially long, and its private key and + passphrase are stored with special care. + + We have collected some third-party signatures on the Master Key, in + order to increase the chances that you can find a suitable trust + path to them. + + We have uploaded our various keys to public keyservers, so that even + if you don't know any of the people who have signed our keys, you + can still be reasonably confident that an attacker would find it + hard to substitute fake keys on all the public keyservers at once. + + E.3 Key rollover + + Our current keys were generated in August 2018. + + Each new Master Key is signed with the old one, to show that it + really is owned by the same people and not substituted by an + attacker. + + Each new Master Key also signs the previous Release Keys, in case + you're trying to verify the signatures on a release prior to the + rollover and can find a chain of trust to those keys from any of the + people who have signed our new Master Key. + + Each release is signed with the Release Key that was current at the + time of release. We don't go back and re-sign old releases with + newly generated keys. + + The details of all previous keys are given here. + + *Key generated in 2016* (when we first introduced the Secure Contact + Key) + + *Secure Contact Key* (2016) + + RSA, 2048-bit. Main key ID: 2048R/8A0AF00B (long version: + 2048R/C4FCAAD08A0AF00B). Encryption subkey ID: 2048R/50C2CF5C + (long version: 2048R/9EB39CC150C2CF5C). Fingerprint: + 8A26 250E 763F E359 75F3 118F C4FC AAD0 8A0A F00B + + *Keys generated in the 2015 rollover* + + *Master Key* (2015) + + RSA, 4096-bit. Key ID: 4096R/04676F7C (long + version: 4096R/AB585DC604676F7C). Fingerprint: + 440D E3B5 B7A1 CA85 B3CC 1718 AB58 5DC6 0467 6F7C + + *Release Key* (2015) + + RSA, 2048-bit. Key ID: 2048R/B43434E4 (long + version: 2048R/9DFE2648B43434E4). Fingerprint: + 0054 DDAA 8ADA 15D2 768A 6DE7 9DFE 2648 B434 34E4 + + *Snapshot Key* (2015) + + RSA, 2048-bit. Key ID: 2048R/D15F7E8A (long + version: 2048R/EEF20295D15F7E8A). Fingerprint: + 0A3B 0048 FE49 9B67 A234 FEB6 EEF2 0295 D15F 7E8A + + *Original keys generated in 2000* (two sets, RSA and DSA) + + *Master Key* (original RSA) + + RSA, 1024-bit. Key ID: 1024R/1E34AC41 (long + version: 1024R/9D5877BF1E34AC41). Fingerprint: + 8F 15 97 DA 25 30 AB 0D 88 D1 92 54 11 CF 0C 4C + + *Master Key* (original DSA) + + DSA, 1024-bit. Key ID: 1024D/6A93B34E (long + version: 1024D/4F5E6DF56A93B34E). Fingerprint: + 313C 3E76 4B74 C2C5 F2AE 83A8 4F5E 6DF5 6A93 B34E + + *Release Key* (original RSA) + + RSA, 1024-bit. Key ID: 1024R/B41CAE29 (long + version: 1024R/EF39CCC0B41CAE29). Fingerprint: + AE 65 D3 F7 85 D3 18 E0 3B 0C 9B 02 FF 3A 81 FE + + *Release Key* (original DSA) + + DSA, 1024-bit. Key ID: 1024D/08B0A90B (long + version: 1024D/FECD6F3F08B0A90B). Fingerprint: + 00B1 1009 38E6 9800 6518 F0AB FECD 6F3F 08B0 A90B + + *Snapshot Key* (original RSA) + + RSA, 1024-bit. Key ID: 1024R/32B903A9 (long + version: 1024R/FAAED21532B903A9). Fingerprint: + 86 8B 1F 79 9C F4 7F BD 8B 1B D7 8E C6 4E 4C 03 + + *Snapshot Key* (original DSA) + + DSA, 1024-bit. Key ID: 1024D/7D3E4A00 (long + version: 1024D/165E56F77D3E4A00). Fingerprint: + 63DD 8EF8 32F5 D777 9FF0 2947 165E 56F7 7D3E 4A00 + +Appendix F: SSH-2 names specified for PuTTY +------------------------------------------- + + There are various parts of the SSH-2 protocol where things + are specified using a textual name. Names ending in + @putty.projects.tartarus.org are reserved for allocation by the + PuTTY team. Allocated names are documented here. + + F.1 Connection protocol channel request names + + These names can be sent in a SSH_MSG_CHANNEL_REQUEST message. + + simple@putty.projects.tartarus.org + + This is sent by a client to announce that it will not have more + than one channel open at a time in the current connection (that + one being the one the request is sent on). The intention is that + the server, knowing this, can set the window on that one channel + to something very large, and leave flow control to TCP. There is + no message-specific data. + + winadj@putty.projects.tartarus.org + + PuTTY sends this request along with some + SSH_MSG_CHANNEL_WINDOW_ADJUST messages as part of its window- + size tuning. It can be sent on any type of channel. There is no + message-specific data. Servers MUST treat it as an unrecognised + request and respond with SSH_MSG_CHANNEL_FAILURE. + + (Some SSH servers get confused by this message, so there is a + bug-compatibility mode for disabling it. See section 4.28.3.) + + F.2 Key exchange method names + + rsa-sha1-draft-00@putty.projects.tartarus.org + + rsa-sha256-draft-00@putty.projects.tartarus.org + + rsa1024-sha1-draft-01@putty.projects.tartarus.org + + rsa1024-sha256-draft-01@putty.projects.tartarus.org + + rsa2048-sha256-draft-01@putty.projects.tartarus.org + + rsa1024-sha1-draft-02@putty.projects.tartarus.org + + rsa2048-sha512-draft-02@putty.projects.tartarus.org + + rsa1024-sha1-draft-03@putty.projects.tartarus.org + + rsa2048-sha256-draft-03@putty.projects.tartarus.org + + rsa1024-sha1-draft-04@putty.projects.tartarus.org + + rsa2048-sha256-draft-04@putty.projects.tartarus.org + + These appeared in various drafts of what eventually became + RFC 4432. They have been superseded by rsa1024-sha1 and rsa2048- + sha256. + + F.3 Encryption algorithm names + + arcfour128-draft-00@putty.projects.tartarus.org + + arcfour256-draft-00@putty.projects.tartarus.org + + These were used in drafts of what eventually became RFC 4345. + They have been superseded by arcfour128 and arcfour256. + +[PuTTY release 0.72] diff --git a/doc/puttygen.1 b/doc/puttygen.1 new file mode 100644 index 0000000..fcb7f1e --- /dev/null +++ b/doc/puttygen.1 @@ -0,0 +1,139 @@ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.TH "puttygen" "1" "2004\(hy03\(hy24" "PuTTY\ tool\ suite" "PuTTY\ tool\ suite" +.SH "NAME" +.PP +\fBputtygen\fP - public-key generator for the PuTTY tools +.SH "SYNOPSIS" +.PP +.nf +\fBputtygen\fP\ (\ \fIkeyfile\fP\ |\ \fB\-t\fP\ \fIkeytype\fP\ [\ \fB\-b\fP\ \fIbits\fP\ ]\ ) +\ \ \ \ \ \ \ \ \ [\ \fB\-C\fP\ \fInew\-comment\fP\ ]\ [\ \fB\-P\fP\ ]\ [\ \fB\-q\fP\ ] +\ \ \ \ \ \ \ \ \ [\ \fB\-O\fP\ \fIoutput\-type\fP\ |\ \fB\-l\fP\ |\ \fB\-L\fP\ |\ \fB\-p\fP\ ] +\ \ \ \ \ \ \ \ \ [\ \fB\-o\fP\ \fIoutput\-file\fP\ ] +.fi +.SH "DESCRIPTION" +.PP +\fBputtygen\fP is a tool to generate and manipulate SSH public and private key pairs. It is part of the PuTTY suite, although it can also interoperate with the key formats used by some other SSH clients. +.PP +When you run \fBputtygen\fP, it does three things. Firstly, it either loads an existing key file (if you specified \fIkeyfile\fP), or generates a new key (if you specified \fIkeytype\fP). Then, it optionally makes modifications to the key (changing the comment and/or the passphrase); finally, it outputs the key, or some information about the key, to a file. +.PP +All three of these phases are controlled by the options described in the following section. +.SH "OPTIONS" +.PP +In the first phase, \fBputtygen\fP either loads or generates a key. Note that generating a key requires random data, which can cause \fBputtygen\fP to pause, possibly for some time if your system does not have much randomness available. +.PP +The options to control this phase are: +.IP "\fIkeyfile\fP" +Specify a key file to be loaded. +.RS +.PP +Usually this will be a private key, which can be in the (de facto standard) SSH-1 key format, or in PuTTY's SSH-2 key format, or in either of the SSH-2 private key formats used by OpenSSH and ssh.com's implementation. +.PP +You can also specify a file containing only a \fIpublic\fP key here. The operations you can do are limited to outputting another public key format or a fingerprint. Public keys can be in RFC 4716 or OpenSSH format, or the standard SSH-1 format. +.RE +.IP "\fB\-t\fP \fIkeytype\fP" +Specify a type of key to generate. The acceptable values here are \fBrsa\fP, \fBdsa\fP, \fBecdsa\fP, and \fBed25519\fP (to generate SSH-2 keys), and \fBrsa1\fP (to generate SSH-1 keys). +.IP "\fB\-b\fP \fIbits\fP" +Specify the size of the key to generate, in bits. Default is 2048. +.IP "\fB\-q\fP" +Suppress the progress display when generating a new key. +.IP "\fB\-\-old\-passphrase\fP \fIfile\fP" +Specify a file name; the first line will be read from this file (removing any trailing newline) and used as the old passphrase. \fBCAUTION:\fP If the passphrase is important, the file should be stored on a temporary filesystem or else securely erased after use. +.IP "\fB\-\-random\-device\fP \fIdevice\fP" +Specify device to read entropy from. By default, \fBputtygen\fP uses \fB/dev/urandom\fP, falling back to \fB/dev/random\fP if it has to. +.PP +In the second phase, \fBputtygen\fP optionally alters properties of the key it has loaded or generated. The options to control this are: +.IP "\fB\-C\fP \fInew\-comment\fP" +Specify a comment string to describe the key. This comment string will be used by PuTTY to identify the key to you (when asking you to enter the passphrase, for example, so that you know which passphrase to type). +.IP "\fB\-P\fP" +Indicate that you want to change the key's passphrase. This is automatic when you are generating a new key, but not when you are modifying an existing key. +.PP +In the third phase, \fBputtygen\fP saves the key or information about it. The options to control this are: +.IP "\fB\-O\fP \fIoutput\-type\fP" +Specify the type of output you want \fBputtygen\fP to produce. Acceptable options are: +.RS +.IP "\fBprivate\fP" +Save the private key in a format usable by PuTTY. This will either be the standard SSH-1 key format, or PuTTY's own SSH-2 key format. +.IP "\fBpublic\fP" +Save the public key only. For SSH-1 keys, the standard public key format will be used (`\fB1024 37 5698745\fP...'). For SSH-2 keys, the public key will be output in the format specified by RFC 4716, which is a multi-line text file beginning with the line `\fB---- BEGIN SSH2 PUBLIC KEY ----\fP'. +.IP "\fBpublic-openssh\fP" +Save the public key only, in a format usable by OpenSSH. For SSH-1 keys, this output format behaves identically to \fBpublic\fP. For SSH-2 keys, the public key will be output in the OpenSSH format, which is a single line (`\fBssh-rsa AAAAB3NzaC1yc2\fP...'). +.IP "\fBfingerprint\fP" +Print the fingerprint of the public key. All fingerprinting algorithms are believed compatible with OpenSSH. +.IP "\fBprivate-openssh\fP" +Save an SSH-2 private key in OpenSSH's format, using the oldest format available to maximise backward compatibility. This option is not permitted for SSH-1 keys. +.IP "\fBprivate-openssh-new\fP" +As \fBprivate-openssh\fP, except that it forces the use of OpenSSH\*(Aqs newer format even for RSA, DSA, and ECDSA keys. +.IP "\fBprivate-sshcom\fP" +Save an SSH-2 private key in ssh.com's format. This option is not permitted for SSH-1 keys. +.PP +If no output type is specified, the default is \fBprivate\fP. +.RE +.IP "\fB\-o\fP \fIoutput\-file\fP" +Specify the file where \fBputtygen\fP should write its output. If this option is not specified, \fBputtygen\fP will assume you want to overwrite the original file if the input and output file types are the same (changing a comment or passphrase), and will assume you want to output to stdout if you are asking for a public key or fingerprint. Otherwise, the \fB\-o\fP option is required. +.IP "\fB\-l\fP" +Synonym for `\fB-O fingerprint\fP'. +.IP "\fB\-L\fP" +Synonym for `\fB-O public-openssh\fP'. +.IP "\fB\-p\fP" +Synonym for `\fB-O public\fP'. +.IP "\fB\-\-new\-passphrase\fP \fIfile\fP" +Specify a file name; the first line will be read from this file (removing any trailing newline) and used as the new passphrase. If the file is empty then the saved key will be unencrypted. \fBCAUTION:\fP If the passphrase is important, the file should be stored on a temporary filesystem or else securely erased after use. +.PP +The following options do not run PuTTYgen as normal, but print informational messages and then quit: +.IP "\fB\-h\fP, \fB\-\-help\fP" +Display a message summarizing the available options. +.IP "\fB\-V\fP, \fB\-\-version\fP" +Display the version of PuTTYgen. +.IP "\fB\-\-pgpfp\fP" +Display the fingerprints of the PuTTY PGP Master Keys, to aid in verifying new files released by the PuTTY team. +.SH "EXAMPLES" +.PP +To generate an SSH-2 RSA key pair and save it in PuTTY's own format (you will be prompted for the passphrase): +.PP +.nf +puttygen\ \-t\ rsa\ \-C\ "my\ home\ key"\ \-o\ mykey.ppk +.fi +.PP +To generate a larger (4096-bit) key: +.PP +.nf +puttygen\ \-t\ rsa\ \-b\ 4096\ \-C\ "my\ home\ key"\ \-o\ mykey.ppk +.fi +.PP +To change the passphrase on a key (you will be prompted for the old and new passphrases): +.PP +.nf +puttygen\ \-P\ mykey.ppk +.fi +.PP +To change the comment on a key: +.PP +.nf +puttygen\ \-C\ "new\ comment"\ mykey.ppk +.fi +.PP +To convert a key into OpenSSH's private key format: +.PP +.nf +puttygen\ mykey.ppk\ \-O\ private\-openssh\ \-o\ my\-openssh\-key +.fi +.PP +To convert a key \fIfrom\fP another format (\fBputtygen\fP will automatically detect the input key type): +.PP +.nf +puttygen\ my\-ssh.com\-key\ \-o\ mykey.ppk +.fi +.PP +To display the fingerprint of a key (some key types require a passphrase to extract even this much information): +.PP +.nf +puttygen\ \-l\ mykey.ppk +.fi +.PP +To add the OpenSSH-format public half of a key to your authorised keys file: +.PP +.nf +puttygen\ \-L\ mykey.ppk\ >>\ $HOME/.ssh/authorized_keys +.fi diff --git a/doc/puttytel.1 b/doc/puttytel.1 new file mode 100644 index 0000000..45feba1 --- /dev/null +++ b/doc/puttytel.1 @@ -0,0 +1,98 @@ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.TH "puttytel" "1" "2004\(hy03\(hy24" "PuTTY\ tool\ suite" "PuTTY\ tool\ suite" +.SH "NAME" +.PP +\fBputtytel\fP \- GUI Telnet and Rlogin client for X +.SH "SYNOPSIS" +.PP +.nf +\fBputtytel\fP\ [\ \fIoptions\fP\ ]\ [\ \fIhost\fP\ ] +.fi +.SH "DESCRIPTION" +.PP +\fBputtytel\fP is a graphical Telnet and Rlogin client for X. It is a direct port of the Windows Telnet and Rlogin client of the same name, and a cut-down cryptography-free version of PuTTY. +.SH "OPTIONS" +.PP +The command-line options supported by \fBputtytel\fP are: +.IP "\fB\-\-display\fP \fIdisplay\-name\fP" +Specify the X display on which to open \fBputtytel\fP. (Note this option has a double minus sign, even though none of the others do. This is because this option is supplied automatically by GTK. Sorry.) +.IP "\fB\-fn\fP \fIfont-name\fP" +Specify the font to use for normal text displayed in the terminal. For example, \fB\-fn\ fixed\fP, \fB\-fn\ "Monospace\ 12"\fP. +.IP "\fB\-fb\fP \fIfont-name\fP" +Specify the font to use for bold text displayed in the terminal. If the \fBBoldAsColour\fP resource is set to 1 (the default), bold text will be displayed in different colours instead of a different font, so this option will be ignored. If \fBBoldAsColour\fP is set to 0 or 2 and you do not specify a bold font, \fBputtytel\fP will overprint the normal font to make it look bolder. +.IP "\fB\-fw\fP \fIfont-name\fP" +Specify the font to use for double-width characters (typically Chinese, Japanese and Korean text) displayed in the terminal. +.IP "\fB\-fwb\fP \fIfont-name\fP" +Specify the font to use for bold double-width characters (typically Chinese, Japanese and Korean text). Like \fB-fb\fP, this will be ignored unless the \fBBoldAsColour\fP resource is set to 0 or 2. +.IP "\fB\-geometry\fP \fIgeometry\fP" +Specify the size of the terminal, in rows and columns of text. See \fIX(7)\fP for more information on the syntax of geometry specifications. +.IP "\fB\-sl\fP \fIlines\fP" +Specify the number of lines of scrollback to save off the top of the terminal. +.IP "\fB\-fg\fP \fIcolour\fP" +Specify the foreground colour to use for normal text. +.IP "\fB\-bg\fP \fIcolour\fP" +Specify the background colour to use for normal text. +.IP "\fB\-bfg\fP \fIcolour\fP" +Specify the foreground colour to use for bold text, if the \fBBoldAsColour\fP resource is set to 1 (the default) or 2. +.IP "\fB\-bbg\fP \fIcolour\fP" +Specify the foreground colour to use for bold reverse-video text, if the \fBBoldAsColour\fP resource is set to 1 (the default) or 2. (This colour is best thought of as the bold version of the background colour; so it only appears when text is displayed \fIin\fP the background colour.) +.IP "\fB\-cfg\fP \fIcolour\fP" +Specify the foreground colour to use for text covered by the cursor. +.IP "\fB\-cbg\fP \fIcolour\fP" +Specify the background colour to use for text covered by the cursor. In other words, this is the main colour of the cursor. +.IP "\fB\-title\fP \fItitle\fP" +Specify the initial title of the terminal window. (This can be changed under control of the server.) +.IP "\fB\-sb\-\fP or \fB+sb\fP" +Tells \fBputtytel\fP not to display a scroll bar. +.IP "\fB\-sb\fP" +Tells \fBputtytel\fP to display a scroll bar: this is the opposite of \fB\-sb\-\fP. This is the default option: you will probably only need to specify it explicitly if you have changed the default using the \fBScrollBar\fP resource. +.IP "\fB\-log\fP \fIlogfile\fP, \fB\-sessionlog\fP \fIlogfile\fP" +This option makes \fBputtytel\fP log all the terminal output to a file as well as displaying it in the terminal. +.IP "\fB\-cs\fP \fIcharset\fP" +This option specifies the character set in which \fBputtytel\fP should assume the session is operating. This character set will be used to interpret all the data received from the session, and all input you type or paste into \fBputtytel\fP will be converted into this character set before being sent to the session. +.RS +.PP +Any character set name which is valid in a MIME header (and supported by \fBputtytel\fP) should be valid here (examples are `\fBISO-8859-1\fP', `\fBwindows-1252\fP' or `\fBUTF-8\fP'). Also, any character encoding which is valid in an X logical font description should be valid (`\fBibm-cp437\fP', for example). +.PP +\fBputtytel\fP\*(Aqs default behaviour is to use the same character encoding as its primary font. If you supply a Unicode (\fBiso10646-1\fP) font, it will default to the UTF-8 character set. +.PP +Character set names are case-insensitive. +.RE +.IP "\fB\-nethack\fP" +Tells \fBputtytel\fP to enable NetHack keypad mode, in which the numeric keypad generates the NetHack \fBhjklyubn\fP direction keys. This enables you to play NetHack with the numeric keypad without having to use the NetHack \fBnumber_pad\fP option (which requires you to press `\fBn\fP' before any repeat count). So you can move with the numeric keypad, and enter repeat counts with the normal number keys. +.IP "\fB\-help\fP, \fB\-\-help\fP" +Display a message summarizing the available options. +.IP "\fB\-pgpfp\fP" +Display the fingerprints of the PuTTY PGP Master Keys, to aid in verifying new files released by the PuTTY team. +.IP "\fB\-load\fP \fIsession\fP" +Load a saved session by name. This allows you to run a saved session straight from the command line without having to go through the configuration box first. +.IP "\fB\-telnet\fP, \fB\-rlogin\fP, \fB\-raw\fP" +Select the protocol \fBputtytel\fP will use to make the connection. +.IP "\fB\-proxycmd\fP \fIcommand\fP" +Instead of making a TCP connection, use \fIcommand\fP as a proxy; network traffic will be redirected to the standard input and output of \fIcommand\fP. \fIcommand\fP must be a single word, so is likely to need quoting by the shell. +.RS +.PP +The special strings \fB%host\fP and \fB%port\fP in \fIcommand\fP will be replaced by the hostname and port number you want to connect to; to get a literal \fB%\fP sign, enter \fB%%\fP. +.PP +Backslash escapes are also supported, such as sequences like \fB\en\fP being replaced by a literal newline; to get a literal backslash, enter \fB\e\e\fP. (Further escaping may be required by the shell.) +.PP +(See the main PuTTY manual for full details of the supported \fB%\fP- and backslash-delimited tokens, although most of them are probably not very useful in this context.) +.RE +.IP "\fB\-l\fP \fIusername\fP" +Specify the username to use when logging in to the server. +.IP "\fB\-P\fP \fIport\fP" +Specify the port to connect to the server on. +.IP "\fB-4\fP, \fB-6\fP" +Force use of IPv4 or IPv6 for network connections. +.SH "SAVED SESSIONS" +.PP +Saved sessions are stored in a \fB.putty/sessions\fP subdirectory in your home directory. +.SH "MORE INFORMATION" +.PP +For more information on PuTTY and PuTTYtel, it's probably best to go and look at the manual on the web page: +.PP +\fBhttps://www.chiark.greenend.org.uk/~sgtatham/putty/\fP +.SH "BUGS" +.PP +This man page isn't terribly complete. diff --git a/doc/udp.but b/doc/udp.but index c853277..406b469 100644 --- a/doc/udp.but +++ b/doc/udp.but @@ -25,9 +25,8 @@ is almost guaranteed to make us reject a contribution. The PuTTY source base is divided into platform-specific modules and platform-generic modules. The Unix-specific modules are all in the -\c{unix} subdirectory; the Mac-specific modules are in the \c{mac} -subdirectory; the Windows-specific modules are in the \c{windows} -subdirectory. +\c{unix} subdirectory; the Windows-specific modules are in the +\c{windows} subdirectory. All the modules in the main source directory - notably \e{all} of the code for the various back ends - are platform-generic. We want diff --git a/doc/using.but b/doc/using.but index 515e3a4..82a9033 100644 --- a/doc/using.but +++ b/doc/using.but @@ -154,54 +154,6 @@ have special commands. The \q{break} signal can also be invoked from the keyboard with \i{Ctrl-Break}. -The following \I{Telnet special commands}special commands are -available in Telnet: - -\b \I{Are You There, Telnet special command}Are You There - -\b \I{Break, Telnet special command}Break - -\b \I{Synch, Telnet special command}Synch - -\b \I{Erase Character, Telnet special command}Erase Character - -\lcont{ -PuTTY can also be configured to send this when the Backspace key is -pressed; see \k{config-telnetkey}. -} - -\b \I{Erase Line, Telnet special command}Erase Line - -\b \I{Go Ahead, Telnet special command}Go Ahead - -\b \I{No Operation, Telnet special command}No Operation - -\lcont{ -Should have no effect. -} - -\b \I{Abort Process, Telnet special command}Abort Process - -\b \I{Abort Output, Telnet special command}Abort Output - -\b \I{Interrupt Process, Telnet special command}Interrupt Process - -\lcont{ -PuTTY can also be configured to send this when Ctrl-C is typed; see -\k{config-telnetkey}. -} - -\b \I{Suspend Process, Telnet special command}Suspend Process - -\lcont{ -PuTTY can also be configured to send this when Ctrl-Z is typed; see -\k{config-telnetkey}. -} - -\b \I{End Of Record, Telnet special command}End Of Record - -\b \I{End Of File, Telnet special command}End Of File - In an SSH connection, the following \I{SSH special commands}special commands are available: @@ -257,6 +209,54 @@ Only available in SSH-2, and only during a session. Sends various POSIX signals. Not honoured by all servers. } +The following \I{Telnet special commands}special commands are +available in Telnet: + +\b \I{Are You There, Telnet special command}Are You There + +\b \I{Break, Telnet special command}Break + +\b \I{Synch, Telnet special command}Synch + +\b \I{Erase Character, Telnet special command}Erase Character + +\lcont{ +PuTTY can also be configured to send this when the Backspace key is +pressed; see \k{config-telnetkey}. +} + +\b \I{Erase Line, Telnet special command}Erase Line + +\b \I{Go Ahead, Telnet special command}Go Ahead + +\b \I{No Operation, Telnet special command}No Operation + +\lcont{ +Should have no effect. +} + +\b \I{Abort Process, Telnet special command}Abort Process + +\b \I{Abort Output, Telnet special command}Abort Output + +\b \I{Interrupt Process, Telnet special command}Interrupt Process + +\lcont{ +PuTTY can also be configured to send this when Ctrl-C is typed; see +\k{config-telnetkey}. +} + +\b \I{Suspend Process, Telnet special command}Suspend Process + +\lcont{ +PuTTY can also be configured to send this when Ctrl-Z is typed; see +\k{config-telnetkey}. +} + +\b \I{End Of Record, Telnet special command}End Of Record + +\b \I{End Of File, Telnet special command}End Of File + With a serial connection, the only available special command is \I{Break, serial special command}\q{Break}. @@ -620,8 +620,6 @@ use the \c{-load} option (described in \k{using-cmdline-load}). \S{using-cleanup} \i\c{-cleanup} -\cfg{winhelp-topic}{options.cleanup} - If invoked with the \c{-cleanup} option, rather than running as normal, PuTTY will remove its \I{removing registry entries}registry entries and \i{random seed file} from the local machine (after @@ -1071,4 +1069,4 @@ Pageant stores the more critical information (hence benefits more from the extra protection), so it's reasonable to want to run Pageant but not PuTTY with the ACL restrictions. You can force Pageant to start subsidiary PuTTY processes with a restricted ACL if you also pass the -\c{-restrict-putty-acl} option. +\i\c{-restrict-putty-acl} option. diff --git a/doc/vstr.but b/doc/vstr.but new file mode 100644 index 0000000..6ae9d73 --- /dev/null +++ b/doc/vstr.but @@ -0,0 +1 @@ +\versionid PuTTY release 0.72 diff --git a/empty.h b/empty.h new file mode 100644 index 0000000..52cebd7 --- /dev/null +++ b/empty.h @@ -0,0 +1 @@ +/* Empty file touched by automake makefile to force rebuild of version.o */ diff --git a/fuzzterm.c b/fuzzterm.c index fbc4ced..a54f6fc 100644 --- a/fuzzterm.c +++ b/fuzzterm.c @@ -175,6 +175,7 @@ void dlg_coloursel_start(union control *ctrl, void *dlg, bool dlg_coloursel_results(union control *ctrl, void *dlg, int *r, int *g, int *b) { return false; } void dlg_refresh(union control *ctrl, void *dlg) { } +bool dlg_is_visible(union control *ctrl, dlgparam *dp) { return false; } const char *const appname = "FuZZterm"; const int ngsslibs = 0; diff --git a/import.c b/import.c index c441078..61f1437 100644 --- a/import.c +++ b/import.c @@ -1166,7 +1166,7 @@ static struct openssh_new_key *load_openssh_new_key(const Filename *filename, fclose(fp); fp = NULL; - if (ret->keyblob->len == 0 || !ret->keyblob) { + if (ret->keyblob->len == 0) { errmsg = "key body not present"; goto error; } @@ -1442,7 +1442,7 @@ static ssh2_userkey *openssh_new_read( } } - if (!retkey) { + if (!retkey->key) { errmsg = "key index out of range"; goto error; } diff --git a/install-sh b/install-sh new file mode 100644 index 0000000..59990a1 --- /dev/null +++ b/install-sh @@ -0,0 +1,508 @@ +#!/bin/sh +# install - install a program, script, or datafile + +scriptversion=2014-09-12.12; # UTC + +# This originates from X11R5 (mit/util/scripts/install.sh), which was +# later released in X11R6 (xc/config/util/install.sh) with the +# following copyright and license. +# +# Copyright (C) 1994 X Consortium +# +# Permission is hereby granted, free of charge, to any person obtaining a copy +# of this software and associated documentation files (the "Software"), to +# deal in the Software without restriction, including without limitation the +# rights to use, copy, modify, merge, publish, distribute, sublicense, and/or +# sell copies of the Software, and to permit persons to whom the Software is +# furnished to do so, subject to the following conditions: +# +# The above copyright notice and this permission notice shall be included in +# all copies or substantial portions of the Software. +# +# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +# X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN +# AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNEC- +# TION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. +# +# Except as contained in this notice, the name of the X Consortium shall not +# be used in advertising or otherwise to promote the sale, use or other deal- +# ings in this Software without prior written authorization from the X Consor- +# tium. +# +# +# FSF changes to this file are in the public domain. +# +# Calling this script install-sh is preferred over install.sh, to prevent +# 'make' implicit rules from creating a file called install from it +# when there is no Makefile. +# +# This script is compatible with the BSD install script, but was written +# from scratch. + +tab=' ' +nl=' +' +IFS=" $tab$nl" + +# Set DOITPROG to "echo" to test this script. + +doit=${DOITPROG-} +doit_exec=${doit:-exec} + +# Put in absolute file names if you don't have them in your path; +# or use environment vars. + +chgrpprog=${CHGRPPROG-chgrp} +chmodprog=${CHMODPROG-chmod} +chownprog=${CHOWNPROG-chown} +cmpprog=${CMPPROG-cmp} +cpprog=${CPPROG-cp} +mkdirprog=${MKDIRPROG-mkdir} +mvprog=${MVPROG-mv} +rmprog=${RMPROG-rm} +stripprog=${STRIPPROG-strip} + +posix_mkdir= + +# Desired mode of installed file. +mode=0755 + +chgrpcmd= +chmodcmd=$chmodprog +chowncmd= +mvcmd=$mvprog +rmcmd="$rmprog -f" +stripcmd= + +src= +dst= +dir_arg= +dst_arg= + +copy_on_change=false +is_target_a_directory=possibly + +usage="\ +Usage: $0 [OPTION]... [-T] SRCFILE DSTFILE + or: $0 [OPTION]... SRCFILES... DIRECTORY + or: $0 [OPTION]... -t DIRECTORY SRCFILES... + or: $0 [OPTION]... -d DIRECTORIES... + +In the 1st form, copy SRCFILE to DSTFILE. +In the 2nd and 3rd, copy all SRCFILES to DIRECTORY. +In the 4th, create DIRECTORIES. + +Options: + --help display this help and exit. + --version display version info and exit. + + -c (ignored) + -C install only if different (preserve the last data modification time) + -d create directories instead of installing files. + -g GROUP $chgrpprog installed files to GROUP. + -m MODE $chmodprog installed files to MODE. + -o USER $chownprog installed files to USER. + -s $stripprog installed files. + -t DIRECTORY install into DIRECTORY. + -T report an error if DSTFILE is a directory. + +Environment variables override the default commands: + CHGRPPROG CHMODPROG CHOWNPROG CMPPROG CPPROG MKDIRPROG MVPROG + RMPROG STRIPPROG +" + +while test $# -ne 0; do + case $1 in + -c) ;; + + -C) copy_on_change=true;; + + -d) dir_arg=true;; + + -g) chgrpcmd="$chgrpprog $2" + shift;; + + --help) echo "$usage"; exit $?;; + + -m) mode=$2 + case $mode in + *' '* | *"$tab"* | *"$nl"* | *'*'* | *'?'* | *'['*) + echo "$0: invalid mode: $mode" >&2 + exit 1;; + esac + shift;; + + -o) chowncmd="$chownprog $2" + shift;; + + -s) stripcmd=$stripprog;; + + -t) + is_target_a_directory=always + dst_arg=$2 + # Protect names problematic for 'test' and other utilities. + case $dst_arg in + -* | [=\(\)!]) dst_arg=./$dst_arg;; + esac + shift;; + + -T) is_target_a_directory=never;; + + --version) echo "$0 $scriptversion"; exit $?;; + + --) shift + break;; + + -*) echo "$0: invalid option: $1" >&2 + exit 1;; + + *) break;; + esac + shift +done + +# We allow the use of options -d and -T together, by making -d +# take the precedence; this is for compatibility with GNU install. + +if test -n "$dir_arg"; then + if test -n "$dst_arg"; then + echo "$0: target directory not allowed when installing a directory." >&2 + exit 1 + fi +fi + +if test $# -ne 0 && test -z "$dir_arg$dst_arg"; then + # When -d is used, all remaining arguments are directories to create. + # When -t is used, the destination is already specified. + # Otherwise, the last argument is the destination. Remove it from $@. + for arg + do + if test -n "$dst_arg"; then + # $@ is not empty: it contains at least $arg. + set fnord "$@" "$dst_arg" + shift # fnord + fi + shift # arg + dst_arg=$arg + # Protect names problematic for 'test' and other utilities. + case $dst_arg in + -* | [=\(\)!]) dst_arg=./$dst_arg;; + esac + done +fi + +if test $# -eq 0; then + if test -z "$dir_arg"; then + echo "$0: no input file specified." >&2 + exit 1 + fi + # It's OK to call 'install-sh -d' without argument. + # This can happen when creating conditional directories. + exit 0 +fi + +if test -z "$dir_arg"; then + if test $# -gt 1 || test "$is_target_a_directory" = always; then + if test ! -d "$dst_arg"; then + echo "$0: $dst_arg: Is not a directory." >&2 + exit 1 + fi + fi +fi + +if test -z "$dir_arg"; then + do_exit='(exit $ret); exit $ret' + trap "ret=129; $do_exit" 1 + trap "ret=130; $do_exit" 2 + trap "ret=141; $do_exit" 13 + trap "ret=143; $do_exit" 15 + + # Set umask so as not to create temps with too-generous modes. + # However, 'strip' requires both read and write access to temps. + case $mode in + # Optimize common cases. + *644) cp_umask=133;; + *755) cp_umask=22;; + + *[0-7]) + if test -z "$stripcmd"; then + u_plus_rw= + else + u_plus_rw='% 200' + fi + cp_umask=`expr '(' 777 - $mode % 1000 ')' $u_plus_rw`;; + *) + if test -z "$stripcmd"; then + u_plus_rw= + else + u_plus_rw=,u+rw + fi + cp_umask=$mode$u_plus_rw;; + esac +fi + +for src +do + # Protect names problematic for 'test' and other utilities. + case $src in + -* | [=\(\)!]) src=./$src;; + esac + + if test -n "$dir_arg"; then + dst=$src + dstdir=$dst + test -d "$dstdir" + dstdir_status=$? + else + + # Waiting for this to be detected by the "$cpprog $src $dsttmp" command + # might cause directories to be created, which would be especially bad + # if $src (and thus $dsttmp) contains '*'. + if test ! -f "$src" && test ! -d "$src"; then + echo "$0: $src does not exist." >&2 + exit 1 + fi + + if test -z "$dst_arg"; then + echo "$0: no destination specified." >&2 + exit 1 + fi + dst=$dst_arg + + # If destination is a directory, append the input filename; won't work + # if double slashes aren't ignored. + if test -d "$dst"; then + if test "$is_target_a_directory" = never; then + echo "$0: $dst_arg: Is a directory" >&2 + exit 1 + fi + dstdir=$dst + dst=$dstdir/`basename "$src"` + dstdir_status=0 + else + dstdir=`dirname "$dst"` + test -d "$dstdir" + dstdir_status=$? + fi + fi + + obsolete_mkdir_used=false + + if test $dstdir_status != 0; then + case $posix_mkdir in + '') + # Create intermediate dirs using mode 755 as modified by the umask. + # This is like FreeBSD 'install' as of 1997-10-28. + umask=`umask` + case $stripcmd.$umask in + # Optimize common cases. + *[2367][2367]) mkdir_umask=$umask;; + .*0[02][02] | .[02][02] | .[02]) mkdir_umask=22;; + + *[0-7]) + mkdir_umask=`expr $umask + 22 \ + - $umask % 100 % 40 + $umask % 20 \ + - $umask % 10 % 4 + $umask % 2 + `;; + *) mkdir_umask=$umask,go-w;; + esac + + # With -d, create the new directory with the user-specified mode. + # Otherwise, rely on $mkdir_umask. + if test -n "$dir_arg"; then + mkdir_mode=-m$mode + else + mkdir_mode= + fi + + posix_mkdir=false + case $umask in + *[123567][0-7][0-7]) + # POSIX mkdir -p sets u+wx bits regardless of umask, which + # is incompatible with FreeBSD 'install' when (umask & 300) != 0. + ;; + *) + # $RANDOM is not portable (e.g. dash); use it when possible to + # lower collision chance + tmpdir=${TMPDIR-/tmp}/ins$RANDOM-$$ + trap 'ret=$?; rmdir "$tmpdir/a/b" "$tmpdir/a" "$tmpdir" 2>/dev/null; exit $ret' 0 + + # As "mkdir -p" follows symlinks and we work in /tmp possibly; so + # create the $tmpdir first (and fail if unsuccessful) to make sure + # that nobody tries to guess the $tmpdir name. + if (umask $mkdir_umask && + $mkdirprog $mkdir_mode "$tmpdir" && + exec $mkdirprog $mkdir_mode -p -- "$tmpdir/a/b") >/dev/null 2>&1 + then + if test -z "$dir_arg" || { + # Check for POSIX incompatibilities with -m. + # HP-UX 11.23 and IRIX 6.5 mkdir -m -p sets group- or + # other-writable bit of parent directory when it shouldn't. + # FreeBSD 6.1 mkdir -m -p sets mode of existing directory. + test_tmpdir="$tmpdir/a" + ls_ld_tmpdir=`ls -ld "$test_tmpdir"` + case $ls_ld_tmpdir in + d????-?r-*) different_mode=700;; + d????-?--*) different_mode=755;; + *) false;; + esac && + $mkdirprog -m$different_mode -p -- "$test_tmpdir" && { + ls_ld_tmpdir_1=`ls -ld "$test_tmpdir"` + test "$ls_ld_tmpdir" = "$ls_ld_tmpdir_1" + } + } + then posix_mkdir=: + fi + rmdir "$tmpdir/a/b" "$tmpdir/a" "$tmpdir" + else + # Remove any dirs left behind by ancient mkdir implementations. + rmdir ./$mkdir_mode ./-p ./-- "$tmpdir" 2>/dev/null + fi + trap '' 0;; + esac;; + esac + + if + $posix_mkdir && ( + umask $mkdir_umask && + $doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir" + ) + then : + else + + # The umask is ridiculous, or mkdir does not conform to POSIX, + # or it failed possibly due to a race condition. Create the + # directory the slow way, step by step, checking for races as we go. + + case $dstdir in + /*) prefix='/';; + [-=\(\)!]*) prefix='./';; + *) prefix='';; + esac + + oIFS=$IFS + IFS=/ + set -f + set fnord $dstdir + shift + set +f + IFS=$oIFS + + prefixes= + + for d + do + test X"$d" = X && continue + + prefix=$prefix$d + if test -d "$prefix"; then + prefixes= + else + if $posix_mkdir; then + (umask=$mkdir_umask && + $doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir") && break + # Don't fail if two instances are running concurrently. + test -d "$prefix" || exit 1 + else + case $prefix in + *\'*) qprefix=`echo "$prefix" | sed "s/'/'\\\\\\\\''/g"`;; + *) qprefix=$prefix;; + esac + prefixes="$prefixes '$qprefix'" + fi + fi + prefix=$prefix/ + done + + if test -n "$prefixes"; then + # Don't fail if two instances are running concurrently. + (umask $mkdir_umask && + eval "\$doit_exec \$mkdirprog $prefixes") || + test -d "$dstdir" || exit 1 + obsolete_mkdir_used=true + fi + fi + fi + + if test -n "$dir_arg"; then + { test -z "$chowncmd" || $doit $chowncmd "$dst"; } && + { test -z "$chgrpcmd" || $doit $chgrpcmd "$dst"; } && + { test "$obsolete_mkdir_used$chowncmd$chgrpcmd" = false || + test -z "$chmodcmd" || $doit $chmodcmd $mode "$dst"; } || exit 1 + else + + # Make a couple of temp file names in the proper directory. + dsttmp=$dstdir/_inst.$$_ + rmtmp=$dstdir/_rm.$$_ + + # Trap to clean up those temp files at exit. + trap 'ret=$?; rm -f "$dsttmp" "$rmtmp" && exit $ret' 0 + + # Copy the file name to the temp name. + (umask $cp_umask && $doit_exec $cpprog "$src" "$dsttmp") && + + # and set any options; do chmod last to preserve setuid bits. + # + # If any of these fail, we abort the whole thing. If we want to + # ignore errors from any of these, just make sure not to ignore + # errors from the above "$doit $cpprog $src $dsttmp" command. + # + { test -z "$chowncmd" || $doit $chowncmd "$dsttmp"; } && + { test -z "$chgrpcmd" || $doit $chgrpcmd "$dsttmp"; } && + { test -z "$stripcmd" || $doit $stripcmd "$dsttmp"; } && + { test -z "$chmodcmd" || $doit $chmodcmd $mode "$dsttmp"; } && + + # If -C, don't bother to copy if it wouldn't change the file. + if $copy_on_change && + old=`LC_ALL=C ls -dlL "$dst" 2>/dev/null` && + new=`LC_ALL=C ls -dlL "$dsttmp" 2>/dev/null` && + set -f && + set X $old && old=:$2:$4:$5:$6 && + set X $new && new=:$2:$4:$5:$6 && + set +f && + test "$old" = "$new" && + $cmpprog "$dst" "$dsttmp" >/dev/null 2>&1 + then + rm -f "$dsttmp" + else + # Rename the file to the real destination. + $doit $mvcmd -f "$dsttmp" "$dst" 2>/dev/null || + + # The rename failed, perhaps because mv can't rename something else + # to itself, or perhaps because mv is so ancient that it does not + # support -f. + { + # Now remove or move aside any old file at destination location. + # We try this two ways since rm can't unlink itself on some + # systems and the destination file might be busy for other + # reasons. In this case, the final cleanup might fail but the new + # file should still install successfully. + { + test ! -f "$dst" || + $doit $rmcmd -f "$dst" 2>/dev/null || + { $doit $mvcmd -f "$dst" "$rmtmp" 2>/dev/null && + { $doit $rmcmd -f "$rmtmp" 2>/dev/null; :; } + } || + { echo "$0: cannot unlink or rename $dst" >&2 + (exit 1); exit 1 + } + } && + + # Now rename the file to the real destination. + $doit $mvcmd "$dsttmp" "$dst" + } + fi || exit 1 + + trap '' 0 + fi +done + +# Local variables: +# eval: (add-hook 'write-file-hooks 'time-stamp) +# time-stamp-start: "scriptversion=" +# time-stamp-format: "%:y-%02m-%02d.%02H" +# time-stamp-time-zone: "UTC" +# time-stamp-end: "; # UTC" +# End: diff --git a/ldisc.c b/ldisc.c index 660e05d..bd7ffb0 100644 --- a/ldisc.c +++ b/ldisc.c @@ -15,12 +15,10 @@ #define ECHOING (ldisc->localecho == FORCE_ON || \ (ldisc->localecho == AUTO && \ - (backend_ldisc_option_state(ldisc->backend, LD_ECHO) || \ - term_ldisc(ldisc->term, LD_ECHO)))) + (backend_ldisc_option_state(ldisc->backend, LD_ECHO)))) #define EDITING (ldisc->localedit == FORCE_ON || \ (ldisc->localedit == AUTO && \ - (backend_ldisc_option_state(ldisc->backend, LD_EDIT) || \ - term_ldisc(ldisc->term, LD_EDIT)))) + (backend_ldisc_option_state(ldisc->backend, LD_EDIT)))) static void c_write(Ldisc *ldisc, const void *buf, int len) { diff --git a/ldiscucs.c b/ldiscucs.c deleted file mode 100644 index d7a0e26..0000000 --- a/ldiscucs.c +++ /dev/null @@ -1,83 +0,0 @@ -/* - * ldisc.c: PuTTY line discipline. Sits between the input coming - * from keypresses in the window, and the output channel leading to - * the back end. Implements echo and/or local line editing, - * depending on what's currently configured. - */ - -#include -#include - -#include "putty.h" -#include "terminal.h" -#include "ldisc.h" - -void lpage_send(Ldisc *ldisc, - int codepage, const char *buf, int len, bool interactive) -{ - wchar_t *widebuffer = 0; - int widesize = 0; - int wclen; - - if (codepage < 0) { - ldisc_send(ldisc, buf, len, interactive); - return; - } - - widesize = len * 2; - widebuffer = snewn(widesize, wchar_t); - - wclen = mb_to_wc(codepage, 0, buf, len, widebuffer, widesize); - luni_send(ldisc, widebuffer, wclen, interactive); - - sfree(widebuffer); -} - -void luni_send(Ldisc *ldisc, const wchar_t *widebuf, int len, bool interactive) -{ - int ratio = (in_utf(ldisc->term))?3:1; - char *linebuffer; - int linesize; - int i; - char *p; - - linesize = len * ratio * 2; - linebuffer = snewn(linesize, char); - - if (in_utf(ldisc->term)) { - /* UTF is a simple algorithm */ - for (p = linebuffer, i = 0; i < len; i++) { - unsigned long ch = widebuf[i]; - - if (IS_SURROGATE(ch)) { -#ifdef PLATFORM_IS_UTF16 - if (i+1 < len) { - unsigned long ch2 = widebuf[i+1]; - if (IS_SURROGATE_PAIR(ch, ch2)) { - ch = FROM_SURROGATES(ch, ch2); - i++; - } - } else -#endif - { - /* Unrecognised UTF-16 sequence */ - ch = '.'; - } - } - - p += encode_utf8(p, ch); - } - } else { - int rv; - rv = wc_to_mb(ldisc->term->ucsdata->line_codepage, 0, widebuf, len, - linebuffer, linesize, NULL, ldisc->term->ucsdata); - if (rv >= 0) - p = linebuffer + rv; - else - p = linebuffer; - } - if (p > linebuffer) - ldisc_send(ldisc, linebuffer, p - linebuffer, interactive); - - sfree(linebuffer); -} diff --git a/mainchan.c b/mainchan.c index 1471261..320db2b 100644 --- a/mainchan.c +++ b/mainchan.c @@ -334,33 +334,13 @@ static void mainchan_ready(mainchan *mc) queue_idempotent_callback(&mc->ppl->ic_process_queue); } -struct mainchan_open_failure_abort_ctx { - Ssh *ssh; - char *abort_message; -}; - -static void mainchan_open_failure_abort(void *vctx) -{ - struct mainchan_open_failure_abort_ctx *ctx = - (struct mainchan_open_failure_abort_ctx *)vctx; - ssh_sw_abort( - ctx->ssh, "Server refused to open main channel: %s", - ctx->abort_message); - sfree(ctx->abort_message); - sfree(ctx); -} - static void mainchan_open_failure(Channel *chan, const char *errtext) { assert(chan->vt == &mainchan_channelvt); mainchan *mc = container_of(chan, mainchan, chan); - struct mainchan_open_failure_abort_ctx *ctx = - snew(struct mainchan_open_failure_abort_ctx); - - ctx->ssh = mc->ppl->ssh; - ctx->abort_message = dupstr(errtext); - queue_toplevel_callback(mainchan_open_failure_abort, ctx); + ssh_sw_abort_deferred(mc->ppl->ssh, + "Server refused to open main channel: %s", errtext); } static size_t mainchan_send(Channel *chan, bool is_stderr, diff --git a/memory.c b/memory.c index b6fb325..5d34025 100644 --- a/memory.c +++ b/memory.c @@ -10,26 +10,35 @@ #include "puttymem.h" #include "misc.h" -void *safemalloc(size_t n, size_t size) +void *safemalloc(size_t factor1, size_t factor2, size_t addend) { - void *p; + if (factor1 > SIZE_MAX / factor2) + goto fail; + size_t product = factor1 * factor2; - if (n > INT_MAX / size) { - p = NULL; - } else { - size *= n; - if (size == 0) size = 1; + if (addend > SIZE_MAX) + goto fail; + if (product > SIZE_MAX - addend) + goto fail; + size_t size = product + addend; + + if (size == 0) + size = 1; + + void *p; #ifdef MINEFIELD - p = minefield_c_malloc(size); + p = minefield_c_malloc(size); #else - p = malloc(size); + p = malloc(size); #endif - } if (!p) - out_of_memory(); + goto fail; return p; + + fail: + out_of_memory(); } void *saferealloc(void *ptr, size_t n, size_t size) @@ -111,7 +120,7 @@ void *safegrowarray(void *ptr, size_t *allocated, size_t eltsize, size_t newsize = oldsize + increment; void *toret; if (secret) { - toret = safemalloc(newsize, eltsize); + toret = safemalloc(newsize, eltsize, 0); memcpy(toret, ptr, oldsize * eltsize); smemclr(ptr, oldsize * eltsize); sfree(ptr); diff --git a/misc.c b/misc.c index c687dad..479d1a2 100644 --- a/misc.c +++ b/misc.c @@ -238,50 +238,63 @@ char *buildinfo(const char *newline) strbuf_catf(buf, ", emulating "); #endif strbuf_catf(buf, "Visual Studio", newline); -#if _MSC_VER == 1900 - strbuf_catf(buf, " 2015 / MSVC++ 14.0"); + +#if 0 + /* + * List of _MSC_VER values and their translations taken from + * https://docs.microsoft.com/en-us/cpp/preprocessor/predefined-macros + * except for 1920, which is not yet listed on that page as of + * 2019-03-22, and was determined experimentally by Sean Kain. + * + * The pointless #if 0 branch containing this comment is there so + * that every real clause can start with #elif and there's no + * anomalous first clause. That way the patch looks nicer when you + * add extra ones. + */ +#elif _MSC_VER == 1920 + strbuf_catf(buf, " 2019 (16.x)"); +#elif _MSC_VER == 1916 + strbuf_catf(buf, " 2017 version 15.9"); +#elif _MSC_VER == 1915 + strbuf_catf(buf, " 2017 version 15.8"); +#elif _MSC_VER == 1914 + strbuf_catf(buf, " 2017 version 15.7"); +#elif _MSC_VER == 1913 + strbuf_catf(buf, " 2017 version 15.6"); #elif _MSC_VER == 1912 - strbuf_catf(buf, " 2017 / MSVC++ 14.12"); + strbuf_catf(buf, " 2017 version 15.5"); +#elif _MSC_VER == 1911 + strbuf_catf(buf, " 2017 version 15.3"); +#elif _MSC_VER == 1910 + strbuf_catf(buf, " 2017 RTW (15.0)"); +#elif _MSC_VER == 1900 + strbuf_catf(buf, " 2015 (14.0)"); #elif _MSC_VER == 1800 - strbuf_catf(buf, " 2013 / MSVC++ 12.0"); + strbuf_catf(buf, " 2013 (12.0)"); #elif _MSC_VER == 1700 - strbuf_catf(buf, " 2012 / MSVC++ 11.0"); + strbuf_catf(buf, " 2012 (11.0)"); #elif _MSC_VER == 1600 - strbuf_catf(buf, " 2010 / MSVC++ 10.0"); + strbuf_catf(buf, " 2010 (10.0)"); #elif _MSC_VER == 1500 - strbuf_catf(buf, " 2008 / MSVC++ 9.0"); + strbuf_catf(buf, " 2008 (9.0)"); #elif _MSC_VER == 1400 - strbuf_catf(buf, " 2005 / MSVC++ 8.0"); + strbuf_catf(buf, " 2005 (8.0)"); #elif _MSC_VER == 1310 - strbuf_catf(buf, " 2003 / MSVC++ 7.1"); + strbuf_catf(buf, " .NET 2003 (7.1)"); #elif _MSC_VER == 1300 - strbuf_catf(buf, " 2003 / MSVC++ 7.0"); + strbuf_catf(buf, " .NET 2002 (7.0)"); +#elif _MSC_VER == 1200 + strbuf_catf(buf, " 6.0"); #else #ifdef PUTTY_CAC -#if _MSC_VER == 1910 - strbuf_catf(buf, " 2017 / MSVC++ 14.1"); -#elif _MSC_VER == 1911 - strbuf_catf(buf, " 2017 / MSVC++ 14.11"); -#elif _MSC_VER == 1912 - strbuf_catf(buf, " 2017 / MSVC++ 14.12"); -#elif _MSC_VER == 1913 - strbuf_catf(buf, " 2017 / MSVC++ 14.13"); -#elif _MSC_VER == 1914 - strbuf_catf(buf, " 2017 / MSVC++ 14.14"); -#elif _MSC_VER == 1915 - strbuf_catf(buf, " 2017 / MSVC++ 14.15"); -#elif _MSC_VER == 1916 - strbuf_catf(buf, " 2017 / MSVC++ 14.16"); -#elif _MSC_VER == 1920 - strbuf_catf(buf, " 2019 / MSVC++ 14.20"); -#else - strbuf_catf(buf, ", unrecognised version"); +#if _MSC_VER == 1921 + strbuf_catf(buf, " 2019 (16.1)"); #endif #else strbuf_catf(buf, ", unrecognised version"); #endif // PUTTY_CAC #endif - strbuf_catf(buf, " (_MSC_VER=%d)", (int)_MSC_VER); + strbuf_catf(buf, ", _MSC_VER=%d", (int)_MSC_VER); #endif #ifdef BUILDINFO_GTK diff --git a/misc.h b/misc.h index a6f9da4..465110a 100644 --- a/misc.h +++ b/misc.h @@ -24,11 +24,27 @@ char *host_strchr(const char *s, int c); char *host_strrchr(const char *s, int c); char *host_strduptrim(const char *s); +#ifdef __GNUC__ +/* + * On MinGW, the correct compiler format checking for vsnprintf() etc + * can depend on compile-time flags; these control whether you get + * ISO C or Microsoft's non-standard format strings. + * We sometimes use __attribute__ ((format)) for our own printf-like + * functions, which are ultimately interpreted by the toolchain-chosen + * printf, so we need to take that into account to get correct warnings. + */ +#ifdef __MINGW_PRINTF_FORMAT +#define PUTTY_PRINTF_ARCHETYPE __MINGW_PRINTF_FORMAT +#else +#define PUTTY_PRINTF_ARCHETYPE printf +#endif +#endif /* __GNUC__ */ + char *dupstr(const char *s); char *dupcat(const char *s1, ...); char *dupprintf(const char *fmt, ...) #ifdef __GNUC__ - __attribute__ ((format (printf, 1, 2))) + __attribute__ ((format (PUTTY_PRINTF_ARCHETYPE, 1, 2))) #endif ; char *dupvprintf(const char *fmt, va_list ap); @@ -97,6 +113,7 @@ static inline int toint(unsigned u) } char *fgetline(FILE *fp); +bool read_file_into(BinarySink *bs, FILE *fp); char *chomp(char *str); bool strstartswith(const char *s, const char *t); bool strendswith(const char *s, const char *t); @@ -168,8 +185,14 @@ static inline ptrlen ptrlen_from_strbuf(strbuf *sb) bool ptrlen_eq_string(ptrlen pl, const char *str); bool ptrlen_eq_ptrlen(ptrlen pl1, ptrlen pl2); int ptrlen_strcmp(ptrlen pl1, ptrlen pl2); +/* ptrlen_startswith and ptrlen_endswith write through their 'tail' + * argument if and only if it is non-NULL and they return true. Hence + * you can write ptrlen_startswith(thing, prefix, &thing), writing + * back to the same ptrlen it read from, to remove a prefix if present + * and say whether it did so. */ bool ptrlen_startswith(ptrlen whole, ptrlen prefix, ptrlen *tail); bool ptrlen_endswith(ptrlen whole, ptrlen suffix, ptrlen *tail); +ptrlen ptrlen_get_word(ptrlen *input, const char *separators); char *mkstr(ptrlen pl); int string_length_for_printf(size_t); /* Derive two printf arguments from a ptrlen, suitable for "%.*s" */ @@ -269,14 +292,14 @@ static inline uint64_t GET_64BIT_LSB_FIRST(const void *vp) static inline void PUT_64BIT_LSB_FIRST(void *vp, uint64_t value) { uint8_t *p = (uint8_t *)vp; - p[0] = value; - p[1] = (value) >> 8; - p[2] = (value) >> 16; - p[3] = (value) >> 24; - p[4] = (value) >> 32; - p[5] = (value) >> 40; - p[6] = (value) >> 48; - p[7] = (value) >> 56; + p[0] = (uint8_t)(value); + p[1] = (uint8_t)(value >> 8); + p[2] = (uint8_t)(value >> 16); + p[3] = (uint8_t)(value >> 24); + p[4] = (uint8_t)(value >> 32); + p[5] = (uint8_t)(value >> 40); + p[6] = (uint8_t)(value >> 48); + p[7] = (uint8_t)(value >> 56); } static inline uint32_t GET_32BIT_LSB_FIRST(const void *vp) @@ -289,10 +312,10 @@ static inline uint32_t GET_32BIT_LSB_FIRST(const void *vp) static inline void PUT_32BIT_LSB_FIRST(void *vp, uint32_t value) { uint8_t *p = (uint8_t *)vp; - p[0] = value; - p[1] = (value) >> 8; - p[2] = (value) >> 16; - p[3] = (value) >> 24; + p[0] = (uint8_t)(value); + p[1] = (uint8_t)(value >> 8); + p[2] = (uint8_t)(value >> 16); + p[3] = (uint8_t)(value >> 24); } static inline uint16_t GET_16BIT_LSB_FIRST(const void *vp) @@ -304,8 +327,8 @@ static inline uint16_t GET_16BIT_LSB_FIRST(const void *vp) static inline void PUT_16BIT_LSB_FIRST(void *vp, uint16_t value) { uint8_t *p = (uint8_t *)vp; - p[0] = value; - p[1] = (value) >> 8; + p[0] = (uint8_t)(value); + p[1] = (uint8_t)(value >> 8); } static inline uint64_t GET_64BIT_MSB_FIRST(const void *vp) @@ -320,14 +343,14 @@ static inline uint64_t GET_64BIT_MSB_FIRST(const void *vp) static inline void PUT_64BIT_MSB_FIRST(void *vp, uint64_t value) { uint8_t *p = (uint8_t *)vp; - p[7] = value; - p[6] = (value) >> 8; - p[5] = (value) >> 16; - p[4] = (value) >> 24; - p[3] = (value) >> 32; - p[2] = (value) >> 40; - p[1] = (value) >> 48; - p[0] = (value) >> 56; + p[7] = (uint8_t)(value); + p[6] = (uint8_t)(value >> 8); + p[5] = (uint8_t)(value >> 16); + p[4] = (uint8_t)(value >> 24); + p[3] = (uint8_t)(value >> 32); + p[2] = (uint8_t)(value >> 40); + p[1] = (uint8_t)(value >> 48); + p[0] = (uint8_t)(value >> 56); } static inline uint32_t GET_32BIT_MSB_FIRST(const void *vp) @@ -340,10 +363,10 @@ static inline uint32_t GET_32BIT_MSB_FIRST(const void *vp) static inline void PUT_32BIT_MSB_FIRST(void *vp, uint32_t value) { uint8_t *p = (uint8_t *)vp; - p[3] = value; - p[2] = (value) >> 8; - p[1] = (value) >> 16; - p[0] = (value) >> 24; + p[3] = (uint8_t)(value); + p[2] = (uint8_t)(value >> 8); + p[1] = (uint8_t)(value >> 16); + p[0] = (uint8_t)(value >> 24); } static inline uint16_t GET_16BIT_MSB_FIRST(const void *vp) @@ -355,8 +378,8 @@ static inline uint16_t GET_16BIT_MSB_FIRST(const void *vp) static inline void PUT_16BIT_MSB_FIRST(void *vp, uint16_t value) { uint8_t *p = (uint8_t *)vp; - p[1] = value; - p[0] = (value) >> 8; + p[1] = (uint8_t)(value); + p[0] = (uint8_t)(value >> 8); } /* Replace NULL with the empty string, permitting an idiom in which we diff --git a/missing b/missing new file mode 100644 index 0000000..f62bbae --- /dev/null +++ b/missing @@ -0,0 +1,215 @@ +#! /bin/sh +# Common wrapper for a few potentially missing GNU programs. + +scriptversion=2013-10-28.13; # UTC + +# Copyright (C) 1996-2014 Free Software Foundation, Inc. +# Originally written by Fran,cois Pinard , 1996. + +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2, or (at your option) +# any later version. + +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. + +# You should have received a copy of the GNU General Public License +# along with this program. If not, see . + +# As a special exception to the GNU General Public License, if you +# distribute this file as part of a program that contains a +# configuration script generated by Autoconf, you may include it under +# the same distribution terms that you use for the rest of that program. + +if test $# -eq 0; then + echo 1>&2 "Try '$0 --help' for more information" + exit 1 +fi + +case $1 in + + --is-lightweight) + # Used by our autoconf macros to check whether the available missing + # script is modern enough. + exit 0 + ;; + + --run) + # Back-compat with the calling convention used by older automake. + shift + ;; + + -h|--h|--he|--hel|--help) + echo "\ +$0 [OPTION]... PROGRAM [ARGUMENT]... + +Run 'PROGRAM [ARGUMENT]...', returning a proper advice when this fails due +to PROGRAM being missing or too old. + +Options: + -h, --help display this help and exit + -v, --version output version information and exit + +Supported PROGRAM values: + aclocal autoconf autoheader autom4te automake makeinfo + bison yacc flex lex help2man + +Version suffixes to PROGRAM as well as the prefixes 'gnu-', 'gnu', and +'g' are ignored when checking the name. + +Send bug reports to ." + exit $? + ;; + + -v|--v|--ve|--ver|--vers|--versi|--versio|--version) + echo "missing $scriptversion (GNU Automake)" + exit $? + ;; + + -*) + echo 1>&2 "$0: unknown '$1' option" + echo 1>&2 "Try '$0 --help' for more information" + exit 1 + ;; + +esac + +# Run the given program, remember its exit status. +"$@"; st=$? + +# If it succeeded, we are done. +test $st -eq 0 && exit 0 + +# Also exit now if we it failed (or wasn't found), and '--version' was +# passed; such an option is passed most likely to detect whether the +# program is present and works. +case $2 in --version|--help) exit $st;; esac + +# Exit code 63 means version mismatch. This often happens when the user +# tries to use an ancient version of a tool on a file that requires a +# minimum version. +if test $st -eq 63; then + msg="probably too old" +elif test $st -eq 127; then + # Program was missing. + msg="missing on your system" +else + # Program was found and executed, but failed. Give up. + exit $st +fi + +perl_URL=http://www.perl.org/ +flex_URL=http://flex.sourceforge.net/ +gnu_software_URL=http://www.gnu.org/software + +program_details () +{ + case $1 in + aclocal|automake) + echo "The '$1' program is part of the GNU Automake package:" + echo "<$gnu_software_URL/automake>" + echo "It also requires GNU Autoconf, GNU m4 and Perl in order to run:" + echo "<$gnu_software_URL/autoconf>" + echo "<$gnu_software_URL/m4/>" + echo "<$perl_URL>" + ;; + autoconf|autom4te|autoheader) + echo "The '$1' program is part of the GNU Autoconf package:" + echo "<$gnu_software_URL/autoconf/>" + echo "It also requires GNU m4 and Perl in order to run:" + echo "<$gnu_software_URL/m4/>" + echo "<$perl_URL>" + ;; + esac +} + +give_advice () +{ + # Normalize program name to check for. + normalized_program=`echo "$1" | sed ' + s/^gnu-//; t + s/^gnu//; t + s/^g//; t'` + + printf '%s\n' "'$1' is $msg." + + configure_deps="'configure.ac' or m4 files included by 'configure.ac'" + case $normalized_program in + autoconf*) + echo "You should only need it if you modified 'configure.ac'," + echo "or m4 files included by it." + program_details 'autoconf' + ;; + autoheader*) + echo "You should only need it if you modified 'acconfig.h' or" + echo "$configure_deps." + program_details 'autoheader' + ;; + automake*) + echo "You should only need it if you modified 'Makefile.am' or" + echo "$configure_deps." + program_details 'automake' + ;; + aclocal*) + echo "You should only need it if you modified 'acinclude.m4' or" + echo "$configure_deps." + program_details 'aclocal' + ;; + autom4te*) + echo "You might have modified some maintainer files that require" + echo "the 'autom4te' program to be rebuilt." + program_details 'autom4te' + ;; + bison*|yacc*) + echo "You should only need it if you modified a '.y' file." + echo "You may want to install the GNU Bison package:" + echo "<$gnu_software_URL/bison/>" + ;; + lex*|flex*) + echo "You should only need it if you modified a '.l' file." + echo "You may want to install the Fast Lexical Analyzer package:" + echo "<$flex_URL>" + ;; + help2man*) + echo "You should only need it if you modified a dependency" \ + "of a man page." + echo "You may want to install the GNU Help2man package:" + echo "<$gnu_software_URL/help2man/>" + ;; + makeinfo*) + echo "You should only need it if you modified a '.texi' file, or" + echo "any other file indirectly affecting the aspect of the manual." + echo "You might want to install the Texinfo package:" + echo "<$gnu_software_URL/texinfo/>" + echo "The spurious makeinfo call might also be the consequence of" + echo "using a buggy 'make' (AIX, DU, IRIX), in which case you might" + echo "want to install GNU make:" + echo "<$gnu_software_URL/make/>" + ;; + *) + echo "You might have modified some files without having the proper" + echo "tools for further handling them. Check the 'README' file, it" + echo "often tells you about the needed prerequisites for installing" + echo "this package. You may also peek at any GNU archive site, in" + echo "case some other package contains this missing '$1' program." + ;; + esac +} + +give_advice "$1" | sed -e '1s/^/WARNING: /' \ + -e '2,$s/^/ /' >&2 + +# Propagate the correct exit status (expected to be 127 for a program +# not found, 63 for a program that failed due to version mismatch). +exit $st + +# Local variables: +# eval: (add-hook 'write-file-hooks 'time-stamp) +# time-stamp-start: "scriptversion=" +# time-stamp-format: "%:y-%02m-%02d.%02H" +# time-stamp-time-zone: "UTC" +# time-stamp-end: "; # UTC" +# End: diff --git a/mkfiles.pl b/mkfiles.pl index 42690cf..0b378f6 100755 --- a/mkfiles.pl +++ b/mkfiles.pl @@ -601,7 +601,7 @@ sub manpages { print &def($makefile_extra{'clangcl'}->{'end'}); print "\nclean:\n". &splitline("\trm -f \$(BUILDDIR)*.obj \$(BUILDDIR)*.exe ". - "\$(BUILDDIR)*.res \$(BUILDDIR)*.map ". + "\$(BUILDDIR)*.rcpp \$(BUILDDIR)*.res \$(BUILDDIR)*.map ". "\$(BUILDDIR)*.exe.manifest")."\n"; select STDOUT; close OUT; } diff --git a/mksrcarc.sh b/mksrcarc.sh new file mode 100644 index 0000000..9b53317 --- /dev/null +++ b/mksrcarc.sh @@ -0,0 +1,33 @@ +#!/bin/sh + +set -e + +perl mkfiles.pl +# These are text files. +text=`{ find . -name CVS -prune -o \ + -name .cvsignore -prune -o \ + -name .svn -prune -o \ + -name LATEST.VER -prune -o \ + -name CHECKLST.txt -prune -o \ + -name mksrcarc.sh -prune -o \ + -name '*.dsp' -prune -o \ + -name '*.dsw' -prune -o \ + -type f -print | sed 's/^\.\///'; } | \ + grep -ivE 'test/.*\.txt|MODULE|website.url' | grep -vF .ico | grep -vF .icns` +# These are files which I'm _sure_ should be treated as text, but +# which zip might complain about, so we direct its moans to +# /dev/null! Apparently its heuristics are doubtful of UTF-8 text +# files. +bintext=test/*.txt +# These are actual binary files which we don't want transforming. +bin=`{ ls -1 windows/*.ico windows/website.url; \ + find . -name '*.dsp' -print -o -name '*.dsw' -print; }` + +verbosely() { + echo "$@" + "$@" +} + +verbosely zip -l putty-src.zip $text +verbosely zip -l putty-src.zip $bintext +verbosely zip putty-src.zip $bin diff --git a/network.h b/network.h index 84287e7..689b4c5 100644 --- a/network.h +++ b/network.h @@ -163,14 +163,14 @@ static inline void sk_flush(Socket *s) static inline void plug_log( Plug *p, int type, SockAddr *addr, int port, const char *msg, int code) -{ return p->vt->log(p, type, addr, port, msg, code); } +{ p->vt->log(p, type, addr, port, msg, code); } static inline void plug_closing( Plug *p, const char *msg, int code, bool calling_back) -{ return p->vt->closing(p, msg, code, calling_back); } +{ p->vt->closing(p, msg, code, calling_back); } static inline void plug_receive(Plug *p, int urg, const char *data, size_t len) -{ return p->vt->receive(p, urg, data, len); } +{ p->vt->receive(p, urg, data, len); } static inline void plug_sent (Plug *p, size_t bufsize) -{ return p->vt->sent(p, bufsize); } +{ p->vt->sent(p, bufsize); } static inline int plug_accepting(Plug *p, accept_fn_t cons, accept_ctx_t ctx) { return p->vt->accepting(p, cons, ctx); } diff --git a/packager/build.cmd b/packager/build.cmd index dc3c1e9..a0b442f 100644 --- a/packager/build.cmd +++ b/packager/build.cmd @@ -1,11 +1,11 @@ @ECHO OFF :: version information -SET VER=0.71 -SET VERN=0.71.0.0 +SET VER=0.72 +SET VERN=0.72.0.0 :: cert info to use for signing -SET CERT=2FA35B20356EFEB88F9E9B5F20221693C57100E5 +SET CERT=D4C06C609230B7BC433A428BFFD6EDC4F77FD166 set TSAURL=http://time.certum.pl/ set LIBNAME=PuTTY-CAC set LIBURL=https://github.com/NoMoreFood/putty-cac diff --git a/pageant.c b/pageant.c index f95a1b7..042b8fd 100644 --- a/pageant.c +++ b/pageant.c @@ -134,7 +134,7 @@ void pageant_make_keylist2(BinarySink *bs) static void plog(void *logctx, pageant_logfn_t logfn, const char *fmt, ...) #ifdef __GNUC__ -__attribute__ ((format (printf, 3, 4))) +__attribute__ ((format (PUTTY_PRINTF_ARCHETYPE, 3, 4))) #endif ; @@ -960,7 +960,7 @@ void pageant_forget_passphrases(void) char *pp = index234(passphrases, 0); smemclr(pp, strlen(pp)); delpos234(passphrases, 0); - free(pp); + sfree(pp); } } @@ -1237,6 +1237,8 @@ int pageant_add_keyfile(Filename *filename, const char *passphrase, */ *retstr = dupstr(error); sfree(rkey); + if (comment) + sfree(comment); return PAGEANT_ACTION_FAILURE; } else if (ret == 1) { /* @@ -1333,6 +1335,8 @@ int pageant_add_keyfile(Filename *filename, const char *passphrase, return PAGEANT_ACTION_FAILURE; } + ssh_key_free(skey->key); + sfree(skey); sfree(response); } else { if (!pageant_add_ssh2_key(skey)) { diff --git a/portfwd.c b/portfwd.c index 6fd3d40..49a8d50 100644 --- a/portfwd.c +++ b/portfwd.c @@ -959,8 +959,10 @@ void portfwdmgr_config(PortFwdManager *mgr, Conf *conf) * rejected. */ ssh_rportfwd_remove(mgr->cl, pfr->remote); + pfr->remote = NULL; } else if (pfr->local) { pfl_terminate(pfr->local); + pfr->local = NULL; } delpos234(mgr->forwardings, i); diff --git a/pscp.c b/pscp.c index 29b3e12..f39d2d0 100644 --- a/pscp.c +++ b/pscp.c @@ -599,21 +599,24 @@ size_t sftp_sendbuffer(void) /* ---------------------------------------------------------------------- * sftp-based replacement for the hacky `pscp -ls'. */ -static int sftp_ls_compare(const void *av, const void *bv) +void list_directory_from_sftp_warn_unsorted(void) { - const struct fxp_name *a = (const struct fxp_name *) av; - const struct fxp_name *b = (const struct fxp_name *) bv; - return strcmp(a->filename, b->filename); + fprintf(stderr, + "Directory is too large to sort; writing file names unsorted\n"); } + +void list_directory_from_sftp_print(struct fxp_name *name) +{ + with_stripctrl(san, name->longname) + printf("%s\n", san); +} + void scp_sftp_listdir(const char *dirname) { struct fxp_handle *dirh; struct fxp_names *names; - struct fxp_name *ournames; struct sftp_packet *pktin; struct sftp_request *req; - size_t nnames, namesize; - int i; if (!fxp_init()) { tell_user(stderr, "unable to initialise SFTP: %s", fxp_error()); @@ -631,8 +634,8 @@ void scp_sftp_listdir(const char *dirname) tell_user(stderr, "Unable to open %s: %s\n", dirname, fxp_error()); errs++; } else { - nnames = namesize = 0; - ournames = NULL; + struct list_directory_from_sftp_ctx *ctx = + list_directory_from_sftp_new(); while (1) { @@ -651,33 +654,17 @@ void scp_sftp_listdir(const char *dirname) break; } - sgrowarrayn(ournames, namesize, nnames, names->nnames); + for (size_t i = 0; i < names->nnames; i++) + list_directory_from_sftp_feed(ctx, &names->names[i]); - for (i = 0; i < names->nnames; i++) - ournames[nnames++] = names->names[i]; - names->nnames = 0; /* prevent free_names */ fxp_free_names(names); } req = fxp_close_send(dirh); pktin = sftp_wait_for_reply(req); fxp_close_recv(pktin, req); - /* - * Now we have our filenames. Sort them by actual file - * name, and then output the longname parts. - */ - if (nnames > 0) - qsort(ournames, nnames, sizeof(*ournames), sftp_ls_compare); - - /* - * And print them. - */ - for (i = 0; i < nnames; i++) { - with_stripctrl(san, ournames[i].longname) - printf("%s\n", san); - } - - sfree(ournames); + list_directory_from_sftp_finish(ctx); + list_directory_from_sftp_free(ctx); } } @@ -1380,11 +1367,13 @@ int scp_get_sink_action(struct scp_sink_action *act) if (ch == '\n') bump("Protocol error: Unexpected newline"); action = ch; - do { + while (1) { if (!ssh_scp_recv(&ch, 1)) bump("Lost connection"); + if (ch == '\n') + break; put_byte(act->buf, ch); - } while (ch != '\n'); + } switch (action) { case '\01': /* error */ with_stripctrl(san, act->buf->s) @@ -1403,6 +1392,7 @@ int scp_get_sink_action(struct scp_sink_action *act) &act->mtime, &act->atime) == 2) { act->settime = true; backend_send(backend, "", 1); + act->buf->len = 0; continue; /* go round again */ } bump("Protocol error: Illegal time format"); @@ -1826,7 +1816,7 @@ static void sink(const char *targ, const char *src) !using_sftp && !scp_unsafe_mode) { with_stripctrl(san, striptarget) tell_user(stderr, "warning: remote host tried to " - "write to a file called '%s'", san); + "write to a file called '%s'", san); tell_user(stderr, " when we requested a file " "called '%s'.", stripsrc); tell_user(stderr, " If this is a wildcard, " @@ -2351,8 +2341,10 @@ int psftp_main(int argc, char *argv[]) random_save_seed(); cmdline_cleanup(); - backend_free(backend); - backend = NULL; + if (backend) { + backend_free(backend); + backend = NULL; + } sk_cleanup(); return (errs == 0 ? 0 : 1); } diff --git a/psftp.c b/psftp.c index 2483068..6215eba 100644 --- a/psftp.c +++ b/psftp.c @@ -33,6 +33,7 @@ static void do_sftp_cleanup(void); */ char *pwd, *homedir; +static LogContext *psftp_logctx = NULL; static Backend *backend; Conf *conf; bool sent_eof = false; @@ -210,20 +211,6 @@ char *canonify(const char *name) } } -/* - * qsort comparison routine for fxp_name structures. Sorts by real - * file name. - */ -static int sftp_name_compare(const void *av, const void *bv) -{ - const struct fxp_name *const *a = (const struct fxp_name *const *) av; - const struct fxp_name *const *b = (const struct fxp_name *const *) bv; - return strcmp((*a)->filename, (*b)->filename); -} - -/* - * Likewise, but for a bare char *. - */ static int bare_name_compare(const void *av, const void *bv) { const char **a = (const char **) av; @@ -1023,6 +1010,17 @@ int sftp_cmd_close(struct sftp_command *cmd) return 0; } +void list_directory_from_sftp_warn_unsorted(void) +{ + printf("Directory is too large to sort; writing file names unsorted\n"); +} + +void list_directory_from_sftp_print(struct fxp_name *name) +{ + with_stripctrl(san, name->longname) + printf("%s\n", san); +} + /* * List a directory. If no arguments are given, list pwd; otherwise * list the directory given in words[1]. @@ -1031,8 +1029,6 @@ int sftp_cmd_ls(struct sftp_command *cmd) { struct fxp_handle *dirh; struct fxp_names *names; - struct fxp_name **ournames; - size_t nnames, namesize; const char *dir; char *cdir, *unwcdir, *wildcard; struct sftp_packet *pktin; @@ -1090,8 +1086,8 @@ int sftp_cmd_ls(struct sftp_command *cmd) sfree(unwcdir); return 0; } else { - nnames = namesize = 0; - ournames = NULL; + struct list_directory_from_sftp_ctx *ctx = + list_directory_from_sftp_new(); while (1) { @@ -1110,34 +1106,19 @@ int sftp_cmd_ls(struct sftp_command *cmd) break; } - sgrowarrayn(ournames, namesize, nnames, names->nnames); - for (size_t i = 0; i < names->nnames; i++) if (!wildcard || wc_match(wildcard, names->names[i].filename)) - ournames[nnames++] = fxp_dup_name(&names->names[i]); + list_directory_from_sftp_feed(ctx, &names->names[i]); fxp_free_names(names); } + req = fxp_close_send(dirh); pktin = sftp_wait_for_reply(req); fxp_close_recv(pktin, req); - /* - * Now we have our filenames. Sort them by actual file - * name, and then output the longname parts. - */ - if (nnames > 0) - qsort(ournames, nnames, sizeof(*ournames), sftp_name_compare); - - /* - * And print them. - */ - for (size_t i = 0; i < nnames; i++) { - with_stripctrl(san, ournames[i]->longname) - printf("%s\n", san); - fxp_free_name(ournames[i]); - } - sfree(ournames); + list_directory_from_sftp_finish(ctx); + list_directory_from_sftp_free(ctx); } sfree(cdir); @@ -2576,7 +2557,6 @@ static int psftp_connect(char *userhost, char *user, int portnumber) { char *host, *realhost; const char *err; - LogContext *logctx; /* Separate host and username */ host = userhost; @@ -2733,11 +2713,11 @@ static int psftp_connect(char *userhost, char *user, int portnumber) "exec sftp-server"); conf_set_bool(conf, CONF_ssh_subsys2, false); - logctx = log_init(default_logpolicy, conf); + psftp_logctx = log_init(default_logpolicy, conf); platform_psftp_pre_conn_setup(); - err = backend_init(&ssh_backend, psftp_seat, &backend, logctx, conf, + err = backend_init(&ssh_backend, psftp_seat, &backend, psftp_logctx, conf, conf_get_str(conf, CONF_host), conf_get_int(conf, CONF_port), &realhost, 0, @@ -2906,5 +2886,11 @@ int psftp_main(int argc, char *argv[]) cmdline_cleanup(); sk_cleanup(); + stripctrl_free(string_scc); + stripctrl_free(stderr_scc); + + if (psftp_logctx) + log_free(psftp_logctx); + return ret; } diff --git a/psftp.h b/psftp.h index c9f2d65..db9f5b7 100644 --- a/psftp.h +++ b/psftp.h @@ -1,6 +1,6 @@ /* - * psftp.h: interface between psftp.c / scp.c and each - * platform-specific SFTP module. + * psftp.h: interface between psftp.c / pscp.c, psftpcommon.c, and + * each platform-specific SFTP module. */ #ifndef PUTTY_PSFTP_H @@ -198,4 +198,30 @@ char *dir_file_cat(const char *dir, const char *file); */ char *stripslashes(const char *str, bool local); +/* ---------------------------------------------------------------------- + * In psftpcommon.c + */ + +/* + * qsort comparison routine for fxp_name structures. Sorts by real + * file name. + */ +int sftp_name_compare(const void *av, const void *bv); + +/* + * Shared code for outputting a directory listing in response to a + * stream of name structures from FXP_READDIR operations. Used by + * psftp's ls command and pscp -ls. + */ +struct list_directory_from_sftp_ctx; +struct fxp_name; /* in sftp.h */ +struct list_directory_from_sftp_ctx *list_directory_from_sftp_new(void); +void list_directory_from_sftp_feed(struct list_directory_from_sftp_ctx *ctx, + struct fxp_name *name); +void list_directory_from_sftp_finish(struct list_directory_from_sftp_ctx *ctx); +void list_directory_from_sftp_free(struct list_directory_from_sftp_ctx *ctx); +/* Callbacks provided by the tool front end */ +void list_directory_from_sftp_warn_unsorted(void); +void list_directory_from_sftp_print(struct fxp_name *name); + #endif /* PUTTY_PSFTP_H */ diff --git a/psftpcommon.c b/psftpcommon.c new file mode 100644 index 0000000..21f3737 --- /dev/null +++ b/psftpcommon.c @@ -0,0 +1,102 @@ +/* + * psftpcommon.c: front-end functionality shared between both file + * transfer tools across platforms. (As opposed to sftpcommon.c, which + * has *protocol*-level common code.) + */ + +#include +#include + +#include "putty.h" +#include "sftp.h" +#include "psftp.h" + +#define MAX_NAMES_MEMORY ((size_t)8 << 20) + +/* + * qsort comparison routine for fxp_name structures. Sorts by real + * file name. + */ +int sftp_name_compare(const void *av, const void *bv) +{ + const struct fxp_name *const *a = (const struct fxp_name *const *) av; + const struct fxp_name *const *b = (const struct fxp_name *const *) bv; + return strcmp((*a)->filename, (*b)->filename); +} + +struct list_directory_from_sftp_ctx { + size_t nnames, namesize, total_memory; + struct fxp_name **names; + bool sorting; +}; + +struct list_directory_from_sftp_ctx *list_directory_from_sftp_new(void) +{ + struct list_directory_from_sftp_ctx *ctx = + snew(struct list_directory_from_sftp_ctx); + memset(ctx, 0, sizeof(*ctx)); + ctx->sorting = true; + return ctx; +} + +void list_directory_from_sftp_free(struct list_directory_from_sftp_ctx *ctx) +{ + for (size_t i = 0; i < ctx->nnames; i++) + fxp_free_name(ctx->names[i]); + sfree(ctx->names); + sfree(ctx); +} + +void list_directory_from_sftp_feed(struct list_directory_from_sftp_ctx *ctx, + struct fxp_name *name) +{ + if (ctx->sorting) { + /* + * Accumulate these filenames into an array that we'll sort - + * unless the array gets _really_ big, in which case, to avoid + * consuming all the client's memory, we fall back to + * outputting the directory listing unsorted. + */ + size_t this_name_memory = + sizeof(*ctx->names) + sizeof(**ctx->names) + + strlen(name->filename) + + strlen(name->longname); + + if (MAX_NAMES_MEMORY - ctx->total_memory < this_name_memory) { + list_directory_from_sftp_warn_unsorted(); + + /* Output all the previously stored names. */ + for (size_t i = 0; i < ctx->nnames; i++) { + list_directory_from_sftp_print(ctx->names[i]); + fxp_free_name(ctx->names[i]); + } + + /* Don't store further names in that array. */ + sfree(ctx->names); + ctx->names = NULL; + ctx->nnames = 0; + ctx->namesize = 0; + ctx->sorting = false; + + /* And don't forget to output the name passed in this + * actual function call. */ + list_directory_from_sftp_print(name); + } else { + sgrowarray(ctx->names, ctx->namesize, ctx->nnames); + ctx->names[ctx->nnames++] = fxp_dup_name(name); + ctx->total_memory += this_name_memory; + } + } else { + list_directory_from_sftp_print(name); + } +} + +void list_directory_from_sftp_finish(struct list_directory_from_sftp_ctx *ctx) +{ + if (ctx->nnames > 0) { + assert(ctx->sorting); + qsort(ctx->names, ctx->nnames, sizeof(*ctx->names), sftp_name_compare); + for (size_t i = 0; i < ctx->nnames; i++) + list_directory_from_sftp_print(ctx->names[i]); + } +} diff --git a/putty.h b/putty.h index 6306fed..c6092b8 100644 --- a/putty.h +++ b/putty.h @@ -1397,8 +1397,8 @@ NORETURN void cleanup_exit(int); X(INT, NONE, window_border) /* in pixels */ \ X(STR, NONE, answerback) \ X(STR, NONE, printer) \ - X(BOOL, NONE, arabicshaping) \ - X(BOOL, NONE, bidi) \ + X(BOOL, NONE, no_arabicshaping) \ + X(BOOL, NONE, no_bidi) \ /* Colour options */ \ X(BOOL, NONE, ansi_colour) \ X(BOOL, NONE, xterm_256_colour) \ @@ -1537,10 +1537,6 @@ bool conf_deserialise(Conf *conf, BinarySource *src);/*returns true on success*/ * Functions to copy, free, serialise and deserialise FontSpecs. * Provided per-platform, to go with the platform's idea of a * FontSpec's contents. - * - * fontspec_serialise returns the number of bytes written, and can - * handle data==NULL without crashing. So you can call it once to find - * out a size, then again once you've allocated a buffer. */ FontSpec *fontspec_copy(const FontSpec *f); void fontspec_free(FontSpec *f); @@ -1638,7 +1634,6 @@ void term_invalidate(Terminal *); void term_blink(Terminal *, bool set_cursor); void term_do_paste(Terminal *, const wchar_t *, int); void term_nopaste(Terminal *); -bool term_ldisc(Terminal *, int option); void term_copyall(Terminal *, const int *, int); void term_reconfig(Terminal *, Conf *); void term_request_copy(Terminal *, const int *clipboards, int n_clipboards); @@ -1651,6 +1646,8 @@ void term_set_focus(Terminal *term, bool has_focus); char *term_get_ttymode(Terminal *term, const char *mode); int term_get_userpass_input(Terminal *term, prompts_t *p, bufchain *input); void term_set_trust_status(Terminal *term, bool trusted); +void term_keyinput(Terminal *, int codepage, const void *buf, int len); +void term_keyinputw(Terminal *, const wchar_t * widebuf, int len); typedef enum SmallKeypadKey { SKK_HOME, SKK_END, SKK_INSERT, SKK_DELETE, SKK_PGUP, SKK_PGDN, @@ -1787,13 +1784,6 @@ void ldisc_free(Ldisc *); void ldisc_send(Ldisc *, const void *buf, int len, bool interactive); void ldisc_echoedit_update(Ldisc *); -/* - * Exports from ldiscucs.c. - */ -void lpage_send(Ldisc *, int codepage, const char *buf, int len, - bool interactive); -void luni_send(Ldisc *, const wchar_t * widebuf, int len, bool interactive); - /* * Exports from sshrand.c. */ @@ -1807,6 +1797,13 @@ extern int random_active; * calls random_ref on startup and random_unref on shutdown. */ void random_ref(void); void random_unref(void); +/* random_clear is equivalent to calling random_unref as many times as + * necessary to shut down the global PRNG instance completely. It's + * not needed in normal applications, but the command-line PuTTYgen + * test finds it useful to clean up after each invocation of the + * logical main() no matter whether it needed random numbers or + * not. */ +void random_clear(void); /* random_setup_special is used by PuTTYgen. It makes an extra-big * random number generator. */ void random_setup_special(); diff --git a/puttymem.h b/puttymem.h index 85184a1..ac1bd68 100644 --- a/puttymem.h +++ b/puttymem.h @@ -10,13 +10,13 @@ #include "defs.h" -#define smalloc(z) safemalloc(z,1) +#define smalloc(z) safemalloc(z,1,0) #define snmalloc safemalloc #define srealloc(y,z) saferealloc(y,z,1) #define snrealloc saferealloc #define sfree safefree -void *safemalloc(size_t, size_t); +void *safemalloc(size_t factor1, size_t factor2, size_t addend); void *saferealloc(void *, size_t, size_t); void safefree(void *); @@ -28,8 +28,8 @@ void safefree(void *); * TYPECHECK to verify that the _input_ pointer is a pointer to the * correct type. */ -#define snew(type) ((type *)snmalloc(1, sizeof(type))) -#define snewn(n, type) ((type *)snmalloc((n), sizeof(type))) +#define snew(type) ((type *)snmalloc(1, sizeof(type), 0)) +#define snewn(n, type) ((type *)snmalloc((n), sizeof(type), 0)) #define sresize(ptr, n, type) TYPECHECK((type *)0 == (ptr), \ ((type *)snrealloc((ptr), (n), sizeof(type)))) @@ -45,7 +45,7 @@ void safefree(void *); * result to void *, so you can assign it straight to wherever you * wanted it. */ -#define snew_plus(type, extra) ((type *)snmalloc(1, sizeof(type) + (extra))) +#define snew_plus(type, extra) ((type *)snmalloc(1, sizeof(type), (extra))) #define snew_plus_get_aux(ptr) ((void *)((ptr) + 1)) /* diff --git a/release.pl b/release.pl index b5ad149..e27db47 100644 --- a/release.pl +++ b/release.pl @@ -45,8 +45,6 @@ $plink_transcript =~ s/^Unidentified build/Release ${version}/m or die; $plink_transcript =~ s/^/\\c /mg; &transform("LATEST.VER", sub { s/^\d+\.\d+$/$version/ }); - &transform("windows/putty.iss", sub { - s/^(AppVerName=PuTTY version |VersionInfoTextVersion=Release |AppVersion=|VersionInfoVersion=)\d+\.\d+/$1$version/ }); our $transforming = 0; &transform("doc/pscp.but", sub { if (/^\\c.*>pscp$/) { $transforming = 1; $_ .= $pscp_transcript; } @@ -100,7 +98,7 @@ } } elsif (m!^putty/(.*sum)s!) { print $pipe "echo checking ${1}s\n"; - print $pipe "$1 -c ${1}s\n"; + print $pipe "grep -vF ' (installer version)' ${1}s | grep . | $1 -c\n"; } }, no_chdir => 1}, "putty"); print $pipe "echo all verified ok\n"; diff --git a/rlogin.c b/rlogin.c index 1702f15..7a8a3ba 100644 --- a/rlogin.c +++ b/rlogin.c @@ -221,6 +221,8 @@ static const char *rlogin_init(Seat *seat, Backend **backend_handle, * anything else until the local prompt mechanism returns. */ if ((ruser = get_remote_username(conf)) != NULL) { + /* Next terminal output will come from server */ + seat_set_trust_status(rlogin->seat, false); rlogin_startup(rlogin, ruser); sfree(ruser); } else { @@ -233,6 +235,8 @@ static const char *rlogin_init(Seat *seat, Backend **backend_handle, add_prompt(rlogin->prompt, dupstr("rlogin username: "), true); ret = seat_get_userpass_input(rlogin->seat, rlogin->prompt, NULL); if (ret >= 0) { + /* Next terminal output will come from server */ + seat_set_trust_status(rlogin->seat, false); rlogin_startup(rlogin, rlogin->prompt->prompts[0]->result); } } @@ -280,6 +284,8 @@ static size_t rlogin_send(Backend *be, const char *buf, size_t len) */ int ret = seat_get_userpass_input(rlogin->seat, rlogin->prompt, &bc); if (ret >= 0) { + /* Next terminal output will come from server */ + seat_set_trust_status(rlogin->seat, false); rlogin_startup(rlogin, rlogin->prompt->prompts[0]->result); /* that nulls out rlogin->prompt, so then we'll start sending * data down the wire in the obvious way */ diff --git a/scpserver.c b/scpserver.c index 794d614..da04782 100644 --- a/scpserver.c +++ b/scpserver.c @@ -521,6 +521,9 @@ static void scp_source_free(ScpServer *s) scp->head = node->next; sfree(node); } + + delete_callbacks_for_context(scp); + sfree(scp); } diff --git a/sesschan.c b/sesschan.c index 6725a64..ecb34f4 100644 --- a/sesschan.c +++ b/sesschan.c @@ -43,6 +43,7 @@ typedef struct sesschan { bufchain subsys_input; SftpServer *sftpsrv; ScpServer *scpsrv; + const SshServerConfig *ssc; Channel chan; } sesschan; @@ -198,7 +199,8 @@ static const SeatVtable sesschan_seat_vt = { }; Channel *sesschan_new(SshChannel *c, LogContext *logctx, - const SftpServerVtable *sftpserver_vt) + const SftpServerVtable *sftpserver_vt, + const SshServerConfig *ssc) { sesschan *sess = snew(sesschan); memset(sess, 0, sizeof(sesschan)); @@ -207,6 +209,7 @@ Channel *sesschan_new(SshChannel *c, LogContext *logctx, sess->chan.vt = &sesschan_channelvt; sess->chan.initial_fixed_window_size = 0; sess->parent_logctx = logctx; + sess->ssc = ssc; /* Start with a completely default Conf */ sess->conf = conf_new(); @@ -277,9 +280,25 @@ static void sesschan_set_input_wanted(Channel *chan, bool wanted) static void sesschan_start_backend(sesschan *sess, const char *cmd) { + /* + * List of environment variables that we should not pass through + * from the login session Uppity was run in (which, it being a + * test server, there will usually be one of). These variables + * will be set as part of X or agent forwarding, and shouldn't be + * confusingly set in the absence of that. + * + * (DISPLAY must also be cleared, but uxpty.c will do that anyway + * when our get_x_display method returns NULL.) + */ + static const char *const env_to_unset[] = { + "XAUTHORITY", "SSH_AUTH_SOCK", "SSH_AGENT_PID", + NULL /* terminator */ + }; + sess->backend = pty_backend_create( &sess->seat, sess->child_logctx, sess->conf, NULL, cmd, - sess->ttymodes, !sess->want_pty); + sess->ttymodes, !sess->want_pty, sess->ssc->session_starting_dir, + env_to_unset); backend_size(sess->backend, sess->wc, sess->hc); } @@ -605,25 +624,39 @@ static bool sesschan_seat_eof(Seat *seat) static void sesschan_notify_remote_exit(Seat *seat) { sesschan *sess = container_of(seat, sesschan, seat); - ptrlen signame; - char *sigmsg; if (!sess->backend) return; - signame = pty_backend_exit_signame(sess->backend, &sigmsg); - if (signame.len) { - if (!sigmsg) - sigmsg = dupstr(""); + bool got_signal = false; + if (!sess->ssc->exit_signal_numeric) { + char *sigmsg; + ptrlen signame = pty_backend_exit_signame(sess->backend, &sigmsg); - sshfwd_send_exit_signal( - sess->c, signame, false, ptrlen_from_asciz(sigmsg)); + if (signame.len) { + if (!sigmsg) + sigmsg = dupstr(""); - sfree(sigmsg); + sshfwd_send_exit_signal( + sess->c, signame, false, ptrlen_from_asciz(sigmsg)); + + sfree(sigmsg); + + got_signal = true; + } } else { - sshfwd_send_exit_status(sess->c, backend_exitcode(sess->backend)); + int signum = pty_backend_exit_signum(sess->backend); + + if (signum >= 0) { + sshfwd_send_exit_signal_numeric(sess->c, signum, false, + PTRLEN_LITERAL("")); + got_signal = true; + } } + if (!got_signal) + sshfwd_send_exit_status(sess->c, backend_exitcode(sess->backend)); + sess->seen_exit = true; queue_toplevel_callback(sesschan_check_close_callback, sess); } diff --git a/sessprep.c b/sessprep.c index 15d830d..95e7b65 100644 --- a/sessprep.c +++ b/sessprep.c @@ -63,7 +63,7 @@ void prepare_session(Conf *conf) * _more_ than one (un-IPv6-bracketed) colon. */ p = host_strchr(host, ':'); - if (p && p != host_strrchr(host, ':')) { + if (p && p == host_strrchr(host, ':')) { *p = '\0'; } diff --git a/settings.c b/settings.c index 5ff9209..131e56c 100644 --- a/settings.c +++ b/settings.c @@ -110,7 +110,7 @@ char *get_remote_username(Conf *conf) static char *gpps_raw(settings_r *sesskey, const char *name, const char *def) { - char *ret = sesskey ? read_setting_s(sesskey, name) : NULL; + char *ret = read_setting_s(sesskey, name); if (!ret) ret = platform_default_s(name); if (!ret) @@ -134,7 +134,7 @@ static void gpps(settings_r *sesskey, const char *name, const char *def, static void gppfont(settings_r *sesskey, char *name, Conf *conf, int primary) { - FontSpec *result = sesskey ? read_setting_fontspec(sesskey, name) : NULL; + FontSpec *result = read_setting_fontspec(sesskey, name); if (!result) result = platform_default_fontspec(name); conf_set_fontspec(conf, primary, result); @@ -143,7 +143,7 @@ static void gppfont(settings_r *sesskey, char *name, static void gppfile(settings_r *sesskey, const char *name, Conf *conf, int primary) { - Filename *result = sesskey ? read_setting_filename(sesskey, name) : NULL; + Filename *result = read_setting_filename(sesskey, name); if (!result) result = platform_default_filename(name); conf_set_filename(conf, primary, result); @@ -165,7 +165,7 @@ static void gppb(settings_r *sesskey, const char *name, bool def, static int gppi_raw(settings_r *sesskey, const char *name, int def) { def = platform_default_i(name, def); - return sesskey ? read_setting_i(sesskey, name, def) : def; + return read_setting_i(sesskey, name, def); } static void gppi(settings_r *sesskey, const char *name, int def, @@ -595,21 +595,25 @@ void save_open_settings(settings_w *sesskey, Conf *conf) write_setting_b(sesskey, "Compression", conf_get_bool(conf, CONF_compression)); write_setting_b(sesskey, "TryAgent", conf_get_bool(conf, CONF_tryagent)); write_setting_b(sesskey, "AgentFwd", conf_get_bool(conf, CONF_agentfwd)); +#ifndef NO_GSSAPI write_setting_b(sesskey, "GssapiFwd", conf_get_bool(conf, CONF_gssapifwd)); +#endif write_setting_b(sesskey, "ChangeUsername", conf_get_bool(conf, CONF_change_username)); wprefs(sesskey, "Cipher", ciphernames, CIPHER_MAX, conf, CONF_ssh_cipherlist); wprefs(sesskey, "KEX", kexnames, KEX_MAX, conf, CONF_ssh_kexlist); wprefs(sesskey, "HostKey", hknames, HK_MAX, conf, CONF_ssh_hklist); write_setting_i(sesskey, "RekeyTime", conf_get_int(conf, CONF_ssh_rekey_time)); +#ifndef NO_GSSAPI write_setting_i(sesskey, "GssapiRekey", conf_get_int(conf, CONF_gssapirekey)); +#endif write_setting_s(sesskey, "RekeyBytes", conf_get_str(conf, CONF_ssh_rekey_data)); write_setting_b(sesskey, "SshNoAuth", conf_get_bool(conf, CONF_ssh_no_userauth)); write_setting_b(sesskey, "SshBanner", conf_get_bool(conf, CONF_ssh_show_banner)); write_setting_b(sesskey, "AuthTIS", conf_get_bool(conf, CONF_try_tis_auth)); write_setting_b(sesskey, "AuthKI", conf_get_bool(conf, CONF_try_ki_auth)); +#ifndef NO_GSSAPI write_setting_b(sesskey, "AuthGSSAPI", conf_get_bool(conf, CONF_try_gssapi_auth)); write_setting_b(sesskey, "AuthGSSAPIKEX", conf_get_bool(conf, CONF_try_gssapi_kex)); -#ifndef NO_GSSAPI wprefs(sesskey, "GSSLibs", gsslibkeywords, ngsslibs, conf, CONF_ssh_gsslist); write_setting_filename(sesskey, "GSSCustom", conf_get_filename(conf, CONF_ssh_gss_custom)); #endif @@ -682,8 +686,8 @@ void save_open_settings(settings_w *sesskey, Conf *conf) write_setting_b(sesskey, "AutoWrapMode", conf_get_bool(conf, CONF_wrap_mode)); write_setting_b(sesskey, "LFImpliesCR", conf_get_bool(conf, CONF_lfhascr)); write_setting_b(sesskey, "CRImpliesLF", conf_get_bool(conf, CONF_crhaslf)); - write_setting_b(sesskey, "DisableArabicShaping", conf_get_bool(conf, CONF_arabicshaping)); - write_setting_b(sesskey, "DisableBidi", conf_get_bool(conf, CONF_bidi)); + write_setting_b(sesskey, "DisableArabicShaping", conf_get_bool(conf, CONF_no_arabicshaping)); + write_setting_b(sesskey, "DisableBidi", conf_get_bool(conf, CONF_no_bidi)); write_setting_b(sesskey, "WinNameAlways", conf_get_bool(conf, CONF_win_name_always)); write_setting_s(sesskey, "WinTitle", conf_get_str(conf, CONF_wintitle)); write_setting_i(sesskey, "TermWidth", conf_get_int(conf, CONF_width)); @@ -944,7 +948,9 @@ void load_open_settings(settings_r *sesskey, Conf *conf) gppb(sesskey, "TryAgent", true, conf, CONF_tryagent); gppb(sesskey, "AgentFwd", false, conf, CONF_agentfwd); gppb(sesskey, "ChangeUsername", false, conf, CONF_change_username); +#ifndef NO_GSSAPI gppb(sesskey, "GssapiFwd", false, conf, CONF_gssapifwd); +#endif gprefs(sesskey, "Cipher", "\0", ciphernames, CIPHER_MAX, conf, CONF_ssh_cipherlist); { @@ -997,7 +1003,9 @@ void load_open_settings(settings_r *sesskey, Conf *conf) gprefs(sesskey, "HostKey", "ed25519,ecdsa,rsa,dsa,WARN", hknames, HK_MAX, conf, CONF_ssh_hklist); gppi(sesskey, "RekeyTime", 60, conf, CONF_ssh_rekey_time); +#ifndef NO_GSSAPI gppi(sesskey, "GssapiRekey", GSS_DEF_REKEY_MINS, conf, CONF_gssapirekey); +#endif gpps(sesskey, "RekeyBytes", "1G", conf, CONF_ssh_rekey_data); { /* SSH-2 only by default */ @@ -1014,9 +1022,9 @@ void load_open_settings(settings_r *sesskey, Conf *conf) gppb(sesskey, "SshBanner", true, conf, CONF_ssh_show_banner); gppb(sesskey, "AuthTIS", false, conf, CONF_try_tis_auth); gppb(sesskey, "AuthKI", true, conf, CONF_try_ki_auth); +#ifndef NO_GSSAPI gppb(sesskey, "AuthGSSAPI", true, conf, CONF_try_gssapi_auth); gppb(sesskey, "AuthGSSAPIKEX", true, conf, CONF_try_gssapi_kex); -#ifndef NO_GSSAPI gprefs(sesskey, "GSSLibs", "\0", gsslibkeywords, ngsslibs, conf, CONF_ssh_gsslist); gppfile(sesskey, "GSSCustom", conf, CONF_ssh_gss_custom); @@ -1114,8 +1122,8 @@ void load_open_settings(settings_r *sesskey, Conf *conf) gppb(sesskey, "AutoWrapMode", true, conf, CONF_wrap_mode); gppb(sesskey, "LFImpliesCR", false, conf, CONF_lfhascr); gppb(sesskey, "CRImpliesLF", false, conf, CONF_crhaslf); - gppb(sesskey, "DisableArabicShaping", false, conf, CONF_arabicshaping); - gppb(sesskey, "DisableBidi", false, conf, CONF_bidi); + gppb(sesskey, "DisableArabicShaping", false, conf, CONF_no_arabicshaping); + gppb(sesskey, "DisableBidi", false, conf, CONF_no_bidi); gppb(sesskey, "WinNameAlways", true, conf, CONF_win_name_always); gpps(sesskey, "WinTitle", "", conf, CONF_wintitle); gppi(sesskey, "TermWidth", 80, conf, CONF_width); diff --git a/sftp.c b/sftp.c index 7a6d544..4efcf7a 100644 --- a/sftp.c +++ b/sftp.c @@ -596,8 +596,6 @@ bool fxp_fstat_recv(struct sftp_packet *pktin, struct sftp_request *req, sfree(req); if (pktin->type == SSH_FXP_ATTRS) { return fxp_got_attrs(pktin, attrs); - sftp_pkt_free(pktin); - return true; } else { fxp_got_status(pktin); sftp_pkt_free(pktin); diff --git a/sftpcommon.c b/sftpcommon.c index 4912899..43b6575 100644 --- a/sftpcommon.c +++ b/sftpcommon.c @@ -85,6 +85,12 @@ bool BinarySource_get_fxp_attrs(BinarySource *src, struct fxp_attrs *attrs) if (attrs->flags & SSH_FILEXFER_ATTR_EXTENDED) { unsigned long count = get_uint32(src); while (count--) { + if (get_err(src)) { + /* Truncated packet. Don't waste time looking for + * attributes that aren't there. Caller should spot + * the truncation. */ + break; + } /* * We should try to analyse these, if we ever find one * we recognise. diff --git a/sign.sh b/sign.sh index bece850..2d81c63 100755 --- a/sign.sh +++ b/sign.sh @@ -49,6 +49,8 @@ else for i in putty*src.zip putty*.tar.gz \ w32/*.exe w32/*.zip w32/*.msi \ w64/*.exe w64/*.zip w64/*.msi \ + wa32/*.exe wa32/*.zip wa32/*.msi \ + wa64/*.exe wa64/*.zip wa64/*.msi \ w32old/*.exe w32old/*.zip; do sign --detach-sign "$i" "$i.gpg" done diff --git a/ssh.c b/ssh.c index 9cab648..c304804 100644 --- a/ssh.c +++ b/ssh.c @@ -54,7 +54,9 @@ struct Ssh { ssh_sharing_state *connshare; bool attempting_connshare; +#ifndef NO_GSSAPI struct ssh_connection_shared_gss_state gss_state; +#endif char *savedhost; int savedport; @@ -135,6 +137,8 @@ struct Ssh { Pinger *pinger; + char *deferred_abort_message; + bool need_random_unref; }; @@ -264,13 +268,22 @@ static void ssh_got_ssh_version(struct ssh_version_receiver *rcv, userauth_layer = ssh2_userauth_new( connection_layer, ssh->savedhost, ssh->fullhostname, conf_get_filename(ssh->conf, CONF_keyfile), + conf_get_bool(ssh->conf, CONF_ssh_show_banner), conf_get_bool(ssh->conf, CONF_tryagent), username, conf_get_bool(ssh->conf, CONF_change_username), conf_get_bool(ssh->conf, CONF_try_ki_auth), +#ifndef NO_GSSAPI conf_get_bool(ssh->conf, CONF_try_gssapi_auth), conf_get_bool(ssh->conf, CONF_try_gssapi_kex), conf_get_bool(ssh->conf, CONF_gssapifwd), - &ssh->gss_state); + &ssh->gss_state +#else + false, + false, + false, + NULL +#endif + ); ssh_connect_ppl(ssh, userauth_layer); transport_child_layer = userauth_layer; @@ -282,8 +295,12 @@ static void ssh_got_ssh_version(struct ssh_version_receiver *rcv, ssh->fullhostname, ssh_verstring_get_local(old_bpp), ssh_verstring_get_remote(old_bpp), +#ifndef NO_GSSAPI &ssh->gss_state, - &ssh->stats, transport_child_layer, false); +#else + NULL, +#endif + &ssh->stats, transport_child_layer, NULL); ssh_connect_ppl(ssh, ssh->base_layer); if (userauth_layer) @@ -555,6 +572,24 @@ void ssh_user_close(Ssh *ssh, const char *fmt, ...) } } +void ssh_deferred_abort_callback(void *vctx) +{ + Ssh *ssh = (Ssh *)vctx; + char *msg = ssh->deferred_abort_message; + ssh->deferred_abort_message = NULL; + ssh_sw_abort(ssh, msg); + sfree(msg); +} + +void ssh_sw_abort_deferred(Ssh *ssh, const char *fmt, ...) +{ + if (!ssh->deferred_abort_message) { + GET_FORMATTED_MSG; + ssh->deferred_abort_message = msg; + queue_toplevel_callback(ssh_deferred_abort_callback, ssh); + } +} + static void ssh_socket_log(Plug *plug, int type, SockAddr *addr, int port, const char *error_msg, int error_code) { @@ -580,7 +615,7 @@ static void ssh_closing(Plug *plug, const char *error_msg, int error_code, { Ssh *ssh = container_of(plug, Ssh, plug); if (error_msg) { - ssh_remote_error(ssh, "Network error: %s", error_msg); + ssh_remote_error(ssh, "%s", error_msg); } else if (ssh->bpp) { ssh->bpp->input_eof = true; queue_idempotent_callback(&ssh->bpp->ic_in_raw); @@ -915,6 +950,8 @@ static void ssh_free(Backend *be) ssh_gss_cleanup(ssh->gss_state.libs); #endif + sfree(ssh->deferred_abort_message); + delete_callbacks_for_context(ssh); /* likely to catch ic_out_raw */ need_random_unref = ssh->need_random_unref; diff --git a/ssh.h b/ssh.h index e769e5f..b6dd71e 100644 --- a/ssh.h +++ b/ssh.h @@ -407,12 +407,25 @@ void ssh_remote_error(Ssh *ssh, const char *fmt, ...); void ssh_remote_eof(Ssh *ssh, const char *fmt, ...); void ssh_proto_error(Ssh *ssh, const char *fmt, ...); void ssh_sw_abort(Ssh *ssh, const char *fmt, ...); +void ssh_sw_abort_deferred(Ssh *ssh, const char *fmt, ...); void ssh_user_close(Ssh *ssh, const char *fmt, ...); -#define SSH_CIPHER_IDEA 1 -#define SSH_CIPHER_DES 2 -#define SSH_CIPHER_3DES 3 -#define SSH_CIPHER_BLOWFISH 6 +/* Bit positions in the SSH-1 cipher protocol word */ +#define SSH1_CIPHER_IDEA 1 +#define SSH1_CIPHER_DES 2 +#define SSH1_CIPHER_3DES 3 +#define SSH1_CIPHER_BLOWFISH 6 + +/* The subset of those that we support, with names for selecting them + * on Uppity's command line */ +#define SSH1_SUPPORTED_CIPHER_LIST(X) \ + X(SSH1_CIPHER_3DES, "3des") \ + X(SSH1_CIPHER_BLOWFISH, "blowfish") \ + X(SSH1_CIPHER_DES, "des") \ + /* end of list */ +#define SSH1_CIPHER_LIST_MAKE_MASK(bitpos, name) | (1U << bitpos) +#define SSH1_SUPPORTED_CIPHER_MASK \ + (0 SSH1_SUPPORTED_CIPHER_LIST(SSH1_CIPHER_LIST_MAKE_MASK)) struct ssh_key { const ssh_keyalg *vt; @@ -451,6 +464,7 @@ struct ec_mcurve { MontgomeryCurve *mc; MontgomeryPoint *G; + unsigned log2_cofactor; }; /* Edwards form curve */ @@ -634,10 +648,10 @@ static inline void ssh_cipher_decrypt(ssh_cipher *c, void *blk, int len) { c->vt->decrypt(c, blk, len); } static inline void ssh_cipher_encrypt_length( ssh_cipher *c, void *blk, int len, unsigned long seq) -{ return c->vt->encrypt_length(c, blk, len, seq); } +{ c->vt->encrypt_length(c, blk, len, seq); } static inline void ssh_cipher_decrypt_length( ssh_cipher *c, void *blk, int len, unsigned long seq) -{ return c->vt->decrypt_length(c, blk, len, seq); } +{ c->vt->decrypt_length(c, blk, len, seq); } static inline const struct ssh_cipheralg *ssh_cipher_alg(ssh_cipher *c) { return c->vt; } @@ -715,9 +729,9 @@ static inline ssh_hash *ssh_hash_new(const ssh_hashalg *alg) static inline ssh_hash *ssh_hash_copy(ssh_hash *h) { return h->vt->copy(h); } static inline void ssh_hash_final(ssh_hash *h, unsigned char *out) -{ return h->vt->final(h, out); } +{ h->vt->final(h, out); } static inline void ssh_hash_free(ssh_hash *h) -{ return h->vt->free(h); } +{ h->vt->free(h); } static inline const ssh_hashalg *ssh_hash_alg(ssh_hash *h) { return h->vt; } @@ -741,6 +755,13 @@ struct ssh_kexes { const ssh_kex *const *list; }; +/* Indices of the negotiation strings in the KEXINIT packet */ +enum kexlist { + KEXLIST_KEX, KEXLIST_HOSTKEY, KEXLIST_CSCIPHER, KEXLIST_SCCIPHER, + KEXLIST_CSMAC, KEXLIST_SCMAC, KEXLIST_CSCOMP, KEXLIST_SCCOMP, + NKEXLIST +}; + struct ssh_keyalg { /* Constructors that create an ssh_key */ ssh_key *(*new_pub) (const ssh_keyalg *self, ptrlen pub); diff --git a/ssh1bpp.c b/ssh1bpp.c index 77cec35..381da1e 100644 --- a/ssh1bpp.c +++ b/ssh1bpp.c @@ -42,6 +42,7 @@ static const struct BinaryPacketProtocolVtable ssh1_bpp_vtable = { ssh1_bpp_handle_output, ssh1_bpp_new_pktout, ssh1_bpp_queue_disconnect, + 0xFFFFFFFF, /* no special packet size limit for this bpp */ }; BinaryPacketProtocol *ssh1_bpp_new(LogContext *logctx) @@ -143,9 +144,9 @@ static void ssh1_bpp_handle_input(BinaryPacketProtocol *bpp) s->len = toint(GET_32BIT_MSB_FIRST(lenbuf)); } - if (s->len < 0 || s->len > 262144) { /* SSH1.5-mandated max size */ + if (s->len < 5 || s->len > 262144) { /* SSH1.5-mandated max size */ ssh_sw_abort(s->bpp.ssh, - "Extremely large packet length from remote suggests" + "Out-of-range packet length from remote suggests" " data stream corruption"); crStopV; } diff --git a/ssh1connection-client.c b/ssh1connection-client.c index faa0df2..40107dc 100644 --- a/ssh1connection-client.c +++ b/ssh1connection-client.c @@ -526,3 +526,8 @@ SshChannel *ssh1_serverside_agent_open(ConnectionLayer *cl, Channel *chan) { unreachable("Should never be called in the client"); } + +bool ssh1_connection_need_antispoof_prompt(struct ssh1_connection_state *s) +{ + return !seat_set_trust_status(s->ppl.seat, false); +} diff --git a/ssh1connection-server.c b/ssh1connection-server.c index 14a54ae..aa44c52 100644 --- a/ssh1connection-server.c +++ b/ssh1connection-server.c @@ -45,13 +45,22 @@ static const struct SshChannelVtable ssh1sesschan_vtable = { NULL /* hint_channel_is_simple */, }; +void ssh1connection_server_configure( + PacketProtocolLayer *ppl, const SshServerConfig *ssc) +{ + struct ssh1_connection_state *s = + container_of(ppl, struct ssh1_connection_state, ppl); + s->ssc = ssc; +} + void ssh1_connection_direction_specific_setup( struct ssh1_connection_state *s) { if (!s->mainchan_chan) { s->mainchan_sc.vt = &ssh1sesschan_vtable; s->mainchan_sc.cl = &s->cl; - s->mainchan_chan = sesschan_new(&s->mainchan_sc, s->ppl.logctx, NULL); + s->mainchan_chan = sesschan_new( + &s->mainchan_sc, s->ppl.logctx, NULL, s->ssc); } } @@ -88,7 +97,7 @@ bool ssh1_handle_direction_specific_packet( return true; case SSH1_CMSG_REQUEST_COMPRESSION: - if (s->compressing) { + if (s->compressing || !s->ssc->ssh1_allow_compression) { pktout = ssh_bpp_new_pktout(s->ppl.bpp, SSH1_SMSG_FAILURE); pq_push(s->ppl.out_pq, pktout); } else { @@ -365,3 +374,8 @@ SshChannel *ssh1_serverside_agent_open(ConnectionLayer *cl, Channel *chan) return &c->sc; } + +bool ssh1_connection_need_antispoof_prompt(struct ssh1_connection_state *s) +{ + return false; +} diff --git a/ssh1connection.c b/ssh1connection.c index 8b0c3aa..501ab2a 100644 --- a/ssh1connection.c +++ b/ssh1connection.c @@ -197,6 +197,8 @@ static void ssh1_connection_free(PacketProtocolLayer *ppl) while ((c = delpos234(s->channels, 0)) != NULL) ssh1_channel_free(c); freetree234(s->channels); + if (s->mainchan_chan) + chan_free(s->mainchan_chan); if (s->x11disp) x11_free_display(s->x11disp); @@ -209,6 +211,9 @@ static void ssh1_connection_free(PacketProtocolLayer *ppl) freetree234(s->rportfwds); portfwdmgr_free(s->portfwdmgr); + if (s->antispoof_prompt) + free_prompts(s->antispoof_prompt); + delete_callbacks_for_context(s); sfree(s); @@ -376,6 +381,42 @@ static void ssh1_connection_process_queue(PacketProtocolLayer *ppl) crBegin(s->crState); + /* + * Signal the seat that authentication is done, so that it can + * deploy spoofing defences. If it doesn't have any, deploy our + * own fallback one. + * + * We do this here rather than at the end of userauth, because we + * might not have gone through userauth at all (if we're a + * connection-sharing downstream). + */ + if (ssh1_connection_need_antispoof_prompt(s)) { + s->antispoof_prompt = new_prompts(); + s->antispoof_prompt->to_server = true; + s->antispoof_prompt->from_server = false; + s->antispoof_prompt->name = dupstr("Authentication successful"); + add_prompt( + s->antispoof_prompt, + dupstr("Access granted. Press Return to begin session. "), false); + s->antispoof_ret = seat_get_userpass_input( + s->ppl.seat, s->antispoof_prompt, NULL); + while (1) { + while (s->antispoof_ret < 0 && + bufchain_size(s->ppl.user_input) > 0) + s->antispoof_ret = seat_get_userpass_input( + s->ppl.seat, s->antispoof_prompt, s->ppl.user_input); + + if (s->antispoof_ret >= 0) + break; + + s->want_user_input = true; + crReturnV; + s->want_user_input = false; + } + free_prompts(s->antispoof_prompt); + s->antispoof_prompt = NULL; + } + portfwdmgr_config(s->portfwdmgr, s->conf); s->portfwdmgr_configured = true; diff --git a/ssh1connection.h b/ssh1connection.h index a9ef072..1ee5465 100644 --- a/ssh1connection.h +++ b/ssh1connection.h @@ -52,6 +52,11 @@ struct ssh1_connection_state { bool compressing; /* used in server mode only */ bool sent_exit_status; /* also for server mode */ + prompts_t *antispoof_prompt; + int antispoof_ret; + + const SshServerConfig *ssc; + ConnectionLayer cl; PacketProtocolLayer ppl; }; @@ -118,3 +123,5 @@ bool ssh1_handle_direction_specific_packet( struct ssh1_connection_state *s, PktIn *pktin); bool ssh1_check_termination(struct ssh1_connection_state *s); + +bool ssh1_connection_need_antispoof_prompt(struct ssh1_connection_state *s); diff --git a/ssh1login-server.c b/ssh1login-server.c index c27882d..10d9a37 100644 --- a/ssh1login-server.c +++ b/ssh1login-server.c @@ -17,6 +17,8 @@ struct ssh1_login_server_state { PacketProtocolLayer *successor_layer; + const SshServerConfig *ssc; + int remote_protoflags; int local_protoflags; unsigned long supported_ciphers_mask, supported_auths_mask; @@ -70,12 +72,13 @@ static void no_progress(void *param, int action, int phase, int iprogress) {} PacketProtocolLayer *ssh1_login_server_new( PacketProtocolLayer *successor_layer, RSAKey *hostkey, - AuthPolicy *authpolicy) + AuthPolicy *authpolicy, const SshServerConfig *ssc) { struct ssh1_login_server_state *s = snew(struct ssh1_login_server_state); memset(s, 0, sizeof(*s)); s->ppl.vt = &ssh1_login_server_vtable; + s->ssc = ssc; s->hostkey = hostkey; s->authpolicy = authpolicy; @@ -143,10 +146,7 @@ static void ssh1_login_server_process_queue(PacketProtocolLayer *ppl) } s->local_protoflags = SSH1_PROTOFLAGS_SUPPORTED; - /* FIXME: ability to configure this to a subset */ - s->supported_ciphers_mask = ((1U << SSH_CIPHER_3DES) | - (1U << SSH_CIPHER_BLOWFISH) | - (1U << SSH_CIPHER_DES)); + s->supported_ciphers_mask = s->ssc->ssh1_cipher_mask; s->supported_auths_mask = 0; s->ap_methods = auth_methods(s->authpolicy); if (s->ap_methods & AUTHMETHOD_PASSWORD) @@ -241,8 +241,8 @@ static void ssh1_login_server_process_queue(PacketProtocolLayer *ppl) { const ssh_cipheralg *cipher = - (s->cipher_type == SSH_CIPHER_BLOWFISH ? &ssh_blowfish_ssh1 : - s->cipher_type == SSH_CIPHER_DES ? &ssh_des : &ssh_3des_ssh1); + (s->cipher_type == SSH1_CIPHER_BLOWFISH ? &ssh_blowfish_ssh1 : + s->cipher_type == SSH1_CIPHER_DES ? &ssh_des : &ssh_3des_ssh1); ssh1_bpp_new_cipher(s->ppl.bpp, cipher, s->session_key); } diff --git a/ssh1login.c b/ssh1login.c index 7ed3363..1922820 100644 --- a/ssh1login.c +++ b/ssh1login.c @@ -217,8 +217,11 @@ static void ssh1_login_process_queue(PacketProtocolLayer *ppl) return; } - s->len = (s->hostkey.bytes > s->servkey.bytes ? - s->hostkey.bytes : s->servkey.bytes); + s->len = 32; + if (s->len < s->hostkey.bytes) + s->len = s->hostkey.bytes; + if (s->len < s->servkey.bytes) + s->len = s->servkey.bytes; s->rsabuf = snewn(s->len, unsigned char); @@ -300,11 +303,11 @@ static void ssh1_login_process_queue(PacketProtocolLayer *ppl) ppl_logevent("AES not supported in SSH-1, skipping"); } else { switch (next_cipher) { - case CIPHER_3DES: s->cipher_type = SSH_CIPHER_3DES; + case CIPHER_3DES: s->cipher_type = SSH1_CIPHER_3DES; cipher_string = "3DES"; break; - case CIPHER_BLOWFISH: s->cipher_type = SSH_CIPHER_BLOWFISH; + case CIPHER_BLOWFISH: s->cipher_type = SSH1_CIPHER_BLOWFISH; cipher_string = "Blowfish"; break; - case CIPHER_DES: s->cipher_type = SSH_CIPHER_DES; + case CIPHER_DES: s->cipher_type = SSH1_CIPHER_DES; cipher_string = "single-DES"; break; } if (s->supported_ciphers_mask & (1 << s->cipher_type)) @@ -312,7 +315,7 @@ static void ssh1_login_process_queue(PacketProtocolLayer *ppl) } } if (!cipher_chosen) { - if ((s->supported_ciphers_mask & (1 << SSH_CIPHER_3DES)) == 0) { + if ((s->supported_ciphers_mask & (1 << SSH1_CIPHER_3DES)) == 0) { ssh_proto_error(s->ppl.ssh, "Server violates SSH-1 protocol " "by not supporting 3DES encryption"); } else { @@ -336,13 +339,13 @@ static void ssh1_login_process_queue(PacketProtocolLayer *ppl) } switch (s->cipher_type) { - case SSH_CIPHER_3DES: + case SSH1_CIPHER_3DES: ppl_logevent("Using 3DES encryption"); break; - case SSH_CIPHER_DES: + case SSH1_CIPHER_DES: ppl_logevent("Using single-DES encryption"); break; - case SSH_CIPHER_BLOWFISH: + case SSH1_CIPHER_BLOWFISH: ppl_logevent("Using Blowfish encryption"); break; } @@ -369,8 +372,8 @@ static void ssh1_login_process_queue(PacketProtocolLayer *ppl) { const ssh_cipheralg *cipher = - (s->cipher_type == SSH_CIPHER_BLOWFISH ? &ssh_blowfish_ssh1 : - s->cipher_type == SSH_CIPHER_DES ? &ssh_des : &ssh_3des_ssh1); + (s->cipher_type == SSH1_CIPHER_BLOWFISH ? &ssh_blowfish_ssh1 : + s->cipher_type == SSH1_CIPHER_DES ? &ssh_des : &ssh_3des_ssh1); ssh1_bpp_new_cipher(s->ppl.bpp, cipher, s->session_key); } diff --git a/ssh2bpp-bare.c b/ssh2bpp-bare.c index 44bb333..8dc3b11 100644 --- a/ssh2bpp-bare.c +++ b/ssh2bpp-bare.c @@ -31,6 +31,7 @@ static const struct BinaryPacketProtocolVtable ssh2_bare_bpp_vtable = { ssh2_bare_bpp_handle_output, ssh2_bare_bpp_new_pktout, ssh2_bpp_queue_disconnect, /* in sshcommon.c */ + 0x4000, /* packet size limit, per protocol spec in sshshare.c comment */ }; BinaryPacketProtocol *ssh2_bare_bpp_new(LogContext *logctx) diff --git a/ssh2bpp.c b/ssh2bpp.c index 8b8ccc4..79b97b3 100644 --- a/ssh2bpp.c +++ b/ssh2bpp.c @@ -52,6 +52,7 @@ static const struct BinaryPacketProtocolVtable ssh2_bpp_vtable = { ssh2_bpp_handle_output, ssh2_bpp_new_pktout, ssh2_bpp_queue_disconnect, /* in sshcommon.c */ + 0xFFFFFFFF, /* no special packet size limit for this bpp */ }; BinaryPacketProtocol *ssh2_bpp_new( diff --git a/ssh2connection-server.c b/ssh2connection-server.c index 274d9e3..1467db1 100644 --- a/ssh2connection-server.c +++ b/ssh2connection-server.c @@ -14,11 +14,13 @@ #include "sshserver.h" void ssh2connection_server_configure( - PacketProtocolLayer *ppl, const SftpServerVtable *sftpserver_vt) + PacketProtocolLayer *ppl, const SftpServerVtable *sftpserver_vt, + const SshServerConfig *ssc) { struct ssh2_connection_state *s = container_of(ppl, struct ssh2_connection_state, ppl); s->sftpserver_vt = sftpserver_vt; + s->ssc = ssc; } static ChanopenResult chan_open_session( @@ -28,7 +30,7 @@ static ChanopenResult chan_open_session( ppl_logevent("Opened session channel"); CHANOPEN_RETURN_SUCCESS(sesschan_new(sc, s->ppl.logctx, - s->sftpserver_vt)); + s->sftpserver_vt, s->ssc)); } static ChanopenResult chan_open_direct_tcpip( diff --git a/ssh2connection.c b/ssh2connection.c index 1a40ca7..78bb0ad 100644 --- a/ssh2connection.c +++ b/ssh2connection.c @@ -310,6 +310,11 @@ static void ssh2_connection_free(PacketProtocolLayer *ppl) } portfwdmgr_free(s->portfwdmgr); + if (s->antispoof_prompt) + free_prompts(s->antispoof_prompt); + + delete_callbacks_for_context(s); + sfree(s); } @@ -416,6 +421,8 @@ static bool ssh2_connection_filter_queue(struct ssh2_connection_state *s) ssh2_channel_init(c); c->remwindow = winsize; c->remmaxpkt = pktsize; + if (c->remmaxpkt > s->ppl.bpp->vt->packet_size_limit) + c->remmaxpkt = s->ppl.bpp->vt->packet_size_limit; if (c->chan->initial_fixed_window_size) { c->locwindow = c->locmaxwin = c->remlocwin = c->chan->initial_fixed_window_size; @@ -482,6 +489,8 @@ static bool ssh2_connection_filter_queue(struct ssh2_connection_state *s) c->halfopen = false; c->remwindow = get_uint32(pktin); c->remmaxpkt = get_uint32(pktin); + if (c->remmaxpkt > s->ppl.bpp->vt->packet_size_limit) + c->remmaxpkt = s->ppl.bpp->vt->packet_size_limit; chan_open_confirmation(c->chan); @@ -535,6 +544,17 @@ static bool ssh2_connection_filter_queue(struct ssh2_connection_state *s) c->chan, ext_type == SSH2_EXTENDED_DATA_STDERR, data.ptr, data.len); + /* + * The channel may have turned into a connection- + * shared one as a result of that chan_send, e.g. + * if the data we just provided completed the X11 + * auth phase and caused a callback to + * x11_sharing_handover. If so, do nothing + * further. + */ + if (c->sharectx) + break; + /* * If it looks like the remote end hit the end of * its window, and we didn't want it to do that, @@ -986,6 +1006,7 @@ static void ssh2_connection_process_queue(PacketProtocolLayer *ppl) s->want_user_input = false; } free_prompts(s->antispoof_prompt); + s->antispoof_prompt = NULL; } /* diff --git a/ssh2connection.h b/ssh2connection.h index 3858414..82145fc 100644 --- a/ssh2connection.h +++ b/ssh2connection.h @@ -41,6 +41,7 @@ struct ssh2_connection_state { int antispoof_ret; const SftpServerVtable *sftpserver_vt; + const SshServerConfig *ssc; /* * These store the list of global requests that we're waiting for diff --git a/ssh2kex-client.c b/ssh2kex-client.c index 4ed074f..64ec033 100644 --- a/ssh2kex-client.c +++ b/ssh2kex-client.c @@ -412,9 +412,6 @@ void ssh2kex_coroutine(struct ssh2_transport_state *s, bool *aborted) data = get_string(pktin); s->mic.value = (char *)data.ptr; s->mic.length = data.len; - /* Save expiration time of cred when delegating */ - if (s->gss_delegate && s->gss_cred_expiry != GSS_NO_EXPIRATION) - s->gss_cred_expiry = s->gss_cred_expiry; /* If there's a final token we loop to consume it */ if (get_bool(pktin)) { data = get_string(pktin); @@ -552,6 +549,7 @@ void ssh2kex_coroutine(struct ssh2_transport_state *s, bool *aborted) *aborted = true; return; } + s->rsa_kex_key_needs_freeing = true; put_stringpl(s->exhash, rsakeydata); @@ -611,6 +609,7 @@ void ssh2kex_coroutine(struct ssh2_transport_state *s, bool *aborted) ssh_rsakex_freekey(s->rsa_kex_key); s->rsa_kex_key = NULL; + s->rsa_kex_key_needs_freeing = false; crMaybeWaitUntilV((pktin = ssh2_transport_pop(s)) != NULL); if (pktin->type != SSH2_MSG_KEXRSA_DONE) { diff --git a/ssh2kex-server.c b/ssh2kex-server.c index d86a59f..d83d233 100644 --- a/ssh2kex-server.c +++ b/ssh2kex-server.c @@ -9,6 +9,7 @@ #include "sshbpp.h" #include "sshppl.h" #include "sshcr.h" +#include "sshserver.h" #include "storage.h" #include "ssh2transport.h" #include "mpint.h" @@ -243,13 +244,27 @@ void ssh2kex_coroutine(struct ssh2_transport_state *s, bool *aborted) ssh_hash_alg(s->exhash)->text_name); s->ppl.bpp->pls->kctx = SSH2_PKTCTX_RSAKEX; - { - const struct ssh_rsa_kex_extra *extra = - (const struct ssh_rsa_kex_extra *)s->kex_alg->extra; + const struct ssh_rsa_kex_extra *extra = + (const struct ssh_rsa_kex_extra *)s->kex_alg->extra; + + if (s->ssc && s->ssc->rsa_kex_key) { + int klen = ssh_rsakex_klen(s->ssc->rsa_kex_key); + if (klen >= extra->minklen) { + ppl_logevent("Using configured %d-bit RSA key", klen); + s->rsa_kex_key = s->ssc->rsa_kex_key; + } else { + ppl_logevent("Configured %d-bit RSA key is too short (min %d)", + klen, extra->minklen); + } + } + + if (!s->rsa_kex_key) { + ppl_logevent("Generating a %d-bit RSA key", extra->minklen); s->rsa_kex_key = snew(RSAKey); rsa_generate(s->rsa_kex_key, extra->minklen, no_progress, NULL); s->rsa_kex_key->comment = NULL; + s->rsa_kex_key_needs_freeing = true; } pktout = ssh_bpp_new_pktout(s->ppl.bpp, SSH2_MSG_KEXRSA_PUBKEY); @@ -288,8 +303,12 @@ void ssh2kex_coroutine(struct ssh2_transport_state *s, bool *aborted) return; } - ssh_rsakex_freekey(s->rsa_kex_key); + if (s->rsa_kex_key_needs_freeing) { + ssh_rsakex_freekey(s->rsa_kex_key); + sfree(s->rsa_kex_key); + } s->rsa_kex_key = NULL; + s->rsa_kex_key_needs_freeing = false; pktout = ssh_bpp_new_pktout(s->ppl.bpp, SSH2_MSG_KEXRSA_DONE); put_stringsb(pktout, finalise_and_sign_exhash(s)); diff --git a/ssh2transhk.c b/ssh2transhk.c index 237fdee..2e77fdf 100644 --- a/ssh2transhk.c +++ b/ssh2transhk.c @@ -76,6 +76,7 @@ void ssh_transient_hostkey_cache_add( if ((ent = find234(thc->cache, (void *)ssh_key_alg(key), ssh_transient_hostkey_cache_find)) != NULL) { + del234(thc->cache, ent); strbuf_free(ent->pub_blob); sfree(ent); } diff --git a/ssh2transport.c b/ssh2transport.c index 8640d89..4a6b8c7 100644 --- a/ssh2transport.c +++ b/ssh2transport.c @@ -9,6 +9,7 @@ #include "sshbpp.h" #include "sshppl.h" #include "sshcr.h" +#include "sshserver.h" #include "storage.h" #include "ssh2transport.h" #include "mpint.h" @@ -115,7 +116,7 @@ PacketProtocolLayer *ssh2_transport_new( const char *client_greeting, const char *server_greeting, struct ssh_connection_shared_gss_state *shgss, struct DataTransferStats *stats, PacketProtocolLayer *higher_layer, - bool is_server) + const SshServerConfig *ssc) { struct ssh2_transport_state *s = snew(struct ssh2_transport_state); memset(s, 0, sizeof(*s)); @@ -151,13 +152,18 @@ PacketProtocolLayer *ssh2_transport_new( s->outgoing_kexinit = strbuf_new(); s->incoming_kexinit = strbuf_new(); - if (is_server) { + if (ssc) { + s->ssc = ssc; s->client_kexinit = s->incoming_kexinit; s->server_kexinit = s->outgoing_kexinit; + s->cstrans = &s->in; + s->sctrans = &s->out; s->out.mkkey_adjust = 1; } else { s->client_kexinit = s->outgoing_kexinit; s->server_kexinit = s->incoming_kexinit; + s->cstrans = &s->out; + s->sctrans = &s->in; s->in.mkkey_adjust = 1; } @@ -214,8 +220,10 @@ static void ssh2_transport_free(PacketProtocolLayer *ppl) if (s->K) mp_free(s->K); if (s->dh_ctx) dh_cleanup(s->dh_ctx); - if (s->rsa_kex_key) + if (s->rsa_kex_key_needs_freeing) { ssh_rsakex_freekey(s->rsa_kex_key); + sfree(s->rsa_kex_key); + } if (s->ecdh_key) ssh_ecdhkex_freekey(s->ecdh_key); if (s->exhash) @@ -416,7 +424,7 @@ PktIn *ssh2_transport_pop(struct ssh2_transport_state *s) static void ssh2_write_kexinit_lists( BinarySink *pktout, struct kexinit_algorithm kexlists[NKEXLIST][MAXKEXLIST], - Conf *conf, int remote_bugs, + Conf *conf, const SshServerConfig *ssc, int remote_bugs, const char *hk_host, int hk_port, const ssh_keyalg *hk_prev, ssh_transient_hostkey_cache *thc, ssh_key *const *our_hostkeys, int our_nhostkeys, @@ -737,9 +745,13 @@ static void ssh2_write_kexinit_lists( */ for (i = 0; i < NKEXLIST; i++) { strbuf *list = strbuf_new(); - for (j = 0; j < MAXKEXLIST; j++) { - if (kexlists[i][j].name == NULL) break; - add_to_commasep(list, kexlists[i][j].name); + if (ssc && ssc->kex_override[i].ptr) { + put_datapl(list, ssc->kex_override[i]); + } else { + for (j = 0; j < MAXKEXLIST; j++) { + if (kexlists[i][j].name == NULL) break; + add_to_commasep(list, kexlists[i][j].name); + } } put_stringsb(pktout, list); } @@ -821,12 +833,26 @@ static bool ssh2_scan_kexinits( selected[i] = NULL; for (j = 0; j < MAXKEXLIST; j++) { - if (ptrlen_eq_string(found, kexlists[i][j].name)) { + if (kexlists[i][j].name && + ptrlen_eq_string(found, kexlists[i][j].name)) { selected[i] = &kexlists[i][j]; break; } } - assert(selected[i]); /* kexlists[] must cover one of the inputs */ + if (!selected[i]) { + /* + * In the client, this should never happen! But in the + * server, where we allow manual override on the command + * line of the exact KEXINIT strings, it can happen + * because the command line contained a typo. So we + * produce a reasonably useful message instead of an + * assertion failure. + */ + ssh_sw_abort(ssh, "Selected %s \"%.*s\" does not correspond to " + "any supported algorithm", + kexlist_descr[i], PTRLEN_PRINTF(found)); + return false; + } /* * If the kex or host key algorithm is not the first one in @@ -1062,7 +1088,7 @@ static void ssh2_transport_process_queue(PacketProtocolLayer *ppl) random_read(strbuf_append(s->outgoing_kexinit, 16), 16); ssh2_write_kexinit_lists( BinarySink_UPCAST(s->outgoing_kexinit), s->kexlists, - s->conf, s->ppl.remote_bugs, + s->conf, s->ssc, s->ppl.remote_bugs, s->savedhost, s->savedport, s->hostkey_alg, s->thc, s->hostkeys, s->nhostkeys, !s->got_session_id, s->can_gssapi_keyex, @@ -1109,8 +1135,8 @@ static void ssh2_transport_process_queue(PacketProtocolLayer *ppl) if (!ssh2_scan_kexinits( ptrlen_from_strbuf(s->client_kexinit), ptrlen_from_strbuf(s->server_kexinit), - s->kexlists, &s->kex_alg, &s->hostkey_alg, &s->out, &s->in, - &s->warn_kex, &s->warn_hk, &s->warn_cscipher, + s->kexlists, &s->kex_alg, &s->hostkey_alg, s->cstrans, + s->sctrans, &s->warn_kex, &s->warn_hk, &s->warn_cscipher, &s->warn_sccipher, s->ppl.ssh, NULL, &s->ignorepkt, &nhk, hks)) return; /* false means a fatal error function was called */ @@ -1781,6 +1807,7 @@ static void ssh2_transport_gss_update(struct ssh2_transport_state *s, if (mins > 0 && s->gss_ctxt_lifetime <= mins * 60) s->gss_status |= GSS_CTXT_EXPIRES; } +#endif /* NO_GSSAPI */ ptrlen ssh2_transport_get_session_id(PacketProtocolLayer *ppl) { @@ -1805,8 +1832,6 @@ void ssh2_transport_notify_auth_done(PacketProtocolLayer *ppl) queue_idempotent_callback(&s->ppl.ic_process_queue); } -#endif /* NO_GSSAPI */ - static bool ssh2_transport_get_specials( PacketProtocolLayer *ppl, add_special_fn_t add_special, void *ctx) { diff --git a/ssh2transport.h b/ssh2transport.h index 37bc570..8dc2330 100644 --- a/ssh2transport.h +++ b/ssh2transport.h @@ -18,11 +18,6 @@ #define DH_MIN_SIZE 1024 #define DH_MAX_SIZE 8192 -enum kexlist { - KEXLIST_KEX, KEXLIST_HOSTKEY, KEXLIST_CSCIPHER, KEXLIST_SCCIPHER, - KEXLIST_CSMAC, KEXLIST_SCMAC, KEXLIST_CSCOMP, KEXLIST_SCCOMP, - NKEXLIST -}; #define MAXKEXLIST 16 struct kexinit_algorithm { const char *name; @@ -139,6 +134,8 @@ struct ssh2_transport_state { struct DataTransferStats *stats; + const SshServerConfig *ssc; + char *client_greeting, *server_greeting; bool kex_in_progress; @@ -170,12 +167,13 @@ struct ssh2_transport_state { strbuf *outgoing_kexinit, *incoming_kexinit; strbuf *client_kexinit, *server_kexinit; /* aliases to the above */ int kex_init_value, kex_reply_value; - transport_direction in, out; + transport_direction in, out, *cstrans, *sctrans; ptrlen hostkeydata, sigdata; strbuf *hostkeyblob; char *keystr, *fingerprint; ssh_key *hkey; /* actual host key */ RSAKey *rsa_kex_key; /* for RSA kex */ + bool rsa_kex_key_needs_freeing; ecdh_key *ecdh_key; /* for ECDH kex */ unsigned char exchange_hash[MAX_HASH_LEN]; bool can_gssapi_keyex; diff --git a/ssh2userauth-server.c b/ssh2userauth-server.c index 465a710..3775395 100644 --- a/ssh2userauth-server.c +++ b/ssh2userauth-server.c @@ -24,6 +24,7 @@ struct ssh2_userauth_server_state { ptrlen session_id; AuthPolicy *authpolicy; + const SshServerConfig *ssc; ptrlen username, service, method; unsigned methods, this_method; @@ -64,7 +65,8 @@ static void free_auth_kbdint(AuthKbdInt *aki) } PacketProtocolLayer *ssh2_userauth_server_new( - PacketProtocolLayer *successor_layer, AuthPolicy *authpolicy) + PacketProtocolLayer *successor_layer, AuthPolicy *authpolicy, + const SshServerConfig *ssc) { struct ssh2_userauth_server_state *s = snew(struct ssh2_userauth_server_state); @@ -73,6 +75,7 @@ PacketProtocolLayer *ssh2_userauth_server_new( s->successor_layer = successor_layer; s->authpolicy = authpolicy; + s->ssc = ssc; return &s->ppl; } @@ -124,6 +127,13 @@ static void ssh2_userauth_server_process_queue(PacketProtocolLayer *ppl) s->session_id = ssh2_transport_get_session_id(s->transport_layer); + if (s->ssc->banner.ptr) { + pktout = ssh_bpp_new_pktout(s->ppl.bpp, SSH2_MSG_USERAUTH_BANNER); + put_stringpl(pktout, s->ssc->banner); + put_stringz(pktout, ""); /* language tag */ + pq_push(s->ppl.out_pq, pktout); + } + while (1) { crMaybeWaitUntilV((pktin = ssh2_userauth_server_pop(s)) != NULL); if (pktin->type != SSH2_MSG_USERAUTH_REQUEST) { diff --git a/ssh2userauth.c b/ssh2userauth.c index 2fca99b..c245275 100644 --- a/ssh2userauth.c +++ b/ssh2userauth.c @@ -27,7 +27,7 @@ struct ssh2_userauth_state { PacketProtocolLayer *transport_layer, *successor_layer; Filename *keyfile; - bool tryagent, change_username; + bool show_banner, tryagent, change_username; char *hostname, *fullhostname; char *default_username; bool try_ki_auth, try_gssapi_auth, try_gssapi_kex_auth, gssapi_fwd; @@ -61,8 +61,9 @@ struct ssh2_userauth_state { strbuf *last_methods_string; bool kbd_inter_refused; prompts_t *cur_prompt; - int num_prompts; - char *username; + uint32_t num_prompts; + const char *username; + char *locally_allocated_username; char *password; bool got_username; strbuf *publickey_blob; @@ -129,7 +130,7 @@ static const struct PacketProtocolLayerVtable ssh2_userauth_vtable = { PacketProtocolLayer *ssh2_userauth_new( PacketProtocolLayer *successor_layer, const char *hostname, const char *fullhostname, - Filename *keyfile, bool tryagent, + Filename *keyfile, bool show_banner, bool tryagent, const char *default_username, bool change_username, bool try_ki_auth, bool try_gssapi_auth, bool try_gssapi_kex_auth, bool gssapi_fwd, struct ssh_connection_shared_gss_state *shgss) @@ -142,6 +143,7 @@ PacketProtocolLayer *ssh2_userauth_new( s->hostname = dupstr(hostname); s->fullhostname = dupstr(fullhostname); s->keyfile = filename_copy(keyfile); + s->show_banner = show_banner; s->tryagent = tryagent; s->default_username = dupstr(default_username); s->change_username = change_username; @@ -179,8 +181,13 @@ static void ssh2_userauth_free(PacketProtocolLayer *ppl) agent_cancel_query(s->auth_agent_query); filename_free(s->keyfile); sfree(s->default_username); + sfree(s->locally_allocated_username); sfree(s->hostname); sfree(s->fullhostname); + sfree(s->publickey_comment); + sfree(s->publickey_algorithm); + if (s->publickey_blob) + strbuf_free(s->publickey_blob); strbuf_free(s->last_methods_string); if (s->banner_scc) stripctrl_free(s->banner_scc); @@ -197,6 +204,11 @@ static void ssh2_userauth_filter_queue(struct ssh2_userauth_state *s) while ((pktin = pq_peek(s->ppl.in_pq)) != NULL) { switch (pktin->type) { case SSH2_MSG_USERAUTH_BANNER: + if (!s->show_banner) { + pq_pop(s->ppl.in_pq); + break; + } + string = get_string(pktin); if (string.len > BANNER_LIMIT - bufchain_size(&s->banner)) string.len = BANNER_LIMIT - bufchain_size(&s->banner); @@ -386,7 +398,7 @@ static void ssh2_userauth_process_queue(PacketProtocolLayer *ppl) /* * Get a username. */ - if (s->got_username && s->change_username) { + if (s->got_username && !s->change_username) { /* * We got a username last time round this loop, and * with change_username turned off we don't try to get @@ -422,7 +434,9 @@ static void ssh2_userauth_process_queue(PacketProtocolLayer *ppl) ssh_user_close(s->ppl.ssh, "No username provided"); return; } - s->username = dupstr(s->cur_prompt->prompts[0]->result); + sfree(s->locally_allocated_username); /* for change_username */ + s->username = s->locally_allocated_username = + dupstr(s->cur_prompt->prompts[0]->result); free_prompts(s->cur_prompt); } else { if ((flags & FLAG_VERBOSE) || (flags & FLAG_INTERACTIVE)) @@ -617,8 +631,10 @@ static void ssh2_userauth_process_queue(PacketProtocolLayer *ppl) * Scan it for method identifiers we know about. */ bool srv_pubkey = false, srv_passwd = false; - bool srv_keyb_inter = false, srv_gssapi = false; - bool srv_gssapi_keyex_auth = false; + bool srv_keyb_inter = false; +#ifndef NO_GSSAPI + bool srv_gssapi = false, srv_gssapi_keyex_auth = false; +#endif for (ptrlen method; get_commasep_word(&methods, &method) ;) { if (ptrlen_eq_string(method, "publickey")) @@ -627,10 +643,12 @@ static void ssh2_userauth_process_queue(PacketProtocolLayer *ppl) srv_passwd = true; else if (ptrlen_eq_string(method, "keyboard-interactive")) srv_keyb_inter = true; +#ifndef NO_GSSAPI else if (ptrlen_eq_string(method, "gssapi-with-mic")) srv_gssapi = true; else if (ptrlen_eq_string(method, "gssapi-keyex")) srv_gssapi_keyex_auth = true; +#endif } /* @@ -1227,7 +1245,6 @@ static void ssh2_userauth_process_queue(PacketProtocolLayer *ppl) ptrlen name, inst; strbuf *sb; - int i; /* * We've got a fresh USERAUTH_INFO_REQUEST. @@ -1244,10 +1261,17 @@ static void ssh2_userauth_process_queue(PacketProtocolLayer *ppl) * Get any prompt(s) from the packet. */ s->num_prompts = get_uint32(pktin); - for (i = 0; i < s->num_prompts; i++) { + for (uint32_t i = 0; i < s->num_prompts; i++) { ptrlen prompt = get_string(pktin); bool echo = get_bool(pktin); + if (get_err(pktin)) { + ssh_proto_error( + s->ppl.ssh, "Server sent truncated " + "SSH_MSG_USERAUTH_INFO_REQUEST packet"); + return; + } + sb = strbuf_new(); if (!prompt.len) { put_datapl(sb, PTRLEN_LITERAL( @@ -1314,6 +1338,8 @@ static void ssh2_userauth_process_queue(PacketProtocolLayer *ppl) } else { s->cur_prompt->instr_reqd = false; } + if (sb->len) + s->cur_prompt->instruction = strbuf_to_str(sb); /* * Our prompts_t is fully constructed now. Get the @@ -1353,7 +1379,7 @@ static void ssh2_userauth_process_queue(PacketProtocolLayer *ppl) s->pktout = ssh_bpp_new_pktout( s->ppl.bpp, SSH2_MSG_USERAUTH_INFO_RESPONSE); put_uint32(s->pktout, s->num_prompts); - for (i=0; i < s->num_prompts; i++) { + for (uint32_t i = 0; i < s->num_prompts; i++) { put_stringz(s->pktout, s->cur_prompt->prompts[i]->result); } diff --git a/sshaes.c b/sshaes.c index d30ca91..1fce4d2 100644 --- a/sshaes.c +++ b/sshaes.c @@ -52,15 +52,17 @@ # define USE_CLANG_ATTR_TARGET_AARCH64 # endif #elif defined _MSC_VER - /* Visual Studio supports the crypto extension when targeting - * AArch64, but as of VS2017, the AArch32 header doesn't quite - * manage it (declaring the aese/aesd intrinsics without a round - * key operand). */ # if defined _M_ARM64 # define HW_AES HW_AES_NEON -# if defined _M_ARM64 -# define USE_ARM64_NEON_H /* unusual header name in this case */ -# endif + /* 64-bit Visual Studio uses the header in place + * of the standard */ +# define USE_ARM64_NEON_H +# elif defined _M_ARM +# define HW_AES HW_AES_NEON + /* 32-bit Visual Studio uses the right header name, but requires + * this #define to enable a set of intrinsic definitions that + * do not omit one of the parameters for vaes[ed]q_u8 */ +# define _ARM_USE_NEW_NEON_INTRINSICS # endif #endif diff --git a/sshbpp.h b/sshbpp.h index 8b3677c..380c41a 100644 --- a/sshbpp.h +++ b/sshbpp.h @@ -12,6 +12,7 @@ struct BinaryPacketProtocolVtable { PktOut *(*new_pktout)(int type); void (*queue_disconnect)(BinaryPacketProtocol *, const char *msg, int category); + uint32_t packet_size_limit; }; struct BinaryPacketProtocol { diff --git a/sshchan.h b/sshchan.h index df063f0..cedf357 100644 --- a/sshchan.h +++ b/sshchan.h @@ -250,8 +250,8 @@ static inline void sshfwd_x11_sharing_handover( SshChannel *c, ssh_sharing_connstate *cs, share_channel *sch, const char *addr, int port, int endian, int maj, int min, const void *idata, int ilen) -{ return c->vt->x11_sharing_handover(c, cs, sch, addr, port, endian, - maj, min, idata, ilen); } +{ c->vt->x11_sharing_handover(c, cs, sch, addr, port, endian, + maj, min, idata, ilen); } static inline void sshfwd_send_exit_status(SshChannel *c, int status) { c->vt->send_exit_status(c, status); } static inline void sshfwd_send_exit_signal( diff --git a/sshecc.c b/sshecc.c index 8096568..dd9a7e3 100644 --- a/sshecc.c +++ b/sshecc.c @@ -66,11 +66,12 @@ static void initialise_wcurve( static void initialise_mcurve( struct ec_curve *curve, mp_int *p, mp_int *a, mp_int *b, - mp_int *G_x) + mp_int *G_x, unsigned log2_cofactor) { initialise_common(curve, EC_MONTGOMERY, p); curve->m.mc = ecc_montgomery_curve(p, a, b); + curve->m.log2_cofactor = log2_cofactor; curve->m.G = ecc_montgomery_point_new(curve->m.mc, G_x); } @@ -194,7 +195,7 @@ static struct ec_curve *ec_curve25519(void) mp_int *a = MP_LITERAL(0x0000000000000000000000000000000000000000000000000000000000076d06); mp_int *b = MP_LITERAL(0x0000000000000000000000000000000000000000000000000000000000000001); mp_int *G_x = MP_LITERAL(0x0000000000000000000000000000000000000000000000000000000000000009); - initialise_mcurve(&curve, p, a, b, G_x); + initialise_mcurve(&curve, p, a, b, G_x, 3); mp_free(p); mp_free(a); mp_free(b); @@ -796,14 +797,14 @@ static ssh_key *ecdsa_new_priv_openssh( get_string(src); - struct eddsa_key *ek = snew(struct eddsa_key); + struct ecdsa_key *ek = snew(struct ecdsa_key); ek->sshk.vt = alg; ek->curve = curve; ek->privateKey = NULL; - ek->publicKey = get_epoint(src, curve); + ek->publicKey = get_wpoint(src, curve); if (!ek->publicKey) { - eddsa_freekey(&ek->sshk); + ecdsa_freekey(&ek->sshk); return NULL; } @@ -1283,10 +1284,17 @@ static void ssh_ecdhkex_m_setup(ecdh_key *dh) random_read(strbuf_append(bytes, dh->curve->fieldBytes), dh->curve->fieldBytes); - bytes->u[0] &= 0xF8; - bytes->u[bytes->len-1] &= 0x7F; - bytes->u[bytes->len-1] |= 0x40; dh->private = mp_from_bytes_le(ptrlen_from_strbuf(bytes)); + + /* Ensure the private key has the highest valid bit set, and no + * bits _above_ the highest valid one */ + mp_reduce_mod_2to(dh->private, dh->curve->fieldBits); + mp_set_bit(dh->private, dh->curve->fieldBits - 1, 1); + + /* Clear a curve-specific number of low bits */ + for (unsigned bit = 0; bit < dh->curve->m.log2_cofactor; bit++) + mp_set_bit(dh->private, bit, 0); + strbuf_free(bytes); dh->m_public = ecc_montgomery_multiply(dh->curve->m.G, dh->private); @@ -1349,6 +1357,14 @@ static mp_int *ssh_ecdhkex_w_getkey(ecdh_key *dh, ptrlen remoteKey) static mp_int *ssh_ecdhkex_m_getkey(ecdh_key *dh, ptrlen remoteKey) { mp_int *remote_x = mp_from_bytes_le(remoteKey); + + /* Per RFC 7748 section 5, discard any set bits of the other + * side's public value beyond the minimum number of bits required + * to represent all valid values. However, an overlarge value that + * still fits into the remaining number of bits is accepted, and + * will be reduced mod p. */ + mp_reduce_mod_2to(remote_x, dh->curve->fieldBits); + if (mp_eq_integer(remote_x, 0)) { /* * The libssh spec for Curve25519 key exchange says that diff --git a/sshppl.h b/sshppl.h index 068e8e6..baae1d8 100644 --- a/sshppl.h +++ b/sshppl.h @@ -103,11 +103,11 @@ PacketProtocolLayer *ssh2_transport_new( const char *client_greeting, const char *server_greeting, struct ssh_connection_shared_gss_state *shgss, struct DataTransferStats *stats, PacketProtocolLayer *higher_layer, - bool is_server); + const SshServerConfig *ssc); PacketProtocolLayer *ssh2_userauth_new( PacketProtocolLayer *successor_layer, const char *hostname, const char *fullhostname, - Filename *keyfile, bool tryagent, + Filename *keyfile, bool show_banner, bool tryagent, const char *default_username, bool change_username, bool try_ki_auth, bool try_gssapi_auth, bool try_gssapi_kex_auth, diff --git a/sshprime.c b/sshprime.c index 4d1524a..44ab386 100644 --- a/sshprime.c +++ b/sshprime.c @@ -194,10 +194,12 @@ mp_int *primegen( * random number with the top bit set and the bottom bit clear, * multiply it by `factor', and add one. */ - mp_int *p = mp_random_bits(bits - 1); + mp_int *p = mp_power_2(bits - 1); /* ensure top bit is 1 */ + mp_int *r = mp_random_bits(bits - 1); + mp_or_into(p, p, r); + mp_free(r); + mp_set_bit(p, 0, factor ? 0 : 1); /* set bottom bit appropriately */ - mp_set_bit(p, 0, factor ? 0 : 1); /* bottom bit */ - mp_set_bit(p, bits-1, 1); /* top bit */ for (size_t i = 0; i < fbsize; i++) mp_set_bit(p, bits-fbsize + i, 1 & (firstbits >> i)); @@ -382,7 +384,7 @@ static inline unsigned firstbits_b_min( unsigned a, unsigned lo, unsigned hi, unsigned min_separation) { /* To get a large enough product, b must be at least this much */ - unsigned b_min = (lo*lo + a - 1) / a; + unsigned b_min = (2*lo*lo + a - 1) / a; /* Now enforce a /* Collect environmental noise every 5 minutes */ @@ -78,6 +79,18 @@ static void random_create(const ssh_hashalg *hashalg) random_save_seed(); } +void random_save_seed(void) +{ + int len; + void *data; + + if (random_active) { + random_get_savedata(&data, &len); + write_random_seed(data, len); + sfree(data); + } +} + void random_ref(void) { if (!random_active++) @@ -97,16 +110,22 @@ void random_reseed(ptrlen seed) prng_seed_finish(global_prng); } -void random_unref(void) +void random_clear(void) { - assert(random_active > 0); - if (random_active == 1) { + if (global_prng) { random_save_seed(); expire_timer_context(&random_timer_ctx); prng_free(global_prng); global_prng = NULL; + random_active = 0; } - random_active--; +} + +void random_unref(void) +{ + assert(random_active > 0); + if (--random_active == 0) + random_clear(); } void random_read(void *buf, size_t size) diff --git a/sshrsa.c b/sshrsa.c index 1fd5fb2..4d26f9f 100644 --- a/sshrsa.c +++ b/sshrsa.c @@ -296,8 +296,11 @@ bool rsa_verify(RSAKey *key) mp_int *n, *ed, *pm1, *qm1; unsigned ok = 1; - /* Preliminary checks: p,q must actually be nonzero. */ - if (mp_eq_integer(key->p, 0) | mp_eq_integer(key->q, 0)) + /* Preliminary checks: p,q can't be 0 or 1. (Of course no other + * very small value is any good either, but these are the values + * we _must_ check for to avoid assertion failures further down + * this function.) */ + if (!(mp_hs_integer(key->p, 2) & mp_hs_integer(key->q, 2))) return false; /* n must equal pq. */ diff --git a/sshrsag.c b/sshrsag.c index d70ac6b..2d88fef 100644 --- a/sshrsag.c +++ b/sshrsag.c @@ -71,15 +71,26 @@ int rsa_generate(RSAKey *key, int bits, progfn_t pfn, * but it doesn't cost much to make sure.) */ invent_firstbits(&pfirst, &qfirst, 2); - mp_int *p = primegen(bits / 2, RSA_EXPONENT, 1, NULL, - 1, pfn, pfnparam, pfirst); - mp_int *q = primegen(bits - bits / 2, RSA_EXPONENT, 1, NULL, - 2, pfn, pfnparam, qfirst); + int qbits = bits / 2; + int pbits = bits - qbits; + assert(pbits >= qbits); + mp_int *p = primegen(pbits, RSA_EXPONENT, 1, NULL, + 1, pfn, pfnparam, pfirst); + mp_int *q = primegen(qbits, RSA_EXPONENT, 1, NULL, + 2, pfn, pfnparam, qfirst); /* * Ensure p > q, by swapping them if not. + * + * We only need to do this if the two primes were generated with + * the same number of bits (i.e. if the requested key size is + * even) - otherwise it's already guaranteed! */ - mp_cond_swap(p, q, mp_cmp_hs(q, p)); + if (pbits == qbits) { + mp_cond_swap(p, q, mp_cmp_hs(q, p)); + } else { + assert(mp_cmp_hs(p, q)); + } /* * Now we have p, q and e. All we need to do now is work out diff --git a/sshserver.c b/sshserver.c index 5f6e7dd..876e1c0 100644 --- a/sshserver.c +++ b/sshserver.c @@ -21,6 +21,7 @@ typedef struct server server; struct server { bufchain in_raw, out_raw; IdempotentCallback ic_out_raw; + bool pending_close; bufchain dummy_user_input; /* we never put anything on this */ @@ -36,10 +37,12 @@ struct server { bool frozen; Conf *conf; + const SshServerConfig *ssc; ssh_key *const *hostkeys; int nhostkeys; RSAKey *hostkey1; AuthPolicy *authpolicy; + LogPolicy *logpolicy; const SftpServerVtable *sftpserver_vt; Seat seat; @@ -50,7 +53,9 @@ struct server { PacketProtocolLayer *base_layer; ConnectionLayer *cl; +#ifndef NO_GSSAPI struct ssh_connection_shared_gss_state gss_state; +#endif }; static void ssh_server_free_callback(void *vsrv); @@ -129,7 +134,7 @@ static void server_closing(Plug *plug, const char *error_msg, int error_code, { server *srv = container_of(plug, server, plug); if (error_msg) { - ssh_remote_error(&srv->ssh, "Network error: %s", error_msg); + ssh_remote_error(&srv->ssh, "%s", error_msg); } else if (srv->bpp) { srv->bpp->input_eof = true; queue_idempotent_callback(&srv->bpp->ic_in_raw); @@ -212,6 +217,19 @@ void ssh_conn_processed_data(Ssh *ssh) * around a peculiarity of the GUI event loop, I haven't yet. */ } +Conf *make_ssh_server_conf(void) +{ + Conf *conf = conf_new(); + load_open_settings(NULL, conf); + /* In Uppity, we support even the legacy des-cbc cipher by + * default, so that it will be available if the user forces it by + * overriding the KEXINIT strings. If the user wants it _not_ + * supported, of course, they can override KEXINIT in the other + * direction. */ + conf_set_bool(conf, CONF_ssh2_des_cbc, true); + return conf; +} + static const PlugVtable ssh_server_plugvt = { server_socket_log, server_closing, @@ -221,7 +239,8 @@ static const PlugVtable ssh_server_plugvt = { }; Plug *ssh_server_plug( - Conf *conf, ssh_key *const *hostkeys, int nhostkeys, + Conf *conf, const SshServerConfig *ssc, + ssh_key *const *hostkeys, int nhostkeys, RSAKey *hostkey1, AuthPolicy *authpolicy, LogPolicy *logpolicy, const SftpServerVtable *sftpserver_vt) { @@ -231,12 +250,14 @@ Plug *ssh_server_plug( srv->plug.vt = &ssh_server_plugvt; srv->conf = conf_copy(conf); + srv->ssc = ssc; srv->logctx = log_init(logpolicy, conf); conf_set_bool(srv->conf, CONF_ssh_no_shell, true); srv->nhostkeys = nhostkeys; srv->hostkeys = hostkeys; srv->hostkey1 = hostkey1; srv->authpolicy = authpolicy; + srv->logpolicy = logpolicy; srv->sftpserver_vt = sftpserver_vt; srv->seat.vt = &server_seat_vt; @@ -245,9 +266,11 @@ Plug *ssh_server_plug( bufchain_init(&srv->out_raw); bufchain_init(&srv->dummy_user_input); +#ifndef NO_GSSAPI /* FIXME: replace with sensible */ srv->gss_state.libs = snew(struct ssh_gss_liblist); srv->gss_state.libs->nlibraries = 0; +#endif return &srv->plug; } @@ -283,12 +306,17 @@ static void ssh_server_free_callback(void *vsrv) { server *srv = (server *)vsrv; + logeventf(srv->logctx, "freeing server instance"); + bufchain_clear(&srv->in_raw); bufchain_clear(&srv->out_raw); bufchain_clear(&srv->dummy_user_input); - sk_close(srv->socket); + if (srv->socket) + sk_close(srv->socket); + if (srv->base_layer) + ssh_ppl_free(srv->base_layer); if (srv->bpp) ssh_bpp_free(srv->bpp); @@ -297,11 +325,14 @@ static void ssh_server_free_callback(void *vsrv) conf_free(srv->conf); log_free(srv->logctx); +#ifndef NO_GSSAPI sfree(srv->gss_state.libs); /* FIXME: replace with sensible */ +#endif + LogPolicy *lp = srv->logpolicy; sfree(srv); - server_instance_terminated(); + server_instance_terminated(lp); } static void server_connect_bpp(server *srv) @@ -355,14 +386,51 @@ static void server_bpp_output_raw_data_callback(void *vctx) } } -#ifdef FIXME - if (ssh->pending_close) { - sk_close(ssh->s); - ssh->s = NULL; + if (srv->pending_close) { + sk_close(srv->socket); + srv->socket = NULL; + queue_toplevel_callback(ssh_server_free_callback, srv); } -#endif } +static void server_shutdown_internal(server *srv) +{ + /* + * We only need to free the base PPL, which will free the others + * (if any) transitively. + */ + if (srv->base_layer) { + ssh_ppl_free(srv->base_layer); + srv->base_layer = NULL; + } + + srv->cl = NULL; +} + +static void server_initiate_connection_close(server *srv) +{ + /* Wind up everything above the BPP. */ + server_shutdown_internal(srv); + + /* Force any remaining queued SSH packets through the BPP, and + * schedule closing the network socket after they go out. */ + ssh_bpp_handle_output(srv->bpp); + srv->pending_close = true; + queue_idempotent_callback(&srv->ic_out_raw); + + /* Now we expect the other end to close the connection too in + * response, so arrange that we'll receive notification of that + * via ssh_remote_eof. */ + srv->bpp->expect_close = true; +} + +#define GET_FORMATTED_MSG(fmt) \ + char *msg; \ + va_list ap; \ + va_start(ap, fmt); \ + msg = dupvprintf(fmt, ap); \ + va_end(ap); + #define LOG_FORMATTED_MSG(logctx, fmt) do \ { \ va_list ap; \ @@ -388,8 +456,14 @@ void ssh_remote_eof(Ssh *ssh, const char *fmt, ...) void ssh_proto_error(Ssh *ssh, const char *fmt, ...) { server *srv = container_of(ssh, server, ssh); - LOG_FORMATTED_MSG(srv->logctx, fmt); - queue_toplevel_callback(ssh_server_free_callback, srv); + if (srv->base_layer) { + GET_FORMATTED_MSG(fmt); + ssh_bpp_queue_disconnect(srv->bpp, msg, + SSH2_DISCONNECT_PROTOCOL_ERROR); + server_initiate_connection_close(srv); + logeventf(srv->logctx, "Protocol error: %s", msg); + sfree(msg); + } } void ssh_sw_abort(Ssh *ssh, const char *fmt, ...) @@ -425,7 +499,8 @@ static void server_got_ssh_version(struct ssh_version_receiver *rcv, connection_layer = ssh2_connection_new( &srv->ssh, NULL, false, srv->conf, ssh_verstring_get_local(old_bpp), &srv->cl); - ssh2connection_server_configure(connection_layer, srv->sftpserver_vt); + ssh2connection_server_configure(connection_layer, + srv->sftpserver_vt, srv->ssc); server_connect_ppl(srv, connection_layer); if (conf_get_bool(srv->conf, CONF_ssh_no_userauth)) { @@ -433,7 +508,7 @@ static void server_got_ssh_version(struct ssh_version_receiver *rcv, transport_child_layer = connection_layer; } else { userauth_layer = ssh2_userauth_server_new( - connection_layer, srv->authpolicy); + connection_layer, srv->authpolicy, srv->ssc); server_connect_ppl(srv, userauth_layer); transport_child_layer = userauth_layer; } @@ -442,7 +517,12 @@ static void server_got_ssh_version(struct ssh_version_receiver *rcv, srv->conf, NULL, 0, NULL, ssh_verstring_get_remote(old_bpp), ssh_verstring_get_local(old_bpp), - &srv->gss_state, &srv->stats, transport_child_layer, true); +#ifndef NO_GSSAPI + &srv->gss_state, +#else + NULL, +#endif + &srv->stats, transport_child_layer, srv->ssc); ssh2_transport_provide_hostkeys( srv->base_layer, srv->hostkeys, srv->nhostkeys); if (userauth_layer) @@ -455,10 +535,11 @@ static void server_got_ssh_version(struct ssh_version_receiver *rcv, server_connect_bpp(srv); connection_layer = ssh1_connection_new(&srv->ssh, srv->conf, &srv->cl); + ssh1connection_server_configure(connection_layer, srv->ssc); server_connect_ppl(srv, connection_layer); srv->base_layer = ssh1_login_server_new( - connection_layer, srv->hostkey1, srv->authpolicy); + connection_layer, srv->hostkey1, srv->authpolicy, srv->ssc); server_connect_ppl(srv, srv->base_layer); } diff --git a/sshserver.h b/sshserver.h index 2d6f829..129d6fe 100644 --- a/sshserver.h +++ b/sshserver.h @@ -1,12 +1,31 @@ typedef struct AuthPolicy AuthPolicy; +struct SshServerConfig { + const char *session_starting_dir; + + RSAKey *rsa_kex_key; + + /* + * In all of these ptrlens, setting the 'ptr' member to NULL means + * that we're not overriding the default configuration. + */ + ptrlen banner; /* default here is 'no banner' */ + ptrlen kex_override[NKEXLIST]; + + bool exit_signal_numeric; /* mimic an old server bug */ + + unsigned long ssh1_cipher_mask; + bool ssh1_allow_compression; +}; + Plug *ssh_server_plug( - Conf *conf, ssh_key *const *hostkeys, int nhostkeys, + Conf *conf, const SshServerConfig *ssc, + ssh_key *const *hostkeys, int nhostkeys, RSAKey *hostkey1, AuthPolicy *authpolicy, LogPolicy *logpolicy, const SftpServerVtable *sftpserver_vt); void ssh_server_start(Plug *plug, Socket *socket); -void server_instance_terminated(void); +void server_instance_terminated(LogPolicy *logpolicy); void platform_logevent(const char *msg); #define AUTHMETHODS(X) \ @@ -67,23 +86,30 @@ RSAKey *auth_publickey_ssh1( bool auth_successful(AuthPolicy *, ptrlen username, unsigned method); PacketProtocolLayer *ssh2_userauth_server_new( - PacketProtocolLayer *successor_layer, AuthPolicy *authpolicy); + PacketProtocolLayer *successor_layer, AuthPolicy *authpolicy, + const SshServerConfig *ssc); void ssh2_userauth_server_set_transport_layer( PacketProtocolLayer *userauth, PacketProtocolLayer *transport); void ssh2connection_server_configure( - PacketProtocolLayer *ppl, const SftpServerVtable *sftpserver_vt); + PacketProtocolLayer *ppl, const SftpServerVtable *sftpserver_vt, + const SshServerConfig *ssc); +void ssh1connection_server_configure( + PacketProtocolLayer *ppl, const SshServerConfig *ssc); PacketProtocolLayer *ssh1_login_server_new( PacketProtocolLayer *successor_layer, RSAKey *hostkey, - AuthPolicy *authpolicy); + AuthPolicy *authpolicy, const SshServerConfig *ssc); Channel *sesschan_new(SshChannel *c, LogContext *logctx, - const SftpServerVtable *sftpserver_vt); + const SftpServerVtable *sftpserver_vt, + const SshServerConfig *ssc); Backend *pty_backend_create( Seat *seat, LogContext *logctx, Conf *conf, char **argv, const char *cmd, - struct ssh_ttymodes ttymodes, bool pipes_instead_of_pty); + struct ssh_ttymodes ttymodes, bool pipes_instead_of_pty, const char *dir, + const char *const *env_vars_to_unset); +int pty_backend_exit_signum(Backend *be); ptrlen pty_backend_exit_signame(Backend *be, char **aux_msg); /* @@ -101,3 +127,5 @@ int platform_make_x11_server(Plug *plug, const char *progname, int mindisp, const char *screen_number_suffix, ptrlen authproto, ptrlen authdata, Socket **sockets, Conf *conf); + +Conf *make_ssh_server_conf(void); diff --git a/sshsha.c b/sshsha.c index 3c09d4c..d2bd7c5 100644 --- a/sshsha.c +++ b/sshsha.c @@ -702,8 +702,6 @@ struct sha1_neon_core { uint32_t e; }; -/* ------------- got up to here ----------------------------------------- */ - FUNC_ISA static inline uint32x4_t sha1_neon_load_input(const uint8_t *p) { diff --git a/sshverstring.c b/sshverstring.c index 0b9152f..4828c37 100644 --- a/sshverstring.c +++ b/sshverstring.c @@ -51,6 +51,7 @@ static const struct BinaryPacketProtocolVtable ssh_verstring_vtable = { ssh_verstring_handle_output, ssh_verstring_new_pktout, ssh_verstring_queue_disconnect, + 0xFFFFFFFF, /* no special packet size limit for this bpp */ }; static void ssh_detect_bugs(struct ssh_verstring_state *s); diff --git a/sshzlib.c b/sshzlib.c index 413a735..d7a78c6 100644 --- a/sshzlib.c +++ b/sshzlib.c @@ -850,7 +850,51 @@ struct zlib_decompress_ctx { lenrep; int uncomplen; unsigned char lenlen[19]; - unsigned char lengths[286 + 32]; + + /* + * Array that accumulates the code lengths sent in the header of a + * dynamic-Huffman-tree block. + * + * There are 286 actual symbols in the literal/length alphabet + * (256 literals plus 20 length categories), and 30 symbols in the + * distance alphabet. However, the block header transmits the + * number of code lengths for the former alphabet as a 5-bit value + * HLIT to be added to 257, and the latter as a 5-bit value HDIST + * to be added to 1. This means that the number of _code lengths_ + * can go as high as 288 for the symbol alphabet and 32 for the + * distance alphabet - each of those values being 2 more than the + * maximum number of actual symbols. + * + * It's tempting to rule that sending out-of-range HLIT or HDIST + * is therefore just illegal, and to fault it when we initially + * receive that header. But instead I've chosen to permit the + * Huffman-code definition to include code length entries for + * those unused symbols; if a header of that form is transmitted, + * then the effect will be that in the main body of the block, + * some bit sequence(s) will generate an illegal symbol number, + * and _that_ will be faulted as a decoding error. + * + * Rationale: this can already happen! The standard Huffman code + * used in a _static_ block for the literal/length alphabet is + * defined in such a way that it includes codes for symbols 287 + * and 288, which are then never actually sent in the body of the + * block. And I think that if the standard static tree definition + * is willing to include Huffman codes that don't correspond to a + * symbol, then it's an excessive restriction on dynamic tables + * not to permit them to do the same. In particular, it would be + * strange for a dynamic block not to be able to exactly mimic + * either or both of the Huffman codes used by a static block for + * the corresponding alphabet. + * + * So we place no constraint on HLIT or HDIST during code + * construction, and we make this array large enough to include + * the maximum number of code lengths that can possibly arise as a + * result. It's only trying to _use_ the junk Huffman codes after + * table construction is completed that will provoke a decode + * error. + */ + unsigned char lengths[288 + 32]; + unsigned long bits; int nbits; unsigned char window[WINSIZE]; @@ -1105,10 +1149,13 @@ bool zlib_decompress_block(ssh_decompressor *dc, zlib_freetable(&dctx->currdisttable); dctx->currdisttable = NULL; } - } else if (code < 286) { /* static tree can give >285; ignore */ + } else if (code < 286) { dctx->state = GOTLENSYM; dctx->sym = code; - } + } else { + /* literal/length symbols 286 and 287 are invalid */ + goto decode_error; + } break; case GOTLENSYM: rec = &lencodes[dctx->sym - 257]; diff --git a/stripctrl.c b/stripctrl.c index a688301..b5a8f05 100644 --- a/stripctrl.c +++ b/stripctrl.c @@ -159,16 +159,19 @@ static inline void stripctrl_check_line_limit( static inline void stripctrl_locale_put_wc(StripCtrlCharsImpl *scc, wchar_t wc) { - if (iswprint(wc) || stripctrl_ctrlchar_ok(scc, wc)) { + int width = mk_wcwidth(wc); + if ((iswprint(wc) && width >= 0) || stripctrl_ctrlchar_ok(scc, wc)) { /* Printable character, or one we're going to let through anyway. */ } else if (scc->substitution) { wc = scc->substitution; + width = mk_wcwidth(wc); + assert(width >= 0); } else { /* No defined substitution, so don't write any output wchar_t. */ return; } - stripctrl_check_line_limit(scc, wc, mk_wcwidth(wc)); + stripctrl_check_line_limit(scc, wc, width); char outbuf[MB_LEN_MAX]; size_t produced = wcrtomb(outbuf, wc, &scc->mbs_out); @@ -180,15 +183,19 @@ static inline void stripctrl_term_put_wc( StripCtrlCharsImpl *scc, unsigned long wc) { ptrlen prefix = PTRLEN_LITERAL(""); + int width = term_char_width(scc->term, wc); - if (!(wc & ~0x9F)) { + if (!(wc & ~0x9F) || width < 0) { /* This is something the terminal interprets as a control * character. */ if (!stripctrl_ctrlchar_ok(scc, wc)) { - if (!scc->substitution) + if (!scc->substitution) { return; - else + } else { wc = scc->substitution; + width = term_char_width(scc->term, wc); + assert(width >= 0); + } } if (wc == '\012') { @@ -200,7 +207,7 @@ static inline void stripctrl_term_put_wc( } } - stripctrl_check_line_limit(scc, wc, term_char_width(scc->term, wc)); + stripctrl_check_line_limit(scc, wc, width); if (prefix.len) put_datapl(scc->bs_out, prefix); diff --git a/terminal.c b/terminal.c index 2086698..968bc12 100644 --- a/terminal.c +++ b/terminal.c @@ -114,6 +114,7 @@ static void deselect(Terminal *); static void term_print_finish(Terminal *); static void scroll(Terminal *, int, int, int, bool); static void parse_optionalrgb(optionalrgb *out, unsigned *values); +static void term_added_data(Terminal *term); static termline *newtermline(Terminal *term, int cols, bool bce) { @@ -1340,7 +1341,6 @@ static void power_on(Terminal *term, bool clear) term->alt_save_attr = term->curr_attr = ATTR_DEFAULT; term->curr_truecolour.fg = term->curr_truecolour.bg = optionalrgb_none; term->save_truecolour = term->alt_save_truecolour = term->curr_truecolour; - term->term_editing = term->term_echoing = false; term->app_cursor_keys = conf_get_bool(term->conf, CONF_app_cursor); term->app_keypad_keys = conf_get_bool(term->conf, CONF_app_keypad); term->use_bce = conf_get_bool(term->conf, CONF_bce); @@ -1353,6 +1353,7 @@ static void power_on(Terminal *term, bool clear) term->urxvt_extended_mouse = false; win_set_raw_mouse_mode(term->win, false); term->bracketed_paste = false; + term->srm_echo = false; { int i; for (i = 0; i < 256; i++) @@ -1464,13 +1465,13 @@ static void set_erase_char(Terminal *term) void term_copy_stuff_from_conf(Terminal *term) { term->ansi_colour = conf_get_bool(term->conf, CONF_ansi_colour); - term->arabicshaping = conf_get_bool(term->conf, CONF_arabicshaping); + term->no_arabicshaping = conf_get_bool(term->conf, CONF_no_arabicshaping); term->beep = conf_get_int(term->conf, CONF_beep); term->bellovl = conf_get_bool(term->conf, CONF_bellovl); term->bellovl_n = conf_get_int(term->conf, CONF_bellovl_n); term->bellovl_s = conf_get_int(term->conf, CONF_bellovl_s); term->bellovl_t = conf_get_int(term->conf, CONF_bellovl_t); - term->bidi = conf_get_bool(term->conf, CONF_bidi); + term->no_bidi = conf_get_bool(term->conf, CONF_no_bidi); term->bksp_is_delete = conf_get_bool(term->conf, CONF_bksp_is_delete); term->blink_cur = conf_get_bool(term->conf, CONF_blink_cur); term->blinktext = conf_get_bool(term->conf, CONF_blinktext); @@ -1564,10 +1565,10 @@ void term_reconfig(Terminal *term, Conf *conf) * If the bidi or shaping settings have changed, flush the bidi * cache completely. */ - if (conf_get_bool(term->conf, CONF_arabicshaping) != - conf_get_bool(conf, CONF_arabicshaping) || - conf_get_bool(term->conf, CONF_bidi) != - conf_get_bool(conf, CONF_bidi)) { + if (conf_get_bool(term->conf, CONF_no_arabicshaping) != + conf_get_bool(conf, CONF_no_arabicshaping) || + conf_get_bool(term->conf, CONF_no_bidi) != + conf_get_bool(conf, CONF_no_bidi)) { for (i = 0; i < term->bidi_cache_size; i++) { sfree(term->pre_bidi_cache[i].chars); sfree(term->post_bidi_cache[i].chars); @@ -1754,6 +1755,8 @@ Terminal *term_init(Conf *myconf, struct unicode_data *ucsdata, TermWin *win) term->trusted = true; + term->bracketed_paste_active = false; + return term; } @@ -1804,6 +1807,7 @@ void term_free(Terminal *term) sfree(term->tabs); expire_timer_context(term); + delete_callbacks_for_context(term); conf_free(term->conf); @@ -2634,11 +2638,6 @@ static void toggle_mode(Terminal *term, int mode, int query, bool state) case 8: /* DECARM: auto key repeat */ term->repeat_off = !state; break; - case 10: /* DECEDM: set local edit mode */ - term->term_editing = state; - if (term->ldisc) /* cause ldisc to notice changes */ - ldisc_echoedit_update(term->ldisc); - break; case 25: /* DECTCEM: enable/disable cursor */ compatibility2(OTHER, VT220); term->cursor_on = state; @@ -2700,9 +2699,7 @@ static void toggle_mode(Terminal *term, int mode, int query, bool state) term->insert = state; break; case 12: /* SRM: set echo mode */ - term->term_echoing = !state; - if (term->ldisc) /* cause ldisc to notice changes */ - ldisc_echoedit_update(term->ldisc); + term->srm_echo = !state; break; case 20: /* LNM: Return sends ... */ term->cr_lf_return = state; @@ -2954,6 +2951,126 @@ static void term_display_graphic_char(Terminal *term, unsigned long c) seen_disp_event(term); } +static strbuf *term_input_data_from_unicode( + Terminal *term, const wchar_t *widebuf, int len) +{ + strbuf *buf = strbuf_new(); + + if (in_utf(term)) { + /* + * Translate input wide characters into UTF-8 to go in the + * terminal's input data queue. + */ + for (int i = 0; i < len; i++) { + unsigned long ch = widebuf[i]; + + if (IS_SURROGATE(ch)) { +#ifdef PLATFORM_IS_UTF16 + if (i+1 < len) { + unsigned long ch2 = widebuf[i+1]; + if (IS_SURROGATE_PAIR(ch, ch2)) { + ch = FROM_SURROGATES(ch, ch2); + i++; + } + } else +#endif + { + /* Unrecognised UTF-16 sequence */ + ch = '.'; + } + } + + char utf8_chr[6]; + put_data(buf, utf8_chr, encode_utf8(utf8_chr, ch)); + } + } else { + /* + * Call to the character-set subsystem to translate into + * whatever charset the terminal is currently configured in. + * + * Since the terminal doesn't currently support any multibyte + * character set other than UTF-8, we can assume here that + * there will be at most one output byte per input wchar_t. + * (But also we must allow space for the trailing NUL that + * wc_to_mb will write.) + */ + char *bufptr = strbuf_append(buf, len + 1); + int rv; + rv = wc_to_mb(term->ucsdata->line_codepage, 0, widebuf, len, + bufptr, len + 1, NULL, term->ucsdata); + buf->len = rv < 0 ? 0 : rv; + } + + return buf; +} + +static strbuf *term_input_data_from_charset( + Terminal *term, int codepage, const char *str, int len) +{ + strbuf *buf; + + if (codepage < 0) { + buf = strbuf_new(); + put_data(buf, str, len); + } else { + int widesize = len * 2; /* allow for UTF-16 surrogates */ + wchar_t *widebuf = snewn(widesize, wchar_t); + int widelen = mb_to_wc(codepage, 0, str, len, widebuf, widesize); + buf = term_input_data_from_unicode(term, widebuf, widelen); + sfree(widebuf); + } + + return buf; +} + +static inline void term_bracketed_paste_start(Terminal *term) +{ + ptrlen seq = PTRLEN_LITERAL("\033[200~"); + if (term->ldisc) + ldisc_send(term->ldisc, seq.ptr, seq.len, false); + term->bracketed_paste_active = true; +} + +static inline void term_bracketed_paste_stop(Terminal *term) +{ + if (!term->bracketed_paste_active) + return; + + ptrlen seq = PTRLEN_LITERAL("\033[201~"); + if (term->ldisc) + ldisc_send(term->ldisc, seq.ptr, seq.len, false); + term->bracketed_paste_active = false; +} + +static inline void term_keyinput_internal( + Terminal *term, const void *buf, int len, bool interactive) +{ + if (term->srm_echo) { + /* + * Implement the terminal-level local echo behaviour that + * ECMA-48 specifies when terminal mode 12 is configured off + * (ESC[12l). In this mode, data input to the terminal via the + * keyboard is also added to the output buffer. But this + * doesn't apply to escape sequences generated as session + * input _within_ the terminal, e.g. in response to terminal + * query sequences, or the bracketing sequences of bracketed + * paste mode. Those will be sent directly via + * ldisc_send(term->ldisc, ...) and won't go through this + * function. + */ + + /* Mimic the special case of negative length in ldisc_send */ + int true_len = len >= 0 ? len : strlen(buf); + + bufchain_add(&term->inbuf, buf, true_len); + term_added_data(term); + } + term_bracketed_paste_stop(term); + if (term->ldisc) + ldisc_send(term->ldisc, buf, len, interactive); + term_seen_key_event(term); +} + unsigned long term_translate( Terminal *term, struct term_utf8_decode *utf8, unsigned char c) { @@ -3226,8 +3343,11 @@ static void term_out(Terminal *term) */ compatibility(ANSIMIN); if (term->ldisc) { - lpage_send(term->ldisc, DEFAULT_CODEPAGE, - term->answerback, term->answerbacklen, false); + strbuf *buf = term_input_data_from_charset( + term, DEFAULT_CODEPAGE, + term->answerback, term->answerbacklen); + ldisc_send(term->ldisc, buf->s, buf->len, false); + strbuf_free(buf); } break; case '\007': /* BEL: Bell */ @@ -5058,7 +5178,7 @@ static termchar *term_bidi_line(Terminal *term, struct termline *ldata, int it; /* Do Arabic shaping and bidi. */ - if (!term->bidi || !term->arabicshaping || + if (!term->no_bidi || !term->no_arabicshaping || (ldata->trusted && term->cols > TRUST_SIGIL_WIDTH)) { if (!term_bidi_cache_hit(term, scr_y, ldata->chars, term->cols, @@ -5127,16 +5247,16 @@ static termchar *term_bidi_line(Terminal *term, struct termline *ldata, nbc++; } - if(!term->bidi) + if(!term->no_bidi) do_bidi(term->wcFrom, nbc); - /* this is saved iff done from inside the shaping */ - if(!term->bidi && term->arabicshaping) - for(it=0; itwcTo[it] = term->wcFrom[it]; - - if(!term->arabicshaping) + if(!term->no_arabicshaping) { do_shape(term->wcFrom, term->wcTo, nbc); + } else { + /* If we're not calling do_shape, we must copy the + * data into wcTo anyway, unchanged */ + memcpy(term->wcTo, term->wcFrom, nbc * sizeof(*term->wcTo)); + } if (term->ltemp_size < ldata->size) { term->ltemp_size = ldata->size; @@ -6230,9 +6350,12 @@ static void term_paste_callback(void *vterm) if (term->paste_buffer[term->paste_pos + n++] == '\015') break; } - if (term->ldisc) - luni_send(term->ldisc, term->paste_buffer + term->paste_pos, n, - false); + if (term->ldisc) { + strbuf *buf = term_input_data_from_unicode( + term, term->paste_buffer + term->paste_pos, n); + term_keyinput_internal(term, buf->s, buf->len, false); + strbuf_free(buf); + } term->paste_pos += n; if (term->paste_pos < term->paste_len) { @@ -6240,6 +6363,7 @@ static void term_paste_callback(void *vterm) return; } } + term_bracketed_paste_stop(term); sfree(term->paste_buffer); term->paste_buffer = NULL; term->paste_len = 0; @@ -6275,10 +6399,8 @@ void term_do_paste(Terminal *term, const wchar_t *data, int len) term->paste_pos = term->paste_len = 0; term->paste_buffer = snewn(len + 12, wchar_t); - if (term->bracketed_paste) { - memcpy(term->paste_buffer, L"\033[200~", 6 * sizeof(wchar_t)); - term->paste_len += 6; - } + if (term->bracketed_paste) + term_bracketed_paste_start(term); p = data; while (p < data + len) { @@ -6327,19 +6449,18 @@ void term_do_paste(Terminal *term, const wchar_t *data, int len) term->paste_buffer[term->paste_len++] = wc; } - if (term->bracketed_paste) { - memcpy(term->paste_buffer + term->paste_len, - L"\033[201~", 6 * sizeof(wchar_t)); - term->paste_len += 6; - } - /* Assume a small paste will be OK in one go. */ if (term->paste_len < 256) { - if (term->ldisc) - luni_send(term->ldisc, term->paste_buffer, term->paste_len, false); + if (term->ldisc) { + strbuf *buf = term_input_data_from_unicode( + term, term->paste_buffer, term->paste_len); + term_keyinput_internal(term, buf->s, buf->len, false); + strbuf_free(buf); + } if (term->paste_buffer) sfree(term->paste_buffer); - term->paste_buffer = 0; + term_bracketed_paste_stop(term); + term->paste_buffer = NULL; term->paste_pos = term->paste_len = 0; } @@ -6836,20 +6957,42 @@ int format_numeric_keypad_key(char *buf, Terminal *term, char key, } } - if (p == buf && !app_keypad && key != 'G') { - /* Fallback: numeric keypad keys decode as their ASCII - * representation. */ - p += sprintf(p, "%c", key); - } - return p - buf; } +void term_keyinputw(Terminal *term, const wchar_t *widebuf, int len) +{ + strbuf *buf = term_input_data_from_unicode(term, widebuf, len); + if (buf->len) + term_keyinput_internal(term, buf->s, buf->len, true); + strbuf_free(buf); +} + +void term_keyinput(Terminal *term, int codepage, const void *str, int len) +{ + if (codepage < 0 || codepage == term->ucsdata->line_codepage) { + /* + * This text needs no translation, either because it's already + * in the right character set, or because we got the special + * codepage value -1 from our caller which means 'this data + * should be charset-agnostic, just send it raw' (for really + * simple things like control characters). + */ + term_keyinput_internal(term, str, len, true); + } else { + strbuf *buf = term_input_data_from_charset(term, codepage, str, len); + if (buf->len) + term_keyinput_internal(term, buf->s, buf->len, true); + strbuf_free(buf); + } +} + void term_nopaste(Terminal *term) { if (term->paste_len == 0) return; sfree(term->paste_buffer); + term_bracketed_paste_stop(term); term->paste_buffer = NULL; term->paste_len = 0; } @@ -6878,15 +7021,6 @@ void term_lost_clipboard_ownership(Terminal *term, int clipboard) term_out(term); } -bool term_ldisc(Terminal *term, int option) -{ - if (option == LD_ECHO) - return term->term_echoing; - if (option == LD_EDIT) - return term->term_editing; - return false; -} - static void term_added_data(Terminal *term) { if (!term->in_term_out) { diff --git a/terminal.h b/terminal.h index 0512687..23c91e1 100644 --- a/terminal.h +++ b/terminal.h @@ -123,8 +123,6 @@ struct terminal_tag { bool cblinker; /* When blinking is the cursor on ? */ bool tblinker; /* When the blinking text is on */ bool blink_is_real; /* Actually blink blinking text */ - bool term_echoing; /* Does terminal want local echo? */ - bool term_editing; /* Does terminal want local edit? */ int sco_acs, save_sco_acs; /* CSI 10,11,12m -> OEM charset */ bool vt52_bold; /* Force bold on non-bold colours */ bool utf; /* Are we in toggleable UTF-8 mode? */ @@ -148,7 +146,7 @@ struct terminal_tag { bool in_vbell; long vbell_end; bool app_cursor_keys, app_keypad_keys, vt52_mode; - bool repeat_off, cr_lf_return; + bool repeat_off, srm_echo, cr_lf_return; bool seen_disp_event; bool big_cursor; @@ -157,7 +155,7 @@ struct terminal_tag { bool urxvt_extended_mouse; int mouse_is_down; /* used while tracking mouse buttons */ - bool bracketed_paste; + bool bracketed_paste, bracketed_paste_active; int cset_attr[2]; @@ -297,13 +295,13 @@ struct terminal_tag { bool ansi_colour; char *answerback; int answerbacklen; - bool arabicshaping; + bool no_arabicshaping; int beep; bool bellovl; int bellovl_n; int bellovl_s; int bellovl_t; - bool bidi; + bool no_bidi; bool bksp_is_delete; bool blink_cur; bool blinktext; diff --git a/test/cryptsuite.py b/test/cryptsuite.py index 6f45d5c..20b8b7b 100644 --- a/test/cryptsuite.py +++ b/test/cryptsuite.py @@ -7,6 +7,7 @@ import contextlib import hashlib import binascii +import base64 try: from math import gcd except ImportError: @@ -15,6 +16,11 @@ from eccref import * from testcrypt import * +try: + base64decode = base64.decodebytes +except AttributeError: + base64decode = base64.decodestring + def nbits(n): # Mimic mp_get_nbits for ordinary Python integers. assert 0 <= n @@ -116,6 +122,12 @@ def queued_random_data(nbytes, seed): yield None random_clear() +@contextlib.contextmanager +def queued_specific_random_data(data): + random_queue(data) + yield None + random_clear() + def hash_str(alg, message): h = ssh_hash_new(alg) ssh_hash_update(h, message) @@ -986,13 +998,13 @@ def testCRC32(self): for prior in test_prior_values: prior_shifted = shift8(prior) - for i in range(256): - exp = shift8(i) ^ prior_shifted - self.assertEqual(crc32_update(prior, struct.pack("B", i)), exp) + for i in range(256): + exp = shift8(i) ^ prior_shifted + self.assertEqual(crc32_update(prior, struct.pack("B", i)), exp) - # Check linearity of the _reference_ implementation, while - # we're at it! - self.assertEqual(shift8(i ^ prior), exp) + # Check linearity of the _reference_ implementation, while + # we're at it! + self.assertEqual(shift8(i ^ prior), exp) def testCRCDA(self): def pattern(badblk, otherblks, pat): @@ -1264,6 +1276,161 @@ def testDSA(self): self.assertFalse(ssh_key_verify(pubkey, badsig0, "hello, again")) self.assertFalse(ssh_key_verify(pubkey, badsigq, "hello, again")) + def testRSAVerify(self): + def blobs(n, e, d, p, q, iqmp): + pubblob = ssh_string(b"ssh-rsa") + ssh2_mpint(e) + ssh2_mpint(n) + privblob = (ssh2_mpint(d) + ssh2_mpint(p) + + ssh2_mpint(q) + ssh2_mpint(iqmp)) + return pubblob, privblob + + def failure_test(*args): + pubblob, privblob = blobs(*args) + key = ssh_key_new_priv('rsa', pubblob, privblob) + self.assertEqual(key, None) + + def success_test(*args): + pubblob, privblob = blobs(*args) + key = ssh_key_new_priv('rsa', pubblob, privblob) + self.assertNotEqual(key, None) + + # Parameters for a (trivially small) test key. + n = 0xb5d545a2f6423eabd55ffede53e21628d5d4491541482e10676d9d6f2783b9a5 + e = 0x25 + d = 0x6733db6a546ac99fcc21ba2b28b0c077156e8a705976205a955c6d9cef98f419 + p = 0xe30ebd7348bf10dca72b36f2724dafa7 + q = 0xcd02c87a7f7c08c4e9dc80c9b9bad5d3 + iqmp = 0x60a129b30db9227910efe1608976c513 + + # Check the test key makes sense unmodified. + success_test(n, e, d, p, q, iqmp) + + # Try modifying the values one by one to ensure they are + # rejected, except iqmp, which sshrsa.c regenerates anyway so + # it won't matter at all. + failure_test(n+1, e, d, p, q, iqmp) + failure_test(n, e+1, d, p, q, iqmp) + failure_test(n, e, d+1, p, q, iqmp) + failure_test(n, e, d, p+1, q, iqmp) + failure_test(n, e, d, p, q+1, iqmp) + success_test(n, e, d, p, q, iqmp+1) + + # The key should also be accepted with p,q reversed. (Again, + # iqmp gets regenerated, so it won't matter if that's wrong.) + success_test(n, e, d, q, p, iqmp) + + # Replace each of p and q with 0, and with 1. These should + # still fail validation (obviously), but the point is that the + # validator should also avoid trying to divide by zero in the + # process. + failure_test(n, e, d, 0, q, iqmp) + failure_test(n, e, d, p, 0, iqmp) + failure_test(n, e, d, 1, q, iqmp) + failure_test(n, e, d, p, 1, iqmp) + + def testKeyMethods(self): + # Exercise all the methods of the ssh_key trait on all key + # types, and ensure that they're consistent with each other. + # No particular test is done on the rightness of the + # signatures by any objective standard, only that the output + # from our signing method can be verified by the corresponding + # verification method. + # + # However, we do include the expected signature text in each + # case, which checks determinism in the sense of being + # independent of any random numbers, and also in the sense of + # tomorrow's change to the code not having accidentally + # changed the behaviour. + + test_message = b"Message to be signed by crypt.testKeyMethods\n" + + test_keys = [ + ('ed25519', 'AAAAC3NzaC1lZDI1NTE5AAAAIM7jupzef6CD0ps2JYxJp9IlwY49oorOseV5z5JFDFKn', 'AAAAIAf4/WRtypofgdNF2vbZOUFE1h4hvjw4tkGJZyOzI7c3', 255, b'0xf4d6e7f6f4479c23f0764ef43cea1711dbfe02aa2b5a32ff925c7c1fbf0f0db,0x27520c4592cf79e5b1ce8aa23d8ec125d2a7498c25369bd283a07fde9cbae3ce', [(0, 'AAAAC3NzaC1lZDI1NTE5AAAAQN73EqfyA4WneqDhgZ98TlRj9V5Wg8zCrMxTLJN1UtyfAnPUJDtfG/U0vOsP8PrnQxd41DDDnxrAXuqJz8rOagc=')]), + ('p256', 'AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBHkYQ0sQoq5LbJI1VMWhw3bV43TSYi3WVpqIgKcBKK91TcFFlAMZgceOHQ0xAFYcSczIttLvFu+xkcLXrRd4N7Q=', 'AAAAIQCV/1VqiCsHZm/n+bq7lHEHlyy7KFgZBEbzqYaWtbx48Q==', 256, b'nistp256,0x7918434b10a2ae4b6c923554c5a1c376d5e374d2622dd6569a8880a70128af75,0x4dc14594031981c78e1d0d3100561c49ccc8b6d2ef16efb191c2d7ad177837b4', [(0, 'AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAABIAAAAIAryzHDGi/TcCnbdxZkIYR5EGR6SNYXr/HlQRF8le+/IAAAAIERfzn6eHuBbqWIop2qL8S7DWRB3lenN1iyL10xYQPKw')]), + ('p384', 'AAAAE2VjZHNhLXNoYTItbmlzdHAzODQAAAAIbmlzdHAzODQAAABhBMYK8PUtfAlJwKaBTIGEuCzH0vqOMa4UbcjrBbTbkGVSUnfo+nuC80NCdj9JJMs1jvfF8GzKLc5z8H3nZyM741/BUFjV7rEHsQFDek4KyWvKkEgKiTlZid19VukNo1q2Hg==', 'AAAAMGsfTmdB4zHdbiQ2euTSdzM6UKEOnrVjMAWwHEYvmG5qUOcBnn62fJDRJy67L+QGdg==', 384, b'nistp384,0xc60af0f52d7c0949c0a6814c8184b82cc7d2fa8e31ae146dc8eb05b4db9065525277e8fa7b82f34342763f4924cb358e,0xf7c5f06cca2dce73f07de767233be35fc15058d5eeb107b101437a4e0ac96bca90480a89395989dd7d56e90da35ab61e', [(0, 'AAAAE2VjZHNhLXNoYTItbmlzdHAzODQAAABpAAAAMDmHrtXCADzLvkkWG/duBAHlf6B1mVvdt6F0uzXfsf8Yub8WXNUNVnYq6ovrWPzLggAAADEA9izzwoUuFcXYRJeKcRLZEGMmSDDPzUZb7oZR0UgD1jsMQXs8UfpO31Qur/FDSCRK')]), + ('p521', 'AAAAE2VjZHNhLXNoYTItbmlzdHA1MjEAAAAIbmlzdHA1MjEAAACFBAFrGthlKM152vu2Ghk+R7iO9/M6e+hTehNZ6+FBwof4HPkPB2/HHXj5+w5ynWyUrWiX5TI2riuJEIrJErcRH5LglADnJDX2w4yrKZ+wDHSz9lwh9p2F+B5R952es6gX3RJRkGA+qhKpKup8gKx78RMbleX8wgRtIu+4YMUnKb1edREiRg==', 'AAAAQgFh7VNJFUljWhhyAEiL0z+UPs/QggcMTd3Vv2aKDeBdCRl5di8r+BMm39L7bRzxRMEtW5NSKlDtE8MFEGdIE9khsw==', 521, b'nistp521,0x16b1ad86528cd79dafbb61a193e47b88ef7f33a7be8537a1359ebe141c287f81cf90f076fc71d78f9fb0e729d6c94ad6897e53236ae2b89108ac912b7111f92e094,0xe72435f6c38cab299fb00c74b3f65c21f69d85f81e51f79d9eb3a817dd125190603eaa12a92aea7c80ac7bf1131b95e5fcc2046d22efb860c52729bd5e75112246', [(0, 'AAAAE2VjZHNhLXNoYTItbmlzdHA1MjEAAACMAAAAQgCLgvftvwM3CUaigrW0yzmCHoYjC6GLtO+6S91itqpgMEtWPNlaTZH6QQqkgscijWdXx98dDkQao/gcAKVmOZKPXgAAAEIB1PIrsDF1y6poJ/czqujB7NSUWt31v+c2t6UA8m2gTA1ARuVJ9XBGLMdceOTB00Hi9psC2RYFLpaWREOGCeDa6ow=')]), + ('dsa', 'AAAAB3NzaC1kc3MAAABhAJyWZzjVddGdyc5JPu/WPrC07vKRAmlqO6TUi49ah96iRcM7/D1aRMVAdYBepQ2mf1fsQTmvoC9KgQa79nN3kHhz0voQBKOuKI1ZAodfVOgpP4xmcXgjaA73Vjz22n4newAAABUA6l7/vIveaiA33YYv+SKcKLQaA8cAAABgbErc8QLw/WDz7mhVRZrU+9x3Tfs68j3eW+B/d7Rz1ZCqMYDk7r/F8dlBdQlYhpQvhuSBgzoFa0+qPvSSxPmutgb94wNqhHlVIUb9ZOJNloNr2lXiPP//Wu51TxXAEvAAAAAAYQCcQ9mufXtZa5RyfwT4NuLivdsidP4HRoLXdlnppfFAbNdbhxE0Us8WZt+a/443bwKnYxgif8dgxv5UROnWTngWu0jbJHpaDcTc9lRyTeSUiZZK312s/Sl7qDk3/Du7RUI=', 'AAAAFGx3ft7G8AQzFsjhle7PWardUXh3', 768, b'0x9c966738d575d19dc9ce493eefd63eb0b4eef29102696a3ba4d48b8f5a87dea245c33bfc3d5a44c54075805ea50da67f57ec4139afa02f4a8106bbf67377907873d2fa1004a3ae288d5902875f54e8293f8c66717823680ef7563cf6da7e277b,0xea5effbc8bde6a2037dd862ff9229c28b41a03c7,0x6c4adcf102f0fd60f3ee6855459ad4fbdc774dfb3af23dde5be07f77b473d590aa3180e4eebfc5f1d94175095886942f86e481833a056b4faa3ef492c4f9aeb606fde3036a8479552146fd64e24d96836bda55e23cffff5aee754f15c012f000,0x9c43d9ae7d7b596b94727f04f836e2e2bddb2274fe074682d77659e9a5f1406cd75b87113452cf1666df9aff8e376f02a76318227fc760c6fe5444e9d64e7816bb48db247a5a0dc4dcf654724de49489964adf5dacfd297ba83937fc3bbb4542', [(0, 'AAAAB3NzaC1kc3MAAAAo0T2t6dr8Qr5DK2B0ETwUa3BhxMLPjLY0ZtlOACmP/kUt3JgByLv+3g==')]), + ('rsa', 'AAAAB3NzaC1yc2EAAAABJQAAAGEA2ChX9+mQD/NULFkBrxLDI8d1PHgrInC2u11U4Grqu4oVzKvnFROo6DZeCu6sKhFJE5CnIL7evAthQ9hkXVHDhQ7xGVauzqyHGdIU4/pHRScAYWBv/PZOlNMrSoP/PP91', 'AAAAYCMNdgyGvWpez2EjMLSbQj0nQ3GW8jzvru3zdYwtA3hblNUU9QpWNxDmOMOApkwCzUgsdIPsBxctIeWT2h+v8sVOH+d66LCaNmNR0lp+dQ+iXM67hcGNuxJwRdMupD9ZbQAAADEA7XMrMAb4WuHaFafoTfGrf6Jhdy9Ozjqi1fStuld7Nj9JkoZluiL2dCwIrxqOjwU5AAAAMQDpC1gYiGVSPeDRILr2oxREtXWOsW+/ZZTfZNX7lvoufnp+qvwZPqvZnXQFHyZ8qB0AAAAwQE0wx8TPgcvRVEVv8Wt+o1NFlkJZayWD5hqpe/8AqUMZbqfg/aiso5mvecDLFgfV', 768, b'0x25,0xd82857f7e9900ff3542c5901af12c323c7753c782b2270b6bb5d54e06aeabb8a15ccabe71513a8e8365e0aeeac2a11491390a720bedebc0b6143d8645d51c3850ef11956aeceac8719d214e3fa4745270061606ffcf64e94d32b4a83ff3cff75', [(0, 'AAAAB3NzaC1yc2EAAABgrLSC4635RCsH1b3en58NqLsrH7PKRZyb3YmRasOyr8xIZMSlKZyxNg+kkn9OgBzbH9vChafzarfHyVwtJE2IMt3uwxTIWjwgwH19tc16k8YmNfDzujmB6OFOArmzKJgJ'), (2, 'AAAADHJzYS1zaGEyLTI1NgAAAGAJszr04BZlVBEdRLGOv1rTJwPiid/0I6/MycSH+noahvUH2wjrRhqDuv51F4nKYF5J9vBsEotTSrSF/cnLsliCdvVkEfmvhdcn/jx2LWF2OfjqETiYSc69Dde9UFmAPds='), (4, 'AAAADHJzYS1zaGEyLTUxMgAAAGBxfZ2m+WjvZ5YV5RFm0+w84CgHQ95EPndoAha0PCMc93AUHBmoHnezsJvEGuLovUm35w/0POmUNHI7HzM9PECwXrV0rO6N/HL/oFxJuDYmeqCpjMVmN8QXka+yxs2GEtA=')]), + ] + + for alg, pubb64, privb64, bits, cachestr, siglist in test_keys: + # Decode the blobs in the above test data. + pubblob = base64decode(pubb64.encode('ASCII')) + privblob = base64decode(privb64.encode('ASCII')) + + # Check the method that examines a public blob directly + # and returns an integer showing the key size. + self.assertEqual(ssh_key_public_bits(alg, pubblob), bits) + + # Make a public-only and a full ssh_key object. + pubkey = ssh_key_new_pub(alg, pubblob) + privkey = ssh_key_new_priv(alg, pubblob, privblob) + + # Test that they re-export the public and private key + # blobs unchanged. + self.assertEqual(ssh_key_public_blob(pubkey), pubblob) + self.assertEqual(ssh_key_public_blob(privkey), pubblob) + self.assertEqual(ssh_key_private_blob(privkey), privblob) + + # Round-trip through the OpenSSH wire encoding used by the + # agent protocol (and the newer OpenSSH key file format), + # and check the result still exports all the same blobs. + osshblob = ssh_key_openssh_blob(privkey) + privkey2 = ssh_key_new_priv_openssh(alg, osshblob) + self.assertEqual(ssh_key_public_blob(privkey2), pubblob) + self.assertEqual(ssh_key_private_blob(privkey2), privblob) + self.assertEqual(ssh_key_openssh_blob(privkey2), osshblob) + + # Test that the string description used in the host key + # cache is as expected. + for key in [pubkey, privkey, privkey2]: + self.assertEqual(ssh_key_cache_str(key), cachestr) + + # Now test signatures, separately for each provided flags + # value. + for flags, sigb64 in siglist: + # Decode the signature blob from the test data. + sigblob = base64decode(sigb64.encode('ASCII')) + + # Sign our test message, and check it produces exactly + # the expected signature blob. + # + # We do this with both the original private key and + # the one we round-tripped through OpenSSH wire + # format, just in case that round trip made some kind + # of a mess that didn't show up in the re-extraction + # of the blobs. + for key in [privkey, privkey2]: + self.assertEqual(ssh_key_sign( + key, test_message, flags), sigblob) + + if flags != 0: + # Currently we only support _generating_ + # signatures with flags != 0, not verifying them. + continue + + # Check the signature verifies successfully, with all + # three of the key objects we have. + for key in [pubkey, privkey, privkey2]: + self.assertTrue(ssh_key_verify(key, sigblob, test_message)) + + # A crude check that at least _something_ doesn't + # verify successfully: flip a bit of the signature + # and expect it to fail. + # + # We do this twice, at the 1/3 and 2/3 points along + # the signature's length, so that in the case of + # signatures in two parts (DSA-like) we try perturbing + # both parts. Other than that, we don't do much to + # make this a rigorous cryptographic test. + for n, d in [(1,3),(2,3)]: + sigbytes = list(bytevals(sigblob)) + bit = 8 * len(sigbytes) * n // d + sigbytes[bit // 8] ^= 1 << (bit % 8) + badsig = valbytes(sigbytes) + for key in [pubkey, privkey, privkey2]: + self.assertFalse(ssh_key_verify( + key, badsig, test_message)) + class standard_test_vectors(MyTestBase): def testAES(self): def vector(cipher, key, plaintext, ciphertext): @@ -1740,6 +1907,48 @@ def vector(privkey, pubkey, message, signature): signature = unhex(words[3])[:64] vector(privkey, pubkey, message, signature) + def testMontgomeryKex(self): + # Unidirectional tests, consisting of an input random number + # string and peer public value, giving the expected output + # shared key. Source: RFC 7748 section 5.2. + rfc7748s5_2 = [ + ('a546e36bf0527c9d3b16154b82465edd62144c0ac1fc5a18506a2244ba449ac4', + 'e6db6867583030db3594c1a424b15f7c726624ec26b3353b10a903a6d0ab1c4c', + 0xc3da55379de9c6908e94ea4df28d084f32eccf03491c71f754b4075577a28552), + ('4b66e9d4d1b4673c5ad22691957d6af5c11b6421e0ea01d42ca4169e7918ba0d', + 'e5210f12786811d3f4b7959d0538ae2c31dbe7106fc03c3efc4cd549c715a493', + 0x95cbde9476e8907d7aade45cb4b873f88b595a68799fa152e6f8f7647aac7957), + ] + + for priv, pub, expected in rfc7748s5_2: + with queued_specific_random_data(unhex(priv)): + ecdh = ssh_ecdhkex_newkey('curve25519') + key = ssh_ecdhkex_getkey(ecdh, unhex(pub)) + self.assertEqual(int(key), expected) + + # Bidirectional tests, consisting of the input random number + # strings for both parties, and the expected public values and + # shared key. Source: RFC 7748 section 6.1. + rfc7748s6_1 = [ + ('77076d0a7318a57d3c16c17251b26645df4c2f87ebc0992ab177fba51db92c2a', + '8520f0098930a754748b7ddcb43ef75a0dbf3a0d26381af4eba4a98eaa9b4e6a', + '5dab087e624a8a4b79e17f8b83800ee66f3bb1292618b6fd1c2f8b27ff88e0eb', + 'de9edb7d7b7dc1b4d35b61c2ece435373f8343c85b78674dadfc7e146f882b4f', + 0x4a5d9d5ba4ce2de1728e3bf480350f25e07e21c947d19e3376f09b3c1e161742), + ] + + for apriv, apub, bpriv, bpub, expected in rfc7748s6_1: + with queued_specific_random_data(unhex(apriv)): + alice = ssh_ecdhkex_newkey('curve25519') + with queued_specific_random_data(unhex(bpriv)): + bob = ssh_ecdhkex_newkey('curve25519') + self.assertEqualBin(ssh_ecdhkex_getpublic(alice), unhex(apub)) + self.assertEqualBin(ssh_ecdhkex_getpublic(bob), unhex(bpub)) + akey = ssh_ecdhkex_getkey(alice, unhex(bpub)) + bkey = ssh_ecdhkex_getkey(bob, unhex(apub)) + self.assertEqual(int(akey), expected) + self.assertEqual(int(bkey), expected) + def testCRC32(self): self.assertEqual(crc32_rfc1662("123456789"), 0xCBF43926) self.assertEqual(crc32_ssh1("123456789"), 0x2DFD2D88) @@ -1785,10 +1994,17 @@ def testCRC32(self): self.assertEqual(crc32_rfc1662(vec), 0x2144DF1C) if __name__ == "__main__": - try: - unittest.main() - finally: - # On exit, make sure we check the subprocess's return status, - # so that if Leak Sanitiser detected any memory leaks, the - # test will turn into a failure at the last minute. - childprocess.check_return_status() + # Run the tests, suppressing automatic sys.exit and collecting the + # unittest.TestProgram instance returned by unittest.main instead. + testprogram = unittest.main(exit=False) + + # If any test failed, just exit with failure status. + if not testprogram.result.wasSuccessful(): + childprocess.wait_for_exit() + sys.exit(1) + + # But if no tests failed, we have one last check to do: look at + # the subprocess's return status, so that if Leak Sanitiser + # detected any memory leaks, the success return status will turn + # into a failure at the last minute. + childprocess.check_return_status() diff --git a/test/sclog/CMakeLists.txt b/test/sclog/CMakeLists.txt new file mode 100644 index 0000000..6ac0ddf --- /dev/null +++ b/test/sclog/CMakeLists.txt @@ -0,0 +1,16 @@ +# CMake script for the 'sclog' DynamoRIO instrumentation system that +# goes with the PuTTY test binary 'testsc'. For build instructions see +# the comment at the top of testsc.c. + +cmake_minimum_required(VERSION 3.5) + +find_package(DynamoRIO) +if (NOT DynamoRIO_FOUND) + message(FATAL_ERROR "DynamoRIO not found") +endif() + +add_library(sclog SHARED sclog.c) +configure_DynamoRIO_client(sclog) +foreach(extension drmgr drsyms drreg drutil drwrap) + use_DynamoRIO_extension(sclog ${extension}) +endforeach() diff --git a/test/testcrypt.py b/test/testcrypt.py index 95d311d..42da9d8 100644 --- a/test/testcrypt.py +++ b/test/testcrypt.py @@ -22,10 +22,15 @@ def valbytes(b): b = list(b) return struct.pack("{:d}B".format(len(b)), *b) +class ChildProcessFailure(Exception): + pass + class ChildProcess(object): def __init__(self): self.sp = None self.debug = None + self.exitstatus = None + self.exception = None dbg = os.environ.get("PUTTY_TESTCRYPT_DEBUG") if dbg is not None: @@ -46,12 +51,21 @@ def start(self): self.sp = subprocess.Popen( cmd, shell=shell, stdin=subprocess.PIPE, stdout=subprocess.PIPE) def write_line(self, line): + if self.exception is not None: + # Re-raise our fatal-error exception, if it previously + # occurred in a context where it couldn't be propagated (a + # __del__ method). + raise self.exception if self.debug is not None: self.debug.write("send: {}\n".format(line)) self.sp.stdin.write(line + b"\n") self.sp.stdin.flush() def read_line(self): - line = self.sp.stdout.readline().rstrip(b"\r\n") + line = self.sp.stdout.readline() + if len(line) == 0: + self.exception = ChildProcessFailure("received EOF from testcrypt") + raise self.exception + line = line.rstrip(b"\r\n") if self.debug is not None: self.debug.write("recv: {}\n".format(line)) return line @@ -62,12 +76,16 @@ def funcall(self, cmd, args): unicode_to_bytes(arg) for arg in args)) argcount = int(self.read_line()) return [self.read_line() for arg in range(argcount)] + def wait_for_exit(self): + if self.sp is not None: + self.sp.stdin.close() + self.exitstatus = self.sp.wait() + self.sp = None def check_return_status(self): - assert self.sp is not None - self.sp.stdin.close() - status = self.sp.wait() - if status != 0: - raise Exception("testcrypt returned exit status {}".format(status)) + self.wait_for_exit() + if self.exitstatus is not None and self.exitstatus != 0: + raise ChildProcessFailure("testcrypt returned exit status {}" + .format(self.exitstatus)) childprocess = ChildProcess() @@ -81,7 +99,22 @@ def __repr__(self): return "Value({!r}, {!r})".format(self.typename, self.ident) def __del__(self): if self.ident is not None: - childprocess.funcall("free", [self.ident]) + try: + childprocess.funcall("free", [self.ident]) + except ChildProcessFailure: + # If we see this exception now, we can't do anything + # about it, because exceptions don't propagate out of + # __del__ methods. Squelch it to prevent the annoying + # runtime warning from Python, and the + # 'self.exception' mechanism in the ChildProcess class + # will raise it again at the next opportunity. + # + # (This covers both the case where testcrypt crashes + # _during_ one of these free operations, and the + # silencing of cascade failures when we try to send a + # "free" command to testcrypt after it had already + # crashed for some other reason.) + pass def __long__(self): if self.typename != "val_mpint": raise TypeError("testcrypt values of types other than mpint" diff --git a/testcrypt.c b/testcrypt.c index 8071c01..b8d18ae 100644 --- a/testcrypt.c +++ b/testcrypt.c @@ -503,29 +503,19 @@ static void return_val_string_asciz(strbuf *out, char *s) return_val_string(out, sb); } -static void return_opt_val_string_asciz(strbuf *out, char *s) -{ - if (!s) - strbuf_catf(out, "NULL\n"); - else - return_val_string_asciz(out, s); -} - -static void return_opt_val_cipher(strbuf *out, ssh_cipher *c) -{ - if (!c) - strbuf_catf(out, "NULL\n"); - else - return_val_cipher(out, c); -} +#define NULLABLE_RETURN_WRAPPER(type_name, c_type) \ + static void return_opt_##type_name(strbuf *out, c_type ptr) \ + { \ + if (!ptr) \ + strbuf_catf(out, "NULL\n"); \ + else \ + return_##type_name(out, ptr); \ + } -static void return_opt_val_hash(strbuf *out, ssh_hash *h) -{ - if (!h) - strbuf_catf(out, "NULL\n"); - else - return_val_hash(out, h); -} +NULLABLE_RETURN_WRAPPER(val_string_asciz, char *) +NULLABLE_RETURN_WRAPPER(val_cipher, ssh_cipher *) +NULLABLE_RETURN_WRAPPER(val_hash, ssh_hash *) +NULLABLE_RETURN_WRAPPER(val_key, ssh_key *) static void handle_hello(BinarySource *in, strbuf *out) { diff --git a/testcrypt.h b/testcrypt.h index 620ab4b..5f1fd61 100644 --- a/testcrypt.h +++ b/testcrypt.h @@ -145,8 +145,8 @@ FUNC1(val_string, ssh2_mac_genresult, val_mac) * returning a string. */ FUNC2(val_key, ssh_key_new_pub, keyalg, val_string_ptrlen) -FUNC3(val_key, ssh_key_new_priv, keyalg, val_string_ptrlen, val_string_ptrlen) -FUNC2(val_key, ssh_key_new_priv_openssh, keyalg, val_string_binarysource) +FUNC3(opt_val_key, ssh_key_new_priv, keyalg, val_string_ptrlen, val_string_ptrlen) +FUNC2(opt_val_key, ssh_key_new_priv_openssh, keyalg, val_string_binarysource) FUNC2(opt_val_string_asciz, ssh_key_invalid, val_key, uint) FUNC4(void, ssh_key_sign, val_key, val_string_ptrlen, uint, out_val_string_binarysink) FUNC3(boolean, ssh_key_verify, val_key, val_string_ptrlen, val_string_ptrlen) diff --git a/testsc.c b/testsc.c index ab60d9a..2005a21 100644 --- a/testsc.c +++ b/testsc.c @@ -334,6 +334,7 @@ static void test_mp_get_nbits(void) log_end(); } mp_free(prev); + mp_free(z); } static void test_mp_from_decimal(void) @@ -386,6 +387,7 @@ static void test_mp_string_format(char *(*mp_format)(mp_int *x)) log_end(); sfree(formatted); } + mp_free(z); } static void test_mp_get_decimal(void) @@ -589,6 +591,10 @@ static void test_mp_modarith( mp_free(out); } + + mp_free(base); + mp_free(exponent); + mp_free(modulus); } static void test_mp_modadd(void) @@ -625,6 +631,8 @@ static void test_mp_invert_mod_2to(void) mp_free(out); } + + mp_free(x); } static void test_mp_modsqrt(void) @@ -647,7 +655,8 @@ static void test_mp_modsqrt(void) /* Do one initial call to cause the lazily initialised sub-context * to be set up. This will take a while, but it can't be helped. */ - mp_modsqrt(sc, x, &success); + mp_int *unwanted = mp_modsqrt(sc, x, &success); + mp_free(unwanted); for (size_t i = 0; i < looplimit(8); i++) { mp_random_bits_into(x, bits - 1); @@ -658,6 +667,7 @@ static void test_mp_modsqrt(void) } mp_free(x); + modsqrt_free(sc); } static WeierstrassCurve *wcurve(void) @@ -801,6 +811,7 @@ static void test_ecc_weierstrass_multiply(void) } ecc_weierstrass_point_free(a); ecc_weierstrass_curve_free(wc); + mp_free(exponent); } static void test_ecc_weierstrass_is_identity(void) @@ -999,6 +1010,7 @@ static void test_ecc_montgomery_multiply(void) } ecc_montgomery_point_free(a); ecc_montgomery_curve_free(wc); + mp_free(exponent); } static void test_ecc_montgomery_get_affine(void) @@ -1131,6 +1143,7 @@ static void test_ecc_edwards_multiply(void) } ecc_edwards_point_free(a); ecc_edwards_curve_free(ec); + mp_free(exponent); } static void test_ecc_edwards_eq(void) @@ -1302,9 +1315,9 @@ static void test_mac(const ssh2_macalg *malg) return; } - uint8_t *mkey = malg ? snewn(malg->keylen, uint8_t) : NULL; + uint8_t *mkey = snewn(malg->keylen, uint8_t); size_t datalen = 256; - size_t maclen = malg ? malg->len : 0; + size_t maclen = malg->len; uint8_t *data = snewn(datalen + maclen, uint8_t); /* Preliminarily key the MAC, to avoid the divergence of control diff --git a/unix/Makefile.gtk b/unix/Makefile.gtk index 007aebe..d56c0c6 100644 --- a/unix/Makefile.gtk +++ b/unix/Makefile.gtk @@ -145,30 +145,29 @@ cgtest: cgtest.o conf.o ecc.o import.o marshal.o memory.o misc.o mpint.o \ sshmd5.o sshprime.o sshprng.o sshpubk.o sshrand.o sshrsa.o \ sshrsag.o sshsh256.o sshsh512.o sshsha.o stripctrl.o time.o \ tree234.o utils.o uxcons.o uxgen.o uxmisc.o uxnogtk.o \ - uxnoise.o uxpoll.o uxstore.o version.o wcwidth.o + uxnoise.o uxpoll.o uxstore.o uxutils.o version.o wcwidth.o $(CC) -o $@ cgtest.o conf.o ecc.o import.o marshal.o memory.o misc.o \ mpint.o notiming.o sshaes.o sshauxcrypt.o sshbcrypt.o \ sshblowf.o sshdes.o sshdss.o sshdssg.o sshecc.o sshecdsag.o \ sshhmac.o sshmd5.o sshprime.o sshprng.o sshpubk.o sshrand.o \ sshrsa.o sshrsag.o sshsh256.o sshsh512.o sshsha.o \ stripctrl.o time.o tree234.o utils.o uxcons.o uxgen.o \ - uxmisc.o uxnogtk.o uxnoise.o uxpoll.o uxstore.o version.o \ - wcwidth.o $(ULDFLAGS) + uxmisc.o uxnogtk.o uxnoise.o uxpoll.o uxstore.o uxutils.o \ + version.o wcwidth.o $(ULDFLAGS) fuzzterm: be_none.o callback.o conf.o config.o dialog.o fromucs.o fuzzterm.o \ - ldiscucs.o localenc.o logging.o macenc.o marshal.o memory.o \ + localenc.o logging.o macenc.o marshal.o memory.o mimeenc.o \ + minibidi.o misc.o miscucs.o sbcs.o sbcsdat.o sercfg.o \ + settings.o slookup.o stripctrl.o terminal.o time.o timing.o \ + toucs.o tree234.o utf8.o utils.o uxcfg.o uxmisc.o uxnogtk.o \ + uxprint.o uxstore.o uxucs.o version.o wcwidth.o xenc.o + $(CC) -o $@ be_none.o callback.o conf.o config.o dialog.o fromucs.o \ + fuzzterm.o localenc.o logging.o macenc.o marshal.o memory.o \ mimeenc.o minibidi.o misc.o miscucs.o sbcs.o sbcsdat.o \ sercfg.o settings.o slookup.o stripctrl.o terminal.o time.o \ timing.o toucs.o tree234.o utf8.o utils.o uxcfg.o uxmisc.o \ uxnogtk.o uxprint.o uxstore.o uxucs.o version.o wcwidth.o \ - xenc.o - $(CC) -o $@ be_none.o callback.o conf.o config.o dialog.o fromucs.o \ - fuzzterm.o ldiscucs.o localenc.o logging.o macenc.o \ - marshal.o memory.o mimeenc.o minibidi.o misc.o miscucs.o \ - sbcs.o sbcsdat.o sercfg.o settings.o slookup.o stripctrl.o \ - terminal.o time.o timing.o toucs.o tree234.o utf8.o utils.o \ - uxcfg.o uxmisc.o uxnogtk.o uxprint.o uxstore.o uxucs.o \ - version.o wcwidth.o xenc.o $(ULDFLAGS) + xenc.o $(ULDFLAGS) osxlaunch: osxlaunch.o $(CC) -o $@ osxlaunch.o $(ULDFLAGS) @@ -177,22 +176,22 @@ pageant: aqsync.o be_misc.o be_none.o callback.o conf.o ecc.o errsock.o \ gtkask.o gtkmisc.o logging.o marshal.o memory.o misc.o \ mpint.o nocproxy.o nogss.o nullplug.o pageant.o proxy.o \ settings.o sshaes.o sshauxcrypt.o sshdes.o sshdss.o sshecc.o \ - sshhmac.o sshmd5.o sshpubk.o sshrsa.o sshsh256.o sshsh512.o \ - sshsha.o stripctrl.o time.o timing.o tree234.o utils.o \ - ux_x11.o uxagentc.o uxagentsock.o uxcons.o uxfdsock.o \ - uxmisc.o uxnet.o uxpeer.o uxpgnt.o uxpoll.o uxproxy.o \ - uxsel.o uxsignal.o uxstore.o uxutils.o version.o wcwidth.o \ - x11fwd.o + sshhmac.o sshmd5.o sshprng.o sshpubk.o sshrsa.o sshsh256.o \ + sshsh512.o sshsha.o stripctrl.o time.o timing.o tree234.o \ + utils.o ux_x11.o uxagentc.o uxagentsock.o uxcons.o \ + uxfdsock.o uxmisc.o uxnet.o uxnoise.o uxpeer.o uxpgnt.o \ + uxpoll.o uxproxy.o uxsel.o uxsignal.o uxstore.o uxutils.o \ + version.o wcwidth.o x11fwd.o $(CC) -o $@ aqsync.o be_misc.o be_none.o callback.o conf.o ecc.o \ errsock.o gtkask.o gtkmisc.o logging.o marshal.o memory.o \ misc.o mpint.o nocproxy.o nogss.o nullplug.o pageant.o \ proxy.o settings.o sshaes.o sshauxcrypt.o sshdes.o sshdss.o \ - sshecc.o sshhmac.o sshmd5.o sshpubk.o sshrsa.o sshsh256.o \ - sshsh512.o sshsha.o stripctrl.o time.o timing.o tree234.o \ - utils.o ux_x11.o uxagentc.o uxagentsock.o uxcons.o \ - uxfdsock.o uxmisc.o uxnet.o uxpeer.o uxpgnt.o uxpoll.o \ - uxproxy.o uxsel.o uxsignal.o uxstore.o uxutils.o version.o \ - wcwidth.o x11fwd.o $(XLDFLAGS) + sshecc.o sshhmac.o sshmd5.o sshprng.o sshpubk.o sshrsa.o \ + sshsh256.o sshsh512.o sshsha.o stripctrl.o time.o timing.o \ + tree234.o utils.o ux_x11.o uxagentc.o uxagentsock.o uxcons.o \ + uxfdsock.o uxmisc.o uxnet.o uxnoise.o uxpeer.o uxpgnt.o \ + uxpoll.o uxproxy.o uxsel.o uxsignal.o uxstore.o uxutils.o \ + version.o wcwidth.o x11fwd.o $(XLDFLAGS) plink: agentf.o aqsync.o be_all_s.o be_misc.o callback.o cmdline.o conf.o \ cproxy.o ecc.o errsock.o ldisc.o logging.o mainchan.o \ @@ -236,8 +235,8 @@ plink: agentf.o aqsync.o be_all_s.o be_misc.o callback.o cmdline.o conf.o \ pscp: agentf.o aqsync.o be_misc.o be_ssh.o callback.o cmdline.o conf.o \ cproxy.o ecc.o errsock.o logging.o mainchan.o marshal.o \ memory.o misc.o mpint.o nullplug.o pgssapi.o pinger.o \ - portfwd.o proxy.o pscp.o settings.o sftp.o sftpcommon.o \ - ssh.o ssh1bpp.o ssh1censor.o ssh1connection.o \ + portfwd.o proxy.o pscp.o psftpcommon.o settings.o sftp.o \ + sftpcommon.o ssh.o ssh1bpp.o ssh1censor.o ssh1connection.o \ ssh1connection-client.o ssh1login.o ssh2bpp.o ssh2bpp-bare.o \ ssh2censor.o ssh2connection.o ssh2connection-client.o \ ssh2kex-client.o ssh2transhk.o ssh2transport.o \ @@ -253,8 +252,8 @@ pscp: agentf.o aqsync.o be_misc.o be_ssh.o callback.o cmdline.o conf.o \ $(CC) -o $@ agentf.o aqsync.o be_misc.o be_ssh.o callback.o \ cmdline.o conf.o cproxy.o ecc.o errsock.o logging.o \ mainchan.o marshal.o memory.o misc.o mpint.o nullplug.o \ - pgssapi.o pinger.o portfwd.o proxy.o pscp.o settings.o \ - sftp.o sftpcommon.o ssh.o ssh1bpp.o ssh1censor.o \ + pgssapi.o pinger.o portfwd.o proxy.o pscp.o psftpcommon.o \ + settings.o sftp.o sftpcommon.o ssh.o ssh1bpp.o ssh1censor.o \ ssh1connection.o ssh1connection-client.o ssh1login.o \ ssh2bpp.o ssh2bpp-bare.o ssh2censor.o ssh2connection.o \ ssh2connection-client.o ssh2kex-client.o ssh2transhk.o \ @@ -272,8 +271,8 @@ pscp: agentf.o aqsync.o be_misc.o be_ssh.o callback.o cmdline.o conf.o \ psftp: agentf.o aqsync.o be_misc.o be_ssh.o callback.o cmdline.o conf.o \ cproxy.o ecc.o errsock.o logging.o mainchan.o marshal.o \ memory.o misc.o mpint.o nullplug.o pgssapi.o pinger.o \ - portfwd.o proxy.o psftp.o settings.o sftp.o sftpcommon.o \ - ssh.o ssh1bpp.o ssh1censor.o ssh1connection.o \ + portfwd.o proxy.o psftp.o psftpcommon.o settings.o sftp.o \ + sftpcommon.o ssh.o ssh1bpp.o ssh1censor.o ssh1connection.o \ ssh1connection-client.o ssh1login.o ssh2bpp.o ssh2bpp-bare.o \ ssh2censor.o ssh2connection.o ssh2connection-client.o \ ssh2kex-client.o ssh2transhk.o ssh2transport.o \ @@ -289,8 +288,8 @@ psftp: agentf.o aqsync.o be_misc.o be_ssh.o callback.o cmdline.o conf.o \ $(CC) -o $@ agentf.o aqsync.o be_misc.o be_ssh.o callback.o \ cmdline.o conf.o cproxy.o ecc.o errsock.o logging.o \ mainchan.o marshal.o memory.o misc.o mpint.o nullplug.o \ - pgssapi.o pinger.o portfwd.o proxy.o psftp.o settings.o \ - sftp.o sftpcommon.o ssh.o ssh1bpp.o ssh1censor.o \ + pgssapi.o pinger.o portfwd.o proxy.o psftp.o psftpcommon.o \ + settings.o sftp.o sftpcommon.o ssh.o ssh1bpp.o ssh1censor.o \ ssh1connection.o ssh1connection-client.o ssh1login.o \ ssh2bpp.o ssh2bpp-bare.o ssh2censor.o ssh2connection.o \ ssh2connection-client.o ssh2kex-client.o ssh2transhk.o \ @@ -307,54 +306,54 @@ psftp: agentf.o aqsync.o be_misc.o be_ssh.o callback.o cmdline.o conf.o \ pterm: be_none.o callback.o cmdline.o conf.o config.o dialog.o fromucs.o \ gtkcfg.o gtkcols.o gtkcomm.o gtkdlg.o gtkfont.o gtkmain.o \ - gtkmisc.o gtkwin.o ldisc.o ldiscucs.o localenc.o logging.o \ + gtkmisc.o gtkwin.o ldisc.o localenc.o logging.o macenc.o \ + marshal.o memory.o mimeenc.o minibidi.o misc.o miscucs.o \ + nocproxy.o nogss.o sbcs.o sbcsdat.o sercfg.o sessprep.o \ + settings.o slookup.o stripctrl.o terminal.o time.o timing.o \ + toucs.o tree234.o utf8.o utils.o uxcfg.o uxmisc.o uxprint.o \ + uxpterm.o uxpty.o uxsel.o uxsignal.o uxstore.o uxucs.o \ + version.o wcwidth.o x11misc.o xenc.o xkeysym.o xpmptcfg.o \ + xpmpterm.o + $(CC) -o $@ be_none.o callback.o cmdline.o conf.o config.o dialog.o \ + fromucs.o gtkcfg.o gtkcols.o gtkcomm.o gtkdlg.o gtkfont.o \ + gtkmain.o gtkmisc.o gtkwin.o ldisc.o localenc.o logging.o \ macenc.o marshal.o memory.o mimeenc.o minibidi.o misc.o \ miscucs.o nocproxy.o nogss.o sbcs.o sbcsdat.o sercfg.o \ sessprep.o settings.o slookup.o stripctrl.o terminal.o \ time.o timing.o toucs.o tree234.o utf8.o utils.o uxcfg.o \ uxmisc.o uxprint.o uxpterm.o uxpty.o uxsel.o uxsignal.o \ uxstore.o uxucs.o version.o wcwidth.o x11misc.o xenc.o \ - xkeysym.o xpmptcfg.o xpmpterm.o - $(CC) -o $@ be_none.o callback.o cmdline.o conf.o config.o dialog.o \ - fromucs.o gtkcfg.o gtkcols.o gtkcomm.o gtkdlg.o gtkfont.o \ - gtkmain.o gtkmisc.o gtkwin.o ldisc.o ldiscucs.o localenc.o \ - logging.o macenc.o marshal.o memory.o mimeenc.o minibidi.o \ - misc.o miscucs.o nocproxy.o nogss.o sbcs.o sbcsdat.o \ - sercfg.o sessprep.o settings.o slookup.o stripctrl.o \ - terminal.o time.o timing.o toucs.o tree234.o utf8.o utils.o \ - uxcfg.o uxmisc.o uxprint.o uxpterm.o uxpty.o uxsel.o \ - uxsignal.o uxstore.o uxucs.o version.o wcwidth.o x11misc.o \ - xenc.o xkeysym.o xpmptcfg.o xpmpterm.o $(XLDFLAGS) + xkeysym.o xpmptcfg.o xpmpterm.o $(XLDFLAGS) ptermapp: be_none.o callback.o conf.o config.o dialog.o fromucs.o gtkapp.o \ gtkcfg.o gtkcols.o gtkcomm.o gtkdlg.o gtkfont.o gtkmisc.o \ - gtkwin.o ldisc.o ldiscucs.o localenc.o logging.o macenc.o \ + gtkwin.o ldisc.o localenc.o logging.o macenc.o marshal.o \ + memory.o mimeenc.o minibidi.o misc.o miscucs.o nocmdline.o \ + nocproxy.o nogss.o sbcs.o sbcsdat.o sercfg.o sessprep.o \ + settings.o slookup.o stripctrl.o terminal.o time.o timing.o \ + toucs.o tree234.o utf8.o utils.o uxcfg.o uxmisc.o uxprint.o \ + uxpterm.o uxpty.o uxsel.o uxsignal.o uxstore.o uxucs.o \ + version.o wcwidth.o x11misc.o xenc.o xkeysym.o xpmptcfg.o \ + xpmpterm.o + $(CC) -o $@ be_none.o callback.o conf.o config.o dialog.o fromucs.o \ + gtkapp.o gtkcfg.o gtkcols.o gtkcomm.o gtkdlg.o gtkfont.o \ + gtkmisc.o gtkwin.o ldisc.o localenc.o logging.o macenc.o \ marshal.o memory.o mimeenc.o minibidi.o misc.o miscucs.o \ nocmdline.o nocproxy.o nogss.o sbcs.o sbcsdat.o sercfg.o \ sessprep.o settings.o slookup.o stripctrl.o terminal.o \ time.o timing.o toucs.o tree234.o utf8.o utils.o uxcfg.o \ uxmisc.o uxprint.o uxpterm.o uxpty.o uxsel.o uxsignal.o \ uxstore.o uxucs.o version.o wcwidth.o x11misc.o xenc.o \ - xkeysym.o xpmptcfg.o xpmpterm.o - $(CC) -o $@ be_none.o callback.o conf.o config.o dialog.o fromucs.o \ - gtkapp.o gtkcfg.o gtkcols.o gtkcomm.o gtkdlg.o gtkfont.o \ - gtkmisc.o gtkwin.o ldisc.o ldiscucs.o localenc.o logging.o \ - macenc.o marshal.o memory.o mimeenc.o minibidi.o misc.o \ - miscucs.o nocmdline.o nocproxy.o nogss.o sbcs.o sbcsdat.o \ - sercfg.o sessprep.o settings.o slookup.o stripctrl.o \ - terminal.o time.o timing.o toucs.o tree234.o utf8.o utils.o \ - uxcfg.o uxmisc.o uxprint.o uxpterm.o uxpty.o uxsel.o \ - uxsignal.o uxstore.o uxucs.o version.o wcwidth.o x11misc.o \ - xenc.o xkeysym.o xpmptcfg.o xpmpterm.o $(XLDFLAGS) + xkeysym.o xpmptcfg.o xpmpterm.o $(XLDFLAGS) putty: agentf.o aqsync.o be_all_s.o be_misc.o callback.o cmdline.o conf.o \ config.o cproxy.o dialog.o ecc.o errsock.o fromucs.o \ gtkcfg.o gtkcols.o gtkcomm.o gtkdlg.o gtkfont.o gtkmain.o \ - gtkmisc.o gtkwin.o ldisc.o ldiscucs.o localenc.o logging.o \ - macenc.o mainchan.o marshal.o memory.o mimeenc.o minibidi.o \ - misc.o miscucs.o mpint.o nullplug.o pgssapi.o pinger.o \ - portfwd.o proxy.o raw.o rlogin.o sbcs.o sbcsdat.o sercfg.o \ - sessprep.o settings.o slookup.o ssh.o ssh1bpp.o ssh1censor.o \ + gtkmisc.o gtkwin.o ldisc.o localenc.o logging.o macenc.o \ + mainchan.o marshal.o memory.o mimeenc.o minibidi.o misc.o \ + miscucs.o mpint.o nullplug.o pgssapi.o pinger.o portfwd.o \ + proxy.o raw.o rlogin.o sbcs.o sbcsdat.o sercfg.o sessprep.o \ + settings.o slookup.o ssh.o ssh1bpp.o ssh1censor.o \ ssh1connection.o ssh1connection-client.o ssh1login.o \ ssh2bpp.o ssh2bpp-bare.o ssh2censor.o ssh2connection.o \ ssh2connection-client.o ssh2kex-client.o ssh2transhk.o \ @@ -373,19 +372,19 @@ putty: agentf.o aqsync.o be_all_s.o be_misc.o callback.o cmdline.o conf.o \ $(CC) -o $@ agentf.o aqsync.o be_all_s.o be_misc.o callback.o \ cmdline.o conf.o config.o cproxy.o dialog.o ecc.o errsock.o \ fromucs.o gtkcfg.o gtkcols.o gtkcomm.o gtkdlg.o gtkfont.o \ - gtkmain.o gtkmisc.o gtkwin.o ldisc.o ldiscucs.o localenc.o \ - logging.o macenc.o mainchan.o marshal.o memory.o mimeenc.o \ - minibidi.o misc.o miscucs.o mpint.o nullplug.o pgssapi.o \ - pinger.o portfwd.o proxy.o raw.o rlogin.o sbcs.o sbcsdat.o \ - sercfg.o sessprep.o settings.o slookup.o ssh.o ssh1bpp.o \ - ssh1censor.o ssh1connection.o ssh1connection-client.o \ - ssh1login.o ssh2bpp.o ssh2bpp-bare.o ssh2censor.o \ - ssh2connection.o ssh2connection-client.o ssh2kex-client.o \ - ssh2transhk.o ssh2transport.o ssh2userauth.o sshaes.o \ - ssharcf.o sshauxcrypt.o sshblowf.o sshccp.o sshcommon.o \ - sshcrc.o sshcrcda.o sshdes.o sshdh.o sshdss.o sshecc.o \ - sshgssc.o sshhmac.o sshmac.o sshmd5.o sshprng.o sshpubk.o \ - sshrand.o sshrsa.o sshsh256.o sshsh512.o sshsha.o sshshare.o \ + gtkmain.o gtkmisc.o gtkwin.o ldisc.o localenc.o logging.o \ + macenc.o mainchan.o marshal.o memory.o mimeenc.o minibidi.o \ + misc.o miscucs.o mpint.o nullplug.o pgssapi.o pinger.o \ + portfwd.o proxy.o raw.o rlogin.o sbcs.o sbcsdat.o sercfg.o \ + sessprep.o settings.o slookup.o ssh.o ssh1bpp.o ssh1censor.o \ + ssh1connection.o ssh1connection-client.o ssh1login.o \ + ssh2bpp.o ssh2bpp-bare.o ssh2censor.o ssh2connection.o \ + ssh2connection-client.o ssh2kex-client.o ssh2transhk.o \ + ssh2transport.o ssh2userauth.o sshaes.o ssharcf.o \ + sshauxcrypt.o sshblowf.o sshccp.o sshcommon.o sshcrc.o \ + sshcrcda.o sshdes.o sshdh.o sshdss.o sshecc.o sshgssc.o \ + sshhmac.o sshmac.o sshmd5.o sshprng.o sshpubk.o sshrand.o \ + sshrsa.o sshsh256.o sshsh512.o sshsha.o sshshare.o \ sshverstring.o sshzlib.o stripctrl.o telnet.o terminal.o \ time.o timing.o toucs.o tree234.o utf8.o utils.o ux_x11.o \ uxagentc.o uxcfg.o uxfdsock.o uxgss.o uxmisc.o uxnet.o \ @@ -397,11 +396,11 @@ putty: agentf.o aqsync.o be_all_s.o be_misc.o callback.o cmdline.o conf.o \ puttyapp: agentf.o aqsync.o be_all_s.o be_misc.o callback.o conf.o config.o \ cproxy.o dialog.o ecc.o errsock.o fromucs.o gtkapp.o \ gtkcfg.o gtkcols.o gtkcomm.o gtkdlg.o gtkfont.o gtkmisc.o \ - gtkwin.o ldisc.o ldiscucs.o localenc.o logging.o macenc.o \ - mainchan.o marshal.o memory.o mimeenc.o minibidi.o misc.o \ - miscucs.o mpint.o nocmdline.o nullplug.o pgssapi.o pinger.o \ - portfwd.o proxy.o raw.o rlogin.o sbcs.o sbcsdat.o sercfg.o \ - sessprep.o settings.o slookup.o ssh.o ssh1bpp.o ssh1censor.o \ + gtkwin.o ldisc.o localenc.o logging.o macenc.o mainchan.o \ + marshal.o memory.o mimeenc.o minibidi.o misc.o miscucs.o \ + mpint.o nocmdline.o nullplug.o pgssapi.o pinger.o portfwd.o \ + proxy.o raw.o rlogin.o sbcs.o sbcsdat.o sercfg.o sessprep.o \ + settings.o slookup.o ssh.o ssh1bpp.o ssh1censor.o \ ssh1connection.o ssh1connection-client.o ssh1login.o \ ssh2bpp.o ssh2bpp-bare.o ssh2censor.o ssh2connection.o \ ssh2connection-client.o ssh2kex-client.o ssh2transhk.o \ @@ -420,19 +419,19 @@ puttyapp: agentf.o aqsync.o be_all_s.o be_misc.o callback.o conf.o config.o \ $(CC) -o $@ agentf.o aqsync.o be_all_s.o be_misc.o callback.o conf.o \ config.o cproxy.o dialog.o ecc.o errsock.o fromucs.o \ gtkapp.o gtkcfg.o gtkcols.o gtkcomm.o gtkdlg.o gtkfont.o \ - gtkmisc.o gtkwin.o ldisc.o ldiscucs.o localenc.o logging.o \ - macenc.o mainchan.o marshal.o memory.o mimeenc.o minibidi.o \ - misc.o miscucs.o mpint.o nocmdline.o nullplug.o pgssapi.o \ - pinger.o portfwd.o proxy.o raw.o rlogin.o sbcs.o sbcsdat.o \ - sercfg.o sessprep.o settings.o slookup.o ssh.o ssh1bpp.o \ - ssh1censor.o ssh1connection.o ssh1connection-client.o \ - ssh1login.o ssh2bpp.o ssh2bpp-bare.o ssh2censor.o \ - ssh2connection.o ssh2connection-client.o ssh2kex-client.o \ - ssh2transhk.o ssh2transport.o ssh2userauth.o sshaes.o \ - ssharcf.o sshauxcrypt.o sshblowf.o sshccp.o sshcommon.o \ - sshcrc.o sshcrcda.o sshdes.o sshdh.o sshdss.o sshecc.o \ - sshgssc.o sshhmac.o sshmac.o sshmd5.o sshprng.o sshpubk.o \ - sshrand.o sshrsa.o sshsh256.o sshsh512.o sshsha.o sshshare.o \ + gtkmisc.o gtkwin.o ldisc.o localenc.o logging.o macenc.o \ + mainchan.o marshal.o memory.o mimeenc.o minibidi.o misc.o \ + miscucs.o mpint.o nocmdline.o nullplug.o pgssapi.o pinger.o \ + portfwd.o proxy.o raw.o rlogin.o sbcs.o sbcsdat.o sercfg.o \ + sessprep.o settings.o slookup.o ssh.o ssh1bpp.o ssh1censor.o \ + ssh1connection.o ssh1connection-client.o ssh1login.o \ + ssh2bpp.o ssh2bpp-bare.o ssh2censor.o ssh2connection.o \ + ssh2connection-client.o ssh2kex-client.o ssh2transhk.o \ + ssh2transport.o ssh2userauth.o sshaes.o ssharcf.o \ + sshauxcrypt.o sshblowf.o sshccp.o sshcommon.o sshcrc.o \ + sshcrcda.o sshdes.o sshdh.o sshdss.o sshecc.o sshgssc.o \ + sshhmac.o sshmac.o sshmd5.o sshprng.o sshpubk.o sshrand.o \ + sshrsa.o sshsh256.o sshsh512.o sshsha.o sshshare.o \ sshverstring.o sshzlib.o stripctrl.o telnet.o terminal.o \ time.o timing.o toucs.o tree234.o utf8.o utils.o ux_x11.o \ uxagentc.o uxcfg.o uxfdsock.o uxgss.o uxmisc.o uxnet.o \ @@ -447,40 +446,40 @@ puttygen: cmdgen.o conf.o ecc.o import.o marshal.o memory.o misc.o mpint.o \ sshmd5.o sshprime.o sshprng.o sshpubk.o sshrand.o sshrsa.o \ sshrsag.o sshsh256.o sshsh512.o sshsha.o stripctrl.o time.o \ tree234.o utils.o uxcons.o uxgen.o uxmisc.o uxnogtk.o \ - uxnoise.o uxpoll.o uxstore.o version.o wcwidth.o + uxnoise.o uxpoll.o uxstore.o uxutils.o version.o wcwidth.o $(CC) -o $@ cmdgen.o conf.o ecc.o import.o marshal.o memory.o misc.o \ mpint.o notiming.o sshaes.o sshauxcrypt.o sshbcrypt.o \ sshblowf.o sshdes.o sshdss.o sshdssg.o sshecc.o sshecdsag.o \ sshhmac.o sshmd5.o sshprime.o sshprng.o sshpubk.o sshrand.o \ sshrsa.o sshrsag.o sshsh256.o sshsh512.o sshsha.o \ stripctrl.o time.o tree234.o utils.o uxcons.o uxgen.o \ - uxmisc.o uxnogtk.o uxnoise.o uxpoll.o uxstore.o version.o \ - wcwidth.o $(ULDFLAGS) + uxmisc.o uxnogtk.o uxnoise.o uxpoll.o uxstore.o uxutils.o \ + version.o wcwidth.o $(ULDFLAGS) puttytel: be_misc.o be_nos_s.o callback.o cmdline.o conf.o config.o dialog.o \ errsock.o fromucs.o gtkcfg.o gtkcols.o gtkcomm.o gtkdlg.o \ - gtkfont.o gtkmain.o gtkmisc.o gtkwin.o ldisc.o ldiscucs.o \ - localenc.o logging.o macenc.o marshal.o memory.o mimeenc.o \ - minibidi.o misc.o miscucs.o nocproxy.o nogss.o pinger.o \ - proxy.o raw.o rlogin.o sbcs.o sbcsdat.o sercfg.o sessprep.o \ - settings.o slookup.o stripctrl.o telnet.o terminal.o time.o \ - timing.o toucs.o tree234.o utf8.o utils.o uxcfg.o uxfdsock.o \ - uxmisc.o uxnet.o uxpeer.o uxpoll.o uxprint.o uxproxy.o \ - uxputty.o uxsel.o uxser.o uxsignal.o uxstore.o uxucs.o \ - uxutils.o version.o wcwidth.o x11misc.o xenc.o xkeysym.o \ - xpmpucfg.o xpmputty.o + gtkfont.o gtkmain.o gtkmisc.o gtkwin.o ldisc.o localenc.o \ + logging.o macenc.o marshal.o memory.o mimeenc.o minibidi.o \ + misc.o miscucs.o nocproxy.o nogss.o pinger.o proxy.o raw.o \ + rlogin.o sbcs.o sbcsdat.o sercfg.o sessprep.o settings.o \ + slookup.o stripctrl.o telnet.o terminal.o time.o timing.o \ + toucs.o tree234.o utf8.o utils.o uxcfg.o uxfdsock.o uxmisc.o \ + uxnet.o uxpeer.o uxpoll.o uxprint.o uxproxy.o uxputty.o \ + uxsel.o uxser.o uxsignal.o uxstore.o uxucs.o uxutils.o \ + version.o wcwidth.o x11misc.o xenc.o xkeysym.o xpmpucfg.o \ + xpmputty.o $(CC) -o $@ be_misc.o be_nos_s.o callback.o cmdline.o conf.o \ config.o dialog.o errsock.o fromucs.o gtkcfg.o gtkcols.o \ gtkcomm.o gtkdlg.o gtkfont.o gtkmain.o gtkmisc.o gtkwin.o \ - ldisc.o ldiscucs.o localenc.o logging.o macenc.o marshal.o \ - memory.o mimeenc.o minibidi.o misc.o miscucs.o nocproxy.o \ - nogss.o pinger.o proxy.o raw.o rlogin.o sbcs.o sbcsdat.o \ - sercfg.o sessprep.o settings.o slookup.o stripctrl.o \ - telnet.o terminal.o time.o timing.o toucs.o tree234.o utf8.o \ - utils.o uxcfg.o uxfdsock.o uxmisc.o uxnet.o uxpeer.o \ - uxpoll.o uxprint.o uxproxy.o uxputty.o uxsel.o uxser.o \ - uxsignal.o uxstore.o uxucs.o uxutils.o version.o wcwidth.o \ - x11misc.o xenc.o xkeysym.o xpmpucfg.o xpmputty.o $(XLDFLAGS) + ldisc.o localenc.o logging.o macenc.o marshal.o memory.o \ + mimeenc.o minibidi.o misc.o miscucs.o nocproxy.o nogss.o \ + pinger.o proxy.o raw.o rlogin.o sbcs.o sbcsdat.o sercfg.o \ + sessprep.o settings.o slookup.o stripctrl.o telnet.o \ + terminal.o time.o timing.o toucs.o tree234.o utf8.o utils.o \ + uxcfg.o uxfdsock.o uxmisc.o uxnet.o uxpeer.o uxpoll.o \ + uxprint.o uxproxy.o uxputty.o uxsel.o uxser.o uxsignal.o \ + uxstore.o uxucs.o uxutils.o version.o wcwidth.o x11misc.o \ + xenc.o xkeysym.o xpmpucfg.o xpmputty.o $(XLDFLAGS) testcrypt: ecc.o marshal.o memory.o mpint.o sshaes.o ssharcf.o sshauxcrypt.o \ sshblowf.o sshccp.o sshcrc.o sshcrcda.o sshdes.o sshdh.o \ @@ -510,7 +509,7 @@ testzlib: marshal.o memory.o sshzlib.o testzlib.o utils.o uppity: be_misc.o be_none.o callback.o conf.o cproxy.o ecc.o errsock.o \ logging.o marshal.o memory.o misc.o mpint.o nullplug.o \ - pgssapi.o portfwd.o proxy.o scpserver.o sesschan.o \ + pgssapi.o portfwd.o procnet.o proxy.o scpserver.o sesschan.o \ settings.o sftpcommon.o sftpserver.o ssh1bpp.o ssh1censor.o \ ssh1connection.o ssh1connection-server.o ssh1login-server.o \ ssh2bpp.o ssh2censor.o ssh2connection.o \ @@ -528,7 +527,7 @@ uppity: be_misc.o be_none.o callback.o conf.o cproxy.o ecc.o errsock.o \ wcwidth.o wildcard.o x11fwd.o $(CC) -o $@ be_misc.o be_none.o callback.o conf.o cproxy.o ecc.o \ errsock.o logging.o marshal.o memory.o misc.o mpint.o \ - nullplug.o pgssapi.o portfwd.o proxy.o scpserver.o \ + nullplug.o pgssapi.o portfwd.o procnet.o proxy.o scpserver.o \ sesschan.o settings.o sftpcommon.o sftpserver.o ssh1bpp.o \ ssh1censor.o ssh1connection.o ssh1connection-server.o \ ssh1login-server.o ssh2bpp.o ssh2censor.o ssh2connection.o \ @@ -648,7 +647,10 @@ gtkapp.o: ../unix/gtkapp.c ../putty.h ../unix/gtkmisc.h ../defs.h \ ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/gtkapp.c gtkask.o: ../unix/gtkask.c ../defs.h ../unix/gtkfont.h ../unix/gtkcompat.h \ - ../unix/gtkmisc.h ../misc.h ../puttymem.h ../marshal.h + ../unix/gtkmisc.h ../putty.h ../ssh.h ../misc.h ../puttyps.h \ + ../network.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/gtkask.c gtkcfg.o: ../unix/gtkcfg.c ../putty.h ../dialog.h ../storage.h ../defs.h \ ../puttyps.h ../network.h ../misc.h ../marshal.h \ @@ -710,12 +712,6 @@ ldisc.o: ../ldisc.c ../putty.h ../terminal.h ../ldisc.h ../defs.h \ ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ldisc.c -ldiscucs.o: ../ldiscucs.c ../putty.h ../terminal.h ../ldisc.h ../defs.h \ - ../puttyps.h ../network.h ../misc.h ../marshal.h \ - ../sshsignals.h ../tree234.h ../windows/winstuff.h \ - ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ - ../charset/charset.h - $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ldiscucs.c localenc.o: ../charset/localenc.c ../charset/charset.h ../charset/internal.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../charset/localenc.c logging.o: ../logging.c ../putty.h ../defs.h ../puttyps.h ../network.h \ @@ -809,6 +805,8 @@ portfwd.o: ../portfwd.c ../putty.h ../ssh.h ../sshchan.h ../defs.h \ ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../portfwd.c +procnet.o: ../unix/procnet.c ../misc.h ../defs.h ../puttymem.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/procnet.c proxy.o: ../proxy.c ../putty.h ../network.h ../proxy.h ../defs.h \ ../puttyps.h ../misc.h ../marshal.h ../sshsignals.h \ ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ @@ -826,6 +824,12 @@ psftp.o: ../psftp.c ../putty.h ../psftp.h ../storage.h ../ssh.h ../sftp.h \ ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../psftp.c +psftpcommon.o: ../psftpcommon.c ../putty.h ../sftp.h ../psftp.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../psftpcommon.c raw.o: ../raw.c ../putty.h ../defs.h ../puttyps.h ../network.h ../misc.h \ ../marshal.h ../sshsignals.h ../windows/winstuff.h \ ../unix/unix.h ../puttymem.h ../tree234.h \ @@ -992,12 +996,12 @@ ssh2kex-client.o: ../ssh2kex-client.c ../putty.h ../ssh.h ../sshbpp.h \ ../windows/winhelp.h ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2kex-client.c ssh2kex-server.o: ../ssh2kex-server.c ../putty.h ../ssh.h ../sshbpp.h \ - ../sshppl.h ../sshcr.h ../storage.h ../ssh2transport.h \ - ../mpint.h ../defs.h ../puttyps.h ../network.h ../misc.h \ - ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ - ../sshttymodes.h ../sshgssc.h ../sshgss.h \ - ../windows/winstuff.h ../unix/unix.h ../pgssapi.h \ - ../windows/winhelp.h ../charset/charset.h + ../sshppl.h ../sshcr.h ../sshserver.h ../storage.h \ + ../ssh2transport.h ../mpint.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h ../sshgssc.h \ + ../sshgss.h ../windows/winstuff.h ../unix/unix.h \ + ../pgssapi.h ../windows/winhelp.h ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2kex-server.c ssh2transhk.o: ../ssh2transhk.c ../putty.h ../ssh.h ../defs.h ../puttyps.h \ ../network.h ../misc.h ../marshal.h ../sshsignals.h \ @@ -1006,12 +1010,12 @@ ssh2transhk.o: ../ssh2transhk.c ../putty.h ../ssh.h ../defs.h ../puttyps.h \ ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2transhk.c ssh2transport.o: ../ssh2transport.c ../putty.h ../ssh.h ../sshbpp.h \ - ../sshppl.h ../sshcr.h ../storage.h ../ssh2transport.h \ - ../mpint.h ../defs.h ../puttyps.h ../network.h ../misc.h \ - ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ - ../sshttymodes.h ../sshgssc.h ../sshgss.h \ - ../windows/winstuff.h ../unix/unix.h ../pgssapi.h \ - ../windows/winhelp.h ../charset/charset.h + ../sshppl.h ../sshcr.h ../sshserver.h ../storage.h \ + ../ssh2transport.h ../mpint.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h ../sshgssc.h \ + ../sshgss.h ../windows/winstuff.h ../unix/unix.h \ + ../pgssapi.h ../windows/winhelp.h ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2transport.c ssh2userauth.o: ../ssh2userauth.c ../putty.h ../ssh.h ../sshbpp.h \ ../sshppl.h ../sshcr.h ../sshgssc.h ../sshgss.h ../defs.h \ @@ -1118,9 +1122,9 @@ sshpubk.o: ../sshpubk.c ../putty.h ../mpint.h ../ssh.h ../misc.h ../defs.h \ ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshpubk.c -sshrand.o: ../sshrand.c ../putty.h ../ssh.h ../defs.h ../puttyps.h \ - ../network.h ../misc.h ../marshal.h ../sshsignals.h \ - ../puttymem.h ../tree234.h ../sshttymodes.h \ +sshrand.o: ../sshrand.c ../putty.h ../ssh.h ../storage.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshrand.c @@ -1365,9 +1369,11 @@ uxucs.o: ../unix/uxucs.c ../putty.h ../charset/charset.h ../terminal.h \ ../sshsignals.h ../tree234.h ../puttymem.h \ ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxucs.c -uxutils.o: ../unix/uxutils.c ../ssh.h ../puttymem.h ../tree234.h \ - ../network.h ../misc.h ../sshttymodes.h ../defs.h \ - ../marshal.h +uxutils.o: ../unix/uxutils.c ../putty.h ../ssh.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxutils.c version.o: ../version.c ../empty.h ../version.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../version.c diff --git a/unix/Makefile.ux b/unix/Makefile.ux index b32ea3b..a2e4060 100644 --- a/unix/Makefile.ux +++ b/unix/Makefile.ux @@ -126,30 +126,29 @@ cgtest: cgtest.o conf.o ecc.o import.o marshal.o memory.o misc.o mpint.o \ sshmd5.o sshprime.o sshprng.o sshpubk.o sshrand.o sshrsa.o \ sshrsag.o sshsh256.o sshsh512.o sshsha.o stripctrl.o time.o \ tree234.o utils.o uxcons.o uxgen.o uxmisc.o uxnogtk.o \ - uxnoise.o uxpoll.o uxstore.o version.o wcwidth.o + uxnoise.o uxpoll.o uxstore.o uxutils.o version.o wcwidth.o $(CC) -o $@ cgtest.o conf.o ecc.o import.o marshal.o memory.o misc.o \ mpint.o notiming.o sshaes.o sshauxcrypt.o sshbcrypt.o \ sshblowf.o sshdes.o sshdss.o sshdssg.o sshecc.o sshecdsag.o \ sshhmac.o sshmd5.o sshprime.o sshprng.o sshpubk.o sshrand.o \ sshrsa.o sshrsag.o sshsh256.o sshsh512.o sshsha.o \ stripctrl.o time.o tree234.o utils.o uxcons.o uxgen.o \ - uxmisc.o uxnogtk.o uxnoise.o uxpoll.o uxstore.o version.o \ - wcwidth.o $(ULDFLAGS) + uxmisc.o uxnogtk.o uxnoise.o uxpoll.o uxstore.o uxutils.o \ + version.o wcwidth.o $(ULDFLAGS) fuzzterm: be_none.o callback.o conf.o config.o dialog.o fromucs.o fuzzterm.o \ - ldiscucs.o localenc.o logging.o macenc.o marshal.o memory.o \ + localenc.o logging.o macenc.o marshal.o memory.o mimeenc.o \ + minibidi.o misc.o miscucs.o sbcs.o sbcsdat.o sercfg.o \ + settings.o slookup.o stripctrl.o terminal.o time.o timing.o \ + toucs.o tree234.o utf8.o utils.o uxcfg.o uxmisc.o uxnogtk.o \ + uxprint.o uxstore.o uxucs.o version.o wcwidth.o xenc.o + $(CC) -o $@ be_none.o callback.o conf.o config.o dialog.o fromucs.o \ + fuzzterm.o localenc.o logging.o macenc.o marshal.o memory.o \ mimeenc.o minibidi.o misc.o miscucs.o sbcs.o sbcsdat.o \ sercfg.o settings.o slookup.o stripctrl.o terminal.o time.o \ timing.o toucs.o tree234.o utf8.o utils.o uxcfg.o uxmisc.o \ uxnogtk.o uxprint.o uxstore.o uxucs.o version.o wcwidth.o \ - xenc.o - $(CC) -o $@ be_none.o callback.o conf.o config.o dialog.o fromucs.o \ - fuzzterm.o ldiscucs.o localenc.o logging.o macenc.o \ - marshal.o memory.o mimeenc.o minibidi.o misc.o miscucs.o \ - sbcs.o sbcsdat.o sercfg.o settings.o slookup.o stripctrl.o \ - terminal.o time.o timing.o toucs.o tree234.o utf8.o utils.o \ - uxcfg.o uxmisc.o uxnogtk.o uxprint.o uxstore.o uxucs.o \ - version.o wcwidth.o xenc.o $(ULDFLAGS) + xenc.o $(ULDFLAGS) osxlaunch: osxlaunch.o $(CC) -o $@ osxlaunch.o $(ULDFLAGS) @@ -196,8 +195,8 @@ plink: agentf.o aqsync.o be_all_s.o be_misc.o callback.o cmdline.o conf.o \ pscp: agentf.o aqsync.o be_misc.o be_ssh.o callback.o cmdline.o conf.o \ cproxy.o ecc.o errsock.o logging.o mainchan.o marshal.o \ memory.o misc.o mpint.o nullplug.o pgssapi.o pinger.o \ - portfwd.o proxy.o pscp.o settings.o sftp.o sftpcommon.o \ - ssh.o ssh1bpp.o ssh1censor.o ssh1connection.o \ + portfwd.o proxy.o pscp.o psftpcommon.o settings.o sftp.o \ + sftpcommon.o ssh.o ssh1bpp.o ssh1censor.o ssh1connection.o \ ssh1connection-client.o ssh1login.o ssh2bpp.o ssh2bpp-bare.o \ ssh2censor.o ssh2connection.o ssh2connection-client.o \ ssh2kex-client.o ssh2transhk.o ssh2transport.o \ @@ -213,8 +212,8 @@ pscp: agentf.o aqsync.o be_misc.o be_ssh.o callback.o cmdline.o conf.o \ $(CC) -o $@ agentf.o aqsync.o be_misc.o be_ssh.o callback.o \ cmdline.o conf.o cproxy.o ecc.o errsock.o logging.o \ mainchan.o marshal.o memory.o misc.o mpint.o nullplug.o \ - pgssapi.o pinger.o portfwd.o proxy.o pscp.o settings.o \ - sftp.o sftpcommon.o ssh.o ssh1bpp.o ssh1censor.o \ + pgssapi.o pinger.o portfwd.o proxy.o pscp.o psftpcommon.o \ + settings.o sftp.o sftpcommon.o ssh.o ssh1bpp.o ssh1censor.o \ ssh1connection.o ssh1connection-client.o ssh1login.o \ ssh2bpp.o ssh2bpp-bare.o ssh2censor.o ssh2connection.o \ ssh2connection-client.o ssh2kex-client.o ssh2transhk.o \ @@ -232,8 +231,8 @@ pscp: agentf.o aqsync.o be_misc.o be_ssh.o callback.o cmdline.o conf.o \ psftp: agentf.o aqsync.o be_misc.o be_ssh.o callback.o cmdline.o conf.o \ cproxy.o ecc.o errsock.o logging.o mainchan.o marshal.o \ memory.o misc.o mpint.o nullplug.o pgssapi.o pinger.o \ - portfwd.o proxy.o psftp.o settings.o sftp.o sftpcommon.o \ - ssh.o ssh1bpp.o ssh1censor.o ssh1connection.o \ + portfwd.o proxy.o psftp.o psftpcommon.o settings.o sftp.o \ + sftpcommon.o ssh.o ssh1bpp.o ssh1censor.o ssh1connection.o \ ssh1connection-client.o ssh1login.o ssh2bpp.o ssh2bpp-bare.o \ ssh2censor.o ssh2connection.o ssh2connection-client.o \ ssh2kex-client.o ssh2transhk.o ssh2transport.o \ @@ -249,8 +248,8 @@ psftp: agentf.o aqsync.o be_misc.o be_ssh.o callback.o cmdline.o conf.o \ $(CC) -o $@ agentf.o aqsync.o be_misc.o be_ssh.o callback.o \ cmdline.o conf.o cproxy.o ecc.o errsock.o logging.o \ mainchan.o marshal.o memory.o misc.o mpint.o nullplug.o \ - pgssapi.o pinger.o portfwd.o proxy.o psftp.o settings.o \ - sftp.o sftpcommon.o ssh.o ssh1bpp.o ssh1censor.o \ + pgssapi.o pinger.o portfwd.o proxy.o psftp.o psftpcommon.o \ + settings.o sftp.o sftpcommon.o ssh.o ssh1bpp.o ssh1censor.o \ ssh1connection.o ssh1connection-client.o ssh1login.o \ ssh2bpp.o ssh2bpp-bare.o ssh2censor.o ssh2connection.o \ ssh2connection-client.o ssh2kex-client.o ssh2transhk.o \ @@ -271,15 +270,15 @@ puttygen: cmdgen.o conf.o ecc.o import.o marshal.o memory.o misc.o mpint.o \ sshmd5.o sshprime.o sshprng.o sshpubk.o sshrand.o sshrsa.o \ sshrsag.o sshsh256.o sshsh512.o sshsha.o stripctrl.o time.o \ tree234.o utils.o uxcons.o uxgen.o uxmisc.o uxnogtk.o \ - uxnoise.o uxpoll.o uxstore.o version.o wcwidth.o + uxnoise.o uxpoll.o uxstore.o uxutils.o version.o wcwidth.o $(CC) -o $@ cmdgen.o conf.o ecc.o import.o marshal.o memory.o misc.o \ mpint.o notiming.o sshaes.o sshauxcrypt.o sshbcrypt.o \ sshblowf.o sshdes.o sshdss.o sshdssg.o sshecc.o sshecdsag.o \ sshhmac.o sshmd5.o sshprime.o sshprng.o sshpubk.o sshrand.o \ sshrsa.o sshrsag.o sshsh256.o sshsh512.o sshsha.o \ stripctrl.o time.o tree234.o utils.o uxcons.o uxgen.o \ - uxmisc.o uxnogtk.o uxnoise.o uxpoll.o uxstore.o version.o \ - wcwidth.o $(ULDFLAGS) + uxmisc.o uxnogtk.o uxnoise.o uxpoll.o uxstore.o uxutils.o \ + version.o wcwidth.o $(ULDFLAGS) testcrypt: ecc.o marshal.o memory.o mpint.o sshaes.o ssharcf.o sshauxcrypt.o \ sshblowf.o sshccp.o sshcrc.o sshcrcda.o sshdes.o sshdh.o \ @@ -309,7 +308,7 @@ testzlib: marshal.o memory.o sshzlib.o testzlib.o utils.o uppity: be_misc.o be_none.o callback.o conf.o cproxy.o ecc.o errsock.o \ logging.o marshal.o memory.o misc.o mpint.o nullplug.o \ - pgssapi.o portfwd.o proxy.o scpserver.o sesschan.o \ + pgssapi.o portfwd.o procnet.o proxy.o scpserver.o sesschan.o \ settings.o sftpcommon.o sftpserver.o ssh1bpp.o ssh1censor.o \ ssh1connection.o ssh1connection-server.o ssh1login-server.o \ ssh2bpp.o ssh2censor.o ssh2connection.o \ @@ -327,7 +326,7 @@ uppity: be_misc.o be_none.o callback.o conf.o cproxy.o ecc.o errsock.o \ wcwidth.o wildcard.o x11fwd.o $(CC) -o $@ be_misc.o be_none.o callback.o conf.o cproxy.o ecc.o \ errsock.o logging.o marshal.o memory.o misc.o mpint.o \ - nullplug.o pgssapi.o portfwd.o proxy.o scpserver.o \ + nullplug.o pgssapi.o portfwd.o procnet.o proxy.o scpserver.o \ sesschan.o settings.o sftpcommon.o sftpserver.o ssh1bpp.o \ ssh1censor.o ssh1connection.o ssh1connection-server.o \ ssh1login-server.o ssh2bpp.o ssh2censor.o ssh2connection.o \ @@ -447,7 +446,10 @@ gtkapp.o: ../unix/gtkapp.c ../putty.h ../unix/gtkmisc.h ../defs.h \ ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/gtkapp.c gtkask.o: ../unix/gtkask.c ../defs.h ../unix/gtkfont.h ../unix/gtkcompat.h \ - ../unix/gtkmisc.h ../misc.h ../puttymem.h ../marshal.h + ../unix/gtkmisc.h ../putty.h ../ssh.h ../misc.h ../puttyps.h \ + ../network.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/gtkask.c gtkcfg.o: ../unix/gtkcfg.c ../putty.h ../dialog.h ../storage.h ../defs.h \ ../puttyps.h ../network.h ../misc.h ../marshal.h \ @@ -509,12 +511,6 @@ ldisc.o: ../ldisc.c ../putty.h ../terminal.h ../ldisc.h ../defs.h \ ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ldisc.c -ldiscucs.o: ../ldiscucs.c ../putty.h ../terminal.h ../ldisc.h ../defs.h \ - ../puttyps.h ../network.h ../misc.h ../marshal.h \ - ../sshsignals.h ../tree234.h ../windows/winstuff.h \ - ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ - ../charset/charset.h - $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ldiscucs.c localenc.o: ../charset/localenc.c ../charset/charset.h ../charset/internal.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../charset/localenc.c logging.o: ../logging.c ../putty.h ../defs.h ../puttyps.h ../network.h \ @@ -608,6 +604,8 @@ portfwd.o: ../portfwd.c ../putty.h ../ssh.h ../sshchan.h ../defs.h \ ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../portfwd.c +procnet.o: ../unix/procnet.c ../misc.h ../defs.h ../puttymem.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/procnet.c proxy.o: ../proxy.c ../putty.h ../network.h ../proxy.h ../defs.h \ ../puttyps.h ../misc.h ../marshal.h ../sshsignals.h \ ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ @@ -625,6 +623,12 @@ psftp.o: ../psftp.c ../putty.h ../psftp.h ../storage.h ../ssh.h ../sftp.h \ ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../psftp.c +psftpcommon.o: ../psftpcommon.c ../putty.h ../sftp.h ../psftp.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../psftpcommon.c raw.o: ../raw.c ../putty.h ../defs.h ../puttyps.h ../network.h ../misc.h \ ../marshal.h ../sshsignals.h ../windows/winstuff.h \ ../unix/unix.h ../puttymem.h ../tree234.h \ @@ -791,12 +795,12 @@ ssh2kex-client.o: ../ssh2kex-client.c ../putty.h ../ssh.h ../sshbpp.h \ ../windows/winhelp.h ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2kex-client.c ssh2kex-server.o: ../ssh2kex-server.c ../putty.h ../ssh.h ../sshbpp.h \ - ../sshppl.h ../sshcr.h ../storage.h ../ssh2transport.h \ - ../mpint.h ../defs.h ../puttyps.h ../network.h ../misc.h \ - ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ - ../sshttymodes.h ../sshgssc.h ../sshgss.h \ - ../windows/winstuff.h ../unix/unix.h ../pgssapi.h \ - ../windows/winhelp.h ../charset/charset.h + ../sshppl.h ../sshcr.h ../sshserver.h ../storage.h \ + ../ssh2transport.h ../mpint.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h ../sshgssc.h \ + ../sshgss.h ../windows/winstuff.h ../unix/unix.h \ + ../pgssapi.h ../windows/winhelp.h ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2kex-server.c ssh2transhk.o: ../ssh2transhk.c ../putty.h ../ssh.h ../defs.h ../puttyps.h \ ../network.h ../misc.h ../marshal.h ../sshsignals.h \ @@ -805,12 +809,12 @@ ssh2transhk.o: ../ssh2transhk.c ../putty.h ../ssh.h ../defs.h ../puttyps.h \ ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2transhk.c ssh2transport.o: ../ssh2transport.c ../putty.h ../ssh.h ../sshbpp.h \ - ../sshppl.h ../sshcr.h ../storage.h ../ssh2transport.h \ - ../mpint.h ../defs.h ../puttyps.h ../network.h ../misc.h \ - ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ - ../sshttymodes.h ../sshgssc.h ../sshgss.h \ - ../windows/winstuff.h ../unix/unix.h ../pgssapi.h \ - ../windows/winhelp.h ../charset/charset.h + ../sshppl.h ../sshcr.h ../sshserver.h ../storage.h \ + ../ssh2transport.h ../mpint.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h ../sshgssc.h \ + ../sshgss.h ../windows/winstuff.h ../unix/unix.h \ + ../pgssapi.h ../windows/winhelp.h ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2transport.c ssh2userauth.o: ../ssh2userauth.c ../putty.h ../ssh.h ../sshbpp.h \ ../sshppl.h ../sshcr.h ../sshgssc.h ../sshgss.h ../defs.h \ @@ -917,9 +921,9 @@ sshpubk.o: ../sshpubk.c ../putty.h ../mpint.h ../ssh.h ../misc.h ../defs.h \ ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshpubk.c -sshrand.o: ../sshrand.c ../putty.h ../ssh.h ../defs.h ../puttyps.h \ - ../network.h ../misc.h ../marshal.h ../sshsignals.h \ - ../puttymem.h ../tree234.h ../sshttymodes.h \ +sshrand.o: ../sshrand.c ../putty.h ../ssh.h ../storage.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshrand.c @@ -1164,9 +1168,11 @@ uxucs.o: ../unix/uxucs.c ../putty.h ../charset/charset.h ../terminal.h \ ../sshsignals.h ../tree234.h ../puttymem.h \ ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxucs.c -uxutils.o: ../unix/uxutils.c ../ssh.h ../puttymem.h ../tree234.h \ - ../network.h ../misc.h ../sshttymodes.h ../defs.h \ - ../marshal.h +uxutils.o: ../unix/uxutils.c ../putty.h ../ssh.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxutils.c version.o: ../version.c ../empty.h ../version.h $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../version.c diff --git a/unix/gtkask.c b/unix/gtkask.c index 532b260..064e3f1 100644 --- a/unix/gtkask.c +++ b/unix/gtkask.c @@ -19,6 +19,8 @@ #include "gtkcompat.h" #include "gtkmisc.h" +#include "putty.h" +#include "ssh.h" #include "misc.h" #define N_DRAWING_AREAS 3 @@ -55,12 +57,46 @@ struct askpass_ctx { int nattempts; }; +static prng *keypress_prng = NULL; +static void feed_keypress_prng(void *data, int size) +{ + put_data(keypress_prng, data, size); +} +void random_add_noise(NoiseSourceId source, const void *noise, int length) +{ + if (keypress_prng) + prng_add_entropy(keypress_prng, source, make_ptrlen(noise, length)); +} +static void setup_keypress_prng(void) +{ + keypress_prng = prng_new(&ssh_sha256); + prng_seed_begin(keypress_prng); + noise_get_heavy(feed_keypress_prng); + prng_seed_finish(keypress_prng); +} +static void cleanup_keypress_prng(void) +{ + prng_free(keypress_prng); +} +static int choose_new_area(int prev_area) +{ + /* + * Don't actually put the passphrase keystrokes themselves into + * the PRNG; that doesn't seem like the course of wisdom when + * that's precisely what the information displayed on the screen + * is trying _not_ to be correlated to. + */ + noise_ultralight(NOISE_SOURCE_KEY, 0); + uint8_t data[8]; + prng_read(keypress_prng, data, 8); + uint64_t randval = GET_64BIT_MSB_FIRST(data); + int reduced = randval % (N_DRAWING_AREAS - 1); + return (prev_area + 1 + reduced) % N_DRAWING_AREAS; +} + static void visually_acknowledge_keypress(struct askpass_ctx *ctx) { - int new_active; - new_active = rand() % (N_DRAWING_AREAS - 1); - if (new_active >= ctx->active_area) - new_active++; + int new_active = choose_new_area(ctx->active_area); ctx->drawingareas[ctx->active_area].state = NOT_CURRENT; gtk_widget_queue_draw(ctx->drawingareas[ctx->active_area].area); ctx->drawingareas[new_active].state = CURRENT; @@ -546,7 +582,9 @@ char *gtk_askpass_main(const char *display, const char *wintitle, *success = false; return dupprintf("%s", err); } + setup_keypress_prng(); gtk_main(); + cleanup_keypress_prng(); gtk_askpass_cleanup(ctx); if (ctx->passphrase) { @@ -582,7 +620,6 @@ int main(int argc, char **argv) success = false; ret = dupprintf("usage: %s ", argv[0]); } else { - srand(time(NULL)); ret = gtk_askpass_main(NULL, "Enter passphrase", argv[1], &success); } diff --git a/unix/gtkcomm.c b/unix/gtkcomm.c index b50b6d5..265cdda 100644 --- a/unix/gtkcomm.c +++ b/unix/gtkcomm.c @@ -107,18 +107,18 @@ uxsel_id *uxsel_input_add(int fd, int rwx) { #if GTK_CHECK_VERSION(2,0,0) int flags = 0; - if (rwx & 1) flags |= G_IO_IN | G_IO_HUP; - if (rwx & 2) flags |= G_IO_OUT; - if (rwx & 4) flags |= G_IO_PRI; + if (rwx & SELECT_R) flags |= G_IO_IN | G_IO_HUP; + if (rwx & SELECT_W) flags |= G_IO_OUT; + if (rwx & SELECT_X) flags |= G_IO_PRI; id->chan = g_io_channel_unix_new(fd); g_io_channel_set_encoding(id->chan, NULL, NULL); id->watch_id = g_io_add_watch_full(id->chan, GDK_PRIORITY_REDRAW+1, flags, fd_input_func, NULL, NULL); #else int flags = 0; - if (rwx & 1) flags |= GDK_INPUT_READ; - if (rwx & 2) flags |= GDK_INPUT_WRITE; - if (rwx & 4) flags |= GDK_INPUT_EXCEPTION; + if (rwx & SELECT_R) flags |= GDK_INPUT_READ; + if (rwx & SELECT_W) flags |= GDK_INPUT_WRITE; + if (rwx & SELECT_X) flags |= GDK_INPUT_EXCEPTION; assert(flags); id->id = gdk_input_add(fd, flags, fd_input_func, NULL); #endif diff --git a/unix/gtkdlg.c b/unix/gtkdlg.c index b8ed07c..fc72c0b 100644 --- a/unix/gtkdlg.c +++ b/unix/gtkdlg.c @@ -51,6 +51,8 @@ struct Shortcuts { struct Shortcut sc[128]; }; +struct selparam; + struct uctrl { union control *ctrl; GtkWidget *toplevel; @@ -71,6 +73,7 @@ struct uctrl { GtkWidget *text; /* for text */ GtkWidget *label; /* for dlg_label_change */ GtkAdjustment *adj; /* for the scrollbar in a list box */ + struct selparam *sp; /* which switchable pane of the box we're in */ guint entrysig; guint textsig; int nclicks; @@ -94,8 +97,9 @@ struct dlgparam { int ntreeitems; #else size_t nselparams; - struct selparam *selparams; + struct selparam **selparams; #endif + struct selparam *curr_panel; struct controlbox *ctrlbox; int retval; post_dialog_fn_t after; @@ -206,6 +210,7 @@ static void dlg_init(struct dlgparam *dp) dp->treeitems = NULL; dp->currtreeitem = NULL; #endif + dp->curr_panel = NULL; dp->flags = 0; dp->currfocus = NULL; } @@ -1843,8 +1848,9 @@ static void label_sizealloc(GtkWidget *widget, GtkAllocation *alloc, * non-NULL, all buttons created will be default-capable (so they * have extra space round them for the default highlight). */ -GtkWidget *layout_ctrls(struct dlgparam *dp, struct Shortcuts *scs, - struct controlset *s, GtkWindow *win) +GtkWidget *layout_ctrls( + struct dlgparam *dp, struct selparam *sp, struct Shortcuts *scs, + struct controlset *s, GtkWindow *win) { Columns *cols; GtkWidget *ret; @@ -1903,6 +1909,7 @@ GtkWidget *layout_ctrls(struct dlgparam *dp, struct Shortcuts *scs, } uc = snew(struct uctrl); + uc->sp = sp; uc->ctrl = ctrl; uc->buttons = NULL; uc->entry = NULL; @@ -2523,7 +2530,7 @@ struct selparam { static void treeselection_changed(GtkTreeSelection *treeselection, gpointer data) { - struct selparam *sps = (struct selparam *)data, *sp; + struct selparam **sps = (struct selparam **)data, *sp; GtkTreeModel *treemodel; GtkTreeIter treeiter; gint spindex; @@ -2533,11 +2540,12 @@ static void treeselection_changed(GtkTreeSelection *treeselection, return; gtk_tree_model_get(treemodel, &treeiter, TREESTORE_PARAMS, &spindex, -1); - sp = &sps[spindex]; + sp = sps[spindex]; page_num = gtk_notebook_page_num(sp->panels, sp->panel); gtk_notebook_set_current_page(sp->panels, page_num); + sp->dp->curr_panel = sp; dlg_refresh(NULL, sp->dp); sp->dp->shortcuts = &sp->shortcuts; @@ -2551,6 +2559,7 @@ static void treeitem_sel(GtkItem *item, gpointer data) page_num = gtk_notebook_page_num(sp->panels, sp->panel); gtk_notebook_set_page(sp->panels, page_num); + sp->dp->curr_panel = sp; dlg_refresh(NULL, sp->dp); sp->dp->shortcuts = &sp->shortcuts; @@ -2558,6 +2567,17 @@ static void treeitem_sel(GtkItem *item, gpointer data) } #endif +bool dlg_is_visible(union control *ctrl, dlgparam *dp) +{ + struct uctrl *uc = dlg_find_byctrl(dp, ctrl); + /* + * A control is visible if it belongs to _no_ notebook page (i.e. + * it's one of the config-box-global buttons like Load or About), + * or if it belongs to the currently selected page. + */ + return uc->sp == NULL || uc->sp == dp->curr_panel; +} + #if !GTK_CHECK_VERSION(2,0,0) static bool tree_grab_focus(struct dlgparam *dp) { @@ -2879,9 +2899,9 @@ void initial_treeview_collapse(struct dlgparam *dp, GtkWidget *tree) */ int i; for (i = 0; i < dp->nselparams; i++) - if (dp->selparams[i].depth >= 2) + if (dp->selparams[i]->depth >= 2) gtk_tree_view_collapse_row(GTK_TREE_VIEW(tree), - dp->selparams[i].treepath); + dp->selparams[i]->treepath); } #endif @@ -2917,7 +2937,7 @@ GtkWidget *create_config_box(const char *title, Conf *conf, struct dlgparam *dp; struct Shortcuts scs; - struct selparam *selparams = NULL; + struct selparam **selparams = NULL; size_t nselparams = 0, selparamsize = 0; dp = snew(struct dlgparam); @@ -2991,7 +3011,7 @@ GtkWidget *create_config_box(const char *title, Conf *conf, GtkWidget *w; if (!*s->pathname) { - w = layout_ctrls(dp, &scs, s, GTK_WINDOW(window)); + w = layout_ctrls(dp, NULL, &scs, s, GTK_WINDOW(window)); our_dialog_set_action_area(GTK_WINDOW(window), w); } else { @@ -3031,6 +3051,9 @@ GtkWidget *create_config_box(const char *title, Conf *conf, gtk_widget_show(panelvbox); gtk_notebook_append_page(GTK_NOTEBOOK(panels), panelvbox, NULL); + + struct selparam *sp = snew(struct selparam); + if (first) { gint page_num; @@ -3038,13 +3061,16 @@ GtkWidget *create_config_box(const char *title, Conf *conf, panelvbox); gtk_notebook_set_current_page(GTK_NOTEBOOK(panels), page_num); + + dp->curr_panel = sp; } sgrowarray(selparams, selparamsize, nselparams); - selparams[nselparams].dp = dp; - selparams[nselparams].panels = GTK_NOTEBOOK(panels); - selparams[nselparams].panel = panelvbox; - selparams[nselparams].shortcuts = scs; /* structure copy */ + selparams[nselparams] = sp; + sp->dp = dp; + sp->panels = GTK_NOTEBOOK(panels); + sp->panel = panelvbox; + sp->shortcuts = scs; /* structure copy */ assert(j-1 < level); @@ -3063,11 +3089,10 @@ GtkWidget *create_config_box(const char *title, Conf *conf, -1); treeiterlevels[j] = treeiter; - selparams[nselparams].depth = j; + sp->depth = j; if (j > 0) { - selparams[nselparams].treepath = - gtk_tree_model_get_path(GTK_TREE_MODEL(treestore), - &treeiterlevels[j-1]); + sp->treepath = gtk_tree_model_get_path( + GTK_TREE_MODEL(treestore), &treeiterlevels[j-1]); /* * We are going to collapse all tree branches * at depth greater than 2, but not _yet_; see @@ -3075,10 +3100,9 @@ GtkWidget *create_config_box(const char *title, Conf *conf, * gtk_tree_view_collapse_row below. */ gtk_tree_view_expand_row(GTK_TREE_VIEW(tree), - selparams[nselparams].treepath, - false); + sp->treepath, false); } else { - selparams[nselparams].treepath = NULL; + sp->treepath = NULL; } #else treeitem = gtk_tree_item_new_with_label(c); @@ -3109,14 +3133,15 @@ GtkWidget *create_config_box(const char *title, Conf *conf, if (first) gtk_tree_select_child(GTK_TREE(tree), treeitem); - selparams[nselparams].treeitem = treeitem; + sp->treeitem = treeitem; #endif level = j+1; nselparams++; } - w = layout_ctrls(dp, &selparams[nselparams-1].shortcuts, s, NULL); + w = layout_ctrls(dp, selparams[nselparams-1], + &selparams[nselparams-1]->shortcuts, s, NULL); gtk_box_pack_start(GTK_BOX(panelvbox), w, false, false, 0); gtk_widget_show(w); } @@ -3178,7 +3203,7 @@ GtkWidget *create_config_box(const char *title, Conf *conf, dp->data = conf; dlg_refresh(NULL, dp); - dp->shortcuts = &selparams[0].shortcuts; + dp->shortcuts = &selparams[0]->shortcuts; #if !GTK_CHECK_VERSION(2,0,0) dp->currtreeitem = dp->treeitems[0]; #endif @@ -3239,9 +3264,11 @@ static void dlgparam_destroy(GtkWidget *widget, gpointer data) ctrl_free_box(dp->ctrlbox); #if GTK_CHECK_VERSION(2,0,0) if (dp->selparams) { - for (size_t i = 0; i < dp->nselparams; i++) - if (dp->selparams[i].treepath) - gtk_tree_path_free(dp->selparams[i].treepath); + for (size_t i = 0; i < dp->nselparams; i++) { + if (dp->selparams[i]->treepath) + gtk_tree_path_free(dp->selparams[i]->treepath); + sfree(dp->selparams[i]); + } sfree(dp->selparams); } #endif @@ -3341,10 +3368,10 @@ GtkWidget *create_message_box( window = our_dialog_new(); gtk_window_set_title(GTK_WINDOW(window), title); - w0 = layout_ctrls(dp, &scs, s0, GTK_WINDOW(window)); + w0 = layout_ctrls(dp, NULL, &scs, s0, GTK_WINDOW(window)); our_dialog_set_action_area(GTK_WINDOW(window), w0); gtk_widget_show(w0); - w1 = layout_ctrls(dp, &scs, s1, GTK_WINDOW(window)); + w1 = layout_ctrls(dp, NULL, &scs, s1, GTK_WINDOW(window)); gtk_container_set_border_width(GTK_CONTAINER(w1), 10); gtk_widget_set_size_request(w1, minwid+20, -1); our_dialog_add_to_content_area(GTK_WINDOW(window), w1, true, true, 0); @@ -3911,10 +3938,10 @@ void showeventlog(eventlog_stuff *es, void *parentwin) title = dupcat(appname, " Event Log", (const char *)NULL); gtk_window_set_title(GTK_WINDOW(window), title); sfree(title); - w0 = layout_ctrls(&es->dp, &es->scs, s0, GTK_WINDOW(window)); + w0 = layout_ctrls(&es->dp, NULL, &es->scs, s0, GTK_WINDOW(window)); our_dialog_set_action_area(GTK_WINDOW(window), w0); gtk_widget_show(w0); - w1 = layout_ctrls(&es->dp, &es->scs, s1, GTK_WINDOW(window)); + w1 = layout_ctrls(&es->dp, NULL, &es->scs, s1, GTK_WINDOW(window)); gtk_container_set_border_width(GTK_CONTAINER(w1), 10); gtk_widget_set_size_request(w1, 20 + string_width ("LINE OF TEXT GIVING WIDTH OF EVENT LOG IS " diff --git a/unix/gtkmain.c b/unix/gtkmain.c index 9cd32c2..f687e76 100644 --- a/unix/gtkmain.c +++ b/unix/gtkmain.c @@ -515,7 +515,7 @@ bool do_cmdline(int argc, char **argv, bool do_everything, Conf *conf) } else if (!strcmp(p, "-xrm")) { EXPECTS_ARG; - provide_xrm_string(val); + provide_xrm_string(val, appname); } else if(!strcmp(p, "-help") || !strcmp(p, "--help")) { help(stdout); diff --git a/unix/gtkwin.c b/unix/gtkwin.c index 395262b..3bcbb4b 100644 --- a/unix/gtkwin.c +++ b/unix/gtkwin.c @@ -993,6 +993,32 @@ char *dup_keyval_name(guint keyval) static void change_font_size(GtkFrontend *inst, int increment); static void key_pressed(GtkFrontend *inst); +/* Subroutine used in key_event */ +static int return_key(GtkFrontend *inst, char *output, bool *special) +{ + int end; + + /* Ugly label so we can come here as a fallback from + * numeric keypad Enter handling */ + if (inst->term->cr_lf_return) { +#ifdef KEY_EVENT_DIAGNOSTICS + debug(" - Return in cr_lf_return mode, translating as 0d 0a\n"); +#endif + output[1] = '\015'; + output[2] = '\012'; + end = 3; + } else { +#ifdef KEY_EVENT_DIAGNOSTICS + debug(" - Return special case, translating as 0d + special\n"); +#endif + output[1] = '\015'; + end = 2; + *special = true; + } + + return end; +} + gint key_event(GtkWidget *widget, GdkEventKey *event, gpointer data) { GtkFrontend *inst = (GtkFrontend *)data; @@ -1688,13 +1714,8 @@ gint key_event(GtkWidget *widget, GdkEventKey *event, gpointer data) /* We handle Return ourselves, because it needs to be flagged as * special to ldisc. */ if (event->keyval == GDK_KEY_Return) { -#ifdef KEY_EVENT_DIAGNOSTICS - debug(" - Return special case, translating as 0d + special\n"); -#endif - output[1] = '\015'; - use_ucsoutput = false; - end = 2; - special = true; + end = return_key(inst, output, &special); + use_ucsoutput = false; } /* Control-2, Control-Space and Control-@ are NUL */ @@ -1870,6 +1891,15 @@ gint key_event(GtkWidget *widget, GdkEventKey *event, gpointer data) #ifdef KEY_EVENT_DIAGNOSTICS debug(" - numeric keypad key"); #endif + + if (end == 1 && num_keypad_key == '\r') { + /* Keypad Enter, lacking any other translation, + * becomes the same special Return code as normal + * Return. */ + end = return_key(inst, output, &special); + use_ucsoutput = false; + } + use_ucsoutput = false; goto done; } @@ -1902,8 +1932,7 @@ gint key_event(GtkWidget *widget, GdkEventKey *event, gpointer data) */ output[end] = '\0'; /* NUL-terminate */ generated_something = true; - if (inst->ldisc) - ldisc_send(inst->ldisc, output+start, -2, true); + term_keyinput(inst->term, -1, output+start, -2); } else if (!inst->direct_to_font) { if (!use_ucsoutput) { #ifdef KEY_EVENT_DIAGNOSTICS @@ -1922,9 +1951,8 @@ gint key_event(GtkWidget *widget, GdkEventKey *event, gpointer data) sfree(string_string); #endif generated_something = true; - if (inst->ldisc) - lpage_send(inst->ldisc, output_charset, output+start, - end-start, true); + term_keyinput(inst->term, output_charset, + output+start, end-start); } else { #ifdef KEY_EVENT_DIAGNOSTICS char *string_string = dupstr(""); @@ -1947,8 +1975,7 @@ gint key_event(GtkWidget *widget, GdkEventKey *event, gpointer data) * keysym, so use that instead. */ generated_something = true; - if (inst->ldisc) - luni_send(inst->ldisc, ucsoutput+start, end-start, true); + term_keyinputw(inst->term, ucsoutput+start, end-start); } } else { /* @@ -1971,12 +1998,10 @@ gint key_event(GtkWidget *widget, GdkEventKey *event, gpointer data) sfree(string_string); #endif generated_something = true; - if (inst->ldisc) - ldisc_send(inst->ldisc, output+start, end-start, true); + term_keyinput(inst->term, -1, output+start, end-start); } show_mouseptr(inst, false); - term_seen_key_event(inst->term); } if (generated_something) @@ -2004,10 +2029,8 @@ void input_method_commit_event(GtkIMContext *imc, gchar *str, gpointer data) sfree(string_string); #endif - if (inst->ldisc) - lpage_send(inst->ldisc, CS_UTF8, str, strlen(str), true); + term_keyinput(inst->term, CS_UTF8, str, strlen(str)); show_mouseptr(inst, false); - term_seen_key_event(inst->term); key_pressed(inst); } #endif @@ -4605,18 +4628,11 @@ static void after_change_settings_dialog(void *vctx, int retval) sfree(vctx); /* we've copied this already */ - if (retval < 0) { - /* If the dialog box was aborted without giving a result - * (probably because the whole session window closed), we have - * nothing further to do. */ - return; - } - assert(lenof(ww) == NCFGCOLOURS); unregister_dialog(&inst->seat, DIALOG_SLOT_RECONFIGURE); - if (retval) { + if (retval > 0) { inst->conf = newconf; /* Pass new config data to the logging module */ @@ -5059,6 +5075,7 @@ static void start_backend(GtkFrontend *inst) vt = select_backend(inst->conf); + seat_set_trust_status(&inst->seat, true); error = backend_init(vt, &inst->seat, &inst->backend, inst->logctx, inst->conf, conf_get_str(inst->conf, CONF_host), @@ -5068,11 +5085,10 @@ static void start_backend(GtkFrontend *inst) conf_get_bool(inst->conf, CONF_tcp_keepalives)); if (error) { - char *msg = dupprintf("Unable to open connection to %s:\n%s", + seat_connection_fatal(&inst->seat, + "Unable to open connection to %s:\n%s", conf_dest(inst->conf), error); inst->exited = true; - seat_connection_fatal(&inst->seat, msg); - sfree(msg); return; } diff --git a/unix/procnet.c b/unix/procnet.c new file mode 100644 index 0000000..43b1f05 --- /dev/null +++ b/unix/procnet.c @@ -0,0 +1,229 @@ +/* + * Locally authenticate a TCP socket via /proc/net. + * + * Obviously, if a TCP connection comes from a different host, there's + * no way to find out the identity of the thing at the other end (or + * even really to assign that concept a meaning) except by the usual + * method of speaking a protocol over the socket itself which involves + * some form of (preferably cryptographic) authentication exchange. + * + * But if the connection comes from localhost, then on at least some + * operating systems, you can do better. On Linux, /proc/net/tcp and + * /proc/net/tcp6 list the full set of active TCP connection + * endpoints, and they list an owning uid for each one. So once you've + * accepted a connection to a listening socket and found that the + * other end of it is a localhost address, you can look up the _other_ + * endpoint in the right one of those files, and find out which uid + * owns it. + */ + +#include +#include +#include + +#include +#include +#include +#include +#include + +#include "misc.h" + +static ptrlen get_space_separated_field(ptrlen *string) +{ + const char *p = string->ptr, *end = p + string->len; + + while (p < end && isspace((unsigned char)*p)) + p++; + if (p == end) + return PTRLEN_LITERAL(""); + + const char *start = p; + while (p < end && !isspace((unsigned char)*p)) + p++; + *string = make_ptrlen(p, end - p); + return make_ptrlen(start, p - start); +} + +enum { GOT_LOCAL_UID = 1, GOT_REMOTE_UID = 2 }; + +/* + * Open a file formatted like /proc/net/tcp{,6}, and search it for + * both ends of a particular connection. + * + * The operands 'local' and 'remote' give the expected string + * representations of the local and remote addresses of the connection + * we're looking for. + * + * Return value is the bitwise OR of 1 if we found the local end of + * the connection and 2 if we found the remote. Each output uid_t + * parameter is filled in iff the corresponding bit is set in the + * return value. + */ +static int lookup_uids_in_procnet_file( + const char *path, ptrlen local, ptrlen remote, + uid_t *local_uid, uid_t *remote_uid) +{ + FILE *fp = NULL; + int toret = 0; + ptrlen line, field; + + enum { GF_LOCAL = 1, GF_REMOTE = 2, GF_UID = 4 }; + + fp = fopen(path, "r"); + if (!fp) + goto out; + + /* Expected indices of fields in /proc/net/tcp* */ + const int LOCAL_ADDR_INDEX = 1; + const int REMOTE_ADDR_INDEX = 2; + const int UID_INDEX = 7; + + for (char *linez; (linez = chomp(fgetline(fp))) != NULL ;) { + line = ptrlen_from_asciz(linez); + int gotfields = 0; + ptrlen local_addr = PTRLEN_LITERAL(""); + ptrlen remote_addr = PTRLEN_LITERAL(""); + long uid = -1; + + for (int i = 0; (field = get_space_separated_field(&line)).len != 0; + i++) { + + if (i == LOCAL_ADDR_INDEX) { + gotfields |= GF_LOCAL; + local_addr = field; + } else if (i == REMOTE_ADDR_INDEX) { + gotfields |= GF_REMOTE; + remote_addr = field; + } else if (i == UID_INDEX) { + uid = 0; + for (const char *p = field.ptr, *end = p + field.len; + p < end; p++) { + if (!isdigit((unsigned char)*p)) { + uid = -1; + break; + } + int dval = *p - '0'; + if (uid > LONG_MAX/10) { + uid = -1; + break; + } + uid *= 10; + if (uid > LONG_MAX - dval) { + uid = -1; + break; + } + uid += dval; + } + + gotfields |= GF_UID; + } + } + + if (gotfields == (GF_LOCAL | GF_REMOTE | GF_UID)) { + if (ptrlen_eq_ptrlen(local_addr, local) && + ptrlen_eq_ptrlen(remote_addr, remote)) { + *local_uid = uid; + toret |= GOT_LOCAL_UID; + } + if (ptrlen_eq_ptrlen(local_addr, remote) && + ptrlen_eq_ptrlen(remote_addr, local)) { + *remote_uid = uid; + toret |= GOT_REMOTE_UID; + } + } + + sfree(linez); + } + + fclose(fp); + fp = NULL; + + out: + if (fp) + fclose(fp); + return toret; +} + +static const char *procnet_path(int family) +{ + switch (family) { + case AF_INET: return "/proc/net/tcp"; + case AF_INET6: return "/proc/net/tcp6"; + default: return NULL; + } +} + +static char *format_sockaddr(const void *addr, int family) +{ + if (family == AF_INET) { + const struct sockaddr_in *a = (const struct sockaddr_in *)addr; + assert(a->sin_family == family); + /* Linux /proc/net formats the IP address native-endian, so we + * don't use ntohl */ + return dupprintf("%08X:%04X", a->sin_addr.s_addr, ntohs(a->sin_port)); + } else if (family == AF_INET6) { + struct sockaddr_in6 *a = (struct sockaddr_in6 *)addr; + assert(a->sin6_family == family); + + strbuf *sb = strbuf_new(); + + const uint32_t *addrwords = (const uint32_t *)a->sin6_addr.s6_addr; + for (int i = 0; i < 4; i++) + strbuf_catf(sb, "%08X", addrwords[i]); + strbuf_catf(sb, ":%04X", ntohs(a->sin6_port)); + + return strbuf_to_str(sb); + } else { + return NULL; + } +} + +bool socket_peer_is_same_user(int fd) +{ + struct sockaddr_storage addr; + socklen_t addrlen; + int family; + bool toret = false; + char *local = NULL, *remote = NULL; + const char *path; + + addrlen = sizeof(addr); + if (getsockname(fd, (struct sockaddr *)&addr, &addrlen) != 0) + goto out; + family = addr.ss_family; + if ((path = procnet_path(family)) == NULL) + goto out; + local = format_sockaddr(&addr, family); + if (!local) + goto out; + + addrlen = sizeof(addr); + if (getpeername(fd, (struct sockaddr *)&addr, &addrlen) != 0) + goto out; + if (addr.ss_family != family) + goto out; + remote = format_sockaddr(&addr, family); + if (!remote) + goto out; + + ptrlen locpl = ptrlen_from_asciz(local); + ptrlen rempl = ptrlen_from_asciz(remote); + + /* + * Check that _both_ end of the socket are the uid we expect, as a + * sanity check on the /proc/net file being reasonable at all. + */ + uid_t our_uid = getuid(); + uid_t local_uid = -1, remote_uid = -1; + int got = lookup_uids_in_procnet_file( + path, locpl, rempl, &local_uid, &remote_uid); + if (got == (GOT_LOCAL_UID | GOT_REMOTE_UID) && + local_uid == our_uid && remote_uid == our_uid) + toret = true; + + out: + sfree(local); + sfree(remote); + return toret; +} diff --git a/unix/unix.h b/unix/unix.h index 284d143..31e633f 100644 --- a/unix/unix.h +++ b/unix/unix.h @@ -267,7 +267,7 @@ int keysym_to_unicode(int keysym); char *x_get_default(const char *key); /* Things uxstore.c provides to gtkwin.c */ -void provide_xrm_string(char *string); +void provide_xrm_string(const char *string, const char *progname); /* Function that {gtkapp,gtkmain}.c needs from ux{pterm,putty}.c. Does * early process setup that varies between applications (e.g. @@ -369,6 +369,7 @@ bool init_ucs(struct unicode_data *ucsdata, char *line_codepage, * Spare functions exported directly from uxnet.c. */ void *sk_getxdmdata(Socket *sock, int *lenp); +int sk_net_get_fd(Socket *sock); SockAddr *unix_sock_addr(const char *path); Socket *new_unix_listener(SockAddr *listenaddr, Plug *plug); @@ -421,6 +422,16 @@ extern char **pty_argv; char *gtk_askpass_main(const char *display, const char *wintitle, const char *prompt, bool *success); +/* + * procnet.c. + */ +bool socket_peer_is_same_user(int fd); +static inline bool sk_peer_trusted(Socket *sock) +{ + int fd = sk_net_get_fd(sock); + return fd >= 0 && socket_peer_is_same_user(fd); +} + /* * uxsftpserver.c. */ diff --git a/unix/uxcons.c b/unix/uxcons.c index 8e2a908..3780c89 100644 --- a/unix/uxcons.c +++ b/unix/uxcons.c @@ -142,8 +142,10 @@ static int block_and_read(int fd, void *buf, size_t len) ret = pollwrap_poll_endless(pw); } while (ret < 0 && errno == EINTR); assert(ret != 0); - if (ret < 0) + if (ret < 0) { + pollwrap_free(pw); return ret; + } assert(pollwrap_check_fd_rwx(pw, fd, SELECT_R)); } diff --git a/unix/uxmisc.c b/unix/uxmisc.c index 2170c3c..00c1977 100644 --- a/unix/uxmisc.c +++ b/unix/uxmisc.c @@ -119,7 +119,9 @@ char *get_username(void) * coping correctly with people who have su'ed. */ user = getlogin(); +#if HAVE_SETPWENT setpwent(); +#endif if (user) p = getpwnam(user); else @@ -141,7 +143,9 @@ char *get_username(void) return NULL; ret = p->pw_name; } +#if HAVE_ENDPWENT endpwent(); +#endif return dupstr(ret); } diff --git a/unix/uxnet.c b/unix/uxnet.c index 16680fb..ef452d3 100644 --- a/unix/uxnet.c +++ b/unix/uxnet.c @@ -221,6 +221,7 @@ SockAddr *sk_namelookup(const char *host, char **canonicalname, int address_fami } if (err != 0) { ret->error = gai_strerror(err); + strbuf_free(realhost); return ret; } ret->superfamily = IP; @@ -1554,6 +1555,15 @@ static SocketPeerInfo *sk_net_peer_info(Socket *sock) return pi; } +int sk_net_get_fd(Socket *sock) +{ + /* This function is not fully general: it only works on NetSocket */ + if (sock->vt != &NetSocket_sockvt) + return -1; /* failure */ + NetSocket *s = container_of(sock, NetSocket, sock); + return s->s; +} + static void uxsel_tell(NetSocket *s) { int rwx = 0; diff --git a/unix/uxnoise.c b/unix/uxnoise.c index 2402300..fb6c7c2 100644 --- a/unix/uxnoise.c +++ b/unix/uxnoise.c @@ -84,18 +84,6 @@ void noise_get_heavy(void (*func) (void *, int)) read_random_seed(func); } -void random_save_seed(void) -{ - int len; - void *data; - - if (random_active) { - random_get_savedata(&data, &len); - write_random_seed(data, len); - sfree(data); - } -} - /* * This function is called on a timer, and grabs as much changeable * system data as it can quickly get its hands on. diff --git a/unix/uxpgnt.c b/unix/uxpgnt.c index 389853f..ac33a55 100644 --- a/unix/uxpgnt.c +++ b/unix/uxpgnt.c @@ -52,7 +52,6 @@ void uxsel_input_remove(uxsel_id *id) { } */ void random_save_seed(void) {} void random_destroy_seed(void) {} -void noise_ultralight(NoiseSourceId id, unsigned long data) {} char *platform_default_s(const char *name) { return NULL; } bool platform_default_b(const char *name, bool def) { return def; } int platform_default_i(const char *name, int def) { return def; } @@ -990,6 +989,7 @@ void run_agent(void) } conf_free(conf); + pollwrap_free(pw); } int main(int argc, char **argv) diff --git a/unix/uxplink.c b/unix/uxplink.c index 5973b49..13f4a89 100644 --- a/unix/uxplink.c +++ b/unix/uxplink.c @@ -79,10 +79,6 @@ char *x_get_default(const char *key) { return NULL; /* this is a stub */ } -bool term_ldisc(Terminal *term, int mode) -{ - return false; -} static void plink_echoedit_update(Seat *seat, bool echo, bool edit) { /* Update stdin read mode to reflect changes in line discipline. */ @@ -661,7 +657,11 @@ int main(int argc, char **argv) errors = true; } else { --argc; - provide_xrm_string(*++argv); + /* Explicitly pass "plink" in place of appname for + * error reporting purposes. appname will have been + * set by be_foo.c to something more generic, probably + * "PuTTY". */ + provide_xrm_string(*++argv, "plink"); } } else if (!strcmp(p, "-shareexists")) { just_test_share_exists = true; diff --git a/unix/uxpoll.c b/unix/uxpoll.c index bbc5490..da74ebf 100644 --- a/unix/uxpoll.c +++ b/unix/uxpoll.c @@ -1,3 +1,6 @@ +/* On some systems this is needed to get poll.h to define eg.. POLLRDNORM */ +#define _XOPEN_SOURCE + #include #include "putty.h" @@ -72,6 +75,21 @@ void pollwrap_add_fd_events(pollwrapper *pw, int fd, int events) pw->fds[f2p->pos].events |= events; } +/* Omit any of the POLL{RD,WR}{NORM,BAND} flag values that are still + * not defined by poll.h, just in case */ +#ifndef POLLRDNORM +#define POLLRDNORM 0 +#endif +#ifndef POLLRDBAND +#define POLLRDBAND 0 +#endif +#ifndef POLLWRNORM +#define POLLWRNORM 0 +#endif +#ifndef POLLWRBAND +#define POLLWRBAND 0 +#endif + #define SELECT_R_IN (POLLIN | POLLRDNORM | POLLRDBAND) #define SELECT_W_IN (POLLOUT | POLLWRNORM | POLLWRBAND) #define SELECT_X_IN (POLLPRI) diff --git a/unix/uxproxy.c b/unix/uxproxy.c index c1d0c3f..8e7b76d 100644 --- a/unix/uxproxy.c +++ b/unix/uxproxy.c @@ -88,8 +88,11 @@ Socket *platform_new_connection(SockAddr *addr, const char *hostname, } infd = open(cmd, O_RDONLY); if (infd == -1) { + Socket *toret = new_error_socket_fmt( + plug, "%s: %s", cmd, strerror(errno)); sfree(cmd); - return new_error_socket_fmt(plug, "%s: %s", cmd, strerror(errno)); + close(outfd); + return toret; } sfree(cmd); inerrfd = -1; diff --git a/unix/uxpty.c b/unix/uxpty.c index 9372135..6b324e3 100644 --- a/unix/uxpty.c +++ b/unix/uxpty.c @@ -857,7 +857,8 @@ static void copy_ttymodes_into_termios( */ Backend *pty_backend_create( Seat *seat, LogContext *logctx, Conf *conf, char **argv, const char *cmd, - struct ssh_ttymodes ttymodes, bool pipes_instead) + struct ssh_ttymodes ttymodes, bool pipes_instead, const char *dir, + const char *const *env_vars_to_unset) { int slavefd; pid_t pid, pgrp; @@ -1088,6 +1089,11 @@ Backend *pty_backend_create( close(ptyfd); } setpgid(pgrp, pgrp); + + if (env_vars_to_unset) + for (const char *const *p = env_vars_to_unset; *p; p++) + unsetenv(*p); + if (!pipes_instead) { char *term_env_var = dupprintf("TERM=%s", conf_get_str(conf, CONF_termtype)); @@ -1113,9 +1119,13 @@ Backend *pty_backend_create( * on. */ const char *x_display = seat_get_x_display(pty->seat); - char *x_display_env_var = dupprintf("DISPLAY=%s", x_display); - putenv(x_display_env_var); - /* As above, we don't free this. */ + if (x_display) { + char *x_display_env_var = dupprintf("DISPLAY=%s", x_display); + putenv(x_display_env_var); + /* As above, we don't free this. */ + } else { + unsetenv("DISPLAY"); + } } #endif { @@ -1135,6 +1145,13 @@ Backend *pty_backend_create( } } + if (dir) { + if (chdir(dir) < 0) { + /* Ignore the error - nothing we can sensibly do about it, + * and our existing cwd is as good a fallback as any. */ + } + } + /* * SIGINT, SIGQUIT and SIGPIPE may have been set to ignored by * our parent, particularly by things like sh -c 'pterm &' and @@ -1264,7 +1281,7 @@ static const char *pty_init(Seat *seat, Backend **backend_handle, cmd = pty_argv[0]; *backend_handle= pty_backend_create( - seat, logctx, conf, pty_argv, cmd, modes, false); + seat, logctx, conf, pty_argv, cmd, modes, false, NULL, NULL); *realhost = dupstr(""); return NULL; } @@ -1526,18 +1543,24 @@ static int pty_exitcode(Backend *be) return WEXITSTATUS(pty->exit_code); } -ptrlen pty_backend_exit_signame(Backend *be, char **aux_msg) +int pty_backend_exit_signum(Backend *be) { Pty *pty = container_of(be, Pty, backend); - int sig; + if (!pty->finished || !WIFSIGNALED(pty->exit_code)) + return -1; + + return WTERMSIG(pty->exit_code); +} + +ptrlen pty_backend_exit_signame(Backend *be, char **aux_msg) +{ *aux_msg = NULL; - if (!pty->finished || !WIFSIGNALED(pty->exit_code)) + int sig = pty_backend_exit_signum(be); + if (sig < 0) return PTRLEN_LITERAL(""); - sig = WTERMSIG(pty->exit_code); - #define TRANSLATE_SIGNAL(s) do \ { \ if (sig == SIG ## s) \ diff --git a/unix/uxser.c b/unix/uxser.c index 2239154..135a658 100644 --- a/unix/uxser.c +++ b/unix/uxser.c @@ -417,9 +417,9 @@ static void serial_uxsel_setup(Serial *serial) int rwx = 0; if (serial->inbufsize <= SERIAL_MAX_BACKLOG) - rwx |= 1; + rwx |= SELECT_R; if (bufchain_size(&serial->output_data)) - rwx |= 2; /* might also want to write to it */ + rwx |= SELECT_W; /* might also want to write to it */ uxsel_set(serial->fd, rwx, serial_select_result); } diff --git a/unix/uxserver.c b/unix/uxserver.c index 0e7a451..8fdc138 100644 --- a/unix/uxserver.c +++ b/unix/uxserver.c @@ -112,19 +112,26 @@ char *platform_get_x_display(void) { return NULL; } static bool verbose; -static void log_to_stderr(const char *msg) -{ - /* - * FIXME: in multi-connection proper-socket mode, prefix this with - * a connection id of some kind. We'll surely pass this in to - * sshserver.c by way of constructing a distinct LogPolicy per - * instance and making its containing structure contain the id - - * but we'll also have to arrange for those LogPolicy structs to - * be freed when the server instance terminates. - * - * For now, though, we only have one server instance, so no need. - */ +struct AuthPolicyShared { + struct AuthPolicy_ssh1_pubkey *ssh1keys; + struct AuthPolicy_ssh2_pubkey *ssh2keys; +}; + +struct AuthPolicy { + struct AuthPolicyShared *shared; + int kbdint_state; +}; + +struct server_instance { + unsigned id; + AuthPolicy ap; + LogPolicy logpolicy; +}; +static void log_to_stderr(unsigned id, const char *msg) +{ + if (id != (unsigned)-1) + fprintf(stderr, "#%u: ", id); fputs(msg, stderr); fputc('\n', stderr); fflush(stderr); @@ -132,13 +139,17 @@ static void log_to_stderr(const char *msg) static void server_eventlog(LogPolicy *lp, const char *event) { + struct server_instance *inst = container_of( + lp, struct server_instance, logpolicy); if (verbose) - log_to_stderr(event); + log_to_stderr(inst->id, event); } static void server_logging_error(LogPolicy *lp, const char *event) { - log_to_stderr(event); /* unconditional */ + struct server_instance *inst = container_of( + lp, struct server_instance, logpolicy); + log_to_stderr(inst->id, event); /* unconditional */ } static int server_askappend( @@ -153,7 +164,6 @@ static const LogPolicyVtable server_logpolicy_vt = { server_askappend, server_logging_error, }; -LogPolicy server_logpolicy[1] = {{ &server_logpolicy_vt }}; struct AuthPolicy_ssh1_pubkey { RSAKey key; @@ -164,11 +174,6 @@ struct AuthPolicy_ssh2_pubkey { struct AuthPolicy_ssh2_pubkey *next; }; -struct AuthPolicy { - struct AuthPolicy_ssh1_pubkey *ssh1keys; - struct AuthPolicy_ssh2_pubkey *ssh2keys; - int kbdint_state; -}; unsigned auth_methods(AuthPolicy *ap) { return (AUTHMETHOD_PUBLICKEY | AUTHMETHOD_PASSWORD | AUTHMETHOD_KBDINT | @@ -212,7 +217,7 @@ int auth_password(AuthPolicy *ap, ptrlen username, ptrlen password, bool auth_publickey(AuthPolicy *ap, ptrlen username, ptrlen public_blob) { struct AuthPolicy_ssh2_pubkey *iter; - for (iter = ap->ssh2keys; iter; iter = iter->next) { + for (iter = ap->shared->ssh2keys; iter; iter = iter->next) { if (ptrlen_eq_ptrlen(public_blob, iter->public_blob)) return true; } @@ -222,7 +227,7 @@ RSAKey *auth_publickey_ssh1( AuthPolicy *ap, ptrlen username, mp_int *rsa_modulus) { struct AuthPolicy_ssh1_pubkey *iter; - for (iter = ap->ssh1keys; iter; iter = iter->next) { + for (iter = ap->shared->ssh1keys; iter; iter = iter->next) { if (mp_cmp_eq(rsa_modulus, iter->key.modulus)) return &iter->key; } @@ -230,10 +235,11 @@ RSAKey *auth_publickey_ssh1( } AuthKbdInt *auth_kbdint_prompts(AuthPolicy *ap, ptrlen username) { - AuthKbdInt *aki = snew(AuthKbdInt); + AuthKbdInt *aki; switch (ap->kbdint_state) { case 0: + aki = snew(AuthKbdInt); aki->title = dupstr("Initial double prompt"); aki->instruction = dupstr("First prompt should echo, second should not"); @@ -245,6 +251,7 @@ AuthKbdInt *auth_kbdint_prompts(AuthPolicy *ap, ptrlen username) aki->prompts[1].echo = false; return aki; case 1: + aki = snew(AuthKbdInt); aki->title = dupstr("Zero-prompt step"); aki->instruction = dupstr("Shouldn't see any prompts this time"); aki->nprompts = 0; @@ -305,9 +312,42 @@ static void show_help(FILE *fp) safety_warning(fp); fputs("\n" "usage: uppity [options]\n" - "options: --hostkey KEY SSH host key (need at least one)\n" + "options: --listen PORT listen to a port on localhost\n" + " --listen-once (with --listen) stop after one " + "connection\n" + " --hostkey KEY SSH host key (need at least one)\n" + " --rsakexkey KEY key for SSH-2 RSA key exchange " + "(in SSH-1 format)\n" " --userkey KEY public key" " acceptable for user authentication\n" + " --sessiondir DIR cwd for session subprocess (default $HOME)\n" + " --bannertext TEXT send TEXT as SSH-2 auth banner\n" + " --bannerfile FILE send contents of FILE as SSH-2 auth " + "banner\n" + " --kexinit-kex STR override list of SSH-2 KEX methods\n" + " --kexinit-hostkey STR override list of SSH-2 host key " + "types\n" + " --kexinit-cscipher STR override list of SSH-2 " + "client->server ciphers\n" + " --kexinit-sccipher STR override list of SSH-2 " + "server->client ciphers\n" + " --kexinit-csmac STR override list of SSH-2 " + "client->server MACs\n" + " --kexinit-scmac STR override list of SSH-2 " + "server->client MACs\n" + " --kexinit-cscomp STR override list of SSH-2 " + "c->s compression types\n" + " --kexinit-sccomp STR override list of SSH-2 " + "s->c compression types\n" + " --ssh1-ciphers STR override list of SSH-1 ciphers\n" + " --ssh1-no-compression forbid compression in SSH-1\n" + " --exitsignum send buggy numeric \"exit-signal\" " + "message\n" + " --verbose print event log messages to standard " + "output\n" + " --sshlog FILE write SSH packet log to FILE\n" + " --sshrawlog FILE write SSH packets + raw data log" + " to FILE\n" "also: uppity --help show this text\n" " uppity --version show version information\n" "\n", fp); @@ -324,11 +364,20 @@ static void show_version_and_exit(void) const bool buildinfo_gtk_relevant = false; +static bool listening = false, listen_once = false; static bool finished = false; -void server_instance_terminated(void) +void server_instance_terminated(LogPolicy *lp) { - /* FIXME: change policy here if we're running in a listening loop */ - finished = true; + struct server_instance *inst = container_of( + lp, struct server_instance, logpolicy); + + if (listening && !listen_once) { + log_to_stderr(inst->id, "connection terminated"); + } else { + finished = true; + } + + sfree(inst); } static bool longoptarg(const char *arg, const char *expected, @@ -353,6 +402,121 @@ static bool longoptarg(const char *arg, const char *expected, return false; } +static bool longoptnoarg(const char *arg, const char *expected) +{ + int len = strlen(expected); + if (memcmp(arg, expected, len)) + return false; + if (arg[len] == '=') { + fprintf(stderr, "%s: option %s expects no argument\n", + appname, expected); + exit(1); + } else if (arg[len] == '\0') { + return true; + } + return false; +} + +struct server_config { + Conf *conf; + const SshServerConfig *ssc; + + ssh_key **hostkeys; + int nhostkeys; + + RSAKey *hostkey1; + + struct AuthPolicyShared *ap_shared; + + unsigned next_id; + + Socket *listening_socket; + Plug listening_plug; +}; + +static Plug *server_conn_plug( + struct server_config *cfg, struct server_instance **inst_out) +{ + struct server_instance *inst = snew(struct server_instance); + + memset(inst, 0, sizeof(*inst)); + + inst->id = cfg->next_id++; + inst->ap.shared = cfg->ap_shared; + inst->logpolicy.vt = &server_logpolicy_vt; + + if (inst_out) + *inst_out = inst; + + return ssh_server_plug( + cfg->conf, cfg->ssc, cfg->hostkeys, cfg->nhostkeys, cfg->hostkey1, + &inst->ap, &inst->logpolicy, &unix_live_sftpserver_vt); +} + +static void server_log(Plug *plug, int type, SockAddr *addr, int port, + const char *error_msg, int error_code) +{ + log_to_stderr((unsigned)-1, error_msg); +} + +static void server_closing(Plug *plug, const char *error_msg, int error_code, + bool calling_back) +{ + log_to_stderr((unsigned)-1, error_msg); +} + +static int server_accepting(Plug *p, accept_fn_t constructor, accept_ctx_t ctx) +{ + struct server_config *cfg = container_of( + p, struct server_config, listening_plug); + Socket *s; + const char *err; + + struct server_instance *inst; + + if (listen_once) { + if (!cfg->listening_socket) /* in case of rapid double-accept */ + return 1; + sk_close(cfg->listening_socket); + cfg->listening_socket = NULL; + } + + unsigned old_next_id = cfg->next_id; + + Plug *plug = server_conn_plug(cfg, &inst); + s = constructor(ctx, plug); + if ((err = sk_socket_error(s)) != NULL) + return 1; + + SocketPeerInfo *pi = sk_peer_info(s); + + if (!sk_peer_trusted(s)) { + fprintf(stderr, "rejected connection from %s (untrustworthy peer)\n", + pi->log_text); + sk_free_peer_info(pi); + sk_close(s); + cfg->next_id = old_next_id; + return 1; + } + + char *msg = dupprintf("new connection from %s", pi->log_text); + log_to_stderr(inst->id, msg); + sfree(msg); + sk_free_peer_info(pi); + + sk_set_frozen(s, false); + ssh_server_start(plug, s); + return 0; +} + +static const PlugVtable server_plugvt = { + server_log, + server_closing, + NULL, /* recv */ + NULL, /* send */ + server_accepting +}; + int main(int argc, char **argv) { int *fdlist; @@ -360,19 +524,25 @@ int main(int argc, char **argv) int i, fdstate; size_t fdsize; unsigned long now; + int listen_port = -1; ssh_key **hostkeys = NULL; size_t nhostkeys = 0, hostkeysize = 0; RSAKey *hostkey1 = NULL; - AuthPolicy ap; + struct AuthPolicyShared aps; + SshServerConfig ssc; + + Conf *conf = make_ssh_server_conf(); - Conf *conf = conf_new(); - load_open_settings(NULL, conf); + aps.ssh1keys = NULL; + aps.ssh2keys = NULL; - ap.kbdint_state = 0; - ap.ssh1keys = NULL; - ap.ssh2keys = NULL; + memset(&ssc, 0, sizeof(ssc)); + + ssc.session_starting_dir = getenv("HOME"); + ssc.ssh1_cipher_mask = SSH1_SUPPORTED_CIPHER_MASK; + ssc.ssh1_allow_compression = true; if (argc <= 1) { /* @@ -392,10 +562,14 @@ int main(int argc, char **argv) if (!strcmp(arg, "--help")) { show_help(stdout); exit(0); - } else if (!strcmp(arg, "--version")) { + } else if (longoptnoarg(arg, "--version")) { show_version_and_exit(); - } else if (!strcmp(arg, "--verbose") || !strcmp(arg, "-v")) { + } else if (longoptnoarg(arg, "--verbose") || !strcmp(arg, "-v")) { verbose = true; + } else if (longoptarg(arg, "--listen", &val, &argc, &argv)) { + listen_port = atoi(val); + } else if (!strcmp(arg, "--listen-once")) { + listen_once = true; } else if (longoptarg(arg, "--hostkey", &val, &argc, &argv)) { Filename *keyfile; int keytype; @@ -452,6 +626,35 @@ int main(int argc, char **argv) key_type_to_str(keytype)); exit(1); } + } else if (longoptarg(arg, "--rsakexkey", &val, &argc, &argv)) { + Filename *keyfile; + int keytype; + const char *error; + + keyfile = filename_from_str(val); + keytype = key_type(keyfile); + + if (keytype != SSH_KEYTYPE_SSH1) { + fprintf(stderr, "%s: '%s' is not loadable as an SSH-1 format " + "private key (%s)", appname, val, + key_type_to_str(keytype)); + exit(1); + } + + if (ssc.rsa_kex_key) { + freersakey(ssc.rsa_kex_key); + } else { + ssc.rsa_kex_key = snew(RSAKey); + } + + if (!rsa_ssh1_loadkey(keyfile, ssc.rsa_kex_key, + NULL, &error)) { + fprintf(stderr, "%s: unable to load RSA kex key '%s': " + "%s\n", appname, val, error); + exit(1); + } + + ssc.rsa_kex_key->sshk.vt = &ssh_rsa; } else if (longoptarg(arg, "--userkey", &val, &argc, &argv)) { Filename *keyfile; int keytype; @@ -478,8 +681,8 @@ int main(int argc, char **argv) memcpy(blob, sb->u, sb->len); node->public_blob = make_ptrlen(blob, sb->len); - node->next = ap.ssh2keys; - ap.ssh2keys = node; + node->next = aps.ssh2keys; + aps.ssh2keys = node; strbuf_free(sb); } else if (keytype == SSH_KEYTYPE_SSH1_PUBLIC) { @@ -498,8 +701,8 @@ int main(int argc, char **argv) BinarySource_BARE_INIT(src, sb->u, sb->len); get_rsa_ssh1_pub(src, &node->key, RSA_SSH1_EXPONENT_FIRST); - node->next = ap.ssh1keys; - ap.ssh1keys = node; + node->next = aps.ssh1keys; + aps.ssh1keys = node; strbuf_free(sb); } else { @@ -507,6 +710,64 @@ int main(int argc, char **argv) "(%s)\n", appname, val, key_type_to_str(keytype)); exit(1); } + } else if (longoptarg(arg, "--bannerfile", &val, &argc, &argv)) { + FILE *fp = fopen(val, "r"); + if (!fp) { + fprintf(stderr, "%s: %s: open: %s\n", appname, + val, strerror(errno)); + exit(1); + } + strbuf *sb = strbuf_new(); + if (!read_file_into(BinarySink_UPCAST(sb), fp)) { + fprintf(stderr, "%s: %s: read: %s\n", appname, + val, strerror(errno)); + exit(1); + } + fclose(fp); + ssc.banner = ptrlen_from_strbuf(sb); + } else if (longoptarg(arg, "--bannertext", &val, &argc, &argv)) { + ssc.banner = ptrlen_from_asciz(val); + } else if (longoptarg(arg, "--sessiondir", &val, &argc, &argv)) { + ssc.session_starting_dir = val; + } else if (longoptarg(arg, "--kexinit-kex", &val, &argc, &argv)) { + ssc.kex_override[KEXLIST_KEX] = ptrlen_from_asciz(val); + } else if (longoptarg(arg, "--kexinit-hostkey", &val, &argc, &argv)) { + ssc.kex_override[KEXLIST_HOSTKEY] = ptrlen_from_asciz(val); + } else if (longoptarg(arg, "--kexinit-cscipher", &val, &argc, &argv)) { + ssc.kex_override[KEXLIST_CSCIPHER] = ptrlen_from_asciz(val); + } else if (longoptarg(arg, "--kexinit-csmac", &val, &argc, &argv)) { + ssc.kex_override[KEXLIST_CSMAC] = ptrlen_from_asciz(val); + } else if (longoptarg(arg, "--kexinit-cscomp", &val, &argc, &argv)) { + ssc.kex_override[KEXLIST_CSCOMP] = ptrlen_from_asciz(val); + } else if (longoptarg(arg, "--kexinit-sccipher", &val, &argc, &argv)) { + ssc.kex_override[KEXLIST_SCCIPHER] = ptrlen_from_asciz(val); + } else if (longoptarg(arg, "--kexinit-scmac", &val, &argc, &argv)) { + ssc.kex_override[KEXLIST_SCMAC] = ptrlen_from_asciz(val); + } else if (longoptarg(arg, "--kexinit-sccomp", &val, &argc, &argv)) { + ssc.kex_override[KEXLIST_SCCOMP] = ptrlen_from_asciz(val); + } else if (longoptarg(arg, "--ssh1-ciphers", &val, &argc, &argv)) { + ptrlen list = ptrlen_from_asciz(val); + ptrlen word; + unsigned long mask = 0; + while (word = ptrlen_get_word(&list, ","), word.len != 0) { + +#define SSH1_CIPHER_CASE(bitpos, name) \ + if (ptrlen_eq_string(word, name)) { \ + mask |= 1U << bitpos; \ + continue; \ + } + SSH1_SUPPORTED_CIPHER_LIST(SSH1_CIPHER_CASE); +#undef SSH1_CIPHER_CASE + + fprintf(stderr, "%s: unrecognised SSH-1 cipher '%.*s'\n", + appname, PTRLEN_PRINTF(word)); + exit(1); + } + ssc.ssh1_cipher_mask = mask; + } else if (longoptnoarg(arg, "--ssh1-no-compression")) { + ssc.ssh1_allow_compression = false; + } else if (longoptnoarg(arg, "--exitsignum")) { + ssc.exit_signal_numeric = true; } else if (longoptarg(arg, "--sshlog", &val, &argc, &argv) || longoptarg(arg, "-sshlog", &val, &argc, &argv)) { Filename *logfile = filename_from_str(val); @@ -546,11 +807,30 @@ int main(int argc, char **argv) sk_init(); uxsel_init(); - { - Plug *plug = ssh_server_plug( - conf, hostkeys, nhostkeys, hostkey1, &ap, server_logpolicy, - &unix_live_sftpserver_vt); + struct server_config scfg; + scfg.conf = conf; + scfg.ssc = &ssc; + scfg.hostkeys = hostkeys; + scfg.nhostkeys = nhostkeys; + scfg.hostkey1 = hostkey1; + scfg.ap_shared = &aps; + scfg.next_id = 0; + + if (listen_port >= 0) { + listening = true; + scfg.listening_plug.vt = &server_plugvt; + scfg.listening_socket = sk_newlistener( + NULL, listen_port, &scfg.listening_plug, true, ADDRTYPE_UNSPEC); + + char *msg = dupprintf("%s: listening on port %d", + appname, listen_port); + log_to_stderr(-1, msg); + sfree(msg); + } else { + struct server_instance *inst; + Plug *plug = server_conn_plug(&scfg, &inst); ssh_server_start(plug, make_fd_socket(0, 1, -1, plug)); + log_to_stderr(inst->id, "speaking SSH on stdio"); } now = GETTICKCOUNT(); diff --git a/unix/uxsftp.c b/unix/uxsftp.c index 69abf72..9b9592e 100644 --- a/unix/uxsftp.c +++ b/unix/uxsftp.c @@ -12,12 +12,15 @@ #include #include #include -#include #include "putty.h" #include "ssh.h" #include "psftp.h" +#if HAVE_GLOB_H +#include +#endif + /* * In PSFTP our selects are synchronous, so these functions are * empty stubs. @@ -358,6 +361,7 @@ int test_wildcard(const char *name, bool cmdline) */ return WCTYPE_NONEXISTENT; } else { +#if HAVE_GLOB_H glob_t globbed; int ret = WCTYPE_NONEXISTENT; @@ -368,12 +372,18 @@ int test_wildcard(const char *name, bool cmdline) } return ret; +#else + /* On a system without glob.h, we just have to return a + * failure code */ + return WCTYPE_NONEXISTENT; +#endif } } /* * Actually return matching file names for a local wildcard. */ +#if HAVE_GLOB_H struct WildcardMatcher { glob_t globbed; int i; @@ -400,6 +410,20 @@ void finish_wildcard_matching(WildcardMatcher *dir) { globfree(&dir->globbed); sfree(dir); } +#else +WildcardMatcher *begin_wildcard_matching(const char *name) +{ + return NULL; +} +char *wildcard_get_filename(WildcardMatcher *dir) +{ + unreachable("Can't construct a valid WildcardMatcher without "); +} +void finish_wildcard_matching(WildcardMatcher *dir) +{ + unreachable("Can't construct a valid WildcardMatcher without "); +} +#endif char *stripslashes(const char *str, bool local) { @@ -464,8 +488,10 @@ static int ssh_sftp_do_select(bool include_stdin, bool no_fds_ok) for (fd = first_fd(&fdstate, &rwx); fd >= 0; fd = next_fd(&fdstate, &rwx)) i++; - if (i < 1 && !no_fds_ok && !toplevel_callback_pending()) + if (i < 1 && !no_fds_ok && !toplevel_callback_pending()) { + pollwrap_free(pw); return -1; /* doom */ + } /* Expand the fdlist buffer if necessary. */ sgrowarray(fdlist, fdsize, i); diff --git a/unix/uxsftpserver.c b/unix/uxsftpserver.c index 6fab0ba..a90344e 100644 --- a/unix/uxsftpserver.c +++ b/unix/uxsftpserver.c @@ -412,6 +412,16 @@ static void uss_fstat(SftpServer *srv, SftpReplyBuilder *reply, } } +#if !HAVE_FUTIMES +static inline int futimes(int fd, const struct timeval tv[2]) +{ + /* If the OS doesn't support futimes(3) then we have to pretend it + * always returns failure */ + errno = EINVAL; + return -1; +} +#endif + /* * The guts of setstat and fsetstat, macroised so that they can call * fchown(fd,...) or chown(path,...) depending on parameters. diff --git a/unix/uxshare.c b/unix/uxshare.c index 2de65b5..0c5265b 100644 --- a/unix/uxshare.c +++ b/unix/uxshare.c @@ -22,6 +22,9 @@ #define CONNSHARE_SOCKETDIR_PREFIX "/tmp/putty-connshare" #define SALT_FILENAME "salt" #define SALT_SIZE 64 +#ifndef PIPE_BUF +#define PIPE_BUF _POSIX_PIPE_BUF +#endif static char *make_parentdir_name(void) { diff --git a/unix/uxstore.c b/unix/uxstore.c index c66d92b..756b10c 100644 --- a/unix/uxstore.c +++ b/unix/uxstore.c @@ -301,15 +301,16 @@ static int keycmp(void *av, void *bv) return strcmp(a->key, b->key); } -void provide_xrm_string(char *string) +void provide_xrm_string(const char *string, const char *progname) { - char *p, *q, *key; + const char *p, *q; + char *key; struct skeyval *xrms, *ret; p = q = strchr(string, ':'); if (!q) { - fprintf(stderr, "pterm: expected a colon in resource string" - " \"%s\"\n", string); + fprintf(stderr, "%s: expected a colon in resource string" + " \"%s\"\n", progname, string); return; } q++; diff --git a/unix/uxutils.c b/unix/uxutils.c index fcbcc4d..7b63842 100644 --- a/unix/uxutils.c +++ b/unix/uxutils.c @@ -1,6 +1,8 @@ +#include "putty.h" #include "ssh.h" -#if defined __linux__ && (defined __arm__ || defined __aarch64__) +#if defined __linux__ && (defined __arm__ || defined __aarch64__) && \ + HAVE_SYS_AUXV_H && HAVE_ASM_HWCAP_H #include #include diff --git a/utils.c b/utils.c index 96024d2..9824110 100644 --- a/utils.c +++ b/utils.c @@ -308,7 +308,10 @@ int string_length_for_printf(size_t s) #endif /* Also lack of vsnprintf before VS2015 */ -#if defined _WINDOWS && !defined __WINE__ && _MSC_VER < 1900 +#if defined _WINDOWS && \ + !defined __MINGW32__ && \ + !defined __WINE__ && \ + _MSC_VER < 1900 #define vsnprintf _vsnprintf #endif @@ -501,6 +504,20 @@ char *fgetline(FILE *fp) return ret; } +/* + * Read an entire file into a BinarySink. + */ +bool read_file_into(BinarySink *bs, FILE *fp) +{ + char buf[4096]; + while (1) { + size_t retd = fread(buf, 1, sizeof(buf), fp); + if (retd == 0) + return !ferror(fp); + put_data(bs, buf, retd); + } +} + /* * Perl-style 'chomp', for a line we just read with fgetline. Unlike * Perl chomp, however, we're deliberately forgiving of strange @@ -938,6 +955,26 @@ bool ptrlen_endswith(ptrlen whole, ptrlen suffix, ptrlen *tail) return false; } +ptrlen ptrlen_get_word(ptrlen *input, const char *separators) +{ + const char *p = input->ptr, *end = p + input->len; + ptrlen toret; + + while (p < end && strchr(separators, *p)) + p++; + toret.ptr = p; + while (p < end && !strchr(separators, *p)) + p++; + toret.len = p - (const char *)toret.ptr; + + size_t to_consume = p - (const char *)input->ptr; + assert(to_consume <= input->len); + input->ptr = (const char *)input->ptr + to_consume; + input->len -= to_consume; + + return toret; +} + char *mkstr(ptrlen pl) { char *p = snewn(pl.len + 1, char); diff --git a/uxconfig.in b/uxconfig.in new file mode 100644 index 0000000..c1d7985 --- /dev/null +++ b/uxconfig.in @@ -0,0 +1,171 @@ +/* uxconfig.in. Generated from configure.ac by autoheader. */ + +/* Define to 1 if you have the header file. */ +#undef HAVE_ASM_HWCAP_H + +/* Define if clock_gettime() is available */ +#undef HAVE_CLOCK_GETTIME + +/* Define to 1 if you have the declaration of `CLOCK_MONOTONIC', and to 0 if + you don't. */ +#undef HAVE_DECL_CLOCK_MONOTONIC + +/* Define to 1 if you have the `dirfd' function. */ +#undef HAVE_DIRFD + +/* Define to 1 if you have the `endpwent' function. */ +#undef HAVE_ENDPWENT + +/* Define to 1 if you have the `fstatat' function. */ +#undef HAVE_FSTATAT + +/* Define to 1 if you have the `futimes' function. */ +#undef HAVE_FUTIMES + +/* Define to 1 if you have the `getaddrinfo' function. */ +#undef HAVE_GETADDRINFO + +/* Define to 1 if you have the header file. */ +#undef HAVE_GLOB_H + +/* Define to 1 if you have the header file. */ +#undef HAVE_GSSAPI_GSSAPI_H + +/* Define to 1 if you have the header file. */ +#undef HAVE_INTTYPES_H + +/* Define if libX11.a is available */ +#undef HAVE_LIBX11 + +/* Define to 1 if you have the header file. */ +#undef HAVE_MEMORY_H + +/* Define to 1 if you have the `pango_font_family_is_monospace' function. */ +#undef HAVE_PANGO_FONT_FAMILY_IS_MONOSPACE + +/* Define to 1 if you have the `pango_font_map_list_families' function. */ +#undef HAVE_PANGO_FONT_MAP_LIST_FAMILIES + +/* Define to 1 if you have the `posix_openpt' function. */ +#undef HAVE_POSIX_OPENPT + +/* Define to 1 if you have the `ptsname' function. */ +#undef HAVE_PTSNAME + +/* Define to 1 if you have the `setpwent' function. */ +#undef HAVE_SETPWENT + +/* Define to 1 if you have the `setresuid' function. */ +#undef HAVE_SETRESUID + +/* Define if SO_PEERCRED works in the Linux fashion. */ +#undef HAVE_SO_PEERCRED + +/* Define to 1 if you have the header file. */ +#undef HAVE_STDINT_H + +/* Define to 1 if you have the header file. */ +#undef HAVE_STDLIB_H + +/* Define to 1 if you have the header file. */ +#undef HAVE_STRINGS_H + +/* Define to 1 if you have the header file. */ +#undef HAVE_STRING_H + +/* Define to 1 if you have the `strsignal' function. */ +#undef HAVE_STRSIGNAL + +/* Define to 1 if you have the header file. */ +#undef HAVE_SYS_AUXV_H + +/* Define to 1 if you have the header file. */ +#undef HAVE_SYS_STAT_H + +/* Define to 1 if you have the header file. */ +#undef HAVE_SYS_TYPES_H + +/* Define to 1 if you have the header file. */ +#undef HAVE_UNISTD_H + +/* Define to 1 if you have the `updwtmpx' function. */ +#undef HAVE_UPDWTMPX + +/* Define to 1 if you have the header file. */ +#undef HAVE_UTMPX_H + +/* Define if we could not find a gssapi library */ +#undef NO_GSSAPI_LIB + +/* Define if we could not find libdl. */ +#undef NO_LIBDL + +/* Define if building with GTK for MacOS. */ +#undef OSX_GTK + +/* Name of package */ +#undef PACKAGE + +/* Define to the address where bug reports for this package should be sent. */ +#undef PACKAGE_BUGREPORT + +/* Define to the full name of this package. */ +#undef PACKAGE_NAME + +/* Define to the full name and version of this package. */ +#undef PACKAGE_STRING + +/* Define to the one symbol short name of this package. */ +#undef PACKAGE_TARNAME + +/* Define to the home page for this package. */ +#undef PACKAGE_URL + +/* Define to the version of this package. */ +#undef PACKAGE_VERSION + +/* Define to 1 if you have the ANSI C header files. */ +#undef STDC_HEADERS + +/* Version number of package */ +#undef VERSION + +/* Define if building with GSSAPI support. */ +#undef WITH_GSSAPI + + +/* Convert autoconf definitions to ones that PuTTY wants. */ + +#ifndef HAVE_GETADDRINFO +# define NO_IPV6 +#endif +#ifndef HAVE_SETRESUID +# define HAVE_NO_SETRESUID +#endif +#ifndef HAVE_STRSIGNAL +# define HAVE_NO_STRSIGNAL +#endif +#if !defined(HAVE_UTMPX_H) || !defined(HAVE_UPDWTMPX) +# define OMIT_UTMP +#endif +#ifndef HAVE_PTSNAME +# define BSD_PTYS +#endif +#ifndef HAVE_SYS_SELECT_H +# define HAVE_NO_SYS_SELECT_H +#endif +#ifndef HAVE_PANGO_FONT_FAMILY_IS_MONOSPACE +# define PANGO_PRE_1POINT4 +#endif +#ifndef HAVE_PANGO_FONT_MAP_LIST_FAMILIES +# define PANGO_PRE_1POINT6 +#endif +#if !defined(WITH_GSSAPI) +# define NO_GSSAPI +#endif +#if !defined(NO_GSSAPI) && defined(NO_LIBDL) +# if !defined(HAVE_GSSAPI_GSSAPI_H) || defined(NO_GSSAPI_LIB) +# define NO_GSSAPI +# endif +#endif + diff --git a/version.h b/version.h index 4c07c2a..278b842 100644 --- a/version.h +++ b/version.h @@ -1,6 +1,6 @@ /* Generated by automated build script */ -#define RELEASE 0.71 -#define TEXTVER "Release 0.71" -#define SSHVER "-Release-0.71" -#define BINARY_VERSION 0,71,0,0 +#define RELEASE 0.72 +#define TEXTVER "Release 0.72" +#define SSHVER "-Release-0.72" +#define BINARY_VERSION 0,72,0,0 #define SOURCE_COMMIT "See https://github.com/NoMoreFood/putty-cac" diff --git a/windows/DEVCPP/plink/plink.dev b/windows/DEVCPP/plink/plink.dev index b5d899f..6dfd9c1 100644 --- a/windows/DEVCPP/plink/plink.dev +++ b/windows/DEVCPP/plink/plink.dev @@ -1,1501 +1,1511 @@ -# DEV-C++ 5 Project File - plink.dev -# ** DO NOT EDIT ** - -[Project] -FileName=plink.dev -Name=plink -Ver=1 -IsCpp=1 -Type=1 -Compiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ -CppCompiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ -Includes=..\..\..\.;..\..\..\charset;..\..\..\windows;..\..\..\unix -Linker=-ladvapi32 -lcomctl32 -lcomdlg32 -lgdi32 -limm32 -lshell32 -luser32 -lwinmm -lwinspool_@@_ -Libs= -UnitCount=145 -Folders="Header Files","Resource Files","Source Files" -ObjFiles= -PrivateResource=plink_private.rc -ResourceIncludes=..\..\..\WINDOWS -MakeIncludes= -Icon= -ExeOutput= -ObjectOutput= -OverrideOutput=0 -OverrideOutputName=plink.exe -HostApplication= -CommandLine= -UseCustomMakefile=0 -CustomMakefile= -IncludeVersionInfo=0 -SupportXPThemes=0 -CompilerSet=0 -CompilerSettings=0000000000000000000000 - -[Unit1] -FileName=..\..\..\agentf.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit2] -FileName=..\..\..\aqsync.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit3] -FileName=..\..\..\be_all_s.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit4] -FileName=..\..\..\be_misc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit5] -FileName=..\..\..\callback.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit6] -FileName=..\..\..\cmdline.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit7] -FileName=..\..\..\conf.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit8] -FileName=..\..\..\cproxy.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit9] -FileName=..\..\..\ecc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit10] -FileName=..\..\..\errsock.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit11] -FileName=..\..\..\ldisc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit12] -FileName=..\..\..\logging.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit13] -FileName=..\..\..\mainchan.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit14] -FileName=..\..\..\marshal.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit15] -FileName=..\..\..\memory.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit16] -FileName=..\..\..\misc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit17] -FileName=..\..\..\miscucs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit18] -FileName=..\..\..\mpint.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit19] -FileName=..\..\..\noshare.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit20] -FileName=..\..\..\noterm.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit21] -FileName=..\..\..\nullplug.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit22] -FileName=..\..\..\pgssapi.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit23] -FileName=..\..\..\pinger.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit24] -FileName=..\..\..\portfwd.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit25] -FileName=..\..\..\proxy.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit26] -FileName=..\..\..\raw.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit27] -FileName=..\..\..\rlogin.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit28] -FileName=..\..\..\sessprep.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit29] -FileName=..\..\..\settings.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit30] -FileName=..\..\..\ssh.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit31] -FileName=..\..\..\ssh1bpp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit32] -FileName=..\..\..\ssh1censor.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit33] -FileName=..\..\..\ssh1connection-client.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit34] -FileName=..\..\..\ssh1connection.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit35] -FileName=..\..\..\ssh1login.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit36] -FileName=..\..\..\ssh2bpp-bare.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit37] -FileName=..\..\..\ssh2bpp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit38] -FileName=..\..\..\ssh2censor.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit39] -FileName=..\..\..\ssh2connection-client.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit40] -FileName=..\..\..\ssh2connection.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit41] -FileName=..\..\..\ssh2kex-client.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit42] -FileName=..\..\..\ssh2transhk.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit43] -FileName=..\..\..\ssh2transport.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit44] -FileName=..\..\..\ssh2userauth.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit45] -FileName=..\..\..\sshaes.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit46] -FileName=..\..\..\ssharcf.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit47] -FileName=..\..\..\sshauxcrypt.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit48] -FileName=..\..\..\sshblowf.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit49] -FileName=..\..\..\sshccp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit50] -FileName=..\..\..\sshcommon.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit51] -FileName=..\..\..\sshcrc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit52] -FileName=..\..\..\sshcrcda.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit53] -FileName=..\..\..\sshdes.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit54] -FileName=..\..\..\sshdh.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit55] -FileName=..\..\..\sshdss.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit56] -FileName=..\..\..\sshecc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit57] -FileName=..\..\..\sshgssc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit58] -FileName=..\..\..\sshhmac.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit59] -FileName=..\..\..\sshmac.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit60] -FileName=..\..\..\sshmd5.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit61] -FileName=..\..\..\sshprng.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit62] -FileName=..\..\..\sshpubk.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit63] -FileName=..\..\..\sshrand.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit64] -FileName=..\..\..\sshrsa.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit65] -FileName=..\..\..\sshsh256.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit66] -FileName=..\..\..\sshsh512.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit67] -FileName=..\..\..\sshsha.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit68] -FileName=..\..\..\sshshare.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit69] -FileName=..\..\..\sshverstring.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit70] -FileName=..\..\..\sshzlib.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit71] -FileName=..\..\..\stripctrl.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit72] -FileName=..\..\..\telnet.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit73] -FileName=..\..\..\timing.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit74] -FileName=..\..\..\tree234.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit75] -FileName=..\..\..\utils.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit76] -FileName=..\..\..\version.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit77] -FileName=..\..\..\wcwidth.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit78] -FileName=..\..\..\wildcard.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit79] -FileName=..\..\..\windows\wincapi.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit80] -FileName=..\..\..\windows\wincons.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit81] -FileName=..\..\..\windows\windefs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit82] -FileName=..\..\..\windows\wingss.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit83] -FileName=..\..\..\windows\winhandl.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit84] -FileName=..\..\..\windows\winhsock.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit85] -FileName=..\..\..\windows\winmisc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit86] -FileName=..\..\..\windows\winmiscs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit87] -FileName=..\..\..\windows\winnet.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit88] -FileName=..\..\..\windows\winnohlp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit89] -FileName=..\..\..\windows\winnoise.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit90] -FileName=..\..\..\windows\winnojmp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit91] -FileName=..\..\..\windows\winnpc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit92] -FileName=..\..\..\windows\winnps.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit93] -FileName=..\..\..\windows\winpgntc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit94] -FileName=..\..\..\windows\winplink.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit95] -FileName=..\..\..\windows\winproxy.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit96] -FileName=..\..\..\windows\winsecur.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit97] -FileName=..\..\..\windows\winser.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit98] -FileName=..\..\..\windows\winshare.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit99] -FileName=..\..\..\windows\winstore.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit100] -FileName=..\..\..\windows\wintime.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit101] -FileName=..\..\..\windows\winucs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit102] -FileName=..\..\..\windows\winx11.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit103] -FileName=..\..\..\x11fwd.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit104] -FileName=..\..\..\charset\charset.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit105] -FileName=..\..\..\defs.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit106] -FileName=..\..\..\ecc.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit107] -FileName=..\..\..\empty.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit108] -FileName=..\..\..\ldisc.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit109] -FileName=..\..\..\licence.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit110] -FileName=..\..\..\marshal.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit111] -FileName=..\..\..\misc.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit112] -FileName=..\..\..\mpint.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit113] -FileName=..\..\..\mpint_i.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit114] -FileName=..\..\..\network.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit115] -FileName=..\..\..\pageant.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit116] -FileName=..\..\..\pgssapi.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit117] -FileName=..\..\..\proxy.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit118] -FileName=..\..\..\putty.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit119] -FileName=..\..\..\puttymem.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit120] -FileName=..\..\..\puttyps.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit121] -FileName=..\..\..\ssh.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit122] -FileName=..\..\..\ssh1connection.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit123] -FileName=..\..\..\ssh2connection.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit124] -FileName=..\..\..\ssh2transport.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit125] -FileName=..\..\..\sshblowf.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit126] -FileName=..\..\..\sshbpp.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit127] -FileName=..\..\..\sshchan.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit128] -FileName=..\..\..\sshcr.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit129] -FileName=..\..\..\sshgss.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit130] -FileName=..\..\..\sshgssc.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit131] -FileName=..\..\..\sshppl.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit132] -FileName=..\..\..\sshsignals.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit133] -FileName=..\..\..\sshttymodes.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit134] -FileName=..\..\..\storage.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit135] -FileName=..\..\..\terminal.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit136] -FileName=..\..\..\tree234.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit137] -FileName=..\..\..\unix\unix.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit138] -FileName=..\..\..\version.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit139] -FileName=..\..\..\windows\rcstuff.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit140] -FileName=..\..\..\windows\wincapi.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit141] -FileName=..\..\..\windows\winhelp.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit142] -FileName=..\..\..\windows\winsecur.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit143] -FileName=..\..\..\windows\winstuff.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit144] -FileName=..\..\..\windows\plink.rc -Folder=Resource Files -Compile=1 -CompileCpp=1 -Link=0 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit145] -FileName=..\..\..\windows\putty.ico -Folder=Resource Files -Compile=0 -CompileCpp=0 -Link=0 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[VersionInfo] -Major=0 -Minor=0 -Release=1 -Build=1 -LanguageID=1033 -CharsetID=1252 -CompanyName= -FileVersion=0.1 -FileDescription= -InternalName= -LegalCopyright= -LegalTrademarks= -OriginalFilename=plink.exe -ProductName=plink -ProductVersion=0.1 -AutoIncBuildNr=0 +# DEV-C++ 5 Project File - plink.dev +# ** DO NOT EDIT ** + +[Project] +FileName=plink.dev +Name=plink +Ver=1 +IsCpp=1 +Type=1 +Compiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ +CppCompiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ +Includes=..\..\..\.;..\..\..\charset;..\..\..\windows;..\..\..\unix +Linker=-ladvapi32 -lcomctl32 -lcomdlg32 -lgdi32 -limm32 -lshell32 -luser32 -lwinmm -lwinspool_@@_ +Libs= +UnitCount=146 +Folders="Header Files","Resource Files","Source Files" +ObjFiles= +PrivateResource=plink_private.rc +ResourceIncludes=..\..\..\WINDOWS +MakeIncludes= +Icon= +ExeOutput= +ObjectOutput= +OverrideOutput=0 +OverrideOutputName=plink.exe +HostApplication= +CommandLine= +UseCustomMakefile=0 +CustomMakefile= +IncludeVersionInfo=0 +SupportXPThemes=0 +CompilerSet=0 +CompilerSettings=0000000000000000000000 + +[Unit1] +FileName=..\..\..\agentf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit2] +FileName=..\..\..\aqsync.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit3] +FileName=..\..\..\be_all_s.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit4] +FileName=..\..\..\be_misc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit5] +FileName=..\..\..\callback.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit6] +FileName=..\..\..\cmdline.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit7] +FileName=..\..\..\conf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit8] +FileName=..\..\..\cproxy.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit9] +FileName=..\..\..\ecc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit10] +FileName=..\..\..\errsock.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit11] +FileName=..\..\..\ldisc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit12] +FileName=..\..\..\logging.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit13] +FileName=..\..\..\mainchan.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit14] +FileName=..\..\..\marshal.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit15] +FileName=..\..\..\memory.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit16] +FileName=..\..\..\misc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit17] +FileName=..\..\..\miscucs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit18] +FileName=..\..\..\mpint.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit19] +FileName=..\..\..\noshare.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit20] +FileName=..\..\..\noterm.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit21] +FileName=..\..\..\nullplug.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit22] +FileName=..\..\..\pgssapi.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit23] +FileName=..\..\..\pinger.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit24] +FileName=..\..\..\portfwd.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit25] +FileName=..\..\..\proxy.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit26] +FileName=..\..\..\raw.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit27] +FileName=..\..\..\rlogin.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit28] +FileName=..\..\..\sessprep.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit29] +FileName=..\..\..\settings.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit30] +FileName=..\..\..\ssh.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit31] +FileName=..\..\..\ssh1bpp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit32] +FileName=..\..\..\ssh1censor.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit33] +FileName=..\..\..\ssh1connection-client.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit34] +FileName=..\..\..\ssh1connection.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit35] +FileName=..\..\..\ssh1login.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit36] +FileName=..\..\..\ssh2bpp-bare.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit37] +FileName=..\..\..\ssh2bpp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit38] +FileName=..\..\..\ssh2censor.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit39] +FileName=..\..\..\ssh2connection-client.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit40] +FileName=..\..\..\ssh2connection.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit41] +FileName=..\..\..\ssh2kex-client.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit42] +FileName=..\..\..\ssh2transhk.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit43] +FileName=..\..\..\ssh2transport.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit44] +FileName=..\..\..\ssh2userauth.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit45] +FileName=..\..\..\sshaes.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit46] +FileName=..\..\..\ssharcf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit47] +FileName=..\..\..\sshauxcrypt.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit48] +FileName=..\..\..\sshblowf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit49] +FileName=..\..\..\sshccp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit50] +FileName=..\..\..\sshcommon.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit51] +FileName=..\..\..\sshcrc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit52] +FileName=..\..\..\sshcrcda.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit53] +FileName=..\..\..\sshdes.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit54] +FileName=..\..\..\sshdh.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit55] +FileName=..\..\..\sshdss.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit56] +FileName=..\..\..\sshecc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit57] +FileName=..\..\..\sshgssc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit58] +FileName=..\..\..\sshhmac.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit59] +FileName=..\..\..\sshmac.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit60] +FileName=..\..\..\sshmd5.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit61] +FileName=..\..\..\sshprng.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit62] +FileName=..\..\..\sshpubk.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit63] +FileName=..\..\..\sshrand.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit64] +FileName=..\..\..\sshrsa.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit65] +FileName=..\..\..\sshsh256.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit66] +FileName=..\..\..\sshsh512.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit67] +FileName=..\..\..\sshsha.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit68] +FileName=..\..\..\sshshare.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit69] +FileName=..\..\..\sshverstring.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit70] +FileName=..\..\..\sshzlib.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit71] +FileName=..\..\..\stripctrl.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit72] +FileName=..\..\..\telnet.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit73] +FileName=..\..\..\timing.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit74] +FileName=..\..\..\tree234.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit75] +FileName=..\..\..\utils.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit76] +FileName=..\..\..\version.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit77] +FileName=..\..\..\wcwidth.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit78] +FileName=..\..\..\wildcard.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit79] +FileName=..\..\..\windows\wincapi.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit80] +FileName=..\..\..\windows\wincons.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit81] +FileName=..\..\..\windows\windefs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit82] +FileName=..\..\..\windows\wingss.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit83] +FileName=..\..\..\windows\winhandl.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit84] +FileName=..\..\..\windows\winhsock.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit85] +FileName=..\..\..\windows\winmisc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit86] +FileName=..\..\..\windows\winmiscs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit87] +FileName=..\..\..\windows\winnet.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit88] +FileName=..\..\..\windows\winnohlp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit89] +FileName=..\..\..\windows\winnoise.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit90] +FileName=..\..\..\windows\winnojmp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit91] +FileName=..\..\..\windows\winnpc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit92] +FileName=..\..\..\windows\winnps.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit93] +FileName=..\..\..\windows\winpgntc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit94] +FileName=..\..\..\windows\winplink.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit95] +FileName=..\..\..\windows\winproxy.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit96] +FileName=..\..\..\windows\winsecur.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit97] +FileName=..\..\..\windows\winser.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit98] +FileName=..\..\..\windows\winshare.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit99] +FileName=..\..\..\windows\winstore.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit100] +FileName=..\..\..\windows\wintime.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit101] +FileName=..\..\..\windows\winucs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit102] +FileName=..\..\..\windows\winx11.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit103] +FileName=..\..\..\x11fwd.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit104] +FileName=..\..\..\charset\charset.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit105] +FileName=..\..\..\defs.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit106] +FileName=..\..\..\ecc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit107] +FileName=..\..\..\empty.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit108] +FileName=..\..\..\ldisc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit109] +FileName=..\..\..\licence.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit110] +FileName=..\..\..\marshal.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit111] +FileName=..\..\..\misc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit112] +FileName=..\..\..\mpint.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit113] +FileName=..\..\..\mpint_i.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit114] +FileName=..\..\..\network.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit115] +FileName=..\..\..\pageant.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit116] +FileName=..\..\..\pgssapi.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit117] +FileName=..\..\..\proxy.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit118] +FileName=..\..\..\putty.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit119] +FileName=..\..\..\puttymem.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit120] +FileName=..\..\..\puttyps.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit121] +FileName=..\..\..\ssh.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit122] +FileName=..\..\..\ssh1connection.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit123] +FileName=..\..\..\ssh2connection.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit124] +FileName=..\..\..\ssh2transport.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit125] +FileName=..\..\..\sshblowf.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit126] +FileName=..\..\..\sshbpp.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit127] +FileName=..\..\..\sshchan.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit128] +FileName=..\..\..\sshcr.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit129] +FileName=..\..\..\sshgss.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit130] +FileName=..\..\..\sshgssc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit131] +FileName=..\..\..\sshppl.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit132] +FileName=..\..\..\sshserver.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit133] +FileName=..\..\..\sshsignals.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit134] +FileName=..\..\..\sshttymodes.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit135] +FileName=..\..\..\storage.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit136] +FileName=..\..\..\terminal.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit137] +FileName=..\..\..\tree234.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit138] +FileName=..\..\..\unix\unix.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit139] +FileName=..\..\..\version.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit140] +FileName=..\..\..\windows\rcstuff.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit141] +FileName=..\..\..\windows\wincapi.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit142] +FileName=..\..\..\windows\winhelp.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit143] +FileName=..\..\..\windows\winsecur.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit144] +FileName=..\..\..\windows\winstuff.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit145] +FileName=..\..\..\windows\plink.rc +Folder=Resource Files +Compile=1 +CompileCpp=1 +Link=0 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit146] +FileName=..\..\..\windows\putty.ico +Folder=Resource Files +Compile=0 +CompileCpp=0 +Link=0 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[VersionInfo] +Major=0 +Minor=0 +Release=1 +Build=1 +LanguageID=1033 +CharsetID=1252 +CompanyName= +FileVersion=0.1 +FileDescription= +InternalName= +LegalCopyright= +LegalTrademarks= +OriginalFilename=plink.exe +ProductName=plink +ProductVersion=0.1 +AutoIncBuildNr=0 diff --git a/windows/DEVCPP/pscp/pscp.dev b/windows/DEVCPP/pscp/pscp.dev index 911c67f..a27975f 100644 --- a/windows/DEVCPP/pscp/pscp.dev +++ b/windows/DEVCPP/pscp/pscp.dev @@ -1,1461 +1,1481 @@ -# DEV-C++ 5 Project File - pscp.dev -# ** DO NOT EDIT ** - -[Project] -FileName=pscp.dev -Name=pscp -Ver=1 -IsCpp=1 -Type=1 -Compiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ -CppCompiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ -Includes=..\..\..\.;..\..\..\charset;..\..\..\windows;..\..\..\unix -Linker=-ladvapi32 -lcomctl32 -lcomdlg32 -lgdi32 -limm32 -lshell32 -luser32 -lwinmm -lwinspool_@@_ -Libs= -UnitCount=141 -Folders="Header Files","Resource Files","Source Files" -ObjFiles= -PrivateResource=pscp_private.rc -ResourceIncludes=..\..\..\WINDOWS -MakeIncludes= -Icon= -ExeOutput= -ObjectOutput= -OverrideOutput=0 -OverrideOutputName=pscp.exe -HostApplication= -CommandLine= -UseCustomMakefile=0 -CustomMakefile= -IncludeVersionInfo=0 -SupportXPThemes=0 -CompilerSet=0 -CompilerSettings=0000000000000000000000 - -[Unit1] -FileName=..\..\..\agentf.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit2] -FileName=..\..\..\aqsync.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit3] -FileName=..\..\..\be_misc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit4] -FileName=..\..\..\be_ssh.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit5] -FileName=..\..\..\callback.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit6] -FileName=..\..\..\cmdline.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit7] -FileName=..\..\..\conf.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit8] -FileName=..\..\..\cproxy.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit9] -FileName=..\..\..\ecc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit10] -FileName=..\..\..\errsock.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit11] -FileName=..\..\..\logging.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit12] -FileName=..\..\..\mainchan.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit13] -FileName=..\..\..\marshal.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit14] -FileName=..\..\..\memory.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit15] -FileName=..\..\..\misc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit16] -FileName=..\..\..\miscucs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit17] -FileName=..\..\..\mpint.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit18] -FileName=..\..\..\noshare.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit19] -FileName=..\..\..\nullplug.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit20] -FileName=..\..\..\pgssapi.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit21] -FileName=..\..\..\pinger.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit22] -FileName=..\..\..\portfwd.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit23] -FileName=..\..\..\proxy.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit24] -FileName=..\..\..\pscp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit25] -FileName=..\..\..\settings.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit26] -FileName=..\..\..\sftp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit27] -FileName=..\..\..\sftpcommon.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit28] -FileName=..\..\..\ssh.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit29] -FileName=..\..\..\ssh1bpp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit30] -FileName=..\..\..\ssh1censor.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit31] -FileName=..\..\..\ssh1connection-client.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit32] -FileName=..\..\..\ssh1connection.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit33] -FileName=..\..\..\ssh1login.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit34] -FileName=..\..\..\ssh2bpp-bare.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit35] -FileName=..\..\..\ssh2bpp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit36] -FileName=..\..\..\ssh2censor.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit37] -FileName=..\..\..\ssh2connection-client.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit38] -FileName=..\..\..\ssh2connection.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit39] -FileName=..\..\..\ssh2kex-client.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit40] -FileName=..\..\..\ssh2transhk.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit41] -FileName=..\..\..\ssh2transport.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit42] -FileName=..\..\..\ssh2userauth.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit43] -FileName=..\..\..\sshaes.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit44] -FileName=..\..\..\ssharcf.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit45] -FileName=..\..\..\sshauxcrypt.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit46] -FileName=..\..\..\sshblowf.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit47] -FileName=..\..\..\sshccp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit48] -FileName=..\..\..\sshcommon.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit49] -FileName=..\..\..\sshcrc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit50] -FileName=..\..\..\sshcrcda.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit51] -FileName=..\..\..\sshdes.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit52] -FileName=..\..\..\sshdh.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit53] -FileName=..\..\..\sshdss.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit54] -FileName=..\..\..\sshecc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit55] -FileName=..\..\..\sshgssc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit56] -FileName=..\..\..\sshhmac.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit57] -FileName=..\..\..\sshmac.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit58] -FileName=..\..\..\sshmd5.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit59] -FileName=..\..\..\sshprng.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit60] -FileName=..\..\..\sshpubk.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit61] -FileName=..\..\..\sshrand.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit62] -FileName=..\..\..\sshrsa.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit63] -FileName=..\..\..\sshsh256.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit64] -FileName=..\..\..\sshsh512.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit65] -FileName=..\..\..\sshsha.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit66] -FileName=..\..\..\sshshare.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit67] -FileName=..\..\..\sshverstring.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit68] -FileName=..\..\..\sshzlib.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit69] -FileName=..\..\..\stripctrl.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit70] -FileName=..\..\..\timing.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit71] -FileName=..\..\..\tree234.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit72] -FileName=..\..\..\utils.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit73] -FileName=..\..\..\version.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit74] -FileName=..\..\..\wcwidth.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit75] -FileName=..\..\..\wildcard.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit76] -FileName=..\..\..\windows\wincapi.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit77] -FileName=..\..\..\windows\wincons.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit78] -FileName=..\..\..\windows\windefs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit79] -FileName=..\..\..\windows\wingss.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit80] -FileName=..\..\..\windows\winhandl.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit81] -FileName=..\..\..\windows\winhsock.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit82] -FileName=..\..\..\windows\winmisc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit83] -FileName=..\..\..\windows\winmiscs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit84] -FileName=..\..\..\windows\winnet.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit85] -FileName=..\..\..\windows\winnohlp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit86] -FileName=..\..\..\windows\winnoise.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit87] -FileName=..\..\..\windows\winnojmp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit88] -FileName=..\..\..\windows\winnpc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit89] -FileName=..\..\..\windows\winnps.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit90] -FileName=..\..\..\windows\winpgntc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit91] -FileName=..\..\..\windows\winproxy.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit92] -FileName=..\..\..\windows\winsecur.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit93] -FileName=..\..\..\windows\winsftp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit94] -FileName=..\..\..\windows\winshare.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit95] -FileName=..\..\..\windows\winstore.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit96] -FileName=..\..\..\windows\wintime.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit97] -FileName=..\..\..\windows\winucs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit98] -FileName=..\..\..\x11fwd.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit99] -FileName=..\..\..\charset\charset.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit100] -FileName=..\..\..\defs.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit101] -FileName=..\..\..\ecc.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit102] -FileName=..\..\..\empty.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit103] -FileName=..\..\..\licence.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit104] -FileName=..\..\..\marshal.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit105] -FileName=..\..\..\misc.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit106] -FileName=..\..\..\mpint.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit107] -FileName=..\..\..\mpint_i.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit108] -FileName=..\..\..\network.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit109] -FileName=..\..\..\pageant.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit110] -FileName=..\..\..\pgssapi.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit111] -FileName=..\..\..\proxy.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit112] -FileName=..\..\..\psftp.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit113] -FileName=..\..\..\putty.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit114] -FileName=..\..\..\puttymem.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit115] -FileName=..\..\..\puttyps.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit116] -FileName=..\..\..\sftp.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit117] -FileName=..\..\..\ssh.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit118] -FileName=..\..\..\ssh1connection.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit119] -FileName=..\..\..\ssh2connection.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit120] -FileName=..\..\..\ssh2transport.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit121] -FileName=..\..\..\sshblowf.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit122] -FileName=..\..\..\sshbpp.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit123] -FileName=..\..\..\sshchan.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit124] -FileName=..\..\..\sshcr.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit125] -FileName=..\..\..\sshgss.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit126] -FileName=..\..\..\sshgssc.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit127] -FileName=..\..\..\sshppl.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit128] -FileName=..\..\..\sshsignals.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit129] -FileName=..\..\..\sshttymodes.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit130] -FileName=..\..\..\storage.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit131] -FileName=..\..\..\terminal.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit132] -FileName=..\..\..\tree234.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit133] -FileName=..\..\..\unix\unix.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit134] -FileName=..\..\..\version.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit135] -FileName=..\..\..\windows\rcstuff.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit136] -FileName=..\..\..\windows\wincapi.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit137] -FileName=..\..\..\windows\winhelp.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit138] -FileName=..\..\..\windows\winsecur.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit139] -FileName=..\..\..\windows\winstuff.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit140] -FileName=..\..\..\windows\pscp.ico -Folder=Resource Files -Compile=0 -CompileCpp=0 -Link=0 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit141] -FileName=..\..\..\windows\pscp.rc -Folder=Resource Files -Compile=1 -CompileCpp=1 -Link=0 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[VersionInfo] -Major=0 -Minor=0 -Release=1 -Build=1 -LanguageID=1033 -CharsetID=1252 -CompanyName= -FileVersion=0.1 -FileDescription= -InternalName= -LegalCopyright= -LegalTrademarks= -OriginalFilename=pscp.exe -ProductName=pscp -ProductVersion=0.1 -AutoIncBuildNr=0 +# DEV-C++ 5 Project File - pscp.dev +# ** DO NOT EDIT ** + +[Project] +FileName=pscp.dev +Name=pscp +Ver=1 +IsCpp=1 +Type=1 +Compiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ +CppCompiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ +Includes=..\..\..\.;..\..\..\charset;..\..\..\windows;..\..\..\unix +Linker=-ladvapi32 -lcomctl32 -lcomdlg32 -lgdi32 -limm32 -lshell32 -luser32 -lwinmm -lwinspool_@@_ +Libs= +UnitCount=143 +Folders="Header Files","Resource Files","Source Files" +ObjFiles= +PrivateResource=pscp_private.rc +ResourceIncludes=..\..\..\WINDOWS +MakeIncludes= +Icon= +ExeOutput= +ObjectOutput= +OverrideOutput=0 +OverrideOutputName=pscp.exe +HostApplication= +CommandLine= +UseCustomMakefile=0 +CustomMakefile= +IncludeVersionInfo=0 +SupportXPThemes=0 +CompilerSet=0 +CompilerSettings=0000000000000000000000 + +[Unit1] +FileName=..\..\..\agentf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit2] +FileName=..\..\..\aqsync.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit3] +FileName=..\..\..\be_misc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit4] +FileName=..\..\..\be_ssh.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit5] +FileName=..\..\..\callback.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit6] +FileName=..\..\..\cmdline.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit7] +FileName=..\..\..\conf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit8] +FileName=..\..\..\cproxy.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit9] +FileName=..\..\..\ecc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit10] +FileName=..\..\..\errsock.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit11] +FileName=..\..\..\logging.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit12] +FileName=..\..\..\mainchan.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit13] +FileName=..\..\..\marshal.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit14] +FileName=..\..\..\memory.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit15] +FileName=..\..\..\misc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit16] +FileName=..\..\..\miscucs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit17] +FileName=..\..\..\mpint.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit18] +FileName=..\..\..\noshare.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit19] +FileName=..\..\..\nullplug.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit20] +FileName=..\..\..\pgssapi.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit21] +FileName=..\..\..\pinger.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit22] +FileName=..\..\..\portfwd.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit23] +FileName=..\..\..\proxy.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit24] +FileName=..\..\..\pscp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit25] +FileName=..\..\..\psftpcommon.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit26] +FileName=..\..\..\settings.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit27] +FileName=..\..\..\sftp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit28] +FileName=..\..\..\sftpcommon.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit29] +FileName=..\..\..\ssh.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit30] +FileName=..\..\..\ssh1bpp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit31] +FileName=..\..\..\ssh1censor.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit32] +FileName=..\..\..\ssh1connection-client.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit33] +FileName=..\..\..\ssh1connection.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit34] +FileName=..\..\..\ssh1login.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit35] +FileName=..\..\..\ssh2bpp-bare.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit36] +FileName=..\..\..\ssh2bpp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit37] +FileName=..\..\..\ssh2censor.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit38] +FileName=..\..\..\ssh2connection-client.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit39] +FileName=..\..\..\ssh2connection.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit40] +FileName=..\..\..\ssh2kex-client.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit41] +FileName=..\..\..\ssh2transhk.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit42] +FileName=..\..\..\ssh2transport.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit43] +FileName=..\..\..\ssh2userauth.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit44] +FileName=..\..\..\sshaes.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit45] +FileName=..\..\..\ssharcf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit46] +FileName=..\..\..\sshauxcrypt.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit47] +FileName=..\..\..\sshblowf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit48] +FileName=..\..\..\sshccp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit49] +FileName=..\..\..\sshcommon.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit50] +FileName=..\..\..\sshcrc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit51] +FileName=..\..\..\sshcrcda.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit52] +FileName=..\..\..\sshdes.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit53] +FileName=..\..\..\sshdh.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit54] +FileName=..\..\..\sshdss.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit55] +FileName=..\..\..\sshecc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit56] +FileName=..\..\..\sshgssc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit57] +FileName=..\..\..\sshhmac.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit58] +FileName=..\..\..\sshmac.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit59] +FileName=..\..\..\sshmd5.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit60] +FileName=..\..\..\sshprng.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit61] +FileName=..\..\..\sshpubk.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit62] +FileName=..\..\..\sshrand.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit63] +FileName=..\..\..\sshrsa.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit64] +FileName=..\..\..\sshsh256.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit65] +FileName=..\..\..\sshsh512.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit66] +FileName=..\..\..\sshsha.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit67] +FileName=..\..\..\sshshare.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit68] +FileName=..\..\..\sshverstring.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit69] +FileName=..\..\..\sshzlib.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit70] +FileName=..\..\..\stripctrl.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit71] +FileName=..\..\..\timing.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit72] +FileName=..\..\..\tree234.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit73] +FileName=..\..\..\utils.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit74] +FileName=..\..\..\version.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit75] +FileName=..\..\..\wcwidth.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit76] +FileName=..\..\..\wildcard.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit77] +FileName=..\..\..\windows\wincapi.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit78] +FileName=..\..\..\windows\wincons.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit79] +FileName=..\..\..\windows\windefs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit80] +FileName=..\..\..\windows\wingss.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit81] +FileName=..\..\..\windows\winhandl.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit82] +FileName=..\..\..\windows\winhsock.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit83] +FileName=..\..\..\windows\winmisc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit84] +FileName=..\..\..\windows\winmiscs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit85] +FileName=..\..\..\windows\winnet.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit86] +FileName=..\..\..\windows\winnohlp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit87] +FileName=..\..\..\windows\winnoise.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit88] +FileName=..\..\..\windows\winnojmp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit89] +FileName=..\..\..\windows\winnpc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit90] +FileName=..\..\..\windows\winnps.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit91] +FileName=..\..\..\windows\winpgntc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit92] +FileName=..\..\..\windows\winproxy.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit93] +FileName=..\..\..\windows\winsecur.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit94] +FileName=..\..\..\windows\winsftp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit95] +FileName=..\..\..\windows\winshare.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit96] +FileName=..\..\..\windows\winstore.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit97] +FileName=..\..\..\windows\wintime.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit98] +FileName=..\..\..\windows\winucs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit99] +FileName=..\..\..\x11fwd.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit100] +FileName=..\..\..\charset\charset.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit101] +FileName=..\..\..\defs.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit102] +FileName=..\..\..\ecc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit103] +FileName=..\..\..\empty.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit104] +FileName=..\..\..\licence.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit105] +FileName=..\..\..\marshal.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit106] +FileName=..\..\..\misc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit107] +FileName=..\..\..\mpint.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit108] +FileName=..\..\..\mpint_i.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit109] +FileName=..\..\..\network.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit110] +FileName=..\..\..\pageant.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit111] +FileName=..\..\..\pgssapi.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit112] +FileName=..\..\..\proxy.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit113] +FileName=..\..\..\psftp.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit114] +FileName=..\..\..\putty.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit115] +FileName=..\..\..\puttymem.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit116] +FileName=..\..\..\puttyps.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit117] +FileName=..\..\..\sftp.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit118] +FileName=..\..\..\ssh.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit119] +FileName=..\..\..\ssh1connection.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit120] +FileName=..\..\..\ssh2connection.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit121] +FileName=..\..\..\ssh2transport.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit122] +FileName=..\..\..\sshblowf.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit123] +FileName=..\..\..\sshbpp.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit124] +FileName=..\..\..\sshchan.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit125] +FileName=..\..\..\sshcr.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit126] +FileName=..\..\..\sshgss.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit127] +FileName=..\..\..\sshgssc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit128] +FileName=..\..\..\sshppl.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit129] +FileName=..\..\..\sshserver.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit130] +FileName=..\..\..\sshsignals.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit131] +FileName=..\..\..\sshttymodes.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit132] +FileName=..\..\..\storage.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit133] +FileName=..\..\..\terminal.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit134] +FileName=..\..\..\tree234.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit135] +FileName=..\..\..\unix\unix.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit136] +FileName=..\..\..\version.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit137] +FileName=..\..\..\windows\rcstuff.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit138] +FileName=..\..\..\windows\wincapi.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit139] +FileName=..\..\..\windows\winhelp.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit140] +FileName=..\..\..\windows\winsecur.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit141] +FileName=..\..\..\windows\winstuff.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit142] +FileName=..\..\..\windows\pscp.ico +Folder=Resource Files +Compile=0 +CompileCpp=0 +Link=0 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit143] +FileName=..\..\..\windows\pscp.rc +Folder=Resource Files +Compile=1 +CompileCpp=1 +Link=0 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[VersionInfo] +Major=0 +Minor=0 +Release=1 +Build=1 +LanguageID=1033 +CharsetID=1252 +CompanyName= +FileVersion=0.1 +FileDescription= +InternalName= +LegalCopyright= +LegalTrademarks= +OriginalFilename=pscp.exe +ProductName=pscp +ProductVersion=0.1 +AutoIncBuildNr=0 diff --git a/windows/DEVCPP/psftp/psftp.dev b/windows/DEVCPP/psftp/psftp.dev index 0db5754..75dc64a 100644 --- a/windows/DEVCPP/psftp/psftp.dev +++ b/windows/DEVCPP/psftp/psftp.dev @@ -1,1461 +1,1481 @@ -# DEV-C++ 5 Project File - psftp.dev -# ** DO NOT EDIT ** - -[Project] -FileName=psftp.dev -Name=psftp -Ver=1 -IsCpp=1 -Type=1 -Compiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ -CppCompiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ -Includes=..\..\..\.;..\..\..\charset;..\..\..\windows;..\..\..\unix -Linker=-ladvapi32 -lcomctl32 -lcomdlg32 -lgdi32 -limm32 -lshell32 -luser32 -lwinmm -lwinspool_@@_ -Libs= -UnitCount=141 -Folders="Header Files","Resource Files","Source Files" -ObjFiles= -PrivateResource=psftp_private.rc -ResourceIncludes=..\..\..\WINDOWS -MakeIncludes= -Icon= -ExeOutput= -ObjectOutput= -OverrideOutput=0 -OverrideOutputName=psftp.exe -HostApplication= -CommandLine= -UseCustomMakefile=0 -CustomMakefile= -IncludeVersionInfo=0 -SupportXPThemes=0 -CompilerSet=0 -CompilerSettings=0000000000000000000000 - -[Unit1] -FileName=..\..\..\agentf.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit2] -FileName=..\..\..\aqsync.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit3] -FileName=..\..\..\be_misc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit4] -FileName=..\..\..\be_ssh.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit5] -FileName=..\..\..\callback.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit6] -FileName=..\..\..\cmdline.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit7] -FileName=..\..\..\conf.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit8] -FileName=..\..\..\cproxy.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit9] -FileName=..\..\..\ecc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit10] -FileName=..\..\..\errsock.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit11] -FileName=..\..\..\logging.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit12] -FileName=..\..\..\mainchan.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit13] -FileName=..\..\..\marshal.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit14] -FileName=..\..\..\memory.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit15] -FileName=..\..\..\misc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit16] -FileName=..\..\..\miscucs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit17] -FileName=..\..\..\mpint.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit18] -FileName=..\..\..\noshare.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit19] -FileName=..\..\..\nullplug.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit20] -FileName=..\..\..\pgssapi.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit21] -FileName=..\..\..\pinger.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit22] -FileName=..\..\..\portfwd.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit23] -FileName=..\..\..\proxy.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit24] -FileName=..\..\..\psftp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit25] -FileName=..\..\..\settings.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit26] -FileName=..\..\..\sftp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit27] -FileName=..\..\..\sftpcommon.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit28] -FileName=..\..\..\ssh.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit29] -FileName=..\..\..\ssh1bpp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit30] -FileName=..\..\..\ssh1censor.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit31] -FileName=..\..\..\ssh1connection-client.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit32] -FileName=..\..\..\ssh1connection.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit33] -FileName=..\..\..\ssh1login.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit34] -FileName=..\..\..\ssh2bpp-bare.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit35] -FileName=..\..\..\ssh2bpp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit36] -FileName=..\..\..\ssh2censor.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit37] -FileName=..\..\..\ssh2connection-client.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit38] -FileName=..\..\..\ssh2connection.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit39] -FileName=..\..\..\ssh2kex-client.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit40] -FileName=..\..\..\ssh2transhk.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit41] -FileName=..\..\..\ssh2transport.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit42] -FileName=..\..\..\ssh2userauth.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit43] -FileName=..\..\..\sshaes.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit44] -FileName=..\..\..\ssharcf.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit45] -FileName=..\..\..\sshauxcrypt.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit46] -FileName=..\..\..\sshblowf.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit47] -FileName=..\..\..\sshccp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit48] -FileName=..\..\..\sshcommon.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit49] -FileName=..\..\..\sshcrc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit50] -FileName=..\..\..\sshcrcda.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit51] -FileName=..\..\..\sshdes.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit52] -FileName=..\..\..\sshdh.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit53] -FileName=..\..\..\sshdss.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit54] -FileName=..\..\..\sshecc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit55] -FileName=..\..\..\sshgssc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit56] -FileName=..\..\..\sshhmac.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit57] -FileName=..\..\..\sshmac.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit58] -FileName=..\..\..\sshmd5.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit59] -FileName=..\..\..\sshprng.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit60] -FileName=..\..\..\sshpubk.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit61] -FileName=..\..\..\sshrand.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit62] -FileName=..\..\..\sshrsa.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit63] -FileName=..\..\..\sshsh256.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit64] -FileName=..\..\..\sshsh512.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit65] -FileName=..\..\..\sshsha.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit66] -FileName=..\..\..\sshshare.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit67] -FileName=..\..\..\sshverstring.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit68] -FileName=..\..\..\sshzlib.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit69] -FileName=..\..\..\stripctrl.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit70] -FileName=..\..\..\timing.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit71] -FileName=..\..\..\tree234.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit72] -FileName=..\..\..\utils.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit73] -FileName=..\..\..\version.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit74] -FileName=..\..\..\wcwidth.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit75] -FileName=..\..\..\wildcard.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit76] -FileName=..\..\..\windows\wincapi.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit77] -FileName=..\..\..\windows\wincons.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit78] -FileName=..\..\..\windows\windefs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit79] -FileName=..\..\..\windows\wingss.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit80] -FileName=..\..\..\windows\winhandl.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit81] -FileName=..\..\..\windows\winhsock.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit82] -FileName=..\..\..\windows\winmisc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit83] -FileName=..\..\..\windows\winmiscs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit84] -FileName=..\..\..\windows\winnet.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit85] -FileName=..\..\..\windows\winnohlp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit86] -FileName=..\..\..\windows\winnoise.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit87] -FileName=..\..\..\windows\winnojmp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit88] -FileName=..\..\..\windows\winnpc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit89] -FileName=..\..\..\windows\winnps.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit90] -FileName=..\..\..\windows\winpgntc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit91] -FileName=..\..\..\windows\winproxy.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit92] -FileName=..\..\..\windows\winsecur.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit93] -FileName=..\..\..\windows\winsftp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit94] -FileName=..\..\..\windows\winshare.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit95] -FileName=..\..\..\windows\winstore.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit96] -FileName=..\..\..\windows\wintime.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit97] -FileName=..\..\..\windows\winucs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit98] -FileName=..\..\..\x11fwd.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit99] -FileName=..\..\..\charset\charset.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit100] -FileName=..\..\..\defs.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit101] -FileName=..\..\..\ecc.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit102] -FileName=..\..\..\empty.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit103] -FileName=..\..\..\licence.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit104] -FileName=..\..\..\marshal.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit105] -FileName=..\..\..\misc.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit106] -FileName=..\..\..\mpint.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit107] -FileName=..\..\..\mpint_i.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit108] -FileName=..\..\..\network.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit109] -FileName=..\..\..\pageant.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit110] -FileName=..\..\..\pgssapi.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit111] -FileName=..\..\..\proxy.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit112] -FileName=..\..\..\psftp.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit113] -FileName=..\..\..\putty.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit114] -FileName=..\..\..\puttymem.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit115] -FileName=..\..\..\puttyps.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit116] -FileName=..\..\..\sftp.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit117] -FileName=..\..\..\ssh.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit118] -FileName=..\..\..\ssh1connection.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit119] -FileName=..\..\..\ssh2connection.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit120] -FileName=..\..\..\ssh2transport.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit121] -FileName=..\..\..\sshblowf.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit122] -FileName=..\..\..\sshbpp.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit123] -FileName=..\..\..\sshchan.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit124] -FileName=..\..\..\sshcr.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit125] -FileName=..\..\..\sshgss.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit126] -FileName=..\..\..\sshgssc.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit127] -FileName=..\..\..\sshppl.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit128] -FileName=..\..\..\sshsignals.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit129] -FileName=..\..\..\sshttymodes.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit130] -FileName=..\..\..\storage.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit131] -FileName=..\..\..\terminal.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit132] -FileName=..\..\..\tree234.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit133] -FileName=..\..\..\unix\unix.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit134] -FileName=..\..\..\version.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit135] -FileName=..\..\..\windows\rcstuff.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit136] -FileName=..\..\..\windows\wincapi.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit137] -FileName=..\..\..\windows\winhelp.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit138] -FileName=..\..\..\windows\winsecur.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit139] -FileName=..\..\..\windows\winstuff.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit140] -FileName=..\..\..\windows\pscp.ico -Folder=Resource Files -Compile=0 -CompileCpp=0 -Link=0 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit141] -FileName=..\..\..\windows\psftp.rc -Folder=Resource Files -Compile=1 -CompileCpp=1 -Link=0 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[VersionInfo] -Major=0 -Minor=0 -Release=1 -Build=1 -LanguageID=1033 -CharsetID=1252 -CompanyName= -FileVersion=0.1 -FileDescription= -InternalName= -LegalCopyright= -LegalTrademarks= -OriginalFilename=psftp.exe -ProductName=psftp -ProductVersion=0.1 -AutoIncBuildNr=0 +# DEV-C++ 5 Project File - psftp.dev +# ** DO NOT EDIT ** + +[Project] +FileName=psftp.dev +Name=psftp +Ver=1 +IsCpp=1 +Type=1 +Compiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ +CppCompiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ +Includes=..\..\..\.;..\..\..\charset;..\..\..\windows;..\..\..\unix +Linker=-ladvapi32 -lcomctl32 -lcomdlg32 -lgdi32 -limm32 -lshell32 -luser32 -lwinmm -lwinspool_@@_ +Libs= +UnitCount=143 +Folders="Header Files","Resource Files","Source Files" +ObjFiles= +PrivateResource=psftp_private.rc +ResourceIncludes=..\..\..\WINDOWS +MakeIncludes= +Icon= +ExeOutput= +ObjectOutput= +OverrideOutput=0 +OverrideOutputName=psftp.exe +HostApplication= +CommandLine= +UseCustomMakefile=0 +CustomMakefile= +IncludeVersionInfo=0 +SupportXPThemes=0 +CompilerSet=0 +CompilerSettings=0000000000000000000000 + +[Unit1] +FileName=..\..\..\agentf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit2] +FileName=..\..\..\aqsync.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit3] +FileName=..\..\..\be_misc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit4] +FileName=..\..\..\be_ssh.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit5] +FileName=..\..\..\callback.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit6] +FileName=..\..\..\cmdline.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit7] +FileName=..\..\..\conf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit8] +FileName=..\..\..\cproxy.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit9] +FileName=..\..\..\ecc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit10] +FileName=..\..\..\errsock.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit11] +FileName=..\..\..\logging.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit12] +FileName=..\..\..\mainchan.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit13] +FileName=..\..\..\marshal.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit14] +FileName=..\..\..\memory.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit15] +FileName=..\..\..\misc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit16] +FileName=..\..\..\miscucs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit17] +FileName=..\..\..\mpint.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit18] +FileName=..\..\..\noshare.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit19] +FileName=..\..\..\nullplug.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit20] +FileName=..\..\..\pgssapi.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit21] +FileName=..\..\..\pinger.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit22] +FileName=..\..\..\portfwd.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit23] +FileName=..\..\..\proxy.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit24] +FileName=..\..\..\psftp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit25] +FileName=..\..\..\psftpcommon.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit26] +FileName=..\..\..\settings.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit27] +FileName=..\..\..\sftp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit28] +FileName=..\..\..\sftpcommon.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit29] +FileName=..\..\..\ssh.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit30] +FileName=..\..\..\ssh1bpp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit31] +FileName=..\..\..\ssh1censor.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit32] +FileName=..\..\..\ssh1connection-client.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit33] +FileName=..\..\..\ssh1connection.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit34] +FileName=..\..\..\ssh1login.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit35] +FileName=..\..\..\ssh2bpp-bare.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit36] +FileName=..\..\..\ssh2bpp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit37] +FileName=..\..\..\ssh2censor.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit38] +FileName=..\..\..\ssh2connection-client.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit39] +FileName=..\..\..\ssh2connection.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit40] +FileName=..\..\..\ssh2kex-client.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit41] +FileName=..\..\..\ssh2transhk.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit42] +FileName=..\..\..\ssh2transport.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit43] +FileName=..\..\..\ssh2userauth.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit44] +FileName=..\..\..\sshaes.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit45] +FileName=..\..\..\ssharcf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit46] +FileName=..\..\..\sshauxcrypt.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit47] +FileName=..\..\..\sshblowf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit48] +FileName=..\..\..\sshccp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit49] +FileName=..\..\..\sshcommon.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit50] +FileName=..\..\..\sshcrc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit51] +FileName=..\..\..\sshcrcda.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit52] +FileName=..\..\..\sshdes.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit53] +FileName=..\..\..\sshdh.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit54] +FileName=..\..\..\sshdss.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit55] +FileName=..\..\..\sshecc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit56] +FileName=..\..\..\sshgssc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit57] +FileName=..\..\..\sshhmac.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit58] +FileName=..\..\..\sshmac.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit59] +FileName=..\..\..\sshmd5.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit60] +FileName=..\..\..\sshprng.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit61] +FileName=..\..\..\sshpubk.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit62] +FileName=..\..\..\sshrand.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit63] +FileName=..\..\..\sshrsa.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit64] +FileName=..\..\..\sshsh256.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit65] +FileName=..\..\..\sshsh512.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit66] +FileName=..\..\..\sshsha.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit67] +FileName=..\..\..\sshshare.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit68] +FileName=..\..\..\sshverstring.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit69] +FileName=..\..\..\sshzlib.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit70] +FileName=..\..\..\stripctrl.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit71] +FileName=..\..\..\timing.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit72] +FileName=..\..\..\tree234.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit73] +FileName=..\..\..\utils.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit74] +FileName=..\..\..\version.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit75] +FileName=..\..\..\wcwidth.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit76] +FileName=..\..\..\wildcard.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit77] +FileName=..\..\..\windows\wincapi.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit78] +FileName=..\..\..\windows\wincons.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit79] +FileName=..\..\..\windows\windefs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit80] +FileName=..\..\..\windows\wingss.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit81] +FileName=..\..\..\windows\winhandl.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit82] +FileName=..\..\..\windows\winhsock.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit83] +FileName=..\..\..\windows\winmisc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit84] +FileName=..\..\..\windows\winmiscs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit85] +FileName=..\..\..\windows\winnet.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit86] +FileName=..\..\..\windows\winnohlp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit87] +FileName=..\..\..\windows\winnoise.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit88] +FileName=..\..\..\windows\winnojmp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit89] +FileName=..\..\..\windows\winnpc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit90] +FileName=..\..\..\windows\winnps.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit91] +FileName=..\..\..\windows\winpgntc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit92] +FileName=..\..\..\windows\winproxy.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit93] +FileName=..\..\..\windows\winsecur.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit94] +FileName=..\..\..\windows\winsftp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit95] +FileName=..\..\..\windows\winshare.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit96] +FileName=..\..\..\windows\winstore.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit97] +FileName=..\..\..\windows\wintime.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit98] +FileName=..\..\..\windows\winucs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit99] +FileName=..\..\..\x11fwd.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit100] +FileName=..\..\..\charset\charset.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit101] +FileName=..\..\..\defs.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit102] +FileName=..\..\..\ecc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit103] +FileName=..\..\..\empty.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit104] +FileName=..\..\..\licence.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit105] +FileName=..\..\..\marshal.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit106] +FileName=..\..\..\misc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit107] +FileName=..\..\..\mpint.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit108] +FileName=..\..\..\mpint_i.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit109] +FileName=..\..\..\network.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit110] +FileName=..\..\..\pageant.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit111] +FileName=..\..\..\pgssapi.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit112] +FileName=..\..\..\proxy.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit113] +FileName=..\..\..\psftp.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit114] +FileName=..\..\..\putty.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit115] +FileName=..\..\..\puttymem.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit116] +FileName=..\..\..\puttyps.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit117] +FileName=..\..\..\sftp.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit118] +FileName=..\..\..\ssh.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit119] +FileName=..\..\..\ssh1connection.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit120] +FileName=..\..\..\ssh2connection.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit121] +FileName=..\..\..\ssh2transport.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit122] +FileName=..\..\..\sshblowf.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit123] +FileName=..\..\..\sshbpp.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit124] +FileName=..\..\..\sshchan.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit125] +FileName=..\..\..\sshcr.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit126] +FileName=..\..\..\sshgss.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit127] +FileName=..\..\..\sshgssc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit128] +FileName=..\..\..\sshppl.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit129] +FileName=..\..\..\sshserver.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit130] +FileName=..\..\..\sshsignals.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit131] +FileName=..\..\..\sshttymodes.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit132] +FileName=..\..\..\storage.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit133] +FileName=..\..\..\terminal.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit134] +FileName=..\..\..\tree234.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit135] +FileName=..\..\..\unix\unix.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit136] +FileName=..\..\..\version.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit137] +FileName=..\..\..\windows\rcstuff.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit138] +FileName=..\..\..\windows\wincapi.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit139] +FileName=..\..\..\windows\winhelp.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit140] +FileName=..\..\..\windows\winsecur.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit141] +FileName=..\..\..\windows\winstuff.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit142] +FileName=..\..\..\windows\pscp.ico +Folder=Resource Files +Compile=0 +CompileCpp=0 +Link=0 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit143] +FileName=..\..\..\windows\psftp.rc +Folder=Resource Files +Compile=1 +CompileCpp=1 +Link=0 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[VersionInfo] +Major=0 +Minor=0 +Release=1 +Build=1 +LanguageID=1033 +CharsetID=1252 +CompanyName= +FileVersion=0.1 +FileDescription= +InternalName= +LegalCopyright= +LegalTrademarks= +OriginalFilename=psftp.exe +ProductName=psftp +ProductVersion=0.1 +AutoIncBuildNr=0 diff --git a/windows/DEVCPP/putty/putty.dev b/windows/DEVCPP/putty/putty.dev index 662e5be..8121fc5 100644 --- a/windows/DEVCPP/putty/putty.dev +++ b/windows/DEVCPP/putty/putty.dev @@ -1,1631 +1,1631 @@ -# DEV-C++ 5 Project File - putty.dev -# ** DO NOT EDIT ** - -[Project] -FileName=putty.dev -Name=putty -Ver=1 -IsCpp=1 -Type=0 -Compiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ -CppCompiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ -Includes=..\..\..\.;..\..\..\charset;..\..\..\windows;..\..\..\unix -Linker=-ladvapi32 -lcomctl32 -lcomdlg32 -lgdi32 -limm32 -lshell32 -luser32 -lwinmm -lwinspool_@@_ -Libs= -UnitCount=158 -Folders="Header Files","Resource Files","Source Files" -ObjFiles= -PrivateResource=putty_private.rc -ResourceIncludes=..\..\..\WINDOWS -MakeIncludes= -Icon= -ExeOutput= -ObjectOutput= -OverrideOutput=0 -OverrideOutputName=putty.exe -HostApplication= -CommandLine= -UseCustomMakefile=0 -CustomMakefile= -IncludeVersionInfo=0 -SupportXPThemes=0 -CompilerSet=0 -CompilerSettings=0000000000000000000000 - -[Unit1] -FileName=..\..\..\agentf.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit2] -FileName=..\..\..\aqsync.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit3] -FileName=..\..\..\be_all_s.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit4] -FileName=..\..\..\be_misc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit5] -FileName=..\..\..\callback.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit6] -FileName=..\..\..\cmdline.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit7] -FileName=..\..\..\conf.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit8] -FileName=..\..\..\config.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit9] -FileName=..\..\..\cproxy.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit10] -FileName=..\..\..\dialog.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit11] -FileName=..\..\..\ecc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit12] -FileName=..\..\..\errsock.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit13] -FileName=..\..\..\ldisc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit14] -FileName=..\..\..\ldiscucs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit15] -FileName=..\..\..\logging.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit16] -FileName=..\..\..\mainchan.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit17] -FileName=..\..\..\marshal.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit18] -FileName=..\..\..\memory.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit19] -FileName=..\..\..\minibidi.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit20] -FileName=..\..\..\misc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit21] -FileName=..\..\..\miscucs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit22] -FileName=..\..\..\mpint.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit23] -FileName=..\..\..\noshare.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit24] -FileName=..\..\..\nullplug.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit25] -FileName=..\..\..\pgssapi.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit26] -FileName=..\..\..\pinger.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit27] -FileName=..\..\..\portfwd.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit28] -FileName=..\..\..\proxy.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit29] -FileName=..\..\..\raw.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit30] -FileName=..\..\..\rlogin.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit31] -FileName=..\..\..\sercfg.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit32] -FileName=..\..\..\sessprep.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit33] -FileName=..\..\..\settings.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit34] -FileName=..\..\..\ssh.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit35] -FileName=..\..\..\ssh1bpp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit36] -FileName=..\..\..\ssh1censor.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit37] -FileName=..\..\..\ssh1connection-client.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit38] -FileName=..\..\..\ssh1connection.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit39] -FileName=..\..\..\ssh1login.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit40] -FileName=..\..\..\ssh2bpp-bare.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit41] -FileName=..\..\..\ssh2bpp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit42] -FileName=..\..\..\ssh2censor.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit43] -FileName=..\..\..\ssh2connection-client.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit44] -FileName=..\..\..\ssh2connection.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit45] -FileName=..\..\..\ssh2kex-client.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit46] -FileName=..\..\..\ssh2transhk.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit47] -FileName=..\..\..\ssh2transport.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit48] -FileName=..\..\..\ssh2userauth.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit49] -FileName=..\..\..\sshaes.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit50] -FileName=..\..\..\ssharcf.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit51] -FileName=..\..\..\sshauxcrypt.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit52] -FileName=..\..\..\sshblowf.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit53] -FileName=..\..\..\sshccp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit54] -FileName=..\..\..\sshcommon.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit55] -FileName=..\..\..\sshcrc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit56] -FileName=..\..\..\sshcrcda.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit57] -FileName=..\..\..\sshdes.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit58] -FileName=..\..\..\sshdh.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit59] -FileName=..\..\..\sshdss.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit60] -FileName=..\..\..\sshecc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit61] -FileName=..\..\..\sshgssc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit62] -FileName=..\..\..\sshhmac.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit63] -FileName=..\..\..\sshmac.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit64] -FileName=..\..\..\sshmd5.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit65] -FileName=..\..\..\sshprng.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit66] -FileName=..\..\..\sshpubk.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit67] -FileName=..\..\..\sshrand.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit68] -FileName=..\..\..\sshrsa.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit69] -FileName=..\..\..\sshsh256.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit70] -FileName=..\..\..\sshsh512.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit71] -FileName=..\..\..\sshsha.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit72] -FileName=..\..\..\sshshare.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit73] -FileName=..\..\..\sshverstring.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit74] -FileName=..\..\..\sshzlib.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit75] -FileName=..\..\..\stripctrl.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit76] -FileName=..\..\..\telnet.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit77] -FileName=..\..\..\terminal.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit78] -FileName=..\..\..\timing.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit79] -FileName=..\..\..\tree234.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit80] -FileName=..\..\..\utils.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit81] -FileName=..\..\..\version.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit82] -FileName=..\..\..\wcwidth.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit83] -FileName=..\..\..\wildcard.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit84] -FileName=..\..\..\windows\sizetip.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit85] -FileName=..\..\..\windows\wincapi.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit86] -FileName=..\..\..\windows\wincfg.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit87] -FileName=..\..\..\windows\winctrls.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit88] -FileName=..\..\..\windows\windefs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit89] -FileName=..\..\..\windows\windlg.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit90] -FileName=..\..\..\windows\window.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit91] -FileName=..\..\..\windows\wingss.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit92] -FileName=..\..\..\windows\winhandl.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit93] -FileName=..\..\..\windows\winhelp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit94] -FileName=..\..\..\windows\winhsock.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit95] -FileName=..\..\..\windows\winjump.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit96] -FileName=..\..\..\windows\winmisc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit97] -FileName=..\..\..\windows\winmiscs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit98] -FileName=..\..\..\windows\winnet.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit99] -FileName=..\..\..\windows\winnoise.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit100] -FileName=..\..\..\windows\winnpc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit101] -FileName=..\..\..\windows\winnps.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit102] -FileName=..\..\..\windows\winpgntc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit103] -FileName=..\..\..\windows\winprint.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit104] -FileName=..\..\..\windows\winproxy.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit105] -FileName=..\..\..\windows\winsecur.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit106] -FileName=..\..\..\windows\winser.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit107] -FileName=..\..\..\windows\winshare.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit108] -FileName=..\..\..\windows\winstore.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit109] -FileName=..\..\..\windows\wintime.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit110] -FileName=..\..\..\windows\winucs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit111] -FileName=..\..\..\windows\winutils.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit112] -FileName=..\..\..\windows\winx11.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit113] -FileName=..\..\..\x11fwd.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit114] -FileName=..\..\..\charset\charset.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit115] -FileName=..\..\..\defs.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit116] -FileName=..\..\..\dialog.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit117] -FileName=..\..\..\ecc.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit118] -FileName=..\..\..\empty.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit119] -FileName=..\..\..\ldisc.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit120] -FileName=..\..\..\licence.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit121] -FileName=..\..\..\marshal.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit122] -FileName=..\..\..\misc.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit123] -FileName=..\..\..\mpint.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit124] -FileName=..\..\..\mpint_i.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit125] -FileName=..\..\..\network.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit126] -FileName=..\..\..\pageant.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit127] -FileName=..\..\..\pgssapi.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit128] -FileName=..\..\..\proxy.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit129] -FileName=..\..\..\putty.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit130] -FileName=..\..\..\puttymem.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit131] -FileName=..\..\..\puttyps.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit132] -FileName=..\..\..\ssh.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit133] -FileName=..\..\..\ssh1connection.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit134] -FileName=..\..\..\ssh2connection.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit135] -FileName=..\..\..\ssh2transport.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit136] -FileName=..\..\..\sshblowf.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit137] -FileName=..\..\..\sshbpp.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit138] -FileName=..\..\..\sshchan.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit139] -FileName=..\..\..\sshcr.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit140] -FileName=..\..\..\sshgss.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit141] -FileName=..\..\..\sshgssc.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit142] -FileName=..\..\..\sshppl.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit143] -FileName=..\..\..\sshsignals.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit144] -FileName=..\..\..\sshttymodes.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit145] -FileName=..\..\..\storage.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit146] -FileName=..\..\..\terminal.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit147] -FileName=..\..\..\tree234.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit148] -FileName=..\..\..\unix\unix.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit149] -FileName=..\..\..\version.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit150] -FileName=..\..\..\windows\rcstuff.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit151] -FileName=..\..\..\windows\win_res.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit152] -FileName=..\..\..\windows\wincapi.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit153] -FileName=..\..\..\windows\winhelp.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit154] -FileName=..\..\..\windows\winsecur.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit155] -FileName=..\..\..\windows\winstuff.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit156] -FileName=..\..\..\windows\putty.ico -Folder=Resource Files -Compile=0 -CompileCpp=0 -Link=0 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit157] -FileName=..\..\..\windows\putty.rc -Folder=Resource Files -Compile=1 -CompileCpp=1 -Link=0 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit158] -FileName=..\..\..\windows\puttycfg.ico -Folder=Resource Files -Compile=0 -CompileCpp=0 -Link=0 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[VersionInfo] -Major=0 -Minor=0 -Release=1 -Build=1 -LanguageID=1033 -CharsetID=1252 -CompanyName= -FileVersion=0.1 -FileDescription= -InternalName= -LegalCopyright= -LegalTrademarks= -OriginalFilename=putty.exe -ProductName=putty -ProductVersion=0.1 -AutoIncBuildNr=0 +# DEV-C++ 5 Project File - putty.dev +# ** DO NOT EDIT ** + +[Project] +FileName=putty.dev +Name=putty +Ver=1 +IsCpp=1 +Type=0 +Compiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ +CppCompiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ +Includes=..\..\..\.;..\..\..\charset;..\..\..\windows;..\..\..\unix +Linker=-ladvapi32 -lcomctl32 -lcomdlg32 -lgdi32 -limm32 -lshell32 -luser32 -lwinmm -lwinspool_@@_ +Libs= +UnitCount=158 +Folders="Header Files","Resource Files","Source Files" +ObjFiles= +PrivateResource=putty_private.rc +ResourceIncludes=..\..\..\WINDOWS +MakeIncludes= +Icon= +ExeOutput= +ObjectOutput= +OverrideOutput=0 +OverrideOutputName=putty.exe +HostApplication= +CommandLine= +UseCustomMakefile=0 +CustomMakefile= +IncludeVersionInfo=0 +SupportXPThemes=0 +CompilerSet=0 +CompilerSettings=0000000000000000000000 + +[Unit1] +FileName=..\..\..\agentf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit2] +FileName=..\..\..\aqsync.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit3] +FileName=..\..\..\be_all_s.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit4] +FileName=..\..\..\be_misc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit5] +FileName=..\..\..\callback.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit6] +FileName=..\..\..\cmdline.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit7] +FileName=..\..\..\conf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit8] +FileName=..\..\..\config.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit9] +FileName=..\..\..\cproxy.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit10] +FileName=..\..\..\dialog.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit11] +FileName=..\..\..\ecc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit12] +FileName=..\..\..\errsock.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit13] +FileName=..\..\..\ldisc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit14] +FileName=..\..\..\logging.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit15] +FileName=..\..\..\mainchan.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit16] +FileName=..\..\..\marshal.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit17] +FileName=..\..\..\memory.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit18] +FileName=..\..\..\minibidi.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit19] +FileName=..\..\..\misc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit20] +FileName=..\..\..\miscucs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit21] +FileName=..\..\..\mpint.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit22] +FileName=..\..\..\noshare.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit23] +FileName=..\..\..\nullplug.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit24] +FileName=..\..\..\pgssapi.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit25] +FileName=..\..\..\pinger.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit26] +FileName=..\..\..\portfwd.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit27] +FileName=..\..\..\proxy.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit28] +FileName=..\..\..\raw.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit29] +FileName=..\..\..\rlogin.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit30] +FileName=..\..\..\sercfg.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit31] +FileName=..\..\..\sessprep.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit32] +FileName=..\..\..\settings.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit33] +FileName=..\..\..\ssh.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit34] +FileName=..\..\..\ssh1bpp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit35] +FileName=..\..\..\ssh1censor.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit36] +FileName=..\..\..\ssh1connection-client.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit37] +FileName=..\..\..\ssh1connection.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit38] +FileName=..\..\..\ssh1login.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit39] +FileName=..\..\..\ssh2bpp-bare.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit40] +FileName=..\..\..\ssh2bpp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit41] +FileName=..\..\..\ssh2censor.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit42] +FileName=..\..\..\ssh2connection-client.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit43] +FileName=..\..\..\ssh2connection.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit44] +FileName=..\..\..\ssh2kex-client.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit45] +FileName=..\..\..\ssh2transhk.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit46] +FileName=..\..\..\ssh2transport.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit47] +FileName=..\..\..\ssh2userauth.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit48] +FileName=..\..\..\sshaes.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit49] +FileName=..\..\..\ssharcf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit50] +FileName=..\..\..\sshauxcrypt.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit51] +FileName=..\..\..\sshblowf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit52] +FileName=..\..\..\sshccp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit53] +FileName=..\..\..\sshcommon.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit54] +FileName=..\..\..\sshcrc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit55] +FileName=..\..\..\sshcrcda.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit56] +FileName=..\..\..\sshdes.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit57] +FileName=..\..\..\sshdh.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit58] +FileName=..\..\..\sshdss.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit59] +FileName=..\..\..\sshecc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit60] +FileName=..\..\..\sshgssc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit61] +FileName=..\..\..\sshhmac.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit62] +FileName=..\..\..\sshmac.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit63] +FileName=..\..\..\sshmd5.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit64] +FileName=..\..\..\sshprng.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit65] +FileName=..\..\..\sshpubk.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit66] +FileName=..\..\..\sshrand.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit67] +FileName=..\..\..\sshrsa.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit68] +FileName=..\..\..\sshsh256.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit69] +FileName=..\..\..\sshsh512.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit70] +FileName=..\..\..\sshsha.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit71] +FileName=..\..\..\sshshare.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit72] +FileName=..\..\..\sshverstring.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit73] +FileName=..\..\..\sshzlib.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit74] +FileName=..\..\..\stripctrl.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit75] +FileName=..\..\..\telnet.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit76] +FileName=..\..\..\terminal.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit77] +FileName=..\..\..\timing.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit78] +FileName=..\..\..\tree234.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit79] +FileName=..\..\..\utils.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit80] +FileName=..\..\..\version.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit81] +FileName=..\..\..\wcwidth.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit82] +FileName=..\..\..\wildcard.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit83] +FileName=..\..\..\windows\sizetip.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit84] +FileName=..\..\..\windows\wincapi.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit85] +FileName=..\..\..\windows\wincfg.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit86] +FileName=..\..\..\windows\winctrls.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit87] +FileName=..\..\..\windows\windefs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit88] +FileName=..\..\..\windows\windlg.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit89] +FileName=..\..\..\windows\window.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit90] +FileName=..\..\..\windows\wingss.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit91] +FileName=..\..\..\windows\winhandl.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit92] +FileName=..\..\..\windows\winhelp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit93] +FileName=..\..\..\windows\winhsock.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit94] +FileName=..\..\..\windows\winjump.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit95] +FileName=..\..\..\windows\winmisc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit96] +FileName=..\..\..\windows\winmiscs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit97] +FileName=..\..\..\windows\winnet.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit98] +FileName=..\..\..\windows\winnoise.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit99] +FileName=..\..\..\windows\winnpc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit100] +FileName=..\..\..\windows\winnps.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit101] +FileName=..\..\..\windows\winpgntc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit102] +FileName=..\..\..\windows\winprint.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit103] +FileName=..\..\..\windows\winproxy.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit104] +FileName=..\..\..\windows\winsecur.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit105] +FileName=..\..\..\windows\winser.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit106] +FileName=..\..\..\windows\winshare.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit107] +FileName=..\..\..\windows\winstore.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit108] +FileName=..\..\..\windows\wintime.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit109] +FileName=..\..\..\windows\winucs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit110] +FileName=..\..\..\windows\winutils.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit111] +FileName=..\..\..\windows\winx11.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit112] +FileName=..\..\..\x11fwd.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit113] +FileName=..\..\..\charset\charset.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit114] +FileName=..\..\..\defs.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit115] +FileName=..\..\..\dialog.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit116] +FileName=..\..\..\ecc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit117] +FileName=..\..\..\empty.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit118] +FileName=..\..\..\ldisc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit119] +FileName=..\..\..\licence.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit120] +FileName=..\..\..\marshal.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit121] +FileName=..\..\..\misc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit122] +FileName=..\..\..\mpint.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit123] +FileName=..\..\..\mpint_i.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit124] +FileName=..\..\..\network.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit125] +FileName=..\..\..\pageant.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit126] +FileName=..\..\..\pgssapi.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit127] +FileName=..\..\..\proxy.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit128] +FileName=..\..\..\putty.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit129] +FileName=..\..\..\puttymem.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit130] +FileName=..\..\..\puttyps.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit131] +FileName=..\..\..\ssh.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit132] +FileName=..\..\..\ssh1connection.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit133] +FileName=..\..\..\ssh2connection.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit134] +FileName=..\..\..\ssh2transport.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit135] +FileName=..\..\..\sshblowf.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit136] +FileName=..\..\..\sshbpp.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit137] +FileName=..\..\..\sshchan.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit138] +FileName=..\..\..\sshcr.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit139] +FileName=..\..\..\sshgss.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit140] +FileName=..\..\..\sshgssc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit141] +FileName=..\..\..\sshppl.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit142] +FileName=..\..\..\sshserver.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit143] +FileName=..\..\..\sshsignals.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit144] +FileName=..\..\..\sshttymodes.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit145] +FileName=..\..\..\storage.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit146] +FileName=..\..\..\terminal.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit147] +FileName=..\..\..\tree234.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit148] +FileName=..\..\..\unix\unix.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit149] +FileName=..\..\..\version.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit150] +FileName=..\..\..\windows\rcstuff.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit151] +FileName=..\..\..\windows\win_res.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit152] +FileName=..\..\..\windows\wincapi.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit153] +FileName=..\..\..\windows\winhelp.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit154] +FileName=..\..\..\windows\winsecur.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit155] +FileName=..\..\..\windows\winstuff.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit156] +FileName=..\..\..\windows\putty.ico +Folder=Resource Files +Compile=0 +CompileCpp=0 +Link=0 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit157] +FileName=..\..\..\windows\putty.rc +Folder=Resource Files +Compile=1 +CompileCpp=1 +Link=0 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit158] +FileName=..\..\..\windows\puttycfg.ico +Folder=Resource Files +Compile=0 +CompileCpp=0 +Link=0 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[VersionInfo] +Major=0 +Minor=0 +Release=1 +Build=1 +LanguageID=1033 +CharsetID=1252 +CompanyName= +FileVersion=0.1 +FileDescription= +InternalName= +LegalCopyright= +LegalTrademarks= +OriginalFilename=putty.exe +ProductName=putty +ProductVersion=0.1 +AutoIncBuildNr=0 diff --git a/windows/DEVCPP/puttytel/puttytel.dev b/windows/DEVCPP/puttytel/puttytel.dev index 42ad1be..7b196d7 100644 --- a/windows/DEVCPP/puttytel/puttytel.dev +++ b/windows/DEVCPP/puttytel/puttytel.dev @@ -1,911 +1,901 @@ -# DEV-C++ 5 Project File - puttytel.dev -# ** DO NOT EDIT ** - -[Project] -FileName=puttytel.dev -Name=puttytel -Ver=1 -IsCpp=1 -Type=0 -Compiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ -CppCompiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ -Includes=..\..\..\.;..\..\..\charset;..\..\..\windows;..\..\..\unix -Linker=-ladvapi32 -lcomctl32 -lcomdlg32 -lgdi32 -limm32 -lshell32 -luser32 -lwinmm -lwinspool_@@_ -Libs= -UnitCount=86 -Folders="Header Files","Resource Files","Source Files" -ObjFiles= -PrivateResource=puttytel_private.rc -ResourceIncludes=..\..\..\WINDOWS -MakeIncludes= -Icon= -ExeOutput= -ObjectOutput= -OverrideOutput=0 -OverrideOutputName=puttytel.exe -HostApplication= -CommandLine= -UseCustomMakefile=0 -CustomMakefile= -IncludeVersionInfo=0 -SupportXPThemes=0 -CompilerSet=0 -CompilerSettings=0000000000000000000000 - -[Unit1] -FileName=..\..\..\be_misc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit2] -FileName=..\..\..\be_nos_s.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit3] -FileName=..\..\..\callback.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit4] -FileName=..\..\..\cmdline.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit5] -FileName=..\..\..\conf.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit6] -FileName=..\..\..\config.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit7] -FileName=..\..\..\dialog.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit8] -FileName=..\..\..\errsock.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit9] -FileName=..\..\..\ldisc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit10] -FileName=..\..\..\ldiscucs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit11] -FileName=..\..\..\logging.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit12] -FileName=..\..\..\marshal.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit13] -FileName=..\..\..\memory.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit14] -FileName=..\..\..\minibidi.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit15] -FileName=..\..\..\misc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit16] -FileName=..\..\..\miscucs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit17] -FileName=..\..\..\nocproxy.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit18] -FileName=..\..\..\nogss.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit19] -FileName=..\..\..\pinger.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit20] -FileName=..\..\..\proxy.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit21] -FileName=..\..\..\raw.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit22] -FileName=..\..\..\rlogin.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit23] -FileName=..\..\..\sercfg.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit24] -FileName=..\..\..\sessprep.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit25] -FileName=..\..\..\settings.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit26] -FileName=..\..\..\stripctrl.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit27] -FileName=..\..\..\telnet.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit28] -FileName=..\..\..\terminal.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit29] -FileName=..\..\..\timing.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit30] -FileName=..\..\..\tree234.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit31] -FileName=..\..\..\utils.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit32] -FileName=..\..\..\version.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit33] -FileName=..\..\..\wcwidth.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit34] -FileName=..\..\..\windows\sizetip.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit35] -FileName=..\..\..\windows\wincfg.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit36] -FileName=..\..\..\windows\winctrls.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit37] -FileName=..\..\..\windows\windefs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit38] -FileName=..\..\..\windows\windlg.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit39] -FileName=..\..\..\windows\window.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit40] -FileName=..\..\..\windows\winhandl.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit41] -FileName=..\..\..\windows\winhelp.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit42] -FileName=..\..\..\windows\winhsock.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit43] -FileName=..\..\..\windows\winjump.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit44] -FileName=..\..\..\windows\winmisc.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit45] -FileName=..\..\..\windows\winmiscs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit46] -FileName=..\..\..\windows\winnet.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit47] -FileName=..\..\..\windows\winprint.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit48] -FileName=..\..\..\windows\winproxy.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit49] -FileName=..\..\..\windows\winsecur.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit50] -FileName=..\..\..\windows\winser.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit51] -FileName=..\..\..\windows\winstore.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit52] -FileName=..\..\..\windows\wintime.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit53] -FileName=..\..\..\windows\winucs.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit54] -FileName=..\..\..\windows\winutils.c -Folder=Source Files -Compile=1 -CompileCpp=0 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit55] -FileName=..\..\..\charset\charset.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit56] -FileName=..\..\..\defs.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit57] -FileName=..\..\..\dialog.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit58] -FileName=..\..\..\empty.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit59] -FileName=..\..\..\ldisc.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit60] -FileName=..\..\..\licence.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit61] -FileName=..\..\..\marshal.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit62] -FileName=..\..\..\misc.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit63] -FileName=..\..\..\network.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit64] -FileName=..\..\..\pgssapi.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit65] -FileName=..\..\..\proxy.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit66] -FileName=..\..\..\putty.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit67] -FileName=..\..\..\puttymem.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit68] -FileName=..\..\..\puttyps.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit69] -FileName=..\..\..\ssh.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit70] -FileName=..\..\..\sshgss.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit71] -FileName=..\..\..\sshgssc.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit72] -FileName=..\..\..\sshsignals.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit73] -FileName=..\..\..\sshttymodes.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit74] -FileName=..\..\..\storage.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit75] -FileName=..\..\..\terminal.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit76] -FileName=..\..\..\tree234.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit77] -FileName=..\..\..\unix\unix.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit78] -FileName=..\..\..\version.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit79] -FileName=..\..\..\windows\rcstuff.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit80] -FileName=..\..\..\windows\win_res.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit81] -FileName=..\..\..\windows\winhelp.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit82] -FileName=..\..\..\windows\winsecur.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit83] -FileName=..\..\..\windows\winstuff.h -Folder=Header Files -Compile=1 -CompileCpp=1 -Link=1 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit84] -FileName=..\..\..\windows\putty.ico -Folder=Resource Files -Compile=0 -CompileCpp=0 -Link=0 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit85] -FileName=..\..\..\windows\puttycfg.ico -Folder=Resource Files -Compile=0 -CompileCpp=0 -Link=0 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[Unit86] -FileName=..\..\..\windows\puttytel.rc -Folder=Resource Files -Compile=1 -CompileCpp=1 -Link=0 -Priority=1000 -OverrideBuildCmd=0 -BuildCmd= - -[VersionInfo] -Major=0 -Minor=0 -Release=1 -Build=1 -LanguageID=1033 -CharsetID=1252 -CompanyName= -FileVersion=0.1 -FileDescription= -InternalName= -LegalCopyright= -LegalTrademarks= -OriginalFilename=puttytel.exe -ProductName=puttytel -ProductVersion=0.1 -AutoIncBuildNr=0 +# DEV-C++ 5 Project File - puttytel.dev +# ** DO NOT EDIT ** + +[Project] +FileName=puttytel.dev +Name=puttytel +Ver=1 +IsCpp=1 +Type=0 +Compiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ +CppCompiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ +Includes=..\..\..\.;..\..\..\charset;..\..\..\windows;..\..\..\unix +Linker=-ladvapi32 -lcomctl32 -lcomdlg32 -lgdi32 -limm32 -lshell32 -luser32 -lwinmm -lwinspool_@@_ +Libs= +UnitCount=85 +Folders="Header Files","Resource Files","Source Files" +ObjFiles= +PrivateResource=puttytel_private.rc +ResourceIncludes=..\..\..\WINDOWS +MakeIncludes= +Icon= +ExeOutput= +ObjectOutput= +OverrideOutput=0 +OverrideOutputName=puttytel.exe +HostApplication= +CommandLine= +UseCustomMakefile=0 +CustomMakefile= +IncludeVersionInfo=0 +SupportXPThemes=0 +CompilerSet=0 +CompilerSettings=0000000000000000000000 + +[Unit1] +FileName=..\..\..\be_misc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit2] +FileName=..\..\..\be_nos_s.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit3] +FileName=..\..\..\callback.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit4] +FileName=..\..\..\cmdline.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit5] +FileName=..\..\..\conf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit6] +FileName=..\..\..\config.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit7] +FileName=..\..\..\dialog.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit8] +FileName=..\..\..\errsock.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit9] +FileName=..\..\..\ldisc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit10] +FileName=..\..\..\logging.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit11] +FileName=..\..\..\marshal.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit12] +FileName=..\..\..\memory.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit13] +FileName=..\..\..\minibidi.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit14] +FileName=..\..\..\misc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit15] +FileName=..\..\..\miscucs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit16] +FileName=..\..\..\nocproxy.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit17] +FileName=..\..\..\nogss.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit18] +FileName=..\..\..\pinger.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit19] +FileName=..\..\..\proxy.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit20] +FileName=..\..\..\raw.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit21] +FileName=..\..\..\rlogin.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit22] +FileName=..\..\..\sercfg.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit23] +FileName=..\..\..\sessprep.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit24] +FileName=..\..\..\settings.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit25] +FileName=..\..\..\stripctrl.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit26] +FileName=..\..\..\telnet.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit27] +FileName=..\..\..\terminal.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit28] +FileName=..\..\..\timing.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit29] +FileName=..\..\..\tree234.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit30] +FileName=..\..\..\utils.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit31] +FileName=..\..\..\version.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit32] +FileName=..\..\..\wcwidth.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit33] +FileName=..\..\..\windows\sizetip.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit34] +FileName=..\..\..\windows\wincfg.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit35] +FileName=..\..\..\windows\winctrls.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit36] +FileName=..\..\..\windows\windefs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit37] +FileName=..\..\..\windows\windlg.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit38] +FileName=..\..\..\windows\window.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit39] +FileName=..\..\..\windows\winhandl.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit40] +FileName=..\..\..\windows\winhelp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit41] +FileName=..\..\..\windows\winhsock.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit42] +FileName=..\..\..\windows\winjump.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit43] +FileName=..\..\..\windows\winmisc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit44] +FileName=..\..\..\windows\winmiscs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit45] +FileName=..\..\..\windows\winnet.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit46] +FileName=..\..\..\windows\winprint.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit47] +FileName=..\..\..\windows\winproxy.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit48] +FileName=..\..\..\windows\winsecur.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit49] +FileName=..\..\..\windows\winser.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit50] +FileName=..\..\..\windows\winstore.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit51] +FileName=..\..\..\windows\wintime.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit52] +FileName=..\..\..\windows\winucs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit53] +FileName=..\..\..\windows\winutils.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit54] +FileName=..\..\..\charset\charset.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit55] +FileName=..\..\..\defs.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit56] +FileName=..\..\..\dialog.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit57] +FileName=..\..\..\empty.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit58] +FileName=..\..\..\ldisc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit59] +FileName=..\..\..\licence.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit60] +FileName=..\..\..\marshal.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit61] +FileName=..\..\..\misc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit62] +FileName=..\..\..\network.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit63] +FileName=..\..\..\pgssapi.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit64] +FileName=..\..\..\proxy.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit65] +FileName=..\..\..\putty.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit66] +FileName=..\..\..\puttymem.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit67] +FileName=..\..\..\puttyps.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit68] +FileName=..\..\..\ssh.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit69] +FileName=..\..\..\sshgss.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit70] +FileName=..\..\..\sshgssc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit71] +FileName=..\..\..\sshsignals.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit72] +FileName=..\..\..\sshttymodes.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit73] +FileName=..\..\..\storage.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit74] +FileName=..\..\..\terminal.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit75] +FileName=..\..\..\tree234.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit76] +FileName=..\..\..\unix\unix.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit77] +FileName=..\..\..\version.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit78] +FileName=..\..\..\windows\rcstuff.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit79] +FileName=..\..\..\windows\win_res.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit80] +FileName=..\..\..\windows\winhelp.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit81] +FileName=..\..\..\windows\winsecur.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit82] +FileName=..\..\..\windows\winstuff.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit83] +FileName=..\..\..\windows\putty.ico +Folder=Resource Files +Compile=0 +CompileCpp=0 +Link=0 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit84] +FileName=..\..\..\windows\puttycfg.ico +Folder=Resource Files +Compile=0 +CompileCpp=0 +Link=0 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit85] +FileName=..\..\..\windows\puttytel.rc +Folder=Resource Files +Compile=1 +CompileCpp=1 +Link=0 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[VersionInfo] +Major=0 +Minor=0 +Release=1 +Build=1 +LanguageID=1033 +CharsetID=1252 +CompanyName= +FileVersion=0.1 +FileDescription= +InternalName= +LegalCopyright= +LegalTrademarks= +OriginalFilename=puttytel.exe +ProductName=puttytel +ProductVersion=0.1 +AutoIncBuildNr=0 diff --git a/windows/DEVCPP/testcrypt/testcrypt.dev b/windows/DEVCPP/testcrypt/testcrypt.dev new file mode 100644 index 0000000..80158b8 --- /dev/null +++ b/windows/DEVCPP/testcrypt/testcrypt.dev @@ -0,0 +1,521 @@ +# DEV-C++ 5 Project File - testcrypt.dev +# ** DO NOT EDIT ** + +[Project] +FileName=testcrypt.dev +Name=testcrypt +Ver=1 +IsCpp=1 +Type=1 +Compiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ +CppCompiler=-W -D__GNUWIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNO_MULTIMON -D_MBCS_@@_ +Includes=..\..\..\.;..\..\..\charset;..\..\..\windows;..\..\..\unix +Linker=-ladvapi32 -lcomctl32 -lcomdlg32 -lgdi32 -limm32 -lshell32 -luser32 -lwinmm -lwinspool_@@_ +Libs= +UnitCount=47 +Folders="Header Files","Resource Files","Source Files" +ObjFiles= +PrivateResource=testcrypt_private.rc +ResourceIncludes=..\..\..\WINDOWS +MakeIncludes= +Icon= +ExeOutput= +ObjectOutput= +OverrideOutput=0 +OverrideOutputName=testcrypt.exe +HostApplication= +CommandLine= +UseCustomMakefile=0 +CustomMakefile= +IncludeVersionInfo=0 +SupportXPThemes=0 +CompilerSet=0 +CompilerSettings=0000000000000000000000 + +[Unit1] +FileName=..\..\..\ecc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit2] +FileName=..\..\..\marshal.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit3] +FileName=..\..\..\memory.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit4] +FileName=..\..\..\mpint.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit5] +FileName=..\..\..\sshaes.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit6] +FileName=..\..\..\ssharcf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit7] +FileName=..\..\..\sshauxcrypt.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit8] +FileName=..\..\..\sshblowf.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit9] +FileName=..\..\..\sshccp.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit10] +FileName=..\..\..\sshcrc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit11] +FileName=..\..\..\sshcrcda.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit12] +FileName=..\..\..\sshdes.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit13] +FileName=..\..\..\sshdh.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit14] +FileName=..\..\..\sshdss.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit15] +FileName=..\..\..\sshecc.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit16] +FileName=..\..\..\sshhmac.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit17] +FileName=..\..\..\sshmd5.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit18] +FileName=..\..\..\sshprime.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit19] +FileName=..\..\..\sshprng.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit20] +FileName=..\..\..\sshrsa.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit21] +FileName=..\..\..\sshsh256.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit22] +FileName=..\..\..\sshsh512.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit23] +FileName=..\..\..\sshsha.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit24] +FileName=..\..\..\testcrypt.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit25] +FileName=..\..\..\tree234.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit26] +FileName=..\..\..\utils.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit27] +FileName=..\..\..\windows\winmiscs.c +Folder=Source Files +Compile=1 +CompileCpp=0 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit28] +FileName=..\..\..\charset\charset.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit29] +FileName=..\..\..\defs.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit30] +FileName=..\..\..\ecc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit31] +FileName=..\..\..\marshal.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit32] +FileName=..\..\..\misc.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit33] +FileName=..\..\..\mpint.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit34] +FileName=..\..\..\mpint_i.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit35] +FileName=..\..\..\network.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit36] +FileName=..\..\..\putty.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit37] +FileName=..\..\..\puttymem.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit38] +FileName=..\..\..\puttyps.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit39] +FileName=..\..\..\ssh.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit40] +FileName=..\..\..\sshblowf.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit41] +FileName=..\..\..\sshsignals.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit42] +FileName=..\..\..\sshttymodes.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit43] +FileName=..\..\..\testcrypt.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit44] +FileName=..\..\..\tree234.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit45] +FileName=..\..\..\unix\unix.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit46] +FileName=..\..\..\windows\winhelp.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[Unit47] +FileName=..\..\..\windows\winstuff.h +Folder=Header Files +Compile=1 +CompileCpp=1 +Link=1 +Priority=1000 +OverrideBuildCmd=0 +BuildCmd= + +[VersionInfo] +Major=0 +Minor=0 +Release=1 +Build=1 +LanguageID=1033 +CharsetID=1252 +CompanyName= +FileVersion=0.1 +FileDescription= +InternalName= +LegalCopyright= +LegalTrademarks= +OriginalFilename=testcrypt.exe +ProductName=testcrypt +ProductVersion=0.1 +AutoIncBuildNr=0 diff --git a/windows/MSVC/plink/plink.dsp b/windows/MSVC/plink/plink.dsp index 0a6d8ff..08e1765 100644 --- a/windows/MSVC/plink/plink.dsp +++ b/windows/MSVC/plink/plink.dsp @@ -631,6 +631,10 @@ SOURCE=..\..\..\sshppl.h # End Source File # Begin Source File +SOURCE=..\..\..\sshserver.h +# End Source File +# Begin Source File + SOURCE=..\..\..\sshsignals.h # End Source File # Begin Source File diff --git a/windows/MSVC/pscp/pscp.dsp b/windows/MSVC/pscp/pscp.dsp index df964bf..d8c15bd 100644 --- a/windows/MSVC/pscp/pscp.dsp +++ b/windows/MSVC/pscp/pscp.dsp @@ -199,6 +199,10 @@ SOURCE=..\..\..\pscp.c # End Source File # Begin Source File +SOURCE=..\..\..\psftpcommon.c +# End Source File +# Begin Source File + SOURCE=..\..\..\settings.c # End Source File # Begin Source File @@ -624,6 +628,10 @@ SOURCE=..\..\..\sshppl.h # End Source File # Begin Source File +SOURCE=..\..\..\sshserver.h +# End Source File +# Begin Source File + SOURCE=..\..\..\sshsignals.h # End Source File # Begin Source File diff --git a/windows/MSVC/psftp/psftp.dsp b/windows/MSVC/psftp/psftp.dsp index bdeb498..2797af3 100644 --- a/windows/MSVC/psftp/psftp.dsp +++ b/windows/MSVC/psftp/psftp.dsp @@ -199,6 +199,10 @@ SOURCE=..\..\..\psftp.c # End Source File # Begin Source File +SOURCE=..\..\..\psftpcommon.c +# End Source File +# Begin Source File + SOURCE=..\..\..\settings.c # End Source File # Begin Source File @@ -624,6 +628,10 @@ SOURCE=..\..\..\sshppl.h # End Source File # Begin Source File +SOURCE=..\..\..\sshserver.h +# End Source File +# Begin Source File + SOURCE=..\..\..\sshsignals.h # End Source File # Begin Source File diff --git a/windows/MSVC/putty/putty.dsp b/windows/MSVC/putty/putty.dsp index 305d470..c17314d 100644 --- a/windows/MSVC/putty/putty.dsp +++ b/windows/MSVC/putty/putty.dsp @@ -146,10 +146,6 @@ SOURCE=..\..\..\ldisc.c # End Source File # Begin Source File -SOURCE=..\..\..\ldiscucs.c -# End Source File -# Begin Source File - SOURCE=..\..\..\logging.c # End Source File # Begin Source File @@ -675,6 +671,10 @@ SOURCE=..\..\..\sshppl.h # End Source File # Begin Source File +SOURCE=..\..\..\sshserver.h +# End Source File +# Begin Source File + SOURCE=..\..\..\sshsignals.h # End Source File # Begin Source File diff --git a/windows/MSVC/puttytel/puttytel.dsp b/windows/MSVC/puttytel/puttytel.dsp index 9f8f980..16da18e 100644 --- a/windows/MSVC/puttytel/puttytel.dsp +++ b/windows/MSVC/puttytel/puttytel.dsp @@ -130,10 +130,6 @@ SOURCE=..\..\..\ldisc.c # End Source File # Begin Source File -SOURCE=..\..\..\ldiscucs.c -# End Source File -# Begin Source File - SOURCE=..\..\..\logging.c # End Source File # Begin Source File diff --git a/windows/MSVC/testcrypt/testcrypt.dsp b/windows/MSVC/testcrypt/testcrypt.dsp new file mode 100644 index 0000000..15598b2 --- /dev/null +++ b/windows/MSVC/testcrypt/testcrypt.dsp @@ -0,0 +1,293 @@ +# Microsoft Developer Studio Project File - Name="testcrypt" - Package Owner=<4> +# Microsoft Developer Studio Generated Build File, Format Version 6.00 +# ** DO NOT EDIT ** + +# TARGTYPE "Win32 (x86) Application" 0x0101 + +CFG=testcrypt - Win32 Debug +!MESSAGE This is not a valid makefile. To build this project using NMAKE, +!MESSAGE use the Export Makefile command and run +!MESSAGE +!MESSAGE NMAKE /f "testcrypt.mak". +!MESSAGE +!MESSAGE You can specify a configuration when running NMAKE +!MESSAGE by defining the macro CFG on the command line. For example: +!MESSAGE +!MESSAGE NMAKE /f "testcrypt.mak" CFG="testcrypt - Win32 Debug" +!MESSAGE +!MESSAGE Possible choices for configuration are: +!MESSAGE +!MESSAGE "testcrypt - Win32 Release" (based on "Win32 (x86) Application") +!MESSAGE "testcrypt - Win32 Debug" (based on "Win32 (x86) Application") +!MESSAGE + +# Begin Project +# PROP AllowPerConfigDependencies 0 +# PROP Scc_ProjName "" +# PROP Scc_LocalPath "" +CPP=cl.exe +MTL=midl.exe +RSC=rc.exe + +!IF "$(CFG)" == "testcrypt - Win32 Release" + +# PROP BASE Use_MFC 0 +# PROP BASE Use_Debug_Libraries 0 +# PROP BASE Output_Dir "Release" +# PROP BASE Intermediate_Dir "Release" +# PROP BASE Target_Dir "" +# PROP Use_MFC 0 +# PROP Use_Debug_Libraries 0 +# PROP Output_Dir "Release" +# PROP Intermediate_Dir "Release" +# PROP Ignore_Export_Lib 0 +# PROP Target_Dir "" +# ADD BASE CPP /nologo /W3 /GX /O2 /I "..\..\..\./" /I "..\..\..\charset/" /I "..\..\..\windows/" /I "..\..\..\unix/" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /YX /FD /c +# ADD CPP /nologo /W3 /GX /O2 /I "..\..\..\./" /I "..\..\..\charset/" /I "..\..\..\windows/" /I "..\..\..\unix/" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /YX /FD /c +# ADD BASE MTL /nologo /D "NDEBUG" /mktyplib203 /win32 +# ADD MTL /nologo /D "NDEBUG" /mktyplib203 /win32 +# ADD BASE RSC /l 0x809 /d "NDEBUG" +# ADD RSC /l 0x809 /d "NDEBUG" +BSC32=bscmake.exe +# ADD BASE BSC32 /nologo +# ADD BSC32 /nologo +LINK32=link.exe +# ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:console /machine:I386 +# ADD LINK32 /nologo /subsystem:console /machine:I386 +# SUBTRACT LINK32 /pdb:none + +!ELSEIF "$(CFG)" == "testcrypt - Win32 Debug" + +# PROP BASE Use_MFC 0 +# PROP BASE Use_Debug_Libraries 1 +# PROP BASE Output_Dir "Debug" +# PROP BASE Intermediate_Dir "Debug" +# PROP BASE Target_Dir "" +# PROP Use_MFC 0 +# PROP Use_Debug_Libraries 1 +# PROP Output_Dir "Debug" +# PROP Intermediate_Dir "Debug" +# PROP Ignore_Export_Lib 0 +# PROP Target_Dir "" +# ADD BASE CPP /nologo /W3 /Gm /GX /ZI /Od /I "..\..\..\./" /I "..\..\..\charset/" /I "..\..\..\windows/" /I "..\..\..\unix/" /D "WIN32" /D "_DEBUG" /D "_WINDOWS" /D "_MBCS" /YX /FD /GZ /c +# ADD CPP /nologo /W3 /Gm /GX /ZI /Od /I "..\..\..\./" /I "..\..\..\charset/" /I "..\..\..\windows/" /I "..\..\..\unix/" /D "WIN32" /D "_DEBUG" /D "_WINDOWS" /D "_MBCS" /YX /FD /GZ /c +# ADD BASE MTL /nologo /D "_DEBUG" /mktyplib203 /win32 +# ADD MTL /nologo /D "_DEBUG" /mktyplib203 /win32 +# ADD BASE RSC /l 0x809 /d "_DEBUG" +# ADD RSC /l 0x809 /d "_DEBUG" +BSC32=bscmake.exe +# ADD BASE BSC32 /nologo +# ADD BSC32 /nologo +LINK32=link.exe +# ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:console /debug /machine:I386 /pdbtype:sept +# ADD LINK32 /nologo /subsystem:console /debug /machine:I386 /pdbtype:sept +# SUBTRACT LINK32 /pdb:none + +!ENDIF + +# Begin Target + +# Name "testcrypt - Win32 Release" +# Name "testcrypt - Win32 Debug" +# Begin Group "Source Files" + +# PROP Default_Filter "cpp;c;cxx;rc;def;r;odl;idl;hpj;bat" +# Begin Source File + +SOURCE=..\..\..\ecc.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\marshal.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\memory.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\mpint.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshaes.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\ssharcf.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshauxcrypt.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshblowf.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshccp.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshcrc.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshcrcda.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshdes.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshdh.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshdss.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshecc.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshhmac.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshmd5.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshprime.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshprng.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshrsa.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshsh256.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshsh512.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshsha.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\testcrypt.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\tree234.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\utils.c +# End Source File +# Begin Source File + +SOURCE=..\..\..\windows\winmiscs.c +# End Source File +# End Group +# Begin Group "Header Files" + +# PROP Default_Filter "h;hpp;hxx;hm;inl" +# Begin Source File + +SOURCE=..\..\..\charset\charset.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\defs.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\ecc.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\marshal.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\misc.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\mpint.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\mpint_i.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\network.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\putty.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\puttymem.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\puttyps.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\ssh.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshblowf.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshsignals.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\sshttymodes.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\testcrypt.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\tree234.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\unix\unix.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\windows\winhelp.h +# End Source File +# Begin Source File + +SOURCE=..\..\..\windows\winstuff.h +# End Source File +# End Group +# Begin Group "Resource Files" + +# PROP Default_Filter "ico;cur;bmp;dlg;rc2;rct;bin;rgs;gif;jpg;jpeg;jpe" +# End Group +# End Target +# End Project diff --git a/windows/Makefile.clangcl b/windows/Makefile.clangcl new file mode 100644 index 0000000..1b256a6 --- /dev/null +++ b/windows/Makefile.clangcl @@ -0,0 +1,2161 @@ +# Makefile for cross-compiling putty using clang-cl, lld-link, +# and llvm-rc, using GNU make on Linux. +# +# This file was created by `mkfiles.pl' from the `Recipe' file. +# DO NOT EDIT THIS FILE DIRECTLY; edit Recipe or mkfiles.pl instead. +# +# Extra options you can set: +# +# - COMPAT=/DAUTO_WINSOCK (Windows only) +# Causes PuTTY to assume that includes its own WinSock +# header file, so that it won't try to include . +# +# - COMPAT=/DWINSOCK_TWO (Windows only) +# Causes the PuTTY utilities to include instead of +# , except Plink which _needs_ WinSock 2 so it already +# does this. +# +# - COMPAT=/DNO_SECURITY (Windows only) +# Disables use of , which is not available with some +# development environments (such as very old versions of the +# mingw/Cygwin GNU toolchain). This has the following effects: +# - Pageant won't care about the local user ID of processes +# accessing it; a version of Pageant built with this option +# will therefore refuse to run under NT-series OSes on +# security grounds (although it will run fine on Win95-series +# OSes where there is no access control anyway). +# - SSH connection sharing is disabled. +# - There is no support for restriction of the process ACLs. +# +# - COMPAT=/DNO_MULTIMON (Windows only) +# Disables PuTTY's use of , which is not available +# with some development environments. This means that PuTTY's +# full-screen mode (configurable to work on Alt-Enter) will +# not behave usefully in a multi-monitor environment. +# +# - COMPAT=/DNO_HTMLHELP (Windows only) +# Disables PuTTY's use of , which is not available +# with some development environments. +# +# If you don't have this header, you may be able to use the copy +# supplied with HTML Help Workshop. +# +# - RCFL=/DNO_MANIFESTS (Windows only) +# Disables inclusion of XML application manifests in the PuTTY +# binaries. This may be necessary to build for 64-bit Windows; +# the manifests are only included to use the XP GUI style on +# Windows XP, and the architecture tags are a lie on 64-bit. +# +# - COMPAT=/DNO_IPV6 +# Disables PuTTY's ability to make IPv6 connections, enabling +# it to compile under development environments which do not +# support IPv6 in their header files. +# +# - COMPAT=/DNO_GSSAPI +# Disables PuTTY's ability to use GSSAPI functions for +# authentication and key exchange. +# +# - COMPAT=/DSTATIC_GSSAPI +# Causes PuTTY to try to link statically against the GSSAPI +# library instead of the default of doing it at run time. +# +# - COMPAT=/DMSVC4 (Windows only) +# - RCFL=/DMSVC4 +# Makes a couple of minor changes so that PuTTY compiles using +# MSVC 4. You will also need /DNO_SECURITY and /DNO_MULTIMON. +# +# - COMPAT=/DNO_SECUREZEROMEMORY (Windows only) +# Disables PuTTY's use of SecureZeroMemory(), which is missing +# from some environments' header files. +# +# - XFLAGS=/DTELNET_DEFAULT +# Causes PuTTY to default to the Telnet protocol (in the absence +# of Default Settings and so on to the contrary). Normally PuTTY +# will default to SSH. +# +# - XFLAGS=/DDEBUG +# Causes PuTTY to enable internal debugging. +# +# - XFLAGS=/DMALLOC_LOG +# Causes PuTTY to emit a file called putty_mem.log, logging every +# memory allocation and free, so you can track memory leaks. +# +# - XFLAGS=/DMINEFIELD (Windows only) +# Causes PuTTY to use a custom memory allocator, similar in +# concept to Electric Fence, in place of regular malloc(). Wastes +# huge amounts of RAM, but should cause heap-corruption bugs to +# show up as GPFs at the point of failure rather than appearing +# later on as second-level damage. +# +# - XFLAGS=/DFUZZING +# Builds a version of PuTTY with some tweaks to make fuzz testing +# easier: the SSH random number generator is replaced by one that +# always returns the same thing. Note that this makes SSH +# completely insecure -- a FUZZING build should never be used to +# connect to a real server. + +CCCMD = clang-cl +RCCMD = llvm-rc +ifeq ($(Platform),x64) +CCTARGET = x86_64-pc-windows-msvc18.0.0 +PLATFORMCFLAGS = +else ifeq ($(Platform),arm) +CCTARGET = arm-pc-windows-msvc18.0.0 +PLATFORMCFLAGS = /D_ARM_WINAPI_PARTITION_DESKTOP_SDK_AVAILABLE /GS- +else ifeq ($(Platform),arm64) +CCTARGET = arm64-pc-windows-msvc18.0.0 +PLATFORMCFLAGS = /D_ARM_WINAPI_PARTITION_DESKTOP_SDK_AVAILABLE /GS- +else +CCTARGET = i386-pc-windows-msvc18.0.0 +PLATFORMCFLAGS = +endif +CC = $(CCCMD) +RC = $(RCCMD) /c 1252 +RCPREPROC = $(CCCMD) /P /TC +LD = lld-link + +# C compilation flags +CFLAGS = --target=$(CCTARGET) /nologo /W3 /O1 -Wvla -I.././ -I../charset/ \ + -I../windows/ -I../unix/ /D_WINDOWS /D_WIN32_WINDOWS=0x500 \ + /DWINVER=0x500 /D_CRT_SECURE_NO_WARNINGS \ + /D_WINSOCK_DEPRECATED_NO_WARNINGS $(PLATFORMCFLAGS) +LFLAGS = /incremental:no /dynamicbase /nxcompat +RCPPFLAGS = -I.././ -I../charset/ -I../windows/ -I../unix/ -DWIN32 -D_WIN32 \ + -DWINVER=0x0400 $(RCFL) + +CFLAGS += /DHAS_GSSAPI + + +all: $(BUILDDIR)pageant.exe $(BUILDDIR)plink.exe $(BUILDDIR)pscp.exe \ + $(BUILDDIR)psftp.exe $(BUILDDIR)putty.exe \ + $(BUILDDIR)puttygen.exe $(BUILDDIR)puttytel.exe \ + $(BUILDDIR)testcrypt.exe + +$(BUILDDIR)pageant.exe: $(BUILDDIR)aqsync.obj $(BUILDDIR)conf.obj \ + $(BUILDDIR)ecc.obj $(BUILDDIR)marshal.obj \ + $(BUILDDIR)memory.obj $(BUILDDIR)misc.obj \ + $(BUILDDIR)mpint.obj $(BUILDDIR)pageant.obj \ + $(BUILDDIR)pageant.res $(BUILDDIR)sshaes.obj \ + $(BUILDDIR)sshauxcrypt.obj $(BUILDDIR)sshdes.obj \ + $(BUILDDIR)sshdss.obj $(BUILDDIR)sshecc.obj \ + $(BUILDDIR)sshhmac.obj $(BUILDDIR)sshmd5.obj \ + $(BUILDDIR)sshpubk.obj $(BUILDDIR)sshrsa.obj \ + $(BUILDDIR)sshsh256.obj $(BUILDDIR)sshsh512.obj \ + $(BUILDDIR)sshsha.obj $(BUILDDIR)stripctrl.obj \ + $(BUILDDIR)tree234.obj $(BUILDDIR)utils.obj \ + $(BUILDDIR)version.obj $(BUILDDIR)wcwidth.obj \ + $(BUILDDIR)winhelp.obj $(BUILDDIR)winmisc.obj \ + $(BUILDDIR)winmiscs.obj $(BUILDDIR)winpgnt.obj \ + $(BUILDDIR)winpgntc.obj $(BUILDDIR)winsecur.obj \ + $(BUILDDIR)winutils.obj + $(LD) $(LFLAGS) $(XLFLAGS) /out:$(BUILDDIR)pageant.exe \ + /lldmap:$(BUILDDIR)pageant.map \ + /subsystem:windows$(SUBSYSVER) $(EXTRA_windows) advapi32.lib \ + $(BUILDDIR)aqsync.obj comdlg32.lib $(BUILDDIR)conf.obj \ + $(BUILDDIR)ecc.obj gdi32.lib imm32.lib \ + $(BUILDDIR)marshal.obj $(BUILDDIR)memory.obj \ + $(BUILDDIR)misc.obj $(BUILDDIR)mpint.obj ole32.lib \ + $(BUILDDIR)pageant.obj $(BUILDDIR)pageant.res shell32.lib \ + $(BUILDDIR)sshaes.obj $(BUILDDIR)sshauxcrypt.obj \ + $(BUILDDIR)sshdes.obj $(BUILDDIR)sshdss.obj \ + $(BUILDDIR)sshecc.obj $(BUILDDIR)sshhmac.obj \ + $(BUILDDIR)sshmd5.obj $(BUILDDIR)sshpubk.obj \ + $(BUILDDIR)sshrsa.obj $(BUILDDIR)sshsh256.obj \ + $(BUILDDIR)sshsh512.obj $(BUILDDIR)sshsha.obj \ + $(BUILDDIR)stripctrl.obj $(BUILDDIR)tree234.obj user32.lib \ + $(BUILDDIR)utils.obj $(BUILDDIR)version.obj \ + $(BUILDDIR)wcwidth.obj $(BUILDDIR)winhelp.obj \ + $(BUILDDIR)winmisc.obj $(BUILDDIR)winmiscs.obj \ + $(BUILDDIR)winpgnt.obj $(BUILDDIR)winpgntc.obj \ + $(BUILDDIR)winsecur.obj $(BUILDDIR)winutils.obj \ + $(EXTRA_libs) + +$(BUILDDIR)plink.exe: $(BUILDDIR)agentf.obj $(BUILDDIR)aqsync.obj \ + $(BUILDDIR)be_all_s.obj $(BUILDDIR)be_misc.obj \ + $(BUILDDIR)callback.obj $(BUILDDIR)cmdline.obj \ + $(BUILDDIR)conf.obj $(BUILDDIR)cproxy.obj $(BUILDDIR)ecc.obj \ + $(BUILDDIR)errsock.obj $(BUILDDIR)ldisc.obj \ + $(BUILDDIR)logging.obj $(BUILDDIR)mainchan.obj \ + $(BUILDDIR)marshal.obj $(BUILDDIR)memory.obj \ + $(BUILDDIR)misc.obj $(BUILDDIR)miscucs.obj \ + $(BUILDDIR)mpint.obj $(BUILDDIR)noterm.obj \ + $(BUILDDIR)nullplug.obj $(BUILDDIR)pgssapi.obj \ + $(BUILDDIR)pinger.obj $(BUILDDIR)plink.res \ + $(BUILDDIR)portfwd.obj $(BUILDDIR)proxy.obj \ + $(BUILDDIR)raw.obj $(BUILDDIR)rlogin.obj \ + $(BUILDDIR)sessprep.obj $(BUILDDIR)settings.obj \ + $(BUILDDIR)ssh.obj $(BUILDDIR)ssh1bpp.obj \ + $(BUILDDIR)ssh1censor.obj $(BUILDDIR)ssh1connection.obj \ + $(BUILDDIR)ssh1connection-client.obj \ + $(BUILDDIR)ssh1login.obj $(BUILDDIR)ssh2bpp.obj \ + $(BUILDDIR)ssh2bpp-bare.obj $(BUILDDIR)ssh2censor.obj \ + $(BUILDDIR)ssh2connection.obj \ + $(BUILDDIR)ssh2connection-client.obj \ + $(BUILDDIR)ssh2kex-client.obj $(BUILDDIR)ssh2transhk.obj \ + $(BUILDDIR)ssh2transport.obj $(BUILDDIR)ssh2userauth.obj \ + $(BUILDDIR)sshaes.obj $(BUILDDIR)ssharcf.obj \ + $(BUILDDIR)sshauxcrypt.obj $(BUILDDIR)sshblowf.obj \ + $(BUILDDIR)sshccp.obj $(BUILDDIR)sshcommon.obj \ + $(BUILDDIR)sshcrc.obj $(BUILDDIR)sshcrcda.obj \ + $(BUILDDIR)sshdes.obj $(BUILDDIR)sshdh.obj \ + $(BUILDDIR)sshdss.obj $(BUILDDIR)sshecc.obj \ + $(BUILDDIR)sshgssc.obj $(BUILDDIR)sshhmac.obj \ + $(BUILDDIR)sshmac.obj $(BUILDDIR)sshmd5.obj \ + $(BUILDDIR)sshprng.obj $(BUILDDIR)sshpubk.obj \ + $(BUILDDIR)sshrand.obj $(BUILDDIR)sshrsa.obj \ + $(BUILDDIR)sshsh256.obj $(BUILDDIR)sshsh512.obj \ + $(BUILDDIR)sshsha.obj $(BUILDDIR)sshshare.obj \ + $(BUILDDIR)sshverstring.obj $(BUILDDIR)sshzlib.obj \ + $(BUILDDIR)stripctrl.obj $(BUILDDIR)telnet.obj \ + $(BUILDDIR)timing.obj $(BUILDDIR)tree234.obj \ + $(BUILDDIR)utils.obj $(BUILDDIR)version.obj \ + $(BUILDDIR)wcwidth.obj $(BUILDDIR)wildcard.obj \ + $(BUILDDIR)wincapi.obj $(BUILDDIR)wincons.obj \ + $(BUILDDIR)windefs.obj $(BUILDDIR)wingss.obj \ + $(BUILDDIR)winhandl.obj $(BUILDDIR)winhsock.obj \ + $(BUILDDIR)winmisc.obj $(BUILDDIR)winmiscs.obj \ + $(BUILDDIR)winnet.obj $(BUILDDIR)winnohlp.obj \ + $(BUILDDIR)winnoise.obj $(BUILDDIR)winnojmp.obj \ + $(BUILDDIR)winnpc.obj $(BUILDDIR)winnps.obj \ + $(BUILDDIR)winpgntc.obj $(BUILDDIR)winplink.obj \ + $(BUILDDIR)winproxy.obj $(BUILDDIR)winsecur.obj \ + $(BUILDDIR)winser.obj $(BUILDDIR)winshare.obj \ + $(BUILDDIR)winstore.obj $(BUILDDIR)wintime.obj \ + $(BUILDDIR)winucs.obj $(BUILDDIR)winx11.obj \ + $(BUILDDIR)x11fwd.obj + $(LD) $(LFLAGS) $(XLFLAGS) /out:$(BUILDDIR)plink.exe \ + /lldmap:$(BUILDDIR)plink.map /subsystem:console$(SUBSYSVER) \ + $(EXTRA_console) advapi32.lib $(BUILDDIR)agentf.obj \ + $(BUILDDIR)aqsync.obj $(BUILDDIR)be_all_s.obj \ + $(BUILDDIR)be_misc.obj $(BUILDDIR)callback.obj \ + $(BUILDDIR)cmdline.obj comdlg32.lib $(BUILDDIR)conf.obj \ + $(BUILDDIR)cproxy.obj $(BUILDDIR)ecc.obj \ + $(BUILDDIR)errsock.obj gdi32.lib imm32.lib \ + $(BUILDDIR)ldisc.obj $(BUILDDIR)logging.obj \ + $(BUILDDIR)mainchan.obj $(BUILDDIR)marshal.obj \ + $(BUILDDIR)memory.obj $(BUILDDIR)misc.obj \ + $(BUILDDIR)miscucs.obj $(BUILDDIR)mpint.obj \ + $(BUILDDIR)noterm.obj $(BUILDDIR)nullplug.obj ole32.lib \ + $(BUILDDIR)pgssapi.obj $(BUILDDIR)pinger.obj \ + $(BUILDDIR)plink.res $(BUILDDIR)portfwd.obj \ + $(BUILDDIR)proxy.obj $(BUILDDIR)raw.obj \ + $(BUILDDIR)rlogin.obj $(BUILDDIR)sessprep.obj \ + $(BUILDDIR)settings.obj shell32.lib $(BUILDDIR)ssh.obj \ + $(BUILDDIR)ssh1bpp.obj $(BUILDDIR)ssh1censor.obj \ + $(BUILDDIR)ssh1connection.obj \ + $(BUILDDIR)ssh1connection-client.obj \ + $(BUILDDIR)ssh1login.obj $(BUILDDIR)ssh2bpp.obj \ + $(BUILDDIR)ssh2bpp-bare.obj $(BUILDDIR)ssh2censor.obj \ + $(BUILDDIR)ssh2connection.obj \ + $(BUILDDIR)ssh2connection-client.obj \ + $(BUILDDIR)ssh2kex-client.obj $(BUILDDIR)ssh2transhk.obj \ + $(BUILDDIR)ssh2transport.obj $(BUILDDIR)ssh2userauth.obj \ + $(BUILDDIR)sshaes.obj $(BUILDDIR)ssharcf.obj \ + $(BUILDDIR)sshauxcrypt.obj $(BUILDDIR)sshblowf.obj \ + $(BUILDDIR)sshccp.obj $(BUILDDIR)sshcommon.obj \ + $(BUILDDIR)sshcrc.obj $(BUILDDIR)sshcrcda.obj \ + $(BUILDDIR)sshdes.obj $(BUILDDIR)sshdh.obj \ + $(BUILDDIR)sshdss.obj $(BUILDDIR)sshecc.obj \ + $(BUILDDIR)sshgssc.obj $(BUILDDIR)sshhmac.obj \ + $(BUILDDIR)sshmac.obj $(BUILDDIR)sshmd5.obj \ + $(BUILDDIR)sshprng.obj $(BUILDDIR)sshpubk.obj \ + $(BUILDDIR)sshrand.obj $(BUILDDIR)sshrsa.obj \ + $(BUILDDIR)sshsh256.obj $(BUILDDIR)sshsh512.obj \ + $(BUILDDIR)sshsha.obj $(BUILDDIR)sshshare.obj \ + $(BUILDDIR)sshverstring.obj $(BUILDDIR)sshzlib.obj \ + $(BUILDDIR)stripctrl.obj $(BUILDDIR)telnet.obj \ + $(BUILDDIR)timing.obj $(BUILDDIR)tree234.obj user32.lib \ + $(BUILDDIR)utils.obj $(BUILDDIR)version.obj \ + $(BUILDDIR)wcwidth.obj $(BUILDDIR)wildcard.obj \ + $(BUILDDIR)wincapi.obj $(BUILDDIR)wincons.obj \ + $(BUILDDIR)windefs.obj $(BUILDDIR)wingss.obj \ + $(BUILDDIR)winhandl.obj $(BUILDDIR)winhsock.obj \ + $(BUILDDIR)winmisc.obj $(BUILDDIR)winmiscs.obj \ + $(BUILDDIR)winnet.obj $(BUILDDIR)winnohlp.obj \ + $(BUILDDIR)winnoise.obj $(BUILDDIR)winnojmp.obj \ + $(BUILDDIR)winnpc.obj $(BUILDDIR)winnps.obj \ + $(BUILDDIR)winpgntc.obj $(BUILDDIR)winplink.obj \ + $(BUILDDIR)winproxy.obj $(BUILDDIR)winsecur.obj \ + $(BUILDDIR)winser.obj $(BUILDDIR)winshare.obj \ + $(BUILDDIR)winstore.obj $(BUILDDIR)wintime.obj \ + $(BUILDDIR)winucs.obj $(BUILDDIR)winx11.obj \ + $(BUILDDIR)x11fwd.obj $(EXTRA_libs) + +$(BUILDDIR)pscp.exe: $(BUILDDIR)agentf.obj $(BUILDDIR)aqsync.obj \ + $(BUILDDIR)be_misc.obj $(BUILDDIR)be_ssh.obj \ + $(BUILDDIR)callback.obj $(BUILDDIR)cmdline.obj \ + $(BUILDDIR)conf.obj $(BUILDDIR)cproxy.obj $(BUILDDIR)ecc.obj \ + $(BUILDDIR)errsock.obj $(BUILDDIR)logging.obj \ + $(BUILDDIR)mainchan.obj $(BUILDDIR)marshal.obj \ + $(BUILDDIR)memory.obj $(BUILDDIR)misc.obj \ + $(BUILDDIR)miscucs.obj $(BUILDDIR)mpint.obj \ + $(BUILDDIR)nullplug.obj $(BUILDDIR)pgssapi.obj \ + $(BUILDDIR)pinger.obj $(BUILDDIR)portfwd.obj \ + $(BUILDDIR)proxy.obj $(BUILDDIR)pscp.obj $(BUILDDIR)pscp.res \ + $(BUILDDIR)psftpcommon.obj $(BUILDDIR)settings.obj \ + $(BUILDDIR)sftp.obj $(BUILDDIR)sftpcommon.obj \ + $(BUILDDIR)ssh.obj $(BUILDDIR)ssh1bpp.obj \ + $(BUILDDIR)ssh1censor.obj $(BUILDDIR)ssh1connection.obj \ + $(BUILDDIR)ssh1connection-client.obj \ + $(BUILDDIR)ssh1login.obj $(BUILDDIR)ssh2bpp.obj \ + $(BUILDDIR)ssh2bpp-bare.obj $(BUILDDIR)ssh2censor.obj \ + $(BUILDDIR)ssh2connection.obj \ + $(BUILDDIR)ssh2connection-client.obj \ + $(BUILDDIR)ssh2kex-client.obj $(BUILDDIR)ssh2transhk.obj \ + $(BUILDDIR)ssh2transport.obj $(BUILDDIR)ssh2userauth.obj \ + $(BUILDDIR)sshaes.obj $(BUILDDIR)ssharcf.obj \ + $(BUILDDIR)sshauxcrypt.obj $(BUILDDIR)sshblowf.obj \ + $(BUILDDIR)sshccp.obj $(BUILDDIR)sshcommon.obj \ + $(BUILDDIR)sshcrc.obj $(BUILDDIR)sshcrcda.obj \ + $(BUILDDIR)sshdes.obj $(BUILDDIR)sshdh.obj \ + $(BUILDDIR)sshdss.obj $(BUILDDIR)sshecc.obj \ + $(BUILDDIR)sshgssc.obj $(BUILDDIR)sshhmac.obj \ + $(BUILDDIR)sshmac.obj $(BUILDDIR)sshmd5.obj \ + $(BUILDDIR)sshprng.obj $(BUILDDIR)sshpubk.obj \ + $(BUILDDIR)sshrand.obj $(BUILDDIR)sshrsa.obj \ + $(BUILDDIR)sshsh256.obj $(BUILDDIR)sshsh512.obj \ + $(BUILDDIR)sshsha.obj $(BUILDDIR)sshshare.obj \ + $(BUILDDIR)sshverstring.obj $(BUILDDIR)sshzlib.obj \ + $(BUILDDIR)stripctrl.obj $(BUILDDIR)timing.obj \ + $(BUILDDIR)tree234.obj $(BUILDDIR)utils.obj \ + $(BUILDDIR)version.obj $(BUILDDIR)wcwidth.obj \ + $(BUILDDIR)wildcard.obj $(BUILDDIR)wincapi.obj \ + $(BUILDDIR)wincons.obj $(BUILDDIR)windefs.obj \ + $(BUILDDIR)wingss.obj $(BUILDDIR)winhandl.obj \ + $(BUILDDIR)winhsock.obj $(BUILDDIR)winmisc.obj \ + $(BUILDDIR)winmiscs.obj $(BUILDDIR)winnet.obj \ + $(BUILDDIR)winnohlp.obj $(BUILDDIR)winnoise.obj \ + $(BUILDDIR)winnojmp.obj $(BUILDDIR)winnpc.obj \ + $(BUILDDIR)winnps.obj $(BUILDDIR)winpgntc.obj \ + $(BUILDDIR)winproxy.obj $(BUILDDIR)winsecur.obj \ + $(BUILDDIR)winsftp.obj $(BUILDDIR)winshare.obj \ + $(BUILDDIR)winstore.obj $(BUILDDIR)wintime.obj \ + $(BUILDDIR)winucs.obj $(BUILDDIR)x11fwd.obj + $(LD) $(LFLAGS) $(XLFLAGS) /out:$(BUILDDIR)pscp.exe \ + /lldmap:$(BUILDDIR)pscp.map /subsystem:console$(SUBSYSVER) \ + $(EXTRA_console) advapi32.lib $(BUILDDIR)agentf.obj \ + $(BUILDDIR)aqsync.obj $(BUILDDIR)be_misc.obj \ + $(BUILDDIR)be_ssh.obj $(BUILDDIR)callback.obj \ + $(BUILDDIR)cmdline.obj comdlg32.lib $(BUILDDIR)conf.obj \ + $(BUILDDIR)cproxy.obj $(BUILDDIR)ecc.obj \ + $(BUILDDIR)errsock.obj gdi32.lib imm32.lib \ + $(BUILDDIR)logging.obj $(BUILDDIR)mainchan.obj \ + $(BUILDDIR)marshal.obj $(BUILDDIR)memory.obj \ + $(BUILDDIR)misc.obj $(BUILDDIR)miscucs.obj \ + $(BUILDDIR)mpint.obj $(BUILDDIR)nullplug.obj ole32.lib \ + $(BUILDDIR)pgssapi.obj $(BUILDDIR)pinger.obj \ + $(BUILDDIR)portfwd.obj $(BUILDDIR)proxy.obj \ + $(BUILDDIR)pscp.obj $(BUILDDIR)pscp.res \ + $(BUILDDIR)psftpcommon.obj $(BUILDDIR)settings.obj \ + $(BUILDDIR)sftp.obj $(BUILDDIR)sftpcommon.obj shell32.lib \ + $(BUILDDIR)ssh.obj $(BUILDDIR)ssh1bpp.obj \ + $(BUILDDIR)ssh1censor.obj $(BUILDDIR)ssh1connection.obj \ + $(BUILDDIR)ssh1connection-client.obj \ + $(BUILDDIR)ssh1login.obj $(BUILDDIR)ssh2bpp.obj \ + $(BUILDDIR)ssh2bpp-bare.obj $(BUILDDIR)ssh2censor.obj \ + $(BUILDDIR)ssh2connection.obj \ + $(BUILDDIR)ssh2connection-client.obj \ + $(BUILDDIR)ssh2kex-client.obj $(BUILDDIR)ssh2transhk.obj \ + $(BUILDDIR)ssh2transport.obj $(BUILDDIR)ssh2userauth.obj \ + $(BUILDDIR)sshaes.obj $(BUILDDIR)ssharcf.obj \ + $(BUILDDIR)sshauxcrypt.obj $(BUILDDIR)sshblowf.obj \ + $(BUILDDIR)sshccp.obj $(BUILDDIR)sshcommon.obj \ + $(BUILDDIR)sshcrc.obj $(BUILDDIR)sshcrcda.obj \ + $(BUILDDIR)sshdes.obj $(BUILDDIR)sshdh.obj \ + $(BUILDDIR)sshdss.obj $(BUILDDIR)sshecc.obj \ + $(BUILDDIR)sshgssc.obj $(BUILDDIR)sshhmac.obj \ + $(BUILDDIR)sshmac.obj $(BUILDDIR)sshmd5.obj \ + $(BUILDDIR)sshprng.obj $(BUILDDIR)sshpubk.obj \ + $(BUILDDIR)sshrand.obj $(BUILDDIR)sshrsa.obj \ + $(BUILDDIR)sshsh256.obj $(BUILDDIR)sshsh512.obj \ + $(BUILDDIR)sshsha.obj $(BUILDDIR)sshshare.obj \ + $(BUILDDIR)sshverstring.obj $(BUILDDIR)sshzlib.obj \ + $(BUILDDIR)stripctrl.obj $(BUILDDIR)timing.obj \ + $(BUILDDIR)tree234.obj user32.lib $(BUILDDIR)utils.obj \ + $(BUILDDIR)version.obj $(BUILDDIR)wcwidth.obj \ + $(BUILDDIR)wildcard.obj $(BUILDDIR)wincapi.obj \ + $(BUILDDIR)wincons.obj $(BUILDDIR)windefs.obj \ + $(BUILDDIR)wingss.obj $(BUILDDIR)winhandl.obj \ + $(BUILDDIR)winhsock.obj $(BUILDDIR)winmisc.obj \ + $(BUILDDIR)winmiscs.obj $(BUILDDIR)winnet.obj \ + $(BUILDDIR)winnohlp.obj $(BUILDDIR)winnoise.obj \ + $(BUILDDIR)winnojmp.obj $(BUILDDIR)winnpc.obj \ + $(BUILDDIR)winnps.obj $(BUILDDIR)winpgntc.obj \ + $(BUILDDIR)winproxy.obj $(BUILDDIR)winsecur.obj \ + $(BUILDDIR)winsftp.obj $(BUILDDIR)winshare.obj \ + $(BUILDDIR)winstore.obj $(BUILDDIR)wintime.obj \ + $(BUILDDIR)winucs.obj $(BUILDDIR)x11fwd.obj $(EXTRA_libs) + +$(BUILDDIR)psftp.exe: $(BUILDDIR)agentf.obj $(BUILDDIR)aqsync.obj \ + $(BUILDDIR)be_misc.obj $(BUILDDIR)be_ssh.obj \ + $(BUILDDIR)callback.obj $(BUILDDIR)cmdline.obj \ + $(BUILDDIR)conf.obj $(BUILDDIR)cproxy.obj $(BUILDDIR)ecc.obj \ + $(BUILDDIR)errsock.obj $(BUILDDIR)logging.obj \ + $(BUILDDIR)mainchan.obj $(BUILDDIR)marshal.obj \ + $(BUILDDIR)memory.obj $(BUILDDIR)misc.obj \ + $(BUILDDIR)miscucs.obj $(BUILDDIR)mpint.obj \ + $(BUILDDIR)nullplug.obj $(BUILDDIR)pgssapi.obj \ + $(BUILDDIR)pinger.obj $(BUILDDIR)portfwd.obj \ + $(BUILDDIR)proxy.obj $(BUILDDIR)psftp.obj \ + $(BUILDDIR)psftp.res $(BUILDDIR)psftpcommon.obj \ + $(BUILDDIR)settings.obj $(BUILDDIR)sftp.obj \ + $(BUILDDIR)sftpcommon.obj $(BUILDDIR)ssh.obj \ + $(BUILDDIR)ssh1bpp.obj $(BUILDDIR)ssh1censor.obj \ + $(BUILDDIR)ssh1connection.obj \ + $(BUILDDIR)ssh1connection-client.obj \ + $(BUILDDIR)ssh1login.obj $(BUILDDIR)ssh2bpp.obj \ + $(BUILDDIR)ssh2bpp-bare.obj $(BUILDDIR)ssh2censor.obj \ + $(BUILDDIR)ssh2connection.obj \ + $(BUILDDIR)ssh2connection-client.obj \ + $(BUILDDIR)ssh2kex-client.obj $(BUILDDIR)ssh2transhk.obj \ + $(BUILDDIR)ssh2transport.obj $(BUILDDIR)ssh2userauth.obj \ + $(BUILDDIR)sshaes.obj $(BUILDDIR)ssharcf.obj \ + $(BUILDDIR)sshauxcrypt.obj $(BUILDDIR)sshblowf.obj \ + $(BUILDDIR)sshccp.obj $(BUILDDIR)sshcommon.obj \ + $(BUILDDIR)sshcrc.obj $(BUILDDIR)sshcrcda.obj \ + $(BUILDDIR)sshdes.obj $(BUILDDIR)sshdh.obj \ + $(BUILDDIR)sshdss.obj $(BUILDDIR)sshecc.obj \ + $(BUILDDIR)sshgssc.obj $(BUILDDIR)sshhmac.obj \ + $(BUILDDIR)sshmac.obj $(BUILDDIR)sshmd5.obj \ + $(BUILDDIR)sshprng.obj $(BUILDDIR)sshpubk.obj \ + $(BUILDDIR)sshrand.obj $(BUILDDIR)sshrsa.obj \ + $(BUILDDIR)sshsh256.obj $(BUILDDIR)sshsh512.obj \ + $(BUILDDIR)sshsha.obj $(BUILDDIR)sshshare.obj \ + $(BUILDDIR)sshverstring.obj $(BUILDDIR)sshzlib.obj \ + $(BUILDDIR)stripctrl.obj $(BUILDDIR)timing.obj \ + $(BUILDDIR)tree234.obj $(BUILDDIR)utils.obj \ + $(BUILDDIR)version.obj $(BUILDDIR)wcwidth.obj \ + $(BUILDDIR)wildcard.obj $(BUILDDIR)wincapi.obj \ + $(BUILDDIR)wincons.obj $(BUILDDIR)windefs.obj \ + $(BUILDDIR)wingss.obj $(BUILDDIR)winhandl.obj \ + $(BUILDDIR)winhsock.obj $(BUILDDIR)winmisc.obj \ + $(BUILDDIR)winmiscs.obj $(BUILDDIR)winnet.obj \ + $(BUILDDIR)winnohlp.obj $(BUILDDIR)winnoise.obj \ + $(BUILDDIR)winnojmp.obj $(BUILDDIR)winnpc.obj \ + $(BUILDDIR)winnps.obj $(BUILDDIR)winpgntc.obj \ + $(BUILDDIR)winproxy.obj $(BUILDDIR)winsecur.obj \ + $(BUILDDIR)winsftp.obj $(BUILDDIR)winshare.obj \ + $(BUILDDIR)winstore.obj $(BUILDDIR)wintime.obj \ + $(BUILDDIR)winucs.obj $(BUILDDIR)x11fwd.obj + $(LD) $(LFLAGS) $(XLFLAGS) /out:$(BUILDDIR)psftp.exe \ + /lldmap:$(BUILDDIR)psftp.map /subsystem:console$(SUBSYSVER) \ + $(EXTRA_console) advapi32.lib $(BUILDDIR)agentf.obj \ + $(BUILDDIR)aqsync.obj $(BUILDDIR)be_misc.obj \ + $(BUILDDIR)be_ssh.obj $(BUILDDIR)callback.obj \ + $(BUILDDIR)cmdline.obj comdlg32.lib $(BUILDDIR)conf.obj \ + $(BUILDDIR)cproxy.obj $(BUILDDIR)ecc.obj \ + $(BUILDDIR)errsock.obj gdi32.lib imm32.lib \ + $(BUILDDIR)logging.obj $(BUILDDIR)mainchan.obj \ + $(BUILDDIR)marshal.obj $(BUILDDIR)memory.obj \ + $(BUILDDIR)misc.obj $(BUILDDIR)miscucs.obj \ + $(BUILDDIR)mpint.obj $(BUILDDIR)nullplug.obj ole32.lib \ + $(BUILDDIR)pgssapi.obj $(BUILDDIR)pinger.obj \ + $(BUILDDIR)portfwd.obj $(BUILDDIR)proxy.obj \ + $(BUILDDIR)psftp.obj $(BUILDDIR)psftp.res \ + $(BUILDDIR)psftpcommon.obj $(BUILDDIR)settings.obj \ + $(BUILDDIR)sftp.obj $(BUILDDIR)sftpcommon.obj shell32.lib \ + $(BUILDDIR)ssh.obj $(BUILDDIR)ssh1bpp.obj \ + $(BUILDDIR)ssh1censor.obj $(BUILDDIR)ssh1connection.obj \ + $(BUILDDIR)ssh1connection-client.obj \ + $(BUILDDIR)ssh1login.obj $(BUILDDIR)ssh2bpp.obj \ + $(BUILDDIR)ssh2bpp-bare.obj $(BUILDDIR)ssh2censor.obj \ + $(BUILDDIR)ssh2connection.obj \ + $(BUILDDIR)ssh2connection-client.obj \ + $(BUILDDIR)ssh2kex-client.obj $(BUILDDIR)ssh2transhk.obj \ + $(BUILDDIR)ssh2transport.obj $(BUILDDIR)ssh2userauth.obj \ + $(BUILDDIR)sshaes.obj $(BUILDDIR)ssharcf.obj \ + $(BUILDDIR)sshauxcrypt.obj $(BUILDDIR)sshblowf.obj \ + $(BUILDDIR)sshccp.obj $(BUILDDIR)sshcommon.obj \ + $(BUILDDIR)sshcrc.obj $(BUILDDIR)sshcrcda.obj \ + $(BUILDDIR)sshdes.obj $(BUILDDIR)sshdh.obj \ + $(BUILDDIR)sshdss.obj $(BUILDDIR)sshecc.obj \ + $(BUILDDIR)sshgssc.obj $(BUILDDIR)sshhmac.obj \ + $(BUILDDIR)sshmac.obj $(BUILDDIR)sshmd5.obj \ + $(BUILDDIR)sshprng.obj $(BUILDDIR)sshpubk.obj \ + $(BUILDDIR)sshrand.obj $(BUILDDIR)sshrsa.obj \ + $(BUILDDIR)sshsh256.obj $(BUILDDIR)sshsh512.obj \ + $(BUILDDIR)sshsha.obj $(BUILDDIR)sshshare.obj \ + $(BUILDDIR)sshverstring.obj $(BUILDDIR)sshzlib.obj \ + $(BUILDDIR)stripctrl.obj $(BUILDDIR)timing.obj \ + $(BUILDDIR)tree234.obj user32.lib $(BUILDDIR)utils.obj \ + $(BUILDDIR)version.obj $(BUILDDIR)wcwidth.obj \ + $(BUILDDIR)wildcard.obj $(BUILDDIR)wincapi.obj \ + $(BUILDDIR)wincons.obj $(BUILDDIR)windefs.obj \ + $(BUILDDIR)wingss.obj $(BUILDDIR)winhandl.obj \ + $(BUILDDIR)winhsock.obj $(BUILDDIR)winmisc.obj \ + $(BUILDDIR)winmiscs.obj $(BUILDDIR)winnet.obj \ + $(BUILDDIR)winnohlp.obj $(BUILDDIR)winnoise.obj \ + $(BUILDDIR)winnojmp.obj $(BUILDDIR)winnpc.obj \ + $(BUILDDIR)winnps.obj $(BUILDDIR)winpgntc.obj \ + $(BUILDDIR)winproxy.obj $(BUILDDIR)winsecur.obj \ + $(BUILDDIR)winsftp.obj $(BUILDDIR)winshare.obj \ + $(BUILDDIR)winstore.obj $(BUILDDIR)wintime.obj \ + $(BUILDDIR)winucs.obj $(BUILDDIR)x11fwd.obj $(EXTRA_libs) + +$(BUILDDIR)putty.exe: $(BUILDDIR)agentf.obj $(BUILDDIR)aqsync.obj \ + $(BUILDDIR)be_all_s.obj $(BUILDDIR)be_misc.obj \ + $(BUILDDIR)callback.obj $(BUILDDIR)cmdline.obj \ + $(BUILDDIR)conf.obj $(BUILDDIR)config.obj \ + $(BUILDDIR)cproxy.obj $(BUILDDIR)dialog.obj \ + $(BUILDDIR)ecc.obj $(BUILDDIR)errsock.obj \ + $(BUILDDIR)ldisc.obj $(BUILDDIR)logging.obj \ + $(BUILDDIR)mainchan.obj $(BUILDDIR)marshal.obj \ + $(BUILDDIR)memory.obj $(BUILDDIR)minibidi.obj \ + $(BUILDDIR)misc.obj $(BUILDDIR)miscucs.obj \ + $(BUILDDIR)mpint.obj $(BUILDDIR)nullplug.obj \ + $(BUILDDIR)pgssapi.obj $(BUILDDIR)pinger.obj \ + $(BUILDDIR)portfwd.obj $(BUILDDIR)proxy.obj \ + $(BUILDDIR)putty.res $(BUILDDIR)raw.obj \ + $(BUILDDIR)rlogin.obj $(BUILDDIR)sercfg.obj \ + $(BUILDDIR)sessprep.obj $(BUILDDIR)settings.obj \ + $(BUILDDIR)sizetip.obj $(BUILDDIR)ssh.obj \ + $(BUILDDIR)ssh1bpp.obj $(BUILDDIR)ssh1censor.obj \ + $(BUILDDIR)ssh1connection.obj \ + $(BUILDDIR)ssh1connection-client.obj \ + $(BUILDDIR)ssh1login.obj $(BUILDDIR)ssh2bpp.obj \ + $(BUILDDIR)ssh2bpp-bare.obj $(BUILDDIR)ssh2censor.obj \ + $(BUILDDIR)ssh2connection.obj \ + $(BUILDDIR)ssh2connection-client.obj \ + $(BUILDDIR)ssh2kex-client.obj $(BUILDDIR)ssh2transhk.obj \ + $(BUILDDIR)ssh2transport.obj $(BUILDDIR)ssh2userauth.obj \ + $(BUILDDIR)sshaes.obj $(BUILDDIR)ssharcf.obj \ + $(BUILDDIR)sshauxcrypt.obj $(BUILDDIR)sshblowf.obj \ + $(BUILDDIR)sshccp.obj $(BUILDDIR)sshcommon.obj \ + $(BUILDDIR)sshcrc.obj $(BUILDDIR)sshcrcda.obj \ + $(BUILDDIR)sshdes.obj $(BUILDDIR)sshdh.obj \ + $(BUILDDIR)sshdss.obj $(BUILDDIR)sshecc.obj \ + $(BUILDDIR)sshgssc.obj $(BUILDDIR)sshhmac.obj \ + $(BUILDDIR)sshmac.obj $(BUILDDIR)sshmd5.obj \ + $(BUILDDIR)sshprng.obj $(BUILDDIR)sshpubk.obj \ + $(BUILDDIR)sshrand.obj $(BUILDDIR)sshrsa.obj \ + $(BUILDDIR)sshsh256.obj $(BUILDDIR)sshsh512.obj \ + $(BUILDDIR)sshsha.obj $(BUILDDIR)sshshare.obj \ + $(BUILDDIR)sshverstring.obj $(BUILDDIR)sshzlib.obj \ + $(BUILDDIR)stripctrl.obj $(BUILDDIR)telnet.obj \ + $(BUILDDIR)terminal.obj $(BUILDDIR)timing.obj \ + $(BUILDDIR)tree234.obj $(BUILDDIR)utils.obj \ + $(BUILDDIR)version.obj $(BUILDDIR)wcwidth.obj \ + $(BUILDDIR)wildcard.obj $(BUILDDIR)wincapi.obj \ + $(BUILDDIR)wincfg.obj $(BUILDDIR)winctrls.obj \ + $(BUILDDIR)windefs.obj $(BUILDDIR)windlg.obj \ + $(BUILDDIR)window.obj $(BUILDDIR)wingss.obj \ + $(BUILDDIR)winhandl.obj $(BUILDDIR)winhelp.obj \ + $(BUILDDIR)winhsock.obj $(BUILDDIR)winjump.obj \ + $(BUILDDIR)winmisc.obj $(BUILDDIR)winmiscs.obj \ + $(BUILDDIR)winnet.obj $(BUILDDIR)winnoise.obj \ + $(BUILDDIR)winnpc.obj $(BUILDDIR)winnps.obj \ + $(BUILDDIR)winpgntc.obj $(BUILDDIR)winprint.obj \ + $(BUILDDIR)winproxy.obj $(BUILDDIR)winsecur.obj \ + $(BUILDDIR)winser.obj $(BUILDDIR)winshare.obj \ + $(BUILDDIR)winstore.obj $(BUILDDIR)wintime.obj \ + $(BUILDDIR)winucs.obj $(BUILDDIR)winutils.obj \ + $(BUILDDIR)winx11.obj $(BUILDDIR)x11fwd.obj + $(LD) $(LFLAGS) $(XLFLAGS) /out:$(BUILDDIR)putty.exe \ + /lldmap:$(BUILDDIR)putty.map /subsystem:windows$(SUBSYSVER) \ + $(EXTRA_windows) advapi32.lib $(BUILDDIR)agentf.obj \ + $(BUILDDIR)aqsync.obj $(BUILDDIR)be_all_s.obj \ + $(BUILDDIR)be_misc.obj $(BUILDDIR)callback.obj \ + $(BUILDDIR)cmdline.obj comdlg32.lib $(BUILDDIR)conf.obj \ + $(BUILDDIR)config.obj $(BUILDDIR)cproxy.obj \ + $(BUILDDIR)dialog.obj $(BUILDDIR)ecc.obj \ + $(BUILDDIR)errsock.obj gdi32.lib imm32.lib \ + $(BUILDDIR)ldisc.obj $(BUILDDIR)logging.obj \ + $(BUILDDIR)mainchan.obj $(BUILDDIR)marshal.obj \ + $(BUILDDIR)memory.obj $(BUILDDIR)minibidi.obj \ + $(BUILDDIR)misc.obj $(BUILDDIR)miscucs.obj \ + $(BUILDDIR)mpint.obj $(BUILDDIR)nullplug.obj ole32.lib \ + $(BUILDDIR)pgssapi.obj $(BUILDDIR)pinger.obj \ + $(BUILDDIR)portfwd.obj $(BUILDDIR)proxy.obj \ + $(BUILDDIR)putty.res $(BUILDDIR)raw.obj \ + $(BUILDDIR)rlogin.obj $(BUILDDIR)sercfg.obj \ + $(BUILDDIR)sessprep.obj $(BUILDDIR)settings.obj shell32.lib \ + $(BUILDDIR)sizetip.obj $(BUILDDIR)ssh.obj \ + $(BUILDDIR)ssh1bpp.obj $(BUILDDIR)ssh1censor.obj \ + $(BUILDDIR)ssh1connection.obj \ + $(BUILDDIR)ssh1connection-client.obj \ + $(BUILDDIR)ssh1login.obj $(BUILDDIR)ssh2bpp.obj \ + $(BUILDDIR)ssh2bpp-bare.obj $(BUILDDIR)ssh2censor.obj \ + $(BUILDDIR)ssh2connection.obj \ + $(BUILDDIR)ssh2connection-client.obj \ + $(BUILDDIR)ssh2kex-client.obj $(BUILDDIR)ssh2transhk.obj \ + $(BUILDDIR)ssh2transport.obj $(BUILDDIR)ssh2userauth.obj \ + $(BUILDDIR)sshaes.obj $(BUILDDIR)ssharcf.obj \ + $(BUILDDIR)sshauxcrypt.obj $(BUILDDIR)sshblowf.obj \ + $(BUILDDIR)sshccp.obj $(BUILDDIR)sshcommon.obj \ + $(BUILDDIR)sshcrc.obj $(BUILDDIR)sshcrcda.obj \ + $(BUILDDIR)sshdes.obj $(BUILDDIR)sshdh.obj \ + $(BUILDDIR)sshdss.obj $(BUILDDIR)sshecc.obj \ + $(BUILDDIR)sshgssc.obj $(BUILDDIR)sshhmac.obj \ + $(BUILDDIR)sshmac.obj $(BUILDDIR)sshmd5.obj \ + $(BUILDDIR)sshprng.obj $(BUILDDIR)sshpubk.obj \ + $(BUILDDIR)sshrand.obj $(BUILDDIR)sshrsa.obj \ + $(BUILDDIR)sshsh256.obj $(BUILDDIR)sshsh512.obj \ + $(BUILDDIR)sshsha.obj $(BUILDDIR)sshshare.obj \ + $(BUILDDIR)sshverstring.obj $(BUILDDIR)sshzlib.obj \ + $(BUILDDIR)stripctrl.obj $(BUILDDIR)telnet.obj \ + $(BUILDDIR)terminal.obj $(BUILDDIR)timing.obj \ + $(BUILDDIR)tree234.obj user32.lib $(BUILDDIR)utils.obj \ + $(BUILDDIR)version.obj $(BUILDDIR)wcwidth.obj \ + $(BUILDDIR)wildcard.obj $(BUILDDIR)wincapi.obj \ + $(BUILDDIR)wincfg.obj $(BUILDDIR)winctrls.obj \ + $(BUILDDIR)windefs.obj $(BUILDDIR)windlg.obj \ + $(BUILDDIR)window.obj $(BUILDDIR)wingss.obj \ + $(BUILDDIR)winhandl.obj $(BUILDDIR)winhelp.obj \ + $(BUILDDIR)winhsock.obj $(BUILDDIR)winjump.obj \ + $(BUILDDIR)winmisc.obj $(BUILDDIR)winmiscs.obj \ + $(BUILDDIR)winnet.obj $(BUILDDIR)winnoise.obj \ + $(BUILDDIR)winnpc.obj $(BUILDDIR)winnps.obj \ + $(BUILDDIR)winpgntc.obj $(BUILDDIR)winprint.obj \ + $(BUILDDIR)winproxy.obj $(BUILDDIR)winsecur.obj \ + $(BUILDDIR)winser.obj $(BUILDDIR)winshare.obj \ + $(BUILDDIR)winstore.obj $(BUILDDIR)wintime.obj \ + $(BUILDDIR)winucs.obj $(BUILDDIR)winutils.obj \ + $(BUILDDIR)winx11.obj $(BUILDDIR)x11fwd.obj $(EXTRA_libs) + +$(BUILDDIR)puttygen.exe: $(BUILDDIR)conf.obj $(BUILDDIR)ecc.obj \ + $(BUILDDIR)import.obj $(BUILDDIR)marshal.obj \ + $(BUILDDIR)memory.obj $(BUILDDIR)misc.obj \ + $(BUILDDIR)mpint.obj $(BUILDDIR)notiming.obj \ + $(BUILDDIR)puttygen.res $(BUILDDIR)sshaes.obj \ + $(BUILDDIR)sshauxcrypt.obj $(BUILDDIR)sshbcrypt.obj \ + $(BUILDDIR)sshblowf.obj $(BUILDDIR)sshdes.obj \ + $(BUILDDIR)sshdss.obj $(BUILDDIR)sshdssg.obj \ + $(BUILDDIR)sshecc.obj $(BUILDDIR)sshecdsag.obj \ + $(BUILDDIR)sshhmac.obj $(BUILDDIR)sshmd5.obj \ + $(BUILDDIR)sshprime.obj $(BUILDDIR)sshprng.obj \ + $(BUILDDIR)sshpubk.obj $(BUILDDIR)sshrand.obj \ + $(BUILDDIR)sshrsa.obj $(BUILDDIR)sshrsag.obj \ + $(BUILDDIR)sshsh256.obj $(BUILDDIR)sshsh512.obj \ + $(BUILDDIR)sshsha.obj $(BUILDDIR)stripctrl.obj \ + $(BUILDDIR)tree234.obj $(BUILDDIR)utils.obj \ + $(BUILDDIR)version.obj $(BUILDDIR)wcwidth.obj \ + $(BUILDDIR)winctrls.obj $(BUILDDIR)winhelp.obj \ + $(BUILDDIR)winmisc.obj $(BUILDDIR)winmiscs.obj \ + $(BUILDDIR)winnoise.obj $(BUILDDIR)winnojmp.obj \ + $(BUILDDIR)winpgen.obj $(BUILDDIR)winsecur.obj \ + $(BUILDDIR)winstore.obj $(BUILDDIR)wintime.obj \ + $(BUILDDIR)winutils.obj + $(LD) $(LFLAGS) $(XLFLAGS) /out:$(BUILDDIR)puttygen.exe \ + /lldmap:$(BUILDDIR)puttygen.map \ + /subsystem:windows$(SUBSYSVER) $(EXTRA_windows) advapi32.lib \ + comdlg32.lib $(BUILDDIR)conf.obj $(BUILDDIR)ecc.obj \ + gdi32.lib imm32.lib $(BUILDDIR)import.obj \ + $(BUILDDIR)marshal.obj $(BUILDDIR)memory.obj \ + $(BUILDDIR)misc.obj $(BUILDDIR)mpint.obj \ + $(BUILDDIR)notiming.obj ole32.lib $(BUILDDIR)puttygen.res \ + shell32.lib $(BUILDDIR)sshaes.obj $(BUILDDIR)sshauxcrypt.obj \ + $(BUILDDIR)sshbcrypt.obj $(BUILDDIR)sshblowf.obj \ + $(BUILDDIR)sshdes.obj $(BUILDDIR)sshdss.obj \ + $(BUILDDIR)sshdssg.obj $(BUILDDIR)sshecc.obj \ + $(BUILDDIR)sshecdsag.obj $(BUILDDIR)sshhmac.obj \ + $(BUILDDIR)sshmd5.obj $(BUILDDIR)sshprime.obj \ + $(BUILDDIR)sshprng.obj $(BUILDDIR)sshpubk.obj \ + $(BUILDDIR)sshrand.obj $(BUILDDIR)sshrsa.obj \ + $(BUILDDIR)sshrsag.obj $(BUILDDIR)sshsh256.obj \ + $(BUILDDIR)sshsh512.obj $(BUILDDIR)sshsha.obj \ + $(BUILDDIR)stripctrl.obj $(BUILDDIR)tree234.obj user32.lib \ + $(BUILDDIR)utils.obj $(BUILDDIR)version.obj \ + $(BUILDDIR)wcwidth.obj $(BUILDDIR)winctrls.obj \ + $(BUILDDIR)winhelp.obj $(BUILDDIR)winmisc.obj \ + $(BUILDDIR)winmiscs.obj $(BUILDDIR)winnoise.obj \ + $(BUILDDIR)winnojmp.obj $(BUILDDIR)winpgen.obj \ + $(BUILDDIR)winsecur.obj $(BUILDDIR)winstore.obj \ + $(BUILDDIR)wintime.obj $(BUILDDIR)winutils.obj $(EXTRA_libs) + +$(BUILDDIR)puttytel.exe: $(BUILDDIR)be_misc.obj $(BUILDDIR)be_nos_s.obj \ + $(BUILDDIR)callback.obj $(BUILDDIR)cmdline.obj \ + $(BUILDDIR)conf.obj $(BUILDDIR)config.obj \ + $(BUILDDIR)dialog.obj $(BUILDDIR)errsock.obj \ + $(BUILDDIR)ldisc.obj $(BUILDDIR)logging.obj \ + $(BUILDDIR)marshal.obj $(BUILDDIR)memory.obj \ + $(BUILDDIR)minibidi.obj $(BUILDDIR)misc.obj \ + $(BUILDDIR)miscucs.obj $(BUILDDIR)nocproxy.obj \ + $(BUILDDIR)nogss.obj $(BUILDDIR)pinger.obj \ + $(BUILDDIR)proxy.obj $(BUILDDIR)puttytel.res \ + $(BUILDDIR)raw.obj $(BUILDDIR)rlogin.obj \ + $(BUILDDIR)sercfg.obj $(BUILDDIR)sessprep.obj \ + $(BUILDDIR)settings.obj $(BUILDDIR)sizetip.obj \ + $(BUILDDIR)stripctrl.obj $(BUILDDIR)telnet.obj \ + $(BUILDDIR)terminal.obj $(BUILDDIR)timing.obj \ + $(BUILDDIR)tree234.obj $(BUILDDIR)utils.obj \ + $(BUILDDIR)version.obj $(BUILDDIR)wcwidth.obj \ + $(BUILDDIR)wincfg.obj $(BUILDDIR)winctrls.obj \ + $(BUILDDIR)windefs.obj $(BUILDDIR)windlg.obj \ + $(BUILDDIR)window.obj $(BUILDDIR)winhandl.obj \ + $(BUILDDIR)winhelp.obj $(BUILDDIR)winhsock.obj \ + $(BUILDDIR)winjump.obj $(BUILDDIR)winmisc.obj \ + $(BUILDDIR)winmiscs.obj $(BUILDDIR)winnet.obj \ + $(BUILDDIR)winprint.obj $(BUILDDIR)winproxy.obj \ + $(BUILDDIR)winsecur.obj $(BUILDDIR)winser.obj \ + $(BUILDDIR)winstore.obj $(BUILDDIR)wintime.obj \ + $(BUILDDIR)winucs.obj $(BUILDDIR)winutils.obj + $(LD) $(LFLAGS) $(XLFLAGS) /out:$(BUILDDIR)puttytel.exe \ + /lldmap:$(BUILDDIR)puttytel.map \ + /subsystem:windows$(SUBSYSVER) $(EXTRA_windows) advapi32.lib \ + $(BUILDDIR)be_misc.obj $(BUILDDIR)be_nos_s.obj \ + $(BUILDDIR)callback.obj $(BUILDDIR)cmdline.obj comdlg32.lib \ + $(BUILDDIR)conf.obj $(BUILDDIR)config.obj \ + $(BUILDDIR)dialog.obj $(BUILDDIR)errsock.obj gdi32.lib \ + imm32.lib $(BUILDDIR)ldisc.obj $(BUILDDIR)logging.obj \ + $(BUILDDIR)marshal.obj $(BUILDDIR)memory.obj \ + $(BUILDDIR)minibidi.obj $(BUILDDIR)misc.obj \ + $(BUILDDIR)miscucs.obj $(BUILDDIR)nocproxy.obj \ + $(BUILDDIR)nogss.obj ole32.lib $(BUILDDIR)pinger.obj \ + $(BUILDDIR)proxy.obj $(BUILDDIR)puttytel.res \ + $(BUILDDIR)raw.obj $(BUILDDIR)rlogin.obj \ + $(BUILDDIR)sercfg.obj $(BUILDDIR)sessprep.obj \ + $(BUILDDIR)settings.obj shell32.lib $(BUILDDIR)sizetip.obj \ + $(BUILDDIR)stripctrl.obj $(BUILDDIR)telnet.obj \ + $(BUILDDIR)terminal.obj $(BUILDDIR)timing.obj \ + $(BUILDDIR)tree234.obj user32.lib $(BUILDDIR)utils.obj \ + $(BUILDDIR)version.obj $(BUILDDIR)wcwidth.obj \ + $(BUILDDIR)wincfg.obj $(BUILDDIR)winctrls.obj \ + $(BUILDDIR)windefs.obj $(BUILDDIR)windlg.obj \ + $(BUILDDIR)window.obj $(BUILDDIR)winhandl.obj \ + $(BUILDDIR)winhelp.obj $(BUILDDIR)winhsock.obj \ + $(BUILDDIR)winjump.obj $(BUILDDIR)winmisc.obj \ + $(BUILDDIR)winmiscs.obj $(BUILDDIR)winnet.obj \ + $(BUILDDIR)winprint.obj $(BUILDDIR)winproxy.obj \ + $(BUILDDIR)winsecur.obj $(BUILDDIR)winser.obj \ + $(BUILDDIR)winstore.obj $(BUILDDIR)wintime.obj \ + $(BUILDDIR)winucs.obj $(BUILDDIR)winutils.obj $(EXTRA_libs) + +$(BUILDDIR)testcrypt.exe: $(BUILDDIR)ecc.obj $(BUILDDIR)marshal.obj \ + $(BUILDDIR)memory.obj $(BUILDDIR)mpint.obj \ + $(BUILDDIR)sshaes.obj $(BUILDDIR)ssharcf.obj \ + $(BUILDDIR)sshauxcrypt.obj $(BUILDDIR)sshblowf.obj \ + $(BUILDDIR)sshccp.obj $(BUILDDIR)sshcrc.obj \ + $(BUILDDIR)sshcrcda.obj $(BUILDDIR)sshdes.obj \ + $(BUILDDIR)sshdh.obj $(BUILDDIR)sshdss.obj \ + $(BUILDDIR)sshecc.obj $(BUILDDIR)sshhmac.obj \ + $(BUILDDIR)sshmd5.obj $(BUILDDIR)sshprime.obj \ + $(BUILDDIR)sshprng.obj $(BUILDDIR)sshrsa.obj \ + $(BUILDDIR)sshsh256.obj $(BUILDDIR)sshsh512.obj \ + $(BUILDDIR)sshsha.obj $(BUILDDIR)testcrypt.obj \ + $(BUILDDIR)tree234.obj $(BUILDDIR)utils.obj \ + $(BUILDDIR)winmiscs.obj + $(LD) $(LFLAGS) $(XLFLAGS) /out:$(BUILDDIR)testcrypt.exe \ + /lldmap:$(BUILDDIR)testcrypt.map \ + /subsystem:console$(SUBSYSVER) $(EXTRA_console) \ + $(BUILDDIR)ecc.obj $(BUILDDIR)marshal.obj \ + $(BUILDDIR)memory.obj $(BUILDDIR)mpint.obj \ + $(BUILDDIR)sshaes.obj $(BUILDDIR)ssharcf.obj \ + $(BUILDDIR)sshauxcrypt.obj $(BUILDDIR)sshblowf.obj \ + $(BUILDDIR)sshccp.obj $(BUILDDIR)sshcrc.obj \ + $(BUILDDIR)sshcrcda.obj $(BUILDDIR)sshdes.obj \ + $(BUILDDIR)sshdh.obj $(BUILDDIR)sshdss.obj \ + $(BUILDDIR)sshecc.obj $(BUILDDIR)sshhmac.obj \ + $(BUILDDIR)sshmd5.obj $(BUILDDIR)sshprime.obj \ + $(BUILDDIR)sshprng.obj $(BUILDDIR)sshrsa.obj \ + $(BUILDDIR)sshsh256.obj $(BUILDDIR)sshsh512.obj \ + $(BUILDDIR)sshsha.obj $(BUILDDIR)testcrypt.obj \ + $(BUILDDIR)tree234.obj $(BUILDDIR)utils.obj \ + $(BUILDDIR)winmiscs.obj $(EXTRA_libs) + +$(BUILDDIR)agentf.obj: ../agentf.c ../putty.h ../ssh.h ../pageant.h \ + ../sshchan.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)aqsync.obj: ../aqsync.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)be_all_s.obj: ../be_all_s.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)be_misc.obj: ../be_misc.c ../putty.h ../network.h ../defs.h \ + ../puttyps.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)be_none.obj: ../be_none.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)be_nos_s.obj: ../be_nos_s.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)be_ssh.obj: ../be_ssh.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)callback.obj: ../callback.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)cgtest.obj: ../cgtest.c ../cmdgen.c ../putty.h ../ssh.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)cmdgen.obj: ../cmdgen.c ../putty.h ../ssh.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)cmdline.obj: ../cmdline.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)conf.obj: ../conf.c ../tree234.h ../putty.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)config.obj: ../config.c ../putty.h ../dialog.h ../storage.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)cproxy.obj: ../cproxy.c ../putty.h ../ssh.h ../network.h \ + ../proxy.h ../marshal.h ../defs.h ../puttyps.h ../misc.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)dialog.obj: ../dialog.c ../putty.h ../dialog.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ecc.obj: ../ecc.c ../ssh.h ../mpint.h ../ecc.h ../puttymem.h \ + ../tree234.h ../network.h ../misc.h ../sshttymodes.h \ + ../defs.h ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)errsock.obj: ../errsock.c ../tree234.h ../putty.h ../network.h \ + ../defs.h ../puttyps.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)fromucs.obj: ../charset/fromucs.c ../charset/charset.h \ + ../charset/internal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)fuzzterm.obj: ../fuzzterm.c ../putty.h ../terminal.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../tree234.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)gtkapp.obj: ../unix/gtkapp.c ../putty.h ../unix/gtkmisc.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)gtkask.obj: ../unix/gtkask.c ../defs.h ../unix/gtkfont.h \ + ../unix/gtkcompat.h ../unix/gtkmisc.h ../putty.h ../ssh.h \ + ../misc.h ../puttyps.h ../network.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)gtkcfg.obj: ../unix/gtkcfg.c ../putty.h ../dialog.h ../storage.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)gtkcols.obj: ../unix/gtkcols.c ../defs.h ../unix/gtkcompat.h \ + ../unix/gtkcols.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)gtkcomm.obj: ../unix/gtkcomm.c ../putty.h ../terminal.h \ + ../unix/gtkcompat.h ../unix/gtkfont.h ../unix/gtkmisc.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../tree234.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)gtkdlg.obj: ../unix/gtkdlg.c ../putty.h ../unix/gtkcompat.h \ + ../unix/gtkcols.h ../unix/gtkfont.h ../unix/gtkmisc.h \ + ../unix/x11misc.h ../storage.h ../dialog.h ../tree234.h \ + ../licence.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)gtkfont.obj: ../unix/gtkfont.c ../putty.h ../unix/gtkfont.h \ + ../unix/gtkcompat.h ../unix/gtkmisc.h ../tree234.h \ + ../unix/x11misc.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)gtkmain.obj: ../unix/gtkmain.c ../putty.h ../terminal.h \ + ../unix/gtkcompat.h ../unix/gtkfont.h ../unix/gtkmisc.h \ + ../unix/x11misc.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../tree234.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)gtkmisc.obj: ../unix/gtkmisc.c ../putty.h ../unix/gtkcompat.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)gtkwin.obj: ../unix/gtkwin.c ../putty.h ../terminal.h \ + ../unix/gtkcompat.h ../unix/gtkfont.h ../unix/gtkmisc.h \ + ../unix/x11misc.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../tree234.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)import.obj: ../import.c ../putty.h ../ssh.h ../mpint.h ../misc.h \ + ../defs.h ../puttyps.h ../network.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ldisc.obj: ../ldisc.c ../putty.h ../terminal.h ../ldisc.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../tree234.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)localenc.obj: ../charset/localenc.c ../charset/charset.h \ + ../charset/internal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)logging.obj: ../logging.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)macenc.obj: ../charset/macenc.c ../charset/charset.h \ + ../charset/internal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)mainchan.obj: ../mainchan.c ../putty.h ../ssh.h ../sshppl.h \ + ../sshchan.h ../sshsignals.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)marshal.obj: ../marshal.c ../marshal.h ../misc.h ../defs.h \ + ../puttymem.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)memory.obj: ../memory.c ../defs.h ../puttymem.h ../misc.h \ + ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)mimeenc.obj: ../charset/mimeenc.c ../charset/charset.h \ + ../charset/internal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)minibidi.obj: ../minibidi.c ../putty.h ../misc.h ../defs.h \ + ../puttyps.h ../network.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../windows/winstuff.h ../unix/unix.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)misc.obj: ../misc.c ../defs.h ../putty.h ../misc.h ../puttyps.h \ + ../network.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../windows/winstuff.h ../unix/unix.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)miscucs.obj: ../miscucs.c ../putty.h ../misc.h ../defs.h \ + ../puttyps.h ../network.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../windows/winstuff.h ../unix/unix.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)mpint.obj: ../mpint.c ../defs.h ../misc.h ../puttymem.h \ + ../mpint.h ../mpint_i.h ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)nocmdline.obj: ../nocmdline.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)nocproxy.obj: ../nocproxy.c ../putty.h ../network.h ../proxy.h \ + ../defs.h ../puttyps.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)nogss.obj: ../nogss.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)noterm.obj: ../noterm.c ../putty.h ../terminal.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../tree234.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)notiming.obj: ../notiming.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)nullplug.obj: ../nullplug.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)osxlaunch.obj: ../unix/osxlaunch.c + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)pageant.obj: ../pageant.c ../putty.h ../mpint.h ../ssh.h \ + ../sshcr.h ../pageant.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)pageant.res: $(BUILDDIR)pageant.rcpp ../windows/rcstuff.h \ + ../windows/pageant.ico ../windows/pageants.ico \ + ../windows/pageant.mft ../windows/win_res.h ../version.h \ + ../licence.h + $(RC) $(BUILDDIR)pageant.rcpp /FO $(BUILDDIR)pageant.res + +$(BUILDDIR)pgssapi.obj: ../pgssapi.c ../putty.h ../pgssapi.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)pinger.obj: ../pinger.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)plink.res: $(BUILDDIR)plink.rcpp ../windows/rcstuff.h \ + ../windows/putty.ico ../version.h ../licence.h + $(RC) $(BUILDDIR)plink.rcpp /FO $(BUILDDIR)plink.res + +$(BUILDDIR)portfwd.obj: ../portfwd.c ../putty.h ../ssh.h ../sshchan.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)procnet.obj: ../unix/procnet.c ../misc.h ../defs.h ../puttymem.h \ + ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)proxy.obj: ../proxy.c ../putty.h ../network.h ../proxy.h \ + ../defs.h ../puttyps.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)pscp.obj: ../pscp.c ../putty.h ../psftp.h ../ssh.h ../sftp.h \ + ../storage.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)pscp.res: $(BUILDDIR)pscp.rcpp ../windows/rcstuff.h \ + ../windows/pscp.ico ../version.h ../licence.h + $(RC) $(BUILDDIR)pscp.rcpp /FO $(BUILDDIR)pscp.res + +$(BUILDDIR)psftp.obj: ../psftp.c ../putty.h ../psftp.h ../storage.h ../ssh.h \ + ../sftp.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)psftp.res: $(BUILDDIR)psftp.rcpp ../windows/rcstuff.h \ + ../windows/pscp.ico ../version.h ../licence.h + $(RC) $(BUILDDIR)psftp.rcpp /FO $(BUILDDIR)psftp.res + +$(BUILDDIR)psftpcommon.obj: ../psftpcommon.c ../putty.h ../sftp.h ../psftp.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)putty.res: $(BUILDDIR)putty.rcpp ../windows/rcstuff.h \ + ../windows/putty.mft ../windows/win_res.h \ + ../windows/putty.ico ../windows/puttycfg.ico ../version.h \ + ../licence.h + $(RC) $(BUILDDIR)putty.rcpp /FO $(BUILDDIR)putty.res + +$(BUILDDIR)puttygen.res: $(BUILDDIR)puttygen.rcpp ../windows/rcstuff.h \ + ../windows/puttygen.ico ../windows/puttygen.mft \ + ../windows/win_res.h ../version.h ../licence.h + $(RC) $(BUILDDIR)puttygen.rcpp /FO $(BUILDDIR)puttygen.res + +$(BUILDDIR)puttytel.res: $(BUILDDIR)puttytel.rcpp ../windows/rcstuff.h \ + ../windows/puttytel.mft ../windows/win_res.h \ + ../windows/putty.ico ../windows/puttycfg.ico ../version.h \ + ../licence.h + $(RC) $(BUILDDIR)puttytel.rcpp /FO $(BUILDDIR)puttytel.res + +$(BUILDDIR)raw.obj: ../raw.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)rlogin.obj: ../rlogin.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sbcs.obj: ../charset/sbcs.c ../charset/charset.h \ + ../charset/internal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sbcsdat.obj: ../charset/sbcsdat.c ../charset/charset.h \ + ../charset/internal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)scpserver.obj: ../scpserver.c ../putty.h ../ssh.h ../sshcr.h \ + ../sshchan.h ../sftp.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sercfg.obj: ../sercfg.c ../putty.h ../dialog.h ../storage.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sesschan.obj: ../sesschan.c ../putty.h ../ssh.h ../sshchan.h \ + ../sshserver.h ../sftp.h ../sshsignals.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sessprep.obj: ../sessprep.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)settings.obj: ../settings.c ../putty.h ../storage.h ../sshgssc.h \ + ../sshgss.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../pgssapi.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sftp.obj: ../sftp.c ../misc.h ../tree234.h ../sftp.h ../defs.h \ + ../puttymem.h ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sftpcommon.obj: ../sftpcommon.c ../misc.h ../sftp.h ../defs.h \ + ../puttymem.h ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sftpserver.obj: ../sftpserver.c ../putty.h ../ssh.h ../sftp.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sizetip.obj: ../windows/sizetip.c ../putty.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)slookup.obj: ../charset/slookup.c ../charset/charset.h \ + ../charset/internal.h ../charset/enum.c ../charset/sbcsdat.c \ + ../charset/utf8.c + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh.obj: ../ssh.c ../putty.h ../pageant.h ../tree234.h \ + ../storage.h ../marshal.h ../ssh.h ../sshcr.h ../sshbpp.h \ + ../sshppl.h ../sshchan.h ../sshgssc.h ../sshgss.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../sshsignals.h \ + ../puttymem.h ../sshttymodes.h ../pgssapi.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh1bpp.obj: ../ssh1bpp.c ../putty.h ../ssh.h ../sshbpp.h \ + ../sshcr.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh1censor.obj: ../ssh1censor.c ../putty.h ../ssh.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh1connection.obj: ../ssh1connection.c ../putty.h ../ssh.h \ + ../sshbpp.h ../sshppl.h ../sshchan.h ../sshcr.h \ + ../ssh1connection.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh1connection-client.obj: ../ssh1connection-client.c ../putty.h \ + ../ssh.h ../sshbpp.h ../sshppl.h ../sshchan.h ../sshcr.h \ + ../ssh1connection.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh1connection-server.obj: ../ssh1connection-server.c ../putty.h \ + ../ssh.h ../sshbpp.h ../sshppl.h ../sshchan.h ../sshcr.h \ + ../ssh1connection.h ../sshserver.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh1login.obj: ../ssh1login.c ../putty.h ../ssh.h ../mpint.h \ + ../sshbpp.h ../sshppl.h ../sshcr.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh1login-server.obj: ../ssh1login-server.c ../putty.h ../mpint.h \ + ../ssh.h ../sshbpp.h ../sshppl.h ../sshcr.h ../sshserver.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh2bpp.obj: ../ssh2bpp.c ../putty.h ../ssh.h ../sshbpp.h \ + ../sshcr.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh2bpp-bare.obj: ../ssh2bpp-bare.c ../putty.h ../ssh.h \ + ../sshbpp.h ../sshcr.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh2censor.obj: ../ssh2censor.c ../putty.h ../ssh.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh2connection.obj: ../ssh2connection.c ../putty.h ../ssh.h \ + ../sshbpp.h ../sshppl.h ../sshchan.h ../sshcr.h \ + ../ssh2connection.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh2connection-client.obj: ../ssh2connection-client.c ../putty.h \ + ../ssh.h ../sshbpp.h ../sshppl.h ../sshchan.h ../sshcr.h \ + ../ssh2connection.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh2connection-server.obj: ../ssh2connection-server.c ../putty.h \ + ../ssh.h ../sshbpp.h ../sshppl.h ../sshchan.h ../sshcr.h \ + ../ssh2connection.h ../sshserver.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh2kex-client.obj: ../ssh2kex-client.c ../putty.h ../ssh.h \ + ../sshbpp.h ../sshppl.h ../sshcr.h ../storage.h \ + ../ssh2transport.h ../mpint.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h ../sshgssc.h \ + ../sshgss.h ../windows/winstuff.h ../unix/unix.h \ + ../pgssapi.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh2kex-server.obj: ../ssh2kex-server.c ../putty.h ../ssh.h \ + ../sshbpp.h ../sshppl.h ../sshcr.h ../sshserver.h \ + ../storage.h ../ssh2transport.h ../mpint.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../sshgssc.h ../sshgss.h ../windows/winstuff.h \ + ../unix/unix.h ../pgssapi.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh2transhk.obj: ../ssh2transhk.c ../putty.h ../ssh.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh2transport.obj: ../ssh2transport.c ../putty.h ../ssh.h \ + ../sshbpp.h ../sshppl.h ../sshcr.h ../sshserver.h \ + ../storage.h ../ssh2transport.h ../mpint.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../sshgssc.h ../sshgss.h ../windows/winstuff.h \ + ../unix/unix.h ../pgssapi.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh2userauth.obj: ../ssh2userauth.c ../putty.h ../ssh.h \ + ../sshbpp.h ../sshppl.h ../sshcr.h ../sshgssc.h ../sshgss.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../pgssapi.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssh2userauth-server.obj: ../ssh2userauth-server.c ../putty.h \ + ../ssh.h ../sshbpp.h ../sshppl.h ../sshcr.h ../sshserver.h \ + ../sshgssc.h ../sshgss.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../pgssapi.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshaes.obj: ../sshaes.c ../ssh.h ../mpint_i.h ../puttymem.h \ + ../tree234.h ../network.h ../misc.h ../sshttymodes.h \ + ../defs.h ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ssharcf.obj: ../ssharcf.c ../ssh.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshauxcrypt.obj: ../sshauxcrypt.c ../ssh.h ../puttymem.h \ + ../tree234.h ../network.h ../misc.h ../sshttymodes.h \ + ../defs.h ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshbcrypt.obj: ../sshbcrypt.c ../ssh.h ../sshblowf.h \ + ../puttymem.h ../tree234.h ../network.h ../misc.h \ + ../sshttymodes.h ../defs.h ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshblowf.obj: ../sshblowf.c ../ssh.h ../sshblowf.h ../puttymem.h \ + ../tree234.h ../network.h ../misc.h ../sshttymodes.h \ + ../defs.h ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshccp.obj: ../sshccp.c ../ssh.h ../mpint_i.h ../puttymem.h \ + ../tree234.h ../network.h ../misc.h ../sshttymodes.h \ + ../defs.h ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshcommon.obj: ../sshcommon.c ../putty.h ../mpint.h ../ssh.h \ + ../sshbpp.h ../sshppl.h ../sshchan.h ../sshttymodes.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshcrc.obj: ../sshcrc.c ../ssh.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshcrcda.obj: ../sshcrcda.c ../misc.h ../ssh.h ../defs.h \ + ../puttymem.h ../marshal.h ../tree234.h ../network.h \ + ../sshttymodes.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshdes.obj: ../sshdes.c ../ssh.h ../mpint_i.h ../puttymem.h \ + ../tree234.h ../network.h ../misc.h ../sshttymodes.h \ + ../defs.h ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshdh.obj: ../sshdh.c ../ssh.h ../misc.h ../mpint.h ../puttymem.h \ + ../tree234.h ../network.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshdss.obj: ../sshdss.c ../ssh.h ../mpint.h ../misc.h \ + ../puttymem.h ../tree234.h ../network.h ../sshttymodes.h \ + ../defs.h ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshdssg.obj: ../sshdssg.c ../misc.h ../ssh.h ../mpint.h ../defs.h \ + ../puttymem.h ../marshal.h ../tree234.h ../network.h \ + ../sshttymodes.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshecc.obj: ../sshecc.c ../ssh.h ../mpint.h ../ecc.h \ + ../puttymem.h ../tree234.h ../network.h ../misc.h \ + ../sshttymodes.h ../defs.h ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshecdsag.obj: ../sshecdsag.c ../ssh.h ../mpint.h ../puttymem.h \ + ../tree234.h ../network.h ../misc.h ../sshttymodes.h \ + ../defs.h ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshgssc.obj: ../sshgssc.c ../putty.h ../sshgssc.h ../misc.h \ + ../defs.h ../puttyps.h ../network.h ../marshal.h \ + ../sshsignals.h ../pgssapi.h ../sshgss.h ../puttymem.h \ + ../windows/winstuff.h ../unix/unix.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshhmac.obj: ../sshhmac.c ../ssh.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshmac.obj: ../sshmac.c ../ssh.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshmd5.obj: ../sshmd5.c ../ssh.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshprime.obj: ../sshprime.c ../ssh.h ../mpint.h ../puttymem.h \ + ../tree234.h ../network.h ../misc.h ../sshttymodes.h \ + ../defs.h ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshprng.obj: ../sshprng.c ../putty.h ../ssh.h ../mpint.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshpubk.obj: ../sshpubk.c ../putty.h ../mpint.h ../ssh.h \ + ../misc.h ../defs.h ../puttyps.h ../network.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshrand.obj: ../sshrand.c ../putty.h ../ssh.h ../storage.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshrsa.obj: ../sshrsa.c ../ssh.h ../mpint.h ../misc.h \ + ../puttymem.h ../tree234.h ../network.h ../sshttymodes.h \ + ../defs.h ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshrsag.obj: ../sshrsag.c ../ssh.h ../mpint.h ../puttymem.h \ + ../tree234.h ../network.h ../misc.h ../sshttymodes.h \ + ../defs.h ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshserver.obj: ../sshserver.c ../putty.h ../ssh.h ../sshbpp.h \ + ../sshppl.h ../sshserver.h ../sshgssc.h ../sshgss.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../pgssapi.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshsh256.obj: ../sshsh256.c ../ssh.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshsh512.obj: ../sshsh512.c ../ssh.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshsha.obj: ../sshsha.c ../ssh.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshshare.obj: ../sshshare.c ../putty.h ../tree234.h ../ssh.h \ + ../sshcr.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../puttymem.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshverstring.obj: ../sshverstring.c ../putty.h ../ssh.h \ + ../sshbpp.h ../sshcr.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)sshzlib.obj: ../sshzlib.c ../defs.h ../ssh.h ../puttymem.h \ + ../tree234.h ../network.h ../misc.h ../sshttymodes.h \ + ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)stripctrl.obj: ../stripctrl.c ../putty.h ../terminal.h ../misc.h \ + ../marshal.h ../defs.h ../puttyps.h ../network.h \ + ../sshsignals.h ../tree234.h ../puttymem.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)telnet.obj: ../telnet.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)terminal.obj: ../terminal.c ../putty.h ../terminal.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../tree234.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)testcrypt.obj: ../testcrypt.c ../defs.h ../ssh.h ../misc.h \ + ../mpint.h ../ecc.h ../testcrypt.h ../puttymem.h \ + ../tree234.h ../network.h ../sshttymodes.h ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)testsc.obj: ../testsc.c ../defs.h ../putty.h ../ssh.h ../misc.h \ + ../mpint.h ../ecc.h ../puttyps.h ../network.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)testzlib.obj: ../testzlib.c ../defs.h ../ssh.h ../puttymem.h \ + ../tree234.h ../network.h ../misc.h ../sshttymodes.h \ + ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)time.obj: ../time.c + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)timing.obj: ../timing.c ../putty.h ../tree234.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)toucs.obj: ../charset/toucs.c ../charset/charset.h \ + ../charset/internal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)tree234.obj: ../tree234.c ../defs.h ../tree234.h ../puttymem.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)utf8.obj: ../charset/utf8.c ../charset/charset.h \ + ../charset/internal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)utils.obj: ../utils.c ../defs.h ../misc.h ../puttymem.h \ + ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)ux_x11.obj: ../unix/ux_x11.c ../putty.h ../ssh.h ../network.h \ + ../defs.h ../puttyps.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxagentc.obj: ../unix/uxagentc.c ../putty.h ../misc.h \ + ../tree234.h ../puttymem.h ../defs.h ../puttyps.h \ + ../network.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxagentsock.obj: ../unix/uxagentsock.c ../putty.h ../ssh.h \ + ../misc.h ../pageant.h ../defs.h ../puttyps.h ../network.h \ + ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxcfg.obj: ../unix/uxcfg.c ../putty.h ../dialog.h ../storage.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxcons.obj: ../unix/uxcons.c ../putty.h ../storage.h ../ssh.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxfdsock.obj: ../unix/uxfdsock.c ../tree234.h ../putty.h \ + ../network.h ../defs.h ../puttyps.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxgen.obj: ../unix/uxgen.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxgss.obj: ../unix/uxgss.c ../putty.h ../pgssapi.h ../sshgss.h \ + ../sshgssc.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxmisc.obj: ../unix/uxmisc.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxnet.obj: ../unix/uxnet.c ../putty.h ../network.h ../tree234.h \ + ../defs.h ../puttyps.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxnogtk.obj: ../unix/uxnogtk.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxnoise.obj: ../unix/uxnoise.c ../putty.h ../ssh.h ../storage.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxpeer.obj: ../unix/uxpeer.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxpgnt.obj: ../unix/uxpgnt.c ../putty.h ../ssh.h ../misc.h \ + ../pageant.h ../defs.h ../puttyps.h ../network.h \ + ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxplink.obj: ../unix/uxplink.c ../putty.h ../storage.h \ + ../tree234.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxpoll.obj: ../unix/uxpoll.c ../putty.h ../tree234.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxprint.obj: ../unix/uxprint.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxproxy.obj: ../unix/uxproxy.c ../tree234.h ../putty.h \ + ../network.h ../proxy.h ../defs.h ../puttyps.h ../misc.h \ + ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxpterm.obj: ../unix/uxpterm.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxpty.obj: ../unix/uxpty.c ../putty.h ../ssh.h ../tree234.h \ + ../sshttymodes.h ../sshsignals.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../puttymem.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxputty.obj: ../unix/uxputty.c ../putty.h ../storage.h \ + ../unix/gtkcompat.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxsel.obj: ../unix/uxsel.c ../putty.h ../tree234.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxser.obj: ../unix/uxser.c ../putty.h ../tree234.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxserver.obj: ../unix/uxserver.c ../putty.h ../mpint.h ../ssh.h \ + ../sshserver.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxsftp.obj: ../unix/uxsftp.c ../putty.h ../ssh.h ../psftp.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxsftpserver.obj: ../unix/uxsftpserver.c ../putty.h ../ssh.h \ + ../sftp.h ../tree234.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxshare.obj: ../unix/uxshare.c ../tree234.h ../putty.h \ + ../network.h ../proxy.h ../ssh.h ../defs.h ../puttyps.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxsignal.obj: ../unix/uxsignal.c ../defs.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxstore.obj: ../unix/uxstore.c ../putty.h ../storage.h \ + ../tree234.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxucs.obj: ../unix/uxucs.c ../putty.h ../charset/charset.h \ + ../terminal.h ../misc.h ../defs.h ../puttyps.h ../network.h \ + ../marshal.h ../sshsignals.h ../tree234.h ../puttymem.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)uxutils.obj: ../unix/uxutils.c ../putty.h ../ssh.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)version.obj: ../version.c ../empty.h ../version.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)wcwidth.obj: ../wcwidth.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)wildcard.obj: ../wildcard.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)wincapi.obj: ../windows/wincapi.c ../putty.h ../windows/wincapi.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)wincfg.obj: ../windows/wincfg.c ../putty.h ../dialog.h \ + ../storage.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)wincons.obj: ../windows/wincons.c ../putty.h ../storage.h \ + ../ssh.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winctrls.obj: ../windows/winctrls.c ../putty.h ../misc.h \ + ../dialog.h ../defs.h ../puttyps.h ../network.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../windows/winstuff.h \ + ../unix/unix.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)windefs.obj: ../windows/windefs.c ../putty.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)windlg.obj: ../windows/windlg.c ../putty.h ../ssh.h \ + ../windows/win_res.h ../storage.h ../dialog.h ../licence.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)window.obj: ../windows/window.c ../putty.h ../terminal.h \ + ../storage.h ../windows/win_res.h ../windows/winsecur.h \ + ../tree234.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)wingss.obj: ../windows/wingss.c ../putty.h ../pgssapi.h \ + ../sshgss.h ../sshgssc.h ../misc.h ../defs.h ../puttyps.h \ + ../network.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../windows/winstuff.h ../unix/unix.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winhandl.obj: ../windows/winhandl.c ../putty.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winhelp.obj: ../windows/winhelp.c ../putty.h ../windows/win_res.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winhsock.obj: ../windows/winhsock.c ../tree234.h ../putty.h \ + ../network.h ../defs.h ../puttyps.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winjump.obj: ../windows/winjump.c ../putty.h ../storage.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winmisc.obj: ../windows/winmisc.c ../putty.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winmiscs.obj: ../windows/winmiscs.c ../putty.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winnet.obj: ../windows/winnet.c ../putty.h ../network.h \ + ../tree234.h ../defs.h ../puttyps.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winnohlp.obj: ../windows/winnohlp.c ../putty.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winnoise.obj: ../windows/winnoise.c ../putty.h ../ssh.h \ + ../storage.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winnojmp.obj: ../windows/winnojmp.c + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winnpc.obj: ../windows/winnpc.c ../tree234.h ../putty.h \ + ../network.h ../proxy.h ../ssh.h ../windows/winsecur.h \ + ../defs.h ../puttyps.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winnps.obj: ../windows/winnps.c ../tree234.h ../putty.h \ + ../network.h ../proxy.h ../ssh.h ../windows/winsecur.h \ + ../defs.h ../puttyps.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winpgen.obj: ../windows/winpgen.c ../putty.h ../ssh.h \ + ../licence.h ../windows/winsecur.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winpgnt.obj: ../windows/winpgnt.c ../putty.h ../ssh.h ../misc.h \ + ../tree234.h ../windows/winsecur.h ../pageant.h ../licence.h \ + ../defs.h ../puttyps.h ../network.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winpgntc.obj: ../windows/winpgntc.c ../putty.h ../pageant.h \ + ../windows/winsecur.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winplink.obj: ../windows/winplink.c ../putty.h ../storage.h \ + ../tree234.h ../windows/winsecur.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winprint.obj: ../windows/winprint.c ../putty.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winproxy.obj: ../windows/winproxy.c ../tree234.h ../putty.h \ + ../network.h ../proxy.h ../defs.h ../puttyps.h ../misc.h \ + ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winsecur.obj: ../windows/winsecur.c ../putty.h \ + ../windows/winsecur.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winser.obj: ../windows/winser.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winsftp.obj: ../windows/winsftp.c ../putty.h ../psftp.h ../ssh.h \ + ../windows/winsecur.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winshare.obj: ../windows/winshare.c ../tree234.h ../putty.h \ + ../network.h ../proxy.h ../ssh.h ../windows/wincapi.h \ + ../windows/winsecur.h ../noshare.c ../defs.h ../puttyps.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winstore.obj: ../windows/winstore.c ../putty.h ../storage.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)wintime.obj: ../windows/wintime.c ../putty.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winucs.obj: ../windows/winucs.c ../putty.h ../terminal.h \ + ../misc.h ../defs.h ../puttyps.h ../network.h ../marshal.h \ + ../sshsignals.h ../tree234.h ../puttymem.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winutils.obj: ../windows/winutils.c ../putty.h ../misc.h \ + ../defs.h ../puttyps.h ../network.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../windows/winstuff.h \ + ../unix/unix.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)winx11.obj: ../windows/winx11.c ../putty.h ../ssh.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)x11fwd.obj: ../x11fwd.c ../putty.h ../ssh.h ../sshchan.h \ + ../tree234.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../puttymem.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)x11misc.obj: ../unix/x11misc.c ../putty.h ../unix/x11misc.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)xenc.obj: ../charset/xenc.c ../charset/charset.h \ + ../charset/internal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)xkeysym.obj: ../unix/xkeysym.c ../misc.h ../defs.h ../puttymem.h \ + ../marshal.h + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)xpmptcfg.obj: ../unix/xpmptcfg.c + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)xpmpterm.obj: ../unix/xpmpterm.c + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)xpmpucfg.obj: ../unix/xpmpucfg.c + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + +$(BUILDDIR)xpmputty.obj: ../unix/xpmputty.c + $(CC) /Fo$(BUILDDIR) $(COMPAT) $(CFLAGS) $(XFLAGS) /c $< + + +$(BUILDDIR)pageant.rcpp: ../windows/pageant.rc ../windows/winhelp.rc2 \ + ../windows/version.rc2 + $(RCPREPROC) $(RCPPFLAGS) /Fi$@ $< + +$(BUILDDIR)plink.rcpp: ../windows/plink.rc ../windows/version.rc2 + $(RCPREPROC) $(RCPPFLAGS) /Fi$@ $< + +$(BUILDDIR)pscp.rcpp: ../windows/pscp.rc ../windows/version.rc2 + $(RCPREPROC) $(RCPPFLAGS) /Fi$@ $< + +$(BUILDDIR)psftp.rcpp: ../windows/psftp.rc ../windows/version.rc2 + $(RCPREPROC) $(RCPPFLAGS) /Fi$@ $< + +$(BUILDDIR)putty.rcpp: ../windows/putty.rc ../windows/winhelp.rc2 \ + ../windows/win_res.rc2 ../windows/version.rc2 + $(RCPREPROC) $(RCPPFLAGS) /Fi$@ $< + +$(BUILDDIR)puttygen.rcpp: ../windows/puttygen.rc ../windows/winhelp.rc2 \ + ../windows/version.rc2 + $(RCPREPROC) $(RCPPFLAGS) /Fi$@ $< + +$(BUILDDIR)puttytel.rcpp: ../windows/puttytel.rc ../windows/winhelp.rc2 \ + ../windows/win_res.rc2 ../windows/version.rc2 + $(RCPREPROC) $(RCPPFLAGS) /Fi$@ $< + +cleantestprogs: + -rm -f $(BUILDDIR)testcrypt.exe + +clean: + rm -f $(BUILDDIR)*.obj $(BUILDDIR)*.exe $(BUILDDIR)*.rcpp $(BUILDDIR)*.res \ + $(BUILDDIR)*.map $(BUILDDIR)*.exe.manifest diff --git a/windows/Makefile.lcc b/windows/Makefile.lcc index 0be53e7..83c898a 100644 --- a/windows/Makefile.lcc +++ b/windows/Makefile.lcc @@ -179,10 +179,10 @@ pscp.exe: agentf.obj aqsync.obj be_misc.obj be_ssh.obj callback.obj \ cmdline.obj conf.obj cproxy.obj ecc.obj errsock.obj \ logging.obj mainchan.obj marshal.obj memory.obj misc.obj \ miscucs.obj mpint.obj nullplug.obj pgssapi.obj pinger.obj \ - portfwd.obj proxy.obj pscp.obj pscp.res settings.obj \ - sftp.obj sftpcommon.obj ssh.obj ssh1bpp.obj ssh1censor.obj \ - ssh1connection.obj ssh1connection-client.obj ssh1login.obj \ - ssh2bpp.obj ssh2bpp-bare.obj ssh2censor.obj \ + portfwd.obj proxy.obj pscp.obj pscp.res psftpcommon.obj \ + settings.obj sftp.obj sftpcommon.obj ssh.obj ssh1bpp.obj \ + ssh1censor.obj ssh1connection.obj ssh1connection-client.obj \ + ssh1login.obj ssh2bpp.obj ssh2bpp-bare.obj ssh2censor.obj \ ssh2connection.obj ssh2connection-client.obj \ ssh2kex-client.obj ssh2transhk.obj ssh2transport.obj \ ssh2userauth.obj sshaes.obj ssharcf.obj sshauxcrypt.obj \ @@ -203,20 +203,20 @@ pscp.exe: agentf.obj aqsync.obj be_misc.obj be_ssh.obj callback.obj \ errsock.obj logging.obj mainchan.obj marshal.obj memory.obj \ misc.obj miscucs.obj mpint.obj nullplug.obj pgssapi.obj \ pinger.obj portfwd.obj proxy.obj pscp.obj pscp.res \ - settings.obj sftp.obj sftpcommon.obj ssh.obj ssh1bpp.obj \ - ssh1censor.obj ssh1connection.obj ssh1connection-client.obj \ - ssh1login.obj ssh2bpp.obj ssh2bpp-bare.obj ssh2censor.obj \ - ssh2connection.obj ssh2connection-client.obj \ - ssh2kex-client.obj ssh2transhk.obj ssh2transport.obj \ - ssh2userauth.obj sshaes.obj ssharcf.obj sshauxcrypt.obj \ - sshblowf.obj sshccp.obj sshcommon.obj sshcrc.obj \ - sshcrcda.obj sshdes.obj sshdh.obj sshdss.obj sshecc.obj \ - sshgssc.obj sshhmac.obj sshmac.obj sshmd5.obj sshprng.obj \ - sshpubk.obj sshrand.obj sshrsa.obj sshsh256.obj sshsh512.obj \ - sshsha.obj sshshare.obj sshverstring.obj sshzlib.obj \ - stripctrl.obj timing.obj tree234.obj utils.obj version.obj \ - wcwidth.obj wildcard.obj wincapi.obj wincons.obj windefs.obj \ - wingss.obj winhandl.obj winhsock.obj winmisc.obj \ + psftpcommon.obj settings.obj sftp.obj sftpcommon.obj ssh.obj \ + ssh1bpp.obj ssh1censor.obj ssh1connection.obj \ + ssh1connection-client.obj ssh1login.obj ssh2bpp.obj \ + ssh2bpp-bare.obj ssh2censor.obj ssh2connection.obj \ + ssh2connection-client.obj ssh2kex-client.obj ssh2transhk.obj \ + ssh2transport.obj ssh2userauth.obj sshaes.obj ssharcf.obj \ + sshauxcrypt.obj sshblowf.obj sshccp.obj sshcommon.obj \ + sshcrc.obj sshcrcda.obj sshdes.obj sshdh.obj sshdss.obj \ + sshecc.obj sshgssc.obj sshhmac.obj sshmac.obj sshmd5.obj \ + sshprng.obj sshpubk.obj sshrand.obj sshrsa.obj sshsh256.obj \ + sshsh512.obj sshsha.obj sshshare.obj sshverstring.obj \ + sshzlib.obj stripctrl.obj timing.obj tree234.obj utils.obj \ + version.obj wcwidth.obj wildcard.obj wincapi.obj wincons.obj \ + windefs.obj wingss.obj winhandl.obj winhsock.obj winmisc.obj \ winmiscs.obj winnet.obj winnohlp.obj winnoise.obj \ winnojmp.obj winnpc.obj winnps.obj winpgntc.obj winproxy.obj \ winsecur.obj winsftp.obj winshare.obj winstore.obj \ @@ -227,10 +227,10 @@ psftp.exe: agentf.obj aqsync.obj be_misc.obj be_ssh.obj callback.obj \ cmdline.obj conf.obj cproxy.obj ecc.obj errsock.obj \ logging.obj mainchan.obj marshal.obj memory.obj misc.obj \ miscucs.obj mpint.obj nullplug.obj pgssapi.obj pinger.obj \ - portfwd.obj proxy.obj psftp.obj psftp.res settings.obj \ - sftp.obj sftpcommon.obj ssh.obj ssh1bpp.obj ssh1censor.obj \ - ssh1connection.obj ssh1connection-client.obj ssh1login.obj \ - ssh2bpp.obj ssh2bpp-bare.obj ssh2censor.obj \ + portfwd.obj proxy.obj psftp.obj psftp.res psftpcommon.obj \ + settings.obj sftp.obj sftpcommon.obj ssh.obj ssh1bpp.obj \ + ssh1censor.obj ssh1connection.obj ssh1connection-client.obj \ + ssh1login.obj ssh2bpp.obj ssh2bpp-bare.obj ssh2censor.obj \ ssh2connection.obj ssh2connection-client.obj \ ssh2kex-client.obj ssh2transhk.obj ssh2transport.obj \ ssh2userauth.obj sshaes.obj ssharcf.obj sshauxcrypt.obj \ @@ -251,7 +251,33 @@ psftp.exe: agentf.obj aqsync.obj be_misc.obj be_ssh.obj callback.obj \ errsock.obj logging.obj mainchan.obj marshal.obj memory.obj \ misc.obj miscucs.obj mpint.obj nullplug.obj pgssapi.obj \ pinger.obj portfwd.obj proxy.obj psftp.obj psftp.res \ - settings.obj sftp.obj sftpcommon.obj ssh.obj ssh1bpp.obj \ + psftpcommon.obj settings.obj sftp.obj sftpcommon.obj ssh.obj \ + ssh1bpp.obj ssh1censor.obj ssh1connection.obj \ + ssh1connection-client.obj ssh1login.obj ssh2bpp.obj \ + ssh2bpp-bare.obj ssh2censor.obj ssh2connection.obj \ + ssh2connection-client.obj ssh2kex-client.obj ssh2transhk.obj \ + ssh2transport.obj ssh2userauth.obj sshaes.obj ssharcf.obj \ + sshauxcrypt.obj sshblowf.obj sshccp.obj sshcommon.obj \ + sshcrc.obj sshcrcda.obj sshdes.obj sshdh.obj sshdss.obj \ + sshecc.obj sshgssc.obj sshhmac.obj sshmac.obj sshmd5.obj \ + sshprng.obj sshpubk.obj sshrand.obj sshrsa.obj sshsh256.obj \ + sshsh512.obj sshsha.obj sshshare.obj sshverstring.obj \ + sshzlib.obj stripctrl.obj timing.obj tree234.obj utils.obj \ + version.obj wcwidth.obj wildcard.obj wincapi.obj wincons.obj \ + windefs.obj wingss.obj winhandl.obj winhsock.obj winmisc.obj \ + winmiscs.obj winnet.obj winnohlp.obj winnoise.obj \ + winnojmp.obj winnpc.obj winnps.obj winpgntc.obj winproxy.obj \ + winsecur.obj winsftp.obj winshare.obj winstore.obj \ + wintime.obj winucs.obj x11fwd.obj shell32.lib wsock32.lib \ + ws2_32.lib winspool.lib winmm.lib imm32.lib + +putty.exe: agentf.obj aqsync.obj be_all_s.obj be_misc.obj callback.obj \ + cmdline.obj conf.obj config.obj cproxy.obj dialog.obj \ + ecc.obj errsock.obj ldisc.obj logging.obj mainchan.obj \ + marshal.obj memory.obj minibidi.obj misc.obj miscucs.obj \ + mpint.obj nullplug.obj pgssapi.obj pinger.obj portfwd.obj \ + proxy.obj putty.res raw.obj rlogin.obj sercfg.obj \ + sessprep.obj settings.obj sizetip.obj ssh.obj ssh1bpp.obj \ ssh1censor.obj ssh1connection.obj ssh1connection-client.obj \ ssh1login.obj ssh2bpp.obj ssh2bpp-bare.obj ssh2censor.obj \ ssh2connection.obj ssh2connection-client.obj \ @@ -262,23 +288,22 @@ psftp.exe: agentf.obj aqsync.obj be_misc.obj be_ssh.obj callback.obj \ sshgssc.obj sshhmac.obj sshmac.obj sshmd5.obj sshprng.obj \ sshpubk.obj sshrand.obj sshrsa.obj sshsh256.obj sshsh512.obj \ sshsha.obj sshshare.obj sshverstring.obj sshzlib.obj \ - stripctrl.obj timing.obj tree234.obj utils.obj version.obj \ - wcwidth.obj wildcard.obj wincapi.obj wincons.obj windefs.obj \ - wingss.obj winhandl.obj winhsock.obj winmisc.obj \ - winmiscs.obj winnet.obj winnohlp.obj winnoise.obj \ - winnojmp.obj winnpc.obj winnps.obj winpgntc.obj winproxy.obj \ - winsecur.obj winsftp.obj winshare.obj winstore.obj \ - wintime.obj winucs.obj x11fwd.obj shell32.lib wsock32.lib \ - ws2_32.lib winspool.lib winmm.lib imm32.lib - -putty.exe: agentf.obj aqsync.obj be_all_s.obj be_misc.obj callback.obj \ - cmdline.obj conf.obj config.obj cproxy.obj dialog.obj \ - ecc.obj errsock.obj ldisc.obj ldiscucs.obj logging.obj \ - mainchan.obj marshal.obj memory.obj minibidi.obj misc.obj \ - miscucs.obj mpint.obj nullplug.obj pgssapi.obj pinger.obj \ - portfwd.obj proxy.obj putty.res raw.obj rlogin.obj \ - sercfg.obj sessprep.obj settings.obj sizetip.obj ssh.obj \ - ssh1bpp.obj ssh1censor.obj ssh1connection.obj \ + stripctrl.obj telnet.obj terminal.obj timing.obj tree234.obj \ + utils.obj version.obj wcwidth.obj wildcard.obj wincapi.obj \ + wincfg.obj winctrls.obj windefs.obj windlg.obj window.obj \ + wingss.obj winhandl.obj winhelp.obj winhsock.obj winjump.obj \ + winmisc.obj winmiscs.obj winnet.obj winnoise.obj winnpc.obj \ + winnps.obj winpgntc.obj winprint.obj winproxy.obj \ + winsecur.obj winser.obj winshare.obj winstore.obj \ + wintime.obj winucs.obj winutils.obj winx11.obj x11fwd.obj + lcclnk -subsystem windows -o putty.exe agentf.obj aqsync.obj be_all_s.obj \ + be_misc.obj callback.obj cmdline.obj conf.obj config.obj \ + cproxy.obj dialog.obj ecc.obj errsock.obj ldisc.obj \ + logging.obj mainchan.obj marshal.obj memory.obj minibidi.obj \ + misc.obj miscucs.obj mpint.obj nullplug.obj pgssapi.obj \ + pinger.obj portfwd.obj proxy.obj putty.res raw.obj \ + rlogin.obj sercfg.obj sessprep.obj settings.obj sizetip.obj \ + ssh.obj ssh1bpp.obj ssh1censor.obj ssh1connection.obj \ ssh1connection-client.obj ssh1login.obj ssh2bpp.obj \ ssh2bpp-bare.obj ssh2censor.obj ssh2connection.obj \ ssh2connection-client.obj ssh2kex-client.obj ssh2transhk.obj \ @@ -295,32 +320,6 @@ putty.exe: agentf.obj aqsync.obj be_all_s.obj be_misc.obj callback.obj \ winjump.obj winmisc.obj winmiscs.obj winnet.obj winnoise.obj \ winnpc.obj winnps.obj winpgntc.obj winprint.obj winproxy.obj \ winsecur.obj winser.obj winshare.obj winstore.obj \ - wintime.obj winucs.obj winutils.obj winx11.obj x11fwd.obj - lcclnk -subsystem windows -o putty.exe agentf.obj aqsync.obj be_all_s.obj \ - be_misc.obj callback.obj cmdline.obj conf.obj config.obj \ - cproxy.obj dialog.obj ecc.obj errsock.obj ldisc.obj \ - ldiscucs.obj logging.obj mainchan.obj marshal.obj memory.obj \ - minibidi.obj misc.obj miscucs.obj mpint.obj nullplug.obj \ - pgssapi.obj pinger.obj portfwd.obj proxy.obj putty.res \ - raw.obj rlogin.obj sercfg.obj sessprep.obj settings.obj \ - sizetip.obj ssh.obj ssh1bpp.obj ssh1censor.obj \ - ssh1connection.obj ssh1connection-client.obj ssh1login.obj \ - ssh2bpp.obj ssh2bpp-bare.obj ssh2censor.obj \ - ssh2connection.obj ssh2connection-client.obj \ - ssh2kex-client.obj ssh2transhk.obj ssh2transport.obj \ - ssh2userauth.obj sshaes.obj ssharcf.obj sshauxcrypt.obj \ - sshblowf.obj sshccp.obj sshcommon.obj sshcrc.obj \ - sshcrcda.obj sshdes.obj sshdh.obj sshdss.obj sshecc.obj \ - sshgssc.obj sshhmac.obj sshmac.obj sshmd5.obj sshprng.obj \ - sshpubk.obj sshrand.obj sshrsa.obj sshsh256.obj sshsh512.obj \ - sshsha.obj sshshare.obj sshverstring.obj sshzlib.obj \ - stripctrl.obj telnet.obj terminal.obj timing.obj tree234.obj \ - utils.obj version.obj wcwidth.obj wildcard.obj wincapi.obj \ - wincfg.obj winctrls.obj windefs.obj windlg.obj window.obj \ - wingss.obj winhandl.obj winhelp.obj winhsock.obj winjump.obj \ - winmisc.obj winmiscs.obj winnet.obj winnoise.obj winnpc.obj \ - winnps.obj winpgntc.obj winprint.obj winproxy.obj \ - winsecur.obj winser.obj winshare.obj winstore.obj \ wintime.obj winucs.obj winutils.obj winx11.obj x11fwd.obj \ shell32.lib wsock32.lib ws2_32.lib winspool.lib winmm.lib \ imm32.lib @@ -349,23 +348,23 @@ puttygen.exe: conf.obj ecc.obj import.obj marshal.obj memory.obj misc.obj \ winspool.lib winmm.lib imm32.lib puttytel.exe: be_misc.obj be_nos_s.obj callback.obj cmdline.obj conf.obj \ - config.obj dialog.obj errsock.obj ldisc.obj ldiscucs.obj \ - logging.obj marshal.obj memory.obj minibidi.obj misc.obj \ - miscucs.obj nocproxy.obj nogss.obj pinger.obj proxy.obj \ - puttytel.res raw.obj rlogin.obj sercfg.obj sessprep.obj \ - settings.obj sizetip.obj stripctrl.obj telnet.obj \ - terminal.obj timing.obj tree234.obj utils.obj version.obj \ - wcwidth.obj wincfg.obj winctrls.obj windefs.obj windlg.obj \ - window.obj winhandl.obj winhelp.obj winhsock.obj winjump.obj \ - winmisc.obj winmiscs.obj winnet.obj winprint.obj \ - winproxy.obj winsecur.obj winser.obj winstore.obj \ - wintime.obj winucs.obj winutils.obj + config.obj dialog.obj errsock.obj ldisc.obj logging.obj \ + marshal.obj memory.obj minibidi.obj misc.obj miscucs.obj \ + nocproxy.obj nogss.obj pinger.obj proxy.obj puttytel.res \ + raw.obj rlogin.obj sercfg.obj sessprep.obj settings.obj \ + sizetip.obj stripctrl.obj telnet.obj terminal.obj timing.obj \ + tree234.obj utils.obj version.obj wcwidth.obj wincfg.obj \ + winctrls.obj windefs.obj windlg.obj window.obj winhandl.obj \ + winhelp.obj winhsock.obj winjump.obj winmisc.obj \ + winmiscs.obj winnet.obj winprint.obj winproxy.obj \ + winsecur.obj winser.obj winstore.obj wintime.obj winucs.obj \ + winutils.obj lcclnk -subsystem windows -o puttytel.exe be_misc.obj be_nos_s.obj \ callback.obj cmdline.obj conf.obj config.obj dialog.obj \ - errsock.obj ldisc.obj ldiscucs.obj logging.obj marshal.obj \ - memory.obj minibidi.obj misc.obj miscucs.obj nocproxy.obj \ - nogss.obj pinger.obj proxy.obj puttytel.res raw.obj \ - rlogin.obj sercfg.obj sessprep.obj settings.obj sizetip.obj \ + errsock.obj ldisc.obj logging.obj marshal.obj memory.obj \ + minibidi.obj misc.obj miscucs.obj nocproxy.obj nogss.obj \ + pinger.obj proxy.obj puttytel.res raw.obj rlogin.obj \ + sercfg.obj sessprep.obj settings.obj sizetip.obj \ stripctrl.obj telnet.obj terminal.obj timing.obj tree234.obj \ utils.obj version.obj wcwidth.obj wincfg.obj winctrls.obj \ windefs.obj windlg.obj window.obj winhandl.obj winhelp.obj \ @@ -491,7 +490,10 @@ gtkapp.obj: ..\unix\gtkapp.c ..\putty.h ..\unix\gtkmisc.h ..\defs.h \ ..\charset\charset.h lcc -O -p6 $(COMPAT) $(CFLAGS) $(XFLAGS) ..\unix\gtkapp.c gtkask.obj: ..\unix\gtkask.c ..\defs.h ..\unix\gtkfont.h ..\unix\gtkcompat.h \ - ..\unix\gtkmisc.h ..\misc.h ..\puttymem.h ..\marshal.h + ..\unix\gtkmisc.h ..\putty.h ..\ssh.h ..\misc.h ..\puttyps.h \ + ..\network.h ..\marshal.h ..\sshsignals.h ..\puttymem.h \ + ..\tree234.h ..\sshttymodes.h ..\windows\winstuff.h \ + ..\unix\unix.h ..\windows\winhelp.h ..\charset\charset.h lcc -O -p6 $(COMPAT) $(CFLAGS) $(XFLAGS) ..\unix\gtkask.c gtkcfg.obj: ..\unix\gtkcfg.c ..\putty.h ..\dialog.h ..\storage.h ..\defs.h \ ..\puttyps.h ..\network.h ..\misc.h ..\marshal.h \ @@ -555,12 +557,6 @@ ldisc.obj: ..\ldisc.c ..\putty.h ..\terminal.h ..\ldisc.h ..\defs.h \ ..\unix\unix.h ..\puttymem.h ..\windows\winhelp.h \ ..\charset\charset.h lcc -O -p6 $(COMPAT) $(CFLAGS) $(XFLAGS) ..\ldisc.c -ldiscucs.obj: ..\ldiscucs.c ..\putty.h ..\terminal.h ..\ldisc.h ..\defs.h \ - ..\puttyps.h ..\network.h ..\misc.h ..\marshal.h \ - ..\sshsignals.h ..\tree234.h ..\windows\winstuff.h \ - ..\unix\unix.h ..\puttymem.h ..\windows\winhelp.h \ - ..\charset\charset.h - lcc -O -p6 $(COMPAT) $(CFLAGS) $(XFLAGS) ..\ldiscucs.c localenc.obj: ..\charset\localenc.c ..\charset\charset.h \ ..\charset\internal.h lcc -O -p6 $(COMPAT) $(CFLAGS) $(XFLAGS) ..\charset\localenc.c @@ -664,6 +660,9 @@ portfwd.obj: ..\portfwd.c ..\putty.h ..\ssh.h ..\sshchan.h ..\defs.h \ ..\windows\winstuff.h ..\unix\unix.h ..\windows\winhelp.h \ ..\charset\charset.h lcc -O -p6 $(COMPAT) $(CFLAGS) $(XFLAGS) ..\portfwd.c +procnet.obj: ..\unix\procnet.c ..\misc.h ..\defs.h ..\puttymem.h \ + ..\marshal.h + lcc -O -p6 $(COMPAT) $(CFLAGS) $(XFLAGS) ..\unix\procnet.c proxy.obj: ..\proxy.c ..\putty.h ..\network.h ..\proxy.h ..\defs.h \ ..\puttyps.h ..\misc.h ..\marshal.h ..\sshsignals.h \ ..\windows\winstuff.h ..\unix\unix.h ..\puttymem.h \ @@ -687,6 +686,12 @@ psftp.obj: ..\psftp.c ..\putty.h ..\psftp.h ..\storage.h ..\ssh.h ..\sftp.h \ psftp.res: ..\windows\psftp.rc ..\windows\rcstuff.h ..\windows\pscp.ico \ ..\windows\version.rc2 ..\version.h ..\licence.h lrc $(RCFL) -r $(RCFLAGS) ..\windows\psftp.rc +psftpcommon.obj: ..\psftpcommon.c ..\putty.h ..\sftp.h ..\psftp.h ..\defs.h \ + ..\puttyps.h ..\network.h ..\misc.h ..\marshal.h \ + ..\sshsignals.h ..\windows\winstuff.h ..\unix\unix.h \ + ..\puttymem.h ..\tree234.h ..\windows\winhelp.h \ + ..\charset\charset.h + lcc -O -p6 $(COMPAT) $(CFLAGS) $(XFLAGS) ..\psftpcommon.c putty.res: ..\windows\putty.rc ..\windows\rcstuff.h ..\windows\winhelp.rc2 \ ..\windows\win_res.rc2 ..\windows\putty.mft \ ..\windows\win_res.h ..\windows\putty.ico \ @@ -870,12 +875,12 @@ ssh2kex-client.obj: ..\ssh2kex-client.c ..\putty.h ..\ssh.h ..\sshbpp.h \ ..\windows\winhelp.h ..\charset\charset.h lcc -O -p6 $(COMPAT) $(CFLAGS) $(XFLAGS) ..\ssh2kex-client.c ssh2kex-server.obj: ..\ssh2kex-server.c ..\putty.h ..\ssh.h ..\sshbpp.h \ - ..\sshppl.h ..\sshcr.h ..\storage.h ..\ssh2transport.h \ - ..\mpint.h ..\defs.h ..\puttyps.h ..\network.h ..\misc.h \ - ..\marshal.h ..\sshsignals.h ..\puttymem.h ..\tree234.h \ - ..\sshttymodes.h ..\sshgssc.h ..\sshgss.h \ - ..\windows\winstuff.h ..\unix\unix.h ..\pgssapi.h \ - ..\windows\winhelp.h ..\charset\charset.h + ..\sshppl.h ..\sshcr.h ..\sshserver.h ..\storage.h \ + ..\ssh2transport.h ..\mpint.h ..\defs.h ..\puttyps.h \ + ..\network.h ..\misc.h ..\marshal.h ..\sshsignals.h \ + ..\puttymem.h ..\tree234.h ..\sshttymodes.h ..\sshgssc.h \ + ..\sshgss.h ..\windows\winstuff.h ..\unix\unix.h \ + ..\pgssapi.h ..\windows\winhelp.h ..\charset\charset.h lcc -O -p6 $(COMPAT) $(CFLAGS) $(XFLAGS) ..\ssh2kex-server.c ssh2transhk.obj: ..\ssh2transhk.c ..\putty.h ..\ssh.h ..\defs.h ..\puttyps.h \ ..\network.h ..\misc.h ..\marshal.h ..\sshsignals.h \ @@ -884,12 +889,12 @@ ssh2transhk.obj: ..\ssh2transhk.c ..\putty.h ..\ssh.h ..\defs.h ..\puttyps.h \ ..\charset\charset.h lcc -O -p6 $(COMPAT) $(CFLAGS) $(XFLAGS) ..\ssh2transhk.c ssh2transport.obj: ..\ssh2transport.c ..\putty.h ..\ssh.h ..\sshbpp.h \ - ..\sshppl.h ..\sshcr.h ..\storage.h ..\ssh2transport.h \ - ..\mpint.h ..\defs.h ..\puttyps.h ..\network.h ..\misc.h \ - ..\marshal.h ..\sshsignals.h ..\puttymem.h ..\tree234.h \ - ..\sshttymodes.h ..\sshgssc.h ..\sshgss.h \ - ..\windows\winstuff.h ..\unix\unix.h ..\pgssapi.h \ - ..\windows\winhelp.h ..\charset\charset.h + ..\sshppl.h ..\sshcr.h ..\sshserver.h ..\storage.h \ + ..\ssh2transport.h ..\mpint.h ..\defs.h ..\puttyps.h \ + ..\network.h ..\misc.h ..\marshal.h ..\sshsignals.h \ + ..\puttymem.h ..\tree234.h ..\sshttymodes.h ..\sshgssc.h \ + ..\sshgss.h ..\windows\winstuff.h ..\unix\unix.h \ + ..\pgssapi.h ..\windows\winhelp.h ..\charset\charset.h lcc -O -p6 $(COMPAT) $(CFLAGS) $(XFLAGS) ..\ssh2transport.c ssh2userauth.obj: ..\ssh2userauth.c ..\putty.h ..\ssh.h ..\sshbpp.h \ ..\sshppl.h ..\sshcr.h ..\sshgssc.h ..\sshgss.h ..\defs.h \ @@ -997,9 +1002,9 @@ sshpubk.obj: ..\sshpubk.c ..\putty.h ..\mpint.h ..\ssh.h ..\misc.h ..\defs.h \ ..\windows\winstuff.h ..\unix\unix.h ..\windows\winhelp.h \ ..\charset\charset.h lcc -O -p6 $(COMPAT) $(CFLAGS) $(XFLAGS) ..\sshpubk.c -sshrand.obj: ..\sshrand.c ..\putty.h ..\ssh.h ..\defs.h ..\puttyps.h \ - ..\network.h ..\misc.h ..\marshal.h ..\sshsignals.h \ - ..\puttymem.h ..\tree234.h ..\sshttymodes.h \ +sshrand.obj: ..\sshrand.c ..\putty.h ..\ssh.h ..\storage.h ..\defs.h \ + ..\puttyps.h ..\network.h ..\misc.h ..\marshal.h \ + ..\sshsignals.h ..\puttymem.h ..\tree234.h ..\sshttymodes.h \ ..\windows\winstuff.h ..\unix\unix.h ..\windows\winhelp.h \ ..\charset\charset.h lcc -O -p6 $(COMPAT) $(CFLAGS) $(XFLAGS) ..\sshrand.c @@ -1245,9 +1250,11 @@ uxucs.obj: ..\unix\uxucs.c ..\putty.h ..\charset\charset.h ..\terminal.h \ ..\sshsignals.h ..\tree234.h ..\puttymem.h \ ..\windows\winstuff.h ..\unix\unix.h ..\windows\winhelp.h lcc -O -p6 $(COMPAT) $(CFLAGS) $(XFLAGS) ..\unix\uxucs.c -uxutils.obj: ..\unix\uxutils.c ..\ssh.h ..\puttymem.h ..\tree234.h \ - ..\network.h ..\misc.h ..\sshttymodes.h ..\defs.h \ - ..\marshal.h +uxutils.obj: ..\unix\uxutils.c ..\putty.h ..\ssh.h ..\defs.h ..\puttyps.h \ + ..\network.h ..\misc.h ..\marshal.h ..\sshsignals.h \ + ..\puttymem.h ..\tree234.h ..\sshttymodes.h \ + ..\windows\winstuff.h ..\unix\unix.h ..\windows\winhelp.h \ + ..\charset\charset.h lcc -O -p6 $(COMPAT) $(CFLAGS) $(XFLAGS) ..\unix\uxutils.c version.obj: ..\version.c ..\empty.h ..\version.h lcc -O -p6 $(COMPAT) $(CFLAGS) $(XFLAGS) ..\version.c diff --git a/windows/Makefile.mgw b/windows/Makefile.mgw new file mode 100644 index 0000000..6a4ea71 --- /dev/null +++ b/windows/Makefile.mgw @@ -0,0 +1,1683 @@ +# Makefile for putty under MinGW, Cygwin, or Winelib. +# +# This file was created by `mkfiles.pl' from the `Recipe' file. +# DO NOT EDIT THIS FILE DIRECTLY; edit Recipe or mkfiles.pl instead. +# +# Extra options you can set: +# +# - COMPAT=-DAUTO_WINSOCK (Windows only) +# Causes PuTTY to assume that includes its own WinSock +# header file, so that it won't try to include . +# +# - COMPAT=-DWINSOCK_TWO (Windows only) +# Causes the PuTTY utilities to include instead of +# , except Plink which _needs_ WinSock 2 so it already +# does this. +# +# - COMPAT=-DNO_SECURITY (Windows only) +# Disables use of , which is not available with some +# development environments (such as very old versions of the +# mingw/Cygwin GNU toolchain). This has the following effects: +# - Pageant won't care about the local user ID of processes +# accessing it; a version of Pageant built with this option +# will therefore refuse to run under NT-series OSes on +# security grounds (although it will run fine on Win95-series +# OSes where there is no access control anyway). +# - SSH connection sharing is disabled. +# - There is no support for restriction of the process ACLs. +# +# - COMPAT=-DNO_MULTIMON (Windows only) +# Disables PuTTY's use of , which is not available +# with some development environments. This means that PuTTY's +# full-screen mode (configurable to work on Alt-Enter) will +# not behave usefully in a multi-monitor environment. +# +# - COMPAT=-DNO_HTMLHELP (Windows only) +# Disables PuTTY's use of , which is not available +# with some development environments. +# +# If you don't have this header, you may be able to use the copy +# supplied with HTML Help Workshop. +# +# - RCFL=-DNO_MANIFESTS (Windows only) +# Disables inclusion of XML application manifests in the PuTTY +# binaries. This may be necessary to build for 64-bit Windows; +# the manifests are only included to use the XP GUI style on +# Windows XP, and the architecture tags are a lie on 64-bit. +# +# - COMPAT=-DNO_IPV6 +# Disables PuTTY's ability to make IPv6 connections, enabling +# it to compile under development environments which do not +# support IPv6 in their header files. +# +# - COMPAT=-DNO_GSSAPI +# Disables PuTTY's ability to use GSSAPI functions for +# authentication and key exchange. +# +# - COMPAT=-DSTATIC_GSSAPI +# Causes PuTTY to try to link statically against the GSSAPI +# library instead of the default of doing it at run time. +# +# - COMPAT=-DMSVC4 (Windows only) +# - RCFL=-DMSVC4 +# Makes a couple of minor changes so that PuTTY compiles using +# MSVC 4. You will also need -DNO_SECURITY and -DNO_MULTIMON. +# +# - COMPAT=-DNO_SECUREZEROMEMORY (Windows only) +# Disables PuTTY's use of SecureZeroMemory(), which is missing +# from some environments' header files. +# +# - XFLAGS=-DTELNET_DEFAULT +# Causes PuTTY to default to the Telnet protocol (in the absence +# of Default Settings and so on to the contrary). Normally PuTTY +# will default to SSH. +# +# - XFLAGS=-DDEBUG +# Causes PuTTY to enable internal debugging. +# +# - XFLAGS=-DMALLOC_LOG +# Causes PuTTY to emit a file called putty_mem.log, logging every +# memory allocation and free, so you can track memory leaks. +# +# - XFLAGS=-DMINEFIELD (Windows only) +# Causes PuTTY to use a custom memory allocator, similar in +# concept to Electric Fence, in place of regular malloc(). Wastes +# huge amounts of RAM, but should cause heap-corruption bugs to +# show up as GPFs at the point of failure rather than appearing +# later on as second-level damage. +# +# - XFLAGS=-DFUZZING +# Builds a version of PuTTY with some tweaks to make fuzz testing +# easier: the SSH random number generator is replaced by one that +# always returns the same thing. Note that this makes SSH +# completely insecure -- a FUZZING build should never be used to +# connect to a real server. + +# You can define this path to point at your tools if you need to +# TOOLPATH = c:\cygwin\bin\ # or similar, if you're running Windows +# TOOLPATH = /pkg/mingw32msvc/i386-mingw32msvc/bin/ +# TOOLPATH = i686-w64-mingw32- +CC = $(TOOLPATH)gcc +RC = $(TOOLPATH)windres +# Uncomment the following two lines to compile under Winelib +# CC = winegcc +# RC = wrc +# You may also need to tell windres where to find include files: +# RCINC = --include-dir c:\cygwin\include\ + +CFLAGS = -Wall -O2 -std=gnu99 -Wvla -D_WINDOWS -DWIN32S_COMPAT \ + -D_NO_OLDNAMES -D__USE_MINGW_ANSI_STDIO=1 -I.././ \ + -I../charset/ -I../windows/ -I../unix/ +LDFLAGS = -s +RCFLAGS = $(RCINC) --define WIN32=1 --define _WIN32=1 --define WINVER=0x0400 \ + -I.././ -I../charset/ -I../windows/ -I../unix/ + +# _WIN32_IE is required to expose identifiers that only make sense on +# systems with IE5+ installed, such as some arguments to SHGetFolderPath(). +# WINVER etc perform a similar function for FlashWindowEx(). +CFLAGS += -D_WIN32_IE=0x0500 +CFLAGS += -DWINVER=0x0500 -D_WIN32_WINDOWS=0x0410 -D_WIN32_WINNT=0x0500 + +.SUFFIXES: + +all: pageant.exe plink.exe pscp.exe psftp.exe putty.exe puttygen.exe \ + puttytel.exe testcrypt.exe + +pageant.exe: aqsync.o conf.o ecc.o marshal.o memory.o misc.o mpint.o \ + pageant.o pageant.res.o sshaes.o sshauxcrypt.o sshdes.o \ + sshdss.o sshecc.o sshhmac.o sshmd5.o sshpubk.o sshrsa.o \ + sshsh256.o sshsh512.o sshsha.o stripctrl.o tree234.o utils.o \ + version.o wcwidth.o winhelp.o winmisc.o winmiscs.o winpgnt.o \ + winpgntc.o winsecur.o winutils.o + $(CC) -mwindows $(LDFLAGS) -o $@ -Wl,-Map,pageant.map aqsync.o \ + conf.o ecc.o marshal.o memory.o misc.o mpint.o pageant.o \ + pageant.res.o sshaes.o sshauxcrypt.o sshdes.o sshdss.o \ + sshecc.o sshhmac.o sshmd5.o sshpubk.o sshrsa.o sshsh256.o \ + sshsh512.o sshsha.o stripctrl.o tree234.o utils.o version.o \ + wcwidth.o winhelp.o winmisc.o winmiscs.o winpgnt.o \ + winpgntc.o winsecur.o winutils.o -ladvapi32 -lcomdlg32 \ + -lgdi32 -limm32 -lole32 -lshell32 -luser32 + +plink.exe: agentf.o aqsync.o be_all_s.o be_misc.o callback.o cmdline.o \ + conf.o cproxy.o ecc.o errsock.o ldisc.o logging.o mainchan.o \ + marshal.o memory.o misc.o miscucs.o mpint.o noterm.o \ + nullplug.o pgssapi.o pinger.o plink.res.o portfwd.o proxy.o \ + raw.o rlogin.o sessprep.o settings.o ssh.o ssh1bpp.o \ + ssh1censor.o ssh1connection.o ssh1connection-client.o \ + ssh1login.o ssh2bpp.o ssh2bpp-bare.o ssh2censor.o \ + ssh2connection.o ssh2connection-client.o ssh2kex-client.o \ + ssh2transhk.o ssh2transport.o ssh2userauth.o sshaes.o \ + ssharcf.o sshauxcrypt.o sshblowf.o sshccp.o sshcommon.o \ + sshcrc.o sshcrcda.o sshdes.o sshdh.o sshdss.o sshecc.o \ + sshgssc.o sshhmac.o sshmac.o sshmd5.o sshprng.o sshpubk.o \ + sshrand.o sshrsa.o sshsh256.o sshsh512.o sshsha.o sshshare.o \ + sshverstring.o sshzlib.o stripctrl.o telnet.o timing.o \ + tree234.o utils.o version.o wcwidth.o wildcard.o wincapi.o \ + wincons.o windefs.o wingss.o winhandl.o winhsock.o winmisc.o \ + winmiscs.o winnet.o winnohlp.o winnoise.o winnojmp.o \ + winnpc.o winnps.o winpgntc.o winplink.o winproxy.o \ + winsecur.o winser.o winshare.o winstore.o wintime.o winucs.o \ + winx11.o x11fwd.o + $(CC) $(LDFLAGS) -o $@ -Wl,-Map,plink.map agentf.o aqsync.o \ + be_all_s.o be_misc.o callback.o cmdline.o conf.o cproxy.o \ + ecc.o errsock.o ldisc.o logging.o mainchan.o marshal.o \ + memory.o misc.o miscucs.o mpint.o noterm.o nullplug.o \ + pgssapi.o pinger.o plink.res.o portfwd.o proxy.o raw.o \ + rlogin.o sessprep.o settings.o ssh.o ssh1bpp.o ssh1censor.o \ + ssh1connection.o ssh1connection-client.o ssh1login.o \ + ssh2bpp.o ssh2bpp-bare.o ssh2censor.o ssh2connection.o \ + ssh2connection-client.o ssh2kex-client.o ssh2transhk.o \ + ssh2transport.o ssh2userauth.o sshaes.o ssharcf.o \ + sshauxcrypt.o sshblowf.o sshccp.o sshcommon.o sshcrc.o \ + sshcrcda.o sshdes.o sshdh.o sshdss.o sshecc.o sshgssc.o \ + sshhmac.o sshmac.o sshmd5.o sshprng.o sshpubk.o sshrand.o \ + sshrsa.o sshsh256.o sshsh512.o sshsha.o sshshare.o \ + sshverstring.o sshzlib.o stripctrl.o telnet.o timing.o \ + tree234.o utils.o version.o wcwidth.o wildcard.o wincapi.o \ + wincons.o windefs.o wingss.o winhandl.o winhsock.o winmisc.o \ + winmiscs.o winnet.o winnohlp.o winnoise.o winnojmp.o \ + winnpc.o winnps.o winpgntc.o winplink.o winproxy.o \ + winsecur.o winser.o winshare.o winstore.o wintime.o winucs.o \ + winx11.o x11fwd.o -ladvapi32 -lcomdlg32 -lgdi32 -limm32 \ + -lole32 -lshell32 -luser32 + +pscp.exe: agentf.o aqsync.o be_misc.o be_ssh.o callback.o cmdline.o conf.o \ + cproxy.o ecc.o errsock.o logging.o mainchan.o marshal.o \ + memory.o misc.o miscucs.o mpint.o nullplug.o pgssapi.o \ + pinger.o portfwd.o proxy.o pscp.o pscp.res.o psftpcommon.o \ + settings.o sftp.o sftpcommon.o ssh.o ssh1bpp.o ssh1censor.o \ + ssh1connection.o ssh1connection-client.o ssh1login.o \ + ssh2bpp.o ssh2bpp-bare.o ssh2censor.o ssh2connection.o \ + ssh2connection-client.o ssh2kex-client.o ssh2transhk.o \ + ssh2transport.o ssh2userauth.o sshaes.o ssharcf.o \ + sshauxcrypt.o sshblowf.o sshccp.o sshcommon.o sshcrc.o \ + sshcrcda.o sshdes.o sshdh.o sshdss.o sshecc.o sshgssc.o \ + sshhmac.o sshmac.o sshmd5.o sshprng.o sshpubk.o sshrand.o \ + sshrsa.o sshsh256.o sshsh512.o sshsha.o sshshare.o \ + sshverstring.o sshzlib.o stripctrl.o timing.o tree234.o \ + utils.o version.o wcwidth.o wildcard.o wincapi.o wincons.o \ + windefs.o wingss.o winhandl.o winhsock.o winmisc.o \ + winmiscs.o winnet.o winnohlp.o winnoise.o winnojmp.o \ + winnpc.o winnps.o winpgntc.o winproxy.o winsecur.o winsftp.o \ + winshare.o winstore.o wintime.o winucs.o x11fwd.o + $(CC) $(LDFLAGS) -o $@ -Wl,-Map,pscp.map agentf.o aqsync.o be_misc.o \ + be_ssh.o callback.o cmdline.o conf.o cproxy.o ecc.o \ + errsock.o logging.o mainchan.o marshal.o memory.o misc.o \ + miscucs.o mpint.o nullplug.o pgssapi.o pinger.o portfwd.o \ + proxy.o pscp.o pscp.res.o psftpcommon.o settings.o sftp.o \ + sftpcommon.o ssh.o ssh1bpp.o ssh1censor.o ssh1connection.o \ + ssh1connection-client.o ssh1login.o ssh2bpp.o ssh2bpp-bare.o \ + ssh2censor.o ssh2connection.o ssh2connection-client.o \ + ssh2kex-client.o ssh2transhk.o ssh2transport.o \ + ssh2userauth.o sshaes.o ssharcf.o sshauxcrypt.o sshblowf.o \ + sshccp.o sshcommon.o sshcrc.o sshcrcda.o sshdes.o sshdh.o \ + sshdss.o sshecc.o sshgssc.o sshhmac.o sshmac.o sshmd5.o \ + sshprng.o sshpubk.o sshrand.o sshrsa.o sshsh256.o sshsh512.o \ + sshsha.o sshshare.o sshverstring.o sshzlib.o stripctrl.o \ + timing.o tree234.o utils.o version.o wcwidth.o wildcard.o \ + wincapi.o wincons.o windefs.o wingss.o winhandl.o winhsock.o \ + winmisc.o winmiscs.o winnet.o winnohlp.o winnoise.o \ + winnojmp.o winnpc.o winnps.o winpgntc.o winproxy.o \ + winsecur.o winsftp.o winshare.o winstore.o wintime.o \ + winucs.o x11fwd.o -ladvapi32 -lcomdlg32 -lgdi32 -limm32 \ + -lole32 -lshell32 -luser32 + +psftp.exe: agentf.o aqsync.o be_misc.o be_ssh.o callback.o cmdline.o conf.o \ + cproxy.o ecc.o errsock.o logging.o mainchan.o marshal.o \ + memory.o misc.o miscucs.o mpint.o nullplug.o pgssapi.o \ + pinger.o portfwd.o proxy.o psftp.o psftp.res.o psftpcommon.o \ + settings.o sftp.o sftpcommon.o ssh.o ssh1bpp.o ssh1censor.o \ + ssh1connection.o ssh1connection-client.o ssh1login.o \ + ssh2bpp.o ssh2bpp-bare.o ssh2censor.o ssh2connection.o \ + ssh2connection-client.o ssh2kex-client.o ssh2transhk.o \ + ssh2transport.o ssh2userauth.o sshaes.o ssharcf.o \ + sshauxcrypt.o sshblowf.o sshccp.o sshcommon.o sshcrc.o \ + sshcrcda.o sshdes.o sshdh.o sshdss.o sshecc.o sshgssc.o \ + sshhmac.o sshmac.o sshmd5.o sshprng.o sshpubk.o sshrand.o \ + sshrsa.o sshsh256.o sshsh512.o sshsha.o sshshare.o \ + sshverstring.o sshzlib.o stripctrl.o timing.o tree234.o \ + utils.o version.o wcwidth.o wildcard.o wincapi.o wincons.o \ + windefs.o wingss.o winhandl.o winhsock.o winmisc.o \ + winmiscs.o winnet.o winnohlp.o winnoise.o winnojmp.o \ + winnpc.o winnps.o winpgntc.o winproxy.o winsecur.o winsftp.o \ + winshare.o winstore.o wintime.o winucs.o x11fwd.o + $(CC) $(LDFLAGS) -o $@ -Wl,-Map,psftp.map agentf.o aqsync.o \ + be_misc.o be_ssh.o callback.o cmdline.o conf.o cproxy.o \ + ecc.o errsock.o logging.o mainchan.o marshal.o memory.o \ + misc.o miscucs.o mpint.o nullplug.o pgssapi.o pinger.o \ + portfwd.o proxy.o psftp.o psftp.res.o psftpcommon.o \ + settings.o sftp.o sftpcommon.o ssh.o ssh1bpp.o ssh1censor.o \ + ssh1connection.o ssh1connection-client.o ssh1login.o \ + ssh2bpp.o ssh2bpp-bare.o ssh2censor.o ssh2connection.o \ + ssh2connection-client.o ssh2kex-client.o ssh2transhk.o \ + ssh2transport.o ssh2userauth.o sshaes.o ssharcf.o \ + sshauxcrypt.o sshblowf.o sshccp.o sshcommon.o sshcrc.o \ + sshcrcda.o sshdes.o sshdh.o sshdss.o sshecc.o sshgssc.o \ + sshhmac.o sshmac.o sshmd5.o sshprng.o sshpubk.o sshrand.o \ + sshrsa.o sshsh256.o sshsh512.o sshsha.o sshshare.o \ + sshverstring.o sshzlib.o stripctrl.o timing.o tree234.o \ + utils.o version.o wcwidth.o wildcard.o wincapi.o wincons.o \ + windefs.o wingss.o winhandl.o winhsock.o winmisc.o \ + winmiscs.o winnet.o winnohlp.o winnoise.o winnojmp.o \ + winnpc.o winnps.o winpgntc.o winproxy.o winsecur.o winsftp.o \ + winshare.o winstore.o wintime.o winucs.o x11fwd.o -ladvapi32 \ + -lcomdlg32 -lgdi32 -limm32 -lole32 -lshell32 -luser32 + +putty.exe: agentf.o aqsync.o be_all_s.o be_misc.o callback.o cmdline.o \ + conf.o config.o cproxy.o dialog.o ecc.o errsock.o ldisc.o \ + logging.o mainchan.o marshal.o memory.o minibidi.o misc.o \ + miscucs.o mpint.o nullplug.o pgssapi.o pinger.o portfwd.o \ + proxy.o putty.res.o raw.o rlogin.o sercfg.o sessprep.o \ + settings.o sizetip.o ssh.o ssh1bpp.o ssh1censor.o \ + ssh1connection.o ssh1connection-client.o ssh1login.o \ + ssh2bpp.o ssh2bpp-bare.o ssh2censor.o ssh2connection.o \ + ssh2connection-client.o ssh2kex-client.o ssh2transhk.o \ + ssh2transport.o ssh2userauth.o sshaes.o ssharcf.o \ + sshauxcrypt.o sshblowf.o sshccp.o sshcommon.o sshcrc.o \ + sshcrcda.o sshdes.o sshdh.o sshdss.o sshecc.o sshgssc.o \ + sshhmac.o sshmac.o sshmd5.o sshprng.o sshpubk.o sshrand.o \ + sshrsa.o sshsh256.o sshsh512.o sshsha.o sshshare.o \ + sshverstring.o sshzlib.o stripctrl.o telnet.o terminal.o \ + timing.o tree234.o utils.o version.o wcwidth.o wildcard.o \ + wincapi.o wincfg.o winctrls.o windefs.o windlg.o window.o \ + wingss.o winhandl.o winhelp.o winhsock.o winjump.o winmisc.o \ + winmiscs.o winnet.o winnoise.o winnpc.o winnps.o winpgntc.o \ + winprint.o winproxy.o winsecur.o winser.o winshare.o \ + winstore.o wintime.o winucs.o winutils.o winx11.o x11fwd.o + $(CC) -mwindows $(LDFLAGS) -o $@ -Wl,-Map,putty.map agentf.o \ + aqsync.o be_all_s.o be_misc.o callback.o cmdline.o conf.o \ + config.o cproxy.o dialog.o ecc.o errsock.o ldisc.o logging.o \ + mainchan.o marshal.o memory.o minibidi.o misc.o miscucs.o \ + mpint.o nullplug.o pgssapi.o pinger.o portfwd.o proxy.o \ + putty.res.o raw.o rlogin.o sercfg.o sessprep.o settings.o \ + sizetip.o ssh.o ssh1bpp.o ssh1censor.o ssh1connection.o \ + ssh1connection-client.o ssh1login.o ssh2bpp.o ssh2bpp-bare.o \ + ssh2censor.o ssh2connection.o ssh2connection-client.o \ + ssh2kex-client.o ssh2transhk.o ssh2transport.o \ + ssh2userauth.o sshaes.o ssharcf.o sshauxcrypt.o sshblowf.o \ + sshccp.o sshcommon.o sshcrc.o sshcrcda.o sshdes.o sshdh.o \ + sshdss.o sshecc.o sshgssc.o sshhmac.o sshmac.o sshmd5.o \ + sshprng.o sshpubk.o sshrand.o sshrsa.o sshsh256.o sshsh512.o \ + sshsha.o sshshare.o sshverstring.o sshzlib.o stripctrl.o \ + telnet.o terminal.o timing.o tree234.o utils.o version.o \ + wcwidth.o wildcard.o wincapi.o wincfg.o winctrls.o windefs.o \ + windlg.o window.o wingss.o winhandl.o winhelp.o winhsock.o \ + winjump.o winmisc.o winmiscs.o winnet.o winnoise.o winnpc.o \ + winnps.o winpgntc.o winprint.o winproxy.o winsecur.o \ + winser.o winshare.o winstore.o wintime.o winucs.o winutils.o \ + winx11.o x11fwd.o -ladvapi32 -lcomdlg32 -lgdi32 -limm32 \ + -lole32 -lshell32 -luser32 + +puttygen.exe: conf.o ecc.o import.o marshal.o memory.o misc.o mpint.o \ + notiming.o puttygen.res.o sshaes.o sshauxcrypt.o sshbcrypt.o \ + sshblowf.o sshdes.o sshdss.o sshdssg.o sshecc.o sshecdsag.o \ + sshhmac.o sshmd5.o sshprime.o sshprng.o sshpubk.o sshrand.o \ + sshrsa.o sshrsag.o sshsh256.o sshsh512.o sshsha.o \ + stripctrl.o tree234.o utils.o version.o wcwidth.o winctrls.o \ + winhelp.o winmisc.o winmiscs.o winnoise.o winnojmp.o \ + winpgen.o winsecur.o winstore.o wintime.o winutils.o + $(CC) -mwindows $(LDFLAGS) -o $@ -Wl,-Map,puttygen.map conf.o ecc.o \ + import.o marshal.o memory.o misc.o mpint.o notiming.o \ + puttygen.res.o sshaes.o sshauxcrypt.o sshbcrypt.o sshblowf.o \ + sshdes.o sshdss.o sshdssg.o sshecc.o sshecdsag.o sshhmac.o \ + sshmd5.o sshprime.o sshprng.o sshpubk.o sshrand.o sshrsa.o \ + sshrsag.o sshsh256.o sshsh512.o sshsha.o stripctrl.o \ + tree234.o utils.o version.o wcwidth.o winctrls.o winhelp.o \ + winmisc.o winmiscs.o winnoise.o winnojmp.o winpgen.o \ + winsecur.o winstore.o wintime.o winutils.o -ladvapi32 \ + -lcomdlg32 -lgdi32 -limm32 -lole32 -lshell32 -luser32 + +puttytel.exe: be_misc.o be_nos_s.o callback.o cmdline.o conf.o config.o \ + dialog.o errsock.o ldisc.o logging.o marshal.o memory.o \ + minibidi.o misc.o miscucs.o nocproxy.o nogss.o pinger.o \ + proxy.o puttytel.res.o raw.o rlogin.o sercfg.o sessprep.o \ + settings.o sizetip.o stripctrl.o telnet.o terminal.o \ + timing.o tree234.o utils.o version.o wcwidth.o wincfg.o \ + winctrls.o windefs.o windlg.o window.o winhandl.o winhelp.o \ + winhsock.o winjump.o winmisc.o winmiscs.o winnet.o \ + winprint.o winproxy.o winsecur.o winser.o winstore.o \ + wintime.o winucs.o winutils.o + $(CC) -mwindows $(LDFLAGS) -o $@ -Wl,-Map,puttytel.map be_misc.o \ + be_nos_s.o callback.o cmdline.o conf.o config.o dialog.o \ + errsock.o ldisc.o logging.o marshal.o memory.o minibidi.o \ + misc.o miscucs.o nocproxy.o nogss.o pinger.o proxy.o \ + puttytel.res.o raw.o rlogin.o sercfg.o sessprep.o settings.o \ + sizetip.o stripctrl.o telnet.o terminal.o timing.o tree234.o \ + utils.o version.o wcwidth.o wincfg.o winctrls.o windefs.o \ + windlg.o window.o winhandl.o winhelp.o winhsock.o winjump.o \ + winmisc.o winmiscs.o winnet.o winprint.o winproxy.o \ + winsecur.o winser.o winstore.o wintime.o winucs.o winutils.o \ + -ladvapi32 -lcomdlg32 -lgdi32 -limm32 -lole32 -lshell32 \ + -luser32 + +testcrypt.exe: ecc.o marshal.o memory.o mpint.o sshaes.o ssharcf.o \ + sshauxcrypt.o sshblowf.o sshccp.o sshcrc.o sshcrcda.o \ + sshdes.o sshdh.o sshdss.o sshecc.o sshhmac.o sshmd5.o \ + sshprime.o sshprng.o sshrsa.o sshsh256.o sshsh512.o sshsha.o \ + testcrypt.o tree234.o utils.o winmiscs.o + $(CC) $(LDFLAGS) -o $@ -Wl,-Map,testcrypt.map ecc.o marshal.o \ + memory.o mpint.o sshaes.o ssharcf.o sshauxcrypt.o sshblowf.o \ + sshccp.o sshcrc.o sshcrcda.o sshdes.o sshdh.o sshdss.o \ + sshecc.o sshhmac.o sshmd5.o sshprime.o sshprng.o sshrsa.o \ + sshsh256.o sshsh512.o sshsha.o testcrypt.o tree234.o utils.o \ + winmiscs.o + +agentf.o: ../agentf.c ../putty.h ../ssh.h ../pageant.h ../sshchan.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../agentf.c + +aqsync.o: ../aqsync.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../aqsync.c + +be_all_s.o: ../be_all_s.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../be_all_s.c + +be_misc.o: ../be_misc.c ../putty.h ../network.h ../defs.h ../puttyps.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../be_misc.c + +be_none.o: ../be_none.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../be_none.c + +be_nos_s.o: ../be_nos_s.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../be_nos_s.c + +be_ssh.o: ../be_ssh.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../be_ssh.c + +callback.o: ../callback.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../callback.c + +cgtest.o: ../cgtest.c ../cmdgen.c ../putty.h ../ssh.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../cgtest.c + +cmdgen.o: ../cmdgen.c ../putty.h ../ssh.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../cmdgen.c + +cmdline.o: ../cmdline.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../cmdline.c + +conf.o: ../conf.c ../tree234.h ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../conf.c + +config.o: ../config.c ../putty.h ../dialog.h ../storage.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../config.c + +cproxy.o: ../cproxy.c ../putty.h ../ssh.h ../network.h ../proxy.h \ + ../marshal.h ../defs.h ../puttyps.h ../misc.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../cproxy.c + +dialog.o: ../dialog.c ../putty.h ../dialog.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../dialog.c + +ecc.o: ../ecc.c ../ssh.h ../mpint.h ../ecc.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ecc.c + +errsock.o: ../errsock.c ../tree234.h ../putty.h ../network.h ../defs.h \ + ../puttyps.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../errsock.c + +fromucs.o: ../charset/fromucs.c ../charset/charset.h ../charset/internal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../charset/fromucs.c + +fuzzterm.o: ../fuzzterm.c ../putty.h ../terminal.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../tree234.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../fuzzterm.c + +gtkapp.o: ../unix/gtkapp.c ../putty.h ../unix/gtkmisc.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/gtkapp.c + +gtkask.o: ../unix/gtkask.c ../defs.h ../unix/gtkfont.h ../unix/gtkcompat.h \ + ../unix/gtkmisc.h ../putty.h ../ssh.h ../misc.h ../puttyps.h \ + ../network.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/gtkask.c + +gtkcfg.o: ../unix/gtkcfg.c ../putty.h ../dialog.h ../storage.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/gtkcfg.c + +gtkcols.o: ../unix/gtkcols.c ../defs.h ../unix/gtkcompat.h ../unix/gtkcols.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/gtkcols.c + +gtkcomm.o: ../unix/gtkcomm.c ../putty.h ../terminal.h ../unix/gtkcompat.h \ + ../unix/gtkfont.h ../unix/gtkmisc.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../tree234.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/gtkcomm.c + +gtkdlg.o: ../unix/gtkdlg.c ../putty.h ../unix/gtkcompat.h ../unix/gtkcols.h \ + ../unix/gtkfont.h ../unix/gtkmisc.h ../unix/x11misc.h \ + ../storage.h ../dialog.h ../tree234.h ../licence.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/gtkdlg.c + +gtkfont.o: ../unix/gtkfont.c ../putty.h ../unix/gtkfont.h \ + ../unix/gtkcompat.h ../unix/gtkmisc.h ../tree234.h \ + ../unix/x11misc.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/gtkfont.c + +gtkmain.o: ../unix/gtkmain.c ../putty.h ../terminal.h ../unix/gtkcompat.h \ + ../unix/gtkfont.h ../unix/gtkmisc.h ../unix/x11misc.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../tree234.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/gtkmain.c + +gtkmisc.o: ../unix/gtkmisc.c ../putty.h ../unix/gtkcompat.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/gtkmisc.c + +gtkwin.o: ../unix/gtkwin.c ../putty.h ../terminal.h ../unix/gtkcompat.h \ + ../unix/gtkfont.h ../unix/gtkmisc.h ../unix/x11misc.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../tree234.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/gtkwin.c + +import.o: ../import.c ../putty.h ../ssh.h ../mpint.h ../misc.h ../defs.h \ + ../puttyps.h ../network.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../import.c + +ldisc.o: ../ldisc.c ../putty.h ../terminal.h ../ldisc.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../tree234.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ldisc.c + +localenc.o: ../charset/localenc.c ../charset/charset.h ../charset/internal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../charset/localenc.c + +logging.o: ../logging.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../logging.c + +macenc.o: ../charset/macenc.c ../charset/charset.h ../charset/internal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../charset/macenc.c + +mainchan.o: ../mainchan.c ../putty.h ../ssh.h ../sshppl.h ../sshchan.h \ + ../sshsignals.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../puttymem.h ../tree234.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../mainchan.c + +marshal.o: ../marshal.c ../marshal.h ../misc.h ../defs.h ../puttymem.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../marshal.c + +memory.o: ../memory.c ../defs.h ../puttymem.h ../misc.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../memory.c + +mimeenc.o: ../charset/mimeenc.c ../charset/charset.h ../charset/internal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../charset/mimeenc.c + +minibidi.o: ../minibidi.c ../putty.h ../misc.h ../defs.h ../puttyps.h \ + ../network.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../windows/winstuff.h ../unix/unix.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../minibidi.c + +misc.o: ../misc.c ../defs.h ../putty.h ../misc.h ../puttyps.h ../network.h \ + ../marshal.h ../sshsignals.h ../puttymem.h \ + ../windows/winstuff.h ../unix/unix.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../misc.c + +miscucs.o: ../miscucs.c ../putty.h ../misc.h ../defs.h ../puttyps.h \ + ../network.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../windows/winstuff.h ../unix/unix.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../miscucs.c + +mpint.o: ../mpint.c ../defs.h ../misc.h ../puttymem.h ../mpint.h \ + ../mpint_i.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../mpint.c + +nocmdline.o: ../nocmdline.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../nocmdline.c + +nocproxy.o: ../nocproxy.c ../putty.h ../network.h ../proxy.h ../defs.h \ + ../puttyps.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../nocproxy.c + +nogss.o: ../nogss.c ../putty.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../nogss.c + +noterm.o: ../noterm.c ../putty.h ../terminal.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../tree234.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../noterm.c + +notiming.o: ../notiming.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../notiming.c + +nullplug.o: ../nullplug.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../nullplug.c + +osxlaunch.o: ../unix/osxlaunch.c + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/osxlaunch.c + +pageant.o: ../pageant.c ../putty.h ../mpint.h ../ssh.h ../sshcr.h \ + ../pageant.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../pageant.c + +pageant.res.o: ../windows/pageant.rc ../windows/rcstuff.h \ + ../windows/winhelp.rc2 ../windows/pageant.ico \ + ../windows/pageants.ico ../windows/version.rc2 \ + ../windows/pageant.mft ../windows/win_res.h ../version.h \ + ../licence.h + $(RC) $(RCFL) $(RCFLAGS) ../windows/pageant.rc -o pageant.res.o + +pgssapi.o: ../pgssapi.c ../putty.h ../pgssapi.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../pgssapi.c + +pinger.o: ../pinger.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../pinger.c + +plink.res.o: ../windows/plink.rc ../windows/rcstuff.h ../windows/putty.ico \ + ../windows/version.rc2 ../version.h ../licence.h + $(RC) $(RCFL) $(RCFLAGS) ../windows/plink.rc -o plink.res.o + +portfwd.o: ../portfwd.c ../putty.h ../ssh.h ../sshchan.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../portfwd.c + +procnet.o: ../unix/procnet.c ../misc.h ../defs.h ../puttymem.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/procnet.c + +proxy.o: ../proxy.c ../putty.h ../network.h ../proxy.h ../defs.h \ + ../puttyps.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../proxy.c + +pscp.o: ../pscp.c ../putty.h ../psftp.h ../ssh.h ../sftp.h ../storage.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../pscp.c + +pscp.res.o: ../windows/pscp.rc ../windows/rcstuff.h ../windows/pscp.ico \ + ../windows/version.rc2 ../version.h ../licence.h + $(RC) $(RCFL) $(RCFLAGS) ../windows/pscp.rc -o pscp.res.o + +psftp.o: ../psftp.c ../putty.h ../psftp.h ../storage.h ../ssh.h ../sftp.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../psftp.c + +psftp.res.o: ../windows/psftp.rc ../windows/rcstuff.h ../windows/pscp.ico \ + ../windows/version.rc2 ../version.h ../licence.h + $(RC) $(RCFL) $(RCFLAGS) ../windows/psftp.rc -o psftp.res.o + +psftpcommon.o: ../psftpcommon.c ../putty.h ../sftp.h ../psftp.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../psftpcommon.c + +putty.res.o: ../windows/putty.rc ../windows/rcstuff.h ../windows/winhelp.rc2 \ + ../windows/win_res.rc2 ../windows/putty.mft \ + ../windows/win_res.h ../windows/putty.ico \ + ../windows/puttycfg.ico ../windows/version.rc2 ../version.h \ + ../licence.h + $(RC) $(RCFL) $(RCFLAGS) ../windows/putty.rc -o putty.res.o + +puttygen.res.o: ../windows/puttygen.rc ../windows/rcstuff.h \ + ../windows/winhelp.rc2 ../windows/puttygen.ico \ + ../windows/version.rc2 ../windows/puttygen.mft \ + ../windows/win_res.h ../version.h ../licence.h + $(RC) $(RCFL) $(RCFLAGS) ../windows/puttygen.rc -o puttygen.res.o + +puttytel.res.o: ../windows/puttytel.rc ../windows/rcstuff.h \ + ../windows/winhelp.rc2 ../windows/win_res.rc2 \ + ../windows/puttytel.mft ../windows/win_res.h \ + ../windows/putty.ico ../windows/puttycfg.ico \ + ../windows/version.rc2 ../version.h ../licence.h + $(RC) $(RCFL) $(RCFLAGS) ../windows/puttytel.rc -o puttytel.res.o + +raw.o: ../raw.c ../putty.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../raw.c + +rlogin.o: ../rlogin.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../rlogin.c + +sbcs.o: ../charset/sbcs.c ../charset/charset.h ../charset/internal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../charset/sbcs.c + +sbcsdat.o: ../charset/sbcsdat.c ../charset/charset.h ../charset/internal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../charset/sbcsdat.c + +scpserver.o: ../scpserver.c ../putty.h ../ssh.h ../sshcr.h ../sshchan.h \ + ../sftp.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../scpserver.c + +sercfg.o: ../sercfg.c ../putty.h ../dialog.h ../storage.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sercfg.c + +sesschan.o: ../sesschan.c ../putty.h ../ssh.h ../sshchan.h ../sshserver.h \ + ../sftp.h ../sshsignals.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sesschan.c + +sessprep.o: ../sessprep.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sessprep.c + +settings.o: ../settings.c ../putty.h ../storage.h ../sshgssc.h ../sshgss.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../pgssapi.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../settings.c + +sftp.o: ../sftp.c ../misc.h ../tree234.h ../sftp.h ../defs.h ../puttymem.h \ + ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sftp.c + +sftpcommon.o: ../sftpcommon.c ../misc.h ../sftp.h ../defs.h ../puttymem.h \ + ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sftpcommon.c + +sftpserver.o: ../sftpserver.c ../putty.h ../ssh.h ../sftp.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sftpserver.c + +sizetip.o: ../windows/sizetip.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/sizetip.c + +slookup.o: ../charset/slookup.c ../charset/charset.h ../charset/internal.h \ + ../charset/enum.c ../charset/sbcsdat.c ../charset/utf8.c + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../charset/slookup.c + +ssh.o: ../ssh.c ../putty.h ../pageant.h ../tree234.h ../storage.h \ + ../marshal.h ../ssh.h ../sshcr.h ../sshbpp.h ../sshppl.h \ + ../sshchan.h ../sshgssc.h ../sshgss.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../sshsignals.h ../puttymem.h \ + ../sshttymodes.h ../pgssapi.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh.c + +ssh1bpp.o: ../ssh1bpp.c ../putty.h ../ssh.h ../sshbpp.h ../sshcr.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh1bpp.c + +ssh1censor.o: ../ssh1censor.c ../putty.h ../ssh.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh1censor.c + +ssh1connection.o: ../ssh1connection.c ../putty.h ../ssh.h ../sshbpp.h \ + ../sshppl.h ../sshchan.h ../sshcr.h ../ssh1connection.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh1connection.c + +ssh1connection-client.o: ../ssh1connection-client.c ../putty.h ../ssh.h \ + ../sshbpp.h ../sshppl.h ../sshchan.h ../sshcr.h \ + ../ssh1connection.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh1connection-client.c + +ssh1connection-server.o: ../ssh1connection-server.c ../putty.h ../ssh.h \ + ../sshbpp.h ../sshppl.h ../sshchan.h ../sshcr.h \ + ../ssh1connection.h ../sshserver.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh1connection-server.c + +ssh1login.o: ../ssh1login.c ../putty.h ../ssh.h ../mpint.h ../sshbpp.h \ + ../sshppl.h ../sshcr.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh1login.c + +ssh1login-server.o: ../ssh1login-server.c ../putty.h ../mpint.h ../ssh.h \ + ../sshbpp.h ../sshppl.h ../sshcr.h ../sshserver.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh1login-server.c + +ssh2bpp.o: ../ssh2bpp.c ../putty.h ../ssh.h ../sshbpp.h ../sshcr.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2bpp.c + +ssh2bpp-bare.o: ../ssh2bpp-bare.c ../putty.h ../ssh.h ../sshbpp.h ../sshcr.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2bpp-bare.c + +ssh2censor.o: ../ssh2censor.c ../putty.h ../ssh.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2censor.c + +ssh2connection.o: ../ssh2connection.c ../putty.h ../ssh.h ../sshbpp.h \ + ../sshppl.h ../sshchan.h ../sshcr.h ../ssh2connection.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2connection.c + +ssh2connection-client.o: ../ssh2connection-client.c ../putty.h ../ssh.h \ + ../sshbpp.h ../sshppl.h ../sshchan.h ../sshcr.h \ + ../ssh2connection.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2connection-client.c + +ssh2connection-server.o: ../ssh2connection-server.c ../putty.h ../ssh.h \ + ../sshbpp.h ../sshppl.h ../sshchan.h ../sshcr.h \ + ../ssh2connection.h ../sshserver.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2connection-server.c + +ssh2kex-client.o: ../ssh2kex-client.c ../putty.h ../ssh.h ../sshbpp.h \ + ../sshppl.h ../sshcr.h ../storage.h ../ssh2transport.h \ + ../mpint.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ + ../sshttymodes.h ../sshgssc.h ../sshgss.h \ + ../windows/winstuff.h ../unix/unix.h ../pgssapi.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2kex-client.c + +ssh2kex-server.o: ../ssh2kex-server.c ../putty.h ../ssh.h ../sshbpp.h \ + ../sshppl.h ../sshcr.h ../sshserver.h ../storage.h \ + ../ssh2transport.h ../mpint.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h ../sshgssc.h \ + ../sshgss.h ../windows/winstuff.h ../unix/unix.h \ + ../pgssapi.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2kex-server.c + +ssh2transhk.o: ../ssh2transhk.c ../putty.h ../ssh.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2transhk.c + +ssh2transport.o: ../ssh2transport.c ../putty.h ../ssh.h ../sshbpp.h \ + ../sshppl.h ../sshcr.h ../sshserver.h ../storage.h \ + ../ssh2transport.h ../mpint.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h ../sshgssc.h \ + ../sshgss.h ../windows/winstuff.h ../unix/unix.h \ + ../pgssapi.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2transport.c + +ssh2userauth.o: ../ssh2userauth.c ../putty.h ../ssh.h ../sshbpp.h \ + ../sshppl.h ../sshcr.h ../sshgssc.h ../sshgss.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../pgssapi.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2userauth.c + +ssh2userauth-server.o: ../ssh2userauth-server.c ../putty.h ../ssh.h \ + ../sshbpp.h ../sshppl.h ../sshcr.h ../sshserver.h \ + ../sshgssc.h ../sshgss.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../pgssapi.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssh2userauth-server.c + +sshaes.o: ../sshaes.c ../ssh.h ../mpint_i.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshaes.c + +ssharcf.o: ../ssharcf.c ../ssh.h ../puttymem.h ../tree234.h ../network.h \ + ../misc.h ../sshttymodes.h ../defs.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../ssharcf.c + +sshauxcrypt.o: ../sshauxcrypt.c ../ssh.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshauxcrypt.c + +sshbcrypt.o: ../sshbcrypt.c ../ssh.h ../sshblowf.h ../puttymem.h \ + ../tree234.h ../network.h ../misc.h ../sshttymodes.h \ + ../defs.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshbcrypt.c + +sshblowf.o: ../sshblowf.c ../ssh.h ../sshblowf.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshblowf.c + +sshccp.o: ../sshccp.c ../ssh.h ../mpint_i.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshccp.c + +sshcommon.o: ../sshcommon.c ../putty.h ../mpint.h ../ssh.h ../sshbpp.h \ + ../sshppl.h ../sshchan.h ../sshttymodes.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshcommon.c + +sshcrc.o: ../sshcrc.c ../ssh.h ../puttymem.h ../tree234.h ../network.h \ + ../misc.h ../sshttymodes.h ../defs.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshcrc.c + +sshcrcda.o: ../sshcrcda.c ../misc.h ../ssh.h ../defs.h ../puttymem.h \ + ../marshal.h ../tree234.h ../network.h ../sshttymodes.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshcrcda.c + +sshdes.o: ../sshdes.c ../ssh.h ../mpint_i.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshdes.c + +sshdh.o: ../sshdh.c ../ssh.h ../misc.h ../mpint.h ../puttymem.h ../tree234.h \ + ../network.h ../sshttymodes.h ../defs.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshdh.c + +sshdss.o: ../sshdss.c ../ssh.h ../mpint.h ../misc.h ../puttymem.h \ + ../tree234.h ../network.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshdss.c + +sshdssg.o: ../sshdssg.c ../misc.h ../ssh.h ../mpint.h ../defs.h \ + ../puttymem.h ../marshal.h ../tree234.h ../network.h \ + ../sshttymodes.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshdssg.c + +sshecc.o: ../sshecc.c ../ssh.h ../mpint.h ../ecc.h ../puttymem.h \ + ../tree234.h ../network.h ../misc.h ../sshttymodes.h \ + ../defs.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshecc.c + +sshecdsag.o: ../sshecdsag.c ../ssh.h ../mpint.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshecdsag.c + +sshgssc.o: ../sshgssc.c ../putty.h ../sshgssc.h ../misc.h ../defs.h \ + ../puttyps.h ../network.h ../marshal.h ../sshsignals.h \ + ../pgssapi.h ../sshgss.h ../puttymem.h ../windows/winstuff.h \ + ../unix/unix.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshgssc.c + +sshhmac.o: ../sshhmac.c ../ssh.h ../puttymem.h ../tree234.h ../network.h \ + ../misc.h ../sshttymodes.h ../defs.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshhmac.c + +sshmac.o: ../sshmac.c ../ssh.h ../puttymem.h ../tree234.h ../network.h \ + ../misc.h ../sshttymodes.h ../defs.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshmac.c + +sshmd5.o: ../sshmd5.c ../ssh.h ../puttymem.h ../tree234.h ../network.h \ + ../misc.h ../sshttymodes.h ../defs.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshmd5.c + +sshprime.o: ../sshprime.c ../ssh.h ../mpint.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshprime.c + +sshprng.o: ../sshprng.c ../putty.h ../ssh.h ../mpint.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshprng.c + +sshpubk.o: ../sshpubk.c ../putty.h ../mpint.h ../ssh.h ../misc.h ../defs.h \ + ../puttyps.h ../network.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshpubk.c + +sshrand.o: ../sshrand.c ../putty.h ../ssh.h ../storage.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshrand.c + +sshrsa.o: ../sshrsa.c ../ssh.h ../mpint.h ../misc.h ../puttymem.h \ + ../tree234.h ../network.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshrsa.c + +sshrsag.o: ../sshrsag.c ../ssh.h ../mpint.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../defs.h \ + ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshrsag.c + +sshserver.o: ../sshserver.c ../putty.h ../ssh.h ../sshbpp.h ../sshppl.h \ + ../sshserver.h ../sshgssc.h ../sshgss.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../pgssapi.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshserver.c + +sshsh256.o: ../sshsh256.c ../ssh.h ../puttymem.h ../tree234.h ../network.h \ + ../misc.h ../sshttymodes.h ../defs.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshsh256.c + +sshsh512.o: ../sshsh512.c ../ssh.h ../puttymem.h ../tree234.h ../network.h \ + ../misc.h ../sshttymodes.h ../defs.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshsh512.c + +sshsha.o: ../sshsha.c ../ssh.h ../puttymem.h ../tree234.h ../network.h \ + ../misc.h ../sshttymodes.h ../defs.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshsha.c + +sshshare.o: ../sshshare.c ../putty.h ../tree234.h ../ssh.h ../sshcr.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshshare.c + +sshverstring.o: ../sshverstring.c ../putty.h ../ssh.h ../sshbpp.h ../sshcr.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshverstring.c + +sshzlib.o: ../sshzlib.c ../defs.h ../ssh.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../sshzlib.c + +stripctrl.o: ../stripctrl.c ../putty.h ../terminal.h ../misc.h ../marshal.h \ + ../defs.h ../puttyps.h ../network.h ../sshsignals.h \ + ../tree234.h ../puttymem.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../stripctrl.c + +telnet.o: ../telnet.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../telnet.c + +terminal.o: ../terminal.c ../putty.h ../terminal.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../tree234.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../terminal.c + +testcrypt.o: ../testcrypt.c ../defs.h ../ssh.h ../misc.h ../mpint.h ../ecc.h \ + ../testcrypt.h ../puttymem.h ../tree234.h ../network.h \ + ../sshttymodes.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../testcrypt.c + +testsc.o: ../testsc.c ../defs.h ../putty.h ../ssh.h ../misc.h ../mpint.h \ + ../ecc.h ../puttyps.h ../network.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../testsc.c + +testzlib.o: ../testzlib.c ../defs.h ../ssh.h ../puttymem.h ../tree234.h \ + ../network.h ../misc.h ../sshttymodes.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../testzlib.c + +time.o: ../time.c + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../time.c + +timing.o: ../timing.c ../putty.h ../tree234.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../timing.c + +toucs.o: ../charset/toucs.c ../charset/charset.h ../charset/internal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../charset/toucs.c + +tree234.o: ../tree234.c ../defs.h ../tree234.h ../puttymem.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../tree234.c + +utf8.o: ../charset/utf8.c ../charset/charset.h ../charset/internal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../charset/utf8.c + +utils.o: ../utils.c ../defs.h ../misc.h ../puttymem.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../utils.c + +ux_x11.o: ../unix/ux_x11.c ../putty.h ../ssh.h ../network.h ../defs.h \ + ../puttyps.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/ux_x11.c + +uxagentc.o: ../unix/uxagentc.c ../putty.h ../misc.h ../tree234.h \ + ../puttymem.h ../defs.h ../puttyps.h ../network.h \ + ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxagentc.c + +uxagentsock.o: ../unix/uxagentsock.c ../putty.h ../ssh.h ../misc.h \ + ../pageant.h ../defs.h ../puttyps.h ../network.h \ + ../marshal.h ../sshsignals.h ../puttymem.h ../tree234.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxagentsock.c + +uxcfg.o: ../unix/uxcfg.c ../putty.h ../dialog.h ../storage.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxcfg.c + +uxcons.o: ../unix/uxcons.c ../putty.h ../storage.h ../ssh.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxcons.c + +uxfdsock.o: ../unix/uxfdsock.c ../tree234.h ../putty.h ../network.h \ + ../defs.h ../puttyps.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxfdsock.c + +uxgen.o: ../unix/uxgen.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxgen.c + +uxgss.o: ../unix/uxgss.c ../putty.h ../pgssapi.h ../sshgss.h ../sshgssc.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxgss.c + +uxmisc.o: ../unix/uxmisc.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxmisc.c + +uxnet.o: ../unix/uxnet.c ../putty.h ../network.h ../tree234.h ../defs.h \ + ../puttyps.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxnet.c + +uxnogtk.o: ../unix/uxnogtk.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxnogtk.c + +uxnoise.o: ../unix/uxnoise.c ../putty.h ../ssh.h ../storage.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxnoise.c + +uxpeer.o: ../unix/uxpeer.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxpeer.c + +uxpgnt.o: ../unix/uxpgnt.c ../putty.h ../ssh.h ../misc.h ../pageant.h \ + ../defs.h ../puttyps.h ../network.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxpgnt.c + +uxplink.o: ../unix/uxplink.c ../putty.h ../storage.h ../tree234.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxplink.c + +uxpoll.o: ../unix/uxpoll.c ../putty.h ../tree234.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxpoll.c + +uxprint.o: ../unix/uxprint.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxprint.c + +uxproxy.o: ../unix/uxproxy.c ../tree234.h ../putty.h ../network.h ../proxy.h \ + ../defs.h ../puttyps.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxproxy.c + +uxpterm.o: ../unix/uxpterm.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxpterm.c + +uxpty.o: ../unix/uxpty.c ../putty.h ../ssh.h ../tree234.h ../sshttymodes.h \ + ../sshsignals.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../puttymem.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxpty.c + +uxputty.o: ../unix/uxputty.c ../putty.h ../storage.h ../unix/gtkcompat.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxputty.c + +uxsel.o: ../unix/uxsel.c ../putty.h ../tree234.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxsel.c + +uxser.o: ../unix/uxser.c ../putty.h ../tree234.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxser.c + +uxserver.o: ../unix/uxserver.c ../putty.h ../mpint.h ../ssh.h ../sshserver.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxserver.c + +uxsftp.o: ../unix/uxsftp.c ../putty.h ../ssh.h ../psftp.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxsftp.c + +uxsftpserver.o: ../unix/uxsftpserver.c ../putty.h ../ssh.h ../sftp.h \ + ../tree234.h ../defs.h ../puttyps.h ../network.h ../misc.h \ + ../marshal.h ../sshsignals.h ../puttymem.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxsftpserver.c + +uxshare.o: ../unix/uxshare.c ../tree234.h ../putty.h ../network.h ../proxy.h \ + ../ssh.h ../defs.h ../puttyps.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxshare.c + +uxsignal.o: ../unix/uxsignal.c ../defs.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxsignal.c + +uxstore.o: ../unix/uxstore.c ../putty.h ../storage.h ../tree234.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxstore.c + +uxucs.o: ../unix/uxucs.c ../putty.h ../charset/charset.h ../terminal.h \ + ../misc.h ../defs.h ../puttyps.h ../network.h ../marshal.h \ + ../sshsignals.h ../tree234.h ../puttymem.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxucs.c + +uxutils.o: ../unix/uxutils.c ../putty.h ../ssh.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/uxutils.c + +version.o: ../version.c ../empty.h ../version.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../version.c + +wcwidth.o: ../wcwidth.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../wcwidth.c + +wildcard.o: ../wildcard.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../wildcard.c + +wincapi.o: ../windows/wincapi.c ../putty.h ../windows/wincapi.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/wincapi.c + +wincfg.o: ../windows/wincfg.c ../putty.h ../dialog.h ../storage.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/wincfg.c + +wincons.o: ../windows/wincons.c ../putty.h ../storage.h ../ssh.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/wincons.c + +winctrls.o: ../windows/winctrls.c ../putty.h ../misc.h ../dialog.h ../defs.h \ + ../puttyps.h ../network.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../windows/winstuff.h ../unix/unix.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winctrls.c + +windefs.o: ../windows/windefs.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/windefs.c + +windlg.o: ../windows/windlg.c ../putty.h ../ssh.h ../windows/win_res.h \ + ../storage.h ../dialog.h ../licence.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/windlg.c + +window.o: ../windows/window.c ../putty.h ../terminal.h ../storage.h \ + ../windows/win_res.h ../windows/winsecur.h ../tree234.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/window.c + +wingss.o: ../windows/wingss.c ../putty.h ../pgssapi.h ../sshgss.h \ + ../sshgssc.h ../misc.h ../defs.h ../puttyps.h ../network.h \ + ../marshal.h ../sshsignals.h ../puttymem.h \ + ../windows/winstuff.h ../unix/unix.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/wingss.c + +winhandl.o: ../windows/winhandl.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winhandl.c + +winhelp.o: ../windows/winhelp.c ../putty.h ../windows/win_res.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winhelp.c + +winhsock.o: ../windows/winhsock.c ../tree234.h ../putty.h ../network.h \ + ../defs.h ../puttyps.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winhsock.c + +winjump.o: ../windows/winjump.c ../putty.h ../storage.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winjump.c + +winmisc.o: ../windows/winmisc.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winmisc.c + +winmiscs.o: ../windows/winmiscs.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winmiscs.c + +winnet.o: ../windows/winnet.c ../putty.h ../network.h ../tree234.h ../defs.h \ + ../puttyps.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winnet.c + +winnohlp.o: ../windows/winnohlp.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winnohlp.c + +winnoise.o: ../windows/winnoise.c ../putty.h ../ssh.h ../storage.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winnoise.c + +winnojmp.o: ../windows/winnojmp.c + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winnojmp.c + +winnpc.o: ../windows/winnpc.c ../tree234.h ../putty.h ../network.h \ + ../proxy.h ../ssh.h ../windows/winsecur.h ../defs.h \ + ../puttyps.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winnpc.c + +winnps.o: ../windows/winnps.c ../tree234.h ../putty.h ../network.h \ + ../proxy.h ../ssh.h ../windows/winsecur.h ../defs.h \ + ../puttyps.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winnps.c + +winpgen.o: ../windows/winpgen.c ../putty.h ../ssh.h ../licence.h \ + ../windows/winsecur.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winpgen.c + +winpgnt.o: ../windows/winpgnt.c ../putty.h ../ssh.h ../misc.h ../tree234.h \ + ../windows/winsecur.h ../pageant.h ../licence.h ../defs.h \ + ../puttyps.h ../network.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winpgnt.c + +winpgntc.o: ../windows/winpgntc.c ../putty.h ../pageant.h \ + ../windows/winsecur.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winpgntc.c + +winplink.o: ../windows/winplink.c ../putty.h ../storage.h ../tree234.h \ + ../windows/winsecur.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winplink.c + +winprint.o: ../windows/winprint.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winprint.c + +winproxy.o: ../windows/winproxy.c ../tree234.h ../putty.h ../network.h \ + ../proxy.h ../defs.h ../puttyps.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winproxy.c + +winsecur.o: ../windows/winsecur.c ../putty.h ../windows/winsecur.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winsecur.c + +winser.o: ../windows/winser.c ../putty.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../windows/winstuff.h \ + ../unix/unix.h ../puttymem.h ../tree234.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winser.c + +winsftp.o: ../windows/winsftp.c ../putty.h ../psftp.h ../ssh.h \ + ../windows/winsecur.h ../defs.h ../puttyps.h ../network.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../tree234.h ../sshttymodes.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winsftp.c + +winshare.o: ../windows/winshare.c ../tree234.h ../putty.h ../network.h \ + ../proxy.h ../ssh.h ../windows/wincapi.h \ + ../windows/winsecur.h ../noshare.c ../defs.h ../puttyps.h \ + ../misc.h ../marshal.h ../sshsignals.h ../puttymem.h \ + ../sshttymodes.h ../windows/winstuff.h ../unix/unix.h \ + ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winshare.c + +winstore.o: ../windows/winstore.c ../putty.h ../storage.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winstore.c + +wintime.o: ../windows/wintime.c ../putty.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../windows/winstuff.h ../unix/unix.h ../puttymem.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/wintime.c + +winucs.o: ../windows/winucs.c ../putty.h ../terminal.h ../misc.h ../defs.h \ + ../puttyps.h ../network.h ../marshal.h ../sshsignals.h \ + ../tree234.h ../puttymem.h ../windows/winstuff.h \ + ../unix/unix.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winucs.c + +winutils.o: ../windows/winutils.c ../putty.h ../misc.h ../defs.h \ + ../puttyps.h ../network.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../windows/winstuff.h ../unix/unix.h \ + ../tree234.h ../windows/winhelp.h ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winutils.c + +winx11.o: ../windows/winx11.c ../putty.h ../ssh.h ../defs.h ../puttyps.h \ + ../network.h ../misc.h ../marshal.h ../sshsignals.h \ + ../puttymem.h ../tree234.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../windows/winx11.c + +x11fwd.o: ../x11fwd.c ../putty.h ../ssh.h ../sshchan.h ../tree234.h \ + ../defs.h ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../puttymem.h ../sshttymodes.h \ + ../windows/winstuff.h ../unix/unix.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../x11fwd.c + +x11misc.o: ../unix/x11misc.c ../putty.h ../unix/x11misc.h ../defs.h \ + ../puttyps.h ../network.h ../misc.h ../marshal.h \ + ../sshsignals.h ../windows/winstuff.h ../unix/unix.h \ + ../puttymem.h ../tree234.h ../windows/winhelp.h \ + ../charset/charset.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/x11misc.c + +xenc.o: ../charset/xenc.c ../charset/charset.h ../charset/internal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../charset/xenc.c + +xkeysym.o: ../unix/xkeysym.c ../misc.h ../defs.h ../puttymem.h ../marshal.h + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/xkeysym.c + +xpmptcfg.o: ../unix/xpmptcfg.c + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/xpmptcfg.c + +xpmpterm.o: ../unix/xpmpterm.c + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/xpmpterm.c + +xpmpucfg.o: ../unix/xpmpucfg.c + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/xpmpucfg.c + +xpmputty.o: ../unix/xpmputty.c + $(CC) $(COMPAT) $(CFLAGS) $(XFLAGS) -c ../unix/xpmputty.c + + + +clean: + rm -f *.o *.exe *.res.o *.so *.map + +FORCE: diff --git a/windows/Makefile.vc b/windows/Makefile.vc index d07788c..c2049f6 100644 --- a/windows/Makefile.vc +++ b/windows/Makefile.vc @@ -252,10 +252,10 @@ $(BUILDDIR)pscp.exe: $(BUILDDIR)agentf.obj $(BUILDDIR)aqsync.obj \ $(BUILDDIR)nullplug.obj $(BUILDDIR)pgssapi.obj \ $(BUILDDIR)pinger.obj $(BUILDDIR)portfwd.obj \ $(BUILDDIR)proxy.obj $(BUILDDIR)pscp.obj $(BUILDDIR)pscp.res \ - $(BUILDDIR)settings.obj $(BUILDDIR)sftp.obj \ - $(BUILDDIR)sftpcommon.obj $(BUILDDIR)ssh.obj \ - $(BUILDDIR)ssh1bpp.obj $(BUILDDIR)ssh1censor.obj \ - $(BUILDDIR)ssh1connection.obj \ + $(BUILDDIR)psftpcommon.obj $(BUILDDIR)settings.obj \ + $(BUILDDIR)sftp.obj $(BUILDDIR)sftpcommon.obj \ + $(BUILDDIR)ssh.obj $(BUILDDIR)ssh1bpp.obj \ + $(BUILDDIR)ssh1censor.obj $(BUILDDIR)ssh1connection.obj \ $(BUILDDIR)ssh1connection-client.obj \ $(BUILDDIR)ssh1login.obj $(BUILDDIR)ssh2bpp.obj \ $(BUILDDIR)ssh2bpp-bare.obj $(BUILDDIR)ssh2censor.obj \ @@ -301,9 +301,9 @@ $(BUILDDIR)pscp.exe: $(BUILDDIR)agentf.obj $(BUILDDIR)aqsync.obj \ $(BUILDDIR)miscucs.obj $(BUILDDIR)mpint.obj $(BUILDDIR)nullplug.obj ole32.lib $(BUILDDIR)pgssapi.obj $(BUILDDIR)pinger.obj $(BUILDDIR)portfwd.obj $(BUILDDIR)proxy.obj $(BUILDDIR)pscp.obj - $(BUILDDIR)pscp.res $(BUILDDIR)settings.obj $(BUILDDIR)sftp.obj - $(BUILDDIR)sftpcommon.obj shell32.lib $(BUILDDIR)ssh.obj - $(BUILDDIR)ssh1bpp.obj $(BUILDDIR)ssh1censor.obj + $(BUILDDIR)pscp.res $(BUILDDIR)psftpcommon.obj $(BUILDDIR)settings.obj + $(BUILDDIR)sftp.obj $(BUILDDIR)sftpcommon.obj shell32.lib + $(BUILDDIR)ssh.obj $(BUILDDIR)ssh1bpp.obj $(BUILDDIR)ssh1censor.obj $(BUILDDIR)ssh1connection.obj $(BUILDDIR)ssh1connection-client.obj $(BUILDDIR)ssh1login.obj $(BUILDDIR)ssh2bpp.obj $(BUILDDIR)ssh2bpp-bare.obj $(BUILDDIR)ssh2censor.obj @@ -344,10 +344,11 @@ $(BUILDDIR)psftp.exe: $(BUILDDIR)agentf.obj $(BUILDDIR)aqsync.obj \ $(BUILDDIR)nullplug.obj $(BUILDDIR)pgssapi.obj \ $(BUILDDIR)pinger.obj $(BUILDDIR)portfwd.obj \ $(BUILDDIR)proxy.obj $(BUILDDIR)psftp.obj \ - $(BUILDDIR)psftp.res $(BUILDDIR)settings.obj \ - $(BUILDDIR)sftp.obj $(BUILDDIR)sftpcommon.obj \ - $(BUILDDIR)ssh.obj $(BUILDDIR)ssh1bpp.obj \ - $(BUILDDIR)ssh1censor.obj $(BUILDDIR)ssh1connection.obj \ + $(BUILDDIR)psftp.res $(BUILDDIR)psftpcommon.obj \ + $(BUILDDIR)settings.obj $(BUILDDIR)sftp.obj \ + $(BUILDDIR)sftpcommon.obj $(BUILDDIR)ssh.obj \ + $(BUILDDIR)ssh1bpp.obj $(BUILDDIR)ssh1censor.obj \ + $(BUILDDIR)ssh1connection.obj \ $(BUILDDIR)ssh1connection-client.obj \ $(BUILDDIR)ssh1login.obj $(BUILDDIR)ssh2bpp.obj \ $(BUILDDIR)ssh2bpp-bare.obj $(BUILDDIR)ssh2censor.obj \ @@ -393,9 +394,9 @@ $(BUILDDIR)psftp.exe: $(BUILDDIR)agentf.obj $(BUILDDIR)aqsync.obj \ $(BUILDDIR)miscucs.obj $(BUILDDIR)mpint.obj $(BUILDDIR)nullplug.obj ole32.lib $(BUILDDIR)pgssapi.obj $(BUILDDIR)pinger.obj $(BUILDDIR)portfwd.obj $(BUILDDIR)proxy.obj $(BUILDDIR)psftp.obj - $(BUILDDIR)psftp.res $(BUILDDIR)settings.obj $(BUILDDIR)sftp.obj - $(BUILDDIR)sftpcommon.obj shell32.lib $(BUILDDIR)ssh.obj - $(BUILDDIR)ssh1bpp.obj $(BUILDDIR)ssh1censor.obj + $(BUILDDIR)psftp.res $(BUILDDIR)psftpcommon.obj $(BUILDDIR)settings.obj + $(BUILDDIR)sftp.obj $(BUILDDIR)sftpcommon.obj shell32.lib + $(BUILDDIR)ssh.obj $(BUILDDIR)ssh1bpp.obj $(BUILDDIR)ssh1censor.obj $(BUILDDIR)ssh1connection.obj $(BUILDDIR)ssh1connection-client.obj $(BUILDDIR)ssh1login.obj $(BUILDDIR)ssh2bpp.obj $(BUILDDIR)ssh2bpp-bare.obj $(BUILDDIR)ssh2censor.obj @@ -431,14 +432,14 @@ $(BUILDDIR)putty.exe: $(BUILDDIR)agentf.obj $(BUILDDIR)aqsync.obj \ $(BUILDDIR)conf.obj $(BUILDDIR)config.obj \ $(BUILDDIR)cproxy.obj $(BUILDDIR)dialog.obj \ $(BUILDDIR)ecc.obj $(BUILDDIR)errsock.obj \ - $(BUILDDIR)ldisc.obj $(BUILDDIR)ldiscucs.obj \ - $(BUILDDIR)logging.obj $(BUILDDIR)mainchan.obj \ - $(BUILDDIR)marshal.obj $(BUILDDIR)memory.obj \ - $(BUILDDIR)minibidi.obj $(BUILDDIR)misc.obj \ - $(BUILDDIR)miscucs.obj $(BUILDDIR)mpint.obj \ - $(BUILDDIR)nullplug.obj $(BUILDDIR)pgssapi.obj \ - $(BUILDDIR)pinger.obj $(BUILDDIR)portfwd.obj \ - $(BUILDDIR)proxy.obj $(BUILDDIR)putty.res $(BUILDDIR)raw.obj \ + $(BUILDDIR)ldisc.obj $(BUILDDIR)logging.obj \ + $(BUILDDIR)mainchan.obj $(BUILDDIR)marshal.obj \ + $(BUILDDIR)memory.obj $(BUILDDIR)minibidi.obj \ + $(BUILDDIR)misc.obj $(BUILDDIR)miscucs.obj \ + $(BUILDDIR)mpint.obj $(BUILDDIR)nullplug.obj \ + $(BUILDDIR)pgssapi.obj $(BUILDDIR)pinger.obj \ + $(BUILDDIR)portfwd.obj $(BUILDDIR)proxy.obj \ + $(BUILDDIR)putty.res $(BUILDDIR)raw.obj \ $(BUILDDIR)rlogin.obj $(BUILDDIR)sercfg.obj \ $(BUILDDIR)sessprep.obj $(BUILDDIR)settings.obj \ $(BUILDDIR)sizetip.obj $(BUILDDIR)ssh.obj \ @@ -489,15 +490,15 @@ $(BUILDDIR)putty.exe: $(BUILDDIR)agentf.obj $(BUILDDIR)aqsync.obj \ $(BUILDDIR)cmdline.obj comdlg32.lib $(BUILDDIR)conf.obj $(BUILDDIR)config.obj $(BUILDDIR)cproxy.obj $(BUILDDIR)dialog.obj $(BUILDDIR)ecc.obj $(BUILDDIR)errsock.obj gdi32.lib imm32.lib - $(BUILDDIR)ldisc.obj $(BUILDDIR)ldiscucs.obj $(BUILDDIR)logging.obj - $(BUILDDIR)mainchan.obj $(BUILDDIR)marshal.obj $(BUILDDIR)memory.obj - $(BUILDDIR)minibidi.obj $(BUILDDIR)misc.obj $(BUILDDIR)miscucs.obj - $(BUILDDIR)mpint.obj $(BUILDDIR)nullplug.obj ole32.lib - $(BUILDDIR)pgssapi.obj $(BUILDDIR)pinger.obj $(BUILDDIR)portfwd.obj - $(BUILDDIR)proxy.obj $(BUILDDIR)putty.res $(BUILDDIR)raw.obj - $(BUILDDIR)rlogin.obj $(BUILDDIR)sercfg.obj $(BUILDDIR)sessprep.obj - $(BUILDDIR)settings.obj shell32.lib $(BUILDDIR)sizetip.obj - $(BUILDDIR)ssh.obj $(BUILDDIR)ssh1bpp.obj $(BUILDDIR)ssh1censor.obj + $(BUILDDIR)ldisc.obj $(BUILDDIR)logging.obj $(BUILDDIR)mainchan.obj + $(BUILDDIR)marshal.obj $(BUILDDIR)memory.obj $(BUILDDIR)minibidi.obj + $(BUILDDIR)misc.obj $(BUILDDIR)miscucs.obj $(BUILDDIR)mpint.obj + $(BUILDDIR)nullplug.obj ole32.lib $(BUILDDIR)pgssapi.obj + $(BUILDDIR)pinger.obj $(BUILDDIR)portfwd.obj $(BUILDDIR)proxy.obj + $(BUILDDIR)putty.res $(BUILDDIR)raw.obj $(BUILDDIR)rlogin.obj + $(BUILDDIR)sercfg.obj $(BUILDDIR)sessprep.obj $(BUILDDIR)settings.obj + shell32.lib $(BUILDDIR)sizetip.obj $(BUILDDIR)ssh.obj + $(BUILDDIR)ssh1bpp.obj $(BUILDDIR)ssh1censor.obj $(BUILDDIR)ssh1connection.obj $(BUILDDIR)ssh1connection-client.obj $(BUILDDIR)ssh1login.obj $(BUILDDIR)ssh2bpp.obj $(BUILDDIR)ssh2bpp-bare.obj $(BUILDDIR)ssh2censor.obj @@ -577,52 +578,50 @@ $(BUILDDIR)puttytel.exe: $(BUILDDIR)be_misc.obj $(BUILDDIR)be_nos_s.obj \ $(BUILDDIR)callback.obj $(BUILDDIR)cmdline.obj \ $(BUILDDIR)conf.obj $(BUILDDIR)config.obj \ $(BUILDDIR)dialog.obj $(BUILDDIR)errsock.obj \ - $(BUILDDIR)ldisc.obj $(BUILDDIR)ldiscucs.obj \ - $(BUILDDIR)logging.obj $(BUILDDIR)marshal.obj \ - $(BUILDDIR)memory.obj $(BUILDDIR)minibidi.obj \ - $(BUILDDIR)misc.obj $(BUILDDIR)miscucs.obj \ - $(BUILDDIR)nocproxy.obj $(BUILDDIR)nogss.obj \ - $(BUILDDIR)pinger.obj $(BUILDDIR)proxy.obj \ - $(BUILDDIR)puttytel.res $(BUILDDIR)raw.obj \ - $(BUILDDIR)rlogin.obj $(BUILDDIR)sercfg.obj \ - $(BUILDDIR)sessprep.obj $(BUILDDIR)settings.obj \ - $(BUILDDIR)sizetip.obj $(BUILDDIR)stripctrl.obj \ - $(BUILDDIR)telnet.obj $(BUILDDIR)terminal.obj \ - $(BUILDDIR)timing.obj $(BUILDDIR)tree234.obj \ - $(BUILDDIR)utils.obj $(BUILDDIR)version.obj \ - $(BUILDDIR)wcwidth.obj $(BUILDDIR)wincfg.obj \ - $(BUILDDIR)winctrls.obj $(BUILDDIR)windefs.obj \ - $(BUILDDIR)windlg.obj $(BUILDDIR)window.obj \ - $(BUILDDIR)winhandl.obj $(BUILDDIR)winhelp.obj \ - $(BUILDDIR)winhsock.obj $(BUILDDIR)winjump.obj \ - $(BUILDDIR)winmisc.obj $(BUILDDIR)winmiscs.obj \ - $(BUILDDIR)winnet.obj $(BUILDDIR)winprint.obj \ - $(BUILDDIR)winproxy.obj $(BUILDDIR)winsecur.obj \ - $(BUILDDIR)winser.obj $(BUILDDIR)winstore.obj \ - $(BUILDDIR)wintime.obj $(BUILDDIR)winucs.obj \ - $(BUILDDIR)winutils.obj + $(BUILDDIR)ldisc.obj $(BUILDDIR)logging.obj \ + $(BUILDDIR)marshal.obj $(BUILDDIR)memory.obj \ + $(BUILDDIR)minibidi.obj $(BUILDDIR)misc.obj \ + $(BUILDDIR)miscucs.obj $(BUILDDIR)nocproxy.obj \ + $(BUILDDIR)nogss.obj $(BUILDDIR)pinger.obj \ + $(BUILDDIR)proxy.obj $(BUILDDIR)puttytel.res \ + $(BUILDDIR)raw.obj $(BUILDDIR)rlogin.obj \ + $(BUILDDIR)sercfg.obj $(BUILDDIR)sessprep.obj \ + $(BUILDDIR)settings.obj $(BUILDDIR)sizetip.obj \ + $(BUILDDIR)stripctrl.obj $(BUILDDIR)telnet.obj \ + $(BUILDDIR)terminal.obj $(BUILDDIR)timing.obj \ + $(BUILDDIR)tree234.obj $(BUILDDIR)utils.obj \ + $(BUILDDIR)version.obj $(BUILDDIR)wcwidth.obj \ + $(BUILDDIR)wincfg.obj $(BUILDDIR)winctrls.obj \ + $(BUILDDIR)windefs.obj $(BUILDDIR)windlg.obj \ + $(BUILDDIR)window.obj $(BUILDDIR)winhandl.obj \ + $(BUILDDIR)winhelp.obj $(BUILDDIR)winhsock.obj \ + $(BUILDDIR)winjump.obj $(BUILDDIR)winmisc.obj \ + $(BUILDDIR)winmiscs.obj $(BUILDDIR)winnet.obj \ + $(BUILDDIR)winprint.obj $(BUILDDIR)winproxy.obj \ + $(BUILDDIR)winsecur.obj $(BUILDDIR)winser.obj \ + $(BUILDDIR)winstore.obj $(BUILDDIR)wintime.obj \ + $(BUILDDIR)winucs.obj $(BUILDDIR)winutils.obj type < System and Security > System > Advanced system -settings > Environment Variables. - -Some versions of Windows will refuse to run HTML Help files (.CHM) -if they are installed on a network drive. If you have installed -PuTTY on a network drive, you might want to check that the help file -works properly. If not, see http://support.microsoft.com/kb/896054 -for information on how to solve this problem. - -What do I do if it doesn't work? --------------------------------- - -The PuTTY home web site is - - https://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'. diff --git a/windows/VS2010/pageant/pageant.vcxproj b/windows/VS2010/pageant/pageant.vcxproj new file mode 100644 index 0000000..6c7650c --- /dev/null +++ b/windows/VS2010/pageant/pageant.vcxproj @@ -0,0 +1,204 @@ + + + + + Debug + Win32 + + + Release + Win32 + + + + + + {27e8f930-2567-4fdc-82c1-0662af3cdf6d} + + + + Application + false + MultiByte + v100 + + + Application + false + MultiByte + v100 + + + + + + + + + + + + + .\Release\ + .\Release\ + false + + + .\Debug\ + .\Debug\ + true + + + + MultiThreaded + OnlyExplicitInline + true + true + MaxSpeed + true + Level3 + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;NDEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Release\ + .\Release\pageant.pch + .\Release\ + .\Release\ + + + true + NDEBUG;%(PreprocessorDefinitions) + .\Release\pageant.tlb + true + Win32 + + + 0x0809 + NDEBUG;%(PreprocessorDefinitions) + + + true + .\Release\pageant.bsc + + + true + Windows + .\Release\pageant.exe + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + MultiThreadedDebug + Default + false + Disabled + true + Level3 + true + ProgramDatabase + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;_DEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Debug\ + .\Debug\pageant.pch + .\Debug\ + .\Debug\ + EnableFastChecks + + + true + _DEBUG;%(PreprocessorDefinitions) + .\Debug\pageant.tlb + true + Win32 + + + 0x0809 + _DEBUG;%(PreprocessorDefinitions) + + + true + .\Debug\pageant.bsc + + + true + true + Windows + $(TargetPath) + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + + + + + ..\..;%(AdditionalIncludeDirectories) + ..\..;%(AdditionalIncludeDirectories) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/windows/VS2010/pageant/pageant.vcxproj.filters b/windows/VS2010/pageant/pageant.vcxproj.filters new file mode 100644 index 0000000..cf8e1ad --- /dev/null +++ b/windows/VS2010/pageant/pageant.vcxproj.filters @@ -0,0 +1,149 @@ + + + + + Resource Files + + + Resource Files + + + + + Resource Files + + + + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + + + {700cfdc0-1885-4a48-9760-6fd8f3f62b09} + + + {25d39962-0c67-4b83-a85f-ca32bded1354} + + + {f84c3ab7-54fe-48c4-be65-5115ae325892} + + + \ No newline at end of file diff --git a/windows/VS2010/plink/plink.vcxproj b/windows/VS2010/plink/plink.vcxproj new file mode 100644 index 0000000..36897fd --- /dev/null +++ b/windows/VS2010/plink/plink.vcxproj @@ -0,0 +1,288 @@ + + + + + Debug + Win32 + + + Release + Win32 + + + + + + {4478087b-1dc8-4c3e-b624-13661de1947e} + + + + Application + false + MultiByte + v100 + + + Application + false + MultiByte + v100 + + + + + + + + + + + + + .\Release\ + .\Release\ + false + + + .\Debug\ + .\Debug\ + true + + + + MultiThreaded + OnlyExplicitInline + true + true + MaxSpeed + true + Level3 + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;NDEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Release\ + .\Release\plink.pch + .\Release\ + .\Release\ + + + true + NDEBUG;%(PreprocessorDefinitions) + .\Release\plink.tlb + true + Win32 + + + 0x0809 + NDEBUG;%(PreprocessorDefinitions) + + + true + .\Release\plink.bsc + + + true + Console + .\Release\plink.exe + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + MultiThreadedDebug + Default + false + Disabled + true + Level3 + true + ProgramDatabase + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;_DEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Debug\ + .\Debug\plink.pch + .\Debug\ + .\Debug\ + EnableFastChecks + + + true + _DEBUG;%(PreprocessorDefinitions) + .\Debug\plink.tlb + true + Win32 + + + 0x0809 + _DEBUG;%(PreprocessorDefinitions) + + + true + .\Debug\plink.bsc + + + true + true + Console + $(TargetPath) + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + + + + ..\..;%(AdditionalIncludeDirectories) + ..\..;%(AdditionalIncludeDirectories) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/windows/VS2010/plink/plink.vcxproj.filters b/windows/VS2010/plink/plink.vcxproj.filters new file mode 100644 index 0000000..53ef921 --- /dev/null +++ b/windows/VS2010/plink/plink.vcxproj.filters @@ -0,0 +1,316 @@ + + + + + Resource Files + + + + + Resource Files + + + + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + + + {cabf3930-a192-46fa-9d0b-c12a3c48fb64} + + + {211b9eeb-2f7b-4f17-ba17-7fa34bd6d53f} + + + {7398cce3-d4c6-47d7-8876-968d1b521c8d} + + + \ No newline at end of file diff --git a/windows/VS2010/pscp/pscp.vcxproj b/windows/VS2010/pscp/pscp.vcxproj new file mode 100644 index 0000000..428318f --- /dev/null +++ b/windows/VS2010/pscp/pscp.vcxproj @@ -0,0 +1,285 @@ + + + + + Debug + Win32 + + + Release + Win32 + + + + + + {26d200f3-250a-494f-aaa4-c992ec4345aa} + + + + Application + false + MultiByte + v100 + + + Application + false + MultiByte + v100 + + + + + + + + + + + + + .\Release\ + .\Release\ + false + + + .\Debug\ + .\Debug\ + true + + + + MultiThreaded + OnlyExplicitInline + true + true + MaxSpeed + true + Level3 + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;NDEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Release\ + .\Release\pscp.pch + .\Release\ + .\Release\ + + + true + NDEBUG;%(PreprocessorDefinitions) + .\Release\pscp.tlb + true + Win32 + + + 0x0809 + NDEBUG;%(PreprocessorDefinitions) + + + true + .\Release\pscp.bsc + + + true + Console + .\Release\pscp.exe + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + MultiThreadedDebug + Default + false + Disabled + true + Level3 + true + ProgramDatabase + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;_DEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Debug\ + .\Debug\pscp.pch + .\Debug\ + .\Debug\ + EnableFastChecks + + + true + _DEBUG;%(PreprocessorDefinitions) + .\Debug\pscp.tlb + true + Win32 + + + 0x0809 + _DEBUG;%(PreprocessorDefinitions) + + + true + .\Debug\pscp.bsc + + + true + true + Console + $(TargetPath) + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + + + + ..\..;%(AdditionalIncludeDirectories) + ..\..;%(AdditionalIncludeDirectories) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/windows/VS2010/pscp/pscp.vcxproj.filters b/windows/VS2010/pscp/pscp.vcxproj.filters new file mode 100644 index 0000000..fd97dcc --- /dev/null +++ b/windows/VS2010/pscp/pscp.vcxproj.filters @@ -0,0 +1,310 @@ + + + + + Resource Files + + + + + Resource Files + + + + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + + + {22ad16c0-10f2-4c9e-88ce-19909db06db1} + + + {1939563c-d990-4021-aabb-fe01df059ed9} + + + {a470e852-120c-47b4-8b4b-2caf18dec71c} + + + \ No newline at end of file diff --git a/windows/VS2010/psftp/psftp.vcxproj b/windows/VS2010/psftp/psftp.vcxproj new file mode 100644 index 0000000..b7865e0 --- /dev/null +++ b/windows/VS2010/psftp/psftp.vcxproj @@ -0,0 +1,285 @@ + + + + + Debug + Win32 + + + Release + Win32 + + + + + + {3caa8123-13fe-450d-bfe7-fcda524d6830} + + + + Application + false + MultiByte + v100 + + + Application + false + MultiByte + v100 + + + + + + + + + + + + + .\Release\ + .\Release\ + false + + + .\Debug\ + .\Debug\ + true + + + + MultiThreaded + OnlyExplicitInline + true + true + MaxSpeed + true + Level3 + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;NDEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Release\ + .\Release\psftp.pch + .\Release\ + .\Release\ + + + true + NDEBUG;%(PreprocessorDefinitions) + .\Release\psftp.tlb + true + Win32 + + + 0x0809 + NDEBUG;%(PreprocessorDefinitions) + + + true + .\Release\psftp.bsc + + + true + Console + .\Release\psftp.exe + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + MultiThreadedDebug + Default + false + Disabled + true + Level3 + true + ProgramDatabase + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;_DEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Debug\ + .\Debug\psftp.pch + .\Debug\ + .\Debug\ + EnableFastChecks + + + true + _DEBUG;%(PreprocessorDefinitions) + .\Debug\psftp.tlb + true + Win32 + + + 0x0809 + _DEBUG;%(PreprocessorDefinitions) + + + true + .\Debug\psftp.bsc + + + true + true + Console + $(TargetPath) + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + + + + ..\..;%(AdditionalIncludeDirectories) + ..\..;%(AdditionalIncludeDirectories) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/windows/VS2010/psftp/psftp.vcxproj.filters b/windows/VS2010/psftp/psftp.vcxproj.filters new file mode 100644 index 0000000..f90dbe8 --- /dev/null +++ b/windows/VS2010/psftp/psftp.vcxproj.filters @@ -0,0 +1,310 @@ + + + + + Resource Files + + + + + Resource Files + + + + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + + + {156ce40f-dc1b-4721-b08f-6336b9f4d290} + + + {198936a4-3dd8-46c7-8266-b3a081e1e0fc} + + + {a85261db-1733-4f46-b1b9-cf01dd3da697} + + + \ No newline at end of file diff --git a/windows/VS2010/putty.sln b/windows/VS2010/putty.sln new file mode 100644 index 0000000..d7c1ba6 --- /dev/null +++ b/windows/VS2010/putty.sln @@ -0,0 +1,61 @@ +Microsoft Visual Studio Solution File, Format Version 11.00 +# Visual Studio 2010 +Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "pageant", "pageant\pageant.vcxproj", "{27e8f930-2567-4fdc-82c1-0662af3cdf6d}" +EndProject +Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "plink", "plink\plink.vcxproj", "{4478087b-1dc8-4c3e-b624-13661de1947e}" +EndProject +Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "pscp", "pscp\pscp.vcxproj", "{26d200f3-250a-494f-aaa4-c992ec4345aa}" +EndProject +Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "psftp", "psftp\psftp.vcxproj", "{3caa8123-13fe-450d-bfe7-fcda524d6830}" +EndProject +Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "putty", "putty\putty.vcxproj", "{8f44624a-d188-4188-b9aa-5f99f20723e1}" +EndProject +Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "puttygen", "puttygen\puttygen.vcxproj", "{617b1bef-aa10-42b4-8f69-4c183bc1ec0f}" +EndProject +Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "puttytel", "puttytel\puttytel.vcxproj", "{b7dd98ff-b336-4d23-9c07-e5fa7a9f3130}" +EndProject +Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "testcrypt", "testcrypt\testcrypt.vcxproj", "{232ff6d5-a626-4562-977c-2ab72baa29fd}" +EndProject +Global + GlobalSection(SolutionConfigurationPlatforms) = preSolution + Debug|Win32 = Debug|Win32 + Release|Win32 = Release|Win32 + EndGlobalSection + GlobalSection(ProjectConfigurationPlatforms) = postSolution + {26d200f3-250a-494f-aaa4-c992ec4345aa}.Debug|Win32.ActiveCfg = Debug|Win32 + {26d200f3-250a-494f-aaa4-c992ec4345aa}.Debug|Win32.Build.0 = Debug|Win32 + {26d200f3-250a-494f-aaa4-c992ec4345aa}.Release|Win32.ActiveCfg = Release|Win32 + {26d200f3-250a-494f-aaa4-c992ec4345aa}.Release|Win32.Build.0 = Release|Win32 + {232ff6d5-a626-4562-977c-2ab72baa29fd}.Debug|Win32.ActiveCfg = Debug|Win32 + {232ff6d5-a626-4562-977c-2ab72baa29fd}.Debug|Win32.Build.0 = Debug|Win32 + {232ff6d5-a626-4562-977c-2ab72baa29fd}.Release|Win32.ActiveCfg = Release|Win32 + {232ff6d5-a626-4562-977c-2ab72baa29fd}.Release|Win32.Build.0 = Release|Win32 + {4478087b-1dc8-4c3e-b624-13661de1947e}.Debug|Win32.ActiveCfg = Debug|Win32 + {4478087b-1dc8-4c3e-b624-13661de1947e}.Debug|Win32.Build.0 = Debug|Win32 + {4478087b-1dc8-4c3e-b624-13661de1947e}.Release|Win32.ActiveCfg = Release|Win32 + {4478087b-1dc8-4c3e-b624-13661de1947e}.Release|Win32.Build.0 = Release|Win32 + {8f44624a-d188-4188-b9aa-5f99f20723e1}.Debug|Win32.ActiveCfg = Debug|Win32 + {8f44624a-d188-4188-b9aa-5f99f20723e1}.Debug|Win32.Build.0 = Debug|Win32 + {8f44624a-d188-4188-b9aa-5f99f20723e1}.Release|Win32.ActiveCfg = Release|Win32 + {8f44624a-d188-4188-b9aa-5f99f20723e1}.Release|Win32.Build.0 = Release|Win32 + {27e8f930-2567-4fdc-82c1-0662af3cdf6d}.Debug|Win32.ActiveCfg = Debug|Win32 + {27e8f930-2567-4fdc-82c1-0662af3cdf6d}.Debug|Win32.Build.0 = Debug|Win32 + {27e8f930-2567-4fdc-82c1-0662af3cdf6d}.Release|Win32.ActiveCfg = Release|Win32 + {27e8f930-2567-4fdc-82c1-0662af3cdf6d}.Release|Win32.Build.0 = Release|Win32 + {3caa8123-13fe-450d-bfe7-fcda524d6830}.Debug|Win32.ActiveCfg = Debug|Win32 + {3caa8123-13fe-450d-bfe7-fcda524d6830}.Debug|Win32.Build.0 = Debug|Win32 + {3caa8123-13fe-450d-bfe7-fcda524d6830}.Release|Win32.ActiveCfg = Release|Win32 + {3caa8123-13fe-450d-bfe7-fcda524d6830}.Release|Win32.Build.0 = Release|Win32 + {617b1bef-aa10-42b4-8f69-4c183bc1ec0f}.Debug|Win32.ActiveCfg = Debug|Win32 + {617b1bef-aa10-42b4-8f69-4c183bc1ec0f}.Debug|Win32.Build.0 = Debug|Win32 + {617b1bef-aa10-42b4-8f69-4c183bc1ec0f}.Release|Win32.ActiveCfg = Release|Win32 + {617b1bef-aa10-42b4-8f69-4c183bc1ec0f}.Release|Win32.Build.0 = Release|Win32 + {b7dd98ff-b336-4d23-9c07-e5fa7a9f3130}.Debug|Win32.ActiveCfg = Debug|Win32 + {b7dd98ff-b336-4d23-9c07-e5fa7a9f3130}.Debug|Win32.Build.0 = Debug|Win32 + {b7dd98ff-b336-4d23-9c07-e5fa7a9f3130}.Release|Win32.ActiveCfg = Release|Win32 + {b7dd98ff-b336-4d23-9c07-e5fa7a9f3130}.Release|Win32.Build.0 = Release|Win32 + EndGlobalSection + GlobalSection(SolutionProperties) = preSolution + HideSolutionNode = FALSE + EndGlobalSection +EndGlobal diff --git a/windows/VS2010/putty/putty.vcxproj b/windows/VS2010/putty/putty.vcxproj new file mode 100644 index 0000000..58a4cbc --- /dev/null +++ b/windows/VS2010/putty/putty.vcxproj @@ -0,0 +1,300 @@ + + + + + Debug + Win32 + + + Release + Win32 + + + + + + {8f44624a-d188-4188-b9aa-5f99f20723e1} + + + + Application + false + MultiByte + v100 + + + Application + false + MultiByte + v100 + + + + + + + + + + + + + .\Release\ + .\Release\ + false + + + .\Debug\ + .\Debug\ + true + + + + MultiThreaded + OnlyExplicitInline + true + true + MaxSpeed + true + Level3 + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;NDEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Release\ + .\Release\putty.pch + .\Release\ + .\Release\ + + + true + NDEBUG;%(PreprocessorDefinitions) + .\Release\putty.tlb + true + Win32 + + + 0x0809 + NDEBUG;%(PreprocessorDefinitions) + + + true + .\Release\putty.bsc + + + true + Windows + .\Release\putty.exe + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + MultiThreadedDebug + Default + false + Disabled + true + Level3 + true + ProgramDatabase + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;_DEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Debug\ + .\Debug\putty.pch + .\Debug\ + .\Debug\ + EnableFastChecks + + + true + _DEBUG;%(PreprocessorDefinitions) + .\Debug\putty.tlb + true + Win32 + + + 0x0809 + _DEBUG;%(PreprocessorDefinitions) + + + true + .\Debug\putty.bsc + + + true + true + Windows + $(TargetPath) + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + + + + + ..\..;%(AdditionalIncludeDirectories) + ..\..;%(AdditionalIncludeDirectories) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/windows/VS2010/putty/putty.vcxproj.filters b/windows/VS2010/putty/putty.vcxproj.filters new file mode 100644 index 0000000..8bdd448 --- /dev/null +++ b/windows/VS2010/putty/putty.vcxproj.filters @@ -0,0 +1,341 @@ + + + + + Resource Files + + + Resource Files + + + + + Resource Files + + + + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + + + {382c3c77-0fea-4132-a5ae-2550d8a5f395} + + + {8c940eae-8579-4a10-b1a1-bd19ff6e8c9c} + + + {e34b5d5d-ec5e-422e-9244-e7dd2783eead} + + + \ No newline at end of file diff --git a/windows/VS2010/puttygen/puttygen.vcxproj b/windows/VS2010/puttygen/puttygen.vcxproj new file mode 100644 index 0000000..214fe70 --- /dev/null +++ b/windows/VS2010/puttygen/puttygen.vcxproj @@ -0,0 +1,216 @@ + + + + + Debug + Win32 + + + Release + Win32 + + + + + + {617b1bef-aa10-42b4-8f69-4c183bc1ec0f} + + + + Application + false + MultiByte + v100 + + + Application + false + MultiByte + v100 + + + + + + + + + + + + + .\Release\ + .\Release\ + false + + + .\Debug\ + .\Debug\ + true + + + + MultiThreaded + OnlyExplicitInline + true + true + MaxSpeed + true + Level3 + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;NDEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Release\ + .\Release\puttygen.pch + .\Release\ + .\Release\ + + + true + NDEBUG;%(PreprocessorDefinitions) + .\Release\puttygen.tlb + true + Win32 + + + 0x0809 + NDEBUG;%(PreprocessorDefinitions) + + + true + .\Release\puttygen.bsc + + + true + Windows + .\Release\puttygen.exe + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + MultiThreadedDebug + Default + false + Disabled + true + Level3 + true + ProgramDatabase + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;_DEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Debug\ + .\Debug\puttygen.pch + .\Debug\ + .\Debug\ + EnableFastChecks + + + true + _DEBUG;%(PreprocessorDefinitions) + .\Debug\puttygen.tlb + true + Win32 + + + 0x0809 + _DEBUG;%(PreprocessorDefinitions) + + + true + .\Debug\puttygen.bsc + + + true + true + Windows + $(TargetPath) + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + + + + ..\..;%(AdditionalIncludeDirectories) + ..\..;%(AdditionalIncludeDirectories) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/windows/VS2010/puttygen/puttygen.vcxproj.filters b/windows/VS2010/puttygen/puttygen.vcxproj.filters new file mode 100644 index 0000000..cb260be --- /dev/null +++ b/windows/VS2010/puttygen/puttygen.vcxproj.filters @@ -0,0 +1,172 @@ + + + + + Resource Files + + + + + Resource Files + + + + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + + + {c7e8416f-274c-464e-9d2e-049a34f7e1ef} + + + {ea7fa817-a012-4ecd-8900-9d9896b44c96} + + + {1f675268-5bec-451b-b9c9-30ca628ac7d7} + + + \ No newline at end of file diff --git a/windows/VS2010/puttytel/puttytel.vcxproj b/windows/VS2010/puttytel/puttytel.vcxproj new file mode 100644 index 0000000..e5f5562 --- /dev/null +++ b/windows/VS2010/puttytel/puttytel.vcxproj @@ -0,0 +1,227 @@ + + + + + Debug + Win32 + + + Release + Win32 + + + + + + {b7dd98ff-b336-4d23-9c07-e5fa7a9f3130} + + + + Application + false + MultiByte + v100 + + + Application + false + MultiByte + v100 + + + + + + + + + + + + + .\Release\ + .\Release\ + false + + + .\Debug\ + .\Debug\ + true + + + + MultiThreaded + OnlyExplicitInline + true + true + MaxSpeed + true + Level3 + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;NDEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Release\ + .\Release\puttytel.pch + .\Release\ + .\Release\ + + + true + NDEBUG;%(PreprocessorDefinitions) + .\Release\puttytel.tlb + true + Win32 + + + 0x0809 + NDEBUG;%(PreprocessorDefinitions) + + + true + .\Release\puttytel.bsc + + + true + Windows + .\Release\puttytel.exe + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + MultiThreadedDebug + Default + false + Disabled + true + Level3 + true + ProgramDatabase + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;_DEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Debug\ + .\Debug\puttytel.pch + .\Debug\ + .\Debug\ + EnableFastChecks + + + true + _DEBUG;%(PreprocessorDefinitions) + .\Debug\puttytel.tlb + true + Win32 + + + 0x0809 + _DEBUG;%(PreprocessorDefinitions) + + + true + .\Debug\puttytel.bsc + + + true + true + Windows + $(TargetPath) + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + + + + + ..\..;%(AdditionalIncludeDirectories) + ..\..;%(AdditionalIncludeDirectories) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/windows/VS2010/puttytel/puttytel.vcxproj.filters b/windows/VS2010/puttytel/puttytel.vcxproj.filters new file mode 100644 index 0000000..3cbf267 --- /dev/null +++ b/windows/VS2010/puttytel/puttytel.vcxproj.filters @@ -0,0 +1,195 @@ + + + + + Resource Files + + + Resource Files + + + + + Resource Files + + + + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + + + {f8a8578e-e0a7-4047-85b7-4063a874d8f1} + + + {8e1311d1-7c8d-4ba8-bf25-a7d452a53090} + + + {02db3bf1-02b5-4667-b7f8-455e6493b006} + + + \ No newline at end of file diff --git a/windows/VS2010/testcrypt/testcrypt.vcxproj b/windows/VS2010/testcrypt/testcrypt.vcxproj new file mode 100644 index 0000000..d7090f8 --- /dev/null +++ b/windows/VS2010/testcrypt/testcrypt.vcxproj @@ -0,0 +1,186 @@ + + + + + Debug + Win32 + + + Release + Win32 + + + + + + {232ff6d5-a626-4562-977c-2ab72baa29fd} + + + + Application + false + MultiByte + v100 + + + Application + false + MultiByte + v100 + + + + + + + + + + + + + .\Release\ + .\Release\ + false + + + .\Debug\ + .\Debug\ + true + + + + MultiThreaded + OnlyExplicitInline + true + true + MaxSpeed + true + Level3 + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;NDEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Release\ + .\Release\testcrypt.pch + .\Release\ + .\Release\ + + + true + NDEBUG;%(PreprocessorDefinitions) + .\Release\testcrypt.tlb + true + Win32 + + + 0x0809 + NDEBUG;%(PreprocessorDefinitions) + + + true + .\Release\testcrypt.bsc + + + true + Console + .\Release\testcrypt.exe + ;%(AdditionalDependencies) + + + + + MultiThreadedDebug + Default + false + Disabled + true + Level3 + true + ProgramDatabase + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;_DEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Debug\ + .\Debug\testcrypt.pch + .\Debug\ + .\Debug\ + EnableFastChecks + + + true + _DEBUG;%(PreprocessorDefinitions) + .\Debug\testcrypt.tlb + true + Win32 + + + 0x0809 + _DEBUG;%(PreprocessorDefinitions) + + + true + .\Debug\testcrypt.bsc + + + true + true + Console + $(TargetPath) + ;%(AdditionalDependencies) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/windows/VS2010/testcrypt/testcrypt.vcxproj.filters b/windows/VS2010/testcrypt/testcrypt.vcxproj.filters new file mode 100644 index 0000000..dfa2ba1 --- /dev/null +++ b/windows/VS2010/testcrypt/testcrypt.vcxproj.filters @@ -0,0 +1,116 @@ + + + + + + + + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + + + {da1388df-79d3-4aa3-bb29-c40cd08b764d} + + + {b1161d2a-d615-4e3c-b4a4-790cdcd86977} + + + {d873d947-5884-4fb8-a70a-6a227fee257d} + + + \ No newline at end of file diff --git a/windows/VS2012/pageant/pageant.vcxproj b/windows/VS2012/pageant/pageant.vcxproj new file mode 100644 index 0000000..64e168a --- /dev/null +++ b/windows/VS2012/pageant/pageant.vcxproj @@ -0,0 +1,204 @@ + + + + + Debug + Win32 + + + Release + Win32 + + + + + + {27e8f930-2567-4fdc-82c1-0662af3cdf6d} + + + + Application + false + MultiByte + v110 + + + Application + false + MultiByte + v110 + + + + + + + + + + + + + .\Release\ + .\Release\ + false + + + .\Debug\ + .\Debug\ + true + + + + MultiThreaded + OnlyExplicitInline + true + true + MaxSpeed + true + Level3 + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;NDEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Release\ + .\Release\pageant.pch + .\Release\ + .\Release\ + + + true + NDEBUG;%(PreprocessorDefinitions) + .\Release\pageant.tlb + true + Win32 + + + 0x0809 + NDEBUG;%(PreprocessorDefinitions) + + + true + .\Release\pageant.bsc + + + true + Windows + .\Release\pageant.exe + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + MultiThreadedDebug + Default + false + Disabled + true + Level3 + true + ProgramDatabase + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;_DEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Debug\ + .\Debug\pageant.pch + .\Debug\ + .\Debug\ + EnableFastChecks + + + true + _DEBUG;%(PreprocessorDefinitions) + .\Debug\pageant.tlb + true + Win32 + + + 0x0809 + _DEBUG;%(PreprocessorDefinitions) + + + true + .\Debug\pageant.bsc + + + true + true + Windows + $(TargetPath) + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + + + + + ..\..;%(AdditionalIncludeDirectories) + ..\..;%(AdditionalIncludeDirectories) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/windows/VS2012/pageant/pageant.vcxproj.filters b/windows/VS2012/pageant/pageant.vcxproj.filters new file mode 100644 index 0000000..cf8e1ad --- /dev/null +++ b/windows/VS2012/pageant/pageant.vcxproj.filters @@ -0,0 +1,149 @@ + + + + + Resource Files + + + Resource Files + + + + + Resource Files + + + + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + + + {700cfdc0-1885-4a48-9760-6fd8f3f62b09} + + + {25d39962-0c67-4b83-a85f-ca32bded1354} + + + {f84c3ab7-54fe-48c4-be65-5115ae325892} + + + \ No newline at end of file diff --git a/windows/VS2012/plink/plink.vcxproj b/windows/VS2012/plink/plink.vcxproj new file mode 100644 index 0000000..4c384ff --- /dev/null +++ b/windows/VS2012/plink/plink.vcxproj @@ -0,0 +1,288 @@ + + + + + Debug + Win32 + + + Release + Win32 + + + + + + {4478087b-1dc8-4c3e-b624-13661de1947e} + + + + Application + false + MultiByte + v110 + + + Application + false + MultiByte + v110 + + + + + + + + + + + + + .\Release\ + .\Release\ + false + + + .\Debug\ + .\Debug\ + true + + + + MultiThreaded + OnlyExplicitInline + true + true + MaxSpeed + true + Level3 + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;NDEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Release\ + .\Release\plink.pch + .\Release\ + .\Release\ + + + true + NDEBUG;%(PreprocessorDefinitions) + .\Release\plink.tlb + true + Win32 + + + 0x0809 + NDEBUG;%(PreprocessorDefinitions) + + + true + .\Release\plink.bsc + + + true + Console + .\Release\plink.exe + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + MultiThreadedDebug + Default + false + Disabled + true + Level3 + true + ProgramDatabase + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;_DEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Debug\ + .\Debug\plink.pch + .\Debug\ + .\Debug\ + EnableFastChecks + + + true + _DEBUG;%(PreprocessorDefinitions) + .\Debug\plink.tlb + true + Win32 + + + 0x0809 + _DEBUG;%(PreprocessorDefinitions) + + + true + .\Debug\plink.bsc + + + true + true + Console + $(TargetPath) + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + + + + ..\..;%(AdditionalIncludeDirectories) + ..\..;%(AdditionalIncludeDirectories) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/windows/VS2012/plink/plink.vcxproj.filters b/windows/VS2012/plink/plink.vcxproj.filters new file mode 100644 index 0000000..53ef921 --- /dev/null +++ b/windows/VS2012/plink/plink.vcxproj.filters @@ -0,0 +1,316 @@ + + + + + Resource Files + + + + + Resource Files + + + + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + + + {cabf3930-a192-46fa-9d0b-c12a3c48fb64} + + + {211b9eeb-2f7b-4f17-ba17-7fa34bd6d53f} + + + {7398cce3-d4c6-47d7-8876-968d1b521c8d} + + + \ No newline at end of file diff --git a/windows/VS2012/pscp/pscp.vcxproj b/windows/VS2012/pscp/pscp.vcxproj new file mode 100644 index 0000000..22de869 --- /dev/null +++ b/windows/VS2012/pscp/pscp.vcxproj @@ -0,0 +1,285 @@ + + + + + Debug + Win32 + + + Release + Win32 + + + + + + {26d200f3-250a-494f-aaa4-c992ec4345aa} + + + + Application + false + MultiByte + v110 + + + Application + false + MultiByte + v110 + + + + + + + + + + + + + .\Release\ + .\Release\ + false + + + .\Debug\ + .\Debug\ + true + + + + MultiThreaded + OnlyExplicitInline + true + true + MaxSpeed + true + Level3 + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;NDEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Release\ + .\Release\pscp.pch + .\Release\ + .\Release\ + + + true + NDEBUG;%(PreprocessorDefinitions) + .\Release\pscp.tlb + true + Win32 + + + 0x0809 + NDEBUG;%(PreprocessorDefinitions) + + + true + .\Release\pscp.bsc + + + true + Console + .\Release\pscp.exe + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + MultiThreadedDebug + Default + false + Disabled + true + Level3 + true + ProgramDatabase + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;_DEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Debug\ + .\Debug\pscp.pch + .\Debug\ + .\Debug\ + EnableFastChecks + + + true + _DEBUG;%(PreprocessorDefinitions) + .\Debug\pscp.tlb + true + Win32 + + + 0x0809 + _DEBUG;%(PreprocessorDefinitions) + + + true + .\Debug\pscp.bsc + + + true + true + Console + $(TargetPath) + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + + + + ..\..;%(AdditionalIncludeDirectories) + ..\..;%(AdditionalIncludeDirectories) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/windows/VS2012/pscp/pscp.vcxproj.filters b/windows/VS2012/pscp/pscp.vcxproj.filters new file mode 100644 index 0000000..fd97dcc --- /dev/null +++ b/windows/VS2012/pscp/pscp.vcxproj.filters @@ -0,0 +1,310 @@ + + + + + Resource Files + + + + + Resource Files + + + + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + + + {22ad16c0-10f2-4c9e-88ce-19909db06db1} + + + {1939563c-d990-4021-aabb-fe01df059ed9} + + + {a470e852-120c-47b4-8b4b-2caf18dec71c} + + + \ No newline at end of file diff --git a/windows/VS2012/psftp/psftp.vcxproj b/windows/VS2012/psftp/psftp.vcxproj new file mode 100644 index 0000000..24d1099 --- /dev/null +++ b/windows/VS2012/psftp/psftp.vcxproj @@ -0,0 +1,285 @@ + + + + + Debug + Win32 + + + Release + Win32 + + + + + + {3caa8123-13fe-450d-bfe7-fcda524d6830} + + + + Application + false + MultiByte + v110 + + + Application + false + MultiByte + v110 + + + + + + + + + + + + + .\Release\ + .\Release\ + false + + + .\Debug\ + .\Debug\ + true + + + + MultiThreaded + OnlyExplicitInline + true + true + MaxSpeed + true + Level3 + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;NDEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Release\ + .\Release\psftp.pch + .\Release\ + .\Release\ + + + true + NDEBUG;%(PreprocessorDefinitions) + .\Release\psftp.tlb + true + Win32 + + + 0x0809 + NDEBUG;%(PreprocessorDefinitions) + + + true + .\Release\psftp.bsc + + + true + Console + .\Release\psftp.exe + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + MultiThreadedDebug + Default + false + Disabled + true + Level3 + true + ProgramDatabase + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;_DEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Debug\ + .\Debug\psftp.pch + .\Debug\ + .\Debug\ + EnableFastChecks + + + true + _DEBUG;%(PreprocessorDefinitions) + .\Debug\psftp.tlb + true + Win32 + + + 0x0809 + _DEBUG;%(PreprocessorDefinitions) + + + true + .\Debug\psftp.bsc + + + true + true + Console + $(TargetPath) + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + + + + ..\..;%(AdditionalIncludeDirectories) + ..\..;%(AdditionalIncludeDirectories) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/windows/VS2012/psftp/psftp.vcxproj.filters b/windows/VS2012/psftp/psftp.vcxproj.filters new file mode 100644 index 0000000..f90dbe8 --- /dev/null +++ b/windows/VS2012/psftp/psftp.vcxproj.filters @@ -0,0 +1,310 @@ + + + + + Resource Files + + + + + Resource Files + + + + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + + + {156ce40f-dc1b-4721-b08f-6336b9f4d290} + + + {198936a4-3dd8-46c7-8266-b3a081e1e0fc} + + + {a85261db-1733-4f46-b1b9-cf01dd3da697} + + + \ No newline at end of file diff --git a/windows/VS2012/putty.sln b/windows/VS2012/putty.sln new file mode 100644 index 0000000..540de75 --- /dev/null +++ b/windows/VS2012/putty.sln @@ -0,0 +1,61 @@ +Microsoft Visual Studio Solution File, Format Version 12.00 +# Visual Studio 2012 +Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "pageant", "pageant\pageant.vcxproj", "{27e8f930-2567-4fdc-82c1-0662af3cdf6d}" +EndProject +Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "plink", "plink\plink.vcxproj", "{4478087b-1dc8-4c3e-b624-13661de1947e}" +EndProject +Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "pscp", "pscp\pscp.vcxproj", "{26d200f3-250a-494f-aaa4-c992ec4345aa}" +EndProject +Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "psftp", "psftp\psftp.vcxproj", "{3caa8123-13fe-450d-bfe7-fcda524d6830}" +EndProject +Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "putty", "putty\putty.vcxproj", "{8f44624a-d188-4188-b9aa-5f99f20723e1}" +EndProject +Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "puttygen", "puttygen\puttygen.vcxproj", "{617b1bef-aa10-42b4-8f69-4c183bc1ec0f}" +EndProject +Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "puttytel", "puttytel\puttytel.vcxproj", "{b7dd98ff-b336-4d23-9c07-e5fa7a9f3130}" +EndProject +Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "testcrypt", "testcrypt\testcrypt.vcxproj", "{232ff6d5-a626-4562-977c-2ab72baa29fd}" +EndProject +Global + GlobalSection(SolutionConfigurationPlatforms) = preSolution + Debug|Win32 = Debug|Win32 + Release|Win32 = Release|Win32 + EndGlobalSection + GlobalSection(ProjectConfigurationPlatforms) = postSolution + {617b1bef-aa10-42b4-8f69-4c183bc1ec0f}.Debug|Win32.ActiveCfg = Debug|Win32 + {617b1bef-aa10-42b4-8f69-4c183bc1ec0f}.Debug|Win32.Build.0 = Debug|Win32 + {617b1bef-aa10-42b4-8f69-4c183bc1ec0f}.Release|Win32.ActiveCfg = Release|Win32 + {617b1bef-aa10-42b4-8f69-4c183bc1ec0f}.Release|Win32.Build.0 = Release|Win32 + {3caa8123-13fe-450d-bfe7-fcda524d6830}.Debug|Win32.ActiveCfg = Debug|Win32 + {3caa8123-13fe-450d-bfe7-fcda524d6830}.Debug|Win32.Build.0 = Debug|Win32 + {3caa8123-13fe-450d-bfe7-fcda524d6830}.Release|Win32.ActiveCfg = Release|Win32 + {3caa8123-13fe-450d-bfe7-fcda524d6830}.Release|Win32.Build.0 = Release|Win32 + {b7dd98ff-b336-4d23-9c07-e5fa7a9f3130}.Debug|Win32.ActiveCfg = Debug|Win32 + {b7dd98ff-b336-4d23-9c07-e5fa7a9f3130}.Debug|Win32.Build.0 = Debug|Win32 + {b7dd98ff-b336-4d23-9c07-e5fa7a9f3130}.Release|Win32.ActiveCfg = Release|Win32 + {b7dd98ff-b336-4d23-9c07-e5fa7a9f3130}.Release|Win32.Build.0 = Release|Win32 + {4478087b-1dc8-4c3e-b624-13661de1947e}.Debug|Win32.ActiveCfg = Debug|Win32 + {4478087b-1dc8-4c3e-b624-13661de1947e}.Debug|Win32.Build.0 = Debug|Win32 + {4478087b-1dc8-4c3e-b624-13661de1947e}.Release|Win32.ActiveCfg = Release|Win32 + {4478087b-1dc8-4c3e-b624-13661de1947e}.Release|Win32.Build.0 = Release|Win32 + {8f44624a-d188-4188-b9aa-5f99f20723e1}.Debug|Win32.ActiveCfg = Debug|Win32 + {8f44624a-d188-4188-b9aa-5f99f20723e1}.Debug|Win32.Build.0 = Debug|Win32 + {8f44624a-d188-4188-b9aa-5f99f20723e1}.Release|Win32.ActiveCfg = Release|Win32 + {8f44624a-d188-4188-b9aa-5f99f20723e1}.Release|Win32.Build.0 = Release|Win32 + {27e8f930-2567-4fdc-82c1-0662af3cdf6d}.Debug|Win32.ActiveCfg = Debug|Win32 + {27e8f930-2567-4fdc-82c1-0662af3cdf6d}.Debug|Win32.Build.0 = Debug|Win32 + {27e8f930-2567-4fdc-82c1-0662af3cdf6d}.Release|Win32.ActiveCfg = Release|Win32 + {27e8f930-2567-4fdc-82c1-0662af3cdf6d}.Release|Win32.Build.0 = Release|Win32 + {232ff6d5-a626-4562-977c-2ab72baa29fd}.Debug|Win32.ActiveCfg = Debug|Win32 + {232ff6d5-a626-4562-977c-2ab72baa29fd}.Debug|Win32.Build.0 = Debug|Win32 + {232ff6d5-a626-4562-977c-2ab72baa29fd}.Release|Win32.ActiveCfg = Release|Win32 + {232ff6d5-a626-4562-977c-2ab72baa29fd}.Release|Win32.Build.0 = Release|Win32 + {26d200f3-250a-494f-aaa4-c992ec4345aa}.Debug|Win32.ActiveCfg = Debug|Win32 + {26d200f3-250a-494f-aaa4-c992ec4345aa}.Debug|Win32.Build.0 = Debug|Win32 + {26d200f3-250a-494f-aaa4-c992ec4345aa}.Release|Win32.ActiveCfg = Release|Win32 + {26d200f3-250a-494f-aaa4-c992ec4345aa}.Release|Win32.Build.0 = Release|Win32 + EndGlobalSection + GlobalSection(SolutionProperties) = preSolution + HideSolutionNode = FALSE + EndGlobalSection +EndGlobal diff --git a/windows/VS2012/putty/putty.vcxproj b/windows/VS2012/putty/putty.vcxproj new file mode 100644 index 0000000..170b577 --- /dev/null +++ b/windows/VS2012/putty/putty.vcxproj @@ -0,0 +1,300 @@ + + + + + Debug + Win32 + + + Release + Win32 + + + + + + {8f44624a-d188-4188-b9aa-5f99f20723e1} + + + + Application + false + MultiByte + v110 + + + Application + false + MultiByte + v110 + + + + + + + + + + + + + .\Release\ + .\Release\ + false + + + .\Debug\ + .\Debug\ + true + + + + MultiThreaded + OnlyExplicitInline + true + true + MaxSpeed + true + Level3 + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;NDEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Release\ + .\Release\putty.pch + .\Release\ + .\Release\ + + + true + NDEBUG;%(PreprocessorDefinitions) + .\Release\putty.tlb + true + Win32 + + + 0x0809 + NDEBUG;%(PreprocessorDefinitions) + + + true + .\Release\putty.bsc + + + true + Windows + .\Release\putty.exe + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + MultiThreadedDebug + Default + false + Disabled + true + Level3 + true + ProgramDatabase + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;_DEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Debug\ + .\Debug\putty.pch + .\Debug\ + .\Debug\ + EnableFastChecks + + + true + _DEBUG;%(PreprocessorDefinitions) + .\Debug\putty.tlb + true + Win32 + + + 0x0809 + _DEBUG;%(PreprocessorDefinitions) + + + true + .\Debug\putty.bsc + + + true + true + Windows + $(TargetPath) + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + + + + + ..\..;%(AdditionalIncludeDirectories) + ..\..;%(AdditionalIncludeDirectories) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/windows/VS2012/putty/putty.vcxproj.filters b/windows/VS2012/putty/putty.vcxproj.filters new file mode 100644 index 0000000..8bdd448 --- /dev/null +++ b/windows/VS2012/putty/putty.vcxproj.filters @@ -0,0 +1,341 @@ + + + + + Resource Files + + + Resource Files + + + + + Resource Files + + + + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + + + {382c3c77-0fea-4132-a5ae-2550d8a5f395} + + + {8c940eae-8579-4a10-b1a1-bd19ff6e8c9c} + + + {e34b5d5d-ec5e-422e-9244-e7dd2783eead} + + + \ No newline at end of file diff --git a/windows/VS2012/puttygen/puttygen.vcxproj b/windows/VS2012/puttygen/puttygen.vcxproj new file mode 100644 index 0000000..68c96d2 --- /dev/null +++ b/windows/VS2012/puttygen/puttygen.vcxproj @@ -0,0 +1,216 @@ + + + + + Debug + Win32 + + + Release + Win32 + + + + + + {617b1bef-aa10-42b4-8f69-4c183bc1ec0f} + + + + Application + false + MultiByte + v110 + + + Application + false + MultiByte + v110 + + + + + + + + + + + + + .\Release\ + .\Release\ + false + + + .\Debug\ + .\Debug\ + true + + + + MultiThreaded + OnlyExplicitInline + true + true + MaxSpeed + true + Level3 + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;NDEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Release\ + .\Release\puttygen.pch + .\Release\ + .\Release\ + + + true + NDEBUG;%(PreprocessorDefinitions) + .\Release\puttygen.tlb + true + Win32 + + + 0x0809 + NDEBUG;%(PreprocessorDefinitions) + + + true + .\Release\puttygen.bsc + + + true + Windows + .\Release\puttygen.exe + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + MultiThreadedDebug + Default + false + Disabled + true + Level3 + true + ProgramDatabase + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;_DEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Debug\ + .\Debug\puttygen.pch + .\Debug\ + .\Debug\ + EnableFastChecks + + + true + _DEBUG;%(PreprocessorDefinitions) + .\Debug\puttygen.tlb + true + Win32 + + + 0x0809 + _DEBUG;%(PreprocessorDefinitions) + + + true + .\Debug\puttygen.bsc + + + true + true + Windows + $(TargetPath) + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + + + + ..\..;%(AdditionalIncludeDirectories) + ..\..;%(AdditionalIncludeDirectories) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/windows/VS2012/puttygen/puttygen.vcxproj.filters b/windows/VS2012/puttygen/puttygen.vcxproj.filters new file mode 100644 index 0000000..cb260be --- /dev/null +++ b/windows/VS2012/puttygen/puttygen.vcxproj.filters @@ -0,0 +1,172 @@ + + + + + Resource Files + + + + + Resource Files + + + + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + + + {c7e8416f-274c-464e-9d2e-049a34f7e1ef} + + + {ea7fa817-a012-4ecd-8900-9d9896b44c96} + + + {1f675268-5bec-451b-b9c9-30ca628ac7d7} + + + \ No newline at end of file diff --git a/windows/VS2012/puttytel/puttytel.vcxproj b/windows/VS2012/puttytel/puttytel.vcxproj new file mode 100644 index 0000000..ce0d295 --- /dev/null +++ b/windows/VS2012/puttytel/puttytel.vcxproj @@ -0,0 +1,227 @@ + + + + + Debug + Win32 + + + Release + Win32 + + + + + + {b7dd98ff-b336-4d23-9c07-e5fa7a9f3130} + + + + Application + false + MultiByte + v110 + + + Application + false + MultiByte + v110 + + + + + + + + + + + + + .\Release\ + .\Release\ + false + + + .\Debug\ + .\Debug\ + true + + + + MultiThreaded + OnlyExplicitInline + true + true + MaxSpeed + true + Level3 + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;NDEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Release\ + .\Release\puttytel.pch + .\Release\ + .\Release\ + + + true + NDEBUG;%(PreprocessorDefinitions) + .\Release\puttytel.tlb + true + Win32 + + + 0x0809 + NDEBUG;%(PreprocessorDefinitions) + + + true + .\Release\puttytel.bsc + + + true + Windows + .\Release\puttytel.exe + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + MultiThreadedDebug + Default + false + Disabled + true + Level3 + true + ProgramDatabase + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;_DEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Debug\ + .\Debug\puttytel.pch + .\Debug\ + .\Debug\ + EnableFastChecks + + + true + _DEBUG;%(PreprocessorDefinitions) + .\Debug\puttytel.tlb + true + Win32 + + + 0x0809 + _DEBUG;%(PreprocessorDefinitions) + + + true + .\Debug\puttytel.bsc + + + true + true + Windows + $(TargetPath) + advapi32.lib;comdlg32.lib;gdi32.lib;imm32.lib;ole32.lib;shell32.lib;user32.lib;%(AdditionalDependencies) + + + + + + + + + ..\..;%(AdditionalIncludeDirectories) + ..\..;%(AdditionalIncludeDirectories) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/windows/VS2012/puttytel/puttytel.vcxproj.filters b/windows/VS2012/puttytel/puttytel.vcxproj.filters new file mode 100644 index 0000000..3cbf267 --- /dev/null +++ b/windows/VS2012/puttytel/puttytel.vcxproj.filters @@ -0,0 +1,195 @@ + + + + + Resource Files + + + Resource Files + + + + + Resource Files + + + + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + + + {f8a8578e-e0a7-4047-85b7-4063a874d8f1} + + + {8e1311d1-7c8d-4ba8-bf25-a7d452a53090} + + + {02db3bf1-02b5-4667-b7f8-455e6493b006} + + + \ No newline at end of file diff --git a/windows/VS2012/testcrypt/testcrypt.vcxproj b/windows/VS2012/testcrypt/testcrypt.vcxproj new file mode 100644 index 0000000..d05a1da --- /dev/null +++ b/windows/VS2012/testcrypt/testcrypt.vcxproj @@ -0,0 +1,186 @@ + + + + + Debug + Win32 + + + Release + Win32 + + + + + + {232ff6d5-a626-4562-977c-2ab72baa29fd} + + + + Application + false + MultiByte + v110 + + + Application + false + MultiByte + v110 + + + + + + + + + + + + + .\Release\ + .\Release\ + false + + + .\Debug\ + .\Debug\ + true + + + + MultiThreaded + OnlyExplicitInline + true + true + MaxSpeed + true + Level3 + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;NDEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Release\ + .\Release\testcrypt.pch + .\Release\ + .\Release\ + + + true + NDEBUG;%(PreprocessorDefinitions) + .\Release\testcrypt.tlb + true + Win32 + + + 0x0809 + NDEBUG;%(PreprocessorDefinitions) + + + true + .\Release\testcrypt.bsc + + + true + Console + .\Release\testcrypt.exe + ;%(AdditionalDependencies) + + + + + MultiThreadedDebug + Default + false + Disabled + true + Level3 + true + ProgramDatabase + ..\..\..\./;..\..\..\charset/;..\..\..\windows/;..\..\..\unix/;%(AdditionalIncludeDirectories) + WIN32;_DEBUG;_WINDOWS;POSIX;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions) + .\Debug\ + .\Debug\testcrypt.pch + .\Debug\ + .\Debug\ + EnableFastChecks + + + true + _DEBUG;%(PreprocessorDefinitions) + .\Debug\testcrypt.tlb + true + Win32 + + + 0x0809 + _DEBUG;%(PreprocessorDefinitions) + + + true + .\Debug\testcrypt.bsc + + + true + true + Console + $(TargetPath) + ;%(AdditionalDependencies) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/windows/VS2012/testcrypt/testcrypt.vcxproj.filters b/windows/VS2012/testcrypt/testcrypt.vcxproj.filters new file mode 100644 index 0000000..dfa2ba1 --- /dev/null +++ b/windows/VS2012/testcrypt/testcrypt.vcxproj.filters @@ -0,0 +1,116 @@ + + + + + + + + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + Source Files + + + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + Header Files + + + + {da1388df-79d3-4aa3-bb29-c40cd08b764d} + + + {b1161d2a-d615-4e3c-b4a4-790cdcd86977} + + + {d873d947-5884-4fb8-a70a-6a227fee257d} + + + \ No newline at end of file diff --git a/windows/VS2019/pscp/pscp.vcxproj b/windows/VS2019/pscp/pscp.vcxproj index bd86624..4f0b5c4 100644 --- a/windows/VS2019/pscp/pscp.vcxproj +++ b/windows/VS2019/pscp/pscp.vcxproj @@ -331,6 +331,7 @@ + diff --git a/windows/VS2019/pscp/pscp.vcxproj.filters b/windows/VS2019/pscp/pscp.vcxproj.filters index 7b84293..d678879 100644 --- a/windows/VS2019/pscp/pscp.vcxproj.filters +++ b/windows/VS2019/pscp/pscp.vcxproj.filters @@ -310,6 +310,9 @@ Source Files + + Source Files + diff --git a/windows/VS2019/psftp/psftp.vcxproj b/windows/VS2019/psftp/psftp.vcxproj index c2491dc..ed22a98 100644 --- a/windows/VS2019/psftp/psftp.vcxproj +++ b/windows/VS2019/psftp/psftp.vcxproj @@ -331,6 +331,7 @@ + diff --git a/windows/VS2019/psftp/psftp.vcxproj.filters b/windows/VS2019/psftp/psftp.vcxproj.filters index 4d30a3f..674a6cf 100644 --- a/windows/VS2019/psftp/psftp.vcxproj.filters +++ b/windows/VS2019/psftp/psftp.vcxproj.filters @@ -310,6 +310,9 @@ Source Files + + Source Files + diff --git a/windows/VS2019/putty/putty.vcxproj b/windows/VS2019/putty/putty.vcxproj index 9bbc154..58698ee 100644 --- a/windows/VS2019/putty/putty.vcxproj +++ b/windows/VS2019/putty/putty.vcxproj @@ -316,7 +316,6 @@ - diff --git a/windows/VS2019/putty/putty.vcxproj.filters b/windows/VS2019/putty/putty.vcxproj.filters index 6edd37b..a5a3ad0 100644 --- a/windows/VS2019/putty/putty.vcxproj.filters +++ b/windows/VS2019/putty/putty.vcxproj.filters @@ -58,9 +58,6 @@ Source Files - - Source Files - Source Files diff --git a/windows/VS2019/puttytel/puttytel.vcxproj b/windows/VS2019/puttytel/puttytel.vcxproj index d9caf8e..81d91f5 100644 --- a/windows/VS2019/puttytel/puttytel.vcxproj +++ b/windows/VS2019/puttytel/puttytel.vcxproj @@ -313,7 +313,6 @@ - diff --git a/windows/VS2019/puttytel/puttytel.vcxproj.filters b/windows/VS2019/puttytel/puttytel.vcxproj.filters index 7235c66..2d60bb3 100644 --- a/windows/VS2019/puttytel/puttytel.vcxproj.filters +++ b/windows/VS2019/puttytel/puttytel.vcxproj.filters @@ -28,9 +28,6 @@ Source Files - - Source Files - Source Files diff --git a/windows/putty.iss b/windows/putty.iss deleted file mode 100644 index a18452a..0000000 --- a/windows/putty.iss +++ /dev/null @@ -1,104 +0,0 @@ -; -*- no -*- -; -; -- Legacy Inno Setup installer script for PuTTY and its related tools. -; Last tested with Inno Setup 5.5.9. -; (New work should go to the MSI installer; see installer.wxs.) -; -; TODO for future releases: -; -; - It might be nice to have an option to add PSCP, Plink and PSFTP to -; the PATH. See wish `installer-addpath'. -; -; - Maybe a "custom" installation might be useful? Hassle with -; UninstallDisplayIcon, though. - -[Setup] -AppName=PuTTY -AppVerName=PuTTY version 0.71 -VersionInfoTextVersion=Release 0.71 -AppVersion=0.71 -VersionInfoVersion=0.71.0.0 -AppPublisher=Simon Tatham -AppPublisherURL=https://www.chiark.greenend.org.uk/~sgtatham/putty/ -AppReadmeFile={app}\README.txt -DefaultDirName={pf}\PuTTY -DefaultGroupName=PuTTY -SetupIconFile=puttyins.ico -UninstallDisplayIcon={app}\putty.exe -ChangesAssociations=yes -;ChangesEnvironment=yes -- when PATH munging is sorted (probably) -Compression=zip/9 -AllowNoIcons=yes -OutputBaseFilename=installer - -[Files] -; We flag all files with "restartreplace" et al primarily for the benefit -; of unattended un/installations/upgrades, when the user is running one -; of the apps at a time. Without it, the operation will fail noisily in -; this situation. -; This does mean that the user will be prompted to restart their machine -; if any of the files _were_ open during installation (or, if /VERYSILENT -; is used, the machine will be restarted automatically!). The /NORESTART -; flag avoids this. -; It might be nicer to have a "no worries, replace the file next time you -; reboot" option, but the developers have no interest in adding one. -; NB: apparently, using long (non-8.3) filenames with restartreplace is a -; bad idea. (Not that we do.) -Source: "build32\putty.exe"; DestDir: "{app}"; Flags: promptifolder replacesameversion restartreplace uninsrestartdelete -Source: "build32\pageant.exe"; DestDir: "{app}"; Flags: promptifolder replacesameversion restartreplace uninsrestartdelete -Source: "build32\puttygen.exe"; DestDir: "{app}"; Flags: promptifolder replacesameversion restartreplace uninsrestartdelete -Source: "build32\pscp.exe"; DestDir: "{app}"; Flags: promptifolder replacesameversion restartreplace uninsrestartdelete -Source: "build32\psftp.exe"; DestDir: "{app}"; Flags: promptifolder replacesameversion restartreplace uninsrestartdelete -Source: "build32\plink.exe"; DestDir: "{app}"; Flags: promptifolder replacesameversion restartreplace uninsrestartdelete -Source: "website.url"; DestDir: "{app}"; Flags: restartreplace uninsrestartdelete -Source: "..\doc\putty.chm"; DestDir: "{app}"; Flags: restartreplace uninsrestartdelete -Source: "..\doc\putty.hlp"; DestDir: "{app}"; Flags: restartreplace uninsrestartdelete -Source: "..\doc\putty.cnt"; DestDir: "{app}"; Flags: restartreplace uninsrestartdelete -Source: "..\LICENCE"; DestDir: "{app}"; Flags: restartreplace uninsrestartdelete -Source: "README.txt"; DestDir: "{app}"; Flags: isreadme restartreplace uninsrestartdelete - -[Icons] -Name: "{group}\PuTTY"; Filename: "{app}\putty.exe"; AppUserModelID: "SimonTatham.PuTTY" -; We have to fall back from the .chm to the older .hlp file on some Windows -; versions. -Name: "{group}\PuTTY Manual"; Filename: "{app}\putty.chm"; MinVersion: 4.1,5.0 -Name: "{group}\PuTTY Manual"; Filename: "{app}\putty.hlp"; OnlyBelowVersion: 4.1,5.0 -Name: "{group}\PuTTY Web Site"; Filename: "{app}\website.url" -Name: "{group}\PSFTP"; Filename: "{app}\psftp.exe" -Name: "{group}\PuTTYgen"; Filename: "{app}\puttygen.exe" -Name: "{group}\Pageant"; Filename: "{app}\pageant.exe" -Name: "{commondesktop}\PuTTY"; Filename: "{app}\putty.exe"; Tasks: desktopicon\common; AppUserModelID: "SimonTatham.PuTTY" -Name: "{userdesktop}\PuTTY"; Filename: "{app}\putty.exe"; Tasks: desktopicon\user; AppUserModelID: "SimonTatham.PuTTY" -; Putting this in {commonappdata} doesn't seem to work, on 98SE at least. -Name: "{userappdata}\Microsoft\Internet Explorer\Quick Launch\PuTTY"; Filename: "{app}\putty.exe"; Tasks: quicklaunchicon - -[Tasks] -Name: desktopicon; Description: "Create a &desktop icon for PuTTY"; GroupDescription: "Additional icons:"; Flags: unchecked -Name: desktopicon\common; Description: "For all users"; GroupDescription: "Additional icons:"; Flags: exclusive unchecked -Name: desktopicon\user; Description: "For the current user only"; GroupDescription: "Additional icons:"; Flags: exclusive unchecked -Name: quicklaunchicon; Description: "Create a &Quick Launch icon for PuTTY (current user only)"; GroupDescription: "Additional icons:"; Flags: unchecked -Name: associate; Description: "&Associate .PPK files (PuTTY Private Key) with Pageant and PuTTYgen"; GroupDescription: "Other tasks:" - -[Registry] -Root: HKCR; Subkey: ".ppk"; ValueType: string; ValueName: ""; ValueData: "PuTTYPrivateKey"; Flags: uninsdeletevalue; Tasks: associate -Root: HKCR; Subkey: "PuTTYPrivateKey"; ValueType: string; ValueName: ""; ValueData: "PuTTY Private Key File"; Flags: uninsdeletekey; Tasks: associate -Root: HKCR; Subkey: "PuTTYPrivateKey\DefaultIcon"; ValueType: string; ValueName: ""; ValueData: "{app}\pageant.exe,0"; Tasks: associate -Root: HKCR; Subkey: "PuTTYPrivateKey\shell\open\command"; ValueType: string; ValueName: ""; ValueData: """{app}\pageant.exe"" ""%1"""; Tasks: associate -Root: HKCR; Subkey: "PuTTYPrivateKey\shell\edit"; ValueType: string; ValueName: ""; ValueData: "&Edit"; Tasks: associate -Root: HKCR; Subkey: "PuTTYPrivateKey\shell\edit\command"; ValueType: string; ValueName: ""; ValueData: """{app}\puttygen.exe"" ""%1"""; Tasks: associate -; Add to PATH on NT-class OS? - -[Messages] -; Since it's possible for the user to be asked to restart their computer, -; we should override the default messages to explain exactly why, so they -; can make an informed decision. (Especially as 95% of users won't need or -; want to restart; see rant above.) -FinishedRestartLabel=One or more [name] programs are still running. Setup will not replace these program files until you restart your computer. Would you like to restart now? -; This message is popped up in a message box on a /SILENT install. -FinishedRestartMessage=One or more [name] programs are still running.%nSetup will not replace these program files until you restart your computer.%n%nWould you like to restart now? -; ...and this comes up if you try to uninstall. -UninstalledAndNeedsRestart=One or more %1 programs are still running.%nThe program files will not be removed until your computer is restarted.%n%nWould you like to restart now? -; Old versions of this installer used to prompt to remove saved settings -; and the like after the point this message was printed, so it seems -; polite to warn people that that no longer happens. -ConfirmUninstall=Are you sure you want to completely remove %1 and all of its components?%n%nNote that this will not remove any saved sessions or random seed file that %1 has created. These are harmless to leave on your system, but if you want to remove them, you should answer No here and run 'putty.exe -cleanup' before you uninstall. diff --git a/windows/version.rc2 b/windows/version.rc2 index 8228371..0cf4613 100644 --- a/windows/version.rc2 +++ b/windows/version.rc2 @@ -52,6 +52,8 @@ BEGIN VALUE "InternalName", APPNAME VALUE "OriginalFilename", APPNAME #if (defined HELPVER) + /* FIXME: this doesn't seem to be visible in Win7/Win10's UI. + * Oh well. */ VALUE "FileVersion", TEXTVER HELPVER #else VALUE "FileVersion", TEXTVER diff --git a/windows/winctrls.c b/windows/winctrls.c index 99119cc..973ac89 100644 --- a/windows/winctrls.c +++ b/windows/winctrls.c @@ -2067,6 +2067,17 @@ static struct winctrl *dlg_findbyctrl(struct dlgparam *dp, union control *ctrl) return NULL; } +bool dlg_is_visible(union control *ctrl, dlgparam *dp) +{ + /* + * In this implementation of the dialog box, we physically + * uncreate controls that aren't in a visible panel of the config + * box. So we can tell if a control is visible just by checking if + * it _exists_. + */ + return dlg_findbyctrl(dp, ctrl) != NULL; +} + void dlg_radiobutton_set(union control *ctrl, dlgparam *dp, int whichbutton) { struct winctrl *c = dlg_findbyctrl(dp, ctrl); diff --git a/windows/window.c b/windows/window.c index 0287cc8..26ef3bb 100644 --- a/windows/window.c +++ b/windows/window.c @@ -293,7 +293,7 @@ static const TermWinVtable windows_termwin_vt = { static TermWin wintw[1]; static HDC wintw_hdc; -static HICON icon; +static HICON trust_icon = INVALID_HANDLE_VALUE; const bool share_can_be_downstream = true; const bool share_can_be_upstream = true; @@ -385,6 +385,7 @@ static void start_backend(void) cleanup_exit(1); } + seat_set_trust_status(win_seat, true); error = backend_init(vt, win_seat, &backend, logctx, conf, conf_get_str(conf, CONF_host), conf_get_int(conf, CONF_port), @@ -680,8 +681,6 @@ int WINAPI WinMain(HINSTANCE inst, HINSTANCE prev, LPSTR cmdline, int show) prepare_session(conf); } - icon = LoadIcon(inst, MAKEINTRESOURCE(IDI_MAINICON)); - if (!prev) { WNDCLASSW wndclass; @@ -690,7 +689,7 @@ int WINAPI WinMain(HINSTANCE inst, HINSTANCE prev, LPSTR cmdline, int show) wndclass.cbClsExtra = 0; wndclass.cbWndExtra = 0; wndclass.hInstance = inst; - wndclass.hIcon = icon; + wndclass.hIcon = LoadIcon(inst, MAKEINTRESOURCE(IDI_MAINICON)); wndclass.hCursor = LoadCursor(NULL, IDC_IBEAM); wndclass.hbrBackground = NULL; wndclass.lpszMenuName = NULL; @@ -1499,6 +1498,8 @@ static int get_font_width(HDC hdc, const TEXTMETRIC *tm) * - verify that the underlined font is the same width as the * ordinary one (manual underlining by means of line drawing can * be done in a pinch). + * + * - find a trust sigil icon that will look OK with the chosen font. */ static void init_fonts(int pick_width, int pick_height) { @@ -1664,6 +1665,13 @@ static void init_fonts(int pick_width, int pick_height) ReleaseDC(hwnd, hdc); + if (trust_icon != INVALID_HANDLE_VALUE) { + DestroyIcon(trust_icon); + } + trust_icon = LoadImage(hinst, MAKEINTRESOURCE(IDI_MAINICON), + IMAGE_ICON, font_width*2, font_height, + LR_DEFAULTCOLOR); + if (fontsize[FONT_UNDERLINE] != fontsize[FONT_NORMAL]) { und_mode = UND_LINE; DeleteObject(fonts[FONT_UNDERLINE]); @@ -1746,6 +1754,11 @@ static void deinit_fonts(void) fonts[i] = 0; fontflag[i] = false; } + + if (trust_icon != INVALID_HANDLE_VALUE) { + DestroyIcon(trust_icon); + } + trust_icon = INVALID_HANDLE_VALUE; } static void wintw_request_resize(TermWin *tw, int w, int h) @@ -3232,9 +3245,7 @@ static LRESULT CALLBACK WndProc(HWND hwnd, UINT message, * messages. We _have_ to buffer everything * we're sent. */ - term_seen_key_event(term); - if (ldisc) - ldisc_send(ldisc, buf, len, true); + term_keyinput(term, -1, buf, len); show_mouseptr(false); } } @@ -3276,10 +3287,9 @@ static LRESULT CALLBACK WndProc(HWND hwnd, UINT message, /* * Jaeyoun Chung reports that Korean character * input doesn't work correctly if we do a single - * luni_send() covering the whole of buff. So - * instead we luni_send the characters one by one. + * term_keyinputw covering the whole of buff. So + * instead we send the characters one by one. */ - term_seen_key_event(term); /* don't divide SURROGATE PAIR */ if (ldisc) { for (i = 0; i < n; i += 2) { @@ -3287,13 +3297,14 @@ static LRESULT CALLBACK WndProc(HWND hwnd, UINT message, if (IS_HIGH_SURROGATE(hs) && i+2 < n) { WCHAR ls = *(unsigned short *)(buff+i+2); if (IS_LOW_SURROGATE(ls)) { - luni_send(ldisc, (unsigned short *)(buff+i), - 2, true); + term_keyinputw( + term, (unsigned short *)(buff+i), 2); i += 2; continue; } } - luni_send(ldisc, (unsigned short *)(buff+i), 1, true); + term_keyinputw( + term, (unsigned short *)(buff+i), 1); } } free(buff); @@ -3308,14 +3319,11 @@ static LRESULT CALLBACK WndProc(HWND hwnd, UINT message, buf[1] = wParam; buf[0] = wParam >> 8; - term_seen_key_event(term); - if (ldisc) - lpage_send(ldisc, kbd_codepage, buf, 2, true); + term_keyinput(term, kbd_codepage, buf, 2); } else { char c = (unsigned char) wParam; term_seen_key_event(term); - if (ldisc) - lpage_send(ldisc, kbd_codepage, &c, 1, true); + term_keyinput(term, kbd_codepage, &c, 1); } return (0); case WM_CHAR: @@ -3336,11 +3344,9 @@ static LRESULT CALLBACK WndProc(HWND hwnd, UINT message, wchar_t pair[2]; pair[0] = pending_surrogate; pair[1] = c; - term_seen_key_event(term); - luni_send(ldisc, pair, 2, true); + term_keyinputw(term, pair, 2); } else if (!IS_SURROGATE(c)) { - term_seen_key_event(term); - luni_send(ldisc, &c, 1, true); + term_keyinputw(term, &c, 1); } } return 0; @@ -4001,7 +4007,7 @@ static void wintw_draw_trust_sigil(TermWin *tw, int x, int y) x += offset_width; y += offset_height; - DrawIconEx(wintw_hdc, x, y, icon, font_width * 2, font_height, + DrawIconEx(wintw_hdc, x, y, trust_icon, font_width * 2, font_height, 0, NULL, DI_NORMAL); } @@ -4101,6 +4107,7 @@ static int TranslateKey(UINT message, WPARAM wParam, LPARAM lParam, bool no_applic_k = conf_get_bool(conf, CONF_no_applic_k); bool ctrlaltkeys = conf_get_bool(conf, CONF_ctrlaltkeys); bool nethack_keypad = conf_get_bool(conf, CONF_nethack_keypad); + char keypad_key = '\0'; HKL kbd_layout = GetKeyboardLayout(0); @@ -4466,14 +4473,8 @@ static int TranslateKey(UINT message, WPARAM wParam, LPARAM lParam, *p++ = 0x1E; /* Ctrl-~ == Ctrl-^ in xterm at least */ return p - output; } - if (shift_state == 0 && wParam == VK_RETURN && term->cr_lf_return) { - *p++ = '\r'; - *p++ = '\n'; - return p - output; - } switch (wParam) { - char keypad_key; case VK_NUMPAD0: keypad_key = '0'; goto numeric_keypad; case VK_NUMPAD1: keypad_key = '1'; goto numeric_keypad; case VK_NUMPAD2: keypad_key = '2'; goto numeric_keypad; @@ -4502,10 +4503,36 @@ static int TranslateKey(UINT message, WPARAM wParam, LPARAM lParam, break; } - p += format_numeric_keypad_key( - (char *)p, term, keypad_key, - shift_state & 1, shift_state & 2); - return p - output; + { + int nchars = format_numeric_keypad_key( + (char *)p, term, keypad_key, + shift_state & 1, shift_state & 2); + if (!nchars) { + /* + * If we didn't get an escape sequence out of the + * numeric keypad key, then that must be because + * we're in Num Lock mode without application + * keypad enabled. In that situation we leave this + * keypress to the ToUnicode/ToAsciiEx handler + * below, which will translate it according to the + * appropriate keypad layout (e.g. so that what a + * Brit thinks of as keypad '.' can become ',' in + * the German layout). + * + * An exception is the keypad Return key: if we + * didn't get an escape sequence for that, we + * treat it like ordinary Return, taking into + * account Telnet special new line codes and + * config options. + */ + if (keypad_key == '\r') + goto ordinary_return_key; + break; + } + + p += nchars; + return p - output; + } int fkey_number; case VK_F1: fkey_number = 1; goto numbered_function_key; @@ -4563,9 +4590,16 @@ static int TranslateKey(UINT message, WPARAM wParam, LPARAM lParam, keypad_key = '\r'; goto numeric_keypad; } - *p++ = 0x0D; - *p++ = 0; - return -2; + ordinary_return_key: + if (shift_state == 0 && term->cr_lf_return) { + *p++ = '\r'; + *p++ = '\n'; + return p - output; + } else { + *p++ = 0x0D; + *p++ = 0; + return -2; + } } } @@ -4650,9 +4684,7 @@ static int TranslateKey(UINT message, WPARAM wParam, LPARAM lParam, return 0; } keybuf = nc; - term_seen_key_event(term); - if (ldisc) - luni_send(ldisc, &keybuf, 1, true); + term_keyinputw(term, &keybuf, 1); continue; } @@ -4662,9 +4694,7 @@ static int TranslateKey(UINT message, WPARAM wParam, LPARAM lParam, if (alt_sum) { if (in_utf(term) || ucsdata.dbcs_screenfont) { keybuf = alt_sum; - term_seen_key_event(term); - if (ldisc) - luni_send(ldisc, &keybuf, 1, true); + term_keyinputw(term, &keybuf, 1); } else { char ch = (char) alt_sum; /* @@ -4676,33 +4706,23 @@ static int TranslateKey(UINT message, WPARAM wParam, LPARAM lParam, * messages. We _have_ to buffer * everything we're sent. */ - term_seen_key_event(term); - if (ldisc) - ldisc_send(ldisc, &ch, 1, true); + term_keyinput(term, -1, &ch, 1); } alt_sum = 0; } else { - term_seen_key_event(term); - if (ldisc) - luni_send(ldisc, &wch, 1, true); + term_keyinputw(term, &wch, 1); } } else { if(capsOn && wch < 0x80) { WCHAR cbuf[2]; cbuf[0] = 27; cbuf[1] = xlat_uskbd2cyrllic(wch); - term_seen_key_event(term); - if (ldisc) - luni_send(ldisc, cbuf+!left_alt, 1+!!left_alt, - true); + term_keyinputw(term, cbuf+!left_alt, 1+!!left_alt); } else { WCHAR cbuf[2]; cbuf[0] = '\033'; cbuf[1] = wch; - term_seen_key_event(term); - if (ldisc) - luni_send(ldisc, cbuf +!left_alt, 1+!!left_alt, - true); + term_keyinputw(term, cbuf +!left_alt, 1+!!left_alt); } } show_mouseptr(false); diff --git a/windows/wingss.c b/windows/wingss.c index 4b511b2..d4d5d88 100644 --- a/windows/wingss.c +++ b/windows/wingss.c @@ -170,6 +170,8 @@ struct ssh_gss_liblist *ssh_gss_setup(Conf *conf) BIND_GSS_FN(release_buffer); BIND_GSS_FN(release_cred); BIND_GSS_FN(release_name); + BIND_GSS_FN(acquire_cred); + BIND_GSS_FN(inquire_cred_by_mech); #undef BIND_GSS_FN @@ -252,6 +254,8 @@ struct ssh_gss_liblist *ssh_gss_setup(Conf *conf) BIND_GSS_FN(release_buffer); BIND_GSS_FN(release_cred); BIND_GSS_FN(release_name); + BIND_GSS_FN(acquire_cred); + BIND_GSS_FN(inquire_cred_by_mech); #undef BIND_GSS_FN diff --git a/windows/winhelp.c b/windows/winhelp.c index 0dca451..df6ac37 100644 --- a/windows/winhelp.c +++ b/windows/winhelp.c @@ -229,11 +229,8 @@ void launch_help(HWND hwnd, const char *topic) return; if (topic) { - int colonpos = strcspn(topic, ":"); - assert(topic[colonpos] != '\0'); - char *fname = dupprintf( - "%s::/%s.html>main", chm_path, topic + colonpos + 1); + "%s::/%s.html>main", chm_path, topic); p_HtmlHelpA(hwnd, fname, HH_DISPLAY_TOPIC, 0); sfree(fname); } else { diff --git a/windows/winhelp.h b/windows/winhelp.h index 948cf73..823a242 100644 --- a/windows/winhelp.h +++ b/windows/winhelp.h @@ -1,11 +1,7 @@ /* * winhelp.h - define Windows Help context names. - * Each definition has the form "winhelp-topic:halibut-topic", where: - * - "winhelp-topic" matches up with the \cfg{winhelp-topic} directives - * in the Halibut source, and was used for WinHelp (FIXME: this isn't - * used any more); - * - "halibut-topic" matches up with the Halibut keywords in the source, - * and is used for HTML Help. + * Each definition is simply a string which matches up with the + * section names in the Halibut source, and is used for HTML Help. */ /* Maximum length for WINHELP_CTX_foo strings */ @@ -17,173 +13,173 @@ #define WINHELP_CTX_no_help NULL -#define WINHELP_CTX_session_hostname "session.hostname:config-hostname" -#define WINHELP_CTX_session_saved "session.saved:config-saving" -#define WINHELP_CTX_session_coe "session.coe:config-closeonexit" -#define WINHELP_CTX_logging_main "logging.main:config-logging" -#define WINHELP_CTX_logging_filename "logging.filename:config-logfilename" -#define WINHELP_CTX_logging_exists "logging.exists:config-logfileexists" -#define WINHELP_CTX_logging_flush "logging.flush:config-logflush" -#define WINHELP_CTX_logging_header "logging.header:config-logheader" -#define WINHELP_CTX_logging_ssh_omit_password "logging.ssh.omitpassword:config-logssh" -#define WINHELP_CTX_logging_ssh_omit_data "logging.ssh.omitdata:config-logssh" -#define WINHELP_CTX_keyboard_backspace "keyboard.backspace:config-backspace" -#define WINHELP_CTX_keyboard_homeend "keyboard.homeend:config-homeend" -#define WINHELP_CTX_keyboard_funkeys "keyboard.funkeys:config-funkeys" -#define WINHELP_CTX_keyboard_appkeypad "keyboard.appkeypad:config-appkeypad" -#define WINHELP_CTX_keyboard_appcursor "keyboard.appcursor:config-appcursor" -#define WINHELP_CTX_keyboard_nethack "keyboard.nethack:config-nethack" -#define WINHELP_CTX_keyboard_compose "keyboard.compose:config-compose" -#define WINHELP_CTX_keyboard_ctrlalt "keyboard.ctrlalt:config-ctrlalt" -#define WINHELP_CTX_features_application "features.application:config-features-application" -#define WINHELP_CTX_features_mouse "features.mouse:config-features-mouse" -#define WINHELP_CTX_features_resize "features.resize:config-features-resize" -#define WINHELP_CTX_features_altscreen "features.altscreen:config-features-altscreen" -#define WINHELP_CTX_features_retitle "features.retitle:config-features-retitle" -#define WINHELP_CTX_features_qtitle "features.qtitle:config-features-qtitle" -#define WINHELP_CTX_features_dbackspace "features.dbackspace:config-features-dbackspace" -#define WINHELP_CTX_features_charset "features.charset:config-features-charset" -#define WINHELP_CTX_features_clearscroll "features.clearscroll:config-features-clearscroll" -#define WINHELP_CTX_features_arabicshaping "features.arabicshaping:config-features-shaping" -#define WINHELP_CTX_features_bidi "features.bidi:config-features-bidi" -#define WINHELP_CTX_terminal_autowrap "terminal.autowrap:config-autowrap" -#define WINHELP_CTX_terminal_decom "terminal.decom:config-decom" -#define WINHELP_CTX_terminal_lfhascr "terminal.lfhascr:config-crlf" -#define WINHELP_CTX_terminal_crhaslf "terminal.crhaslf:config-lfcr" -#define WINHELP_CTX_terminal_bce "terminal.bce:config-erase" -#define WINHELP_CTX_terminal_blink "terminal.blink:config-blink" -#define WINHELP_CTX_terminal_answerback "terminal.answerback:config-answerback" -#define WINHELP_CTX_terminal_localecho "terminal.localecho:config-localecho" -#define WINHELP_CTX_terminal_localedit "terminal.localedit:config-localedit" -#define WINHELP_CTX_terminal_printing "terminal.printing:config-printing" -#define WINHELP_CTX_bell_style "bell.style:config-bellstyle" -#define WINHELP_CTX_bell_taskbar "bell.taskbar:config-belltaskbar" -#define WINHELP_CTX_bell_overload "bell.overload:config-bellovl" -#define WINHELP_CTX_window_size "window.size:config-winsize" -#define WINHELP_CTX_window_resize "window.resize:config-winsizelock" -#define WINHELP_CTX_window_scrollback "window.scrollback:config-scrollback" -#define WINHELP_CTX_window_erased "window.erased:config-erasetoscrollback" -#define WINHELP_CTX_behaviour_closewarn "behaviour.closewarn:config-warnonclose" -#define WINHELP_CTX_behaviour_altf4 "behaviour.altf4:config-altf4" -#define WINHELP_CTX_behaviour_altspace "behaviour.altspace:config-altspace" -#define WINHELP_CTX_behaviour_altonly "behaviour.altonly:config-altonly" -#define WINHELP_CTX_behaviour_alwaysontop "behaviour.alwaysontop:config-alwaysontop" -#define WINHELP_CTX_behaviour_altenter "behaviour.altenter:config-fullscreen" -#define WINHELP_CTX_appearance_cursor "appearance.cursor:config-cursor" -#define WINHELP_CTX_appearance_font "appearance.font:config-font" -#define WINHELP_CTX_appearance_title "appearance.title:config-title" -#define WINHELP_CTX_appearance_hidemouse "appearance.hidemouse:config-mouseptr" -#define WINHELP_CTX_appearance_border "appearance.border:config-winborder" -#define WINHELP_CTX_connection_termtype "connection.termtype:config-termtype" -#define WINHELP_CTX_connection_termspeed "connection.termspeed:config-termspeed" -#define WINHELP_CTX_connection_username "connection.username:config-username" -#define WINHELP_CTX_connection_username_from_env "connection.usernamefromenv:config-username-from-env" -#define WINHELP_CTX_connection_keepalive "connection.keepalive:config-keepalive" -#define WINHELP_CTX_connection_nodelay "connection.nodelay:config-nodelay" -#define WINHELP_CTX_connection_ipversion "connection.ipversion:config-address-family" -#define WINHELP_CTX_connection_tcpkeepalive "connection.tcpkeepalive:config-tcp-keepalives" -#define WINHELP_CTX_connection_loghost "connection.loghost:config-loghost" -#define WINHELP_CTX_proxy_type "proxy.type:config-proxy-type" -#define WINHELP_CTX_proxy_main "proxy.main:config-proxy" -#define WINHELP_CTX_proxy_exclude "proxy.exclude:config-proxy-exclude" -#define WINHELP_CTX_proxy_dns "proxy.dns:config-proxy-dns" -#define WINHELP_CTX_proxy_auth "proxy.auth:config-proxy-auth" -#define WINHELP_CTX_proxy_command "proxy.command:config-proxy-command" -#define WINHELP_CTX_proxy_logging "proxy.logging:config-proxy-logging" -#define WINHELP_CTX_telnet_environ "telnet.environ:config-environ" -#define WINHELP_CTX_telnet_oldenviron "telnet.oldenviron:config-oldenviron" -#define WINHELP_CTX_telnet_passive "telnet.passive:config-ptelnet" -#define WINHELP_CTX_telnet_specialkeys "telnet.specialkeys:config-telnetkey" -#define WINHELP_CTX_telnet_newline "telnet.newline:config-telnetnl" -#define WINHELP_CTX_rlogin_localuser "rlogin.localuser:config-rlogin-localuser" -#define WINHELP_CTX_ssh_nopty "ssh.nopty:config-ssh-pty" -#define WINHELP_CTX_ssh_ttymodes "ssh.ttymodes:config-ttymodes" -#define WINHELP_CTX_ssh_noshell "ssh.noshell:config-ssh-noshell" -#define WINHELP_CTX_ssh_ciphers "ssh.ciphers:config-ssh-encryption" -#define WINHELP_CTX_ssh_protocol "ssh.protocol:config-ssh-prot" -#define WINHELP_CTX_ssh_command "ssh.command:config-command" -#define WINHELP_CTX_ssh_compress "ssh.compress:config-ssh-comp" -#define WINHELP_CTX_ssh_share "ssh.sharing:config-ssh-sharing" -#define WINHELP_CTX_ssh_kexlist "ssh.kex.order:config-ssh-kex-order" -#define WINHELP_CTX_ssh_hklist "ssh.hostkey.order:config-ssh-hostkey-order" -#define WINHELP_CTX_ssh_gssapi_kex_delegation "ssh.kex.gssapi.delegation:config-ssh-kex-gssapi-delegation" -#define WINHELP_CTX_ssh_kex_repeat "ssh.kex.repeat:config-ssh-kex-rekey" -#define WINHELP_CTX_ssh_kex_manual_hostkeys "ssh.kex.manualhostkeys:config-ssh-kex-manual-hostkeys" -#define WINHELP_CTX_ssh_auth_bypass "ssh.auth.bypass:config-ssh-noauth" -#define WINHELP_CTX_ssh_auth_banner "ssh.auth.banner:config-ssh-banner" -#define WINHELP_CTX_ssh_auth_privkey "ssh.auth.privkey:config-ssh-privkey" -#define WINHELP_CTX_ssh_auth_agentfwd "ssh.auth.agentfwd:config-ssh-agentfwd" -#define WINHELP_CTX_ssh_auth_changeuser "ssh.auth.changeuser:config-ssh-changeuser" -#define WINHELP_CTX_ssh_auth_pageant "ssh.auth.pageant:config-ssh-tryagent" -#define WINHELP_CTX_ssh_auth_tis "ssh.auth.tis:config-ssh-tis" -#define WINHELP_CTX_ssh_auth_ki "ssh.auth.ki:config-ssh-ki" -#define WINHELP_CTX_ssh_gssapi "ssh.auth.gssapi:config-ssh-auth-gssapi" -#define WINHELP_CTX_ssh_gssapi_delegation "ssh.auth.gssapi.delegation:config-ssh-auth-gssapi-delegation" -#define WINHELP_CTX_ssh_gssapi_libraries "ssh.auth.gssapi.libraries:config-ssh-auth-gssapi-libraries" -#define WINHELP_CTX_selection_buttons "selection.buttons:config-mouse" -#define WINHELP_CTX_selection_shiftdrag "selection.shiftdrag:config-mouseshift" -#define WINHELP_CTX_selection_rect "selection.rect:config-rectselect" -#define WINHELP_CTX_selection_linedraw "selection.linedraw:config-linedrawpaste" -#define WINHELP_CTX_selection_autocopy "selection.autocopy:config-selection-autocopy" -#define WINHELP_CTX_selection_clipactions "selection.clipactions:config-selection-clipactions" -#define WINHELP_CTX_selection_pastectrl "selection.pastectrl:config-paste-ctrl-char" -#define WINHELP_CTX_copy_charclasses "copy.charclasses:config-charclasses" -#define WINHELP_CTX_copy_rtf "copy.rtf:config-rtfcopy" -#define WINHELP_CTX_colours_ansi "colours.ansi:config-ansicolour" -#define WINHELP_CTX_colours_xterm256 "colours.xterm256:config-xtermcolour" -#define WINHELP_CTX_colours_truecolour "colours.truecolour:config-truecolour" -#define WINHELP_CTX_colours_bold "colours.bold:config-boldcolour" -#define WINHELP_CTX_colours_system "colours.system:config-syscolour" -#define WINHELP_CTX_colours_logpal "colours.logpal:config-logpalette" -#define WINHELP_CTX_colours_config "colours.config:config-colourcfg" -#define WINHELP_CTX_translation_codepage "translation.codepage:config-charset" -#define WINHELP_CTX_translation_cjk_ambig_wide "translation.cjkambigwide:config-cjk-ambig-wide" -#define WINHELP_CTX_translation_cyrillic "translation.cyrillic:config-cyr" -#define WINHELP_CTX_translation_linedraw "translation.linedraw:config-linedraw" -#define WINHELP_CTX_translation_utf8linedraw "translation.utf8linedraw:config-utf8linedraw" -#define WINHELP_CTX_ssh_tunnels_x11 "ssh.tunnels.x11:config-ssh-x11" -#define WINHELP_CTX_ssh_tunnels_x11auth "ssh.tunnels.x11auth:config-ssh-x11auth" -#define WINHELP_CTX_ssh_tunnels_xauthority "ssh.tunnels.xauthority:config-ssh-xauthority" -#define WINHELP_CTX_ssh_tunnels_portfwd "ssh.tunnels.portfwd:config-ssh-portfwd" -#define WINHELP_CTX_ssh_tunnels_portfwd_localhost "ssh.tunnels.portfwd.localhost:config-ssh-portfwd-localhost" -#define WINHELP_CTX_ssh_tunnels_portfwd_ipversion "ssh.tunnels.portfwd.ipversion:config-ssh-portfwd-address-family" -#define WINHELP_CTX_ssh_bugs_ignore1 "ssh.bugs.ignore1:config-ssh-bug-ignore1" -#define WINHELP_CTX_ssh_bugs_plainpw1 "ssh.bugs.plainpw1:config-ssh-bug-plainpw1" -#define WINHELP_CTX_ssh_bugs_rsa1 "ssh.bugs.rsa1:config-ssh-bug-rsa1" -#define WINHELP_CTX_ssh_bugs_ignore2 "ssh.bugs.ignore2:config-ssh-bug-ignore2" -#define WINHELP_CTX_ssh_bugs_hmac2 "ssh.bugs.hmac2:config-ssh-bug-hmac2" -#define WINHELP_CTX_ssh_bugs_derivekey2 "ssh.bugs.derivekey2:config-ssh-bug-derivekey2" -#define WINHELP_CTX_ssh_bugs_rsapad2 "ssh.bugs.rsapad2:config-ssh-bug-sig" -#define WINHELP_CTX_ssh_bugs_pksessid2 "ssh.bugs.pksessid2:config-ssh-bug-pksessid2" -#define WINHELP_CTX_ssh_bugs_rekey2 "ssh.bugs.rekey2:config-ssh-bug-rekey" -#define WINHELP_CTX_ssh_bugs_maxpkt2 "ssh.bugs.maxpkt2:config-ssh-bug-maxpkt2" -#define WINHELP_CTX_ssh_bugs_winadj "ssh.bugs.winadj:config-ssh-bug-winadj" -#define WINHELP_CTX_ssh_bugs_chanreq "ssh.bugs.winadj:config-ssh-bug-chanreq" -#define WINHELP_CTX_ssh_bugs_oldgex2 "ssh.bugs.oldgex2:config-ssh-bug-oldgex2" -#define WINHELP_CTX_serial_line "serial.line:config-serial-line" -#define WINHELP_CTX_serial_speed "serial.speed:config-serial-speed" -#define WINHELP_CTX_serial_databits "serial.databits:config-serial-databits" -#define WINHELP_CTX_serial_stopbits "serial.stopbits:config-serial-stopbits" -#define WINHELP_CTX_serial_parity "serial.parity:config-serial-parity" -#define WINHELP_CTX_serial_flow "serial.flow:config-serial-flow" +#define WINHELP_CTX_session_hostname "config-hostname" +#define WINHELP_CTX_session_saved "config-saving" +#define WINHELP_CTX_session_coe "config-closeonexit" +#define WINHELP_CTX_logging_main "config-logging" +#define WINHELP_CTX_logging_filename "config-logfilename" +#define WINHELP_CTX_logging_exists "config-logfileexists" +#define WINHELP_CTX_logging_flush "config-logflush" +#define WINHELP_CTX_logging_header "config-logheader" +#define WINHELP_CTX_logging_ssh_omit_password "config-logssh" +#define WINHELP_CTX_logging_ssh_omit_data "config-logssh" +#define WINHELP_CTX_keyboard_backspace "config-backspace" +#define WINHELP_CTX_keyboard_homeend "config-homeend" +#define WINHELP_CTX_keyboard_funkeys "config-funkeys" +#define WINHELP_CTX_keyboard_appkeypad "config-appkeypad" +#define WINHELP_CTX_keyboard_appcursor "config-appcursor" +#define WINHELP_CTX_keyboard_nethack "config-nethack" +#define WINHELP_CTX_keyboard_compose "config-compose" +#define WINHELP_CTX_keyboard_ctrlalt "config-ctrlalt" +#define WINHELP_CTX_features_application "config-features-application" +#define WINHELP_CTX_features_mouse "config-features-mouse" +#define WINHELP_CTX_features_resize "config-features-resize" +#define WINHELP_CTX_features_altscreen "config-features-altscreen" +#define WINHELP_CTX_features_retitle "config-features-retitle" +#define WINHELP_CTX_features_qtitle "config-features-qtitle" +#define WINHELP_CTX_features_dbackspace "config-features-dbackspace" +#define WINHELP_CTX_features_charset "config-features-charset" +#define WINHELP_CTX_features_clearscroll "config-features-clearscroll" +#define WINHELP_CTX_features_arabicshaping "config-features-shaping" +#define WINHELP_CTX_features_bidi "config-features-bidi" +#define WINHELP_CTX_terminal_autowrap "config-autowrap" +#define WINHELP_CTX_terminal_decom "config-decom" +#define WINHELP_CTX_terminal_lfhascr "config-crlf" +#define WINHELP_CTX_terminal_crhaslf "config-lfcr" +#define WINHELP_CTX_terminal_bce "config-erase" +#define WINHELP_CTX_terminal_blink "config-blink" +#define WINHELP_CTX_terminal_answerback "config-answerback" +#define WINHELP_CTX_terminal_localecho "config-localecho" +#define WINHELP_CTX_terminal_localedit "config-localedit" +#define WINHELP_CTX_terminal_printing "config-printing" +#define WINHELP_CTX_bell_style "config-bellstyle" +#define WINHELP_CTX_bell_taskbar "config-belltaskbar" +#define WINHELP_CTX_bell_overload "config-bellovl" +#define WINHELP_CTX_window_size "config-winsize" +#define WINHELP_CTX_window_resize "config-winsizelock" +#define WINHELP_CTX_window_scrollback "config-scrollback" +#define WINHELP_CTX_window_erased "config-erasetoscrollback" +#define WINHELP_CTX_behaviour_closewarn "config-warnonclose" +#define WINHELP_CTX_behaviour_altf4 "config-altf4" +#define WINHELP_CTX_behaviour_altspace "config-altspace" +#define WINHELP_CTX_behaviour_altonly "config-altonly" +#define WINHELP_CTX_behaviour_alwaysontop "config-alwaysontop" +#define WINHELP_CTX_behaviour_altenter "config-fullscreen" +#define WINHELP_CTX_appearance_cursor "config-cursor" +#define WINHELP_CTX_appearance_font "config-font" +#define WINHELP_CTX_appearance_title "config-title" +#define WINHELP_CTX_appearance_hidemouse "config-mouseptr" +#define WINHELP_CTX_appearance_border "config-winborder" +#define WINHELP_CTX_connection_termtype "config-termtype" +#define WINHELP_CTX_connection_termspeed "config-termspeed" +#define WINHELP_CTX_connection_username "config-username" +#define WINHELP_CTX_connection_username_from_env "config-username-from-env" +#define WINHELP_CTX_connection_keepalive "config-keepalive" +#define WINHELP_CTX_connection_nodelay "config-nodelay" +#define WINHELP_CTX_connection_ipversion "config-address-family" +#define WINHELP_CTX_connection_tcpkeepalive "config-tcp-keepalives" +#define WINHELP_CTX_connection_loghost "config-loghost" +#define WINHELP_CTX_proxy_type "config-proxy-type" +#define WINHELP_CTX_proxy_main "config-proxy" +#define WINHELP_CTX_proxy_exclude "config-proxy-exclude" +#define WINHELP_CTX_proxy_dns "config-proxy-dns" +#define WINHELP_CTX_proxy_auth "config-proxy-auth" +#define WINHELP_CTX_proxy_command "config-proxy-command" +#define WINHELP_CTX_proxy_logging "config-proxy-logging" +#define WINHELP_CTX_telnet_environ "config-environ" +#define WINHELP_CTX_telnet_oldenviron "config-oldenviron" +#define WINHELP_CTX_telnet_passive "config-ptelnet" +#define WINHELP_CTX_telnet_specialkeys "config-telnetkey" +#define WINHELP_CTX_telnet_newline "config-telnetnl" +#define WINHELP_CTX_rlogin_localuser "config-rlogin-localuser" +#define WINHELP_CTX_ssh_nopty "config-ssh-pty" +#define WINHELP_CTX_ssh_ttymodes "config-ttymodes" +#define WINHELP_CTX_ssh_noshell "config-ssh-noshell" +#define WINHELP_CTX_ssh_ciphers "config-ssh-encryption" +#define WINHELP_CTX_ssh_protocol "config-ssh-prot" +#define WINHELP_CTX_ssh_command "config-command" +#define WINHELP_CTX_ssh_compress "config-ssh-comp" +#define WINHELP_CTX_ssh_share "config-ssh-sharing" +#define WINHELP_CTX_ssh_kexlist "config-ssh-kex-order" +#define WINHELP_CTX_ssh_hklist "config-ssh-hostkey-order" +#define WINHELP_CTX_ssh_gssapi_kex_delegation "config-ssh-kex-gssapi-delegation" +#define WINHELP_CTX_ssh_kex_repeat "config-ssh-kex-rekey" +#define WINHELP_CTX_ssh_kex_manual_hostkeys "config-ssh-kex-manual-hostkeys" +#define WINHELP_CTX_ssh_auth_bypass "config-ssh-noauth" +#define WINHELP_CTX_ssh_auth_banner "config-ssh-banner" +#define WINHELP_CTX_ssh_auth_privkey "config-ssh-privkey" +#define WINHELP_CTX_ssh_auth_agentfwd "config-ssh-agentfwd" +#define WINHELP_CTX_ssh_auth_changeuser "config-ssh-changeuser" +#define WINHELP_CTX_ssh_auth_pageant "config-ssh-tryagent" +#define WINHELP_CTX_ssh_auth_tis "config-ssh-tis" +#define WINHELP_CTX_ssh_auth_ki "config-ssh-ki" +#define WINHELP_CTX_ssh_gssapi "config-ssh-auth-gssapi" +#define WINHELP_CTX_ssh_gssapi_delegation "config-ssh-auth-gssapi-delegation" +#define WINHELP_CTX_ssh_gssapi_libraries "config-ssh-auth-gssapi-libraries" +#define WINHELP_CTX_selection_buttons "config-mouse" +#define WINHELP_CTX_selection_shiftdrag "config-mouseshift" +#define WINHELP_CTX_selection_rect "config-rectselect" +#define WINHELP_CTX_selection_linedraw "config-linedrawpaste" +#define WINHELP_CTX_selection_autocopy "config-selection-autocopy" +#define WINHELP_CTX_selection_clipactions "config-selection-clipactions" +#define WINHELP_CTX_selection_pastectrl "config-paste-ctrl-char" +#define WINHELP_CTX_copy_charclasses "config-charclasses" +#define WINHELP_CTX_copy_rtf "config-rtfcopy" +#define WINHELP_CTX_colours_ansi "config-ansicolour" +#define WINHELP_CTX_colours_xterm256 "config-xtermcolour" +#define WINHELP_CTX_colours_truecolour "config-truecolour" +#define WINHELP_CTX_colours_bold "config-boldcolour" +#define WINHELP_CTX_colours_system "config-syscolour" +#define WINHELP_CTX_colours_logpal "config-logpalette" +#define WINHELP_CTX_colours_config "config-colourcfg" +#define WINHELP_CTX_translation_codepage "config-charset" +#define WINHELP_CTX_translation_cjk_ambig_wide "config-cjk-ambig-wide" +#define WINHELP_CTX_translation_cyrillic "config-cyr" +#define WINHELP_CTX_translation_linedraw "config-linedraw" +#define WINHELP_CTX_translation_utf8linedraw "config-utf8linedraw" +#define WINHELP_CTX_ssh_tunnels_x11 "config-ssh-x11" +#define WINHELP_CTX_ssh_tunnels_x11auth "config-ssh-x11auth" +#define WINHELP_CTX_ssh_tunnels_xauthority "config-ssh-xauthority" +#define WINHELP_CTX_ssh_tunnels_portfwd "config-ssh-portfwd" +#define WINHELP_CTX_ssh_tunnels_portfwd_localhost "config-ssh-portfwd-localhost" +#define WINHELP_CTX_ssh_tunnels_portfwd_ipversion "config-ssh-portfwd-address-family" +#define WINHELP_CTX_ssh_bugs_ignore1 "config-ssh-bug-ignore1" +#define WINHELP_CTX_ssh_bugs_plainpw1 "config-ssh-bug-plainpw1" +#define WINHELP_CTX_ssh_bugs_rsa1 "config-ssh-bug-rsa1" +#define WINHELP_CTX_ssh_bugs_ignore2 "config-ssh-bug-ignore2" +#define WINHELP_CTX_ssh_bugs_hmac2 "config-ssh-bug-hmac2" +#define WINHELP_CTX_ssh_bugs_derivekey2 "config-ssh-bug-derivekey2" +#define WINHELP_CTX_ssh_bugs_rsapad2 "config-ssh-bug-sig" +#define WINHELP_CTX_ssh_bugs_pksessid2 "config-ssh-bug-pksessid2" +#define WINHELP_CTX_ssh_bugs_rekey2 "config-ssh-bug-rekey" +#define WINHELP_CTX_ssh_bugs_maxpkt2 "config-ssh-bug-maxpkt2" +#define WINHELP_CTX_ssh_bugs_winadj "config-ssh-bug-winadj" +#define WINHELP_CTX_ssh_bugs_chanreq "config-ssh-bug-chanreq" +#define WINHELP_CTX_ssh_bugs_oldgex2 "config-ssh-bug-oldgex2" +#define WINHELP_CTX_serial_line "config-serial-line" +#define WINHELP_CTX_serial_speed "config-serial-speed" +#define WINHELP_CTX_serial_databits "config-serial-databits" +#define WINHELP_CTX_serial_stopbits "config-serial-stopbits" +#define WINHELP_CTX_serial_parity "config-serial-parity" +#define WINHELP_CTX_serial_flow "config-serial-flow" -#define WINHELP_CTX_pageant_general "pageant.general:pageant" -#define WINHELP_CTX_pageant_keylist "pageant.keylist:pageant-mainwin-keylist" -#define WINHELP_CTX_pageant_addkey "pageant.addkey:pageant-mainwin-addkey" -#define WINHELP_CTX_pageant_remkey "pageant.remkey:pageant-mainwin-remkey" -#define WINHELP_CTX_pgpfingerprints "pgpfingerprints:pgpkeys" -#define WINHELP_CTX_puttygen_general "puttygen.general:pubkey-puttygen" -#define WINHELP_CTX_puttygen_keytype "puttygen.keytype:puttygen-keytype" -#define WINHELP_CTX_puttygen_bits "puttygen.bits:puttygen-strength" -#define WINHELP_CTX_puttygen_generate "puttygen.generate:puttygen-generate" -#define WINHELP_CTX_puttygen_fingerprint "puttygen.fingerprint:puttygen-fingerprint" -#define WINHELP_CTX_puttygen_comment "puttygen.comment:puttygen-comment" -#define WINHELP_CTX_puttygen_passphrase "puttygen.passphrase:puttygen-passphrase" -#define WINHELP_CTX_puttygen_savepriv "puttygen.savepriv:puttygen-savepriv" -#define WINHELP_CTX_puttygen_savepub "puttygen.savepub:puttygen-savepub" -#define WINHELP_CTX_puttygen_pastekey "puttygen.pastekey:puttygen-pastekey" -#define WINHELP_CTX_puttygen_load "puttygen.load:puttygen-load" -#define WINHELP_CTX_puttygen_conversions "puttygen.conversions:puttygen-conversions" +#define WINHELP_CTX_pageant_general "pageant" +#define WINHELP_CTX_pageant_keylist "pageant-mainwin-keylist" +#define WINHELP_CTX_pageant_addkey "pageant-mainwin-addkey" +#define WINHELP_CTX_pageant_remkey "pageant-mainwin-remkey" +#define WINHELP_CTX_pgpfingerprints "pgpkeys" +#define WINHELP_CTX_puttygen_general "pubkey-puttygen" +#define WINHELP_CTX_puttygen_keytype "puttygen-keytype" +#define WINHELP_CTX_puttygen_bits "puttygen-strength" +#define WINHELP_CTX_puttygen_generate "puttygen-generate" +#define WINHELP_CTX_puttygen_fingerprint "puttygen-fingerprint" +#define WINHELP_CTX_puttygen_comment "puttygen-comment" +#define WINHELP_CTX_puttygen_passphrase "puttygen-passphrase" +#define WINHELP_CTX_puttygen_savepriv "puttygen-savepriv" +#define WINHELP_CTX_puttygen_savepub "puttygen-savepub" +#define WINHELP_CTX_puttygen_pastekey "puttygen-pastekey" +#define WINHELP_CTX_puttygen_load "puttygen-load" +#define WINHELP_CTX_puttygen_conversions "puttygen-conversions" /* These are used in Windows-specific bits of the frontend. * We (ab)use "help context identifiers" (dwContextId) to identify them. */ @@ -191,13 +187,13 @@ #define HELPCTXID(x) WINHELP_CTXID_ ## x #define WINHELP_CTXID_no_help 0 -#define WINHELP_CTX_errors_hostkey_absent "errors.hostkey.absent:errors-hostkey-absent" +#define WINHELP_CTX_errors_hostkey_absent "errors-hostkey-absent" #define WINHELP_CTXID_errors_hostkey_absent 1 -#define WINHELP_CTX_errors_hostkey_changed "errors.hostkey.changed:errors-hostkey-wrong" +#define WINHELP_CTX_errors_hostkey_changed "errors-hostkey-wrong" #define WINHELP_CTXID_errors_hostkey_changed 2 -#define WINHELP_CTX_errors_cantloadkey "errors.cantloadkey:errors-cant-load-key" +#define WINHELP_CTX_errors_cantloadkey "errors-cant-load-key" #define WINHELP_CTXID_errors_cantloadkey 3 -#define WINHELP_CTX_option_cleanup "options.cleanup:using-cleanup" +#define WINHELP_CTX_option_cleanup "using-cleanup" #define WINHELP_CTXID_option_cleanup 4 -#define WINHELP_CTX_pgp_fingerprints "pgpfingerprints:pgpkeys" +#define WINHELP_CTX_pgp_fingerprints "pgpkeys" #define WINHELP_CTXID_pgp_fingerprints 5 diff --git a/windows/winhsock.c b/windows/winhsock.c index 5bbcfc2..7f2b447 100644 --- a/windows/winhsock.c +++ b/windows/winhsock.c @@ -128,6 +128,8 @@ static void sk_handle_close(Socket *s) CloseHandle(hs->recv_H); bufchain_clear(&hs->inputdata); + delete_callbacks_for_context(hs); + sfree(hs); } diff --git a/windows/winnet.c b/windows/winnet.c index a968079..ae5b11f 100644 --- a/windows/winnet.c +++ b/windows/winnet.c @@ -247,7 +247,7 @@ void sk_init(void) if (GetProcAddress(winsock_module, "getaddrinfo") != NULL) { GET_WINDOWS_FUNCTION(winsock_module, getaddrinfo); GET_WINDOWS_FUNCTION(winsock_module, freeaddrinfo); - GET_WINDOWS_FUNCTION(winsock_module, getnameinfo); + GET_WINDOWS_FUNCTION_NO_TYPECHECK(winsock_module, getnameinfo); /* This function would fail its type-check if we did one, * because the VS header file provides an inline definition * which is __cdecl instead of WINAPI. */ @@ -258,8 +258,8 @@ void sk_init(void) if (wship6_module) { GET_WINDOWS_FUNCTION(wship6_module, getaddrinfo); GET_WINDOWS_FUNCTION(wship6_module, freeaddrinfo); - GET_WINDOWS_FUNCTION(wship6_module, getnameinfo); /* See comment above about type check */ + GET_WINDOWS_FUNCTION_NO_TYPECHECK(wship6_module, getnameinfo); GET_WINDOWS_FUNCTION_NO_TYPECHECK(winsock_module, gai_strerror); } else { } @@ -1344,6 +1344,7 @@ static void sk_net_close(Socket *sock) p_closesocket(s->s); if (s->addr) sk_addr_free(s->addr); + delete_callbacks_for_context(s); sfree(s); } diff --git a/windows/winnoise.c b/windows/winnoise.c index c4167dd..842a69b 100644 --- a/windows/winnoise.c +++ b/windows/winnoise.c @@ -75,18 +75,6 @@ void noise_get_heavy(void (*func) (void *, int)) read_random_seed(func); } -void random_save_seed(void) -{ - int len; - void *data; - - if (random_active) { - random_get_savedata(&data, &len); - write_random_seed(data, len); - sfree(data); - } -} - /* * This function is called on a timer, and it will monitor * frequently changing quantities such as the state of physical and diff --git a/windows/winpgen.c b/windows/winpgen.c index 818bc72..9076c3e 100644 --- a/windows/winpgen.c +++ b/windows/winpgen.c @@ -895,7 +895,7 @@ static INT_PTR CALLBACK MainDlgProc(HWND hwnd, UINT msg, AppendMenu(menu1, MF_ENABLED, IDC_KEYSSH2RSA, "SSH-2 &RSA key"); AppendMenu(menu1, MF_ENABLED, IDC_KEYSSH2DSA, "SSH-2 &DSA key"); AppendMenu(menu1, MF_ENABLED, IDC_KEYSSH2ECDSA, "SSH-2 &ECDSA key"); - AppendMenu(menu1, MF_ENABLED, IDC_KEYSSH2ED25519, "SSH-2 ED&25519 key"); + AppendMenu(menu1, MF_ENABLED, IDC_KEYSSH2ED25519, "SSH-2 Ed&25519 key"); AppendMenu(menu, MF_POPUP | MF_ENABLED, (UINT_PTR) menu1, "&Key"); state->keymenu = menu1; @@ -978,7 +978,7 @@ static INT_PTR CALLBACK MainDlgProc(HWND hwnd, UINT msg, "&RSA", IDC_KEYSSH2RSA, "&DSA", IDC_KEYSSH2DSA, "&ECDSA", IDC_KEYSSH2ECDSA, - "ED&25519", IDC_KEYSSH2ED25519, + "Ed&25519", IDC_KEYSSH2ED25519, "SSH-&1 (RSA)", IDC_KEYSSH1, NULL); cp2 = cp; diff --git a/windows/winpgntc.c b/windows/winpgntc.c index f5ae3d1..601c757 100644 --- a/windows/winpgntc.c +++ b/windows/winpgntc.c @@ -117,13 +117,24 @@ agent_pending_query *agent_query( SetFocus(hCallingWindow); #endif // PUTTY_CAC if (id > 0) { - retlen = 4 + GET_32BIT_MSB_FIRST(p); - ret = snewn(retlen, unsigned char); - if (ret) { + uint32_t length_field = GET_32BIT_MSB_FIRST(p); + if (length_field > 0 && length_field <= AGENT_MAX_MSGLEN - 4) { + retlen = length_field + 4; + ret = snewn(retlen, unsigned char); memcpy(ret, p, retlen); - *out = ret; - *outlen = retlen; - } + *out = ret; + *outlen = retlen; + } else { + /* + * If we get here, we received an out-of-range length + * field, either without space for a message type code or + * overflowing the FileMapping. + * + * Treat this as if Pageant didn't answer at all - which + * actually means we do nothing, and just don't fill in + * out and outlen. + */ + } } UnmapViewOfFile(p); CloseHandle(filemap); diff --git a/windows/winplink.c b/windows/winplink.c index 446de78..46c19c6 100644 --- a/windows/winplink.c +++ b/windows/winplink.c @@ -43,10 +43,6 @@ WSAEVENT netevent; static Backend *backend; Conf *conf; -bool term_ldisc(Terminal *term, int mode) -{ - return false; -} static void plink_echoedit_update(Seat *seat, bool echo, bool edit) { /* Update stdin read mode to reflect changes in line discipline. */ diff --git a/windows/winstore.c b/windows/winstore.c index c846bd6..01ee86f 100644 --- a/windows/winstore.c +++ b/windows/winstore.c @@ -488,12 +488,17 @@ static bool try_random_seed(char const *path, int action, HANDLE *ret) return (*ret != INVALID_HANDLE_VALUE); } +static bool try_random_seed_and_free(char *path, int action, HANDLE *hout) +{ + bool retd = try_random_seed(path, action, hout); + sfree(path); + return retd; +} + static HANDLE access_random_seed(int action) { HKEY rkey; - DWORD type, size; HANDLE rethandle; - char seedpath[2 * MAX_PATH + 10] = "\0"; /* * Iterate over a selection of possible random seed paths until @@ -510,17 +515,18 @@ static HANDLE access_random_seed(int action) * First, try the location specified by the user in the * Registry, if any. */ - size = sizeof(seedpath); - if (RegOpenKey(HKEY_CURRENT_USER, PUTTY_REG_POS, &rkey) == - ERROR_SUCCESS) { - int ret = RegQueryValueEx(rkey, "RandSeedFile", - 0, &type, (BYTE *)seedpath, &size); - if (ret != ERROR_SUCCESS || type != REG_SZ) - seedpath[0] = '\0'; - RegCloseKey(rkey); - - if (*seedpath && try_random_seed(seedpath, action, &rethandle)) - return rethandle; + { + char regpath[MAX_PATH + 1]; + DWORD type, size = sizeof(regpath); + if (RegOpenKey(HKEY_CURRENT_USER, PUTTY_REG_POS, &rkey) == + ERROR_SUCCESS) { + int ret = RegQueryValueEx(rkey, "RandSeedFile", + 0, &type, (BYTE *)regpath, &size); + RegCloseKey(rkey); + if (ret == ERROR_SUCCESS && type == REG_SZ && + try_random_seed(regpath, action, &rethandle)) + return rethandle; + } } /* @@ -541,19 +547,20 @@ static HANDLE access_random_seed(int action) tried_shgetfolderpath = true; } if (p_SHGetFolderPathA) { + char profile[MAX_PATH + 1]; if (SUCCEEDED(p_SHGetFolderPathA(NULL, CSIDL_LOCAL_APPDATA, - NULL, SHGFP_TYPE_CURRENT, seedpath))) { - strcat(seedpath, "\\PUTTY.RND"); - if (try_random_seed(seedpath, action, &rethandle)) - return rethandle; - } + NULL, SHGFP_TYPE_CURRENT, profile)) && + try_random_seed_and_free(dupcat(profile, "\\PUTTY.RND", + (const char *)NULL), + action, &rethandle)) + return rethandle; if (SUCCEEDED(p_SHGetFolderPathA(NULL, CSIDL_APPDATA, - NULL, SHGFP_TYPE_CURRENT, seedpath))) { - strcat(seedpath, "\\PUTTY.RND"); - if (try_random_seed(seedpath, action, &rethandle)) - return rethandle; - } + NULL, SHGFP_TYPE_CURRENT, profile)) && + try_random_seed_and_free(dupcat(profile, "\\PUTTY.RND", + (const char *)NULL), + action, &rethandle)) + return rethandle; } /* @@ -561,28 +568,36 @@ static HANDLE access_random_seed(int action) * user's home directory. */ { - int len, ret; - - len = - GetEnvironmentVariable("HOMEDRIVE", seedpath, - sizeof(seedpath)); - ret = - GetEnvironmentVariable("HOMEPATH", seedpath + len, - sizeof(seedpath) - len); - if (ret != 0) { - strcat(seedpath, "\\PUTTY.RND"); - if (try_random_seed(seedpath, action, &rethandle)) - return rethandle; - } + char drv[MAX_PATH], path[MAX_PATH]; + + DWORD drvlen = GetEnvironmentVariable("HOMEDRIVE", drv, sizeof(drv)); + DWORD pathlen = GetEnvironmentVariable("HOMEPATH", path, sizeof(path)); + + /* We permit %HOMEDRIVE% to expand to an empty string, but if + * %HOMEPATH% does that, we abort the attempt. Same if either + * variable overflows its buffer. */ + if (drvlen == 0) + drv[0] = '\0'; + + if (drvlen < lenof(drv) && pathlen < lenof(path) && pathlen > 0 && + try_random_seed_and_free( + dupcat(drv, path, "\\PUTTY.RND", (const char *)NULL), + action, &rethandle)) + return rethandle; } /* * And finally, fall back to C:\WINDOWS. */ - GetWindowsDirectory(seedpath, sizeof(seedpath)); - strcat(seedpath, "\\PUTTY.RND"); - if (try_random_seed(seedpath, action, &rethandle)) - return rethandle; + { + char windir[MAX_PATH]; + DWORD len = GetWindowsDirectory(windir, sizeof(windir)); + if (len < lenof(windir) && + try_random_seed_and_free( + dupcat(windir, "\\PUTTY.RND", (const char *)NULL), + action, &rethandle)) + return rethandle; + } /* * If even that failed, give up. diff --git a/windows/winucs.c b/windows/winucs.c index eeafc83..f5fbffe 100644 --- a/windows/winucs.c +++ b/windows/winucs.c @@ -1170,21 +1170,28 @@ int wc_to_mb(int codepage, int flags, const wchar_t *wcstr, int wclen, wchar_t ch = wcstr[i]; int by; char *p1; - if (ucsdata->uni_tbl && (p1 = ucsdata->uni_tbl[(ch >> 8) & 0xFF]) - && (by = p1[ch & 0xFF])) - *p++ = by; + + #define WRITECH(chr) do \ + { \ + assert(p - mbstr < mblen); \ + *p++ = (char)(chr); \ + } while (0) + + if (ucsdata->uni_tbl && + (p1 = ucsdata->uni_tbl[(ch >> 8) & 0xFF]) != NULL && + (by = p1[ch & 0xFF]) != '\0') + WRITECH(by); else if (ch < 0x80) - *p++ = (char) ch; - else if (defchr) { - int j; - for (j = 0; defchr[j]; j++) - *p++ = defchr[j]; - } + WRITECH(ch); + else if (defchr) + for (const char *q = defchr; *q; q++) + WRITECH(*q); #if 1 else - *p++ = '.'; + WRITECH('.'); #endif - assert(p - mbstr < mblen); + + #undef WRITECH } return p - mbstr; } else { diff --git a/windows/winutils.c b/windows/winutils.c index a5fedb8..2f4c8f5 100644 --- a/windows/winutils.c +++ b/windows/winutils.c @@ -163,7 +163,7 @@ char *GetDlgItemText_alloc(HWND hwnd, int id) size_t size = 0; do { - sgrowarray(ret, size, size); + sgrowarray_nm(ret, size, size); GetDlgItemText(hwnd, id, ret, size); } while (!memchr(ret, '\0', size-1));