> re: STunnel I downloaded, installed, looked through the manual,
> homepage, and fiddled with the .conf and quickly came to the
> conclusion that I really wouldn't know how to begin setting up
> something like STunnel. Unfortunately, that's one or more levels of
> end user behind the wall experience than I possess -- I'm decent
> within the constraints of operating program themselves, but when code
> starts popping up, the water quickly goes over my head.
Here's a sample stunnel.conf file for making an OpenSSL connection to GMail. You can probably change this to match the requirements for your ISP pretty easily. Copy this to notepad and make sure it's saved as plain text in the same directory as STunnel. I have high lighted the critical parts for a client setup.
------------------------------------------------------------------------------ stunnel.conf -----------------------------------------------------------------------------------
; Sample stunnel configuration file by Michal Trojnara 2002-2006
; Some options used here may not be adequate for your particular configuration
; Certificate/key is needed in server mode and optional in client mode
; The default certificate is provided only for testing and should not
; be used in a production environment
cert = stunnel.pem
;key = stunnel.pem
; Some performance tunings
socket = l:TCP_NODELAY=1
socket = r:TCP_NODELAY=1
; Workaround for Eudora bug
;options = DONT_INSERT_EMPTY_FRAGMENTS
; Authentication stuff
;verify = 2
; Don't forget to c_rehash CApath
;CApath = certs
; It's often easier to use CAfile
;CAfile = certs.pem
; Don't forget to c_rehash CRLpath
;CRLpath = crls
; Alternatively you can use CRLfile
;CRLfile = crls.pem
; Some debugging stuff useful for troubleshooting
debug = 7
output = stunnel.log
; Use it for client mode
client = yes
; Service-level configuration
;[pop3s]
;accept = 995
;connect = 110
;[imaps]
;accept = 993
;connect = 143
;[ssmtp]
;accept = 465
;connect = 25
;[https]
;accept = 443
;connect = 80
;TIMEOUTclose = 0
; vim:ft=dosini
; Client-level configuration
[GMail IMAP4]
accept = 20993
connect = imap.gmail.com:993
[GMail POP3]
accept = 20995
connect = pop.gmail.com:995
[GMail SMTP]
accept = 20465
connect = smtp.gmail.com:465
--------------------------------------------------------------- cut here -----------------------------------------------
> Rather, is there some way I could help ensure Pegasus' crypto library
> and my provider get along without the need of another program I'd need
> to have someone else configure and have to keep running behind the
> scenes?
I have no idea how to do this; your ISP does not answer properly and I've no idea how to tell them to fix the problem. It may in fact not work with OpenSSL either but since other client can connect I suspect it will work.
<p>&gt; re: STunnel I downloaded, installed, looked through the manual,
&gt; homepage, and fiddled with the .conf and quickly came to the
&gt; conclusion that I really wouldn't know how to begin setting up
&gt; something like STunnel. Unfortunately, that's one or more levels of
&gt; end user behind the wall experience than I possess -- I'm decent
&gt; within the constraints of operating program themselves, but when code
&gt; starts popping up, the water quickly goes over my head.
Here's a sample stunnel.conf file for making an OpenSSL connection to GMail.&nbsp; You can probably change this to match the requirements for your ISP pretty easily.&nbsp; Copy this to notepad and make sure it's saved as plain text in the same directory as STunnel.&nbsp; I have high lighted the critical parts for a client setup.</p><p>
------------------------------------------------------------------------------ stunnel.conf -----------------------------------------------------------------------------------
; Sample stunnel configuration file by Michal Trojnara 2002-2006
; Some options used here may not be adequate for your particular configuration
; Certificate/key is needed in server mode and optional in client mode
; The default certificate is provided only for testing and should not
; be used in a production environment
cert = stunnel.pem
;key = stunnel.pem
; Some performance tunings
socket = l:TCP_NODELAY=1
socket = r:TCP_NODELAY=1
; Workaround for Eudora bug
;options = DONT_INSERT_EMPTY_FRAGMENTS
; Authentication stuff
;verify = 2
; Don't forget to c_rehash CApath
;CApath = certs
; It's often easier to use CAfile
;CAfile = certs.pem
; Don't forget to c_rehash CRLpath
;CRLpath = crls
; Alternatively you can use CRLfile
;CRLfile = crls.pem
; Some debugging stuff useful for troubleshooting
debug = 7
output = stunnel.log
<b>; Use it for client mode
client = yes</b>
; Service-level configuration
;[pop3s]
;accept&nbsp; = 995
;connect = 110
;[imaps]
;accept&nbsp; = 993
;connect = 143
;[ssmtp]
;accept&nbsp; = 465
;connect = 25
;[https]
;accept&nbsp; = 443
;connect = 80
;TIMEOUTclose = 0
; vim:ft=dosini
<b>; Client-level configuration
[GMail IMAP4]
accept = 20993
connect = imap.gmail.com:993
[GMail POP3]
accept = 20995
connect = pop.gmail.com:995
[GMail SMTP]
accept = 20465
connect = smtp.gmail.com:465</b>
--------------------------------------------------------------- cut here -----------------------------------------------
&gt; Rather, is there some way I could help ensure Pegasus' crypto library
&gt; and my provider get along without the need of another program I'd need
&gt; to have someone else configure and have to keep running behind the
&gt; scenes?
I have no idea how to do this; your ISP does not answer properly and I've no idea how to tell them to fix the problem.&nbsp;&nbsp; It may in fact not work with OpenSSL either but since other client can connect I suspect it will work.
</p>