Changes between Version 3 and Version 4 of STunnelTracd

Timestamp:

Jan 5, 2006, 1:52:21 AM (18 years ago)

Author:

brian whitman <trac_bwhitman@…>

Comment:

—

STunnelTracd

@@ -1 +1 @@
 = Securing tracd with stunnel = 
 
-I could not find a good tutorial on securing (at least for avoiding plaintext sending of auth) tracd. I would appreciate if others could go over this and confirm, but it seems to work. This is using trac 0.9.2.
+(I could not find a good tutorial on securing (at least for avoiding plaintext sending of auth) tracd. I would appreciate if others could go over this and confirm, but it seems to work. This is using trac 0.9.2.)
 
 Using stunnel version 4 or higher, you can create a tracd configuration file that passes requests on an https port to the port you specify when running tracd. In this manner, your users can access tracd using an https:// request, ensuring their requests (and passwords) aren't being sent cleartext.
 
-I put this file in /etc/stunnel/stunnel-tracd.conf:
+Put this file in /etc/stunnel/stunnel-tracd.conf:
 
 {{{
@@ -28 +28 @@
 }}}
 
-If you don't already have a certificate, you need to create a self-signed .pem certificate file, I put it in /etc/stunnel/stunnel.pem. You do this with openssl:
+If you don't already have a certificate, you need to create a self-signed .pem certificate file, you can put it in /etc/stunnel/stunnel.pem. You do this with openssl:
 
 {{{