[GNUnet-SVN] [taler-schemafuzz] branch master updated: Some more text

[gnunet]

This is an automated email from the git hooks/post-receive script.

erwan-ulrich pushed a commit to branch master
in repository schemafuzz.

The following commit(s) were added to refs/heads/master by this push:
     new 4f6a9db  Some more text
4f6a9db is described below

commit 4f6a9dbeea3ce03e2dcb16f542e311a739fd6f3d
Author: Feideus <address@hidden>
AuthorDate: Mon Aug 6 19:14:43 2018 +0200

    Some more text
---
 Documentation.tex | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)

diff --git a/Documentation.tex b/Documentation.tex
index 7448c17..fcc76c8 100755
--- a/Documentation.tex
+++ b/Documentation.tex
@@ -114,6 +114,36 @@ To do so, the software has a way to tranfert the mutation 
from a child to its pa
                                
                        \subsubsection{Mutations}
                                \paragraph{Creating malformed data}
+\\*
+As the goal of running this tool is to submit unexpected or invalid data to 
the target software it is necessary to understand what t
+Fuzzing a complex type such a timestamp variable has nothing to do with 
fuzzing a trivial boolean. In practice, A significant part o
+and this matter could absolutly be the subject of a more abstract work. We 
focused here on a very simple approach (as a first step.
+After retrieving the current row being fuzzed (may it be a new row or a 
previously fuzzed row), the algorithm explores the different
+The algorithm then builds the possible modification for each of the fields for 
the current row.
+At the moment, the supported types are : % add a list of the supported types.
+More primitives types will be added in the future.
+The possible modifications that this tool can produce at the moment are : % 
add complete list of the modifications that CAN be gener$
+                               \begin{itemize}
+                                       Number Types :
+                                       \item Extreme values (0-32676 (int) 
etc...)
+                                       \item Random value (0<value<32676 (int) 
etc...)
+                                       \item Increment/Decrement the existing 
value (332 -> 333 OR 332 -> 331)
+                                       String Types :
+                                       \item Change string to "aaa" ("Mount 
Everest" -> "aaa")
+                                       \item Increment/Decrement ASCII 
character at a random position in the string ("Mount Everest" -> "Mount 
Fverest")
+                                       Boolean
+                                       \item Swaping the existing value (F -> 
T OR T -> F)
+                                       Date Types : (! IMPLEMENTED BUT NOT 
FULLY FUNCTIONNAL)
+                                       \item Increment/Decrement date by 1 
day/minutes depending on the precision of the date
+                                       \item Set date to 00/00/0000
+                               \end{itemize}
+Obviously, these "abnormal" values might in fact be totally legit in some 
cases. in that case the analyzer (see dedicated section) w
+                               \\*
+                               \paragraph{Sql handling}
+                               \paragraph{Injecting}
+SchemaFuzz builds the SQL statement that will be injected in the database. As 
every DBRMS has its own synthax only PostGresSql synta
+The statement is built to target the row as precisely as possible, meaning 
that it uses all of the non fuzzed values from the fuzzed
+
                                \paragraph{Sql handling}
                                \paragraph{Injecting}
                                \paragraph{Do/Undo routine}

-- 
To stop receiving notification emails like this one, please contact
address@hidden