SSL Key File not loaded if ratproxy is not started from the default folder

[GoogleCodeExporter]

The MiTM SSL Proxy only works if ratproxy is started from the ratproxy root.

In my setup it was called from a view scripts:
/home/user1/ratproxy is the ratproxy install folder.
/usr/local/bin/myscript.sh calls /home/user1/ratproxy/ratproxy "bla"

On SSL connections this failes:
25386:error:02001002:system library:fopen:No such file or
directory:bss_file.c:352:fopen('keyfile.pem','r')
25386:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:354:
25386:error:140DC002:SSL routines:SSL_CTX_use_certificate_chain_file:system
lib:ssl_rsa.c:720:
PROGRAM ABORT: certificate load failed [ssl_start(), ssl.c:147]

Original issue reported on code.google.com by hija...@googlemail.com on 7 Jul 2009 at 7:58

[GoogleCodeExporter]

At this time, ratproxy is not intended for standalone installation. I will 
probably
add installation support at a later date, though.

Original comment by lcam...@gmail.com on 6 Oct 2009 at 7:54

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I believe I have this same issue running ratproxy on archlinux. I did a wget of 
http://ratproxy.googlecode.com/svn/trunk/keyfile.pem

I ran ratproxy from the directory I saved the keyfile.pem file and was able to 
start testing SSL connections.

Original comment by cspeck...@gmail.com on 27 Mar 2011 at 4:40