Seed found but no PIN shown

[wiire-a]

In some cases Pixiewps successfully recovers the seed but the PIN is not found.

Original issue opened here: t6x/reaver-wps-fork-t6x#35

This is more likely to happen on low end devices with small computational power, especially if far from the Access Point, and it's easy to spot:

First run Pixiewps without --force (-f). If the following message is shown:

[!] The AP /might be/ vulnerable. Try again with --force or with another (newer) set of data.

run it again with --force (-f) and you will see it exits before completing the full bruteforce (e.g. if it usually takes 20 - 30 minutes to complete, but stops just after 1 - 3 minutes).

Wrong output:

pixiewps -e d0141b15656e96b85fcead2e8e76330d2b1ac1576bb026e7a328c0e1baf8cf91664371174c08ee12ec92b0519c54879f21255be5a8770e1fa1880470ef423c90e34d7847a6fcb4924563d1af1db0c481ead9852c519bf1dd429c163951cf69181b132aea2a3684caf35bc54aca1b20c88bb3b7339ff7d56e09139d77f0ac58079097938251dbbe75e86715cc6b7c0ca945fa8dd8d661beb73b414032798dadee32b5dd61bf105f18d89217760b75c5d966a5a490472ceba9e3b4224f3d89fb2b -r 631cf02e22f5949b78c93e063c0d566c86b839c157dd43f0ebb1385b3fbb8beb89ca502b99e45ddafdc9949db8074c4d99bbad43c60ac1a633f7137dfcc64d70234ca40a342cfa64241010c46a7dcd1930b6149f11df44cb8350401f7d090dbf9c9858c6ec1c2c2816299f2cea4f204e390e232454ffdd4d977746d652b8aef6d14e317b0a8c43e647c7613444faf8a50e3f6639a200664a4058365b829fb942d6aba9c0e341712faffc3612f2df1e70e66dfb6c18c52af1b6818d0cbd2195fd -s bd677a7d1a84825189d14f8d4243ffb18cceb24dab8634b9ca0e8275b84c8bda -z 3991659d3a4deb9f7a23fd03c5dfb6a9d78e28cb48736ed32171b579c40d3014 -a da21fca948ae9d14fdc3ba31b12f4e7bbe87f7e651be6c7a57c4becc3ef93f28 -n 0a572db8608d8b7519a030946960ef41

 Pixiewps 1.1

 [-] WPS pin not found!

 [*] Time taken: 0 s 841 ms

 [!] The AP /might be/ vulnerable. Try again with --force or with another (newer) set of data.

After --force:

 Pixiewps 1.1

 [-] WPS pin not found!

 [*] Time taken: 1 s 289 ms

Correct output:

pixiewps -e d0141b15656e96b85fcead2e8e76330d2b1ac1576bb026e7a328c0e1baf8cf91664371174c08ee12ec92b0519c54879f21255be5a8770e1fa1880470ef423c90e34d7847a6fcb4924563d1af1db0c481ead9852c519bf1dd429c163951cf69181b132aea2a3684caf35bc54aca1b20c88bb3b7339ff7d56e09139d77f0ac58079097938251dbbe75e86715cc6b7c0ca945fa8dd8d661beb73b414032798dadee32b5dd61bf105f18d89217760b75c5d966a5a490472ceba9e3b4224f3d89fb2b -r 631cf02e22f5949b78c93e063c0d566c86b839c157dd43f0ebb1385b3fbb8beb89ca502b99e45ddafdc9949db8074c4d99bbad43c60ac1a633f7137dfcc64d70234ca40a342cfa64241010c46a7dcd1930b6149f11df44cb8350401f7d090dbf9c9858c6ec1c2c2816299f2cea4f204e390e232454ffdd4d977746d652b8aef6d14e317b0a8c43e647c7613444faf8a50e3f6639a200664a4058365b829fb942d6aba9c0e341712faffc3612f2df1e70e66dfb6c18c52af1b6818d0cbd2195fd -s bd677a7d1a84825189d14f8d4243ffb18cceb24dab8634b9ca0e8275b84c8bda -z 3991659d3a4deb9f7a23fd03c5dfb6a9d78e28cb48736ed32171b579c40d3014 -a da21fca948ae9d14fdc3ba31b12f4e7bbe87f7e651be6c7a57c4becc3ef93f28 -n 0a572db8608d8b7519a030946960ef41

 Pixiewps 1.1

 [*] PRNG Seed:  1441253945 (Thu Sep  3 06:19:05 2015)
 [*] PSK1:       a3:60:fc:38:36:63:52:2c:98:c7:24:16:09:83:b2:25
 [*] PSK2:       2f:4d:af:58:cf:04:cb:0d:d2:a7:03:3f:94:c9:61:95
 [*] E-S1:       64:d7:17:a1:08:e2:a1:9f:25:cf:9b:67:79:db:b4:e6
 [*] E-S2:       64:d7:17:a1:08:e2:a1:9f:25:cf:9b:67:79:db:b4:e6
 [+] WPS pin:    14987236

 [*] Time taken: 0 s 731 ms

[unlimitedpls]

I have the same issue can you fix it please

[unlimitedpls]

thanks for the update but i have still the same issue...

[wiire-a]

This issue has been fixed. You're probably misunderstanding how --force works. Try compiling using make debug and paste the output here.