commit 2283454917f68da16538cb029a45b8b87325e42f
from: Alexander Barton <alex@barton.de>
date: Wed Jan 26 21:47:47 2005 UTC

Added doc/SSL.txt (from CVS HEAD) to 0.8.x branch.

commit - f0b3a9cacda0ddf89590a4087b3092e1d912f122
commit + 2283454917f68da16538cb029a45b8b87325e42f
blob - a31c1792f0d994867d0ebdd3db7b8ebdeb5a8132
blob + 69ba5fc7fde28c30a9908e0986d7bfdb1d5abed8
--- ChangeLog
+++ ChangeLog
@@ -12,6 +12,7 @@
 
 ngircd 0.8.x (CVS)
 
+  - Added doc/SSL.txt to distribution.
   - Fixed a buffer overflow that could cause the daemon to crash. Bug found
     by Florian Westphal, <westphal@foo.fh-furtwangen.de>.
   - Fixed a possible buffer underrun when reading the MOTD file. Thanks
@@ -553,4 +554,4 @@ ngIRCd 0.0.1, 31.12.2001
 
 
 -- 
-$Id: ChangeLog,v 1.233.2.15 2005/01/26 13:27:01 alex Exp $
+$Id: ChangeLog,v 1.233.2.16 2005/01/26 21:47:47 alex Exp $
blob - /dev/null
blob + 6192ddc4ed1a329cc53e47aa035b2774a14cfb0f (mode 644)
--- /dev/null
+++ doc/SSL.txt
@@ -0,0 +1,58 @@
+
+                     ngIRCd - Next Generation IRC Server
+
+                      (c)2001-2004 by Alexander Barton,
+                    alex@barton.de, http://www.barton.de/
+
+               ngIRCd is free software and published under the
+                   terms of the GNU General Public License.
+
+                                 -- SSL.txt --
+
+
+ngIRCd actually doesn't support secure connections for client-server or
+server-server links using SSL, the Secure Socket Layer, by itself. But you can
+use the stunnel(8) command to make this work.
+
+  <http://stunnel.mirt.net/>
+  <http://www.stunnel.org/>
+
+Stefan Sperling (stefan at binarchy dot net) mailed me the following text as a
+short "how-to", thanks Stefan!
+
+
+=== snip ===
+    ! This guide applies to stunnel 4.x !
+
+    Put this in your stunnel.conf:
+
+        [ircs]
+        accept = 6667
+        connect = 6668
+
+    This makes stunnel listen for incoming connections
+    on port 6667 and forward decrypted data to port 6668.
+    We call the connection 'ircs'. Stunnel will use this
+    name when logging connection attempts via syslog.
+    You can also use the name in /etc/hosts.{allow,deny}
+    if you run tcp-wrappers.
+
+    To make sure ngircd is listening on the port where
+    the decrypted data arrives, set
+
+        Ports = 6668
+
+    in your ngircd.conf.
+
+    Start stunnel and restart ngircd.
+
+    That's it.
+    Don't forget to activate ssl support in your irc client ;)
+=== snip ===
+
+
+Probably ngIRCd will include support for SSL in the future ...
+
+
+-- 
+$Id: SSL.txt,v 1.2.2.1 2005/01/26 21:47:47 alex Exp $