-
Posts
15 -
Joined
-
Last visited
Posts posted by Kel
-
-
well my bad it doesn't work here neither..
guess I'll just drop the usual : Q SET_LANGUAGE fr
before my scripts
-
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.
-
did you follow this guide first ?
https://forums.hak5.org/index.php?/topic/40358-initial-config-of-bash-bunny/#comment-288056
-
did you follow this guide first ?
https://forums.hak5.org/index.php?/topic/40358-initial-config-of-bash-bunny/#comment-288056
- 1
-
omg
-
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
-
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
- 1
-
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)
-
French keyboard, s'il vous plait !
But I think it is already On, by using :
QUACK SET_LANGUAGE fr
-
On 12/03/2017 at 8:05 PM, word2yamutha said:
Hello. I was just wondering if anyone else has experienced this issue, since this is the first time I have used it. I checked device manager and Bashbunny is set to COM4 and Bits per second is set to 115200, data bits: 8, parity bit: No, Stop bit: 1 like it says in the readme file. I set it up the same in Putty and run it as admin. It just loads to a black screen and nothing happens. I'm I missing something or did I get a defective device? Thanks
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
- 1
-
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
WiPassDump
in Bash Bunny
Posted · Edited by Kel
orthography / spelling / grammar
Hi Bob,
yeah, for you it'll be :
Q SET_LANGUAGE us
(or gb if you are from Great Britain)