dyncvoke-core 0.1.0

PEB walking, dynamic invoke, and Tartarus Gate indirect syscalls for Dyncvoke
docs.rs failed to build dyncvoke-core-0.1.0
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build: dyncvoke-core-0.1.1

PEB walking, export parsing, Tartarus Gate syscalls, and nt_* wrappers.

This is the default dyncvoke backend (feature = "syscall"). The usual entry points are [syscall!], [do_syscall!], [resolve_syscall], [get_module_base_address], and [get_function_address].

Indirect syscalls:

  1. [resolve_syscall] finds the ntdll stub, extracts the SSN (Hell's / Halo's / Tartarus Gate), and locates a syscall; ret gadget.
  2. [syscall!] does that and dispatches in one step.
  3. [do_syscall!] dispatches a cached (ssn, addr) pair with no extra resolution.
use dyncvoke_core::syscall;

let status = syscall!("NtClose", handle).unwrap() as i32;

Module lookup walks PEB->Ldr->InLoadOrderModuleList. It does not call EnumProcessModules or GetModuleHandle.