Hello [email protected]:
可以测试,一个波兰黑客发布的。在这里:http://code.google.com/p/ratproxy/
google的东西猛啊。
-----------------
What is ratproxy?
-----------------
Ratproxy is a semi-automated, largely passive web application security audit
tool. It is meant to complement active crawlers and manual proxies more
commonly used for this task, and is optimized specifically for an accurate and
sensitive detection, and automatic annotation, of potential problems and
security-relevant design patterns based on the observation of existing,
user-initiated traffic in complex web 2.0 environments. The approach taken with
ratproxy offers several important advantages over more traditional methods:
* No risk of disruptions. In the default operating mode, tool does not
generate a high volume of attack-simulating traffic, and as such may be
safely employed against production systems at will, for all types of ad hoc,
post-release audits. Active scanners may trigger DoS conditions or
persistent
XSSes, and hence are poorly suited for live platforms.
* Low effort, high yield. Compared to active scanners or fully manual
proxy-based testing, ratproxy assessments take very little time or bandwidth
to run, and proceed in an intuitive, distraction-free manner - yet provide a
good insight into the inner workings of a product, and the potential
security
vulnerabilities therein. They also afford a consistent and predictable
coverage of user-accessible features.
* Preserved control flow of human interaction. By silently following the
browser, the coverage in locations protected by nonces, during other
operations valid only under certain circumstances, or during dynamic events
such as cross-domain Referer data disclosure, is greatly enhanced.
Brute-force crawlers and fuzzers usually have no way to explore these areas
in a reliable manner.
* WYSIWYG data on script behavior. Javascript interfaces and event handlers
are explored precisely to a degree they are used in the browser, with no
need
for complex guesswork or simulations. Active scanners often have a
significant difficulty exploring JSON responses, XMLHttpRequest() behavior,
UI-triggered event data flow, and the like.
* Easy process integration. The proxy can be transparently integrated into
an existing manual security testing or interface QA processes without
introducing a significant setup or operator training overhead.
Regards!
----------------------
zheng918
blog://hi.baidu.com/zheng918
email: [EMAIL PROTECTED]
2008-07-08
--~--~---------~--~----~------------~-------~--~----~
要向邮件组发送邮件,请发到 [email protected]
要退订此邮件,请发邮件至 [EMAIL PROTECTED]
-~----------~----~----~----~------~----~------~--~---