Cannot read from /dev/urandom
Opened this issue · 4 comments
GoogleCodeExporter commented
Hi,
The command I used :
> reaver -i mon0 -b [THE:MAC:HERE!] -vv -p 9998
[+] 93.92% complete @ 2013-05-25 00:02:00 (1 seconds/pin)
[+] Trying pin 99983239
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 99983246
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
Could not open /dev/urandom.
and I'm getting :
Could not open /dev/urandom.
[+] Trying pin 99983253
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
Could not open /dev/urandom.
[+] Sending M2 message
[+] Received M1 message
[+] Sending WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin
After it over and over again.
I can cat the /dev/urandom from terminal while I'm getting this message.
Thank you
Original issue reported on code.google.com by arshamsh...@gmail.com on 24 May 2013 at 11:08
GoogleCodeExporter commented
already know what is pin?
try:
mknod -m 0444 /dev/urandom c 1 9
Original comment by deltomaf...@gmail.com on 27 May 2013 at 2:10
GoogleCodeExporter commented
I have the same problem, it seems to be related to libpcap which open a pipe
but doesn't close it, so i get to many opened files.
$ sudo ls -l /proc/`pidof reaver`/fd | wc -l
will give you the number of files open with reaver.
I got the issue with the latest revision (119).
Original comment by bvan...@gmail.com on 18 Nov 2013 at 3:57
GoogleCodeExporter commented
(libpcap version 1.4.0)
Original comment by bvan...@gmail.com on 18 Nov 2013 at 3:59
GoogleCodeExporter commented
If it's a problem with too many open files, I talked with the libpcap guys, and
it will be fixed in libpcap 1.5.0.
I tried reaver with libpcap 1.5.0 but it failed to work properly, so i guess
they will have to update the code.
You can fix the problem temporarily by setting max open files to 65535 instead
of 1024:
# ulimit -n 65536
# reaver <parameters>
Original comment by bvan...@gmail.com on 19 Nov 2013 at 5:40