docs: point to tech descriptions of network access
This commit is contained in:
@@ -23,6 +23,12 @@ Sparse 0.5 is a stopgap solution until the C2 framework itself is more mature. I
|
||||
- A richer CLI with Sparse specific commands such as #upload, #download, and #edit
|
||||
- A Windows version using winpcap, with both standalone binary and service versions
|
||||
|
||||
## How it works, or what makes this unique
|
||||
|
||||
[Read the blog post about it](https://andrew.riouxs.co/articles/20251017-direct-network-access.html)
|
||||
|
||||
Sparse 0.5 weaponizes libpcap to both receive and send packets. It listens at the network interface level, recreating IP packets to respond to a UDP stream inbound to a specific port. Due to how libpcap creates a raw socket, the only thing the operating system sees is arbitrary writes to the network interface, bypassing the ACLs and auditing included in the IP, UDP, and TCP protocol suites built into the operating system.
|
||||
|
||||
# Obtaining
|
||||
|
||||
Sparse 0.5 is immediately ready to build from source if using the [Nix package manager](https://nixos.org/download) [with flakes enabled](https://nixos.wiki/wiki/Flakes) by running `nix build .#sparse-05-client`.
|
||||
|
||||
Reference in New Issue
Block a user