crazyclown
-
Posts
39 -
Joined
-
Last visited
-
Days Won
2
Posts posted by crazyclown
-
-
Not seeing much new stuff in the turtle world lately, so I thought I'd show you guys a trick I cooked up this afternoon. Its a pretty silly hack, but hey why not.
While I'm not necessarily sure why anyone would do this, I thought I'd post proof positive that it can be done.
With sshfs active (I have mine going to /sshfs) to your home server, in the cli:
opkg updateopkg install screenopkg install rtorrent
Start up screen with...screen...thenrtorrent -n -d /sshfs/ LegalLinuxDistro.torrent
Start up the torrent by selecting it with the arrow keys and hit Ctrl+s to start it up.
This way the torrent traffic is over whatever network you have your turtle dropped on and your own ISP only sees ssh traffic via sshfs! It's pretty slow, bottlenecked by the turtle's tiny proc, but as far as easy mode encrypted torrenting goes, its pretty slick.
Enjoy!
telot
Pretty neat, would be sweet if it worked with the Tor module. Will test and update.
Thumbs up for coming up with the idea. How slow is it exactly in regards to download speed?
-
;
Not trying to be cheeky. The intent isn't to push everyone who bought a Mark V to buy a NANO. As always we're working hard to make the best product possible -- and we believe that the NANO is a massive improvement overall.
We developed the NANO with the highest performance, most reliable components we can obtain. They were arranged in such a way that the usage is streamlined. Wrapping it all together is the new software which focuses on workflow and integrates with multiple platforms easily.
Once you use the NANO you'll see it's a completely different experience.
It is a shame that the RTL8187 was discontinued far before we expected. This caused a pineapple drought which put a huge burden on us at a time when we're very much invested in the next generation of the platform.
We prototyped a version of the Mark V with an alternate to the RTL8187, but it came with its own complications and by the time it was sourced, manufactured, tested, certified, etc -- we could have spun up development on a new system entirely. At the same time having received feedback and done user testing we realized an entirely new approach to the WiFi Pineapple was possible -- which we've now begun to realize through the NANO.
We aren't saying that we won't be developing the new web interface for the Mark V. And it's more than just a UI -- it's a completely new system with compartmentalized components and a rich API to control the device that's agnostic from the web interface. This opens the door to some really great opportunities.
If you bought a Mark V for $100 at launch you received over 2 years of firmware updates including additional features such as PineAP for free. That's the sort of customer service we're committed to and I'd say that's above and beyond the industry norm.
The plan is to make a build of the 6th generation software available for the Mark V. There are various internal differences that add subtle complications, but nothing that can't be remedied. This won't happen immediately as we're focused on wrapping up the firmware for the NANO and the forthcoming 5G hardware. Based on our current timeline I think February is achievable.
This dev kit launch with the first dibs to the forums was done in order to get momentum behind new modules. The core functionality is complete, but it's only together as a community that we're going to realize the full potential of the new platform.
It should also be noted that we have only begun to scratch the surface of the new platform. Remember, the Mark V didn't realize PineAP until 10 months into its life. I'd say similar advances are feasible with the 6th gen system.
If this were any other industry you would probably expect software license fees and such -- but that's not our style. We toyed with the idea of charging for a software update, but in all honesty I have doubts anyone would pay for what they've come to expect for free. Would you pay for the new system on the Mark V?
Lastly, as you can imagine all WiFi Pineapple advances come at considerable cost. Not only in the hardware engineering, sourcing, manufacturing, testing, certification, licensing, etc -- but the continued software development we've enjoyed for the last several years. I think our sole full-time developer Sebkinne deserves significant credit alongside this community of module developers in making the WiFi Pineapple the best wireless auditing platform available.
Thanks for taking the time out to respond, much appreciated.
The whole quoting thing is giving me a headache so I will type up my response all in one.
I have no doubt the Nano will be a new experience, as I mentioned before I will most probably get one. I am not implying in any way that you guys didnt work hard on it or that you dont deserve recognition, quite the contrary actually. As a WiFi pentesting enthusiast much of my work has been possible because of your gadgets. You mentioned:
If you bought a Mark V for $100 at launch you received over 2 years of firmware updates including additional features such as PineAP for free. That's the sort of customer service we're committed to and I'd say that's above and beyond the industry norm.
Which is totally correct, however Id rather pay $200 for the device and expect 4 years of firmware updates rather than having to pay for a new device which isnt really that much different and thats the point Im trying to make. Once again you mentioned:
Would you pay for the new system on the Mark V?
And the answer is no, but I would pay more for the Mark V and expect updates for much longer, and Im sure many here feel the same way. Just look at Apple, most of what youre paying is for the constant software updates, the hardware itself costs like a 1/5 of the actual price.
What it boils down to is the short comings of the Mark V, for instance, limited RAM. For anyone who has done a penitent for more than 5 minutes, you will notice that the Mark V eventually becomes non response and auto reboots and if you dont have a cron job in place, you need to start all over again. Has this been addressed in the Nano?
SSL Strip is obsolete, and so is SSL Strip 2 unless it is combined with DNS2Proxy and Delorean. Is this something that has/will be implemented in the Nano?
For those who have used the Mark V inside out, you will understand where I am coming from. All Im saying is, when I heard about the new Pineapple, I expected some serious updates besides a shiny new web interface but based on what I have seen and read it doesnt seem to be the case. I could be wrong and the new device can and will do all the points I have mentioned, but based on the information you have provided so far, it doesn't appear to be the case.
-
2
-
-
Okay so the new gadget looks cool, no doubt, so job well done.
But I can't be the only one who notices that it's no different from the Mark V, just smaller and with a better web interface, something they could have easily accomplished with the Mark V, but then again that wouldn't drive sales. Rather cheeky if you ask me. Yes yes i understand the RTL8187 is discontinued and you had to come up with something new, but come on, you can't seriously say you couldn't develop the new web interface for the Mark V as well. The point I'm trying to make is, a lot of people spent good hard earned money of the Mark V, and it's disappointing to see that you're just going to push that to the side with no updates or support, especially when the new Pineapple is pretty much the exact same thing. You can very easily continue support and updates for both side by side but i doubt you will.
Still dont believe me? I'll bet the new Pineapple still doesnt have SSL Strip 2 or DNS2Proxy, so how different is it really from the old Pineapple? I hope I'm wrong, and if I am win win for everybody, and if I'm not, well I told you so.
Lastly, no I'm not trolling, credit where it's due, the LAN Turtle was a genius invention, hats off to the Hak5 Team for making that happen, but this just seems like a stunt for driving sales.
Before a moderator swoops down and tires to save the day, let me just say, relax. You will get my money, there is a good chance I will get the new Pineapple, because I can afford to, but I know there are a lot of people out there who can't and this is for them.
-
1
-
-
I set up and installed as the OP said, but i keep getting hangs in Reaver and Wash. More specifically wash does not show any APs and Reaver says its waiting for a beacon response. Do any packages or dependencies for pixie have incompatibilities with any infusions possibly?
Sounds to me like wlan1 is in use, Reaver and Wash won't work if it is.
-
First post updated, new build up, with new features and bug fixes.
important note, -vvv (yes that 3 v's) is now used to display "PixieHashes" you must use this now instead of -vv.
also, ive added auto hash logging with the -H switch.
so if coupled with -vvv and or -P or -K 1 etc, it will save a log of all the hashes gathered with a filename of the target bssid [macaddress].pixie
this file also includes a full command ready for putting into pixiewps, or you can chmod +x the file, and just run it as a script to auto crack the hashes.
there has also been a new default pin generator added :)
Very useful update, it's doesn't get simpler than this.
-
You have connected the Ethernet cable right?
Also you could try this method although I'm not sure if it will work if you just flashed it:
1. Connect Pineapple to your router via Ethernet.
2. Check your router for connected devices and find the IP of the Pineapple.
3. Try to connect with:
IPFROMROUTER:1471
-
Install Apache on the laptop and forward all traffic from the Pineapple using dnsspoof or iptables.
Although if hosting a website is all you want to do, the Pineapple runs Nginx, so you don't really need the laptop.
-
Its "tmp" and not "temp". Try "cd /tmp"
I kept getting the mismatch error myself so had to do it manually.
-
Tested, works wonders! Haven't had any issues yet, although the brute force (-f) takes considerably longer than a laptop/PC, but that's due to the Pineapple's low specs.
-
Still in the process of testing, will let you know how it goes.
-
Awesome, been waiting for this!
-
Check your PM, there was a lot to paste so I've just sent you a message.
-
The -P switch doesn't do anything.
root@Pineapple:/sd# reaver -i mon0 -b 9C:97:26:XX:XX:XX -c 1 -vv -P
Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright © 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>
reaver: invalid option -- P
[+] Switching mon0 to channel 1
Required Arguments:
-i, --interface=<wlan> Name of the monitor-mode interface to use
-b, --bssid=<mac> BSSID of the target AP
Optional Arguments:
-m, --mac=<mac> MAC of the host system
-e, --essid=<ssid> ESSID of the target AP
-c, --channel=<channel> Set the 802.11 channel for the interface (implies -f)
-o, --out-file=<file> Send output to a log file [stdout]
-s, --session=<file> Restore a previous session file
-C, --exec=<command> Execute the supplied command upon successful pin recovery
-D, --daemonize Daemonize reaver
-a, --auto Auto detect the best advanced options for the target AP
-f, --fixed Disable channel hopping
-5, --5ghz Use 5GHz 802.11 channels
-v, --verbose Display non-critical warnings (-vv for more)
-q, --quiet Only display critical messages
-h, --help Show help
Advanced Options:
-p, --pin=<wps pin> Use the specified 4 or 8 digit WPS pin
-d, --delay=<seconds> Set the delay between pin attempts [1]
-l, --lock-delay=<seconds> Set the time to wait if the AP locks WPS pin attempts [60]
-g, --max-attempts=<num> Quit after num pin attempts
-x, --fail-wait=<seconds> Set the time to sleep after 10 unexpected failures [0]
-r, --recurring-delay=<x:y> Sleep for y seconds every x pin attempts
-t, --timeout=<seconds> Set the receive timeout period [5]
-T, --m57-timeout=<seconds> Set the M5/M7 timeout period [0.20]
-A, --no-associate Do not associate with the AP (association must be done by another application)
-N, --no-nacks Do not send NACK messages when out of order packets are received
-S, --dh-small Use small DH keys to improve crack speed
-L, --ignore-locks Ignore locked state reported by the target AP
-E, --eap-terminate Terminate each WPS session with an EAP FAIL packet
-n, --nack Target AP always sends a NACK [Auto]
-w, --win7 Mimic a Windows 7 registrar [False]
Example:
reaver -i mon0 -b 00:90:4C:C1:AC:21 -vv -
Thanks for your responses
If i set up sslstrip2 and dns to reverse changes on vps would that work?
Could i somehow forward all traffic from the wifi pineapple to a vps with the above setup?
There is some success rate, but not on the latest browsers. Futhermore, dns2proxy won't work on the Pineapple.
Not sure what you hope you achieve by forwarding traffic to a VPS, but you can do that using IP tables.
-
The Pineapple on its own will only get you so far, combine it with a laptop running Kali or BackBox and the sky is the limit. You just have to be creative with what you want to do.
-
Google "sslstrip" and "HSTS" and you will have your answer. Afterward check your Pineapple for available infusions.
-
Anyone? help? I think it is something to do with nginx
Yes, you need to first generate your own certificate and then modify the nginx.conf located in /etc/nginx/ and enable SSL and add the path to the .crt andd .key files.
Just do a simple Google search on how to do the above.
-
Hi everyone,
I'm trying to create a rogue AP with PineAP feature to get the most of my Wifi Pineapple.
After tying a source mac (a spoofed MAC) and a target mac (my tablet's one) on PineAP Configuration infusion, then I click on "Start Now" and my Wifi Pineapple seems to not work properly: red led goes off, and sometimes led green remains the only one... Access to Pineapple is missed and I need to turn it off and on again.
Am I missing some important steps?
Any help will be very welcome
Try without spoofing the MAC. Another thing you can try is changing the MAC after you start PineAP.
-
Sorry for going off topic briefly but I wrote this little python script that could be used to find open APs and connect automatically. I'm using python because it is much easier to parse with than bash.
import subprocess import os SSIDs = subprocess.check_output("iw wlan1 scan | grep SSID | awk '{ print $2 }'", shell=True) for ssid in SSIDs.splitlines(): if "\\x00" in ssid: continue cmd = "iw wlan1 connect -w " + ssid os.system(cmd)Of course you will need to change the interfaces to match your own and suppress any output you don't want to see but this will scan APs and attempt to connect to each one. It will only connect if the AP is open (which I'm assuming is what you want because you want to be a MITM on a public network).
I'm not sure if there will be any issues when called from the DIP switches but you can run it like any other python script.
Hey thanks for taking the time out to write this, much appreciated. Just tested it out, it throws out a few errors but seems to connect. The only problem is it doesn't obtain an IP. What would be the OpenWRT equivalent of "dhclient wlan1"?
Thanks again.
-
You can use something like DNS2Proxy and SSLStrip2 i've heard and seen it works to get around HSTS
Not any more, plus as LeonardoNve has deleted sslstrip2 I doubt there will be any updates.
-
I see, is there other methods I should be aware of that are more modern?
What infusions do you think are a must-have?
None for the Pineapple.
Depends on what you want to do. If you have the storage capacity install them all and see what works for you.
-
Most browsers today use HSTS so SSLstrip is pretty much useless.
-
Got my second Pineapple yesterday and I haven't really had much success with this. Any advice?
So far I've changed the IP of the second Pineapple to 172.16.42.2, connected it to the internet using wlan1, then connected it to my laptop using Ethernet. I then tested it by browsing websites on my laptop (which isn't connected to any network except the Pineapple) and it seems to work fine. So now when I connect it to the other Pineapple running PineAP, the clients connected to PineAP still can't get internet.
Do i need to run the wp5 script on the second Pineapple or something? I'm guessing I need to change the "Wired Internet Settings" to "Client Mode". Not sure if I need to use static or DHCP?
-
If you're booting up Kali then the Mac OS plays no part. I don't know of a single Linux distribution that doesn't play well with the Alfa AWUS036NHA.
sslstrip
in LAN Turtle
Posted
Unless the victim is using Internet Explorer, I don't see the point of having SSL Strip as it is obsolete now. If we could use Delorean, SSL Strip 2 and DNS2Proxy then we would be talking.