Save and reload Intruder attacks
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by locating the Intruder attack model, the local session database, and its schema migrations; the issue does not name specific files or tests. Trace how request templates, marker positions, payload sets, and attack settings are represented, then review the roadmap's M4 work. Done means saved attacks reopen with their configuration, management operations are isolated, persistence survives upgrades, optional result retention is bounded, and the listed tests and documentation are covered.
Written by the indexing model from the issue text.
Description
Context
Intruder attacks are runtime-only. A test that needs revisiting after a restart
must be rebuilt by hand, including the request template, marker positions,
payload sets, attack type, and concurrency/scope settings. The roadmap lists
saved attacks as remaining M4 work.
Proposal
- Save an attack definition containing the request template, positions,
payload-set contents, attack type, concurrency, scope/rewrite policy snapshot,
and payload processing rules once available. - Reopen, rename, duplicate, and delete saved attacks.
- Do not save results by default; offer a separate, clearly labeled option to
retain a bounded result set. - Store definitions in the local session database with schema migration.
- Warn that payloads and templates may contain credentials or sensitive data.
Acceptance criteria
- A saved attack reopens exactly as configured and can be started.
- Rename/duplicate/delete work without affecting another attack.
- Definitions survive restart and schema upgrades.
- Saving result rows is opt-in and bounded.
- Tests cover round-trip serialization and invalid/old data.
- Documentation explains retention and sensitive-data handling.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- Avg merge
- 24m
- Merged PRs (30d)
- 52
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from andyintheshell/perseid
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
andyintheshell/perseid#73 ·
Maintainers usually reply within 1 day
-
enhancement help wanted priority: p3
Difficulty 5/5 Over a week Newbie friendliness 25/100
andyintheshell/perseid#72 ·
Maintainers usually reply within 1 day
-
enhancement priority: p3
Difficulty 5/5 Over a week Newbie friendliness 35/100
andyintheshell/perseid#71 ·
Maintainers usually reply within 1 day
-
enhancement priority: p3
Difficulty 5/5 Over a week Newbie friendliness 35/100
andyintheshell/perseid#70 ·
Maintainers usually reply within 1 day
-
accessibility enhancement help wanted priority: p2
Difficulty 5/5 Over a week Newbie friendliness 38/100
andyintheshell/perseid#69 ·
Maintainers usually reply within 1 day
All issues in andyintheshell/perseid
Similar issues
-
checkpoint/verify/rebuild_indexes on a thread holding a WriteTransaction deadlock instead of INT-001Openbug known-issue
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
project-minigraf/minigraf#734 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
bitcoindevkit/electrum_streaming_client#57 ·
Maintainers usually reply within 2 days