-
Notifications
You must be signed in to change notification settings - Fork 788
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
2787 merge vulnerability and brute force exploiter config #2796
2787 merge vulnerability and brute force exploiter config #2796
Conversation
5a1a008
to
c8cf86d
Compare
Codecov ReportBase: 64.21% // Head: 64.19% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #2796 +/- ##
===========================================
- Coverage 64.21% 64.19% -0.03%
===========================================
Files 407 407
Lines 11581 11573 -8
===========================================
- Hits 7437 7429 -8
Misses 4144 4144
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Waiting on BB test fixes
The separation between brute force and vulnerability exploiters was based on the use case of "vulnerability scanning", which is no longer Infection Monkey's main goal. Ultimately, users should be able to configure the order that exploiters run in. While the UI doesn't allow this at the moment, the configuration can be manipulated manually to achieve this. However, vulnerability exploiters always run before brute force exploiters. In other words, this separation reduces the configurability of the system. By merging these into a single list of exploiters, we allow the user to have total control over the order in which exploiters are run. Issue #2787 PR #2789
20257f5
to
3db41de
Compare
What does this PR do?
Fixes #2787.
PR Checklist
Testing Checklist