X-Git-Url: https://git.distorted.org.uk/~mdw/sgt/putty/blobdiff_plain/381f0c3128414a0a49aea6e6b65414c31d65717c..0e27cb6045e34d6e423a4b960b199277f1c58389:/doc/faq.but diff --git a/doc/faq.but b/doc/faq.but index 82214761..58e6a5b5 100644 --- a/doc/faq.but +++ b/doc/faq.but @@ -161,7 +161,7 @@ completely is the wrong solution and we will not do it. If you have host keys available in the common \i\c{known_hosts} format, we have a script called -\W{http://svn.tartarus.org/putty/contrib/kh2reg.py?view=markup}\c{kh2reg.py} +\W{http://svn.tartarus.org/sgt/putty/contrib/kh2reg.py?view=markup}\c{kh2reg.py} to convert them to a Windows .REG file, which can be installed ahead of time by double-clicking or using \c{REGEDIT}. @@ -209,10 +209,10 @@ seems to be working so far. Currently, release versions of PuTTY tools only run on full Win32 systems and Unix. \q{Win32} includes Windows 95, 98, and ME, and it -includes Windows NT, Windows 2000 and Windows XP. +includes Windows NT, 2000, XP, and Vista. -In the development code, a partial port to the Mac OS (see -\k{faq-mac-port}) is under way. +In the development code, partial ports to the Mac OSes exist (see +\k{faq-mac-port}). Currently PuTTY does \e{not} run on Windows CE (see \k{faq-wince}), and it does not quite run on the Win32s environment under Windows @@ -223,7 +223,8 @@ present time. If anyone told you we had an EPOC port, or an iPaq 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. +on the +\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/links.html}{Links page of our website}. \S{faq-unix}{Question} \I{Unix version}Is there a port to Unix? @@ -231,7 +232,9 @@ As of 0.54, 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 containing \c{Makefile.gtk}, which should build you 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, and also \i\c{pterm} - an \cw{xterm}-type program which supports the same terminal emulation as PuTTY. We do not yet have a Unix port of @@ -314,9 +317,22 @@ even on systems the developers \e{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, and a beta -port of PuTTY for the Nokia 9200 Communicator series is available -from \W{http://s2putty.sourceforge.net/}\cw{http://s2putty.sourceforge.net/} +However, some of the work has been done by other people; see the +\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/links.html}{Links page of our website} +for various third-party ports. + +\S{faq-iphone}{Question} 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. Such a port would probably depend upon the +stalled Mac OS X port (see \k{faq-mac-port}). + +However, there is a third-party SSH client for the iPhone and +iPod\_Touch called \W{http://www.instantcocoa.com/products/pTerm/}{pTerm}, +which is apparently based on PuTTY. (This is nothing to do with our +similarly-named \c{pterm}, which is a standalone terminal emulator for +Unix systems; see \k{faq-unix}.) \H{faq-embedding} Embedding PuTTY in other programs @@ -330,6 +346,9 @@ 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 +\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/dll-frontend.html}{the wishlist entry}. + \S{faq-vb}{Question} Is the SSH or Telnet code available as a Visual Basic component? @@ -383,10 +402,9 @@ while host keys are stored under \c{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 \i\c{PUTTY.RND} -in your Windows home directory (\c{%HOMEDRIVE%\\%HOMEPATH%}), or in -the actual Windows directory (such as \c{C:\\WINDOWS}) if the home -directory doesn't exist, for example if you're using Win95. If you +cryptography. This is stored by default in a file called \i\c{PUTTY.RND}; +this is stored by default in the \q{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 @@ -1398,11 +1416,12 @@ and pay any costs, we can't provide this. \H{faq-misc} Miscellaneous questions \S{faq-openssh}{Question} Is PuTTY a port of \i{OpenSSH}, or based on -OpenSSH? +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. +detector for SSH-1 CRC compensation attacks, written by CORE SDI +S.A; we share no code at all with OpenSSL. \S{faq-sillyputty}{Question} Where can I buy silly putty?