Jump to content

0xPHK

Active Members
  • Posts

    19
  • Joined

  • Last visited

Contact Methods

  • Website URL
    http://phr33k.soup.io

Profile Information

  • Gender
    Male
  • Location
    /dev/hal
  • Interests
    IT, hacking, wardriving, making music, mixing, gaming, beer, beer, beer...and soup.io

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

0xPHK's Achievements

Newbie

Newbie (1/14)

  1. @Vile: Thanks for the tip, will try it this weekend... ...as well as playing with spt to see if it can work with a fon 2202 cheers phk
  2. So after 12 days, any news about it?
  3. Ok will try this setting with my w7 box, but how many ppl are using this setting, maybe not so many i think... thanks cheers phk
  4. because the ducky has pwned the autorun function ;)
  5. without deleting the old key associated to ip/hostname in known_hosts it won't let you accept the new key if strict checking is enabled - @sebkinne wil try the new version as soon as i can :) have you played with the simple phishing toolkit on a pineapple yet? thanks for your work. cheers phk
  6. @darren: Which OS's are known to autoconnect, using deauthing or waiting for new victims to come in our bar? Didn't tested any linux dist's yet but xpsp3 and later won't autoconnect to karma - when the known ap was using any sort of encryption. If it wasn't - clients will connect automatically, up to fully patched w7 boxes... so i'm guessing macs could be vulnerable? would be nice to get some informations on this "issue" cheers phk
  7. hope this thread is not dead yet. to your question: maybe both ;) when "debugging" or simply sniffing the packets you will find the needed informations in your dumped packets. give wireshark a try ;) but i can confirm that windows boxes running xpsp3 and later won't autoconnect to karma, all you can do is waiting that someone is dumb enough to manually connect to the karma'd ap.. what i cannot say is which os's will still connect automatically to the rouge ap, but regarding to several hak5 videos with darren, macs are a possibilty... maybe darren could answer to this cheers phk
  8. let's see if we can it run on our lovely pineapples ;) will try this when more time avail. cheers phk
  9. Not sure but i think he means deauthing all clients on that specific AP. Maybe leaving the ClientMAC form empty and only using the BSSID of the attacked AP? Someone here using a 2202 with this firmware?
  10. I recently saw an updated 2.01 firmware on wifipineapple.com Is this a generic atheros based fw like the version on the first post or is this special for a MK3? Tried flashing it to my 2202 but it hangs at redboot and won't boot up. cheers phk
  11. This was the reason of my decision to take a 2202 because of the 32MiB and the USB Port for extra storage, but unfortunately it's not working yet as it should. cheers phk
  12. Well I have tested all the things that came up to my mind, including several IP changes. I was using your 172.16.42.0/24 IP range on my first attempts to get it running. Currently my 2202 is configured @ 192.168.1.1, spoofing lists were modified as well. My major problem is getting Internet connection to work on Lan port and over Wlan, the connection itself comes via Wan port from my local network router. I want to get this running first before doing further investigation why karma is not running too. My intention was to use my 2202 as generic wired mitm device between my router and and the switch that serves all local network clients, to use the snarfing and spoofing capabilities. Maybe I'm thinking into the wrong direction, please correct me if this theoretical scenario won't work at all. Karma is primarily for mobile usage, but as there are wireless clients in my network and my neighbourhood too, so a working Karma would more than just be nice. EDIT: forgot to say private key auth works, dropbear expects authorized_keys in /etc/dropbear Greetings from Germany Phr³³k
  13. Looks like I'm a few steps further into getting things running... My current status: disabled the wan port to "emulate" a mesh/ap51/2100 with just one eth port - internet, spoofing and url snarf works as well as ngrep. only karma won't work as it should be. in the control centers status window association switchtes from enabled to empty, ss well as showing some association info (passing through...) - but but switches after ~10secs to empty and vice versa. the association log shows associated clients even if karma is not enabled ?!? enabling/disabling doesn't seem to make a difference, so i think something is still screwed up. BTW: ngrep causes the 2202 to reboot after aprox. 30-40secs Maybe Darren, Sebastian or someone else could please help troubleshooting my issues? Is there a mk3 user running it stable on a 2202? Usb for logs & paylods and second eth-port would extend the possibilities of the pineapple a lot. One jack in, one jack out - no karma though, but still suitable for mitm using spoof and snarf features. sorry for spamming this thread but can't edit existing posts - dunno why (EDIT 5 posts rule) cheers phk
  14. Well that sounds interesting - sending one to germany is possible? I think ur location is important and so the shipping costs... So please make an offer for one level shifter incl. shipping thanks & cheers phk
×
×
  • Create New...