Jump to content

UnKn0wnBooof

Active Members
  • Posts

    146
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by UnKn0wnBooof

  1. Or even mv /pineapple /pineapple-ORIG

    But I think you should try to work directly with Sebkinne, the pineapple software guy. And get a pineapple too, so you can test your work.

    Also, Version 1.5 will be released at DEFCON (or Bsides) in just about a week. There could be many changes.

    Indeed. Thanks for the note. I want a Pineapple but unfortunately I cannot get the funds to buy one. I know the Pineapple is a low price piece of kit considering it's functionality; but I can't even afford that. I live with my parents and they have bills so their left with very little money.

    Bummer -_-

  2. Lavanoid, it's great to see your theme. It seems you've spent considerable time on this project and I commend you for your contribution. I know there will be some technical details which will need to be ironed out seeing as the interface is currently being changed for v1.5. I believe Seb will detail them soon. Until then I just wanted to say thank you for input on the UI. Cheers!

    No problem Mr Kitchen. I made a comment on the latest Hak5 video about unlocking your device with NFC tags too.

    If you are rooted, install Xposed Framework (Google it), then install NFC Screenoff Enabler (it's name is somewhat among those lines) which can be found within the Xposed app in the Download section. Once the module had been installed, open the modules UI and use it's config to register your tag to unlock the device.

  3. Ok,

    So some time ago I decided to extract the Web UI from the pineapple firmware (/pineapple) and modify it.

    So, let's get onto the facts shall we?

    Hak5 - Wi-Fi Pineapple Web UI changes (By Jack Davies, AKA Lavanoid Volcanic):
    1.) Modified index.php (The root index of the web server). These changes enable the page to read the
    configuration that is located in /includes/configuration/layout.php, which contains the theme config.
    2.) Created the directory "/includes/configuration" - this may prove useful for future implementations.
    3.) Created the directory "/includes/theme" - this directory contains three themes, the original theme,
    and the other two are custom themes created by me, which are white_elegence and black_elegence.
    the background that is included in the two custom themes are NOT my creation - I got them from a free
    wallpaper site - I TAKE NO CREDIT! The background included in the theme "white_elegence" has had it's
    colour inverted to match the white elements, however - I DO NOT TAKE CREDIT FOR THIS EITHER!
    4.) I've sanitised the scripts stored within /includes/api - I don't like messy scripts, although they
    work, I have OCD (Obsessive Cleaning Disorder) so it interferes with my digital life aswell as the real one.
    I've also sanitised the /includes/json.php - why was all of the script placed on one line? If I was a
    CPU, I would be scared to read all of that at once.
    5.) Made a few modifications to /includes/css/styles_main.php (I can't remember if I renamed it to .php from .css).
    The original "styles_main.php" has been placed within the "/includes/theme/original" directory - some people
    may want the original UI, why should my work stop them?
    6.) Made the /includes/api/statusbar_handler.php better by changing the output of the system status. Before, the
    command "uptime" was just run without any other tampering involved - I thought this wasn't good enough
    so I made it give out a much cleaner output.
    7.) Added an API that is stored as /includes/api/cpu_load.php - this just outputs the CPU usage in %. I was
    hoping to use this to implement status bars that show the CPU usage and later on adapt this to show other stats,
    but Javascript hasn't been my "best friend" lately.
    Unfortunately, I do not own the Pineapple so I cannot gurantee that my modifications wiil work on the
    device that it was designed for (MK5) so I hope that if there are bugs, that you can fix them. I have
    been testing as much of the script as I can via my own webserver (Ubuntu, Apache2, PHP5) so that is how
    I have been able to "emulate" a Pineapple, though I cannot use the features such as the infustion tiles etc.
    Ideas for the future:
    I no longer have the time to continue editing the Web UI as I have more important things to deal with (school
    exams, college etc) so here are my ideas that I think should be implemented into the UI:
    1.) A little "tab" box that allows the user to select a different theme without editing the /includes/configuration/layout.php
    file.
    2.) A page dedicated to theme downloads.
    3.) A percentage bar located below the status bar that indicates CPU usage - I tried to add this feature myself
    but the script just won't work - the "setInterval" command in the javascript ignores what I have placed,
    I have no idea for why this is, neither am I able to spend the time figuring it out - sorry.
    Thank you for taking the time to read this changelog!
    Good luck!
    *********** UPDATE ***********
    Version 1.1) Just made another slight modification to the "statusbar_handler.php" file. There was a bug when displaying the No. of logged on users.

    Download link: dl.dropbox.com/s/u5pp48acdcagebo/www_Pineapple_1.1_MK5.zip


    I've tried getting in contact with Darren Kitchen about this for some time now, but no luck so I thought I'd post it in the forum for him to find instead.

    Screenshots:

    WiFiPineapple_Light.png

    WiFiPineapple_Dark.png

    WiFiPineapple_Config.png

    Installation instructions:

    1.) SSH into the pineapple

    2.) Ensure that the pineapple is connected to the internet

    3.) Run the following commands:

    cd /pineapple

    rm -R *

    wget dl.dropbox.com/s/u5pp48acdcagebo/www_Pineapple_1.1_MK5.zip

    unzip *

    As stated before - I do NOT own a Pineapple so I am unable to test all of the features; neither am I able to guarantee a hassle free installation. I would deeply appreciate it if I had some positive feedback though. Give it a try; perhaps you'll love your Pineapple even more than before!

  4. I've already modified a lot of the web interface, of course - when I'm finished I'll show it to Darren for his approval and perhaps he will implement my changes into the firmware itself.

    Changes that I've made:

    1.) Sanitised most of the scripts/pages (I LIKE MY CODE CLEAN! Tabbing achieves this).

    2.) Added theme support (Anyone will be able to create and install custom themes - thats if you want a different appearence).

    3.) Tidied up the status bar - information is more tidy, easier to read and it provides the CPU usage/load in %.

    What I'm planning to do next:

    1.) Add detailed bar charts that inform the user of free disk space, RAM, CPU frequency/min freq/max freq etc.

    2.) Not sure about anything else yet, maybe some cool animations and stuff - I like things to look tidy and efficient.

    I don't own a Pineapple (maybe months or even a year before I can get one - I'm 15 years old, I have to be wise with my pocket money) - so although I can view a majority of the elements, I cannot view/test all of them - such as the tiles, etc...

  5. And if you want to get the source code before you get the pineapple you can download the upgrade.bin file and use something like binwalk to extract its contents

    Thanks for the advice. I've managed to extract the firmware with the software you mentioned - WAHOO! Can't wait to get a Pineapple :lol: . Thanks everyone.

  6. Seeing as the WiFI Pineapple MKV webinterface is written in PHP and Javascript, it is easily found on every WiFi Pineapple MKV in the /pineapple folder.

    While the code is open source, it is under a non-commercial licence.

    Mind if I ask what you want to change and / or make better?

    Best Regards,

    Sebkinne

    I think the UI could be brighter and more "up-to-date" looking.

  7. Seeing as the WiFI Pineapple MKV webinterface is written in PHP and Javascript, it is easily found on every WiFi Pineapple MKV in the /pineapple folder.

    While the code is open source, it is under a non-commercial licence.

    Mind if I ask what you want to change and / or make better?

    Best Regards,

    Sebkinne

    Thanks for the reply. Anyway, as I web developer and a network manager (all of which take place in my free-time), I love being able to modify all of my gadgets. So, the answer to your question is simple - I want a unique interface that suites my personal style, I want something distinguished from everyone else's Pineapple - I want to add even more features of my own.

    I've already written a web UI for my Raspberry Pi that controls a BBC Dr-Who K-9 and I think I can do even better to the Pineapples already existing UI.

    Is it possible to have a link to the source? I can't find it anywhere...

    Also, this is the UI that I wrote for my Pi: https://lh5.googleusercontent.com/-4hRvPgQC5jY/U10QOAu8ufI/AAAAAAAAA9I/LDi8FV34Brk/w702-h335-no/K9-CPL.png

  8. Does anyone know where to get the pineapple source code from? I'm not bothered about how hard it is to compile the code and what not, I simply want access to the web UI source as I want to make it better.

    I currently do not own a Wi-Fi Pineapple, but I am thinking about getting one - ONLY IF I HAVE THE ABILITY TO "CHANGE-UP" the UI elements.

    Thanks.

  9. Looks very cool and useful. Can't wait to try it. Be honest though, have you tested this? 80% of the scripts I see posted here have major halting bugs in them, which makes no sense because surely the developer attempted to run it ONCe on their machine, right? (and someone else's machine!)

    Just tried it on some other systems, it certainly works with Ubuntu. I've also tested it on the Raspberry Pi running Debian Wheezy. Have you tried it?

    Have you changed the variables at the top of the script to work with your configuration? If it doesn't work, please let me know :wink: .

    P.S. You do know that the script that I pasted on this page isn't displayed correctly right? That's why I uploaded it to my dropbox account.

    Don't forget to chmod the script too. I use "chmod 0777 duck" because 0777 means everything. I also recommend placing the "duck" file in your home directory/bin. E.g. /home/Username/bin

    If a file is placed in your bin directory, then you can type "duck" from any directory and run the script. If you run the script like this: "sudo duck erase" etc, then it most likely won't execute because sudo doesn't use your home directory in its path variable. If you do want it to work with sudo, then you should place the script in /bin (not ~/bin or /home/USER/bin).

    SUDO !! (BANG BANG!) :lol:

  10. Looks very cool and useful. Can't wait to try it. Be honest though, have you tested this? 80% of the scripts I see posted here have major halting bugs in them, which makes no sense because surely the developer attempted to run it ONCe on their machine, right? (and someone else's machine!)

    Hi, I've tried all of the functions and it seems to work for me.

  11. Here's a bash script that lets you easily compile scripts as well as flash firmware!

    Unfortunately, when I paste the script directly on to this page, it isn't shown correctly so here is a dropbox link to it (my Github account has messed up a bit so I can't sync my repositories anymore):

    Link (Click Here!)

    Here's the script if you want to review it before downloading:

    #!/bin/bash
    # DFU-PROGRAMMER MUST BE INSTALLED TO USE THIS SCRIPT! RUN "sudo apt-get install dfu-programmer" TO INSTALL IT!
    PROGRAM_VER="Mark 3"
    PATH_DUCK_ENCODER="/var/DuckEncoder/encoder.jar"
    PATH_DUCK_PATH_LAYOUTS="/var/DuckEncoder/resources"
    DUCK_CHIPSET=at32uc3b1256
    if ! [[ -f /usr/bin/dfu-programmer ]]
    then
    echo "WARNING! Package 'dfu-programmer' not installed!"
    echo "Installing package..."
    sudo apt-get -y install dfu-programmer
    if ! [[ -f /usr/bin/dfu-programmer ]]
    then
    echo "Failed to install the required package! Cannot continue."
    exit 0
    fi
    fi
    if [[ $1 == "" ]]
    then
    echo "No command specified! Use --help for usage information."
    exit 0
    fi
    if [[ $1 == "--help" ]]
    then
    echo ""
    echo " HAK5 USB RUBBER DUCKY FLASH UTILITY"
    echo " By Lavanoid Volcanic - $PROGRAM_VER"
    echo ""
    echo ""
    echo " Duck commands:"
    echo ""
    echo " flash - Flash a .hex firmware file (must be in DFU mode)"
    echo " dump - Dump the currently installed firmware (must be in DFU mode)"
    echo " erase - Erase the currently installed firmware (must be in DFU mode)"
    echo " info - Obtain various information about the device (must be in DFU mode)"
    echo " reset - Reset/reboot the device (must be in DFU mode)"
    echo " start - Start the device (must be in DFU mode)"
    echo " encode - Encode/compile a script into a .bin file"
    echo " schips - List chips supported by dfu-programmer"
    echo ""
    exit 0
    fi
    if [[ $1 == "start" ]]
    then
    echo "Starting device..."
    sudo dfu-programmer $DUCK_CHIPSET start
    echo "Done!"
    exit 0
    fi
    if [[ $1 == "schips" ]]
    then
    sudo dfu-programmer --targets
    exit 0
    fi
    if [[ $1 == "info" ]]
    then
    echo "Obtaining information..."
    sudo dfu-programmer $DUCK_CHIPSET get bootloader-version
    sudo dfu-programmer $DUCK_CHIPSET get manufacturer
    sudo dfu-programmer $DUCK_CHIPSET get family
    sudo dfu-programmer $DUCK_CHIPSET get product-name
    sudo dfu-programmer $DUCK_CHIPSET get product-revision
    sudo dfu-programmer $DUCK_CHIPSET get ID1
    sudo dfu-programmer $DUCK_CHIPSET get ID2
    sudo dfu-programmer $DUCK_CHIPSET getfuse LOCK
    sudo dfu-programmer $DUCK_CHIPSET getfuse EPFL
    sudo dfu-programmer $DUCK_CHIPSET getfuse BOOTPROT
    sudo dfu-programmer $DUCK_CHIPSET getfuse BODLEVEL
    sudo dfu-programmer $DUCK_CHIPSET getfuse BODHYST
    sudo dfu-programmer $DUCK_CHIPSET getfuse BODEN
    sudo dfu-programmer $DUCK_CHIPSET getfuse ISP_BOD_EN
    sudo dfu-programmer $DUCK_CHIPSET getfuse ISP_IO_COND_EN
    sudo dfu-programmer $DUCK_CHIPSET getfuse ISP_FORCE
    echo "Done!"
    exit 0
    fi
    if [[ $1 == "flash" ]]
    then
    if [[ $2 == "" ]]
    then
    echo "No firmware specified! Flash failed!"
    exit 0
    else
    if [[ -f $2 ]]
    then
    echo "Flashing firmware file '$2'..."
    echo "Erasing duck (not SD) before flash..."
    sudo dfu-programmer $DUCK_CHIPSET erase
    echo "Flashing new firmware..."
    sudo dfu-programmer $DUCK_CHIPSET flash --suppress-bootloader-mem "$2"
    echo "Done! Use "duck reset" to reset/reboot the device."
    exit 0
    else
    echo "Cannot find firmware file. Flash failed!"
    exit 0
    fi
    fi
    fi
    if [[ $1 == "dump" ]]
    then
    if [[ $2 == "" ]]
    then
    echo "No file was specified to dump the firmware to! Dump failed!"
    exit 0
    else
    echo "Dumping firmware to '$2'..."
    sudo dfu-programmer $DUCK_CHIPSET dump > "$2"
    if [[ -f $2 ]]
    then
    echo "Dump file '$2' written successfully!"
    echo "The file is written even if you have encountered an error."
    exit 0
    else
    echo "Failed to write file '$2'. Firmware dump unsuccessful."
    exit 0
    fi
    fi
    fi
    if [[ $1 == "erase" ]]
    then
    echo "Erasing currently installed firmware (not SD)..."
    sudo dfu-programmer $DUCK_CHIPSET erase
    echo "Done!"
    exit 0
    fi
    if [[ $1 == "reset" ]]
    then
    echo "Resetting/rebooting device..."
    sudo dfu-programmer $DUCK_CHIPSET reset
    echo "Done!"
    exit 0
    fi
    if [[ $1 == "encode" ]]
    then
    if [[ $2 == "" ]]
    then
    echo "No input file specified!"
    exit 0
    else
    if [[ $3 == "" ]]
    then
    echo "No output file specified!"
    exit 0
    else
    if [[ $4 == "" ]]
    then
    echo "No keyboard layout specified!"
    exit 0
    else
    if [[ -f $2 ]]
    then
    if [[ -f $3 ]]
    then
    rm -f "$3"
    fi
    if [[ -f "$PATH_DUCK_PATH_LAYOUTS/$4.properties" ]]
    then
    echo "Encoding script..."
    java -jar "$PATH_DUCK_ENCODER" -l "$PATH_DUCK_PATH_LAYOUTS/$4.properties" -i "$2" -o "$3"
    if [[ -f $3 ]]
    then
    echo "Successfully compiled '$2' -> '$3'"
    exit 0
    else
    echo "Failed to compile '$2' -> '$3'"
    exit 0
    fi
    else
    echo "Layout '$PATH_DUCK_PATH_LAYOUTS/$4.properties' cannot be found! Encode failed!"
    exit 0
    fi
    else
    echo "Cannot locate input file '$2'! Encode failed!"
    exit 0
    fi
    fi
    fi
    fi
    fi
    if ! [[ $1 == "" ]]
    then
    echo "Invalid command specified! Use 'duck --help' for usage information."
    exit 0
    fi
  12. Yeah, you are simply missing the USB devices libraries:

    sudo apt-get libusb-dev

    That should do it.

    Best regards,

    Sebkinne

    Hi,

    thanks for the reply, "sudo apt-get libusb-dev" didn't work because you forgot the "install" argument, thanks anyway - most appreciated.

    Now that I've managed to get libusb installed (thank you!) - I'm still faced with issues.

    I've also just fixed the "gawk" error by running "sudo apt-get install gawk".

    Never the less, I'm still encountering problems when I compile the program.

    Now my output is:

    root@Lavanoid-NB:/home/lavanoid/bin/dfu-programmer# ./bootstrap.sh

    configure.ac:8: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated. For more info, see:
    root@Lavanoid-NB:/home/lavanoid/bin/dfu-programmer# ./configure
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    /home/lavanoid/bin/dfu-programmer/m4/missing: Unknown `--is-lightweight' option
    Try `/home/lavanoid/bin/dfu-programmer/m4/missing --help' for more information
    configure: WARNING: 'missing' script is too old or missing
    checking for a thread-safe mkdir -p... /bin/mkdir -p
    checking for gawk... gawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking whether to enable maintainer-specific portions of Makefiles... no
    checking for gcc... gcc
    checking whether the C compiler works... yes
    checking for C compiler default output file name... a.out
    checking for suffix of executables...
    checking whether we are cross compiling... no
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking for gcc option to accept ISO C89... none needed
    checking whether gcc understands -c and -o together... yes
    checking for style of include used by make... GNU
    checking dependency style of gcc... gcc3
    checking for pkg-config... /usr/bin/pkg-config
    checking pkg-config is at least version 0.9.0... yes
    checking for LIBUSB_1_0... no
    using libusb
    checking how to run the C preprocessor... gcc -E
    checking for grep that handles long lines and -e... /bin/grep
    checking for egrep... /bin/grep -E
    checking for ANSI C header files... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking usb.h usability... yes
    checking usb.h presence... yes
    checking for usb.h... yes
    checking for usb_interrupt_read in -lusb... yes
    checking for ANSI C header files... (cached) yes
    checking for an ANSI C-conforming const... yes
    checking for size_t... yes
    checking for stdlib.h... (cached) yes
    checking for GNU libc compatible malloc... yes
    checking for working memcmp... yes
    checking that generated files are newer than configure... done
    configure: creating ./config.status
    config.status: creating fedora/dfu-programmer.spec
    config.status: creating Makefile
    config.status: creating docs/Makefile
    config.status: creating src/Makefile
    config.status: creating src/config.h
    config.status: executing depfiles commands
    root@Lavanoid-NB:/home/lavanoid/bin/dfu-programmer# make
    Making all in src
    make[1]: Entering directory `/home/lavanoid/bin/dfu-programmer/src'
    make all-am
    make[2]: Entering directory `/home/lavanoid/bin/dfu-programmer/src'
    gcc -DHAVE_CONFIG_H -I. -Wall -g -O2 -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o main.c
    mv -f .deps/main.Tpo .deps/main.Po
    gcc -DHAVE_CONFIG_H -I. -Wall -g -O2 -MT arguments.o -MD -MP -MF .deps/arguments.Tpo -c -o arguments.o arguments.c
    mv -f .deps/arguments.Tpo .deps/arguments.Po
    gcc -DHAVE_CONFIG_H -I. -Wall -g -O2 -MT atmel.o -MD -MP -MF .deps/atmel.Tpo -c -o atmel.o atmel.c
    mv -f .deps/atmel.Tpo .deps/atmel.Po
    gcc -DHAVE_CONFIG_H -I. -Wall -g -O2 -MT commands.o -MD -MP -MF .deps/commands.Tpo -c -o commands.o commands.c
    mv -f .deps/commands.Tpo .deps/commands.Po
    gcc -DHAVE_CONFIG_H -I. -Wall -g -O2 -MT dfu.o -MD -MP -MF .deps/dfu.Tpo -c -o dfu.o dfu.c
    mv -f .deps/dfu.Tpo .deps/dfu.Po
    gcc -DHAVE_CONFIG_H -I. -Wall -g -O2 -MT intel_hex.o -MD -MP -MF .deps/intel_hex.Tpo -c -o intel_hex.o intel_hex.c
    mv -f .deps/intel_hex.Tpo .deps/intel_hex.Po
    gcc -DHAVE_CONFIG_H -I. -Wall -g -O2 -MT util.o -MD -MP -MF .deps/util.Tpo -c -o util.o util.c
    mv -f .deps/util.Tpo .deps/util.Po
    gcc -Wall -g -O2 -o dfu-programmer main.o arguments.o atmel.o commands.o dfu.o intel_hex.o util.o -lusb
    make[2]: Leaving directory `/home/lavanoid/bin/dfu-programmer/src'
    make[1]: Leaving directory `/home/lavanoid/bin/dfu-programmer/src'
    Making all in docs
    make[1]: Entering directory `/home/lavanoid/bin/dfu-programmer/docs'
    make[1]: Nothing to be done for `all'.
    make[1]: Leaving directory `/home/lavanoid/bin/dfu-programmer/docs'
    make[1]: Entering directory `/home/lavanoid/bin/dfu-programmer'
    make[1]: Nothing to be done for `all-am'.
    make[1]: Leaving directory `/home/lavanoid/bin/dfu-programmer'
    root@Lavanoid-NB:/home/lavanoid/bin/dfu-programmer# ls
    aclocal.m4 ChangeLog configure.ac m4 NEWS
    AUTHORS config.log COPYING Makefile README
    autom4te.cache config.status docs Makefile.am src
    bootstrap.sh configure fedora Makefile.in
    root@Lavanoid-NB:/home/lavanoid/bin/dfu-programmer#

    Really hope I can get this working :sad: .

  13. Hi,

    so I've started using Ubuntu (after a really long time) and I have a really frustrating problem.

    I have dfu-programmer-0.5.4 and I've already extracted everything from its archive, but I cannot compile the code so I can flash my duck. It cannot compile because the usb.h file is missing.

    lavanoid@Lavanoid-NB:/bin$ cd ~/bin

    lavanoid@Lavanoid-NB:~/bin$ ls
    arpsslstrip cpu_min_freq duckdump duckreset
    cpu_cur_freq cpu_temperature duckdump~ duckreset~
    cpu_governor dfu-programmer-0.5.4 duckflash manservice
    cpu_max_freq DKE duckflash~ sslstrip.log
    lavanoid@Lavanoid-NB:~/bin$ cd d*4
    lavanoid@Lavanoid-NB:~/bin/dfu-programmer-0.5.4$ ls
    aclocal.m4 ChangeLog configure.ac fedora Makefile.in src
    AUTHORS config.h.in COPYING m4 NEWS
    bootstrap.sh configure docs Makefile.am README
    lavanoid@Lavanoid-NB:~/bin/dfu-programmer-0.5.4$ sudo su
    [sudo] password for lavanoid:
    root@Lavanoid-NB:/home/lavanoid/bin/dfu-programmer-0.5.4# ./bootstrap.sh
    configure.ac:8: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated. For more info, see:
    configure.ac:15: installing 'm4/compile'
    root@Lavanoid-NB:/home/lavanoid/bin/dfu-programmer-0.5.4# ./configure
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    /home/lavanoid/bin/dfu-programmer-0.5.4/m4/missing: Unknown `--is-lightweight' option
    Try `/home/lavanoid/bin/dfu-programmer-0.5.4/m4/missing --help' for more information
    configure: WARNING: 'missing' script is too old or missing
    checking for a thread-safe mkdir -p... /bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking whether to enable maintainer-specific portions of Makefiles... no
    checking for gcc... gcc
    checking whether the C compiler works... yes
    checking for C compiler default output file name... a.out
    checking for suffix of executables...
    checking whether we are cross compiling... no
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking for gcc option to accept ISO C89... none needed
    checking whether gcc understands -c and -o together... yes
    checking for style of include used by make... GNU
    checking dependency style of gcc... gcc3
    checking for pkg-config... /usr/bin/pkg-config
    checking pkg-config is at least version 0.9.0... yes
    checking for LIBUSB_1_0... no
    checking how to run the C preprocessor... gcc -E
    checking for grep that handles long lines and -e... /bin/grep
    checking for egrep... /bin/grep -E
    checking for ANSI C header files... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking usb.h usability... no
    checking usb.h presence... no
    checking for usb.h... no
    checking for ANSI C header files... (cached) yes
    checking for an ANSI C-conforming const... yes
    checking for size_t... yes
    checking for stdlib.h... (cached) yes
    checking for GNU libc compatible malloc... yes
    checking for working memcmp... yes
    checking that generated files are newer than configure... done
    configure: creating ./config.status
    config.status: creating fedora/dfu-programmer.spec
    config.status: creating Makefile
    config.status: creating docs/Makefile
    config.status: creating src/Makefile
    config.status: creating config.h
    config.status: executing depfiles commands
    root@Lavanoid-NB:/home/lavanoid/bin/dfu-programmer-0.5.4# make
    make all-recursive
    make[1]: Entering directory `/home/lavanoid/bin/dfu-programmer-0.5.4'
    Making all in src
    make[2]: Entering directory `/home/lavanoid/bin/dfu-programmer-0.5.4/src'
    gcc -DHAVE_CONFIG_H -I. -I.. -Wall -g -O2 -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o main.c
    main.c:29:17: fatal error: usb.h: No such file or directory
    #include <usb.h>
    ^
    compilation terminated.
    make[2]: *** [main.o] Error 1
    make[2]: Leaving directory `/home/lavanoid/bin/dfu-programmer-0.5.4/src'
    make[1]: *** [all-recursive] Error 1
    make[1]: Leaving directory `/home/lavanoid/bin/dfu-programmer-0.5.4'
    make: *** [all] Error 2
    root@Lavanoid-NB:/home/lavanoid/bin/dfu-programmer-0.5.4#

    Can anyone help? Thanks.

  14. Very impressive.

    The only program that Microsoft Security Essentials flagged when running this payload was WebBrowserPassView.

    Is there any way to execute this program like you did the mimikatz which is normally caught?

    Unfortunately no. I don't have access to the source code of WebBrowserPassView (By Nirsoft). If I had source, then I could fix this issue. My only chance of bypassing this is if I had source code, or access to a program that works like WebBrowserPassView that someone else has created and who has released source code for it.

  15. As far as I can see, the only thing I can see as a possible way around this is having another USB with the PowerSploit toolkit on it, and executing the files off of that USB. Antivirus will detect this, however, and it will attempt to remove any miscellaneous files it will find on the USB. You really do need an internet connection for that particular invoke-mimikatz script.

    It doesn't matter what I try to run - Powershell doesn't want to work. I hate Powershell.

  16. Ok, why is Microsoft so stupid? Seriously! I've set my Powershell execution policy to "remotesigned" so powershell scripts can be executed, but when I try to run a powershell script (.ps1) - the output Window remains blank and the program quits. The only method that I can use to execute powershell scripts is using the download 'n' execute script that is commonly used on this forum.

    Its ridiculous. I've tried to execute the Mimikatz Powersploit Invoke scripts but they don't work unless I use the download 'n' execute script. I want to execute PS1 files locally WITHOUT HAVING AN INTERNET CONNECTION!

    Anyone got any ideas on how to fix this stupid issue?

    Someone needs to give whoever developed Powershell a punch around the mouth - SERIOUSLY! D*** heads.

    Microdick (Microsoft) can be so frustrating. Can't even go on Youtube with an xbox without paying for a gold subscription - money beggars.

  17. OK,

    As the title states, I want to be able to extract a encrypted zip archive and output the files directly into RAM with Powershell so that it was never written to the disk.

    Any ideas? Anyone written a script to do this? Would be great to implement it into my duck payload.

    If anyone has alternatives to the use of Powershell, then still consider replying - Powershell isn't mandatory.

    Thanks.

×
×
  • Create New...