Jump to content
Hak5 Forums

Zylla

Dedicated Members
  • Content Count

    534
  • Joined

  • Last visited

  • Days Won

    32

About Zylla

  • Rank
    Developer / Reverse Engineer
  • Birthday 11/22/1988

Contact Methods

  • Skype
    adde88@gmail.com

Profile Information

  • Gender
    Male
  • Location
    Norway

Recent Profile Visitors

3,840 profile views
  1. Your fstab file is not correct. It's trying to mount the normal SD-card (builtin) to the wrong directory. (/sd1) The directory should be /sd and the device should NOT be /dev/sdcard/sd1 if using a usb flash drive. But normally something like /dev/sdb1 or /dev/sda1. (Depends on how you've formatted the drive and what device ID it registers with (sda, sdb))
  2. I'm not sure. Windows should detect any hardware being connected, like the "sound you get when you connect something to it. What device are you trying to use? You could try pasting me the output of "dmesg" a couple of seconds after inserting the device. For the Nano I recommend using a normal USB flash drive mounted as /sd, instead of the SD-card. As it seems to have alot of issues with SD-cards. Guides for doing so can be found in this thread, as alot of users are doing it. PS. Use pastebin.org for your dmesg output, it's alot of stuff being outputted.
  3. Well, you're main-problem is that /sd is not mounted properly. Also /etc/fstab is a file, not a directory. (Use "cat /etc/fstab" to read it) When you get /sd mounted properly, all you have to do is to launch the INSTALL.sh script. And then "install-mana-depends". You don't have to "opkg update" before launching my installer, it takes care of doing that. It's simply two steps. INSTALL.sh -> install-mana-depends But you need to get /sd sorted out first.
  4. I guess I've forgotten to update the forum-site after upgrading the packages. Just check the repo manually to get the correct files until I get it checked out.
  5. @Colincolin343 Are you sure your /sd directory is mounted properly? What output do you get when using "mount"? And please paste the output of /etc/fstab It could be that your PATH variable is bugged. The launch-mana script gets installed to either /usr/sbin or /sd/usr/sbin If PATH doesn't check /sd/usr/sbin it won't find the script. But it's working flawlessly on both my Tetra and Nano.
  6. Haven't tested it, but since Raspberrien is also based on Debian I don't see any reasons for it to not work if you have all the dependencies installed. But you would need to patch the kernel to get monitor-mode on wlan0.
  7. Phew. I know the last update from ZerBea fixed some bugs with direct probe-request handling. So i got worried something was wrong on my part. 😮 Glad to hear everything's good! 🙂
  8. @g0blin The recent versions don't work? 😮
  9. Kali is based on Debian, the only "modified versions" I can think of is the images you can download containing the Nexmon patches, making you able to run wlan0 in monitor-mode (and AP mode at the same time) But that's just a kernel patch. Here's link for a great version: https://re4son-kernel.com/re4son-pi-kernel/ And yeah, same with the Pineapple. You don't use hashcat on these devices to crack the PMKID, you transfer the captures from the device to your desktop which hopefully has a GPU or something 🙂
  10. I would also like to notify people (since it's been discussed earlier in the thread) that i was able to cmopile this without any problems on my Raspberry Pi 3b+. And it's working perfectly. 🙂
  11. It was working perfectly on my Kali installation, until my laptop died. I have an RPI3B+, and I haven't tested it there myself, it should be working on it according to the developer. (ZerBea) Check if you have all dependencies installed before compiling. 🙂
  12. Thanks. I'm hoping to get back on track asap. 🙂 @Sleezybax That'd be really helpful. I got some components myself that could boost performance, like RAM and SSD-disks laying around. I'm not looking for a beast-laptop for gaming and such. But still something that's stable and works. Like, if i was to purchase a new one today in the stores, i'd probably focus on the CPU. Do you have any details on the "asset" you mentioned? 🙂 Thanks a lot for attempting to help out 🙂
  13. Hi guys! I'm just giving you all a heads up that my laptops motherboard decided to die the other day. I've tried everything to debug it, and it seems hopeless. And due to financial reasons i'm unable to get a new one immediately. I'm hoping to find someone local selling their "old one" (when i can afford it), just so i can get back to working on stuff. So just a heads up that it might be a while until updates are coming, and the module i had started working on. Hoping you all have a great week! I'm still following everything from my phone 🙂
  14. Zylla

    kinda useless device in 2018

    Considering you can now catch the PMKID's of your entire neighborhood with a device that fits in your pocket in just a minute (client less). The Pineapple NANO/TETRA is one of the most useful devices for getting handshakes, MiTM attacks, etc. But it might often require some customization for a higher success-rate. Yes. The Pineapple comes bundled with some GUI attacks through it's web interface, which are useful. (But will fail on alot of attempts) BUT if you really take some time to learn all the stuff you can do with custom scripts, modules, tools, The Pineapples are still EXTREMELY powerful in 2018. But that's just my opinion. The Raspberry Pi B3+ is also quite powerful, and cheap. (Especially love the wifi-chip with the Nexmon drivers. Making it possible to have your one wifi interface in both AP and monitor mode at the same time)
  15. Bah, damn PATH bug. 😛 I've updated again. Removed the PATH patching part of the installation procedure. And rather install the binaries somewhere already specified in the default PATH. But people, or Hak5 should still patch their PATH variable, as tools like for example reaver are known to install to /sd/usr/sbin or /sd/usr/bin, giving users error messages when attempting to install. But now everything should work flawlessly on both devices. No need for the PATH patch 🙂
×