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
Hello, Alex.
In some cases we may have SSID match some pattern. We know default passwords for this pattern match some template.
Based on that we may say "For this SSID pattern try to use this rule" -- this is first request: make able to use particular rules against SSIDs match pattern. Or BSSIDs match pattern (eg vendor used default passwords so by BSSIDs can filter those devices).
Second part: Make possible people defining and submitting their own rules, and target+rules combinations.
They can be stored and based on the efficiency prioritized by the system, like dicts has stats right now.
The text was updated successfully, but these errors were encountered:
Hi, thanks for the suggestions!
Often, we have the original SSID with a user-defined password and vice versa. Also, just bruting the default keyspace can prove ineffective in case we already have broken the default algorithm reversed.
Having said that, I think we have cases, where such attacks will be fruitful - IMEI based ones, NETGEAR/Spectrum and others.
Currently working on functionality to add default keyspaces info to wpa-sec and this can be extended.
As for the second part, you can add options to the cracker, e.g. --co="-r rules/my_custom.rule", which will do the trick in case you have more than one GPU.
Hello, Alex.
In some cases we may have SSID match some pattern. We know default passwords for this pattern match some template.
Based on that we may say "For this SSID pattern try to use this rule" -- this is first request: make able to use particular rules against SSIDs match pattern. Or BSSIDs match pattern (eg vendor used default passwords so by BSSIDs can filter those devices).
Second part: Make possible people defining and submitting their own rules, and target+rules combinations.
They can be stored and based on the efficiency prioritized by the system, like dicts has stats right now.
The text was updated successfully, but these errors were encountered: