You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I spend some hours trying out most of the functionality of the tool and have found some unclear and broken things.
Here i would like to report about the verbosity configuration.
After some tests i could not see some difference between normal and -v mode. The normal and -v mode create the same output on the things i tested. Am i missing something?
The -vv mode display the commands the tool is using in the background. This is good for learning what is really happening in the background.
The -vvv mode had no visable difference to me from the -vv mode.
The tool does not look to stop counting the verbosity at maximum level. I tested - vvvvvvvv and so on and its just counting the reporting how many v i have written. It would be better to stop reporting such a verbosity level when there is no use out of it.
The text was updated successfully, but these errors were encountered:
I spend some hours trying out most of the functionality of the tool and have found some unclear and broken things.
Here i would like to report about the verbosity configuration.
This is how the readme explains it https://github.com/kimocoder/wifite2/blob/master/README.md?plain=1#L137
After some tests i could not see some difference between normal and -v mode. The normal and -v mode create the same output on the things i tested. Am i missing something?
The -vv mode display the commands the tool is using in the background. This is good for learning what is really happening in the background.
The -vvv mode had no visable difference to me from the -vv mode.
The tool does not look to stop counting the verbosity at maximum level. I tested - vvvvvvvv and so on and its just counting the reporting how many v i have written. It would be better to stop reporting such a verbosity level when there is no use out of it.
The text was updated successfully, but these errors were encountered: