📔
Notes
  • Notes
  • Starting with (n)vim
  • Bluetooth
  • Hacking boot2root/ OSCP notes
  • Capture the flag(CTF)
    • Commonly Used Tools
    • Web
    • Cryptography
    • Forensics
  • Making a boot2root VM
    • Important rules
    • [General things](VM/Make boot2root VM.md)
    • Setting Systemd services
    • Setting fail2ban
  • BugBounty notes for Android
    • General
    • Adb/drozer commands
    • Intents
    • Permissions
    • Activities
    • Broadcast Receivers
    • Content Providers
    • Services
  • BugBounty notes for WEB
    • Authentication
    • CORS
    • General Web
    • HTTP Parameter poisoning
    • IDOR
    • graphql
  • Age of Empires IV
    • Age Of Empires
    • Build Orders
      • English Civ
    • Sheep scouting
Powered by GitBook
On this page
  1. Making a boot2root VM

Important rules

PreviousMaking a boot2root VMNext[General things](VM/Make boot2root VM.md)

Last updated 3 years ago

These are the must do's and don'ts of making the boot2root machine.

  • Always link .bash_history file to /dev/null

    • ln -sf /dev/null .bash_history

  • If you for some reason used your SSH key to easily access the VM for testing or any other purpose make sure to remove it.

  • Test your VM with lowest possible hardware configuration so you know when your thing will crash.

  • Make sure to thoroughly test all the things so that you don't mess up.

    • If you want other people to test your VM then contact

      • I get all my VMs test by them :-)

  • Use Fixed memory allocation since that is much faster

    • Not a fixed rule but it's prefered.

  • Assign 1 GB RAM first and then test the VM if it's slow or something then extend the RAM .

    • This helps to test VM on low specs. We might have 8/16GB ram but the person doing might not have that.

  • For ubuntu always use the server version and not the GUI/full ISO

    • http://old-releases.ubuntu.com/releases/

m0tleycr3w