portfwd validation was sometimes not picking up a blank source port

[sgt/putty] / doc / faq.but

diff --git a/doc/faq.but b/doc/faq.but
index b6f4f71..8467384 100644 (file)
--- a/doc/faq.but
+++ b/doc/faq.but
@@ -292,11 +292,17 @@ testing in this area would be very welcome!
 
 \S{faq-mac-port}{Question} Will there be a port to the Mac?
 
 
 \S{faq-mac-port}{Question} Will there be a port to the Mac?
 

-There is a port to the Mac OS in progress. It's just about usable, but
-has an awful lot of gaps and rough edges that will need cleaning up
-before release (such as useful random numbers).
+There are several answers to this question:

 
 

-A separate port to Mac OS X is also underway.
+\b The Unix/Gtk port is already fully working under Mac OS X as an X11
+application.
+
+\b A native (Cocoa) Mac OS X port is in progress. It's just about
+usable, but is of nowhere near release quality yet, and is likely to
+behave in unexpected ways.
+
+\b A separate port to the classic Mac OS (pre-OSX) is also in
+progress; it too is not ready yet.

 
 \S{faq-epoc}{Question} Will there be a port to EPOC?
 
 
 \S{faq-epoc}{Question} Will there be a port to EPOC?
 


@@ -912,8 +918,8 @@ 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).
 
 There is a patch for OpenSSH attached to that bug; it's also fixed in
 recent versions of portable OpenSSH (from around 3.8).
 

-\S{faq-connaborted} Do you want to hear about \q{Software caused
-connection abort}?
+\S{faq-connaborted}{Question} Do you want to hear about \q{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
 
 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