We now have SSL patches.

svn path=/trunk/; revision=2459

2 files changed, 27 insertions, 2 deletions

diff --git a/NEWS b/NEWS
index edd4d8c9..437163a9 100644
--- a/NEWS
+++ b/NEWS
@@ -13,6 +13,7 @@ fetchmail-5.0.2 ():
   ships DSNs when that bit is set (HP OpenMail does this).
 * Delay between POP3 subsessions to allow the server time to release locks.
 * Improved environment-query logic to handle mutiple names per UID.
+* FAQ now includes the location of SSL patches.
 
 There are 255 people on fetchmail-friends and 374 on fetchmail-announce.
 
diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html
index 2ce2ab16..bda28be3 100644
--- a/fetchmail-FAQ.html
+++ b/fetchmail-FAQ.html
@@ -10,7 +10,7 @@
 <table width="100%" cellpadding=0><tr>
 <td width="30%">Back to <a href="index.html">Fetchmail Home Page</a>
 <td width="30%" align=center>To <a href="/~esr/sitemap.html">Site Map</a>
-<td width="30%" align=right>$Date: 1999/04/05 04:27:59 $
+<td width="30%" align=right>$Date: 1999/04/29 06:53:23 $
 </table>
 <HR>
 <H1>Frequently Asked Questions About Fetchmail</H1>
@@ -1569,6 +1569,8 @@ However, the First Amendment of the U.S. Constitution hasn't been
 eviscerated (not yet, anyway -- our would-be totalitarians are
 working on trashing the Second Amendment first).<P>
 
+<h3>Option 1:</h3>
+
 I can therefore safely <em>tell</em> you, in documentation, that there
 appears to be a way to set up an SSL command chain using the `plugin'
 option (originally designed for handling proxy connections across
@@ -1585,6 +1587,28 @@ utility `s_client' as follows:<P>
 
 Now add `plugin ssl_connect' to the server options for your connection.<P>
 
+<h3>Option 2:</h3>
+
+For those in the U.S., there is a set of SSL patches for fetchmail
+available from the <a href="http://www.cryptography.org">North
+American Cryptographic Archives</a>, in the SSL directory.  You have
+to answer three questions about your qualification to access the
+archive, before you are allowed in.  You can enter through the main
+page for the server and browse the archive, or you can go <a
+href="http://www.cryptography.org/cgi-bin/crypto.cgi/SSL">straight to
+the SSL directory</a>.  There you will find patch files against the
+fetchmail release sources as well as patched source tarballs.<P>
+
+While we cannot make the SSL sources available to anyone outside of the
+U.S. at this time, if the patches do leak out of the U.S. through no
+fault of our own, and someone informs us of their location, we can
+provide the URL pointing to archive sites outside of the U.S.<P>
+
+Newer versions of the SSL patches make appear in the "incoming" directory
+and stay there a while until they can be processed and moved to the SSL
+directory.  Check for patches in "incoming" if you do not find patches
+for the latest release.<P>
+
 <hr>
 <h2><a name="R1">R1. Fetchmail isn't working, and -v shows `SMTP connect failed' messages.</a></h2>
 
@@ -2303,7 +2327,7 @@ Re-ordering messages is a user-agent function, anyway.<P>
 <table width="100%" cellpadding=0><tr>
 <td width="30%">Back to <a href="index.html">Fetchmail Home Page</a>
 <td width="30%" align=center>To <a href="/~esr/sitemap.html">Site Map</a>
-<td width="30%" align=right>$Date: 1999/04/05 04:27:59 $
+<td width="30%" align=right>$Date: 1999/04/29 06:53:23 $
 </table>
 
 <P><ADDRESS>Eric S. Raymond <A HREF="mailto:esr@thyrsus.com">&lt;esr@snark.thyrsus.com&gt;</A></ADDRESS>