pwn 0.5.629 → 0.5.631

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2f0c536ea0f5b7dbd2c88621241adfa866f7ed726ee4e2109abe83aef13b0385
-  data.tar.gz: 7e3bc1436b9ce27c63da25dc609eab317a009b1339a843a6cdfe03469386b195
+  metadata.gz: f125b1fd9398d2de99e6b311a1950e646992736f38552b818cb269e9d8704a6d
+  data.tar.gz: a84266bb38a93fecb6e8c5fa0b5c73b638dcaa9196838a436c31127f95eedf31
 SHA512:
-  metadata.gz: 572496cd5d2754022fdb35c360db8e5fec65cd91693ea196f8e44666c28141f198b3353146cd658aa07b93d0add52e3808448fe0836b38830c2fb1b553d8dad2
-  data.tar.gz: 7dc0f6160402b01d8acb694e72d86daef36743fd9b9f0b84a2f87da0d77367798e8ef429463e25f36747f359c5b621615e61e26df29033de9561a24d926af4a6
+  metadata.gz: 9a2114b37283201211235e16fb558b51e5eb64ebec22d164898fc5b40db763696f56fdea8a99e9cf3905701fa3738a866726822a797e970a1de64c3ded54503d
+  data.tar.gz: fb3452718e38139450c34b8de7905188906e5d10935aabb592f6c96c0789e61ab1e29d4b4bc6e4563c1c124ffa87c835c4c417bccd99a0c919a93443e757f70f

data/README.md

@@ -1,7 +1,7 @@
 <!-- ![PWN](https://raw.githubusercontent.com/0dayInc/pwn/master/documentation/PWN.png) -->
 
 <p align="center">
-  <img src="documentation/pwn_silent_help_learn_demo.gif" alt="PWN Silent Demo — Help Surfaces + Learning Feedback Loop" width="640">
+  <img src="documentation/pwn_silent_help_learn_demo.gif" alt="PWN Silent Demo - Help Surfaces + Learning Feedback Loop" width="640">
 </p>
 
 ### **Table of Contents** ###
@@ -24,12 +24,12 @@
 
 #### **What is PWN** ####
 
-PWN (pronounced /pōn/ — *pone*) is an open-source **offensive-security
+PWN (pronounced /pōn/ - *pone*) is an open-source **offensive-security
 automation framework** and **continuous-security-integration** platform.
 It gives security researchers, red teamers, penetration testers and
 vulnerability researchers a single, scriptable Ruby surface over the entire
-offensive toolchain — from OSINT and network discovery, through web / cloud /
-hardware / radio exploitation, to reporting and disclosure — and puts a
+offensive toolchain - from OSINT and network discovery, through web / cloud /
+hardware / radio exploitation, to reporting and disclosure - and puts a
 **self-improving, tool-calling, multi-agent AI** on top of it.
 
 **In numbers:** 66 `PWN::Plugins` · 48 `PWN::SAST` rules · 90 `PWN::AWS`
@@ -43,7 +43,7 @@ Full page: [What is PWN](documentation/What-is-PWN.md)
 Offensive security is a *toolchain problem*. PWN's bet is that the right
 abstraction is **plain Ruby methods with a uniform `opts = {}` signature**,
 exposed simultaneously to a human in a REPL, an LLM in a tool-calling loop, a
-shell script in CI, and a cron job at 3 am — all open-source and auditable,
+shell script in CI, and a cron job at 3 am - all open-source and auditable,
 which matters when the caller is autonomous.
 
 Full page: [Why PWN](documentation/Why-PWN.md)
@@ -54,10 +54,10 @@ Five layers, edges only ever go down:
 
 ![PWN Overall Architecture](documentation/diagrams/overall-pwn-architecture.svg)
 
-The AI layer closes a **self-improvement loop** on every turn — Metrics +
+The AI layer closes a **self-improvement loop** on every turn - Metrics +
 Learning + **Mistakes** (introspection / negative feedback) joined with
-Snapshot + Drift + Intel + RF + **Web** (extrospection) — plus browser-backed **`extro_verify`** / **`extro_watch`** and RF **`extro_rf_tune`** sensing — via `extro_correlate`, so the
-agent knows whether a failure was *its* fault or *the world* changed —
+Snapshot + Drift + Intel + RF + **Web** (extrospection) - plus browser-backed **`extro_verify`** / **`extro_watch`** and RF **`extro_rf_tune`** sensing - via `extro_correlate`, so the
+agent knows whether a failure was *its* fault or *the world* changed -
 **and does not repeat the same mistake twice**:
 
 ![pwn-ai Feedback Learning Loop](documentation/diagrams/pwn-ai-feedback-learning-loop.svg)
@@ -68,8 +68,8 @@ on the next recurrence:
 
 ![Mistakes Negative-Feedback Loop](documentation/diagrams/mistakes-negative-feedback.svg)
 
-And **Swarm** runs multiple personas — each a full tool-calling agent,
-optionally on a *different* LLM engine — over a shared append-only bus:
+And **Swarm** runs multiple personas - each a full tool-calling agent,
+optionally on a *different* LLM engine - over a shared append-only bus:
 
 ![Swarm Multi-Agent](documentation/diagrams/swarm-multi-agent.svg)
 
@@ -103,17 +103,17 @@ Rebuild every SVG from its Graphviz source:
 
 ### **Installation** ###
 
-PWN is a **single gem** with a built-in post-install doctor/provisioner —
-`pwn setup` — that detects your package manager (`apt` · `dnf` · `pacman` ·
+PWN is a **single gem** with a built-in post-install doctor/provisioner -
+`pwn setup` - that detects your package manager (`apt` · `dnf` · `pacman` ·
 `brew` · `port`) and installs exactly the OS headers + external tools each
 `PWN::` capability needs. Tested on Kali/Debian/Ubuntu, Fedora, Arch, macOS.
 
 ```
 $ gem install pwn
 $ pwn setup                        # read-only doctor: which capabilities are usable?
-$ pwn setup --profile full --yes   # provision everything (or: web | net | sdr | vision | …)
+$ pwn setup --profile full --yes   # provision everything (or: web | net | sdr | vision | ...)
 $ pwn
-pwn[v0.5.629]:001 >>> PWN.help
+pwn[v0.5.631]:001 >>> PWN.help
 ```
 
 Only need a subset?
@@ -140,14 +140,14 @@ Full page: [Installation](documentation/Installation.md) ·
 [General Usage Quick-Start](https://github.com/0dayinc/pwn/wiki/General-PWN-Usage) ·
 local: [General PWN Usage](documentation/General-PWN-Usage.md)
 
-Update PWN frequently — new plugins, agent tools, skills and zero-day tooling
+Update PWN frequently - new plugins, agent tools, skills and zero-day tooling
 land regularly:
 
 ```
 $ gem update pwn
-$ pwn setup            # re-doctor — new versions may add capabilities
+$ pwn setup            # re-doctor - new versions may add capabilities
 $ pwn
-pwn[v0.5.629]:001 >>> PWN.help
+pwn[v0.5.631]:001 >>> PWN.help
 ```
 
 From a git checkout:
@@ -158,7 +158,7 @@ $ cd /opt/pwn && git pull && rake install && pwn setup
 
 **Inside the `pwn` REPL:**
 - Full access to every `PWN::` module.
-- `pwn-ai` — launch the autonomous agent TUI (SHIFT+ENTER newline, ENTER submit).
+- `pwn-ai` - launch the autonomous agent TUI (SHIFT+ENTER newline, ENTER submit).
 - `pwn-asm`, `pwn-ai-memory`, `pwn-ai-sessions`, `pwn-ai-cron`, `pwn-ai-delegate`.
 
 **Headless / CI one-shot (`pwn --ai`):**
@@ -181,7 +181,7 @@ $ pwn setup --profile web --yes && pwn setup --check   # exits 1 if degraded
 
 Contributions that expand PWN's offensive capabilities are welcome. If you can
 provide access to additional commercial LLMs, security scanners, or bounty
-platforms — or wish to contribute plugins, AI skills, or exploit modules —
+platforms - or wish to contribute plugins, AI skills, or exploit modules -
 please [email us](mailto:support@0dayinc.com). See
 [CONTRIBUTING.md](https://github.com/0dayInc/pwn/blob/master/CONTRIBUTING.md)
 and the local [Contributing](documentation/Contributing.md) page.
@@ -190,7 +190,7 @@ and the local [Contributing](documentation/Contributing.md) page.
 
 ### **Module Documentation** ###
 
-**Primary:** [`documentation/Home.md`](documentation/Home.md) — the full local
+**Primary:** [`documentation/Home.md`](documentation/Home.md) - the full local
 wiki with 30+ pages and 26 SVG data-flow diagrams.
 
 **API reference:** [rubydoc.info/gems/pwn](https://www.rubydoc.info/gems/pwn),
@@ -206,7 +206,7 @@ Highlights:
 [SAST](documentation/SAST.md) ·
 [AI Integration](documentation/AI-Integration.md)
 
-I hope you enjoy PWN — and remember: **always have permission** before any
+I hope you enjoy PWN - and remember: **always have permission** before any
 security testing. Now go pwn all the things (responsibly)!
 
 ---

data/documentation/AI-Integration.md

@@ -1,4 +1,4 @@
-# AI / LLM Integration — `PWN::AI`
+# AI / LLM Integration - `PWN::AI`
 
 One agent loop, five interchangeable engines. Swap providers by changing one
 line in `~/.pwn/pwn.yaml`; the tool-calling contract is normalised so the
@@ -12,12 +12,12 @@ agent code never cares which model is behind it.
 |---|---|---|---|
 | `openai` | `PWN::AI::OpenAI` | `key:` | function-calling native |
 | `anthropic` | `PWN::AI::Anthropic` | `key:` | tool-use native |
-| `grok` | `PWN::AI::Grok` | `key:` **or** `oauth: true` | OAuth = RFC-8628 device-code flow using xAI's public Grok-CLI client id (no secret) — see skill `xai_grok_oauth_device_flow` |
+| `grok` | `PWN::AI::Grok` | `key:` **or** `oauth: true` | OAuth = RFC-8628 device-code flow using xAI's public Grok-CLI client id (no secret) - see skill `xai_grok_oauth_device_flow` |
 | `gemini` | `PWN::AI::Gemini` | `key:` | function-calling native |
-| `ollama` | `PWN::AI::Ollama` | none | local — native `/api/chat` (`num_ctx`, `keep_alive`, low-temp + `format:'json'` on tool turns) and `/api/embed` for `PWN::MemoryIndex` |
+| `ollama` | `PWN::AI::Ollama` | none | local - native `/api/chat` (`num_ctx`, `keep_alive`, low-temp + `format:'json'` on tool turns) and `/api/embed` for `PWN::MemoryIndex` |
 
 > PWN is **model-agnostic**. `ai.<engine>.model` is passed straight through to
-> the provider — the codebase and docs deliberately never name a specific
+> the provider - the codebase and docs deliberately never name a specific
 > model id so you can point each engine at whatever the vendor currently
 > ships (or whatever `ollama list` shows locally).
 
@@ -29,7 +29,7 @@ ai:
   active: grok
   grok:
     oauth:
-      enroll: true    # first run opens https://accounts.x.ai/… device page
+      enroll: true    # first run opens https://accounts.x.ai/... device page
 ```
 
 ```ruby
@@ -37,7 +37,7 @@ ai:
 PWN::Env[:ai][:active] = :ollama
 ```
 
-## Engine-aware behaviour
+## Engine-aware behavior
 
 The harness adapts to the *class* of engine, not the model name:
 
@@ -48,9 +48,9 @@ The harness adapts to the *class* of engine, not the model name:
 | **Tool schemas shipped** | all toolsets | `CORE_TOOLS` + top-K keyword matches when `ai.agent.tool_router` is on |
 | **Pre-pass** | none | `plan_first` numbered tool plan before first dispatch |
 | **Few-shot** | none | `Learning.exemplars_for(request)` splices a prior successful trace |
-| **Dispatch parsing** | strict | tolerant — Levenshtein tool-name repair + JSON5-ish arg cleanup, each repair fingerprinted into `Mistakes` |
+| **Dispatch parsing** | strict | tolerant - Levenshtein tool-name repair + JSON5-ish arg cleanup, each repair fingerprinted into `Mistakes` |
 | **Post-answer** | `auto_introspect` | `auto_introspect` **+** `fact_check_local_final` (auto `extro_verify` on CVE/version-shaped claims) |
-| **Metrics bucket** | `metrics.json[:tools][name][:engines][:<engine>]` | same — the `TOOL EFFECTIVENESS` block is per-engine so local telemetry never blends with frontier |
+| **Metrics bucket** | `metrics.json[:tools][name][:engines][:<engine>]` | same - the `TOOL EFFECTIVENESS` block is per-engine so local telemetry never blends with frontier |
 
 ## Teacher-student reflection
 
@@ -78,7 +78,7 @@ puts resp[:content]
 ## Model diversity in Swarm
 
 Because each persona in [`agents.yml`](Swarm.md) can override `engine:`, an
-`agent_debate` can pit five *different providers* against each other — real
+`agent_debate` can pit five *different providers* against each other - real
 antagonism, not one model role-playing three voices. The same mechanism backs
 `ai.agent.escalation_persona`: when a local model is stuck, `Loop.run` asks a
 frontier persona for a 3-line corrective hint and injects it as a synthetic

data/documentation/AWS.md

@@ -1,4 +1,4 @@
-# `PWN::AWS` — Cloud Security (90 service wrappers)
+# `PWN::AWS` - Cloud Security (90 service wrappers)
 
 One thin module per AWS service, each wrapping the official `aws-sdk-*` gem
 with the PWN `opts = {}` convention so they compose in the REPL and in
@@ -51,7 +51,7 @@ CLI: `pwn_aws_describe_resources -r us-east-1 -o out/`
   `ec2:RunInstances` with instance profile.
 - **Persist** → new access key, Lambda backdoor, EC2 userdata.
 
-Record everything with `extro_observe(source: 'aws', …)` so
+Record everything with `extro_observe(source: 'aws', ...)` so
 [Extrospection](Extrospection.md) can correlate later.
 
 [← Home](Home.md)

data/documentation/Agent-Tool-Registry.md

@@ -24,7 +24,7 @@ toolsets; the JSON-Schema for each tool is what the model actually sees.
 
 ## Dynamic tool-set slimming (`ai.agent.tool_router`)
 
-Shipping every schema on every turn overwhelms a small local model — the
+Shipping every schema on every turn overwhelms a small local model - the
 choice space is huge and it mis-routes (e.g. picks an RF tool for a git
 question). When `ai.agent.tool_router: true` **and** `Loop.run` passes the
 user request through as `relevance:`, `Registry.definitions` shrinks the

data/documentation/Banner.md

@@ -1,4 +1,4 @@
-# `PWN::Banner` — Startup Art
+# `PWN::Banner` - Startup Art
 
 15 ANSI banners; one is picked at random every time the REPL starts. Purely
 cosmetic, entirely necessary.

data/documentation/Blockchain.md

@@ -1,4 +1,4 @@
-# `PWN::Blockchain` — BTC · ETH
+# `PWN::Blockchain` - BTC · ETH
 
 Lightweight helpers for on-chain recon and wallet interaction.
 Source: `lib/pwn/blockchain/*.rb`.
@@ -11,8 +11,8 @@ Source: `lib/pwn/blockchain/*.rb`.
 Also exposed to the agent via `PWN::AI::Agent::BTC` for wallet-aware prompts.
 
 ```ruby
-PWN::Blockchain::BTC.balance(address: 'bc1q…')
-PWN::Blockchain::ETH.call(contract: '0x…', method: 'owner()')
+PWN::Blockchain::BTC.balance(address: 'bc1q...')
+PWN::Blockchain::ETH.call(contract: '0x...', method: 'owner()')
 ```
 
 [← Home](Home.md)

data/documentation/Bounty.md

@@ -1,4 +1,4 @@
-# `PWN::Bounty` — Bug-Bounty Lifecycle Tooling
+# `PWN::Bounty` - Bug-Bounty Lifecycle Tooling
 
 | Module | Purpose |
 |---|---|
@@ -6,9 +6,9 @@
 
 Pairs naturally with:
 
-- [`PWN::WWW::HackerOne`](WWW.md) / `BugCrowd` / `Synack` — programme navigation
-- `PWN::Plugins::HackerOne` — submissions API
-- [`PWN::Plugins::BurpSuite`](BurpSuite.md) — capture the session to replay
+- [`PWN::WWW::HackerOne`](WWW.md) / `BugCrowd` / `Synack` - programme navigation
+- `PWN::Plugins::HackerOne` - submissions API
+- [`PWN::Plugins::BurpSuite`](BurpSuite.md) - capture the session to replay
 
 ```ruby
 PWN::Bounty::LifecycleAuthzReplay.start(

data/documentation/BurpSuite.md

@@ -6,7 +6,7 @@ Professional's headless mode + REST API.
 
 ![Web application testing](diagrams/web-application-testing.svg)
 
-> **Install:** `pwn setup --profile web` — burpsuite · zaproxy · chromium ·
+> **Install:** `pwn setup --profile web` - burpsuite · zaproxy · chromium ·
 > geckodriver · sqlmap · tor. See [Installation](Installation.md).
 
 ## Configure
@@ -42,7 +42,7 @@ PWN::Plugins::BurpSuite.stop(burp_obj: burp)
 ## CLI drivers
 
 - `pwn_burp_suite_pro_active_scan -t URL -o out/`
-- `pwn_burp_suite_pro_active_rest_api_scan` — pure REST, no JVM spawn
+- `pwn_burp_suite_pro_active_rest_api_scan` - pure REST, no JVM spawn
 
 ## Why preferred over ZAP
 

data/documentation/CLI-Drivers.md

@@ -1,4 +1,4 @@
-# CLI Drivers — `bin/pwn_*`
+# CLI Drivers - `bin/pwn_*`
 
 53 headless executables, each a thin `OptionParser` wrapper over one plugin
 (or one workflow). They exist so CI/CD can call PWN without a REPL or an LLM.
@@ -37,7 +37,7 @@ pwn_jenkins_install_plugin       pwn_www_uri_buster
 
 Run any with `--help` for its flags.
 
-## `pwn_setup` — post-install doctor & capability provisioner
+## `pwn_setup` - post-install doctor & capability provisioner
 
 The one driver that isn't a plugin wrapper. It grows a bare `gem install pwn`
 into a fully-armed host by installing OS headers / external tools for whatever
@@ -69,7 +69,7 @@ sast:
 
 ## Write your own
 
-See [Drivers](Drivers.md) — copy any file in `bin/`, swap the plugin call,
+See [Drivers](Drivers.md) - copy any file in `bin/`, swap the plugin call,
 `rake install`, done.
 
 [← Home](Home.md)