search

popexizhi / ratproxy

Automatically exported from code.google.com/p/ratproxy
0 stars 0 forks source link

Problem in generating report with ratproxy #12

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
I am using ratproxy in windows environment. it shows me that the proxy is
configured properly. I used it for doing an assessment. it generates
various .trace files but when I tried to run reporting tool using the
following command: 

sh ratproxy-report.sh ratproxy.log > report.html

it shows me some error in ratproxy-report.sh (screenshot attached). I want
to know is this some kind of issue in ratproxy-report.sh file or there is
some problem my configuration. 

What is the expected output? What do you see instead?
it should generate a HTML report, containing details of all the issues
identified by ratproxy.

What version of the product are you using? On what operating system?
I am using ratproxy1.5.1 over windows Xp

Original issue reported on code.google.com by srivasta...@gmail.com on 15 Jul 2008 at 2:48

Attachments:

GoogleCodeExporter commented 8 years ago 
Experiencing the exact same behavior - exact same errors. I am running Windows
XP(SP2), ratproxy 1.51 beta. cygwin base 1.5.25-15.

even when i just run ./ratproxy-report.sh, it still returns those errors. I 
would
have expected a different error...

Original comment by ccjjhar...@gmail.com on 15 Jul 2008 at 3:11

GoogleCodeExporter commented 8 years ago 
It's resolved with the help of David Marginian
(http://www.butterdev.com/web-security/2008/07/google-ratproxy-part-2-running-an
d-using-ratproxy/#respond):

Let me be specific in what resolved it - I went back to the cygwin installer, 
and on
the “Choose Installation Directory”, select DOS/text for the Default Text 
File Type.

Original comment by ccjjhar...@gmail.com on 15 Jul 2008 at 3:31

GoogleCodeExporter commented 8 years ago 
The problem appears to be strictly with Cygwin in this configuration: there are 
no
DOS-style newlines in ratproxy-report.sh as such. An incompatibility between 
Cygwin
in unix newline mode and the utility used to unpack the archive might be the 
culprit.

Original comment by lcam...@gmail.com on 15 Jul 2008 at 5:43