If someone else wants to use bits of PuTTY in the process of writing a Windows SSH server, they'd be perfectly welcome to of course, but I really can't see it being a lot less effort for us to do that than it would be for us to write a server from the ground up. 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.
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.)
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.
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.
•
A.3.1 What ports of PuTTY exist?
•
A.3.2 Is there a port to Unix?
•
A.3.3 What's the point of the Unix port? Unix has OpenSSH.
•
A.3.4 Will there be a port to Windows CE or PocketPC?
•
A.3.5 Is there a port to Windows 3.1?
•
A.3.6 Will there be a port to the Mac?
•
A.3.7 Will there be a port to EPOC?
•
A.3.8 Will there be a port to the iPhone?
A.3.1 What ports of PuTTY exist?
Currently, release versions of PuTTY tools only run on full Win32 systems and Unix. ‘Win32’ includes versions of Windows from Windows 95 onwards (as opposed to the 16-bit Windows 3.1; see
question A.3.5
), up to and including Windows 7; and we know of
no reason why PuTTY should not continue to work on future versions of Windows.
The Windows executables we provide are for the 32-bit ‘x86’ processor architecture, but they should work fine on 64-bit processors that are backward-compatible with that architecture. (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, partial ports to the Mac OSes exist (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 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
.
A.3.2 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.
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 Plink, PuTTY itself, PuTTYgen, PSCP, PSFTP, and also pterm - an xterm-type program which supports the same terminal emulation as PuTTY. We do not yet have a Unix port of Pageant.
If you don't have Gtk, you should still be able to build the command-line tools.