Skip to content

Commit 6a7d7ee

Browse files
committed
docs(patches): clarify this is a partial demo subset; v2/persona work ships closed in the binary
1 parent f1042e1 commit 6a7d7ee

1 file changed

Lines changed: 22 additions & 17 deletions

File tree

patches/README.md

Lines changed: 22 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,29 @@
1-
# Patches — the open surface layer
1+
# Patches — a partial surface layer (demo)
22

3-
These are Fortress's **surface-coherence patches**: the in-tree Chromium/Blink modifications that read a
4-
per-launch persona and present it consistently across the JS-observable fingerprint surfaces (user-agent,
5-
platform, WebGL, timezone, languages, screen, keyboard, media, and so on), including inside worker and
6-
iframe realms.
3+
These are **some** of Fortress's surface-coherence patches: in-tree Chromium/Blink
4+
modifications that read a per-launch persona and present it consistently across the
5+
JS-observable fingerprint surfaces (user-agent, platform, WebGL, timezone, languages,
6+
screen, keyboard, media, and so on), including inside worker and iframe realms.
77

8-
> **These patches are a reference layer — not the whole engine, and not the current build.**
8+
> **This is a representative subset — not the full set, not the newest work, and not
9+
> the current build.**
910
>
10-
> The part that *mints* a coherent, per-launch real-device persona and *delivers* it into the process —
11-
> the device-model corpus, the joint-distribution generator, and the process-level delivery seam — ships
12-
> **compiled inside the released binary** and is intentionally **not** in this repository. Building from
13-
> these patches alone will *not* reproduce the shipped stealth (you'll get surfaces that read a persona
14-
> that nothing is providing); it demonstrates the technique, not the product.
11+
> What's here is an earlier demonstration slice. The bulk of the current stealth — the
12+
> newer ("v2") surface-coherence patches, plus the part that *mints* a coherent
13+
> per-launch real-device persona and *delivers* it into the process (the device-model
14+
> corpus, the joint-distribution generator, and the process-level delivery seam) —
15+
> ships **compiled inside the released binary** and is intentionally **not** published
16+
> here.
17+
>
18+
> Building from these patches alone will **not** reproduce the shipped stealth (you'll
19+
> get surfaces reading a persona that nothing provides). It demonstrates the technique,
20+
> not the product.
1521
1622
For the real, current engine:
1723

18-
```bash
19-
pip install -U tilion-fortress
20-
# or
21-
docker run --rm -p 9222:9222 tilion/fortress:latest
22-
```
24+
pip install -U tilion-fortress
25+
# or
26+
docker run --rm -p 9222:9222 tilion/fortress:latest
2327

24-
See the [latest release](https://github.com/tiliondev/fortress/releases/latest) for what actually ships.
28+
See the [latest release](https://github.com/tiliondev/fortress/releases/latest) for
29+
what actually ships.

0 commit comments

Comments
 (0)