b0N3z
-
Posts
1,451 -
Joined
-
Last visited
-
Days Won
41
Posts posted by b0N3z
-
-
-
-
33 minutes ago, Dave-ee Jones said:
Ah, I was going to say you could do better testing with another LED colour (instead of it looking the same, so you could tell if it worked or not), and check your firmware version (arming payload was only supported in 1.3 I think).
Yea I just copied over the payload I already used on switch 2 so now that it's up I'm going to play around a bit. I way over thought that one lol
-
am i maybe doing it on the wrong root directory? I ssh to the bunny and
cd /
mkdir /payload/arming
nano payload.txt
does this directory need to be on the storage part of the partition
EDIT: I over complicated this setup and have now figured it out. thanks lol
-
-
For some reason I make this directory /payloads/arming/payload.txt to change arming mode from serial storage to ecm_ethernet and storage and use a standard payload of
LED B SLOW
ATTACKMODE ECM_ETHERNET STORAGE
the bash bunny doesn't recognize it and keeps the default serial storage payload after a reboot. Am I doing something wrong or is there a step I'm missing?
-
if your computer is not supplying enough power to the pineapple it will do funny things. the nano needs 5v2a so depending on your usb ports you might need to use 2 or 1 and a battery. I usually always connect mine with a battery that is 5v2a just to make sure its not going to do anything funky on me.
-
how are you powering the nano?
-
it will work on any firmware. Just make sure you have that .bin file and the inject.bin file.
-
check this out https://ducktoolkit.com/vidpid/ . find the device you want and download the .bin and place it next to your inject.bin. boom you have a different keyboard.
-
This thread will help
-
have you tried to use a live usb and run kali that way? It is way better than messing with a vm if you are unfamiliar with vm software.
-
its amazing, been using it ever since lol
-
most of the modules are basic programs that are used on kali, so if you can watch a video or read an article or the man page for say mdk3, that would be the deauth module. so anything that mdk3 can do on kali, deauth can do on the pineapple. thats just an example.
-
21 minutes ago, ju663rn4u7 said:
I saw that in your old thread. I was looking for an Apple keyboard.
PID 0273 . VID 05ac . this is a 2015 mbp
-
1
-
-
I had created a list to get around using the above list. My list is for most used devices not all.
-
1
-
-
you might need to use both usb from the y cable
-
its an openwrt router so anything you can do on Openwrt
-
you dont have enough power going to the nano. it needs 5v2a which isn't always what usb on a pc is. which can cause problems while using the pineapple nano.
-
1
-
-
if all your doing is setting up the bunny for future attacks then why does it matter. change your payload when your done.
-
just set a payload on switch 1 or 2 with RNIDS_ETHER and STORAGE
-
I think the point was to keep it as small as possible with big power. and thats what they did. Why add wifi and other things that will eat power and cause more heat?
-
1
-
-
On 8/21/2017 at 6:52 AM, i8igmac said:
I use it almost daily with juicessh from my android phone, after this intro I'm sure you will use it too. Just a example below.
kali@kali:~$screen (New session started with PID=4456) kali@kali:~$airodump-ng -w log-handshakes -i wlp3s0 (ctrl+a+d... disconnect from console and runs in background, We can connect back to the console later) kali@kali:~$screen (Another session with PID-4457) kali@kali:~$mdk3 -I wlp1s0 -d (ctrl+a+d... disconnect from console and background the process.) kali@kali:~$exit (Both sessions are still running)
So. There are 2console applications currently running. The first one is logging handshakes. The second session or daemon is deauthrnticating all clients in range.
I can connect back to these screen sessions at anytime.
kali@kali:~$creen -r 4456
you could do the same with kismet, I assume you are logging data just like I have done with the above example.
I think you can also start kismet with a rc.local startup script using SCREEN to allow you to connect back to the session
Just got around to messing with this and you are correct, this is awesome, definitely going all my RPi.
-
On 8/2/2017 at 9:31 AM, haze1434 said:
I run a headless RPi3 in my car for automation.
Use this and SSH in to it from your phone/whatever you like. Full shell on-the-go. And when you're near a recognised WiFi, it connects to that instead. Lovely.
When you disconnect the SSH session, the RPi can carry on whatever it's doing. You can then SSH back in to it at a later time and stop kismet.
Use the bg and fg commands when running Kismet and you can come back to it later.
This setup you have is awesome. I setup followed that for my rpi3 and worked great. but still stuck on the being able to disconnect from the pi and still keep kismet running and then be able to reconnect later to check on it or stop it.
On 8/2/2017 at 0:54 PM, i8igmac said:have you looked into screen?
screen will allow you to escape from a console while leaving your current application running in the background. You can then connect back to the screen session later on.
So my experience with screen is very little. I read through a couple pages about it and got the tl:dr. would this something I can do from my android phone with an app like juicessh? I installed it on my pi and use it on osx to connect to the bashbunny via serial. but thats about it.
Association Issue
in WiFi Pineapple TETRA
Posted
The pineapple will not work if your using your home routers ap as with PineAp. Your home router has a password and the pineapple takes advantage of you having saved open APs on your devices and it says " hey im that openap, connect to me" . So long story short, I won't replicate a password protected AP without a password.