You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dpulse-docs/docs/config.md
+23-11Lines changed: 23 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,10 @@ As you can understand, configuration file is a file that contains certain parame
6
6
7
7
Configuration file (config.ini) located in 'serivce' folder, which is located inside DPULSE root folder. Default config.ini file generated with your first DPULSE start and it looks like that:
As you can see, config file built with sections, which represent separated DPULSE functions. Lets describe these sections and parameters:
53
59
54
-
[LOGGING] is section for log file configuration, and it's only parameter - log_level - describes log level for Python's logging library. More information about logging levels you [can find here](https://docs.python.org/3/library/logging.html#logging-levels)
55
-
56
-
[CLI VISUAL] is section for command line interface configuration. It's parameters are preview_color (determines color for big DPULSE logo on start) and font (determines font for big DPULSE logo on start). More about these parameters you [can find here](http://www.figlet.org/)
57
-
58
-
[DORKING] is section for dorking process configuration. It's parameters are dorking_delay (secs) (determines delay between dorking steps) and delay_step (determines how many requests will be in one step)
59
-
60
-
[SNAPSHOTTING] is section for snapshotting process configuration. It's parameters are installed_browser (determines your installed browser to be used in screenshot snapshotting), opera_browser_path (path to opera.exe, only in case if you want to use this browser for screenshot snapshotting), wayback_retries (determines amount of retries for getting exact Wayback snapshot in case of errors) and wayback_req_pause (determines pause in seconds between requests to Wayback archive)
61
-
62
-
[USER-AGENTS] is section for user-agents list, which is used in Google Dorking (user-agents are randomly swapped in process)
63
-
64
-
[PROXIES] is section for configuring proxies usage in Dorking, and it's only parameter - proxies_file_path - used to determine path to .txt file (path should be full with //-style slashes) which contains list of proxies (one proxy per row)
60
+
| SECTION | PARAMETER | POSSIBLE VALUES | COMMENT |
|[HTML_REPORTING]| template | modern / legacy | Determines which HTML report template should be used while creating report itself. Modern contains more features like analytics, graphs and interactive features, while legacy is not supported anymore but may be convenient choice for someone |
63
+
|[HTML_REPORTING]| delete_txt_files | y / n | Modern HTML report template contains text boxes for the content of robots.txt and sitemap.xml files, so maybe you won't need them as .txt files. Y parameter makes DPULSE delete this files from report folder, and N parameter leave everything as is |
64
+
|[LOGGING]| log_level | See [here](https://docs.python.org/3/library/logging.html#logging-levels)| Determines how much technical info about program's execution will be logged in journal.log file |
65
+
|[CLI_VISUAL]| preview_color | See [here](https://pypi.org/project/colorama/)| Determines the color of DPULSE ASCII art's color |
66
+
|[CLI_VISUAL]| font | - | - |
67
+
|[DORKING]| dorking_delay (secs) | Any integer value >=0 | Determines how much time browser will be on pause between dorks |
68
+
|[DORKING]| delay_step | Any integer value >0 | Determines the amount of dorks browser should handle before activating delay |
69
+
|[DORKING]| full_path_to_browser | Full path to your browser's executable file with \ symbol as a separator | Determines which browser will be used for Dorking |
70
+
|[DORKING]| browser_mode | headless / nonheadless | Sets which browser mode will be used during Dorking process (headless means that browser window won't be opened, so nonheadless means that browser window will be opened every new dork, and actually it gives better results with TOS and Captcha bypassing) |
|[SNAPSHOTTING]| opera_browser_path | Full path to your Opera.exe / None | Enter your Opera.exe path only if you decided to use Opera for screenshot snapshotting, in other cases - leave it as None |
73
+
|[SNAPSHOTTING]| wayback_retries | Any integer value >0 | Determines how many retries DPULSE will make before abandoning inaccessible Wayback link |
74
+
|[SNAPSHOTTING]| wayback_req_pause | Any integer value >0 | Determines how many seconds DPULSE will wait between different retries to an inaccessible Wayback link |
75
+
|[USER-AGENTS]| agent_N | Any default user-agent string | User-agent are used to try bypassing TOS and Captcha when Dorking domain |
76
+
|[PROXIES]| proxies_file_path | Full path to your proxies .txt file | Determines path to .txt file with "//" symbols as a separator which contains list of proxies (one proxy per row) |
Copy file name to clipboardExpand all lines: docs/dpulse-docs/docs/index.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,4 +14,6 @@ DPULSE is a software solution for conducting OSINT research in relation to a cer
14
14
15
15
4.***API scan:*** extended domain research function with prepared functions for 3rd party APIs usage. Currently DPULSE supports VirusTotal API (for brief domain information gathering) and SecurityTrails API (deep subdomains and DNS enumeration)
16
16
17
+
5.***Snapshotting:*** extended domain research function which copys domain's home page content in various ways: by screenshotting it (screenshot snapshot), by HTML copying (HTML snapshot) and by finding and downloading previous versions (Wayback Machine snapshot)
18
+
17
19
Finally, DPULSE compiles all found data into an easy-to-read HTML or XLSX report by category. It also saves all information about scan in local report storage database, which can be restored later.
0 commit comments