summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFeideus <erwan.ulrich@gmail.com>2018-09-18 15:08:15 +0200
committerFeideus <erwan.ulrich@gmail.com>2018-09-18 15:08:15 +0200
commitec02a75317db983960d066606a552da6bd4e06a2 (patch)
treec2ad8ff637c2955e8609d017ac8caa48caf2fccc
parentb245a8199e5a26a7e9c4037e8c73a224862c4c59 (diff)
downloadschemafuzz-ec02a75317db983960d066606a552da6bd4e06a2.tar.gz
schemafuzz-ec02a75317db983960d066606a552da6bd4e06a2.tar.bz2
schemafuzz-ec02a75317db983960d066606a552da6bd4e06a2.zip
minor adjustements on doc
-rw-r--r--docs/Documentation.pdfbin1088803 -> 1091405 bytes
-rw-r--r--docs/Documentation.tex8
-rw-r--r--docs/PersonnalExperience.tex14
3 files changed, 17 insertions, 5 deletions
diff --git a/docs/Documentation.pdf b/docs/Documentation.pdf
index 95b945b..bcab2e8 100644
--- a/docs/Documentation.pdf
+++ b/docs/Documentation.pdf
Binary files differ
diff --git a/docs/Documentation.tex b/docs/Documentation.tex
index 2f28466..e90d0c2 100644
--- a/docs/Documentation.tex
+++ b/docs/Documentation.tex
@@ -59,9 +59,9 @@ It is hoped that it will give more insights on the philosophy and the drive that
\bigskip
-Le concept du Fuzz testing est le resultat de la soumission de données inapropriées à un programme cible. Ce concept est utilisé au cours du developement dans le but de reveler les erreurs d'implementation ainsi que les failles de securité dans le code source d'un projet informatique. Plusieurs approches differentes peuvent permettrent d'atteindre ce but telles que la concentration sur un type particuler de données ou encore l'utilisation de concepts externes comme l'apprentissage machine. Ce projet est une implementation de la strategie du fuzz testing en se concentrant sur la gestion d'objets issues d'une base de données \\*
-Le but de cette documentation est de fournir une introduction au concept du fuzz testing et de decrire précisement un exemple d'implémentation. \\*
-Nous nourissons l'espoir qu'elle apportera de plus amples détails sur la philisophie et sur les motivation qui soutiennent ce projet ainsi que sur le désign de l'outil SchemaFuzz pour ses utilisateurs et contributeurs.
+Le concept du Fuzz testing est le résultat de la soumission de données inappropriées à un programme cible. Ce concept est utilisé au cours du developpement dans le but de reveler les erreurs d'implementation ainsi que les failles de sécurité dans le code source d'un projet informatique. Plusieurs approches différentes peuvent permettre d'atteindre ce but telles que la concentration sur un type particuler de données ou encore l'utilisation de concepts externes comme l'apprentissage machine. Ce projet est une implementation de la stratégie du fuzz testing en se concentrant sur la gestion d'objets issus d'une base de données \\*
+Le but de cette documentation est de fournir une introduction au concept du fuzz testing et de décrire précisément un exemple d'implémentation. \\*
+Nous nourrissons l'espoir qu'elle apportera de plus amples détails sur la philosophie et sur les motivations qui soutiennent ce projet ainsi que sur le design de l'outil SchemaFuzz pour ses utilisateurs et contributeurs.
\section{Introduction}
@@ -73,7 +73,7 @@ This tool is still at an alpha state; its development will is still in progress
\clearpage
- \section{Context and Perimeter}
+ \section{Context and Perimeter}
\subsection{Context}
SchemaFuzz uses the principle of "fuzz testing" or "fuzzing" to help find out which are the weak code paths of one's project. It is usually defined as:
diff --git a/docs/PersonnalExperience.tex b/docs/PersonnalExperience.tex
index 3a565c6..d867cb2 100644
--- a/docs/PersonnalExperience.tex
+++ b/docs/PersonnalExperience.tex
@@ -1,9 +1,21 @@
-
\section{Internship organization}
\subsection{Introduction}
This section is meant to be added to the University version of this documentation. It will be written as Erwan Ulrich and will focus on the different aspects of the organization of the project. The following text will also be written with a more personal and more critical point of view as a mean of self analyze.
+ \subsection{The BFH and The GNU Taler package}
+My internship was supervised by both the Berner Fachhochschule (Bern University of Applied Sciences) and Christian Grothoff who is the maintainer for multiple GNU packages among which the GNU Taler package.
+
+Founded in 1997, is a non-profit public higher education institution located in the large town of Bern (population range of 50,000-249,999 inhabitants). Berner Fachhochschule (BFH) is a medium-sized (uniRank enrollment range: 6,000-6,999 students) coeducational higher education institution. Berner Fachhochschule (BFH) offers courses and programs leading to officially recognized higher education degrees such as bachelor degrees in several areas of study.
+
+GNU is a politically engaged, free software and mass-colaboration project that was created by Richard Stallman in 1983 at the MIT. It aims to produce and distribute free softwares to help citizens keep control over their computers and digital activities. Most softwares produced by the GNU project share the same GNU General Public License that give rights for it to be run, shared, studied and modified. This subscribes to the global philosophy and political engagements of the GNU project.
+
+Christian Grothoff is professor at the BFH as well as the main developer and team leader of the GNU Taler package.
+The Taler project is an electronic payment system under development at Inria.
+It provides accountability to ensure business operate legally, while also respecting civil liberties of citizens. Taler is based on open standards and free software.
+Taler was built with the goal of fighting corruption and supporting taxation. With Taler, the receiver of any form of payment is easily identified, and the merchant can be compelled to provide the contract that was accepted by the customer. Governments can use this data to tax businesses and individuals based on their income, making tax evasion and black markets less viable.
+
+I was positioned under the supervision of Mr Grothoff with the task of conceiving, coding and deploying a tool that would help secure database exchanges as a part of the Taler payment system development.
\subsection{Calendars}
The SchemaFuzz project has had since its genesis a quiet clear view of how the development should evolve. The desired features have been discussed and the big picture had been designed to fit the time that the main developer had for his work at this position.