Jump to content

Smart-Aswood

Active Members
  • Posts

    47
  • Joined

  • Last visited

Posts posted by Smart-Aswood

  1. I installed female headers of a size that will allow yet more shields (should they be called Pineapple Slices?) to be stacked.

    The holes do line up with a proto-board made by Seeed Studio (so also the Uno, etc). So stacking Slices (shields, capes, hats, whatever) should work easily. I'm going to pick up a breadboard shield.

    One question. The footprint matches the Uno, except for SCL and SDA. Where are those landed? They're landed, right?

    I've got a couple of these things --> https://www.tindie.com/products/Earth_People_Technology/easy-programmable-logic-for-the-uno-with-unoprologic-cpld-shield/

    CPLD could be interesting. Those are 3.3V native (5V tolerant) btw.

  2. So I bought the SDK board and installed it. Even a 3.3V Bluetooth module. Guess I could write an Arduino program to monitor the pins and tell me what they're doing. I noticed at the New Year's bbq, Darren had one hooked up.

    How about giving us a minimal pin mapping. Even if it's presently empty. I'd be nominally satisfied to learn that none of those pins are talking. If that's accurate information, I can dig it. Means I have to wait.

  3. I have a Nov 5510L with Verizon that works solid as a rock tethered. Right out of the box? No, and not with the MK5 web setup. Darren posted some CL stuff awhile back - simple stuff - that makes it work hotplugged. One thing I can tell you is that it's worth the trouble. It's solid, stable, and awakens an Easter egg of sorts with regard to the Verizon 5510L. Here's what that is:

    I get consistently and significantly faster speeds as a MK5 wireless client than I get using the hotspot direct-wireless. I think that has to do with the 5510L bypassing a lot of internal buggy wireless hotspot crap when tethered. Suppose I could tether it to my laptop and compare speeds, but what fun is that?

    It does provide clients connected to the MK5 seamless and stable internet. So much so that I have to portion its use or the clients will use up my 10 monthly gig quickly if I screw up and leave the MK5 tethered and on for a couple of days.

    Had people doing Windows updates on my dime. I don't blame them. My MK5 was a lot faster than the hotel Wifi.

  4. Not sure the Odroid-C1 is Arduino compatible. The Nano is, or they say it is. Not certain I like their video response to some customer problems on Arduino compatibility.

    Language barrier aside, the dude says customers have been complaining about getting the Arduino stuff to work, then runs the simplest Arduino script (blink) and is like, see? It works! Stupid customers!

    Obviously he doesn't address using Arduino shields and other aspects of compatibility.

    I'm not complaining. At that price, I'll find a use for it regardless.

  5. Also, if you don't want to go through the trouble of Karma and PineAP, a honey pot AP still works and always will. All that takes is a good name. I've used "Free Fast and Private WiFi" and that brings in more connections than Karma and PineAP. People just don't use their noggins. "McDonald's #2" and "Starbucks Open" are a bit of a risk. Unnecessary too.

    "Free WiFi" works, and you aren't using anyone else's name.

  6. Well, Karma still works on a lot of devices, and PineAP seems like it's pulling in connections. evilportal - nodogsplash with dnsspoof can yield the same results as sslstrip and that's something they can never *fix* because 90-something percent of people believe something that looks like Facebook IS Facebook. Same with any other login page. For pen testing, security audits it doesn't matter how you penetrate as long as you do. (that's besides it being fun)

    Takes some practice and a little coding to use those methods, but once you've built your evil versions of those website front ends and the scripts to utilize them, you're going to pull in credentials often enough to make it worth the trouble.

    Takes some practice, but learning stuff is what hacking is supposed to be about.

    All this is, of course, just my opinion. Look for stuff they can't secure. Like human nature.

  7. Those Nanos is are a great find. I couldn't resist and ordered one. I'm developing a robotics thing and I'm trying, so far, a Netduino, a Beaglebone Black, and now a PcDuino3 Nano.

    The Netduino has been a disappointment because of the C# overhead. Just too slow for things like following a gyro and accelerometer.

  8. Most websites have changed their implementation of SSL. sslstrip no longer works on them. And they changed that implementation in a way that there's no simple fixes for sslstrip to make it work. Good for them. That was something sslstrip did well - it forced sites like Twitter and Facebook and Amazon and eBay, as well as banking sites to fix their security.

    There are obviously people working on breaking SSL again. About the time they break it and the sites fix it again, us non-professionals will get access to whatever replaces sslstrip. By the time we get it, it won't work either.

    There's things they can't fix, which is why things like the Rubber Ducky scare the crap out of them.

  9. I noticed hints of this as well, but just figured I was doing something wrong (historically, a safe and time-saving assumption). My hotel internet access uses the same 172.16.42.xxx addressing as the default on the MK5 and this causes any number of problems. So I figured I'd try putting the MK5's AP on a 10.0.0.xxx setup. I tried 192.168.xxx.xxx as well.

    Got all balled up. I'll try it again after coffee some morning. I solve a lot of problems that way.

  10. I think a big part of the problem with client mode is what you're a client of. It's adding an additional wireless AP into the mix. Sometimes the AP you're trying to use is poorly managed from the get go. In addition, an AP at McDonald's or Starbucks is crowded. So you're trying to grab this inconsistent resource and share it with others. Might not work real well.

    I'm not saying that's the cause of all Client Mode's poroblems. Bound to be part of it though.

  11. Main problem with the 8188eu is that the Linux driver doesn't like it much, in any capacity. That's what I figure anyway. I use it to grab internet onto my Win7 laptop and then share that with the MK5 via ethernet. Besides not being able to deploy it in a flower pot or something, you have great functionality. Solid, fast, and you can monitor real-time with Wireshark. Just the live Wireshark part - I don't think I can give that up now. Very controllable and stable. Lots of data.

  12. Yeah, it's the client mode stuff I can't seem to keep running for long. When the MK5 gets its signal via ethernet or a 4G modem, there is no perceptable speed difference with the MK5 or without it. With my MiFi 5510l connected to the MK5 via USB I've actually gotten 19 both ways. It was time of the night when Verizon's network wasn't busy.

    I quit beating myself and the MK5 up over client mode. I don't need it. My favorite is actually sharing internet from a Win7 laptop to the MK5 via ethernet - then monitor that connection with Wireshark. Do that and you're getting full value from the MK5. Any information that's gettable, you'll get. Then when you're doing a managed PineAP attack, you're not using any wifi bandwidth in order to perform the management. Both radios are 100% dedicated to the customer. Err victim.

  13. Not for use with Linux in terms of monitor mode or promiscuous mode - or not any that work. I'm using one right now on my Windows 7 laptop just for internet access and in that role it's a great long range "n" adapter. Fantastic. Wireshark hates it's guts though. So I use the 8188 to pull in internet, which I then share over ethernet to the MK5 and monitor that ethernet connection with Wireshark.

    In that role it works excellently. It's a much much better adapter than the internal one on the laptop.

  14. The deauth problem seems tricky to me. Doesn't occur in some situations. I'd worry about a fix that breaks other stuff. I've seen it in Client Mode, but haven't noticed it sharing my laptop internet or tethered to a 4g modem. It may have been there, but it hasn't dropped any clients on me.

  15. MK5 has been running for 14 hours powering the MiFi 5510l and running everything in the PineAP window as well as sslstrip, using the stock power supply. Completely stable. Just did a speed test and got 11 down and 8 up, but the upload had an initial two-second burst of 22. This is the sort of functionality I was looking for. Just made a trip to the Hak5 store for more gear.

    I no longer care about Client Mode, at all. It's become irrelevant for me. I know I can run the MK5 via Ethernet on my laptop running Kali OR tethered to the 5510l. Heck of a useful tool now. Thank you, Darren.

  16. Okay, this page is the basic bump chart. I removed information to protect... somebody... probably me. Each bump is labeled with the ssid.

    G1gwSnI.jpg

    Here's the main page when you're a client of the MK5 (below). Note you can verify your MK5 has internet access with this page with the button in the upper right.

    VNmBMcq.jpg

    Next the the Channels page, before you start Karma and PineAP

    b65ExIV.jpg

    This next one is cool. This is the Channels page AFTER you start Karma and PineAP. Notice anything about all these channels?

    alsDhuR.jpg

    So if YOU aren't doing that at the time, someone certainly is. I could scroll down for about 2 more pages and it was all the same thing, including one that said "FBI Reconnaissance Van #24" ---> It was about -9F outside so there was just no way the actual FBI would be out there.

    If you have helpful Wifi apps (helpful in setting up or diagnosing Pineapple deployment, lets hear about them.

×
×
  • Create New...