/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 keyj.emphy.de
KeyJ's Blog : Blog Archive ยป Writing ultra-small Windows executables
| | idafchev.github.io
Basics of Windows shellcode writing | Ring 0x00
2.8 parsecs away

Travel
| | A second look at the arcane art of shellcode writing
| | gpfault.net
Let's Learn x86-64 Assembly! Part 0 - Setup and First Steps
1.2 parsecs away

Travel
| | [AI summary] The provided text is a detailed explanation of how to write a simple 64-bit Windows application in assembly language that calls the ExitProcess function from the KERNEL32.DLL library. It covers the following key topics: 1. **Memory and Register Basics**: Explains how memory and registers work in 64-bit Windows, including the use of the stack pointer (RSP), registers like RCX, RDX, R8, and R9 for passing arguments, and the importance of stack alignment for performance. 2. **Calling Conventions**: Details the 64-bit Windows calling convention, including how the first four integer or pointer arguments are passed in registers (RCX, RDX, R8, R9), how additional arguments are passed on the stack, and the requirement for the stack to be aligned to ...
| | toddcullumresearch.com
Portable Executable File Corruption Preventing Malware From Running - Todd Cullum Research
4.2 parsecs away

Travel
| | Important Disclaimer YOU MUST READ FIRST! Portions of this article contain source code from the Windows Research Kernel. This code is the intellectual property of Microsoft Corporation. I am using this code under special license in this post under these grounds of the license agreement: You may distribute snippets of this software in research... Read More
| | zenodo.org
AST vs. Bytecode: Interpreters in the Age of Meta-Compilation (Artifact)
24.1 parsecs away

Travel
| This artifact accompanies our paper AST vs. Bytecode: Interpreters in the Age of Meta-Compilationto enable others to reuse our experimental setup and methodology, and verify our claims. Specifically, the artifacts covers our three contributions: It contains the implementation of our methodology to identify run-timeperformance and memory usage tradeoffs between AST and bytecode interpreters. Thus, it contains all benchmarks and experiments for reproduction of results,and reuse for new experiments, as well...