Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OWTF loses *EVERYTHING* on unexpected reboot #421

Closed
viyatb opened this issue May 1, 2015 · 1 comment
Closed

OWTF loses *EVERYTHING* on unexpected reboot #421

viyatb opened this issue May 1, 2015 · 1 comment
Assignees
Projects

Comments

@viyatb
Copy link
Member

viyatb commented May 1, 2015

@7a : While leaving 2 w3af processes running overnight, it probably crashed the VM, because all apps were closed incorrectly, upon reboot, OWTF is COMPLETELY UNABLE to show ANY of the following (EVEN IF started from the same directory):

  • Targets
  • Rankings
  • Workers
  • Worklist

In essence, when this happens, ABSOLUTELY EVERYTHING is lost and the ONLY hope for the pentester is to use the files saved to disk in the owtf_review directory.

This is unacceptable and should be fixed ASAP.

UPDATE:
Workaround use the filesystem OWTF service and use the built-in “visited link” browser functionality as a “has viewed tool output vs. has not”.

i.e. http://127.0.0.1:8010/ ← lists tool output in a relatively friendly way

@viyatb viyatb added this to the OWTF Quality Release milestone Feb 1, 2016
@viyatb viyatb self-assigned this Feb 1, 2016
@viyatb viyatb modified the milestone: OWTF Quality Release May 24, 2016
@viyatb viyatb added this to Backlog in owtf Jul 8, 2017
@viyatb
Copy link
Member Author

viyatb commented Mar 18, 2018

This has been fixed. The root cause are a few plugins which halt the execution of other plugins in the queue and OWTF loses all data for the halted plugin.

@viyatb viyatb closed this as completed Mar 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
owtf
Backlog
Development

No branches or pull requests

1 participant