$ the-wire · showcase
PyRIT ships ProPILE leak probes and a runtime techniques registry
By RepoJournal · Filed · About AI Red Teaming · Composed from the cited sources · methodology
PyRIT gained a native port of Garak's ProPILE privacy-leakage probes and a GUI-time techniques registry, while garak removed a false-positive ANSI hit that inflated detector scores.
FEAT: Add Garak ProPILE privacy leakage scenario microsoft/PyRIT
PyRIT now ships `garak.propile`, a native port of Garak's ProPILE probes, with the `garak_propile_pii` dataset of Garak's 26 records (one seed per subject) and `garak_propile_templates`, its 24 templates converted to Jinja with metadata for the technique, the withheld field and the known fields. If you already run Garak for PII leakage, this gives you the same probes inside a PyRIT orchestrator.
FEAT Add runtime Techniques registry to the GUI microsoft/PyRIT
The GUI now builds its Techniques registry at runtime instead of from a static list, so techniques you have available in your install show up without a GUI rebuild. Worth checking before your next round of manual red-team runs in the browser.
Do not treat octal 27 as a raw ANSI escape (#2255) NVIDIA/garak
`detectors.ansiescape.Raw` matched the Python literal `"\27"`, which is octal 27 (byte 0x17), not ESC (0x1b), so responses containing `0x17[` or `0x17]` scored 1.0. ESC is already covered by `"\x1b"` and `"\033"`; the author verified that on tip the `test_ansiescape_raw_octal_27_is_not_escape` case fails and passes after the change, so any ANSI-escape counts you pulled from garak were overstate...
FIX: give adaptive technique selection the run id on fresh runs microsoft/PyRIT
On a fresh adaptive run, `AdaptiveScenario` passed `self._scenario_result_id` to the dispatcher while it was still None; `ScenarioContext` now carries `scenario_result_id`, picked with `uuid4()` in `initialize_async` before attacks are built and used to create the `ScenarioResult`. Adaptive runs that previously failed to associate attacks with their run id can be re-run and will persist results...
FIX: SQLite analytics timeouts microsoft/PyRIT
The SQLite analytics path no longer times out. The rest of the day was internal: PyRIT split strict HTML from checked PDF doc builds, promptfoo deleted retired site components and the unused markdown sanitizer, and its image-resolver and thumbnail-cache test work left production code unchanged.
