Jump to content

crashie

Active Members
  • Posts

    48
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by crashie

  1. Hi Dez, Actually I wouldn't say WPA/WPA2 passwords are hard to crack. It all depends on the set password of course. I've cracked WPA2 passwords in 2 seconds on my server with GPU's. Just because the password was made up with a word and numbers. Of course I then used my own wordlist together with some own rules in cudahashcat. So sometimes it's not that hard, but sometimes you won't crack the password at all. Completely depends on the complexity of the set password. Soon enough my server will do 1mH/s so crunching through a big wordlist together with some good rules won't take much time. But still all it comes down to is if I'm smarter than the one who set the password :P When cracking clients wireless networks I create own wordlists based on data about that client, like scraping words from their website, different languages etc. /crashie
  2. I will arrange a "manual" that I put on the github later today. With the instructions. Not that complicated though. The first index.html file goes to the /pineapple folder. The image files goes to the /pineapple/img folder. The .css files goes to the /pineapple/css folder. The module.html file in the module/Dashboard folder in the zip goes to the /pineapple/modules/dashboard folder. You have to replace the old files with the new. And make sure you are on firmware 1.0.5. /crashie
  3. For anyone who want's my "NSA-style" themes you'll find them here now: https://github.com/crashieSWE/nanothemes Will upload any future themes there. Until we have a "theme module" in the NANO :P
  4. That's not an issue with the module but with the Nano itself. Sebkinne is working on a solution. Since if you try to download a file let's say 40MB through SFTP or SSH the same error occurs. But seb will solve it soon enough.
  5. I already have them :P Just not in this picture :P
  6. I've actually played around with it and yeah.. I might actually go for it :P My current changes :P
  7. You could always mod the CSS on your own :)
  8. Yeah, interesting at least :) Looking forward to have it fixed so I can download those big pcaps without a hassle :) I have faith in you.
  9. The issue is taken care of by sebkinne. He's looking into it since he could also reproduce the same issue. Probably solved soon enough.
  10. 1. Samsung S4 2. 5.0.1 3. Stock 4. No, not working on the S4 for some reason.. 5. Yes 6. Yes Other than that I'm running it with my Macbook Air and I also have a Alfa AWUS036NEH attached to it from time to time :P See my pic :)
  11. When you are in the webinterface go to Advanced, press the arrow down beside "USB" and choose Format SD Card. /crashie
  12. To add to the issue, I've now tried four different microSD-cards. And the same issue with all of them. Are all SD-cards faulty or is it the NANO who's acting up? Can write to the SD on the NANO but the problem starts when reading a large file (downloading) from it through either the webinterface or sftp etc.
  13. Nice ideas but why not use PineAP and allow association? That will show them what really can be done and that they don't actively have to "choose" the right network SSID :P And that it can happen to them anywhere.. At the office premises, at the restaurant, at the pub, at the train etc. They should always pay attention to networks they are connecting to and don't allow their devices to automatically connect to known wireless networks etc.. Just my 2 cents. /crashie
  14. Works as a charm over here! I am currently having my S4 connected to a Wi-Fi in the area and the USB-cable attached to the NANO and I've enabled USB-Tethering in the S4. Clients connected to the Nano gets served with the Internet. Now I only hope to get the issue with my SD-card solved so that I can get it up and running as it should. But if anyone who owns a S4 and have issues with USB-Tethering let me know and I'll help out. I can add that I am running Android 5.0.1 on the S4. /crashie
  15. Yes, I am running my NANO with a S4. And with USB-tethering enabled. The WiFi Pineapple android app doesn't work (tells me to configure tethering all the time) but still USB-tethering runs and clients get served :P
  16. Some more data: Wed Feb 17 21:15:42 2016 kern.info kernel: [ 118.760000] br-lan: port 3(wlan0-1) entered disabled state Wed Feb 17 21:15:42 2016 kern.info kernel: [ 118.760000] device wlan0-1 left promiscuous mode Wed Feb 17 21:15:42 2016 kern.info kernel: [ 118.770000] br-lan: port 3(wlan0-1) entered disabled state Wed Feb 17 21:15:42 2016 daemon.notice netifd: Network device 'wlan0-1' link is down Wed Feb 17 21:15:42 2016 kern.info kernel: [ 118.910000] device wlan0 left promiscuous mode Wed Feb 17 21:15:42 2016 kern.info kernel: [ 118.910000] br-lan: port 2(wlan0) entered disabled state Wed Feb 17 21:15:42 2016 daemon.notice netifd: Network device 'wlan0' link is down Wed Feb 17 21:15:42 2016 kern.err kernel: [ 119.570000] Buffer I/O error on dev sda1, logical block 2655233, lost sync page write Wed Feb 17 21:15:42 2016 kern.err kernel: [ 119.570000] JBD2: Error -5 detected when updating journal superblock for sda1-8. Wed Feb 17 21:15:42 2016 kern.err kernel: [ 119.580000] Aborting journal on device sda1-8. Wed Feb 17 21:15:42 2016 kern.err kernel: [ 119.580000] Buffer I/O error on dev sda1, logical block 2655233, lost sync page write Wed Feb 17 21:15:42 2016 kern.err kernel: [ 119.590000] JBD2: Error -5 detected when updating journal superblock for sda1-8. Wed Feb 17 21:15:42 2016 kern.err kernel: [ 119.620000] EXT4-fs (sdb1): couldn't mount as ext3 due to feature incompatibilities Wed Feb 17 21:15:43 2016 kern.err kernel: [ 119.650000] EXT4-fs (sdb1): couldn't mount as ext2 due to feature incompatibilities Wed Feb 17 21:15:43 2016 daemon.notice netifd: radio1 (2255): Interface 0 setup failed: BRIDGE_NOT_ALLOWED Wed Feb 17 21:15:43 2016 daemon.notice netifd: Network device 'eth0' link is down Wed Feb 17 21:15:43 2016 kern.info kernel: [ 119.970000] eth0: link down Wed Feb 17 21:15:43 2016 kern.info kernel: [ 119.970000] br-lan: port 1(eth0) entered disabled state Wed Feb 17 21:15:43 2016 kern.info kernel: [ 120.180000] EXT4-fs (sdb1): recovery complete Wed Feb 17 21:15:43 2016 kern.info kernel: [ 120.180000] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) Wed Feb 17 21:15:43 2016 kern.info kernel: [ 120.360000] usb 1-1.2: USB disconnect, device number 5 Wed Feb 17 21:15:43 2016 kern.err kernel: [ 120.370000] scsi 1:0:0:0: rejecting I/O to offline device Wed Feb 17 21:15:43 2016 kern.info kernel: [ 120.370000] scsi 1:0:0:0: [sdb] killing request Wed Feb 17 21:15:43 2016 kern.info kernel: [ 120.370000] scsi 1:0:0:0: [sdb] Wed Feb 17 21:15:43 2016 kern.warn kernel: [ 120.380000] Result: hostbyte=0x01 driverbyte=0x00 Wed Feb 17 21:15:43 2016 kern.info kernel: [ 120.380000] scsi 1:0:0:0: [sdb] CDB: Wed Feb 17 21:15:43 2016 kern.warn kernel: [ 120.390000] cdb[0]=0x28: 28 00 00 00 00 b7 00 00 08 00 Wed Feb 17 21:15:43 2016 kern.err kernel: [ 120.390000] blk_update_request: I/O error, dev sdb, sector 183 Wed Feb 17 21:15:43 2016 kern.err kernel: [ 120.400000] Buffer I/O error on dev sdb2, logical block 60, async page read Wed Feb 17 21:15:43 2016 kern.err kernel: [ 120.400000] Buffer I/O error on dev sdb2, logical block 61, async page read Wed Feb 17 21:15:43 2016 kern.err kernel: [ 120.410000] Buffer I/O error on dev sdb2, logical block 62, async page read Wed Feb 17 21:15:43 2016 kern.err kernel: [ 120.420000] Buffer I/O error on dev sdb2, logical block 63, async page read Wed Feb 17 21:15:44 2016 kern.info kernel: [ 120.970000] eth0: link up (100Mbps/Full duplex) Wed Feb 17 21:15:44 2016 kern.info kernel: [ 120.970000] br-lan: port 1(eth0) entered forwarding state
  17. Ok, next update on the issue.. It seems to relate to the USB (or microSD) interface.. maybe I've got a defect NANO or SD (tried another SD-card but that doesn't mount)?.. Been trying everything but as soon as I initiate a transfer of a file that is large enough the interface goes down and then back up in 3-5 seconds and using sftp I can resume the download but after 10-40 seconds (differs from time to time) then it disconnects again and reconnects which interrupts the transfer.. So to be able to transfer a pcap of 166Mb I have to resume the download 30-50 times before I've got the whole pcap.. I've recorded a video of the screen of what's going on when it happens.. but below is some data from dmesg: [ 459.450000] usb 1-1.2: USB disconnect, device number 6 [ 459.460000] scsi 2:0:0:0: rejecting I/O to offline device [ 459.460000] scsi 2:0:0:0: [sdc] killing request [ 459.470000] scsi 2:0:0:0: [sdc] [ 459.470000] Result: hostbyte=0x01 driverbyte=0x00 [ 459.470000] scsi 2:0:0:0: [sdc] CDB: [ 459.480000] cdb[0]=0x28: 28 00 00 00 00 5f 00 00 40 00 [ 459.480000] blk_update_request: I/O error, dev sdc, sector 95 [ 459.490000] Buffer I/O error on dev sdc2, logical block 28, async page read [ 459.490000] Buffer I/O error on dev sdc2, logical block 29, async page read [ 459.500000] Buffer I/O error on dev sdc2, logical block 30, async page read [ 459.510000] Buffer I/O error on dev sdc2, logical block 31, async page read [ 460.370000] eth0: link down [ 460.370000] br-lan: port 1(eth0) entered disabled state [ 461.480000] device wlan0 entered promiscuous mode [ 461.480000] br-lan: port 2(wlan0) entered forwarding state [ 461.490000] br-lan: port 2(wlan0) entered forwarding state [ 461.610000] device wlan0-1 entered promiscuous mode [ 461.620000] br-lan: port 3(wlan0-1) entered forwarding state [ 461.620000] br-lan: port 3(wlan0-1) entered forwarding state [ 462.600000] usb 1-1.2: new high-speed USB device number 7 using ehci-platform [ 462.610000] br-lan: port 3(wlan0-1) entered disabled state [ 462.740000] usb-storage 1-1.2:1.0: USB Mass Storage device detected [ 462.780000] scsi host3: usb-storage 1-1.2:1.0 [ 463.340000] br-lan: port 3(wlan0-1) entered forwarding state [ 463.340000] br-lan: port 3(wlan0-1) entered forwarding state [ 463.490000] br-lan: port 2(wlan0) entered forwarding state [ 463.610000] eth0: link up (100Mbps/Full duplex) [ 463.610000] br-lan: port 1(eth0) entered forwarding state [ 463.620000] br-lan: port 1(eth0) entered forwarding state [ 463.780000] scsi 3:0:0:0: Direct-Access Generic STORAGE DEVICE 0933 PQ: 0 ANSI: 6 [ 463.790000] sd 3:0:0:0: Attached scsi generic sg0 type 0 [ 464.060000] sd 3:0:0:0: [sdc] 62521344 512-byte logical blocks: (32.0 GB/29.8 GiB) [ 464.070000] sd 3:0:0:0: [sdc] Write Protect is off [ 464.070000] sd 3:0:0:0: [sdc] Mode Sense: 21 00 00 00 [ 464.070000] sd 3:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 464.120000] sdc: sdc1 sdc2 [ 464.130000] sd 3:0:0:0: [sdc] Attached SCSI removable disk [ 465.340000] br-lan: port 3(wlan0-1) entered forwarding state [ 465.620000] br-lan: port 1(eth0) entered forwarding state [ 466.340000] Buffer I/O error on dev sdb1, logical block 3702784, lost sync page write [ 466.350000] JBD2: Error -5 detected when updating journal superblock for sdb1-8. [ 466.350000] Aborting journal on device sdb1-8. [ 466.360000] Buffer I/O error on dev sdb1, logical block 3702784, lost sync page write [ 466.370000] JBD2: Error -5 detected when updating journal superblock for sdb1-8. [ 466.420000] EXT4-fs (sdc1): couldn't mount as ext3 due to feature incompatibilities [ 466.460000] EXT4-fs (sdc1): couldn't mount as ext2 due to feature incompatibilities [ 466.600000] EXT4-fs (sdc1): recovery complete [ 466.610000] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null) [ 466.980000] Adding 1004024k swap on /dev/sdcard/sd2. Priority:-3 extents:1 across:1004024k I've also now tried with another SD-card (2GB) but still have the same issue. I can upload a 160MB pcap to the SD storage through SFTP with no errors. But as soon as I try to download the same file it disconnects and reconnects. With my other SD-card I got this error also if it can help: [ 471.720000] usb 1-1.2: USB disconnect, device number 11 [ 471.720000] scsi 7:0:0:0: rejecting I/O to offline device [ 471.720000] scsi 7:0:0:0: [sdb] killing request [ 471.730000] scsi 7:0:0:0: [sdb] [ 471.740000] Result: hostbyte=0x01 driverbyte=0x00 [ 471.740000] scsi 7:0:0:0: [sdb] CDB: [ 471.740000] cdb[0]=0x28: 28 00 00 00 00 00 00 00 20 00 [ 471.750000] blk_update_request: I/O error, dev sdb, sector 0 [ 471.760000] Buffer I/O error on dev sdb, logical block 0, async page read /crashie
  18. I've provided detailed logs in my other thread: https://forums.hak5.org/index.php?/topic/37655-error-when-downloading-pcaps-from-the-nano/
  19. I can add myself to having issues with the SD-card. It's mounted and all but when clients get connected and starts generating traffic and I've enabled tcpdump the network interface starts to disconnect and reconnect. And in the dmesg I can see this: [ 861.840000] device br-lan entered promiscuous mode [ 948.240000] Write-error on swap-device (8:0:48) [ 948.250000] Write-error on swap-device (8:0:56) [ 948.260000] Write-error on swap-device (8:0:64) [ 948.270000] Write-error on swap-device (8:0:72) [ 948.270000] Write-error on swap-device (8:0:80) [ 948.280000] Write-error on swap-device (8:0:88) [ 948.280000] Write-error on swap-device (8:0:96) [ 948.310000] Write-error on swap-device (8:0:104) [ 948.310000] Write-error on swap-device (8:0:112) [ 948.320000] Write-error on swap-device (8:0:120) [ 948.330000] Write-error on swap-device (8:0:128) [ 948.330000] Write-error on swap-device (8:0:136) [ 948.340000] Write-error on swap-device (8:0:144) [ 948.350000] Write-error on swap-device (8:0:152) [ 948.430000] Write-error on swap-device (8:0:160) [ 948.450000] Write-error on swap-device (8:0:168) [ 948.490000] Write-error on swap-device (8:0:176) [ 948.510000] Write-error on swap-device (8:0:184) [ 948.510000] Write-error on swap-device (8:0:192) [ 948.520000] Write-error on swap-device (8:0:200) [ 948.550000] Write-error on swap-device (8:0:208) [ 948.560000] Write-error on swap-device (8:0:216) [ 948.560000] Write-error on swap-device (8:0:224) [ 948.570000] Write-error on swap-device (8:0:232) [ 948.570000] Write-error on swap-device (8:0:240) [ 948.590000] Write-error on swap-device (8:0:248) [ 948.610000] Write-error on swap-device (8:0:256) [ 948.610000] Write-error on swap-device (8:0:264) [ 948.640000] Write-error on swap-device (8:0:272) [ 948.660000] Write-error on swap-device (8:0:280) [ 948.700000] Write-error on swap-device (8:0:288) [ 948.750000] Write-error on swap-device (8:0:296) [ 948.790000] Write-error on swap-device (8:0:304) [ 948.820000] Write-error on swap-device (8:0:312) [ 948.830000] Write-error on swap-device (8:0:320) [ 948.870000] Write-error on swap-device (8:0:328) [ 949.020000] usb 1-1.3: USB disconnect, device number 11 [ 949.020000] rndis_host 1-1.3:1.0 usb0: unregister 'rndis_host' usb-ehci-platform-1.3, RNDIS device So something seems to not work when using the SD-card. It's a Samsung SDHC-card of 32GB. I've formatted it through the webinterface and that doesn't help. Any help is appreciated. For a while I was thinking it was me who was crazy.. hah.. /crashie
  20. Ok, another update :P The issue is back again and I've only installed the urlsnarf and tcpdump modules on the SD-card. As soon as I initiate a download from the NANO it starts to disconnect and reconnect the interface and behaving crazy. Wondering if it's about heating issues or something else. It doesn't matter if I try to do it connected directly to the NANO with through the USB-port or over the Wi-Fi. The same result in the end. Always disconnects after some seconds, reconnects and disconnects and so on for a while and in the end interrupting the transfer. Doesn't matter which computer I try from, it's the same result. Maybe it's my bad luck and the device is faulty? Or there is something I can do to solve it.. Another thing I've noticed today is that when I've "checked" the PineAP "Allow Associations" box and starts it disables itself after a while. Sometimes not at all but sometimes on it's own after just minutes. I recheck it and it stays enabled for a while after that. But somethings really weird, that I can say at least. Hopefully someone here have some ideas to try :) /crashie
  21. When running the NANO with tcpdump enabled it gives me below error message from time to time. Doesn't matter what settings i use with tcpdump. "tcpdump: pcap_loop: corrupted frame on kernel ring mac offset 18512 + caplen 873269827 > frame len 131072" Anyone who knows why this happens? /crashie
  22. Update.. Did a full reflash of the firmware pushing in the reset button while connecting the nano to my USB. Then flashed the latest firmware again and configured and installed only urlsnarf and tcpdump modules. Now it seems fine and I could download a 138Mb pcap from it without issues. Going to install one module after another and see why it did what it did before.. But that's for tomorrow. Now it's sleeping time :P
×
×
  • Create New...