Explore >> Select a destination
|
You are here 
|
www.andreinc.net | ||
| | | | |
www.rodrigoaraujo.me
|
|
| | | | | Virtual Machines (VMs) are a magical thing: a computer being emulated inside a physical computer. Since this emulated computer isn't physical, we call it "virtual". Such a simple description for something so powerful. From a practical perspective, VMs allow users to safely run programs in an isolated environment: the emulated machine. Why build a Virtual Machine from scratch So, why build one when there are already so many great VMs out there? | |
| | | | |
blog.deobfuscate.io
|
|
| | | | | Using symbolic execution to reverse engineer and devirtualise a binary using virtual machine obfuscation. | |
| | | | |
www.jmeiners.com
|
|
| | | | | [AI summary] The provided text outlines the development of an LC-3 virtual machine (VM) in C, including the implementation of various instructions, memory operations, and input/output handling. It also discusses an advanced C++ approach using templates and bitwise flags to reduce code duplication and improve efficiency. The text covers topics like instruction decoding, memory addressing, flag handling, and platform-specific input buffering. Additionally, it references contributions from the community and mentions GitHub tags for organizing implementations in different languages. | |
| | | | |
xcellerator.github.io
|
|
| | | Okay, so you've built your first kernel module, but now you want to make it do something cool - something like altering the behaviour of the running kernel. The way we do this is by function hooking, but the question is - how do we know which functions to hook? Luckily for us, there is already a great list of potential targets: syscalls! Syscalls (or system calls) are kernel functions that can be called from userspace, and are required for almost anything remotely interesting. | ||
