maemo.org - Talk - [Fremantle Maemo5] [ANNOUNCE] Wpspixie & Reaver v1.5.2 to N900

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - [M5] [ANNOUNCE] Wpspixie & Reaver v1.5.2 to N900 (https://talk.maemo.org/showthread.php?t=95899)

[ANNOUNCE] Wpspixie & Reaver v1.5.2 to N900

Adding the Pixie Dust WPS attack and modified Reaver v1.5.2 (reaver-wps-fork-t6x) to Nokia N900:

For Pixiewps see this link for more information.

This will require you to first install libssl-dev:

Code:

sudo apt-get install libssl-dev

The normal procedure for installation:
1. git clone https://github.com/wiire/pixiewps.git
2. cd pixiewps/src
3. make
4. sudo make install

At step 3 I got an error from /usr/include/asm/byteorder.h

Code:

cc -std=c99 -O3 -Wno-deprecated-declarations -o pixiewps pixiewps.c random_r.c -lcrypto

In file included from pixiewps.c:58:

/usr/include/asm/byteorder.h: In function ‘___arch__swab32’:

/usr/include/asm/byteorder.h:32: error: expected ‘)’ before ‘:’ token

In file included from pixiewps.c:62:

pixiewps.h: At top level:

pixiewps.h:169: warning: C99 inline functions are not supported; using GNU89

pixiewps.h:169: warning: to disable this warning use -fgnu89-inline or the gnu_inline function attribute

pixiewps.h:181: warning: C99 inline functions are not supported; using GNU89

/var/tmp/ccL4emQQ.s: Assembler messages:

/var/tmp/ccL4emQQ.s:168: rdhi, rdlo and rm must all be different

/var/tmp/ccL4emQQ.s:284: rdhi, rdlo and rm must all be different

make: *** [all] Error 1

The byteorder.h had line 32 as:

Code:

asm ("eor\t%0, %1, %1, ror #16" : "=r" (t) : "r" (x));

However I found out that by modifying the byteorder.h with __asm__ resulted in succesful make and make install afterwards.

Modified line 32:

Code:

__asm__ ("eor\t%0, %1, %1, ror #16" : "=r" (t) : "r" (x));

If someone more versed in these could tell us that is it safe to leave that line as such or should it be modified back to prior state? Until then just to be on the safe side modify it back to normal after you have compiled the tool.

For Reaver (reaver-wps-fork-t6x) see this link for more information.

This will require you to first install the following if not already present:

Code:

sudo apt-get install build-essential libpcap-dev sqlite3 libsqlite3-dev aircrack-ng pixiewps

Atleast libpcap-dev migth say: "Depends: libpcap0.8-dev"

Code:

apt-get install libpcap0.8-dev

The normal procedure for installation:
1. git clone https://github.com/t6x/reaver-wps-fork-t6x.git
2. cd reaver-wps-fork-t6x/src
3. ./configure
4. make
5. sudo make install

After step 3 edit the Makefiles, change crT to cr (removing the T):

Code:

nano crypto/Makefile

nano tls/Makefile

nano utils/Makefile

Step 4 was succesful after this.

Step 5 failed by default but last night I was way too tired to waste time with it so at this point I just copied the compiled reaver and wash to my user folder and created a symlink to/usr/bin:

Code:

ln -s /home/user/.reaver/reaver /usr/bin/reaver

ln -s /home/user/.reaver/wash /usr/bin/wash

I spent this afternoon doing a field test and to my great pleasure the tools seem to be working flawlessly. That being said I haven't conducted extensive testing yet but the main aspect is working with:

Code:

reaver -i mon0 -b xx:xx:xx:xx:xx:xx -vv -c <channel number> -K 1

The compiled tools are included in the Tools.zip. Copy those to /usr/bin or if you prefer to symlink them thats fine too. Of course I would not recommend anyone to just blindly take my word for their safety but to compile these for yourself. In my own device there aren't any problems but I cannot guarantee that there won't be some issues.

Edit. stryngs provided us with ready made .debs for easy installation! I'm adding them as an attachment.

WARNING: You will install these on your own risk - you should take backups before proceeding :)

NOTE: The included .deb files have dependencies to packages that are included with the Fremantle SDK repository:

You can add it manually by editing the /etc/apt/sources.list:

Code:

deb http://repository.maemo.org fremantle/sdk free non-free

Alternatively navigate to the application menu in the Application Manager (tap the title bar)
1. Select Application catalogs
2. Select New
3. Enter a catalog name: Fremantle SDK
4. Enter a web address: http://repository.maemo.org
5. Enter a distribution: fremantle/sdk
6. Enter components: free non-free
7. Make sure that Disabled is left unchecked.
8. Select Save.

When this is done you can try installing from the .deb files. I recommend disabling the Fremantle SDK repository after the installation is done.

If you encounter issues with the .deb installation please report them to this thread. However my personal recommendation for installation is to manually compile them for yourself.

Re: Wpspixie & Reaver v1.5.2 to N900

add [ANNOUNCE] to your thread title please

Re: [ANNOUNCE] Wpspixie & Reaver v1.5.2 to N900

hi,
i have problem with reaver in n900

Code:

# reaver

reaver: error while loading shared libraries: libpcap.so.1: cannot open shared object file: No such file or directory

is there anything i missed? i installed reaver and wpspixie from debs packages

Re: [ANNOUNCE] Wpspixie & Reaver v1.5.2 to N900

Quote:

Originally Posted by X-J (Post 1480705)

hi,
i have problem with reaver in n900

Code:

# reaver

reaver: error while loading shared libraries: libpcap.so.1: cannot open shared object file: No such file or directory

is there anything i missed? i installed reaver and wpspixie from debs packages

What do you get from:

Code:

dpkg -l | grep libpcap

If you have installed all the requirements you should see lines like:

Code:

ii  libpcap0.8 1.1.1-2maemo4 system interface for user-level packet capture

ii  libpcap0.8-dev 1.1.1-2maemo4 development library and header files for libpcap0.8

These can be corrected with the:

Code:

sudo apt-get install libpcap0.8-dev

I assume that you had Reaver working prior to installing the .deb files or is this your first try with it?

Re: [ANNOUNCE] Wpspixie & Reaver v1.5.2 to N900

i just get this

Code:

# dpkg -l | grep libpcap

ii  libpcap0.8 1.1.1-2maemo4 system interface for user-level packet capture

when i want install libpcap0.8-dev i get this

Code:

libpcap0.8-dev: Depends: libc6-dev but it is not going to be installed

and after that...

Code:

libc6-dev: Depends: linux-kernel-headers but it is not installable

i had reaver 1.4.2 after install reaver 1.5.2 from attachments and then i replace from previously version

Re: [ANNOUNCE] Wpspixie & Reaver v1.5.2 to N900

Quote:

Originally Posted by X-J (Post 1480707)

i just get this

Code:

# dpkg -l | grep libpcap

ii  libpcap0.8 1.1.1-2maemo4 system interface for user-level packet capture

when i want install libpcap0.8-dev i got this

Code:

libpcap0.8-dev: Depends: libc6-dev but it is not going to be installed

and after that...

Code:

libc6-dev: Depends: linux-kernel-headers but it is not installable

i had reaver 1.4.2 after install reaver 1.5.2 from attachments and then i replace from previously version

The libc6-dev and linux-kernel-headers are available from Fremantle SDK repository if not from anywhere else but that repo is meant for developing so you should be careful with it if you didn't have it enabled before this.

Unfortunately I don't have a chance to test the .deb files today but I'll post back later this week when I have conducted some more testing with them.

Shortly put the issue is currently with missing dependancies that can be corrected by installing the required packages manually - if you do not want to enable Fremantle SDK repository that is.

Re: [ANNOUNCE] Wpspixie & Reaver v1.5.2 to N900

Thanks for your help :)
now,i install linux-kernel-headers with CleaN900 and after that install libpcap0.8-dev & libc6-dev (with apt-get) currectly but reaver problem didn't solve...
i'm waiting for your test :)

Re: [ANNOUNCE] Wpspixie & Reaver v1.5.2 to N900

Hi all,

I chose to compile this, but reaver fails: running ./configure says "no acceptable grep could be found"... so it does not make a Makefile...

I have checked, latest grep is installed on my n900.

Searching on the net I found a solution in which I should link grep to egrep but I wouldn't want to try it until I get some answer from you. Do you have any ideas what I am missing...?

Thanks,

jm

EDIT: I installed pixiwps and reaver from deb file. When I run reaver it said it cannot find libpcap.so.1 though I had all dependecies installed. I checked /usr/lib/ and I had libpcap.so, libpcap.so.0.8. and libpcap.so.1.3.0. I found a solution for this issue on the web: "ln -s /usr/lib/libpcap.so.0.8 /usr/lib/libpcap.so.1". Reaver now runs fine although I cannot test it properly.
(WARNING! DO THINGS AT YOUR OWN RISK!)

Re: [ANNOUNCE] Wpspixie & Reaver v1.5.2 to N900

Quote:

Originally Posted by justmemory (Post 1480767)

EDIT: I installed pixiwps and reaver from deb file. When I run reaver it said it cannot find libpcap.so.1 though I had all dependecies installed. I checked /usr/lib/ and I had libpcap.so, libpcap.so.0.8. and libpcap.so.1.3.0. I found a solution for this issue on the web: "ln -s /usr/lib/libpcap.so.0.8 /usr/lib/libpcap.so.1". Reaver now runs fine although I cannot test it properly.
(WARNING! DO THINGS AT YOUR OWN RISK!)

i test the code..my reaver working now...
Thanks :)

Re: [ANNOUNCE] Wpspixie & Reaver v1.5.2 to N900

Hi ras_older and thanks for these tools,i install attachments debs,everything went fine,but for big regret pixiewps can't found pin.I don't know,maybe this happens because i'm not trying to compiling my own,however,here the result from console;

Quote:

[+] Running pixiewps with the information, wait ...
[Pixie-Dust]
[Pixie-Dust] Pixiewps 1.1
[Pixie-Dust]
[Pixie-Dust] [-] WPS pin not found!
[Pixie-Dust]
[Pixie-Dust][*] Time taken: 2 s 870 ms
[Pixie-Dust]
[+] Pin not found, trying -f (full PRNG brute force), this may take around 30 minutes
[Pixie-Dust]
[Pixie-Dust] Pixiewps 1.1
[Pixie-Dust]
[Pixie-Dust] [-] WPS pin not found!
[Pixie-Dust]
Nokia-N900:~#

It's there anyone else who already have installed reaver and pixiewps and gets the same outputs like above?
regards