Repository navigation
Expand file tree
/
Copy pathREADME.Debian
More file actions
51 lines (40 loc) · 2.45 KB
/
Copy pathREADME.Debian
File metadata and controls
51 lines (40 loc) · 2.45 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
Wraith for Debian-family amd64 systems
======================================
The package installs the sensor at /usr/bin/wraith and the manual at
/usr/share/man/man1/wraith.1.gz. It does not install simulator executables,
a service, a system-wide tracing policy, setuid bits or file capabilities.
Before use:
wraith --version
wraith doctor
wraith doctor --json
man wraith
Doctor checks this machine's native platform, procfs and actual tracing of
an owned child, and reports Yama policy separately. An unhealthy environment
returns status 2 and a JSON ready:false report; that is a runtime prerequisite
failure, not proof that dpkg failed to install the package.
Start with an owned foreground process in observe mode:
wraith run -- /usr/bin/your-service --foreground
wraith run --json ./events.jsonl -- /usr/bin/your-service --foreground
Attach and scan require the permissions already enforced by Linux. Review
ownership, Yama policy, namespaces and conflicting tracers locally. The package
never changes these settings. Do not grant broad capabilities merely to hide a
permission error. Baseline legitimate execution before selecting --block or
--kill. A verdict is a configured behavioral signal, not forensic proof.
Supported execution is native Linux x86-64 (amd64), kernel 5.3 or newer with
procfs and usable ptrace. 32-bit/x32 targets are not supported. Dependencies
in the package control record are calculated from the actual ELF binary by
dpkg-shlibdeps; the binary needs the listed libc/libgcc versions. Building on
a newer distribution can raise those requirements. This package format is
compatible with Debian/Kali package tooling, but it does not constitute a
claim of official Debian/Kali archive inclusion or testing in every release.
The repository's package test inspects and extracts the .deb into a temporary
directory and executes its sensor over local controls. It does not install
into the host package database. Run that test only over a trusted package built
from this source: structural archive checks are not a sandbox for arbitrary
executables. No Kali VM or real-host installation is implied by that evidence.
Full threat model, detection limits and operator guidance:
https://github.com/grloper/Wraith/blob/main/docs/threat-model.md
https://github.com/grloper/Wraith/blob/main/docs/operations.md
Upstream source and private security reporting guidance:
https://github.com/grloper/Wraith
https://github.com/grloper/Wraith/blob/main/SECURITY.md