<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/owasp/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/owasp/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/owasp/feature-requests/</id><updated>2007-01-15T17:07:59Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Option to empty conversation viewer</title><link href="https://sourceforge.net/p/owasp/feature-requests/17/" rel="alternate"/><published>2007-01-15T17:07:59Z</published><updated>2007-01-15T17:07:59Z</updated><author><name>Peter Becker</name><uri>https://sourceforge.net/u/peterbecker/</uri></author><id>https://sourceforge.net274597aedf899c16366737f38b6cc781584dd6d9</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I miss a function (button or similar) to empty the conversation list after one session has been analysed and before the next one should start.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>WSDL parsing requires type in part</title><link href="https://sourceforge.net/p/owasp/feature-requests/16/" rel="alternate"/><published>2006-12-01T11:01:58Z</published><updated>2006-12-01T11:01:58Z</updated><author><name>Arnout Engelen</name><uri>https://sourceforge.net/u/raboofje/</uri></author><id>https://sourceforge.net22273895c4ef73d446f9580ed0f38f0d6bcd6531</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It appears a Part defined like this:&lt;/p&gt;
&lt;p&gt;&amp;lt;wsdl:message name="NieuweMeldingSoapIn"&amp;gt;&lt;br /&gt;
&amp;lt;wsdl:part name="parameters" element="tns:NieuweMelding" /&amp;gt;&lt;br /&gt;
&amp;lt;/wsdl:message&amp;gt;&lt;/p&gt;
&lt;p&gt;is not supported: I get a "no type for Part" error message on the console.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>WSDL from file</title><link href="https://sourceforge.net/p/owasp/feature-requests/15/" rel="alternate"/><published>2006-12-01T10:01:18Z</published><updated>2006-12-01T10:01:18Z</updated><author><name>Arnout Engelen</name><uri>https://sourceforge.net/u/raboofje/</uri></author><id>https://sourceforge.netd9f8d23594524a8085578b028e6c8b6479c888a6</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It'd be nice if i could select a file to read the WSDL from, instead of loading it from a URL.&lt;/p&gt;
&lt;p&gt;This is useful when a webservice doesn't come with a WSDL (and one was hand-crafted locally), or when the officially provided WSDL is not correct.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>JavaScript support</title><link href="https://sourceforge.net/p/owasp/feature-requests/14/" rel="alternate"/><published>2005-04-13T09:17:17Z</published><updated>2005-04-13T09:17:17Z</updated><author><name>Rogan Dawes</name><uri>https://sourceforge.net/u/rogan/</uri></author><id>https://sourceforge.net996465f35e57b6e02224dce4343697fec711038f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It would be great to implement Javascript support in&lt;br /&gt;
WebScarab (mainly the spider, I guess).&lt;/p&gt;
&lt;p&gt;We could combine:&lt;/p&gt;
&lt;p&gt;TagSoup (or maybe HTMLParser) to generate SAX events&lt;br /&gt;
DOMHandler to build a DOM from the SAX events&lt;br /&gt;
Rhino to execute any script elements we encounter&lt;/p&gt;
&lt;p&gt;with some kind of pushback InputStream to allow script&lt;br /&gt;
elements to write into the document so that any&lt;br /&gt;
additions would also be parsed by the SAX handler.&lt;/p&gt;
&lt;p&gt;It seems like the best way to do this is to process&lt;br /&gt;
pages asynchronously, and keep a "waiting list" if the&lt;br /&gt;
page has a dependency on some other URL, e.g. a child&lt;br /&gt;
FRAME, or an included javascript resource.&lt;/p&gt;
&lt;p&gt;So processing of the page would be suspended until&lt;br /&gt;
those pending URL's had been retrieved. This means that&lt;br /&gt;
we may have multiple pages being processed at one time.&lt;/p&gt;
&lt;p&gt;Finally, once there are no more "pending resources",&lt;br /&gt;
fire any "on*" events and monitor for things that&lt;br /&gt;
provide an URL.&lt;/p&gt;
&lt;p&gt;e.g. document.location.href, window.open(), etc&lt;/p&gt;
&lt;p&gt;We would probably have to provide a wrapper for&lt;br /&gt;
"document" that implements the non-standard things like&lt;br /&gt;
document.write(), etc&lt;/p&gt;
&lt;p&gt;It's a big project, but could be fun!&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Forms parser for Spider</title><link href="https://sourceforge.net/p/owasp/feature-requests/13/" rel="alternate"/><published>2005-04-13T08:40:08Z</published><updated>2005-04-13T08:40:08Z</updated><author><name>Rogan Dawes</name><uri>https://sourceforge.net/u/rogan/</uri></author><id>https://sourceforge.net84469fc0e278f8f3be6ec51813f66b0abc24f5fb</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It would be great if the spider could identify forms,&lt;br /&gt;
and make them visible in some fashion to the reviewer.&lt;/p&gt;
&lt;p&gt;Possibly even allowing the operator to populate the&lt;br /&gt;
form fields and submit the forms manually. Ideally, if&lt;br /&gt;
any of the form fields are prefilled (e.g a hidden&lt;br /&gt;
field) these values should be saved and presented to&lt;br /&gt;
the operator.&lt;/p&gt;
&lt;p&gt;Present a table of forms according to the conversation&lt;br /&gt;
in which they were seen, the method (GET/POST), the&lt;br /&gt;
URL, and a "signature" of the INPUT elements that make&lt;br /&gt;
up the form.&lt;/p&gt;
&lt;p&gt;When a row in the table is selected, populate a&lt;br /&gt;
secondary table with the parameters and any known&lt;br /&gt;
values, and allow the operator to edit the fields and&lt;br /&gt;
supply values, before submitting the form.&lt;/p&gt;
&lt;p&gt;It would be useful, but probably quite difficult, to&lt;br /&gt;
mark forms as submitted and remove them from the table&lt;br /&gt;
if we observe a "compatible" request. e.g. the method&lt;br /&gt;
and dst URL are the same, where values are pre-filled&lt;br /&gt;
in, the values are the same, etc.&lt;/p&gt;
&lt;p&gt;It might not be all that difficult, simply iterate over&lt;br /&gt;
the list of conversations, and compare them.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Annotation of conversations</title><link href="https://sourceforge.net/p/owasp/feature-requests/12/" rel="alternate"/><published>2005-04-13T08:18:16Z</published><updated>2005-04-13T08:18:16Z</updated><author><name>Rogan Dawes</name><uri>https://sourceforge.net/u/rogan/</uri></author><id>https://sourceforge.netf323947f48cec1b3ec397b6c2ba495b6e1ac4c57</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It could be really handy to have annotation of&lt;br /&gt;
conversations, so that one has an idea of what was&lt;br /&gt;
going on when that conversation happened.&lt;/p&gt;
&lt;p&gt;This is probably most relevant to the proxy, for&lt;br /&gt;
example, when clicking on a link, and having 10 or more&lt;br /&gt;
conversations result, it is useful to annotate the&lt;br /&gt;
first as the link that was clicked on, and then the&lt;br /&gt;
rest are "subsequent" to that click, and as a result of it.&lt;/p&gt;
&lt;p&gt;Annotating the next "click" will then help to&lt;br /&gt;
reconstruct the flow of the app at a later time.&lt;/p&gt;
&lt;p&gt;Suggestion: Use the "ANNOTATION" conversation property&lt;br /&gt;
to store the comment.&lt;/p&gt;
&lt;p&gt;Create a text field below the conversation table that&lt;br /&gt;
is populated using this property of the selected&lt;br /&gt;
conversation. If 0 or many conversations are selected,&lt;br /&gt;
this text field becomes uneditable, otherwise,&lt;br /&gt;
modifications to the text field are stored as the&lt;br /&gt;
ANNOTATION property for the selected conversation.&lt;/p&gt;
&lt;p&gt;It would also be really helpful if you could "annotate&lt;br /&gt;
in advance" for conversations that the proxy will add&lt;br /&gt;
to the framework.&lt;/p&gt;
&lt;p&gt;A text field in the proxyplugin would be read and&lt;br /&gt;
cleared each time a conversation is fetched by the&lt;br /&gt;
proxy. If the text field is not empty, the text is&lt;br /&gt;
saved as the annotation of the conversation being&lt;br /&gt;
processed.&lt;/p&gt;
&lt;p&gt;This could eventually be extended for Java 1.5 to have&lt;br /&gt;
a "stays on top" window (probably without any&lt;br /&gt;
decoration at all) that you could simply type into,&lt;br /&gt;
before doing an operation in your browser. i.e. with a&lt;br /&gt;
"Float/Capture annotation input box" button somewhere.&lt;/p&gt;
&lt;p&gt;Speak to Rogan if this sounds like something you could do.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Improvements to the Conversation Viewer</title><link href="https://sourceforge.net/p/owasp/feature-requests/11/" rel="alternate"/><published>2005-04-13T08:07:05Z</published><updated>2005-04-13T08:07:05Z</updated><author><name>Rogan Dawes</name><uri>https://sourceforge.net/u/rogan/</uri></author><id>https://sourceforge.net976cf9db89ada4e15ee37ec7153314b0331fb052</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Anyone with reasonable Swing skills could improve the&lt;br /&gt;
conversation panels. For example, to make them resize&lt;br /&gt;
better, set proper minimum sizes, etc.&lt;/p&gt;
&lt;p&gt;General tweaking to make the UI a bit friendlier.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Flash parser</title><link href="https://sourceforge.net/p/owasp/feature-requests/10/" rel="alternate"/><published>2005-04-13T08:04:26Z</published><updated>2005-04-13T08:04:26Z</updated><author><name>Rogan Dawes</name><uri>https://sourceforge.net/u/rogan/</uri></author><id>https://sourceforge.net873ab012e511441eb14bcf79111f7b0a80883b67</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;WebScarab could benefit from a flash parser that&lt;br /&gt;
extracts links. An parser already exists in Metis&lt;/p&gt;
&lt;p&gt;com.iv.flash parser.&lt;/p&gt;
&lt;p&gt;See FlashFileInfoGetter.java for an example&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>implement WebScarab connection latency settings</title><link href="https://sourceforge.net/p/owasp/feature-requests/9/" rel="alternate"/><published>2005-03-23T19:58:23Z</published><updated>2005-03-23T19:58:23Z</updated><author><name>Scott Hasse</name><uri>https://sourceforge.net/u/shasse/</uri></author><id>https://sourceforge.nete9597512097f14d597a2d7125c24eafc4e773657</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The ability for WebScarab connection throughput&lt;br /&gt;
limiting is wonderful.  However, it would help testing&lt;br /&gt;
efforts even more if we were able to configure latency&lt;br /&gt;
settings for both incoming and outgoing HTTP requests.&lt;br /&gt;
This would help simulate, for instance, satellite&lt;br /&gt;
connections that use a telephone line for sending requests.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Scott&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>reference struts-validator and stinger in Guide</title><link href="https://sourceforge.net/p/owasp/feature-requests/8/" rel="alternate"/><published>2004-03-12T11:54:34Z</published><updated>2004-03-12T11:54:34Z</updated><author><name>Ralf Hauser</name><uri>https://sourceforge.net/u/ralfhauser/</uri></author><id>https://sourceforge.net76549891c29b20aeaa2d658ec2512547023e0229</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi, the OWASP Guide is an excellent starter for Web&lt;br /&gt;
Security. Congrats!&lt;br /&gt;
In chapter 10 on "Data Validation" (or the upcoming&lt;br /&gt;
Java chapter), I suggest to add pointers to validation&lt;br /&gt;
frameworks such as &lt;a href="http://aspectsecurity.com/stinger/" rel="nofollow"&gt;http://aspectsecurity.com/stinger/&lt;/a&gt;&lt;br /&gt;
and&lt;br /&gt;
&lt;a href="http://jakarta.apache.org/struts/userGuide/dev_validator.html" rel="nofollow"&gt;http://jakarta.apache.org/struts/userGuide/dev_validator.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;P.S.: Especially since DoS has become a member of OWASP&lt;br /&gt;
top ten, do not forget to mention their limitations -&lt;br /&gt;
i.e. that they get often get called "late" (only after&lt;br /&gt;
finishing uploading e.g. illegitimate 2MB for a form&lt;br /&gt;
field specified to only hold 200 characters; for&lt;br /&gt;
example tomcat hands off to such "application level"&lt;br /&gt;
validation after finishing "http" processing - see&lt;br /&gt;
also:&lt;br /&gt;
&lt;a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27062" rel="nofollow"&gt;http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27062&lt;/a&gt;&lt;br /&gt;
and related out-of-memory conceptual open ends of&lt;br /&gt;
tomcat&lt;br /&gt;
&lt;a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27143\" rel="nofollow"&gt;http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27143\&lt;/a&gt;)&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>