OWASP Hatkit Datafiddler Project - Revision history

Kait Disney-Leugers at 19:56, 23 January 2014

2014-01-23T19:56:46Z

Kait Disney-Leugers at 18:37, 23 January 2014

2014-01-23T18:37:34Z

Kait Disney-Leugers at 02:06, 23 January 2014

2014-01-23T02:06:02Z

Martin Holst Swende at 07:17, 14 May 2011

2011-05-14T07:17:17Z

Martin Holst Swende at 18:53, 3 May 2011

2011-05-03T18:53:36Z

Martin Holst Swende at 18:33, 3 May 2011

2011-05-03T18:33:50Z

Martin Holst Swende at 18:25, 3 May 2011

2011-05-03T18:25:28Z

Martin Holst Swende at 19:22, 11 April 2011

2011-04-11T19:22:28Z

Martin Holst Swende at 19:31, 10 April 2011

2011-04-10T19:31:46Z

Martin Holst Swende at 19:29, 10 April 2011

2011-04-10T19:29:22Z

@@ Line 4: / Line 4: @@
 ! width="500" align="center" | <br>
 |-
-| align="right" | [[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/Category:OWASP_Project]]
+| align="right" | [[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Inactive_Projects]]
 | align="right" |

@@ Line 1: / Line 1: @@
-[[Image:OWASP Inactive Banner.jpg|1155px]]
+{|
 ==== Main  ====
 [[File:hatkit-datafiddler-logo.png]]

← Older revision		Revision as of 02:06, 23 January 2014
Line 1:		Line 1:
		+	[[Image:OWASP Inactive Banner.jpg\|1155px]]
	==== Main ====		==== Main ====
	[[File:hatkit-datafiddler-logo.png]]		[[File:hatkit-datafiddler-logo.png]]

@@ Line 73: / Line 73: @@
 == What to show: Database Filtering ==
-See the database filtering tab.
+Please see the tab called "Database Filtering".
-== How to show it  ==
-Todo
+== How to show it ==
 === Transformers ===
-Todo
+Once objects or part of objects have been loaded into variables <pre>v1 ... vn</pre>, it is possible to perform operations on these objects using python. It is possible to use arbitrary python statemenets, but a set of so called 'transformers' are implemented specifically for the purpose of analysing http traffic:
 ==== Aggregation ====
 Todo

@@ Line 112: / Line 112: @@
 If you write a good filter, you can click "Save as" so you don't have to retype it next time. A good set of standard filters for different purposes is planned for inclusion at a later stage. In the meantime, if you write any handy filters you are encouraged to post them to the datafiddler mailing list.
 ==== Development ====
-Todo
+If you don't already use Mercurial, first do
-=== Getting the source code ===
+ sudo apt-get install hg
-Todo
+Then fetch the code:
 ==== Project About ====
 {{:Projects/OWASP Hatkit Datafiddler Project | Project About}}

@@ Line 84: / Line 84: @@
 The table view (and the upcoming third-party view) supports database filtering. A database filter is a set of expressions which are evaluated in the database, and determines which items are returned in the result of a given query. '''Note:''' This is much like the WHERE-part of an SQL statement (on steroids).
-[[Image:hatkit-datafiddler-datafilter.png]]
+== Native filters ==
-The image above contains two tabs.  One is for 'native' expressions, where the syntax is a standard javascript object notation. Example below: a filter that returns only pages where (url-)parameters were present in the request.
+[[Image:hatkit-datafiddler-datafilter-native.png]]
-[[Image:hatkit-datafiddler-datafilter-native.png]]
+It is also possible to use regular expression in the filters. For further information about how filtering works, and examples of operators which may be used, see the [http://www.mongodb.org/display/DOCS/Advanced+Queries MongoDB documentation]
 In the other tab, you can enter javascript expressions (a V8 engine is embedded inside the database). Simply enter a function which returns true if the object should be returned, false otherwise. Example below: a filter which only returns items where one of the request (url-) parameters were present in the html response - i.e reflected content.
@@ Line 99: / Line 111: @@
 If you write a good filter, you can click "Save as" so you don't have to retype it next time. A good set of standard filters for different purposes is planned for inclusion at a later stage. In the meantime, if you write any handy filters you are encouraged to post them to the datafiddler mailing list.
 ==== Development ====
 Todo

@@ Line 32: / Line 32: @@
 [[Image:hatkit-datafiddler-tabledata-settings-2.png|thumb|The tabledata settings also has filters]]
 [[Image:hatkit-datafiddler-tabledata-settings-3.png|thumb|The filters can be arbitrary javascript expressions]]
 == Settings ==
 If you select Settings, you will be met by the settings-window. This window gives you tools to define what is displayed in the table view to suit your current task.
@@ Line 37: / Line 40: @@
 <blockquote>The section below is pretty technical. You don't '''have''' to know python or javascript to use this tool, Datafiddler comes with predefined expressions and views that you can use. When you learn the ropes a bit, you can just make modifications to these and you should be fine.  </blockquote>
-On the left side, there are '''variables'''. For each object which is fetched from the database, these expressions determines exactly what parts are fetched and places these parts, into python variables with the names '''v0''' and onward.
+On the left side, there are '''variables'''. For each object which is fetched from the database, these expressions determines exactly what parts are fetched and places these parts, into python variables with the names '''v0''' and onward. On the right side, there are the actual definitions of the columns that are shown in the table. These column definitions are python expressions which are evaluated at display-time, and are therefore able to either display a variable directly or perform operations on them and display the result.
 For example, a database object stored by Hatkit Proxy always contain these fields:

@@ Line 49: / Line 49: @@
 This means that this object introspection can be performed '''either''' inside the database - which is using javascript, '''or''' in the application itself, using python. Example:
 <pre>
-v0 = request.headers.Host === (v0 = request)['headers']['Host]
+v0 = request.headers.Host ==> v0 : "foobar.com"
 </pre>