| The Following 3 Users Say Thank You to StefanL For This Useful Post: | ||
|
|
2012-01-14
, 18:21
|
|
|
Posts: 5,028 |
Thanked: 8,614 times |
Joined on Mar 2011
|
#1122
|

| The Following User Says Thank You to Estel For This Useful Post: | ||
|
|
2012-01-14
, 20:28
|
|
|
Posts: 84 |
Thanked: 22 times |
Joined on Nov 2011
@ Italy
|
#1123
|
I may be totally wrong here, but AFAIK, they're not - due to increased power usage, while associated to AP and in standby mode. The fix for it would require osso-something, that is now waiting to get released in CSSU-Testing.
AFAIK (again), kernel-power just provide those drivers (for now, as later, they may be used by default), so they can be loaded without keeping them in some folder - isn't Cleven doing it this way?
Anyway, I've tested it a second ago, and while Monitor mode work without loading injection drivers, injection itself doesn't (surprise). It starts, but doesn't inject anything, even when requirements (MAC from allowed list, ARP catched etc) are meet. No problem with Injection drivers under same conditions.
/Estel
// Edit
It may be worth to mention, that I've found how to finally *properly* fix a eons-old bug with icon. Just put faircrack.png it into '/usr/share/icons/hicolor/48x48/apps', then, in .desktop file, modify line icon=faircrack (*without* .png).
All the trick is that default icon path is '/usr/share/icons/hicolor/48x48/apps', so desktop looks there, unless specified otherwise (via icon path or something) in .desktop file.
This way, icon is displayed properly in desktop, but also in menu etc. I've fixed *every* program with wrong .desktop file and icon location on my device, this way.
One reminder - reboot is *mandatory* after this, or you'll be fooled by "no-icon". There are ways to restart things, but they don't work reliably (sometimes works, sometimes doesn't), so before You conclude "it doesn't work" - and switch it back to full icon path - reboot device.
/Estel
|
|
2012-01-14
, 20:34
|
|
|
Posts: 84 |
Thanked: 22 times |
Joined on Nov 2011
@ Italy
|
#1124
|
Yes, fAircrack implements this on the Monitor Tab using the Enable Injection button.
No, fAircrack uses ifconfig, iwconfig commands to put wlan0 into monitor / managed mode.fAircrack uses for captureCode:sudo ifconfig wlan0 down sudo iwconfig wlan0 mode Monitor sudo ifconfig wlan0 upfor deauthenticationCode:sudo airodump-ng --channel X --bssid BSSID --write FILE wlan0for authenticationCode:sudo aireplay-ng -0 10 -a BSSID wlan0for injectionCode:sudo aireplay-ng -1 5 -q 10 -a BSSID -h MYMAC wlan0for interactive injection (since v0.46)Code:sudo aireplay-ng -3 -b BSSID -h MYMAC wlan0to crack WEP keyCode:sudo aireplay-ng -2 -p 0841 -c FF:FF:FF:FF:FF:FF -b BSSID -h MYMAC wlan0to crack WPA key using wordlistCode:aircrack-ng -l KEYFILE CAPFILESto search for APs and clientsCode:aircrack-ng WORDLIST -l KEYFILE CAPFILESCode:sudo airodump-ng -w FILE wlan0
|
|
2012-01-14
, 21:15
|
|
|
Posts: 298 |
Thanked: 341 times |
Joined on Aug 2010
@ This world :)
|
#1125
|
Is it typo, or have I missed update? Your signature also list 0.45 as latest version. If 0.46 is available, could You please provide link and changelog?
---
As for test, I'll gladly do it after returning home
/Estel
), there are a few tweaks I am looking at before publishing it. Anyhow, attached screenshot shows my system (KP49) put into monitor mode using airmon-ng start wlan0 and then running sudo aireplay-ng mon0 --test. All this without loading the bleeding edge drivers; seems like injection is working straight from kernel power. Let me know how your tests go. So beats me at the moment why all you guys need to load the bleeding edge drivers, on my system I have always had them in a different directory to the recommended ones, so that part has never worked for me, but I have always happily injected since KP46. Of course, I might be completely blindsided by the obvious, so am happy to hear from other people's experience.
).
: Python Gorillas (Maemo5)
Faircrack0.50 Update (Maemo5) 
: WPScrack (Maemo5)
| The Following User Says Thank You to StefanL For This Useful Post: | ||
|
|
2012-01-14
, 21:33
|
|
|
Posts: 298 |
Thanked: 341 times |
Joined on Aug 2010
@ This world :)
|
#1126
|
Many thanks!
I've just noticed a thing: shouldn't it be:
aireplay-ng -1 0 -e [AP ESSID] -a [AP BSSID] -h [N900 MAC Address] wlan0
I mean, you must specify AP ESSID (name)?
I wrote once in Aircrack forum (look at the bottom):
http://forum.aircrack-ng.org/index.p...=3309.msg18601
asking why it was necessary specify network name, and they answered me it was part of the standards.
In fact, if ESSID is hidden, you must find it, first.
). I am happy for any testing and feed-back though, so thanks for your time. I have not yet tested for hidden ESSIDs discovery, still on my list. Edit:ESSID is only required for cracking, where the ESSID is part of the salt for the hashes, so that is another explanation, why the ESSID is not required for this case.
: Python Gorillas (Maemo5)
Faircrack0.50 Update (Maemo5) 
: WPScrack (Maemo5)
|
|
2012-01-14
, 22:44
|
|
|
Posts: 298 |
Thanked: 341 times |
Joined on Aug 2010
@ This world :)
|
#1127
|
tar -xzvf faircrack0.46.tar.gz

: Python Gorillas (Maemo5)
Faircrack0.50 Update (Maemo5) 
: WPScrack (Maemo5)
|
|
2012-01-14
, 23:38
|
|
|
Posts: 5,028 |
Thanked: 8,614 times |
Joined on Mar 2011
|
#1128
|

|
|
2012-01-15
, 00:13
|
|
|
Posts: 5,028 |
Thanked: 8,614 times |
Joined on Mar 2011
|
#1129
|

|
|
2012-01-15
, 00:37
|
|
Posts: 2,076 |
Thanked: 3,267 times |
Joined on Feb 2011
|
#1130
|
![]() |
| Tags |
| aircrack, aircrack-ng, epicfacepalm, pen testing, rtfm dude! |
|
My phone evolution: Nokia 7610 (RIP), N82 (RIP), BB9000 (RIP), N900, BB9760 (RIP), N8, BB9900, N9 64GB
Working
Not so much
Last edited by StefanL; 2012-01-23 at 12:54.