Edgewall Software

Changes between Version 3 and Version 4 of STunnelTracd


Ignore:
Timestamp:
Jan 5, 2006, 1:52:21 AM (17 years ago)
Author:
brian whitman <trac_bwhitman@…>
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • STunnelTracd

    v3 v4  
    11= Securing tracd with stunnel =
    22
    3 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.
     3(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.)
    44
    55Using 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.
    66
    7 I put this file in /etc/stunnel/stunnel-tracd.conf:
     7Put this file in /etc/stunnel/stunnel-tracd.conf:
    88
    99{{{
     
    2828}}}
    2929
    30 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:
     30If 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:
    3131
    3232{{{