Jump to content

altjx

Active Members
  • Posts

    18
  • Joined

  • Last visited

Recent Profile Visitors

656 profile views

altjx's Achievements

Newbie

Newbie (1/14)

  1. Haven't read/watched too much about PineAP but decided to turn on the pineapple and upgrade its firmware. One thing I'm noticing though is that, earlier today, I was able to connect to the APs that I have in the SSID Management page. However, I can't now for some reason -- I just get a "Can't connect" error on my laptop and mobile device. I'm guessing there's something small that I'm missing. Any help with this would be greatly appreciated.
  2. Anyone have any ideas about this?
  3. I'm curious to know if there's a way to keep Kismet's cursor selection on top of the screen. If I'm looking for a rogue AP and the signals of several APs are jumping all around, it's hard for me to keep track of the APs with the closest signal. If I have one AP selected and its signal drop, it moves the selection all the way to the bottom, forcing me to have to scroll back up. Any help would be greatly appreciated. Thanks, Alton
  4. Is there a Kismet infusion that I'm unaware of for pineapple? I've seen other people mention kismet in other threads, but I'm not sure if they just installed it manually, or if there was an infusion for it or something. Just wanted to double check here. Didn't wanna screw anything up (if it's highly likely, that is).Thanks Nevermind, found the thread here that provided instructions: https://forums.hak5.org/index.php?/topic/30999-kismet/
  5. Gotcha -- the mac thing makes perfect sense to me. Have the same type of environment in my apartment. Well, my original perception of evil twin was that I could bring up the same SSID, clone the MAC, deauth a client from original AP, and get that client to connect to my AP instead. In my test environment, I was intending to do this without the knowledge of the key (and as if it wasn't in a dictionary, and long/complex). After realizing that I absolutely need that key though, I'm no longer trying to accomplish this under these circumstances since it doesn't appear to be possible.
  6. The problem that I struggled with during my hours of research is that many articles failed to mentioned that Evil Twin requires you to not only have the same ESSID and MAC, but also the same WEP/WPA/WPA2 key that clients use to connect to the legitimate APs. Unless I'm still wrong on this? Isn't this one of the most important steps in creating an evil twin that uses encryption?
  7. Gotcha, so despite his network using a different key, it still connects to yours, and your AP accepts whatever he gives it it sounds like. I'm in the process now of giving this a shot on the pineapple. For some reason, I can't connect to any of the APs I create with airbase-ng. >_<
  8. Very interesting. This is exactly what I'm trying to figure out how to do. I highly doubt it, but you wouldn't happen to have posted a guide on your process doing this would you? What encryption did he use? He DID have to enter in a key right when connected to yours?
  9. Gotcha. Thanks man! Think I have all the answers I needed then. :) Much appreciated.
  10. So to clarify, you can bring up a rogue AP and have others seamlessly connect to it (by deauthing them, etc) while using encryption -- just not using Karma. Correct?
  11. Well, so Karma will not bring up a rogue AP using encryption because of what you stated. What about this other article that referred to bringing up a rogue AP using WEP, deauthing the victim and having the victim connect to his rogue WEP-enabled AP? I guess I'm trying to figure out if this is a limitation with Karma itself, or if this just can't happen in general. Sorry for any confusion.
  12. Thanks. So I'm guessing airbase should work for something like this since Karma doesn't right?
  13. Is this referring to just Karma? Or bringing up a rogue AP in general? Also, in the probe request, the BSSID of the networks the client is reaching for shows, correct?
  14. Still learning more about the pineapple and loving this device so far. I'm also still learning quite a bit about assessing wireless networks too, and I hope this isn't the wrong place to post my question. To my knowledge, Karma on the wifi pineapple doesn't bring up a rogue AP as long as the probe request is for a wireless network that uses encryption, correct? That being said, I ran across an article that referred to bringing up a rogue AP and making someone connect to his instead of their original one. The confusing part for me is that the victim's original wireless AP is encrypted with WEP, so how does bumping him off his force him to connect to their rogue AP, despite the signal being stronger? Is it possible to bring up a rogue AP with encryption (and trick clients into connecting to it), but just not supported by Karma? I thought the reason Karma didn't bring up rogue APs that use encryption was because clients wouldn't connect to it. Here's an exerpt from the article:
  15. I understand that Karma is used to respond to probe requests and connect clients to networks that aren't in range, but I'm a little confused with the "Karma Configuration" tab. What is this tab used for? I can't really find much online pertaining to this tab, so I've come here for some clarification. SSID Configuration = guessing this means advertise this network instead of waiting for someone to probe for it? Client Blacklisting = guessing this means don't accept clients that have this mac address? SSID Black / White Listing = I'm not 100% on this, but I'm guessing black means to only accept probes for this network, whereas white is the opposite? How do I know which SSIDs are added to the list? It doesn't display it anywhere. Any help with the clarification would be greatly appreciated.
×
×
  • Create New...