mrleelee68 / android-thomson-key-solver

Automatically exported from code.google.com/p/android-thomson-key-solver
0 stars 0 forks source link

Ono longer ssid #18

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
I've seen a longer ono ssid which hasn't been reconized.

ONO_WEP regex should be changed from:
"[Pp]1[0-9]{6}0{4}[0-9]"
to this (i have not verified but i think it is correct):
"[Pp]1[0-9]{6,7}0{4}[0-9]"

Original issue reported on code.google.com by LatinSuD@gmail.com on 13 Jul 2011 at 1:06

GoogleCodeExporter commented 8 years ago
Sorry the problem is not exactly length.
One of the digits assumed to be always 0, but it doesn't have to.

ONO_WEP regex should be changed from:
"[Pp]1[0-9]{6}0{4}[0-9]"
to this:
"[Pp]1[0-9]{7}0{3}[0-9]"

Original comment by LatinSuD@gmail.com on 13 Jul 2011 at 1:27

GoogleCodeExporter commented 8 years ago
Even more. I've seen these SSID in the wild:

p1212450001
p12385209003
p14053170005
p151759470011
p120637930016
p122699080012
p122725310021
p123112490010
p123716600010
p123987390020
p140386650030
p15436318-0016
p15484233-0002

Some of them could be considered errors or anomalies.
I'd still allow the 2 last digits to be non-zero.
"[Pp]1[0-9]{7}0{2}[0-9]{2}"
Or even also allow a more flexible length:
"[Pp]1[0-9]{5,7}0{2}[0-9]{2}"

Original comment by LatinSuD@gmail.com on 13 Jul 2011 at 1:33

GoogleCodeExporter commented 8 years ago
Hmmm, even if different Ono are seen, how can we know that the algorithm used 
will work?

Original comment by ruka.araujo on 15 Jul 2011 at 10:42

GoogleCodeExporter commented 8 years ago
No response.

Original comment by ruka.araujo on 8 Jul 2012 at 8:53