To speed up filtering, hcxhashtool is running only one stage. Therefore less common filter option combinations which do not make sense are ignored.
In that case, it is mandatory to run hcxhashtool a second time (third time, ...) on the output of the task before.
Purpose of ESSID filtering is to get benefit of reuse of PBKDF2, which will speed up hashcat.
Filtering e.g. ESSIDs by occurrence of characters (e.g. x digit, digit, alfa...) doesn't make sense, because it will not speed up hashcat task.
BTW:
It is mandatory that the user knows what he is doing (analytical competencies):
- knowledge of radio technology and electromagnetic-wave engineering (RF power vs. antenna gain vs. range)
- detailed knowledge of 802.11 protocol (AUTHENTICATION sequences)
- detailed knowledge of key derivation functions (PBKDF2 and HMAC functions)
- detailed knowledge of Linux (driver specification, monitor mode, bash)
Otherwise the result is always unexpected.
e.g. as mentioned here:
https://hashcat.net/forum/thread-10441-p...l#pid53995
This applies in particular if you decide to use hcxdumptool/hcxtools, because they are analysis tools.
There is no script inside hcxtools that replaces this knowledge.
In that case, it is mandatory to run hcxhashtool a second time (third time, ...) on the output of the task before.
Purpose of ESSID filtering is to get benefit of reuse of PBKDF2, which will speed up hashcat.
Code:
--essid-group
--essid
--essid-list
Filtering e.g. ESSIDs by occurrence of characters (e.g. x digit, digit, alfa...) doesn't make sense, because it will not speed up hashcat task.
BTW:
It is mandatory that the user knows what he is doing (analytical competencies):
- knowledge of radio technology and electromagnetic-wave engineering (RF power vs. antenna gain vs. range)
- detailed knowledge of 802.11 protocol (AUTHENTICATION sequences)
- detailed knowledge of key derivation functions (PBKDF2 and HMAC functions)
- detailed knowledge of Linux (driver specification, monitor mode, bash)
Otherwise the result is always unexpected.
e.g. as mentioned here:
https://hashcat.net/forum/thread-10441-p...l#pid53995
This applies in particular if you decide to use hcxdumptool/hcxtools, because they are analysis tools.
There is no script inside hcxtools that replaces this knowledge.