Reply
Thread Tools Search this Thread
tanago's Avatar
Posts: 135 | Thanked: 292 times | Joined on Aug 2012 @ Burgas, Bulgaria
#741
Originally Posted by mr_pingu View Post
@tanago: If you use the mon0 way on the n900 and connect the wlan0 to an AP on eg channel 1, it locks mon0 automatically to channel 1 too
mon0 is coming from wlan0 , thus when locking the master device will lock mon0 too. But why you should want to alter wlan0 and/or connect to ap when you have entered monitor mode and you have fully working injection on mon0? Just exit monitor mode and you will be able to connect
Originally Posted by Saturn View Post
If you like coding and have the time, you can edit the clevenHelper.sh file as root to do this. Check lines 51 to 54. I'm guessing this is the part you need to modify as well as replace all references of wlan0 with mon0 in the rest of this bash script.

I cannot really promise, but if you give me complete instructions on how to enable monitor/managed modes then I might give you a test version to test.
I am really interested in this and I like coding but there are 2 clevenHelper.sh files one in /opt/cleven and the other in /home/opt/cleven which one should I edit?
 
Estel's Avatar
Posts: 3,837 | Thanked: 5,594 times | Joined on Mar 2011
#742
I think I've found small glitch in Cleven's reaver implementation.

Using current command to invoke Cleven, after successful cracking of PIN, reaver x-term window just closes - without giving chance to actually verify found PIN or retrieved WPA PSK.

I've just checked it during real-test on my router, and reaver.db file *doesn't* keep retrieved WPA password (at least, using reaver from repositories, aka latest, compiled by Pali). Retrieved data is shown *only* on x-term window with cracking progress.

reaver have argument "-o" for providing output to file, but it prevents any info from appearing inside opened x-term window, where reaver is "working". Furthermore, using static path for -o, would result in further cracking attempts overwriting former ones.

IMO, it would be good idea to create new directory under /home/user/.cleven/keys, called - for example - wps (/home/user/.cleven/keys/wps). Then, some code in clevenHelper would read reaver's output, and react on "success" pattern, saving it (only relevant part, as whole log would be loooong) as retrieved WPS PIN and WPA PSK, vievable from "keys" tab from Cleven GUI.

What do you think, Saturn?

/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
 

The Following 2 Users Say Thank You to Estel For This Useful Post:
Posts: 822 | Thanked: 1,043 times | Joined on Feb 2011 @ The Netherlands
#743
Originally Posted by tanago View Post
mon0 is coming from wlan0 , thus when locking the master device will lock mon0 too.
Mon0 and wlan0 can be on different channels in backtrack on my laptop when I last tested it, IIRC.
Originally Posted by tanago View Post
and you have fully working injection on mon0? Just exit monitor mode and you will be able to connect
Injection works fine when you are connected to AP with wlan0. Ofcourse of what I said before, it only works on the same channel as the AP.


Originally Posted by tanago View Post
But why you should want to alter wlan0 and/or connect to ap when you have entered monitor mode?
Well when I test on my own router (have 2, on on channel 11 and one on channel 1)

Sometimes the N900 connects auto, becuz I have that enabled and then it fails on mon0 too
__________________
N900 loaded with:
CSSU-T (Thumb)
720p recording
--
Second N900 (Thanks to GreatGonzo) loaded with:
CSSU Thumb
720p recording
Kernel-power 52
--
[TCPdump & libpcap | ngrep]
--
2D-Artist needed for game developer
--
donate
 

The Following User Says Thank You to mr_pingu For This Useful Post:
Posts: 822 | Thanked: 1,043 times | Joined on Feb 2011 @ The Netherlands
#744
Code:
Nokia-N900:/home/user/MyDocs/MyScripts# ifconfig wlan0 down
Nokia-N900:/home/user/MyDocs/MyScripts# iwconfig wlan0 mode monitor
Nokia-N900:/home/user/MyDocs/MyScripts# ifconfig wlan0 up
Nokia-N900:/home/user/MyDocs/MyScripts# aireplay-ng -9 wlan0
17:26:00  Trying broadcast probe requests...
17:26:01  No Answer...
17:26:01  Found 2 APs

17:26:01  Trying directed probe requests...
17:26:01  00:11:22:33:44:55  - channel: 11 - 'ESSID'
17:26:02  Ping (min/avg/max): 1.373ms/14.998ms/49.805ms Power: -90.72
17:26:02  29/30:  96%

17:26:02  Injection is working!

17:26:02  00:12:34:56:78:90 - channel: 11 - ''
17:26:03  Ping (min/avg/max): 2.014ms/13.966ms/67.474ms Power: -38.47
17:26:03  30/30: 100%

Nokia-N900:/home/user/MyDocs/MyScripts# ifconfig wlan0 down
Nokia-N900:/home/user/MyDocs/MyScripts# iwconfig wlan0 mode managed
Nokia-N900:/home/user/MyDocs/MyScripts# ifconfig wlan0 up
Nokia-N900:/home/user/MyDocs/MyScripts# airmon-ng start wlan0 
Process with PID 7010 (udhcpc) is running on interface wlan0


Interface	Chipset		Driver

wlan0		TI WL1251	wl12xx - [phy0]
				(monitor mode enabled on mon0)

Nokia-N900:/home/user/MyDocs/MyScripts# aireplay-ng -9 mon0
17:28:32  Trying broadcast probe requests...
17:28:34  No Answer...
17:28:34  Found 2 APs

17:28:34  Trying directed probe requests...
17:28:34  00:12:34:56:78:90 - channel: 11 - ''
17:28:34  Ping (min/avg/max): 1.495ms/10.259ms/38.635ms Power: -43.38
17:28:34  29/30:  96%

17:28:34  Injection is working!

17:28:34  00:11:22:33:44:55 - channel: 11 - 'ESSID'
17:28:40   0/30:   0%
In my situation injection works on wlan0 too...
__________________
N900 loaded with:
CSSU-T (Thumb)
720p recording
--
Second N900 (Thanks to GreatGonzo) loaded with:
CSSU Thumb
720p recording
Kernel-power 52
--
[TCPdump & libpcap | ngrep]
--
2D-Artist needed for game developer
--
donate
 

The Following User Says Thank You to mr_pingu For This Useful Post:
tanago's Avatar
Posts: 135 | Thanked: 292 times | Joined on Aug 2012 @ Burgas, Bulgaria
#745
Originally Posted by mr_pingu View Post
In my situation injection works on wlan0 too...
then the problem is in me and I will take care of it.
 

The Following 2 Users Say Thank You to tanago For This Useful Post:
Saturn's Avatar
Posts: 1,565 | Thanked: 1,873 times | Joined on Mar 2007 @ UNKLE's Never Never Land
#746
Originally Posted by tanago View Post
I am really interested in this and I like coding but there are 2 clevenHelper.sh files one in /opt/cleven and the other in /home/opt/cleven which one should I edit?
Actually /home/opt and /opt are pointing to the same location. That is, it is the same file you just look at it from different links.
 
Saturn's Avatar
Posts: 1,565 | Thanked: 1,873 times | Joined on Mar 2007 @ UNKLE's Never Never Land
#747
Originally Posted by tanago View Post
then the problem is in me and I will take care of it.
from where did you get the aircrack-ng and which version you have?
 
tanago's Avatar
Posts: 135 | Thanked: 292 times | Joined on Aug 2012 @ Burgas, Bulgaria
#748
Originally Posted by Saturn View Post
Actually /home/opt and /opt are pointing to the same location. That is, it is the same file you just look at it from different links.
I saw the little shortcut arrow but I didnt assume they are the same.

Originally Posted by Saturn View Post
from where did you get the aircrack-ng and which version you have?
1.1-maemo12 from extras repo
 

The Following User Says Thank You to tanago For This Useful Post:
Saturn's Avatar
Posts: 1,565 | Thanked: 1,873 times | Joined on Mar 2007 @ UNKLE's Never Never Land
#749
Originally Posted by Estel View Post
I think I've found small glitch in Cleven's reaver implementation.

Using current command to invoke Cleven, after successful cracking of PIN, reaver x-term window just closes - without giving chance to actually verify found PIN or retrieved WPA PSK.

I've just checked it during real-test on my router, and reaver.db file *doesn't* keep retrieved WPA password (at least, using reaver from repositories, aka latest, compiled by Pali). Retrieved data is shown *only* on x-term window with cracking progress.

reaver have argument "-o" for providing output to file, but it prevents any info from appearing inside opened x-term window, where reaver is "working". Furthermore, using static path for -o, would result in further cracking attempts overwriting former ones.

IMO, it would be good idea to create new directory under /home/user/.cleven/keys, called - for example - wps (/home/user/.cleven/keys/wps). Then, some code in clevenHelper would read reaver's output, and react on "success" pattern, saving it (only relevant part, as whole log would be loooong) as retrieved WPS PIN and WPA PSK, vievable from "keys" tab from Cleven GUI.

What do you think, Saturn?

/Estel
Can you delete the db file and re-run reaver?
you can put the correct pin as an option to make it find it immediately.

Maybe you have an old db structure or something.

PS: As I said I haven't tried it as I don't have the means and time.
 

The Following User Says Thank You to Saturn For This Useful Post:
Posts: 43 | Thanked: 16 times | Joined on Mar 2010
#750
Originally Posted by Estel View Post
I think I've found small glitch in Cleven's reaver implementation.

Using current command to invoke Cleven, after successful cracking of PIN, reaver x-term window just closes - without giving chance to actually verify found PIN or retrieved WPA PSK.

I've just checked it during real-test on my router, and reaver.db file *doesn't* keep retrieved WPA password (at least, using reaver from repositories, aka latest, compiled by Pali). Retrieved data is shown *only* on x-term window with cracking progress.

reaver have argument "-o" for providing output to file, but it prevents any info from appearing inside opened x-term window, where reaver is "working". Furthermore, using static path for -o, would result in further cracking attempts overwriting former ones.

IMO, it would be good idea to create new directory under /home/user/.cleven/keys, called - for example - wps (/home/user/.cleven/keys/wps). Then, some code in clevenHelper would read reaver's output, and react on "success" pattern, saving it (only relevant part, as whole log would be loooong) as retrieved WPS PIN and WPA PSK, vievable from "keys" tab from Cleven GUI.

What do you think, Saturn?

/Estel
Yes this would be good.
At the moment I crack WPS with Cleven until the window closes (which means its cracked) then i have to open up a separate Xterminal window outside of Cleven and repeat the Reaver commands manually to finally get the password to stay on screen. Its a 10 second job but annoying
 
Reply

Tags
aircrack, cleven, reaver

Thread Tools Search this Thread
Search this Thread:

Advanced Search

 
Forum Jump


All times are GMT -4. The time now is 11:20 PM.