Repository navigation
LIVE OPS batch 2: recurring schedules, quishing, launch-from-map - #10
Merged
Merged
Conversation
A schedule materialises a fresh campaign on a cadence (baseline -> periodic retest) without rebuilding it each time. Guardrail-safe: each run is created in pending_approval, never auto-sent, so two-person approval and the kill switch still apply — the schedule only automates the drafting cadence. - backend: CampaignSchedule + CampaignTemplate schemas; services/live/scheduler.py (materialize/run_due/run_scheduler background loop wired into lifespan); /live/schedules CRUD + run-now; index. 6 tests. - frontend: a "Jadwalkan berulang" toggle on the create form (reuses all its fields) + a "Kampanye terjadwal" card (run-now / pause / delete). Verified: 194 backend tests pass, ruff clean, frontend builds clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
A campaign can deliver its lure as a QR code instead of (or alongside) a link —
a current, fast-growing attack vector. The QR encodes the GoPhish-tracked URL,
so a phone scan is attributed to that recipient exactly like a click; tracking
and the teachable-moment landing page work unchanged.
- backend: /live/qr PNG endpoint (segno, pure-Python, no Pillow; public so a mail
client can load it); launch injects the QR image (encoding {{.URL}}) when
use_qr is set; use_qr on the campaign + schedule template; public_base_url
added to live config. 5 tests. segno pinned in requirements.
- frontend: "Quishing (kode QR)" toggle on the create form; public_base_url
field in Settings.
Verified: 199 backend tests pass, ruff clean, frontend builds clean.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Connects the two flagship features: a "Luncurkan ke titik rawan" button on the Attack Surface Map collects the emailable, most-susceptible people and hands them to a new live campaign with recipients pre-filled — the map identifies the human risk, one click targets it, and the results feed susceptibility back into the map. - backend: OrgNode gains an optional email (planning address); GET /attack-surface/targets returns emailable people ranked most-susceptible first (resolving via node email or linked user); demo nodes get sandbox emails. 3 tests. - frontend: the map button stashes recipients and navigates to Live Campaigns, which opens the create form pre-filled. Verified: 202 backend tests pass, ruff clean, frontend builds clean; end-to-end in the running stack (7 ranked targets -> prefilled campaign). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…-guide) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three LIVE OPS features, each tested.
Recurring campaign schedules
A schedule materialises a fresh campaign on a cadence (baseline → periodic retest). Guardrail-safe: each run is created in
pending_approval, never auto-sent — two-person approval and the kill switch still apply. UI: a "Jadwalkan berulang" toggle on the create form + a schedules card (run-now / pause / delete). Background loop wired into the app lifespan.Quishing (QR codes)
A campaign can deliver its lure as a QR code encoding the GoPhish-tracked URL, so a phone scan is attributed to the recipient exactly like a click.
/live/qrPNG endpoint (segno, pure-Python), QR injected into the email at launch,use_qrtoggle,public_base_urlin Settings.Launch from the Attack Surface Map
GET /attack-surface/targetsreturns the emailable, most-susceptible people; a "Luncurkan ke titik rawan" button pre-fills a campaign with them. The map finds the human risk, one click targets it, and the results feed susceptibility back into the map.Verification
202 backend tests pass (14 new), ruff clean, frontend builds clean, Docker build green; all three verified end-to-end in the running stack.
🤖 Generated with Claude Code