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
I am about to integrate dumpsterDiver in out cicd pipline at gitlab.
The way the tasks in the pipline works are that they run scripts and check the exit code to determine if the task was succesfull.
Proposal
it would be cool to have the posibility to check wether or not the "dive" was successfull. Depending on wether you use DD as security tool or hacking tool success is defined differently.
Suggestion 1
I suggest that if the tool runs through and finds something it exits with 0.
if it doesn't find anything it exits with 2.
if the code breaks it exits with code 1. (python standard i think)
therefore one can run the programm like so [ $(python DumpsterDiver.py -p .....) -ne 2]
Suggestion 2
to Position it more as a security tool another way would be:
I suggest that if the tool runs through and finds something it exits with 2.
if it doesn't find anything it exits with 0.
if the code breaks it exits with code 1. (python standard i think)
which leads to the more elegant python DumpsterDiver.py -p .....
The text was updated successfully, but these errors were encountered:
I am about to integrate dumpsterDiver in out cicd pipline at gitlab.
The way the tasks in the pipline works are that they run scripts and check the exit code to determine if the task was succesfull.
Proposal
it would be cool to have the posibility to check wether or not the "dive" was successfull. Depending on wether you use DD as security tool or hacking tool success is defined differently.
Suggestion 1
I suggest that if the tool runs through and finds something it exits with 0.
if it doesn't find anything it exits with 2.
if the code breaks it exits with code 1. (python standard i think)
therefore one can run the programm like so
[ $(python DumpsterDiver.py -p .....) -ne 2]
Suggestion 2
to Position it more as a security tool another way would be:
I suggest that if the tool runs through and finds something it exits with 2.
if it doesn't find anything it exits with 0.
if the code breaks it exits with code 1. (python standard i think)
which leads to the more elegant
python DumpsterDiver.py -p .....
The text was updated successfully, but these errors were encountered: