Jump to content

Skinny

Active Members
  • Content Count

    141
  • Joined

  • Last visited

  • Days Won

    16

Everything posted by Skinny

  1. IT'S FIXED!!! This took a stupid amount of time to figure out for such a simple work around. Before heading down the path outlined below, be absolutely certain there is not some other issue keeping the Crab from connecting to C2. Problem: After initially connecting to C2 and running perfectly over WiFi, subsequent attempts to connect to the same AP using the same Screen Crab prove fruitless and do not work. This is due to wlan0 on the Screencrab not being up when C2 is invoked at boot. Solution: Take the case off of the screen crab. Connect to the screen crab's heade
  2. I changed some things today and it seemed to be working for awhile. Jumping back into this project a few days ago, I screwed up the c2 setup. When I started c2, for hostname I put the hostname of the computer and not the IP address of the computer. If you look at the last post: POST: C2 POST ERROR: java.net.UnknownHostException: Unable to resolve host Chippunk: No address associated with hostname| This got me thinking as to why it would give me that error. After correcting the mistake, it worked great on two different networks. After putting the case back together and restarting
  3. For anyone interested, once connected to the serial port, there is a bash file in /system/bin called crab. It has loads of function in there you can play around with like changing LED colors, wifi functions, and other helpful things. To run the function type: source crab After that just type the name of the function you want to run. To find out the functions just cat out the file. cat /system/bin/crab Looking through logs a little more today, I see the problem that is occurring: C2Run: C2 Thread starting| C2Device: C2 STARTUP SYNC| Util: exec [cat /proc/uptime | busybox aw
  4. @trunner It doesn't seem to make a difference whether it's plugged into battery or into a wall outlet through a transformer, the result is the same. @phrogg After it booted, I just pressed Enter and the prompt popped up. I'm using Windows with Putty. The prompt I get is pasted below after the last few lines of the boot sequence. [ 22.793488] init: avc: denied { set } for property=tmp.exec_ubus scontext=u:r:system_app:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service [ 22.930341] init: avc: denied { set } for property=tmp.exec_ubus scontext=u:r:realtek:s0 tcontext=
  5. No. I was just wondering why you have no other network interfaces showing up. Besides the plunder bug, do you have any other network interface available on the machine?
  6. I am curious if anyone has gotten the Inject Raw Frames feature at the bottom of the PineAP page to work. I have tried several different frame types and attempted to receive the transmission from several different boxes (Mint Linux running on a VM and Pentoo running on my laptop). I have PineAP running with no other options on and a fresh firmware load. I am attempting to send an RTS frame. I copied the hex from Wireshark as it appears below. 000012002e48000000308f09c000e7010000b400a20084fcac5ac95f3c37866ef748 The Inject Raw Frame module then said to take out the radio header in
  7. I've finally got it working! But it's an unusable solution for the field. I opened it up and used the serial connection header to connect to check the wireless interface. I fully connected the device with the micoSD card inserted and plugged through an HDMI connection. The results of looking at the network interfaces were as follows after a full boot: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope
  8. The battle continues. I now have 3 screen crabs that all have the same issue. After running them for the 1st time, they never seem to connect consistently again. I have tried many different avenues to get consistent behavior, but the fact remains that the screen crab does not connect to the AP. I've tried 2 separate APs with similar results. Here is what is happening over the air. The screen crab will send out a Wildcard probe request, the AP will respond, and that's about all that happens. After that, the crab just starts sending out probe requests again. This sequence repeats all t
  9. Just to follow this up, usually this behavior will occur if you have the HDMI input and output switched on the crab.
  10. Are you feeding the signal into a monitor, a TV, or something else?
  11. Meanwhile, I'm still having trouble with the WiFi radio. I now have 3 screen crabs in my possession. I grabbed a brand new one and placed an SD card inside of it with a config file, containing just the WIFI SSID and password, and the device.config file from c2. The screen crab worked great. It connected to the AP and called back to C2 perfectly. After letting it grab a few screenshots over the course of several minutes, I pressed the button and let the light go green. I removed the microSD letting the light go red. I disconnected power from the crab. Next, I placed the microSD back into t
  12. Instead of editing it, erase everything in the file except for the WiFi SSID and Password. The only reason I say this is because of the line under #3 on the screen crab instructional page: https://docs.hak5.org/hc/en-us/articles/360033503594-Configuring-Screen-Crab-for-Cloud-C2 See if it makes a difference. Also, after you change it, let it fully reboot, press the button, let the LED turn green, unplug power, and then boot it again. I've found that sometimes it takes 2 boots before things start working. I'm not sure why.
  13. @zenn1999 Mine also gets very warm. It started out working two days ago when I set it up for another infrastructure, and then stopped working yesterday. I went into the office and grabbed two more. I'll test them Monday to see if they are having the same problem and get back to you.
  14. Here's what I did: The problem is that it doesn't work all the time, but it's worth a try. I'm beginning to think it might be a hardware issue, but I'm not sure. I'm about to get my hands on another unit to see if it behaves differently.
  15. Thanks for the response. I gave it a shot and it looked promising but still failed out at the end. Configuring kmod-libphy. Configuring kmod-mii. Configuring kmod-usb-net. Configuring kmod-usb-net-asix-ax88179. Collected errors: * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-usb-net-asix-ax88179: * kernel (= 4.14.176-1-342af9e4f67b3447c53216ab8e3b12a1) I was trying to install a driver for an Ethernet adapter I was working with. Looks like it was going well for the dependencies but then failed to actually load what I wanted. <<<UPDATE&
  16. Your devices aren't going to auto connect to the Pineapple if you are spoofing an access point that requires WPA2 encryption. WPA2 encryption is a mutual authentication. You devices are looking to exchange encryption information with the Pineapple (the spoofed SSID), but the Pineapple cannot provide that information. So your devices believe that it cannot be the SSID they are accustomed to connect to. The SSID you want to spoof is a public one that someone's phone may have used before. To get this to work for your devices, delete out your current AP/SSID from the programming of both devi
  17. One more added bit of strangeness, if your password has a $ symbol in it, change it to something without the symbol. Once you get it to connect once, you can then use the $ once again. I got everything working by setting up my APs guest network and then connected that network to the regular one. I set an easy password on it. The config.txt file was changed so that the easy password was surrounded in "quotes" as specified above. I restarted the Screen Crab twice and on the second time, it connected. After it connected, I changed the config.txt to my normal SSID where I have a $ symbo
  18. Is the regular AP an open access point or does it require a password?
  19. It's solved! (It is not solved. See below: WIFI_SSID "XxxxXxxX" WIFI_PASS "XxxxxXxxX" Once I did this, everything started working. Well that was an insane amount an effort for such an easy fix. Hope this helps someone down the road.
  20. Looks like the kernel is too old to do any of this now: Collected errors: * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-usb-core: * kernel (= 4.14.176-1-342af9e4f67b3447c53216ab8e3b12a1) * opkg_install_cmd: Cannot install package kmod-usb-core. I saw trying to load a usb ethernet adapter and got the same response. Doesn't seem to be a way in Openwrt to pull backwards compatible drivers from old repos.
  21. Can confirm. Having a $ in the password causes connectivity issues. I was having the same problem. I'm going to go back now and try this solution on the Screen Crab and see if it's suffering from the same problem. Thanks for the help @zenn1999.
  22. New day, new attempts at connection. Tried the following: Confirmed through Wireshark that the only Wireless activity coming from the screen crab are probe requests asking for local APs to respond. Forced my wireless AP to use a well known channel (6) just to ensure the screen crab didn't have a problem with my AP being on channel 3. Also varied the power of the AP and whether or not the SSID was being broadcast. Introduced another AP that functioned as a open access point. Tried to vary the config file in every conceivable way to get it to work. None of the
  23. Can confirm the WiFi/Bluetooth chip inside is getting power (3.3V). For those of you that are interested, it is a WiFi/Bluetooth combo module carrying a RTL8723BS chip. Cool that it has bluetooth as well. Datasheet can be found here: http://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Also, right by the USB C header looks to be a Tx/Rx serial connector. If you are interested in gaining root access, connect up through putty and a serial cable adapter. The baud rate 115200. I was able to get the MAC address for the wifi adapter. The MAC OUI is 74:EE:2A. It resolves to
  24. No answers yet, but I have a few more questions to add. Is the serial number the MAC address? Does the screen crab change it's MAC address each time it boots? If the Screen Crab can't find the C2 server, will it disconnect from WiFi? I am still unable to get a WiFi connection out of the device. I'll update as I glean more information.
×
×
  • Create New...