Jump to content

fanbase

Active Members
  • Posts

    19
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    worldwide

Recent Profile Visitors

707 profile views

fanbase's Achievements

Newbie

Newbie (1/14)

  1. It can be both, simultaneously. In fact, this is one of the configurations that the jasagerPwn script sets up for you, with impressive effects.
  2. thesugarat, if I recall correctly your solution entails mac address spoofing. Can you tell me the preferred method for mac spoofing on the pineapple? I vaguely recall in a prior posting that someone had offered one method, only to be told by sebkinne that perhaps their method wasn't the best. In any case, I remember neither method; though I know mac address spoofing is very basic, I would greatly appreciate a quick walk-through of the commands to be used.
  3. I'm very interested. I've tried setting up a OpenVPN connection between my pineapple and VPS but haven't succeeded. This has tremendous potential for an extended MITM attack through the VPS with, e.g., metasploit.
  4. It crashes and reboots when I use the SSLstrip infusion, and that alone (besides Karma). I'll let it run a few hours, check in later, and find that the sslstrip log has restarted with something like the name "log_70." The syslog confirms that an uncommanded reboot occurred at some point since I last checked in on the pineapple. (Incidentally, the sslstrip logs themselves show quite a few errors like "cannot concatenate 'str' and 'NoneType' objects" and "'twisted.internet.error.DNSLookupError'"— not sure if that is related.) It also seems to crash and reboot rather more promptly when I try to combine sslstrip with anything else: nmap, Trap Cookies, urlsnarf... I'll be in Hong Kong next week; I'll look into buying a serial TTL cable while I'm there. Sounds like a project. In the near term, any insight on what might be causing these uncommanded reboots — and how to avoid them?
  5. My pineapple crashes and reboots a lot. I'd like to figure out why. Common sense tells me to begin by sifting through something like a system log that might detail the events that led to each crash. The trouble is, when I look at the log available through the web interface after a crash, the first entry only begins 0:38 seconds after the reboot. No events are listed prior to it: Jan 1 01:00:38 Pineapple kern.info kernel: [ 30.720000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) This makes it difficult to determine what precipitated the uncommanded reboot. How and where do I find log files that would detail events that are occurring prior to the uncommanded reboots? If the answer involves the Log Check infusion or the "custom tail" option, perhaps someone could steer me toward resources that might help in understanding how to use it? I really don't know where to begin.
  6. As it happens, I had a chance to try the work-around this morning -- and remotely from another city, at that! I SSH'ed into the Pineapple through my VPS, then issued the following command: /etc/init.d/uhttpd restart The web interface, which had previously been hung up and was not loading, popped up instantly when I hit refresh in the browser. Does this solve anyone else's problem?
  7. I tested it again by pulling the plug. What was already in the log stayed saved in the log. A new log, titled "Log_70" -- because the pineapple believes it is January 1970 in the moments immediately after it powers up again (and after auto sslstrip has started) -- picks up where the previous log left off before the crash. So, yes, thesugarat, the error with the logs is partly mine own: Each time I backed up sslstrip logs via scp after repeated crashes/unresponsive webUI/plug-pulling cycles, I overwrote my previous log, which of course was also named "Log_70". The essential problem, however (at least for me and, as I understand it, the OP), is that the web interface periodically crashes -- by which I mean it refuses to load or respond -- even though the pineapple remains responsive through SSH. Some further googling turned up this suggestion: Look for these two proccesses: root@Pineapple:~# ps -ef | grep http 1749 root 1136 S /usr/sbin/uhttpd -f -h /www -r Pineapple -x /cgi-bin 1755 root 1160 S /usr/sbin/uhttpd -f -h /pineapple -r Pineapple -c /e If not, try to restart them. /etc/init.d/httpd script You can also use following command: # /etc/init.d/httpd restart # /etc/init.d/httpd start # /etc/init.d/httpd sto I have no idea if that works but it won't be long (at this rate) before I give a shot. Hope you folks try, as well and report back
  8. Cell phone jamming is actually legal in Indonesia, where I live. It's commonly used in mosques, near the entrances of upscale hotels and clubs (rcIED risk), prisons, and, ironically, from what I surmise (based on incidental, non-technical observation) the US Embassy. Not only are jammers incredibly common, so are malicious femtocells and mobile botnets. Unregulated. It's an RF wild west. While jamming can prevent communication in emergencies, it can also save lives. I can also attest that these devices are massively disruptive beyond their intended area.
  9. I'm logging to the SD card. It's a class 10.
  10. I also have this problem. After running sslstrip for an hour or so, return and attempt to open or refresh the web to check its progress. It doesn't load. I can ssh into the pineapple, no problem. What really frustrates me, though, is that when I invariably have to unplug the pineapple (or ssh in and kill -9 the PID for sslstrip), I lose everything the log that had been building! Good stuff -- poof! gone, vanished. It's happened about 6-8 times today alone. And I knew I had some good stuff in those logs, too... The problem predates the latest release, but in my subjective experience, seems to have been exacerbated by it? Maybe just coincidence. I'm willing to work with anyone who wants to test/work this problem.
  11. I haven't tried an ubuntu VM setup. With all due respect to Chris, I thought his tutorial was a little idiosyncratic, since (as I understand it) the setup it yields doesn't work if your network has a firewall that you can't control. An Amazon setup takes little more effort, and (for me at least) removed some of the confusion that a VM introduces. It also allows you to administer the pineapple from any network, anywhere, any time. I did have to watch episode 1112 about 20 times, though. Good luck!
  12. What does it mean when I see this in the sslstrip log?:
  13. Cheeto, I did a writeup last week about configuring a relay server for free on Amazon's EC2 service. I hope it helps you when your pineapple arrives. Configuring a relay for the first time, in my experience, was both easier and harder than others have made it out to be. There's no GUI for this kind of thing. Once you do have your pineapple, you will almost certainly be rolling up your sleeves and mucking around in Terminal more than you expect. I am still learning, but it seems that not all the infusions' GUIs give you the predictability and full range of features that the same program, executed from Terminal, would.
  14. 0.08 BTC reward for whomever can set this up for me and explain how they did it. I'll gladly turn over my keys temporarily.
  15. Thanks for your reply, GuardMoony, but your answer seems at odds with the OpenVPN website: Really? The OpenVPN website seems pretty emphatic that you can't mix tap and tun, as do the comments in the config files: https://forums.openvpn.net/topic14913.html http://openvpn.net/index.php/open-source/faq/community-software-general/305-what-is-the-difference-between-a-tun-device-and-a-tap-device.html Is there something I'm not getting?
×
×
  • Create New...