Jump to content

Johnnie

Active Members
  • Posts

    25
  • Joined

  • Last visited

Posts posted by Johnnie

  1. Hi,

    I'm curious about the current status of this project. Is there a way to get the source code of the experiment8021104 program so we can play around with ideas? If not are there similar alternatives out there? I'd like to develop something for it but would rather use such a starting point instead of starting from scratch.

    Thanks.

  2. If you connect to a honeypotted AP it depends on what traffic you do over it. If you don't pay attention and login to facebook/gmail/etc that's had SSL stripped or ignore any SSL warnings, you're boned.

    There are also apps that use SSL but don't verify SSL certificates. If you use one of these apps and there's someone evil in between you, you can still get boned..

    Sure, but my scenario was not using the network deliberately. I'm already familiar with the risks of that. But can't control what and how every app is sending automatically in the background so that may be a vulnerability I guess.

  3. I have a ZTE MF112 3G dongle. When I connect it to the pineapple (via a battery-powered USB hub), I can see it is listed under "USB Connections" in 3G page as "ZTE WCDMA Technologies MSM MF110/MF627/MF636"

    But it doesn't appear as a "USB 3G Modem" in the Interfaces section on the Status. Should it be there to indicate it's supported?

    The output of the connection script is :

    15:29:22 Pineapple user.notice root: 3G: Connection Script here, searching for modems
    15:25:01 Pineapple user.notice root: CLEANUP: memory looking good
    15:25:01 Pineapple user.notice root: CLEANUP: Karma log looking good
    15:25:01 Pineapple user.notice root: CLEANUP: Clean-up Script Executed
    15:25:01 Pineapple user.notice root: 3G: Keep-Alive Script Executed
    15:25:01 Pineapple user.notice root: 3G: Interface 3g-wan2 seems down. Attempting 3g connect script again

    Also is there a page / wiki or some sort of list of supported 3G modems?

    Thanks.

  4. @gurdz

    Thanks for sharing the specs.

    I mainly decided not to order the pineapple from Hak5 because I was worried that I would have similar issues with the customs. May I ask in which country did you have these issues? If you don't want to tell that's understandable of course.

  5. That sounds scary. I use an Android and then it is entirely possible to get hacked even without using the network.

    I recently sticked an NFC tag on my door. Whenever I'm going out I'm touching my machine which launches a program to disable WiFi completely. I figured I don't need Wifi running when I'm out anyway. Not the ultimate solution obviously, but hope it helps a little.

    Thanks for the info.

  6. Hi,

    Normally I never use open networks and this gave me some (false?) sense of security against hotspot honeypots. But as I'm playing around with Wifi Pineapple these days I'm connecting my phone to my own honeypot it made me thinking: Say I forgot to clear those networks and went outside and my phone connected to another honeypot. What would be the implications of this? I'm not going to use the network obviously but can the attacker run some sort of attack even in this case?

    Just trying to understand all aspects of risks involved with this tool.

    Thanks.

  7. The AP does not "authenticate" that it is a legitimate AP to the client. It "authenticates" itself by confirming that it knows the correct pre-shared key which is verified by successfully completing the 4-way handshake. So if I sit in your parking lot and setup an AP advertising your SSID and I configure it to use the same PSK that your legit APs are using, then your clients will still successfully associate to my rogue AP. That is a misleading use of the term authenticate in that article.

    I see. So the attack is technically possible only if you know the pre-shared key but not supported currently.

    I still find it a low risk though. At least for myself, considering the networks I connect to. Maybe it could be viable option for a targeted attack.

  8. Nice wikipedia article here: http://en.wikipedia.org/wiki/IEEE_802.11i-2004#The_Four-Way_Handshake

    TBH I don't fully understand all the technical details of the process but I think this phrase is very clear "the access point (AP) still needs to authenticate itself to the client station (STA)"

    It's a bit of a relief to know that actually. As long as one can stay away from unprotected networks, they can be immune to karma attack then.

  9. Hi,


    I was just looking for the old versions to flash. In downloads page, versions from 1.0.0 to 2.7.0 seem like they were released on 12-09-2012 (that is dd-mm-yyyy as it should be :-))


    In changelog page they (1.0.0 to 2.7.0) all seem to be released on 11-11-2012.


    Not a big deal but is there a way to find out the release date of a specific version more accurately?


    Thanks.
  10. Hi Darren,

    First of all thanks for the great tool and all the information about it. I had been hearing it for a long time in your shows but only last week had the chance to try it. I think it's a great way of learning a ton about wireless security so I'm planning to dig deeper. I wanted to build it on my own to get more involved and bought a Hornet board and a AP121U. Followed the instructions and flashed the Hornet with the latest firmware. (Also thanks for the openness of everything that made it possible)

    As I am a complete noob to this I didn't know what to expect and now I understand all those probe requests should have been responded and clients should have associated with the network they were probing for (hence the name yes-man)

    There are talks about a bug in the driver. What I'm confused about is: Is this passiveness you mentioned caused by this bug or implementation changes from the manufacturers or both?

    Also, I was wondering if it would be of any help if I flashed my devices to an older firmware and compared the outcome? If it helps to identify when the bug was first introduced please tell me which version do you need to be tested.

    Thanks again for everything (to your team as well of course).

  11. I had a similar problem and had to reboot pineapple to switch from laptop connection sharing to S3 tethering. Now I can see the public internet IP on pineapple UI and I can verify the internet connectivity on the phone. But when I try to connect using another laptop to test it cannot connect to internet. It is assigned an IP address and router shows as 172.16.42.1. I tried it with an iPad too to no avail. Any ideas what the problem might be?

    Thanks.

  12. Thanks guys.

    @Mr-Protocol: Yes, I was referring to your video. Since I was stuck at the beginning I didn't watch all of it and thought they were taken from different machines. Sorry about the newbie error

    @khaotic57: Thank you (and Tyler) for the video.

    I downloaded the drivers from here: http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

    and now all seems to be fine.

    Now I can play around with it, let's see how it's going to wind up.

    Thanks again.

  13. Hi,

    First of all thanks for all the useful information on this forum.

    I recently bought a Hornet-UB board and I am trying to flash it using the instructions here: http://wifipineapple.com/?flashing

    I don't have a Alfa console board, but I bought this

    I'm a bit confused about the environment used in the tutorial video. It shows device manager settings so it's plugged in to a Windows machine, right? But then it switches to Backtrack and connects to serial port via Putty. So is it a different machine, a VM running under the host machine?

    Also when I plug in using the USB UART adapter (I bought this one: http://www.amazon.co.uk/gp/product/B00AFRXKFU/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1

    I hope it is correct) it appears under Other devices as "CP2102 USB to UART Bridge Controller". Do I need to install a driver or something so that I can access under ports section?

    I hope a nudge in the right direction would help a great deal.

    Thanks.

×
×
  • Create New...