I'm using the lastest version 2.3.0 on a CentOS box. When using a previous version (2.2.1?) the scan completed in around 2 hours, however with 2.3.0 the scan is up to 16 hours and still going. This is just the link scanning stage and not the attack stage.
Please let me know if I can send you any specific logs to help with the issue.
Log in to post a comment.