fringes

Well as Darren said in this post, "1.5 and PineAP to be released on or before DEFCON." That's just a week away. Perhals they'll do something at B-Sides, but either way, you can wait a week.

Or even mv /pineapple /pineapple-ORIG But I think you should try to work directly with Sebkinne, the pineapple software guy. And get a pineapple too, so you can test your work. Also, Version 1.5 will be released at DEFCON (or Bsides) in just about a week. There could be many changes.

Darren, just to be clear... This command should port forward (-R) port 80 from the pineapple (localhost:80) to all interfaces (e.g. NICs) on the remote server (0.0.0.0:80), correct? You can of course combine this with multiple -L or -R port forwards on the same tunnel.

Ok, I reached into my bag to see what I had and pulled out a piece of unbranded Chinese junk. I edited /etc/config/network adding: config interface lan2 option ifname eth1 option proto dhcp Then I plugged the adapter in to the pineapple and connected it to the router, plugged in my pineapple, and it got an address and worked! The only info I have on this is Model No: KY-LAN772BL Are there any plans to update the Network infusion to help with this? I sure wish the MkV had two USB ports, I had to unplug my shiny new Alfa to test this.

According to the Pineapple Bar, the GET infusion will: A further description in one of the GET related topics (linked in an earlier post in this topic) states: Indications from fairly recent posts are that it is up to date again. I think your other questions are really off topic for GET Infusion support. But if your 2gb micro-SD card doesn't mount on boot, I suggest you reboot. If it still won't mount, I suggest you reformat it via the "Format SD Card - (Experimental)" link under the "USB Info" tab of the "Resources" infusion.

The pineapple is a tool, a small computer with multiple interfaces and a simplistic UI with several "infusions" to get it to do all kinds of neat stuff. A pineapple is small enough (and cheap enough?) to leave discretely embedded behind a client's firewall during certain engagements. It can also be remotely and securely controlled even while it is behind a firewall. The pineapple doesn't do anything you can't do with any other computer with the same software and interfaces. The tools it uses are all open source and avaliable on many other platforms. WRT the video you reference, It obviously worked when Darren recorded it, and I believe he ended with the following caveat: This is the world of information security and it is constantly changing. It's unfortuate for you that you jumped in while the one exploit that interested you is becoming less effective. Score one for defense! The pineapple is still useful for many other things, and there are reportedly changes on the horizon regarding Karma. I don't perceive any shameless advertising or misleading impressions in that video; I believe you misunderstood what you were watching. So Facebook (and browsers) finally cleaned up some of their most egregious vulnerabilities. But not everyone did, not by a long shot, and there's still plenty more where that came from. I'm sure you can probably return your Mk5 to the hakshop for a refund, but is that one attack really all you bought it for? If so, you might not understand the legal implications of an MITM attack: If you MITM people without written permission from someone with the authority to grant it, that's illegal. So if that's your intent, it probably is better that you return it, ask for a refund, and get another hobby. PS: If you do want to learn more and explore this and other tools, then stick around and read all you can including the link thesugarat provided.

Connect your Ethernet cable and browse (with a browser) to http://172.16.42.1:1471/. Then go into the Network infusion, select the Access Point tab, add an SSID, select a channel, and save. Does the SSID show up in your computers WiFi list? If so, connect to it and browse again to http://172.16.42.1:1471/. Does that work for starters? I absolutely use the WiFi Manager too, as it's very useful. But you shouldn't need it just for this. I wouldn't clear out any infusions either. Just minimize the ones you aren't using to declutter your display.

Sigh, I wish I were going to DEFCON this year... OK, staying tuned.

It seems to be focused only on the ralink (rt2800...) driver, not the rtl8187. I'll have to dig in my bag to see what I can find. And I found one!!! Still having problems connecting, but this needs to be an infusion.

Alright, it's now Sunday morning, I'm well into my 2nd cup, and I was just about to open Josh's blog. Thanks for posting this. (Sadly, I can't get it to run with my AWUS036H; it won't go into AP mode.) This would be an awesome infusion! I really hope someone picks this up and writes an infusion; I wonder if Josh owns a pineapple.

So if not on a network and not in range of WiFi, what's left? Is that what you're asking? I still don't understand what you're trying to do. Please spell it out.

In general, to install other packages from the UI, install the "OPKG Manager" infusion. Internet Explorer? This doesn't sound like a good idea though. Wasn't that article for the MkII? This is the MkV forum. Edit: But you know what? The MkV is so easy to re-flash, have a blast!

I would, but it's Friday afternoon and I'm just not motivated enough to Google it.

If you provide more details regarding the infusion(s) you are using (Network and/or WiFi Manager), the firmware version (1.4.1?), in this case your OS and browser, and use specific language, I'm sure we can give you enough clues to get you up and running in no time. PS: Also mention anything that may be different from the stock setup, such as antennas.

Try it using Chrome.

People talk about things working when they use Windows 7 or 8, but I don't know how that affects the pineapple. I presume you're using either Firefox or Google Chrome, right? It seems there are parts of several infusions that only work correctly with Chrome. So I would say as a rule of thumb, use Chrome when you are having infusion problems. Since you are using the WiFi Manager infusion, try using the Network infusion too. It looks like you might have identified at least one bug. See if you can identify the exact behavior and under what circumstances. For bugs in the WiFi Manager infusion, post it in the Mark V infusions forum, specifically the "[support] WiFi Manager" topic, and for Network infusion bugs, open an issue in the Bug Tracker. Based on your statements above, I suspect that what is happening is that some bash scripting is being used in the infusion and is interfering. (I have not looked at any of the WiFi Manager code, although I have studied the Network infusion code.) In bash (most of the shells), "$$" resolves to the current process id. So "5$$" would be evaluated as 5 + the current process id. I expect the value "5$$" is being saved correctly, but is being reinterpreted for display. So, to continue your experiment, make sure you put the key back to 5$$ each time you save. If the above is correct, please post back, and post reports/bugs to the appropriate linKs above.

Where did you install them and where were they supposed to be installed? What did you do to cause them to install to the /sd card?

I had this problem and then realized that I didn't actually select the list. Make sure your list is selected from the pull-down before you click start.

The comparison of telnet to netcat was intended as humor, highlighting the clear text/poor security issue. When you use a short serial cable, you can use clear text without fear of compromise. But once you send your data "over the air," it's out there for all to see. You might not care about your data being compromised, but how 'bout the passwords? Bluetooth is just another wireless protocol, so it is visible to others. Check out the Ubertooth One from the HakShop.

Please let telnet just die, netcat is much more useful. Bluetooth has it's uses, but it's a low bandwidth technology. I like that it has a short range, but I wouldn't want to use it for tethering. I know you can SSH over Bluetooth, but I think other cheap WiFi dongles are (almost?) always a better option. What exactly is the use case for this idea with the pineapple? I'm not criticizing the idea at all; I think "just to do it" is a perfectly respectable answer. But I'm curious to know if there's a more practical reason too.

What do you mean by "encrypted password?" Did you just put in your plain password? What happened when you tried it with encryption set to none? Are you using the "Access Point" tab of the Network infusion? Wen you say "feeds me the encryption again," do you mean that it prompts you for the WiFi password?

I guess the Mark V Infusions section does get more attention that the Mark IV Infusions section. I don't own a Mark IV, sorry.

I think you missed the part where I said: "(Don't change the setup/Settings in the infusion after you've done this.)" Either edit the config file via the infusion, or via the editor (e.g. nano), but not both. If you want both ports forwarded, you must choose the editor and ignore the Settings portion of the infusion and its Save button. As I also explained: "The infusion does not parse the autossh command line but rather just assumes that certain args will be in certain positions. When you change the command line, the infusion doesn't keep up." So when you edit the arguments in the config file, they will not look right in the infusion. You can still use all the other parts of the infusion, but if you want to forward both ports, stay away from and ignore the "Settings" section under the "Setup" tab. What I did recommend, was setting both up separately via the infusion, and examining the config file of both. Go ahead and post both versions of the "option ssh" here, redacting your relay host name (or IP). Also post the final version that you think is correct and I'll have a look for you. They should look like: -i /etc/dropbear/id_rsa -N -T -R 1471:localhost:1471 raz0r-relay.org -i /etc/dropbear/id_rsa -N -T -R 2203:localhost:22 raz0r-relay.org -i /etc/dropbear/id_rsa -N -T -R 1471:localhost:1471 -R 2203:localhost:22 raz0r-relay.org So I would expect your final option ssh config line to look like: option ssh '-i /etc/dropbear/id_rsa -N -T -R 1471:localhost:1471 -R 2203:localhost:22 raz0r-relay.org'

Excellent! If you compare the /etc/conf/autossh file for both configurations, you'll easily see what you have to to to get both working at the same time. So if you have it set up for SSH, then you can edit /etc/conf/autossh (with vi or nano) and insert "-R 1471:localhost:1471" just before your VPS host name. (Don't change the setup/Settings in the infusion after you've done this.) Post your final command line here (redact your server) and lets see how it works for you. Darren says they're going to update the infusion soon, so I'm planning to delete my hacked up clone.

I'm sorry you are having so much trouble raz0r. The infusion does not parse the autossh command line but rather just assumes that certain args will be in certain positions. When you change the command line, the infusion doesn't keep up. I copied and modified the infusion to just let me edit the entire command line. (Until then, I simply edited the /etc/config/autossh file with vi.) When you change the command line outside the infusion, the infusion won't look right, but you can do so much more. I used different port numbers in my example to keep them all straight, but SSH on your VPS will probably be on the standard SSH port 22 (not 222), so you could drop the -p 222 (-P 222) everywhere. If you are on your VPS running Firefox (a temporary step I assume), and your pineapple has opened a tunnel to your VPS with a port forward to localhost:1471 on your VPS, then just open that without any proxy in Firefox. If you are on your windows laptop and want to do the same thing, run the shortcut I described (modified for your specific configuration of course) and browse to localhost:1471 there. (If you are on a Linux laptop, you can do the same thing with the SSH client and config file.) Did the Hak5 segment I referenced in another topic help? I thought that would help to understand conceptually what is going on. Actually, the whole SSH series was pretty good as I recall. If you're just trying to get started, why don't you use the infusion as is, doing SSH first, and when you get that working, do just port 1471. After that works separately, put it all together.