-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Cmdline Whitelist Feature #110
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
Conversation
I’m confused isn’t a whitelist suppose to be targets that you would not want to attack? Hence the name whitelist |
Also, you missed adding the whitelist in the terminal prompts |
Whitelist in this case would be like a character whitelist or pentest scope whitelist - a list of items allowed through, all others would be blocked. Regarding the terminal prompts, I'm planning on adding that next. |
Okay. I like it I’ll merge it once you get the whitelist added to the terminal, that way we can get it all done in one merge |
Added |
Here da399f4#diff-2b864a0c646b108a48e41ac008b31aa2R172 If a space is provided it will fail add an |
Updated to include "and not whitelist_file.isspace():". "or not..." apparently broke it when supplied a space. |
Merging |
This PR includes the whitelist_wash() function, the cmdline argument, as well as the modification for the exploiter object call. If there is a more preferred way of implementing this feature, let me know. Currently it only works via cmdline, I'm planning on adding options to the interactive prompt next.
I originally thought of implementing this as a default file with its path specified in lib.settings (like the hosts file) but thought it would be better if it required the user to specify at run time.