Results 1 to 7 of 7

Thread: Bad password error when validating authentication in WICD

Hybrid View

  1. #1
    Just burned his ISO
    Join Date
    Jan 2011
    Posts
    5

    Default Bad password error when validating authentication in WICD

    The problem is when connecting to the router with BT5 using wireless antenna model AWUS036NH It tries to get past t validating authentication in WICD but then gives a 'bad password' error when the password is right and Winows can connect to the wireless fine with the same credentials.

    A number of 'fixes' have been tried from going through the forum however none have resolved the issue.

    • BackTrack VM Version 5
    • Tried in ISO
    • BT5 gnome 32 bit VMPlayer
    • BT5 gnome 32 bit VMWare Workstation
    • Tried in ISO within Oracle Virtual Box
    • BackTrack 5 compatible wireless adapter - AWUS036NH


    Has anyone experienced this before and can offer any tips/suggestions?

    Cheers

  2. #2
    Just burned his ISO
    Join Date
    Jul 2011
    Posts
    1

    Default AW: Bad password error when validating authentication in WICD

    Did you chooses the right encryption at properties?
    wpa, wep, etc.?

  3. #3
    Just burned his ISO
    Join Date
    Jan 2011
    Posts
    5

    Default Re: Bad password error when validating authentication in WICD

    Thanks for replying npkev, yeah, the correct encryption has been choosing as when using another adaptor connecting to the same access point using BT5 this worked fine.

  4. #4
    Just burned his ISO
    Join Date
    Jul 2011
    Location
    San Francisco
    Posts
    2

    Default Re: Bad password error when validating authentication in WICD

    I'm having a hell of a time with this as well. I've had it connect ONCE.
    I checked dmesg (whats your output?) and I see it authenticating, associating, then de-authenticating with reason code 3 and 15. Mostly 15.
    something nasty:
    ERROR: This device does not support DMA on your system. It will now be switched to PIO.
    and
    Controller RESET (DMA error) ...
    Checking out linux/kernel/ieee80211.h (http://git.kernel.org/?p=linux/kerne...ux/ieee80211.h)
    reason codes are:
    Code:
    /* Reason codes */
    ...
    WLAN_REASON_DEAUTH_LEAVING = 3,
    ...
    WLAN_REASON_4WAY_HANDSHAKE_TIMEOUT = 15,
    ...
    i check iwpriv wlan0 and I get "no private ioctls"
    from a bit of googling, this seems to be a driver error. Isn't it always with wireless?
    If I discover something I will let you know; maybe it's related regardless if I have broadcom chipset

  5. #5
    Just burned his ISO
    Join Date
    Feb 2011
    Posts
    4

    Default Re: Bad password error when validating authentication in WICD

    I have this same problem with my Alfa AWUS036NH; aireplay-ng -9 mon0 works fine, airodump-ng mon0 works fine. However I can't connect to my router due to "Bad password" in wicd. The password is correct as if I scan with and use wlan0 (stock dell broadcom) it works fine. I tried changing /var/lib/wicd/configurations to use quotes around ASCII instead of the hex which was originally there and that did nothing. Here's my /var/log/wicd:

    [code]2011/08/24 00:08:48 :: Putting interface down
    2011/08/24 00:08:48 :: ifconfig wlan1 down
    2011/08/24 00:08:48 :: Releasing DHCP leases...
    2011/08/24 00:08:48 :: attempting to set hostname with dhclient
    2011/08/24 00:08:48 :: using dhcpcd or another supported client may work better
    2011/08/24 00:08:48 :: /sbin/dhclient -r wlan1
    2011/08/24 00:08:48 :: ifconfig wlan1
    2011/08/24 00:08:49 :: Setting false IP...
    2011/08/24 00:08:49 :: ifconfig wlan1 0.0.0.0
    2011/08/24 00:08:49 :: Stopping wpa_supplicant
    2011/08/24 00:08:49 :: wpa_cli -i wlan1 terminate
    2011/08/24 00:08:49 :: Flushing the routing table...
    2011/08/24 00:08:49 :: /sbin/ip route flush dev wlan1
    2011/08/24 00:08:49 :: iwconfig wlan1 mode managed
    2011/08/24 00:08:49 :: Putting interface up...
    2011/08/24 00:08:49 :: ifconfig wlan1 up
    2011/08/24 00:08:49 :: iwconfig wlan1
    2011/08/24 00:08:51 :: enctype is wpa
    2011/08/24 00:08:51 :: Generating psk...
    2011/08/24 00:08:51 :: ['/usr/bin/wpa_passphrase', 'xxxxx', 'xxxxxx']
    2011/08/24 00:08:51 :: Attempting to authenticate...
    2011/08/24 00:08:51 :: ['wpa_supplicant', '-B', '-i', 'wlan1', '-c', '/var/lib/wicd/configurations/xxxxxaxxxxd', '-D', 'wext']
    2011/08/24 00:08:51 :: ['iwconfig', 'wlan1', 'essid', '--', 'xxxxxx']
    2011/08/24 00:08:51 :: iwconfig wlan1 channel 11
    2011/08/24 00:08:51 :: iwconfig wlan1 ap xx:xx:xx:xx:xx:xx
    2011/08/24 00:08:51 :: WPA_CLI RESULT IS DISCONNECTED
    2011/08/24 00:08:52 :: iwconfig wlan1
    2011/08/24 00:08:52 :: WPA_CLI RESULT IS SCANNING
    2011/08/24 00:08:53 :: WPA_CLI RESULT IS SCANNING
    2011/08/24 00:08:54 :: iwconfig wlan1
    2011/08/24 00:08:56 :: WPA_CLI RESULT IS ASSOCIATING
    2011/08/24 00:08:57 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2011/08/24 00:08:58 :: iwconfig wlan1
    2011/08/24 00:08:58 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2011/08/24 00:08:59 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2011/08/24 00:09:00 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2011/08/24 00:09:00 :: iwconfig wlan1
    2011/08/24 00:09:01 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2011/08/24 00:09:02 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2011/08/24 00:09:02 :: iwconfig wlan1
    2011/08/24 00:09:03 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2011/08/24 00:09:04 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2011/08/24 00:09:04 :: iwconfig wlan1
    2011/08/24 00:09:05 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2011/08/24 00:09:06 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
    2011/08/24 00:09:07 :: iwconfig wlan1
    2011/08/24 00:09:07 :: WPA_CLI RESULT IS SCANNING
    2011/08/24 00:09:09 :: WPA_CLI RESULT IS ASSOCIATING
    2011/08/24 00:09:09 :: iwconfig wlan1
    2011/08/24 00:09:10 :: WPA_CLI RESULT IS ASSOCIATING
    2011/08/24 00:09:11 :: WPA_CLI RESULT IS ASSOCIATED
    2011/08/24 00:09:12 :: iwconfig wlan1
    2011/08/24 00:09:12 :: WPA_CLI RESULT IS ASSOCIATED
    2011/08/24 00:09:13 :: WPA_CLI RESULT IS ASSOCIATED
    2011/08/24 00:09:15 :: WPA_CLI RESULT IS ASSOCIATED
    2011/08/24 00:09:15 :: iwconfig wlan1
    2011/08/24 00:09:16 :: WPA_CLI RESULT IS ASSOCIATED
    2011/08/24 00:09:17 :: WPA_CLI RESULT IS ASSOCIATED
    2011/08/24 00:09:17 :: iwconfig wlan1
    2011/08/24 00:09:18 :: WPA_CLI RESULT IS ASSOCIATED
    2011/08/24 00:09:19 :: WPA_CLI RESULT IS ASSOCIATED
    2011/08/24 00:09:19 :: iwconfig wlan1
    2011/08/24 00:09:20 :: WPA_CLI RESULT IS ASSOCIATED
    2011/08/24 00:09:22 :: iwconfig wlan1
    2011/08/24 00:09:23 :: WPA_CLI RESULT IS None
    2011/08/24 00:09:23 :: connect result is Failed
    2011/08/24 00:09:23 :: exiting connection thread
    2011/08/24 00:09:24 :: Sending connection attempt result bad_pass

    wtf?

  6. #6
    Just burned his ISO
    Join Date
    Feb 2011
    Posts
    4

    Default Re: Bad password error when validating authentication in WICD

    Found a solution albeit one in which I'm not entirely positive what the consequences are. All I did was
    Code:
    ~#modprobe rtl8187
    Here's lsmod | grep rt
    Code:
    rtl8187                51205  0 
    eeprom_93cx6            1292  1 rtl8187
    rt2800usb              10028  0 
    rt2800lib              33048  1 rt2800usb
    crc_ccitt               1281  1 rt2800lib
    rt2x00usb               9319  1 rt2800usb
    rt2x00lib              33002  3 rt2800usb,rt2800lib,rt2x00usb
    mac80211              248838  5 rtl8187,rt2800lib,rt2x00usb,rt2x00lib,b43
    cfg80211              152934  4 rtl8187,rt2x00lib,b43,mac80211
    parport                29468  1 lp
    agpgart                27382  4 drm,intel_agp,intel_gtt
    I have the STA driver blacklisted as well, but whether that was blacklisted or not didn't seem to matter. I heard to blacklist it on another forum but I forget where. I pass the validation and get an IP address.

    Curious problems from this:
    1. nmap stopped working. "route_dst_netlink: can't find interface "wlan1""
    2. Injection works inconsistently. Still trying to find out what's different about when it works and when it doesn't.

    I'll keep working on these problems and stay updated.

  7. #7
    Just burned his ISO
    Join Date
    Sep 2012
    Posts
    1

    Smile Re: Bad password error when validating authentication in WICD

    Here is a fix that worked for me.

    Check your /ect/network/interfaces

    should look something like this:

    auto lo
    iface lo inet loopback

    auto eth0
    iface eth0 inet dhcp

    auto eth1
    iface eth1 inet dhcp

    auto auth0
    iface auth0 inet dhcp

    auto wlan0
    ifce wlan0 inet dhcp


Similar Threads

  1. Wicd Connection Failed: Bad password
    By ElGingo in forum BackTrack 5 Beginners Section
    Replies: 5
    Last Post: 11-22-2012, 05:46 AM
  2. wicd:Bad Password
    By monkeyD in forum Beginners Forum
    Replies: 6
    Last Post: 04-12-2011, 10:47 AM
  3. wicd says bad password, can't connect.
    By Taiiwo in forum Beginners Forum
    Replies: 0
    Last Post: 04-02-2011, 12:52 PM
  4. "Validating Authentication" and then "not connected"
    By Carlcox89 in forum OLD BackTrack 4 General Support
    Replies: 5
    Last Post: 11-13-2009, 06:53 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •