Tutorial: Aircrack-ng on N9!

[SaQ]

************************************************** ************************
http://talk.maemo.org/showthread.php?t=91637

Injection drivers to N9. Thanks to nieldk
************************************************** *************************

Hello!

I managed to install Aircrack-ng to my N9. What i don't have, is injection drivers. So i made simple tutorial.

to use Aircrack-ng in to your n9, you must have "ssh root@localhost" and "develsh" privileges.

to get them you must install n9tweak, which can be downloaded from here:

http://minus.com/mb5trtYJt#6f

Download the file and rename it to "n9.deb". Then connect your N9 in your computer via USB, and move the file in MyDocs folder. Then take your n9 and go to terminal
(Must first be enabled in Settings/Security/developers mode)

in terminal:

1.devel-su
(password is rootme)
2. cd /home/user/MyDocs
3.dpkg -i n9.deb

Once the installation is complete, open the n9tweak. Write in n9tweaks terminal "ssh", to enable ssh as root user.

when you're done, reboot your phone. Once your phone has rebooted, go to terminal and write "ssh root@localhost" and your password. now you should have root privileges.


Then, let's move to install the mighty aircrack.


1. Download zip file in here:
http://www.2shared.com/file/dEFJgjqr/aircrack.html

2. Unzip the file, and move the folder "aircrack" in your N9 MyDocs folder

3. Take your N9, and go to terminal

4. In terminal Write "ssh root@localhost" and password
(Now you should have root privileges)

5. write: cd /home/user/Mydocs/aircrack

6. write: dpkg -i iw.deb
When the installation is complete

7. write: dpkg -i aircrack.deb

to use Aircrack-ng in to your n9, you must have "ssh root@localhost" and "develsh" privileges.

# develsh

now you should be able to use aircrack-ng commands.

I'm sorry for my bad English. I am still quite a beginner myself. So I hope this works all of you. Main purpose of this is to get Aircrack-ng to work properly on N9, we gonna still need Injection drivers and all.

So I ask for your help so that we could get this great program to work in N9 :D

Thanks and sorry :D

[GrimyHR]

dont hold your breath, only reason we have injection drivers on n900 because a developer was supposed to be paid for coding them and was screwed
is there any such comercial project for n9? no, and writing drivers is not a simple process, it would mean months of hard work, especialy for closed hardware as the one i guess is on n9
if you want a pentesting device buy n900, we have everything
metasploit, aircrack-ng, reaver, sslstrip, wireshark, john the ripper and much, much more :p

oh, not to forget a real keyboard and not that mumbo jumbo touch me crap :p

[-Tyler-]

great job man!!

I read in another thread you are trying to compile wireshark for N9, hope you get sucess but looks difficult because wireshark has a lot of dependencies, and the interface is based in GTK+

if you interest another pentesting tools already running in N9 are nmap and netcat, both are already in the repositories.

We hope N9 wifi card supports promiscuous mode if not we can forget of wireshark, ettercap, dsniff, etc

[youmeego]

it is one step closer to aircrack on n9, a good start for talented developers to start writing the driver for n9.

[nieldk]

Perhaps it is usefull to have a go with Davids injection drivers made for n900? He released source for his work.

[Iktwo]

I installed aircrack too some weeks ago, the n900 package, but even without injection I wasn't able to capture any data, so it's pretty useless, I searched a lot about monitor mode for the N9 wifi chipset.. hope someone help us..

[qwazix]

why do you have to ssh to.yourself instead of devel-su?

[mmaadx]

Without capture support (monitor mode) aircrack is totally useless sorry to say it

[SaQ]

Hello qwazix

Ssh has more privileges than devel-su. In this case, you can't use all commands that aircrack has with devel-su. In ssh, you will get "permission denied" when you try some AC command, that's why you must develsh after ssh, to grant even more privileges. If somebody know easier way, Please tell us :D

And mmaadx

I made this tutorial because I wanted to encourage those who know something about injection drivers. In my opinion, that would be great to have working aircrack on ours N9.

[coderus]

try in open mode.

[qwazix]

You can run develsh after devel-su (without ssh). Doesn't that give you the elevated privileges?

[zszabo]

try in open mode.

(someone please try these commands from closed mode)

RM696-40-4_PR_005:~# ip link set wlan0 down && iwconfig wlan0 mode mon
RM696-40-4_PR_005:~# iwconfig
lo no wireless extensions.

phonet0 no wireless extensions.

wlan0 IEEE 802.11abgn Mode:Monitor Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

RM696-40-4_PR_005:~# ip link set wlan0 down && iwconfig wlan0 mode man
RM696-40-4_PR_005:~# iwconfig
lo no wireless extensions.

phonet0 no wireless extensions.

wlan0 IEEE 802.11abgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

[nieldk]

iwconfig is not available
'command not found'

(someone please try these commands from closed mode)

RM696-40-4_PR_005:~# ip link set wlan0 down && iwconfig wlan0 mode mon
RM696-40-4_PR_005:~# iwconfig
lo no wireless extensions.

phonet0 no wireless extensions.

wlan0 IEEE 802.11abgn Mode:Monitor Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

RM696-40-4_PR_005:~# ip link set wlan0 down && iwconfig wlan0 mode man
RM696-40-4_PR_005:~# iwconfig
lo no wireless extensions.

phonet0 no wireless extensions.

wlan0 IEEE 802.11abgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

[hoggerz]

I get

RTNETLINK answers: Operation not permitted

hoggerz

[zszabo]

iwconfig is not available
'command not found'

install wireless-tools from harmattan sdk repo. The actual package is listed here:

http://harmattan-dev.nokia.com/pool/harmattan-beta2/free/w/wireless-tools//

[nieldk]

iwconfig is not available
'command not found'

ok got it
apt-get install wirelesd-tools
then the iwconfig is in /sbin

eg

ip link set wlan0 down && /sbin/iwconfig wlan0 mode mon

works in openmode kernel

[zszabo]

I get

RTNETLINK answers: Operation not permitted

hoggerz

try to disable the network from the settings GUI, rather than by using ip set... and then run just iwconfig wlan0 mode mon. See if that works.

Also, I assume you ran the commands with maximum privileges (i.e. after devel-sh)?

[hoggerz]

With all network connections disabled in GUI and devel-su/rootme I get:

Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Operation not permitted.

hoggerz

[nieldk]

With all network connections disabled in GUI and devel-su/rootme I get:

Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Operation not permitted.

hoggerz

not sure if you can in closef mode, but after deve-su->rootme try to issue
develsh
and then the iwconfig command

[hoggerz]

not sure if you can in closef mode, but after deve-su->rootme try to issue
develsh
and then the iwconfig command

Thats better ;)

Works now using develsh then the commands
Someone just needs to sort out the patched drivers/kernel now....

hoggerz

[zszabo]

not sure if you can in closef mode, but after deve-su->rootme try to issue
develsh
and then the iwconfig command

Might as well go all the way (as someone suggested further up in this thread) and do ssh root@Localhost, followed by devel-sh. I Could have sworn that I got it to work that way, from closed mode.

[nieldk]

Source for the N900 injection drivers (courtesy of David Gned, thanks!)
is available here http://david.gnedt.eu/blog/wl1251/

(download link, from that page: http://david.gnedt.eu/wl1251/wl1251-maemo-0.1.tar.gz)

Perhaps it will be helpull for creating new drivers for N9

[zszabo]

Thats better ;)

Works now using develsh then the commands
Someone just needs to sort out the patched drivers/kernel now....

hoggerz

Are you able to do it without turning networking off from the GUI (i.e. By using IP link set ...)! ?

Btw I noticed that if I try to run the IP link set ... And iwconfig commands separately, I also get an error (in open mode). So I combined them via '&&'. could be that the second command merely has to be issues within a limited period after the first.

[hoggerz]

Yeah, If I do:

devel-su
(rootme)
develsh
ip link set wlan0 down && /sbin/iwconfig wlan0 mode monitor

it works
If I then type: /sbin/iwconfig wlan0
It says wlan0 is in monitor mode

hoggerz

[hoggerz]

Only thing is although airodump-ng will now run, It can't see any wireless networks/clients at all. And it seems to think 596523 hours and 14 mins has elapsed since I opened it.

hoggerz

[nieldk]

Only thing is although airodump-ng will now run, It can't see any wireless networks/clients at all. And it seems to think 596523 hours and 14 mins has elapsed since I opened it.

hoggerz

Can you tell a bit about where you got airodump-ng ?
I installed iw and aircrak from post 1, but only got aircrack-ng, airdecap-ng, aircloack-ng airolib-ng from that

[hoggerz]

I originally installed the deb from rzr in this post:

http://talk.maemo.org/showpost.php?p=1142519&postcount=8

but I overwrote the package with the one in this post

try /opt/maemo/usr/sbin/airodump-ng
It seems to install files in odd places.
I found it with: find / -name airodump-ng

hoggerz

[nieldk]

So far, I added all the missing paths to PATH
(export PATH=$PATH:/opt/maemo/usr/sbin:/sbin:/usr/sbin)
EDIT: add the above to $HOME/.profile to make the path permanent

Now, I can successfully issue
airmon-ng start wlan0 (starts monitor device on mon0)

I can also start airodump-ng, but with the same time issue as hoggerz)

trying to start aireplay-ng or airodump-ng on mon0 after airmon-ng outputs

ioctl($IOCSIFFLAGS)failed: Cannot assign requested address

Also, confirms injection is not available when issuing airodump-ng wlan0 with mon0 devoice up

EDIT: we have wl1271, not wl1251 as the N900, so the drivers from David will probably not work directly compiled.
EDIT: Yes, indeed, should do it if we can recompile on the (openmode) kernel, fromDavids Blog "many ports of missing features from wl12xx/wl1271 to current wl1251 (e.g. bluetooth coexistence, hardware filtering, multicast filtering, ...)"

EDIT: For porting the driver, this is very useful: http://wireless.kernel.org/en/users/Drivers/wl12xx
(our kernel is 2.6.32)

[zszabo]

make sure wlan0 is also brought back up after changing to monitoring mode (ip link set wlan up).

That will at least remove the error I think (still won't work, though). I am currently rebuilding kismet to see how far I get with that.

[nieldk]

make sure wlan0 is also brought back up after changing to monitoring mode (ip link set wlan up).

That will at least remove the error I think (still won't work, though). I am currently rebuilding kismet to see how far I get with that.

wlan0 was up doing all this.

[zszabo]

While trying to get kismet to run, I may have stumbled upon the answer. The netlink (libnl) library for this version of Linux may not be entirely compatible with later implementations. I Suspect the same issue preventing me from running kismet properly is also causing problems here.

More later.

[zszabo]

Btw - after building kismet from source and running it, these are the errors that come up:


[SERVER] *** KISMET IS SHUTTING DOWN ***
[SERVER] INFO: Closed pcapdump log file 'Kismet-20120218-22-52-18-1.pcapdump', 0
[SERVER] logged.
[SERVER] INFO: Closed netxml log file 'Kismet-20120218-22-52-18-1.netxml', 0 logged.
[SERVER] INFO: Closed nettxt log file 'Kismet-20120218-22-52-18-1.nettxt', 0 logged.
[SERVER] INFO: Closed gpsxml log file 'Kismet-20120218-22-52-18-1.gpsxml', 0 logged.
[SERVER] INFO: Closed alert log file 'Kismet-20120218-22-52-18-1.alert', 0 logged,
[SERVER] INFO: Shutting down plugins...
[SERVER] Shutting down log files...
[SERVER] ERROR: Didn't understand driver 'wl1271_sdio' forinterface 'wlan0', but it
[SERVER] looks like a mac80211 device so Kismet will use the generic options for
[SERVER] it. Please post on the Kismet forum or stop by the IRC channel and
[SERVER] report what driver it was.
[SERVER] ERROR: Source 'wlan0' doesn't have mac80211 support, disabling VAP creation of
[SERVER] default monitor mode VAP
[SERVER] ERROR: Source 'wlan0': channel get ioctl failed 22:Invalid argument
[SERVER] ERROR: Didn't understand driver 'wl1271_sdio' forinterface 'wlan0', but it
[SERVER] looks like a mac80211 device so Kismet will use the generic options for
[SERVER] it. Please post on the Kismet forum or stop by the IRC channel and
[SERVER] report what driver it was.
[SERVER] ERROR: Source 'wlan0' doesn't have mac80211 support, disabling VAP creation of
[SERVER] default monitor mode VAP
[SERVER] ERROR: Source 'wlan0': channel get ioctl failed 22:Invalid argument
[SERVER] WARNING: Kismet changes the configuration of network devices.
[SERVER] In most cases you will need to restart networking for
[SERVER] your interface (varies per distribution/OS, but
[SERVER] usually: /etc/init.d/networking restart
[SERVER]
[SERVER] Kismet exiting.
Spawned Kismet server has exited

*** KISMET CLIENT SHUTTING DOWN. ***
Kismet client exiting.

[nieldk]

Getting closer I feel :)
I think what we may need to look into is compat and compat-wireless. This is a workaround that David used for wl1251, which is close to our wl1271.
Good thing though, the wl1271 is a newer device, and we might just get this updated to support injection, as opposed to wl1251, which have already been confirmed as super-low priority since it is a old device.
A few posts back, I posted a link to this.
Keep on moving guys :)

[zszabo]

Getting closer I feel :)
I think what we may need to look into is compat and compat-wireless. This is a workaround that David used for wl1251, which is close to our wl1271.
Good thing though, the wl1271 is a newer device, and we might just get this updated to support injection, as opposed to wl1251, which have already been confirmed as super-low priority since it is a old device.
A few posts back, I posted a link to this.
Keep on moving guys :)


I'm on it. Unfortunately this preliminary finding rules out aegis-mode support:

/src/compat-wireless-2012-02-18 $ make
/home/user/src/compat-wireless-2012-02-18/config.mk:254: "WARNING: CONFIG_CFG80211_WEXT will be deactivated or not working because kernel was compiled with CONFIG_WIRELESS_EXT=n. Tools using wext interface like iwconfig will not work. To activate it build your kernel e.g. with CONFIG_LIBIPW=m."

[zszabo]

You are right about compat-wireless, though. But as I said, it will require a modified kernel that's cool with wireless extensions. That in turn requires access to the the kernel source with proper patches to bypass aegis.

[nieldk]

You are right about compat-wireless, though. But as I said, it will require a modified kernel that's cool with wireless extensions. That in turn requires access to the the kernel source with proper patches to bypass aegis.

Modified kernel (disabled Aegis) is available, not sure if the wireless mod have been set, but the diff (for getting Aegis bypas==root)and kernel sources for pr1.1 is here
http://maemo.cloud-7.de/HARM/N9/openmode_kernel_PR1.1/

[SaQ]

Somebody could make tutorial how to use that openmode kernel...

[nieldk]

Somebody could make tutorial how to use that openmode kernel...

If you refer to how to flash it: Here are instructions.
http://talk.maemo.org/showthread.php?t=81579

For usage, not much about it, it just removes Aegis stuff.

[nieldk]

@zszabo Any luck with compiling combat-wireless against the (modified) kernel sources?

[zszabo]

Still trying to figure out how to incorporate changes (usually done using make menuconfig) which are used to build the final kernel image. Is there a comprehensive wiki that contains this information, specific to Harmattan/Meego? I did figure out how to get make menuconfig to run, but a) I'm not sure the default configuration is the same as what goes into the actual kernel image (and, needless to say, I'm not entirely comfortable with flashing a kernel image that may brick my N9); b) either a number of settings are missing, or configured elsewhere (for example, how would I modify the settings for Netfilter?).

[nieldk]

Still trying to figure out how to incorporate changes (usually done using make menuconfig) which are used to build the final kernel image. Is there a comprehensive wiki that contains this information, specific to Harmattan/Meego? I did figure out how to get make menuconfig to run, but a) I'm not sure the default configuration is the same as what goes into the actual kernel image (and, needless to say, I'm not entirely comfortable with flashing a kernel image that may brick my N9); b) either a number of settings are missing, or configured elsewhere (for example, how would I modify the settings for Netfilter?).

From thread: http://talk.maemo.org/showthread.php?t=78490

Build Kernel:
First install Harmattan Platform SDK and download the kernel source with “apt-get source kernel".
then build kernel in scratchbox using the commond

[sbox-HARMATTAN_ARMEL: ~/kernel-2.6.32] > make rm581_defconfig

[zszabo]

From thread: http://talk.maemo.org/showthread.php?t=78490



Build Kernel:

First install Harmattan Platform SDK and download the kernel source with “apt-get source kernel".

then build kernel in scratchbox using the commond




[sbox-HARMATTAN_ARMEL: ~/kernel-2.6.32] > make rm581_defconfig



Thanks -- that's exactly what I was looking for.

[nieldk]

Thanks -- that's exactly what I was looking for.

Great, I think we can possibly ask the guy who compiled the working openmode kernel also (Been told its Joerg, thought initially it was Jalyst or Javispedro).
Let me know if you need more help, or testing on flashing :)

[jalyst]

(Been told its Joerg, thought initially it was Jalyst or Javispedro).
Let me know if you need more help, or testing on flashing :)

joerg_rw or joergrw over at forum.meego.com

[nieldk]

joerg_rw or joergrw over at forum.meego.com

joergrw over at forum.meego.com
Not sure, if its the same guy :) PM'd joerg here, so lets see what he says

[joerg_rw]

I say "I'm only hosting this kernel, I don't even have a build environment for it"
IIRC there was absolutely nothing special in how the kernel got built, according to the kind anonymous guy who provided it.

For the poster some up, and his concerns about "flashing a kernel to N9 that may brick it": please read the readme.txt and other doc snippets on my cloud-7 site, there's no need to *flash* the kernel, you as well can load to RAM and execute in situ - will vaporize to nuttin on next powercycle (BEWARE! Any changes done to / and maybe working under openmode kernel still will cause secure mode aka stock aegis kernel go MALF on next boot, even when openmode kernel got RAM-loaded)

cheers
jOERG

[jalyst]

I say "I'm only hosting this kernel, I don't even have a build environment for it"
IIRC there was absolutely nothing special in how the kernel got built, according to the kind anonymous guy who provided it.

Apologies, has been a while since I'd read all that.
Hey how's usb host-mode progressing....
Can you please give us all an update in the FMC thread?

[nieldk]

I say "I'm only hosting this kernel, I don't even have a build environment for it"
IIRC there was absolutely nothing special in how the kernel got built, according to the kind anonymous guy who provided it.

For the poster some up, and his concerns about "flashing a kernel to N9 that may brick it": please read the readme.txt and other doc snippets on my cloud-7 site, there's no need to *flash* the kernel, you as well can load to RAM and execute in situ - will vaporize to nuttin on next powercycle (BEWARE! Any changes done to / and maybe working under openmode kernel still will cause secure mode aka stock aegis kernel go MALF on next boot, even when openmode kernel got RAM-loaded)

cheers
jOERG

Thanks mate, it is helpfull to know that (being careful) we can boot just the kernel, without flashing.

[-Tyler-]

Now that we officially have the PR 1.2 with us we need the open kernel for PR 1.2 to begin to testing things, i will try to make it work on N9: wireshark, ettercap, dsniff, sslstrip and other petesting tools that already works in the N900.

i think too the inyection drivers for N900 will work too for N9, the network card is almost the same, belongs to the same company and generally in the world of networks cards the same driver is used for a large variety of networks card of the same company.

[nieldk]

Now that we officially have the PR 1.2 with us we need the open kernel for PR 1.2 to begin to testing things, i will try to make it work on N9: wireshark, ettercap, dsniff, sslstrip and other petesting tools that already works in the N900.

i think too the inyection drivers for N900 will work too for N9, the network card is almost the same, belongs to the same company and generally in the world of networks cards the same driver is used for a large variety of networks card of the same company.

The drivers are definately usable, quite sure about that. Just the compat-wireless that needs to be recompiled. Thanks, and hope we can make it happen !

[nieldk]

great job man!!

I read in another thread you are trying to compile wireshark for N9, hope you get sucess but looks difficult because wireshark has a lot of dependencies, and the interface is based in GTK+

if you interest another pentesting tools already running in N9 are nmap and netcat, both are already in the repositories.

We hope N9 wifi card supports promiscuous mode if not we can forget of wireshark, ettercap, dsniff, etc

I started compiling a bunch of pentest tools, looks promising so far. Free to test them :) Still we miss some implementations in kernel to fully support all features of eg aircrack, but hydra, nmap, netcat, ettercap is looking good. Started a new thread with my development here http://talk.maemo.org/showthread.php?t=82643

[stenkin]

please help,

Aegis pejectung wl.deb : Could not open debian archive

[nieldk]

I'm on it. Unfortunately this preliminary finding rules out aegis-mode support:

/src/compat-wireless-2012-02-18 $ make
/home/user/src/compat-wireless-2012-02-18/config.mk:254: "WARNING: CONFIG_CFG80211_WEXT will be deactivated or not working because kernel was compiled with CONFIG_WIRELESS_EXT=n. Tools using wext interface like iwconfig will not work. To activate it build your kernel e.g. with CONFIG_LIBIPW=m."

looking at the pr1,.2 sources, this seems to be changed in the kernel config CONFIG_CFG80211_WEXT is set to 'y'

[t0lkien]

Are there any updates on this? Does Inception help by any chance?

I have it installed and following are the results:

airmon-ng works
airmon-ng start wlan0 also works

All airodump-ng commands fail with the error "failed: cannot assign request address"

aireplay-ng therefore can't get a chance to work

aircrack-ng seems to work, thought I haven't tested it with a proper .cap file

[balisingh]

open source drivers for wl1271
http://answerpot.com/showthread.php?796613-Android+WLAN+drivers+for+LS+Research+TIWI01-00-5206+module+%28TI+WL+1271+chipset%29

[clopez]

compat-wireless won't help

I tried to build it for the kernel PR1.2 on the N9 (http://harmattan-dev.nokia.com/pool/harmattan/free/k/kernel/kernel_2.6.32-20115101+0m7.tar.gz) but this kernel has the stack MAC80211 built-in instead of having it modular. Check file /boot/config-2.6.32.48-dfl61-20115101 on the N9

"ERROR: you have MAC80211 compiled into the kernel, CONFIG_MAC80211=y, as such you cannot replace its mac80211 driver. You need this set to CONFIG_MAC80211=m. If you are using Fedora upgrade your kernel as later version should this set as modular. For further information on Fedora see https://bugzilla.redhat.com/show_bug.cgi?id=470143. If you are using your own kernel recompile it and make mac80211 modular"

[Garrett_PL]

Lads! How's the work gooing?

Would like to help but have not even nearly enough skills, keep up the good work - for sciense purposes only of course.

[sifo]

dont hold your breath, only reason we have injection drivers on n900 because a developer was supposed to be paid for coding them and was screwed..:(...................


so i think N900 users very lucky with that i really appreciate that developer ;)

./sifo

[Mr.Bungle]

http://www.spinics.net/lists/linux-wireless/msg78413.html

[wook_sf]

hello folks, let's fix those damn drivers, shall we?
todo:
+ get original drivers from n900
+ get injection drivers
- get drivers for n9/50 (can someone supply me a link for documentation please?)
- understand drivers from n900
- compare and understand changes in injection drivers
- understand drivers for n9/50
- remake

what we know so far?
everything works except injection drivers
requirement: OpenMode/inception

[urberg]

...
if you interest another pentesting tools already running in N9 are nmap and netcat, both are already in the repositories.
...


Hi,
Where exactly can I find netcat for the Nokia N9?
Thanks

[calibur]

hi.i have problem with "ssh root@localhost".when i type it in xterminal there comes this text:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHINGNASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
43:0a:69:a1:5f:a9:23:2b:28:6b:5b:21:b9:63:2a:71.
Please contact your system administrator.
Add correct host key in /home/user/.ssh/known_hosts to get rid of this message.
Offending key in /home/user/.ssh/known_hosts:1
RSA host key for localhost has changed and youhave requested strict checking.
Host key verification failed.

i have search how to fix it but i nothing found.i hope someone can help me

[jusE]

Any news regarding the driver for N9? :)

[Rabah_vip]

hi guys ,
I'm a beginner in aircrack in phone , on time i use backtrack and it' good , but i forgot the steps and how because i used for a long time
so someone can put the steps with details please
thanks for your hard work

[jd4200]

hi.i have problem with "ssh root@localhost".when i type it in xterminal there comes this text:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Easiest way is to delete the "known_hosts" file inside /home/user/.ssh/

Basically, it just means that your phone thinks your connecting to a different machine than it thinks you want to.
If your connecting to your phone locally, or another machine on your LAN, it's not normally any thing to worry about, but you should never ignore these warnings if your connecting to a server on the internet.

[calibur]

Easiest way is to delete the "known_hosts" file inside /home/user/.ssh/

Basically, it just means that your phone thinks your connecting to a different machine than it thinks you want to.
If your connecting to your phone locally, or another machine on your LAN, it's not normally any thing to worry about, but you should never ignore these warnings if your connecting to a server on the internet.

thanks for help.now it works.now i try to start ac ;)

[Mentalist Traceur]

After my wandering thoughts (and my stumbling upon this thread) reminded me of the fact that so many of you must live empty, wifi-packet-injection-deprived, and thus essentially meaningless, lives, a few days ago I contacted the developer of the injection driver patches for the N900, to see what the odds were of him being able to produce injection driver patches for the N9/N950 - his response and my further comments here:
http://talk.maemo.org/showthread.php?t=87335

[redhoticaro]

Hi everyone!!!

I've just installed aircrack-ng but I've encountered one problem:

when putting wireless card in monitor mode i type:


ifconfig wlan0 down
iwconfig wlan0 mode monitor
ifconfig wlan0 up


and then:


airodump-ng wlan0


Till there everything works well but when I filter sniffing selecting a channel for example:


airodump-ng -c 3 wlan0


On the top right it appears "fixed channel wlan0: -1"

So is there any solution?

thank you all!!!

[pasko]

Hi.
I have found the package in Openrepos.net, but cannot install it.

When I try to do it manually, it complains about dependencies from 'iw', but 'iw' is not installable because ir lacks permission to write to '/usr/share/man/man8'

I've been tinkering with the directories, changing permissions to no avail.

Am I missing something?

Regards.

P.S: Wireless-tools installed flawlessly, btw.

[nieldk]

try devel-su and develsh following, that will escalate your permissions to that needed for iw

[pasko]

Hi.
Thank you, it worked!

However I've seen that iw creates the folder '/usr/share/man/man8/' with owner:group 1000:1000, so I had to chown it.

Regards.