Jump to content
Hak5 Forums

Search the Community

Showing results for tags 'reboot'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Talk
    • Everything Else
    • Gaming
    • Questions
    • Business and Enterprise IT
    • Security
    • Hacks & Mods
    • Applications & Coding
    • Trading Post
  • WiFi Pineapple / Jasager
    • WiFi Pineapple TETRA
    • WiFi Pineapple NANO
    • Mark V
    • Mark IV
    • Pineapple Modules
    • WiFi Pineapple University
    • Mark I, II, III
  • Active Projects
    • Bash Bunny
    • Packet Squirrel
    • Lan Turtle
    • USB Rubber Ducky
    • SDR - Software Defined Radio
    • Community Projects
  • Hak5 Shows
    • Hak5
    • HakTip
    • Metasploit Minute
    • Threatwire
  • Community
    • Forums and Wiki
    • #Hak5
  • Other Projects
    • Interceptor
    • USB Hacks
    • USB Multipass
    • Pandora Timeshifting

Found 7 results

  1. How to set up once every 1 hour

    I want the wifipineapple to be restarted every 1 hour! I used the Crontab task, but it did not work! How can i do it?
  2. Cron reboot command?

    Hi all, Just got a LT last week, and liking it so far. Though my plan for it requires it be placed in a remote location I can't get into without some effort. That said I want to use cron to reboot the LT on a time schedule, either a specific time say 1AM EST, or after a certain amount of uptime. I've had no luck with the entries I've made into cron so far. ex. 0 1 * * * root reboot > /dev/null 2>&1 0 1 * * * /sbin/reboot If anybody can help me find a working cron reboot setup I'd be so very grateful! Thanks! lasermole.
  3. Hi everyone! I'm new to the pineapple, about one week new; and I've been having a lot of fun so far. Ive been going mad this evening however. I've be learning to use PineAP and once I start it up the Pineapple crashes within about 15 minutes max. I did some googleing and I haven't found anyone else with this issue. Additionally I've tried resetting to factory settings, but the issue persists. Really hoping someone can offer some advise.
  4. Hi, i setup and configured the tetra and everything works fine, I tried to activate the PineAP and started with just collecting SSID into the pool, everything still fine. When i then just activated the broadcasting from the pool it stayed up for 10 seconds and then the tetra just reboots. this happens with any attack on the pine AP. I had it either powered through USB (single on USB3, USB2, or both connections on USB2) and power supply. are there any troubleshoot steps i can perform?
  5. Mark 5 Reboot

    All, When rebooting the mark 5 from the web console it states to give it some time to reboot. When will it reboot and will i need to log back in? The box continues to be on as though it has not rebooted. Help. F3rn.e
  6. This is my first contribution as I am brand new to RubberDucky, This payload sets the syskey password and requires password on reboot. The password is sets is "quackdown" . After setting the password it will force a reboot resulting in a locked computer. This is just a prank and can be fixed with system restore or you can just disable the password requirement by running syskey again. Total execute time should be right at 25 seconds. ducky_code.txt inject.bin
  7. Hell-Low H5 FolkZ @SF, Just got a new Turtle and waz playin around with it. Seems to be quite k3wL, but there are problems with the mac changer of the wan interface. 1st issue - it does not work - the interface goes down and does not come back (eth1). after manually /etc/init.d/network restart all worx fine (with static IP settings and faked mac 2 deploy device in an secured environment with mac binding). 2nd issue - how can i make the mac change persist a power cycle. I want to deply that tiny device in a secured environment with static ip settings and mac binding. So i will loose contact to the turtle after a power cycle. The scenario ist to drop the device @ a network with static IP settings and i must fake the mac of an registered device to be able to autossh out of the network. The fake mac and the static ip settings must persist a power cycle or the device is "lost". Any suggestions ? Maybe a tiny shell script ? but where to put (for persistance) ?
×