-\versionid $Id: faq.but,v 1.47 2003/05/22 08:43:50 simon Exp $
+\versionid $Id: faq.but,v 1.51 2003/11/19 19:09:07 jacob Exp $
\A{faq} PuTTY FAQ
\S{faq-pscp-ascii}{Question} Can PSCP or PSFTP transfer files in
ASCII mode?
-Unfortunately not. This is a limitation of the file transfer
-protocols: the SCP and SFTP protocols have no notion of transferring
-a file in anything other than binary mode.
+Unfortunately not.
-SFTP is designed to be extensible, so it's possible that an
-extension might be proposed at some later date that implements ASCII
-transfer. But the PuTTY team can't do anything about it until that
-happens.
+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.
\H{faq-ports} Ports to other operating systems
It's currently being worked on. If you look at the nightly source
snapshots, you should find a \c{unix} subdirectory, which should
-build you Unix ports of Plink, PuTTY itself, and also \c{pterm} - an
-\cw{xterm}-type program which supports the same terminal emulation
-as PuTTY. We do not yet have Unix ports of PSCP, PSFTP, Pageant or
-PuTTYgen.
+build you Unix ports of Plink, PuTTY itself, PSCP, PSFTP, and
+also \c{pterm} - an \cw{xterm}-type program which supports the
+same terminal emulation as PuTTY. We do not yet have Unix ports of
+Pageant or PuTTYgen.
\S{faq-wince}{Question} Will there be a port to Windows CE or PocketPC?
\S{faq-incorrect-mac}{Question} Why do I see \q{Incorrect MAC
received on packet}?
-This is due to a bug in old SSH 2 servers distributed by
-\cw{ssh.com}. Version 2.3.0 and below of their SSH 2 server
+One possible cause of this that used to be common is a bug in old
+SSH 2 servers distributed by \cw{ssh.com}. (This is not the only
+possible cause; see \k{errors-crc} in the documentation.)
+Version 2.3.0 and below of their SSH 2 server
constructs Message Authentication Codes in the wrong way, and
expects the client to construct them in the same wrong way. PuTTY
constructs the MACs correctly by default, and hence these old