-
Posts
37 -
Joined
-
Last visited
Posts posted by r6uur6nr6u5ur56
-
-
4 minutes ago, haze1434 said:
Seems OK, rfcomm is indeed using /dev/rfcomm0 as expected, as it created it.
Thanks for the tip, I already tried "chmod 777 /dev/rfcomm0" for fun earlier but no luck, same error
-
9 minutes ago, haze1434 said:
Try sudo lsof | grep rfcomm0
Let us know the output if no luck.
rfcomm 9730 root 5r CHR 216,0 0t0 49166 /dev/rfcomm0
I should note that I'm using a raspberry pi 3, don't know if it makes a difference
I'm guessing the "rfcomm" from above is the rfcomm process it self hosting the /dev/rfcomm0
-
6 minutes ago, haze1434 said:
Have you run the following?
gpsd /dev/rfcomm0
(to ask gpsd to use the data from /dev/rfcomm0)
Yes I have that tried that, but it instantly closes the gpsd process with no log/error message
-
For the life of me I can't figure this out, at the moment I have my phone sharing the GPS over bluetooth using the app (Share GPS)
I have the phone paired and using "rfcomm connect rfcomm0 xx:xx:xx:xx..." to create a serial rfcomm0 connection
When I use "cat /dev/rfcomm0" I see all the nmea output constantly flowing
but when check the status of gpsd (systemctl status gpsd)
I get the following output
● gpsd.service - GPS (Global Positioning System) Daemon Loaded: loaded (/lib/systemd/system/gpsd.service; static) Active: active (running) since Fri 2017-12-01 12:12:03 CET; 23min ago Main PID: 9645 (gpsd) CGroup: /system.slice/gpsd.service └─9645 /usr/sbin/gpsd -N /dev/rfcomm0 /dev/rfcomm0 Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: /dev/rfcomm0: device activation failed. Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: device open failed: Device or resource busy - retrying read-only Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: read-only device open failed: Device or resource busy Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: /dev/rfcomm0: device activation failed. Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: device open failed: Device or resource busy - retrying read-only Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: read-only device open failed: Device or resource busy Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: /dev/rfcomm0: device activation failed. Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: device open failed: Device or resource busy - retrying read-only Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: read-only device open failed: Device or resource busy Dec 01 12:35:10 raspi gpsd[9645]: gpsd:ERROR: /dev/rfcomm0: device activation failed.
but (cat \dev\rfcomm0) works fine, when I look in kismet I get the following message
ERROR: No update from GPSD in 15 seconds or more, attempting to reconnect INFO: Connected to a JSON-enabled GPSD version 3.11, turning on JSON mode
-
Nice idea, could be done I guess in the good old PHP, there is already a project going for some time tho, u can check it out here, http://www.fruitywifi.com
-
I tried it on my 3DS, but I was not able to login into the pineapple, it simply redirected back to the login page
-
Are there any europe shops open for the turtle ? if so, link :)
-
Pretty easy really. Just set the pi to have a static ip in the pineapple network range, then connect it to the pineapple. Once connected, you can connect your device to the pineapple's wifi and connect to the pi over that wifi connection.
Thanks, I aswell had to put the ethernet into Classic mode, it's working
-
I'm curious if it's possible to put a ethernet cable between the raspberry pi 2 and the pineapple and access the Pi2 through the pineapple's wifi
I've seen others been able todo so but I've seen no other thread how they got it working, anyone know ?
-
Yoo, is there a nice way to setup a boot script written in bash/shI'm trying to enable wlan0, wlan1 and wlan2 and after that enable airodumpCurrently I'm trying todo it through init.d but no luck really and the dip switches are funky in version 2.3.0Any help is appreciated :)
-
If you wanna to do the same things as mitnick you should see BEEF (XSS).
You could inject some malicious javascript inside the victim browser (like a fake adobe update) & get a hooks (->get shell->hi jacking cookies->steal password->etc...)
but I don't know if we could get beef into the pineapple
I'm curious about this aswell, can it be done together with a Raspberry PI ?
-
Anyone tried to pwn some consoles which are having wifi ?I know most of you are probably targetting devices like laptops, phones and such but what about gaming consoles ?Tried it earlier with my WII U and it was really easy with the pineapple
-
Did anyone got a Raspberry PI working with BeEF together with the Pineapple ?I'm curious how this can be done
-
So I tried to recreate this with my raspberry pi and I had no issue connecting to it. What are your network settings for the pineapple? Did you also create a static ip for the wifi pineapple?
Got it working, simply re-flashed the sdcard for the raspberry, thanks for the help
-
Can you locate the pi through the web interface of the pineapple? Also, from my quick little research; is your pineapple in wired client mode?
Through the web interface... ? I've tried classic and client mode but both didn't really worked, I putted a static ip on the pi 172.16.42.2, couldn't ping it from pineapple over ssh
-
Can you elaborate on how you have connected everything?
It's rather simple really, I have pi plugged in the pineapple and have the pineapple create a hotspot
And with phone or laptop I connect to the hotspot and can nmap etc
But atm I can't seem to find the pi when using nmap or I ping to the wrong ip/subnet
-
Yes, I have this setup with a pi, if you use the admin AP it will work just fine. You will want to set a static IP on the pi though.
I want the setup to be done over the cable, I can't seem to ping the pi when it's plugged in
SSH etc is enabled
-
I was wondering... is there a way to let's say plugin a ethernet cable in the PineApple to the Raspberry PI
And then connect to the Raspberry PI over the Pineapple's hotspot ?
This should be possible in theory, just wondering how it should be done with the pineapple :)
-
I tried your suggestion and changed to channel 3 times but without effect. Is it possible that the new Android versions do not send out network probes? The AP has it's default Pineapple name and is hidden.
Change the channel to 6, this 1 is more common
-
Winscp did even a worser job, couldn't even reach 1%, it nearly instantly gave a "Host is not communicating for more than 15 seconds. Still waiting"And this is over ethernet, it did aswell the same result over wirelessPutty, SSH all works fine... but transfering files ? oh nooThe file I'm trying to transfer is 36,288 KB
Edit: woow I disabled the infusion "RandomRoll" and all the sudden it started transfering the fileEven did a reboot just to be sure... first it didn't download the file at all just 0%, disabled RandomRoll infusion, boom transfering and completed itSomebody should look into that infusion to see wth is going on -
Have you tried running the command with the -v option to see why the disconnects are occurring?
-v ? I'm using FileZilla in windows
-
Just like the title says, I keep getting disconnected when having a connection to the pineapple over Ethernet or Wireless
Every 1-3MB orso it will disconnect and everytime I had to keep hitting resume for a 30MB file it's a pain
Anyone else having this problem aswell ?
-
Very cool idea. Hey whatever works the best for your situation :)
The nice thing about the GPS however is that the simple act of powering it up automatically starts the receiver and looks for sats. So during the 45 seconds or so of the pineapple booting up it usually already has a lock by the time the script starts. The scripts usually takes about 5-20 seconds depending on cold start vs hot start. The Globalsat has a built in supercapacitor that helps keep a lock even after you power it off. This function of course only lasts maybe an hour before it becomes "cold".
Also, no SSH required, which is how I use my pineapple in the feild usually. I like it to be preconfigured and able to deploy autonomously. But like I said, whatever works best for your situation.
One of these days I'd like to experiment with adding a Real Time Clock like this one to the Pineapple.
Thanks
GPS could be fun for kismet etc, which I don't use currently will maybe in the future
A real time clock would be the best fix there is
Wireshark finds the time weird in the column... lol
In the actual packets it's showing the correct time
-
I use a Globalsat BU-353. It only draws about 60mA @9v (measured from the pineapple power supply) but is only needed while the script is running. I simply unplug it afterwards unless i'm using it for other things like Kismet. I also have an older Pharos iGPS-500 that does the job but is much slower and clunkier. I prefer the Globalsat.
I will probably get a GPS stick eventually, but atm I found a even better solution
So, here is my solution, we let the pineapple SSH into a android device, grab the phone's time and voila pineapple is having the time without internet
Stuff I did to get it all working:
1. SSH into the pineapple
2. Go into /root/.ssh
3. ssh-keygen -t dsa (do not fillin a password)
3. cat id_dsa.pub >> ~/.ssh/authorized_keys
4. now copy that id_dsa.pub from your pineapple to the Phone (or laptop whatever) I simply used FileZilla
5. Copy that id_dsa.pub to /<YourHomeFolder>/.ssh
6. cat id_dsa.pub >> ~/.ssh/authorized_keys
7. Create a set_date.sh on your Pineapple in /root/set_date.sh
#!/bin/shdate `ssh USER@HOST date "+%y%m%d%H%M.%S"`8. chmod +x set_date.shSet the Cron job on your pineapple, I setted mine to 5 minutes, could even do 1 minute tbh*/05 * * * * /root/set_date.shThis should do the jobThis method might even be quicker then using a GPS stick since you'd probably have to wait for a lock or somethingDon't forget to use a static ip at your own device (not the pineapple) incase ip changes and script no longer works...
Kismet and Gpsd serial
in Questions
Posted
When looking through dmesg I notice this
not sure if the "not supported" is the problem because I can open "cat /dev/rfcomm0" just fine, not sure how gpsd thinks about it
[ 70.176926] Bluetooth: RFCOMM TTY layer initialized [ 70.176966] Bluetooth: RFCOMM socket layer initialized [ 70.176987] Bluetooth: RFCOMM ver 1.11 [ 77.927678] Bluetooth: TIOCGSERIAL is not supported [ 87.020196] Bluetooth: TIOCGSERIAL is not supported [ 87.021156] Bluetooth: TIOCGSERIAL is not supported [ 93.020151] Bluetooth: TIOCGSERIAL is not supported [ 401.665876] Bluetooth: TIOCGSERIAL is not supported [ 401.670516] Bluetooth: TIOCGSERIAL is not supported [ 411.021010] Bluetooth: TIOCGSERIAL is not supported [ 411.021251] Bluetooth: TIOCGSERIAL is not supported [ 411.022220] Bluetooth: TIOCGSERIAL is not supported [ 411.022454] Bluetooth: TIOCGSERIAL is not supported [ 417.020636] Bluetooth: TIOCGSERIAL is not supported [ 417.020832] Bluetooth: TIOCGSERIAL is not supported [