Jump to content

no42

Dedicated Members
  • Posts

    925
  • Joined

  • Last visited

  • Days Won

    17

Posts posted by no42

  1. Sounds like a timing / focus / payload issue.

    Follow some examples, the ducky will always type in the active window, sometimes timings are OS dependant , also payloads are usually OS dependant. Have you read the links in my signature? Read others posts in the forums - theres a lot of info there; could be information overload? start with the ducky guide and FAQs

    Start with a slightly longer delay between commands, and once a script has successfully run; reduce the timings to find the optimal payload speed.

    like any hacking device/ programming language practise,practise,practise.

    The duck is your friend.

  2. The micro-controller sounds fine. It sounds like dirt on the micro-sd slot.

    Possible solutions:

    1)Try to clean the the sd-card slot with something small

    2) Try replacing the sdcard with an entirely different one (sometimes these small cards fail?)

    3) very gently (there are delicate pins that may break if your too rough) with a wooden toothpick, try to gently probe out any dirt from the sd-card slot

    4) club together with some mates and do a big hakshop purchase and replace the ducky

    Warning... possibly harmful to your ducky...

    5) desolder the sd-card slot & then clean and re-solder the card slot back on?

    6) desolder the sd-card slot & replace with one from rd-online / digikey / farnell?

    note: I bare no responsibility if you harm your ducky.

    Best of Luck...

  3. Karma can see, and mimic WPA/WPA2 probes.

    Problem is that many OS's now record details about the AP, i.e. was it previously encrypted? MAC addresses etc. So when the Pineapple is issuing Probe Responses with "I'm xyz", the host OS may choose to ignore them, and/or present the user with a warning that the WiFi network is different than previously used; As is the case for my IOS/OSX devices.

  4. Apologies this is brief, but should give you the right idea.

    1)You may have to go through the BIOS, or onboard system configuration tool to add the disks.

    2)Then they should show up as extra disks / datastores within vmware.

    3)to add a drive to a vm, right-click the vm.

    choose edit settings

    add

    hard drive

    configure harddrive location, size etc

    finish

    4)then within the powered-up OS of the virtualised machine, you have to configure the drive letter/mount point.

  5. http://wiki.wireshark.org/CaptureSetup/CapturePrivileges

    Wireshark has implemented Privilege Separation which means that the Wireshark GUI (or the tshark CLI) can run as a normal user while the dumpcap capture utility runs as root. This can be achieved by installing dumpcap setuid root. The advantage of this solution is that while dumpcap is run as root the vast majority of Wireshark's code is run as a normal user (where it can do much less damage).

    the following should do the trick if 'dumpcap' is within the user 'root''s path:

    sudo su
    chmod 4755 `which dumpcap`
    exit
    
  6. ok failing that :

    apt-get update

    apt-get --reinstall install gnuradio-dev cmake git libboost-all-dev libusb-1.0-0 libusb-1.0-0-dev libfftw3-dev swig python-numpy

    I did have the same error as you? all i did was reinstall some packages and i got it working, can't remember which package exactly maybe it was the gnuradio-dev not the gnuradio?

  7. Its to do with the tuner chip and raw I/Q frames and sending them directly to the computer, if your dongle can't send these raw I/Q frames, it can't do SDR.

    For a list of compatible chips:

    http://rtlsdr.org

    To find out your tuner chip - crack open the case, and read the letters and numbers off the small black square - may require a magnifying glass

×
×
  • Create New...