joaohenggeler / uc-masters-software-vulnerabilities Goto Github PK

• The page is from the main repository: https://github.com/joaohenggeler/estagio-software-vulnerabilities-2020-2021
• It should list the main goals of this work
• It should have the list of authors responsible for that

(Check an example here: https://github.com/nmsa/tma-framework)

Compile the mozilla source code in order to be able to run SATs:
https://developer.mozilla.org/pt-BR/docs/Mozilla/Developer_guide/Intrucoes_Build

We should aim at compiling old versions of the source code, so we can enrich the database with the SAT alerts.
It would be better if we have the code compiled in a Virtual Machine, so we can replicate it easier.

Implement the automated collection mechanism proposed in the first step of the methodology. The reported vulnerabilities should be collected for the five C/C++ projects.

The tables that were imported from the original dataset use MyISAM as their storage engine. In MySQL 5.5 and later, the default is InnoDB. Since the Python scripts don't specify an engine when creating any new tables, these will use InnoDB while the tables from the original dataset use MyISAM.

The InnoDB engine provides foreign key referential integrity constraints, while MyISAM does not. If you try to define a foreign key when creating a new table (which will use InnoDB by default), you won't be able to relate it to a column in a table that uses MyISAM. For example, when creating a relationship between the table 'alert' (InnoDB) and 'patches' or 'files_*' (MyISAM).

For more information on MySQL storage engines, refer to this page.

How important is this issue? Should only one type of engine be used (use MyISAM for new tables, or convert any old ones to InnoDB)?