Jump to content

Kel

Active Members
  • Posts

    15
  • Joined

  • Last visited

Everything posted by Kel

  1. Kel

    WiPassDump

    Hi Bob, yeah, for you it'll be : Q SET_LANGUAGE us (or gb if you are from Great Britain) Silly question, do you use it on a computer that has some WIFI capabilities ? Whatsoever, what is the result of this command : netsh wlan export profile key=clear in a command prompt ?
  2. well my bad it doesn't work here neither.. guess I'll just drop the usual : Q SET_LANGUAGE fr before my scripts
  3. I think you can change the us.json located here /tools/languages and put your own file like gb.json and it will be used by default.
  4. did you follow this guide first ? https://forums.hak5.org/index.php?/topic/40358-initial-config-of-bash-bunny/#comment-288056
  5. did you follow this guide first ? https://forums.hak5.org/index.php?/topic/40358-initial-config-of-bash-bunny/#comment-288056
  6. as it is specified in the payload : # Use RNDIS for Windows. Mac/*nix use ECM_ETHERNET so depending on the settings you chose it works on Win / Mac / Nix
  7. I was able to install this driver. ATTACKMODE SERIAL Open Device Manager Right click on CDC Serial under 'Other devices' Left click 'Update Driver Software...' search on computer for driver ... Choose from a list... in the list pick : Linux Developer Community / Gadget serial (should be present if you have already connected to your bashBunny in arming mode) profit
  8. Kel

    WiPassDump

    Same here I had to rewrite this one. Works now in Win 10 & 7 here is my version based on samdeg555 's (BTW : no need of a.cmd anymore) payload.txt
  9. French keyboard, s'il vous plait ! But I think it is already On, by using : QUACK SET_LANGUAGE fr
  10. You get greeted by a blank page, that did surprised me as well. Just press enter a few time you'll see the prompt asking for your login / password
  11. I have noticed that the stop url snarf command doesn't always work (as you mentioned the right PID is not killed) solution : exit turtle shell type : ps to show active process note the <pid> of urlsnarf type : kill <pid> to kill the process manually return to turtle shell then go to configure choose SSHFS (option 1 for the logs) then back to the previous menu (urlsnarf should be stopped at the time beeing) start urlsnarf exit turtle shell go to /SSHFS on the turtle browse in http (ursnarf is listening to 80 / 8080 etc...) you should find a urlsnarf log file. which should also be found under /home/turtle in you VPS
×
×
  • Create New...