Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A arachni
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 125
    • Issues 125
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arachni - Web Application Security Scanner Framework
  • arachni
  • Issues
  • #590
Closed
Open
Issue created Jun 11, 2015 by Administrator@rootContributor

Timeout appears to do nothing..

Created by: bstream

Hey!

I want to report an error and ask a question about the timeout option. Error I ran a scan with --timeout=00:01:00 so that the scan would be aborted after 1 minute. When the timeout was reached I was the message [-] Timeout has been reached, shutting down. but then the scan continued until interrupted manually or until it was finished scanning.

  • Command used: ./bin/arachni http://target/application --profile-load-filepath=custom.profile.afp --timeout=00:01:00
  • Output snippet: https://gist.github.com/bstream/31e49f0525c5b8253864

(This may be related to #587 (closed))

Question At the moment the scan will generate an error log if the timeout is reached with the contents Timeout has been reached, shutting down.. Since I supply the timeout I don't regard it as an error if it is triggered. Instead, maybe it could be indicated in the scan report, like "timeout_reached" : True/False? Or, I guess it could be reported as a potential issue in the report, since not running a full scan could mean that vulnerabilities are missed.

Assignee
Assign to
Time tracking