Local Database

[vifor2]

Feature functional although it could use some improvements, but since there is less than 1 week before the end of the project @zer0x64 and me would like to get this merged ASAP. Also to cease the merge conflicts.

Scroll down for TL;DR

Changes done within this PR :

• User can input --result-format with either json or sqlite as args.
• Imports of scoutsuite-results/scoutsuite_results.js and scoutsuite-results/scoutsuite_exceptions.js are no longer in report.html by default, they are instead in a partial that is added if the user chose json in the previous point.
• scoutsuite.js now checks whether an element with the id json_format or sqlite_format exists to know which functions to call.
• When choosing SQLite all of the user's data is saved as a .db file instead of a .js file, these files being more compact as well as readable by a server.
• User can input arguments related to the server (reminder: we have decided that when the user selects SQLite he must then enter a second command to run the server, it will not be launched automatically).
• Exposed all of the data saved in the .db file to our client through CherryPy.
• Modified all .js files to follow standardJS, there are still some changes to do.
• All data except resource pages other than the first one are fetched at the start and properly viewable within the report.
• Added Back and Next buttons to change page, pressing one of those buttons disables it if you're at the page limit afterwards ([0, totalResources / pageSize - 1]), it removes the data of the previous resource from memory (run_results) and add the new page to it, it then overwrites the current template with the same one but with the new data within it.
• Page size is currently hard-coded it would be nice to give the option to the user of choosing the size but Id rather get this issue done and merged beforehand. Same with more buttons to go to first page, last page, page at a specific index, modal that tells the user to make sure his port 8000 is freed and the server is running, etc.
• I know that when we talked I said Id keep the paging buttons on both result formats but for now the buttons are disabled when viewing a report in JSON format (it should look as if nothing had happened) while the SQLite one have 2 buttons.
• Merged develop and it's new architecture into this branch (to do again it seems).

Known issues :

• Works with Firefox but not with Chrome, will discuss about this issue tomorrow with @j4v : jquery-3.3.1.min.js:2 Access to XMLHttpRequest at 'file:///home/vifor2/Documents/ScoutSuite/scoutsuite-report/inc-scoutsuite/sqlite.js' from origin 'null' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https.
• Items in the navbar are not in alphabetical order although they are in the JavaScript object (I'm bamboozled).
• Constant error when used with Firefox although it doesn't seem to actually cause any problem : XML Parsing Error: syntax error Location: file:///home/vifor2/Documents/ScoutSuite/scoutsuite-report/inc-scoutsuite/sqlite.js Line Number 1, Column 1:
• Initial data loading is a bit long compared to other providers because of the 16 regions per resource.

TL;DR

Example with Azure

While in /ScoutSuite open two terminals, in the first one type in azure --cli --serve and in the second one your usual command followed by --result-format sqlite, you can then view the report has usually excepted for the fact that you'll have buttons to load in/out new pages.

Example with GCP

Same as concept as Azure but replace the first command with gcp --user-account --serve

Example with AWS

Same concept as previous ones but replace the first command with aws --serve

[Aboisier]

Can we use const?

Suggested change

	var regionPageSize = 1
	const regionPageSize = 1

[Aboisier]

Same comment as below.

Suggested change

	var defaultPageSize = 2
	const defaultPageSize = 2

[Aboisier]

I think we'll be able to delete that when #183 will be fully merged since those won't exist anymore.