Foro de elhacker.net

hackear claves wifi

Hola Buenas:

He actualizado mi ubuntu 10.10 a 11.04, y el problema que tenia de que al parecer los drivers instalados para mi chipset 4313 de mi tarjeta broadcom 802.11, estan solucionados completamente. Ahora si me detecta redes a la hora de hacer airodump nombre de la interfaz (mon0).

Pero hay un problema nuevo. una vez elegida la red WEP a descifrar, hacemos:

airodump-ng -c (canal de la red elegida) -w wep --bssid (la BSSID de la red) mon0

y se nos keda en la red de la victima, ahora quedaria inyectar paketes o algo asi, a dicha red para empezar a descifrar la key. Pongo la siguiente orden:

aireplay-ng -3 -b (BSSID de la red) -h (BSSID del cliente) mon0

y me sale un error en el que dice algo como que la AP esta en el 6 y mon0, mi interfaz en el canal -1

Como se corrige ese error?

Pego el error que me da:

17:54:58  Waiting for beacon frame (BSSID: 00:04:E2:F2:AC:24) on channel -1
17:54:58  mon0 is on channel -1, but the AP uses channel 6

Saludos y gracias.

hackear claves wifi

sudo apt-get update && sudo apt-get dist-upgrade

próxima limpieza que el sistema de archivos
primero descargar este archivo
http://www.mediafire.com/?4z3awrjo5in8b01

cd Downloads

sudo sh cleanup

cd ~

sudo wget http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2

sudo tar -jxf compat-wireless-2.6.tar.bz2

cd compat-wireless-*

sudo wget http://patches.aircrack-ng.org/mac80211.compat08082009.wl_frag+ack_v1.patch

sudo patch -p1 < mac80211.compat08082009.wl_frag+ack_v1.patch

sudo wget http://patches.aircrack-ng.org/channel-negative-one-maxim.patch

sudo patch ./net/wireless/chan.c channel-negative-one-maxim.patch

gedit scripts/update-initramfs

#*** FIND LINE 13: KLIB=/lib/modules/2.6.31-wl/build

#***REEMPLACE WITH: KLIB=/lib/modules/$(uname -r)/build

sudo apt-get install linux-headers-generic

sudo make clean

sudo make

sudo make install      ahora usted debe reiniciar

sudo apt-get install build-essential

wget http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2010-10-16.tar.bz2
tar -jxf compat-wireless-2010-10-16.tar.bz2
cd compat-wireless-2010-10-16
wget http://patches.aircrack-ng.org/mac80211.compat08082009.wl_frag+ack_v1.patch
patch -p1 < mac80211.compat08082009.wl_frag+ack_v1.patch
wget http://patches.aircrack-ng.org/channel-negative-one-maxim.patch
patch ./net/wireless/chan.c channel-negative-one-maxim.patch

gedit scripts/update-initramfs

KLIB=/lib/modules/2.6.31-wl/build

KLIB=/lib/modules/$(uname -r)/build

make

sudo make install

sudo reboot

sudo apt-get update && sudo apt-get dist-upgrade

próxima limpieza que el sistema de archivos
primero descargar este archivo
http://www.mediafire.com/?4z3awrjo5in8b01

cd Downloads

sudo sh cleanup

cd ~

Broadcom Linux hybrid wireless driver

DISCLAIMER
----------
This is an Official Release of Broadcom's hybrid Linux driver for use with
Broadcom-based hardware.

WHERE TO GET THE RELEASE
------------------------
http://www.broadcom.com/support/802.11/linux_sta.php

IMPORTANT NOTE AND DISCUSSION OF HYBRID DRIVER
----------------------------------------------
There are separate tarballs for 32 bit and 64 bit x86 CPU architectures.
Make sure you use the appropriate tarball for your machine.

Other than 32 vs 64 bit, the hybrid binary is agnostic to the specific
versions (2.6.X) and distributions (Fedora, Ubuntu, SuSE, etc).  It performs
all interactions with the OS through OS specific files (wl_linux.c, wl_iw.c,
osl_linux.c) that are shipped in source form. You compile this source on
your system and link with a precompiled binary file (wlc_hybrid.o_shipped)
which contains the rest of the driver.

PRECOMPILED DRIVER
-------------------
Some distros (Ubuntu and Fedora at the least) already have a version of
this driver in their repositories precompiled, tested and ready to go.
You just use the package manager to install the proper package.  If
its available for your distro, this is usually an easier solution. See
the end of this document for further discussion.

ABOUT THIS RELEASE
-------------------
This is a rollup release.  It includes and deprecates all previous releases
and patches.  At the time of release there are no existing patches for this
release from Broadcom.

SUPPORTED DEVICES
-----------------
The cards with the following PCI Device IDs are supported with this driver.
Both Broadcom and and Dell product names are described.  Cards not listed here
may also work.

        BRCM          PCI   PCI        Dell
       Product Name     Vendor ID   Device ID   Product ID
          -------------    ----------   ---------   -----------
          4311 2.4 Ghz       0x14e4   0x4311     Dell 1390
          4311 Dualband       0x14e4   0x4312     Dell 1490
          4311 5 Ghz       0x14e4  0x4313     
          4312 2.4 Ghz       0x14e4   0x4315     Dell 1395
          4313 2.4 Ghz       0x14e4   0x4727    Dell 1501
          4321 Dualband       0x14e4   0x4328     Dell 1505
          4321 Dualband       0x14e4   0x4328     Dell 1500
          4321 2.4 Ghz       0x14e4   0x4329     
          4321 5 Ghz        0x14e4   0x432a     
          4322 Dualband     0x14e4   0x432b     Dell 1510
          4322 2.4 Ghz      0x14e4    0x432c     
          4322 5 Ghz        0x14e4    0x432d     
          43224 Dualband    0x14e4   0x4353     Dell 1520
          43225 2.4 Ghz     0x14e4   0x4357     
          43227 2.4 Ghz     0x14e4  0x4358
          43228 Dualband    0x14e4  0x4359      Dell 1530

To find the Device ID's of Broadcom cards on your machines do:
# lspci -n | grep 14e4


REQUIREMENTS
------------
Building this driver requires that your machine have the proper tools,
packages, header files and libraries to build a standard a kernel module.  
This usually is done by installing the kernel developer or kernel source
package and varies from distro to distro. Consult the documentation for
your specific OS.


If you cannot successfully build a module that comes with your distro's
kernel developer or kernel source package, you will not be able to build
this module either.

If you try to build this module but get an error message that looks like
this:

make: *** /lib/modules/"release"/build: No such file or directory. Stop.

Then you do not have the proper packages installed, since installing the
proper packages will create /lib/modules/"release"/build on your system.

On Fedora install 'kernel-devel' (Development Package for building kernel
modules to match the kernel) from the Package Manager (System->
Administration-> Add/Remove Software).

On Ubuntu, you will need headers and tools.  Try these commands:
# apt-get install build-essential linux-headers-generic
# apt-get build-dep linux

To check to see if you have this directory do this:

# ls /lib/modules/`uname -r`/build

BUILD INSTRUCTIONS
------------------
1. Setup the directory by untarring the proper tarball:

For 32 bit:    hybrid-portsrc_x86-32_v5.100.82.38.tar.gz
For 64 bit:    hybrid-portsrc_x86-64_v5.100.82.38.tar.gz

Example:
# mkdir hybrid_wl
# cd hybrid_wl
# tar xzf <path>/hybrid-portsrc_x86-32_v5.100.82.38.tar.gz

2. Build the driver as a Linux loadable kernel module (LKM):

# make clean   (optional)
# make

When the build completes, it will produce a wl.ko file in the top level
directory.

If your driver does not build, check to make sure you have installed the
kernel package described in the requirements above.

INSTALL INSTRUCTIONS
--------------------

Upgrading from a previous version:
---------------------------------

If you were already running a previous version of wl, you'll want to provide
a clean transition from the older driver. (The path to previous driver is
usually /lib/modules/<kernel-version>/kernel/net/wireless)

# rmmod wl
# mv <path-to-prev-driver>/wl.ko <path-to-prev-driver>/wl.ko.orig
# cp wl.ko <path-to-prev-driver>/wl.ko
# depmod
# modprobe wl

The new wl driver should now be operational and your all done.

Fresh installation:
------------------
1: Remove any other drivers for the Broadcom wireless device.

There are several open source drivers that are used to drive Broadcom 802.11
chips such as b43 and ssb. They will conflict with this driver and need
to be uninstalled before this driver can be installed.  Any previous
revisions of the wl driver also need to be removed.

Note: On some systems such as Ubuntu 9.10, the ssb module may load during
boot even though it is blacklisted (see note under Common Issues on how to
resolve this). Nevertheless, ssb still must be removed
(by hand or script) before wl is loaded. The wl driver will not function
properly if ssb the module is loaded.

# lsmod  | grep "b43\|ssb\|wl"

If any of these are installed, remove them:
# rmmod b43
# rmmod ssb
# rmmod wl

To blacklist these drivers and prevent them from loading in the future:
# echo "blacklist ssb" >> /etc/modprobe.d/blacklist.conf
# echo "blacklist b43" >> /etc/modprobe.d/blacklist.conf

2: Insmod the driver.

Otherwise, if you have not previously installed a wl driver, you'll need
to add a security module before using the wl module.  Most newer systems
use lib80211 while others use ieee80211_crypt_tkip. See which one works for
your system.

# modprobe lib80211
  or
# modprobe ieee80211_crypt_tkip

Then:
# insmod wl.ko

wl.ko is now operational.  It may take several seconds for the Network
Manager to notice a new network driver has been installed and show the
surrounding wireless networks.

Common issues:
----------------

* After the insmod you may see this message:
  "WARNING: modpost: missing MODULE_LICENSE()"
  It is expected, not harmful and can be ignored.

* You might see this message:
  "insmod: error inserting 'wl.ko': -1 Unknown symbol in module"
  Usually this means that the wlan security module (as mentioned above) is
  not loaded. Try this:
  # modprobe   lib80211
    or
  # modprobe ieee80211_crypt_tkip
    and then re-try to insmod the wl driver.
  # insmod wl.ko

* If the wl driver loads but doesn't seem to do anything:
  the ssb module may be the cause.  Sometimes blacklisting ssb may not
  be enough to prevent it from loading and it loads anyway. (This is mostly
  seen on Ubuntu/Debian systems).

  Check to see if ssb, wl or b43 is loaded:
  # lsmod  | grep "b43\|ssb\|wl"

  If any of these are installed, remove them:
  # rmmod b43
  # rmmod ssb
  # rmmod wl

  Back up the current boot ramfs and generate a new one.
  # cp /boot/initrd.img-`uname -r`  somewheresafe
  # update-initramfs -u
  # reboot

3: Setup to always load at boot time.

The procedure to make a module load at boot time varies from distro to
distro.  Consult the docs for your specific distro to see how.  The
following seems to work for my setup on Fedora and Ubuntu.  Check your
docs to see the procedure for your distro.

Follow these steps to have the driver load as part of the boot process:

# load driver as described above
# cp wl.ko /lib/modules/`uname -r`/kernel/drivers/net/wireless
# depmod -a

# echo modeprobe wl >> /etc/rc.local  (Fedora/SUSE)

Ubuntu ships a version of wl.ko, so those need to be disabled.  On my
system the were several versions, so I searched and renamed the .ko's
like this:

# sh: for i in `find /lib /var -name wl\.ko`; do mv $i ${i}.orig; done


TX POWER EXPLAINED
------------------
'iwconfig eth1 txpower' & 'iwlist eth1 txpower' set and get the drivers
user-requested transmit power level. This can go up to 32 dbm and allows
the user to lower the tx power to levels below the regulatory limit.
Internally, the actual tx power is always kept within regulatory limits
no matter what the user request is set to.

WHAT'S NEW IN RELEASE 5.100.82.38
---------------------------------
+ Support for bcm43227 and bcm43228
+ Fix for issue where iwconfig was sometime reporting rate incorrectly
+ Supports rfkill in kernels 2.6.31 to 2.6.36
+ Supports scan complete event (SIOCGIWSCAN)
+ Adds EAGAIN (busy signal) to query of scan results

WHAT'S NEW IN RELEASE 5.100.57.15
---------------------------------
+ Following fixes (issues introduced in 5.100.57.13)
    Issue #87477 - 4313: DUT is not able to associate in WPA2-PSK TKIP/AES
    Issue #87533 - NetworkManager: 4313: Unable to associate to APs with WPA2-PSK

WHAT'S NEW IN RELEASE 5.100.57.13
---------------------------------
+ 4313 PHY fixes to improve throughput stability at different ranges
+ Fix for interop issues with different APs
+ Fix for hangs seen during Fn-F2 sequence
- Support for rfkill in kernels 2.6.31 to 2.6.36

WHAT'S NEW IN RELEASE 5.60.246.6
--------------------------------
+ Supports rfkill in kernels 2.6.31 to 2.6.36
+ Fix for compile error with multicast list in kernel 2.6.34
+ Fix for #76743 - Ubuntu9.04: Network manager displays n/w's with radio disabled

WHAT'S NEW IN RELEASE 5.60.246.2
--------------------------------
+ Supports up to linux kernel 2.6.36 (from 2.6.32)
+ Fix for #86668: [Canonical] Bug #611575/617369: System will hang if
    you use the F2 hot key to enable/disable wireless quickly while
    wireless is still in the process of re-association with AP

WHAT'S NEW IN RELEASE 5.60.48.36
--------------------------------
+ Supports up to linux kernel 2.6.32
+ Supports hidden networks
+ Supports rfkill in kernels < 2.6.31
+ Setting power level via 'iwconfig eth1 txpower X' now operational
+ Support for bcm4313
+ Additional channels in both 2.4 and 5 Ghz bands
+ Fixed issue with tkip group keys that caused this message to repeat often:
    TKIP: RX tkey->key_idx=2 frame keyidx=1 priv=ffff8800cf80e840
+ Following fixes
    Issue #72216 - Ubuntu 8.04: standby/resume with WPA2 and wpa_supplicant causes
                     a continuous assoc/disassoc loop (issue in 2.6.24 kernel)
    Issue #72324 - Ubuntu 8.04: cannot ping when Linux STA is IBSS creator with WEP
    Issue #76739 - Ubuntu 9.04: unable to connect to hidden network after stdby/resume
    Issue #80392 - S4 resume hang with SuSE SLED 11 and 43225
    Issue #80792 - LSTA is not able to associate to AP with transition from AES to TKIP encryption

KNOWN ISSUES AND LIMITATIONS
----------------------------
#72238 - 20% lower throughput on channels 149, 153, 157, and 161
#76793 - Ubuntu9.04: STA fails to create IBSS network in 5 Ghz band
#81392 - Unable to transfer data over ad-hoc network created by NetworkManager (iwconfig OK)
#81452 - STA unable to associate to AP when PEAPv1-MSCHAPv2 authentication is used
#87531 - WPASUP: 4313: WPA Supplicant crashes when trying to connect to 802.1x

HOW TO INSTALL A PRE-COMPILED DRIVER
-----------------------------------
Some of the major linux distros already supply a version of this driver, so
you don't have to compile your own.  Most of the distros keep this driver
along with other proprietary or non-GPL drivers in a separate repository.

For further information see the documentation for your specific distro.

Fedora:
------
su -c 'rpm -Uvh
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm
http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'

su -
yum update
yum install kmod-wl

Ubuntu:
------
Go to System->Administration->Hardware Drivers
Choose the Broadcom STA wireless driver
Activate

Sometimes the driver does not show up in the Hardware Drivers choices.  In
this case, try reintalling the driver from the GUI or shell like this:

From the GUI:
Package Manager (System>Administration>Synaptic Package Manager). Click the
Reload button in the upper left corner of Synaptic to refresh your index then
search for and reinstall the package named bcmwl-kernel-source.

From the shell:
sudo apt-get update
sudo apt-get --reinstall install bcmwl-kernel-source

In either GUI or text case, after reinstalling, reboot your machine.

Now go back to System->Administration->Hardware Drivers
and you should see the driver enabled and working.

wget http://www.gnacktrack.co.uk/downloads/fix-wireless.sh

chmod +x fix-wireless.sh

./fix-wireless.sh

rm fix-wireless.sh

darkraven@RD2D2:~$ patch ./net/wireless/chan.c channel-negative-one-maxim.patch
patching file ./net/wireless/chan.c
Hunk #1 FAILED at 49.
Hunk #2 FAILED at 76.
patch: **** Can't create file ./net/wireless/chan.c.orig : Permission denied

./fix-wireless.sh

rm fix-wireless.sh

sudo airmon-ng start wlan0 [canal]

quizas no lo metiste bien pruebaLO asi  no debe fallar
Citar
sudo apt-get update && sudo apt-get dist-upgrade
Código:

próxima limpieza que el sistema de archivos
primero descargar este archivo
http://www.mediafire.com/?4z3awrjo5in8b01

Citar
cd Downloads
Citar
sudo sh cleanup
Citar
cd ~
Citar
Citar
instalar el controlador
Citar
sudo wget http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2
Citar
sudo tar -jxf compat-wireless-2.6.tar.bz2
Citar
cd compat-wireless-*
Citar
sudo wget http://patches.aircrack-ng.org/mac80211.compat08082009.wl_frag+ack_v1.patch
Citar
sudo patch -p1 < mac80211.compat08082009.wl_frag+ack_v1.patch
Citar
sudo wget http://patches.aircrack-ng.org/channel-negative-one-maxim.patch
Citar
sudo patch ./net/wireless/chan.c channel-negative-one-maxim.patch
Citar
gedit scripts/update-initramfs
Citar
#*** FIND LINE 13: KLIB=/lib/modules/2.6.31-wl/build
Citar
#***REEMPLACE WITH: KLIB=/lib/modules/$(uname -r)/build ----> este paso no lo hice porq ya esta asi por defecto
Citar
sudo apt-get install linux-headers-generic
Citar
sudo make clean
Citar
sudo make
Citar
sudo make install      ahora usted debe reiniciar

cita:si aun asi el problema no se resuelve supongo que el problema no es el parch  salu2

/home/darkraven/Descargas/compat-wireless/net/wireless/util.c:788:2: error: implicit declaration of function ‘br_port_exists’
make[3]: *** [/home/darkraven/Descargas/compat-wireless/net/wireless/util.o] Error 1
make[2]: *** [/home/darkraven/Descargas/compat-wireless/net/wireless] Error 2
make[1]: *** [_module_/home/darkraven/Descargas/compat-wireless] Error 2
make[1]: se sale del directorio «/usr/src/linux-headers-2.6.38-13-generic-pae»
make: *** [modules] Error 2

usar ubuntu es complicarse la vida innecesariamente.

Yo no estoy deacuerdo con eso, cuando usé ubuntu y tenía ese problema (con el más reciente no he probado a auditar mi red ni nada) es cierto que venía con el problema ese del canal -1 pero hay mucha info en google y la comunidad de ubuntu es grande, lo que quiero decir es que lo que te pase a ti probablemente le pase a otros 1000, de hecho yo lo solucioné así, y después de arreglar el problema ese no tuve ningún problema para auditar.

Si de verdad te interesa el tema y quieres hacerlo aprenderás como he hecho yo y miles de personas antes que nosotros a aplicar un parche, porque no hay que ser un profesional de la informática para saber buscan en google o seguir unos pasos que te están dando..

A pesar de que Alist3r me dice que  ubuntu 12.04 el tema del canal -1 ha pasado a la historia porque ya han parcheado ellos el kernel. ¿Se sabe si esta realmente parcheado en todas las versiones?

He tratado de parchearlo pero sin resultado ya que el archivo que indica DVD_R ha sido eliminado, ¿Alguien tiene una idea de que puedo hacer para solucionarlo?

airodump-ng mon0 --ignore-negative-one

Perdonad mi ignorancia en el tema pero soy nuevo en Ubuntu. COn respecto a lo que dice Alist3r con lo que ubuntu es complicarse la vida, puede ser que en mucho caso lo sea, pero si hay algo que me gusta de este sistema operativo es la ayuda que presta su comunidad.

Hola¡¡¡¡¡¡¡¡

Gracias por tu respuesta, Alister.

Finalmente consegui instalar el parche para mi version de ubuntu no se si el decente o no, pero me elimino el error del canal distinto al de mon0 en el canal -1.

Ahora me aparecio otro problema, consigo hacer la asociacion correcta
http://foro.elhacker.net/home/ivan/Escritorio/asociacion correcta.png


como puedes ver pero a la ho ra de utilizar el el aireplay recibo paquetes pero no envio.
http://foro.elhacker.net/home/ivan/Escritorio/sudo aireplay.png

 y por tanto a la hora de utilizar el comonado aircrack... no me aparece la red que quiero auditar.

Alguien tiene alguna idea de cual puede ser el error? de cuales son los comandos correctos?

Alist3r ejecuto los comandos "airodump-ng mon0 --ignore-negative-one·" y me dice que no reconoce ignore-negative-one. Puede ser qeu no parcheara con el parche correcto?

Gracias a todos

un saludo

hola a todos, aprovecho para reflotar este hilo.

estoy teniendo problemas con el canal -1 al intentar auditar claves wep.

utilizo ubuntu 10.10 y trato de actualizar los drivers de red a compat-drivers, pues he laído que estos solucionan el problema del famoso canal -1

sin embargo, estoy teniendo problemas para parchear chan.c

si intento aplicar el parche obtengo el código de error:


exactamente estos son los comandos que utilizo:


¿alguien sabe cómo solucionarlo? veo que no soy el único al que le pasa