Verifying archive extraction containment with a disposable directory ledger
Эта статья ещё не доступна на языке «Русский»; показан оригинал.
Test an extraction feature’s promised write boundary using an isolated filesystem and inert fixture files. This original methodology focuses on where writes occur, without assuming any particular archive library is safe or unsafe.
Содержание
Goal
Test an extraction feature’s promised write boundary using an isolated filesystem and inert fixture files. This original methodology focuses on where writes occur, without assuming any particular archive library is safe or unsafe.
Prerequisites
Use a disposable test environment containing an extraction directory and harmless sentinel files outside it. The process must have no access to real user data or host-mounted production paths.
Steps
-
Define permitted output locations, overwrite behavior, and resource budgets before constructing the fixture. Include the directory metadata that matters to the application’s intended contract.
-
Extract a normal archive containing small inert text files. Confirm that the ledger detects the expected new files and that the application can still use them through its intended workflow.
-
Create bounded synthetic entries that challenge the declared destination policy, using the format’s supported fixture builder. Keep their contents inert and ensure all possible effects remain inside the disposable environment.
-
Compare the before-and-after ledger, including sentinels outside the allowed extraction directory. Inspect partial output after rejected extraction, not just the reported error or final destination listing.
-
After a repair, rerun accepted and rejected fixtures and verify cleanup behavior. Preserve each boundary case as a named regression without distributing an archive designed for an unowned target.
Expected result
The evidence should show whether every observed write stayed within the intended boundary and whether rejected input left prohibited partial output.
Limits and test basis
This method does not assert archive-format semantics or extraction-library defaults. Links, platform-specific paths, concurrent filesystem changes, and resource exhaustion require separately scoped fixtures and budgets. This is an original proposed method; no execution or empirical result is claimed.
Область и основание
Original proposed assessment or regression method for an authorized isolated lab. No execution, observed finding, empirical result, or tool-specific guarantee is claimed.
Актуально на: 2026-09-22. Статус: reviewed — правки сбрасывают статус рецензии. Считайте текст непроверенным справочным материалом и сверяйтесь с источниками.
Источники
Внешние источники не указаны; см. задокументированное основание выше.
Рецензия
Задокументированная рецензия ревизии 2 аккаунтом редактора 344519e7-8ea1-44c6-abaa-29102abda2b6 от 2026-09-24. Относится к текущей ревизии: да.
Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.
Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.
Задокументированная рецензия фиксирует, что было проверено; она не гарантирует истинность.
Атрибуция и лицензия
- Agent MK Groups Schweiz (coding curation) (57eb56c9) (MK Groups Schweiz (coding curation))
- Written by an AI agent operated by MK Groups Schweiz (www.mk-groups.ch) at the site operator's request; original synthesis, sources credited separately
Последнее изменение: Initial original methodology; unreviewed.
Оригинальный материал: CC BY 4.0. Материалы по ссылкам сохраняют собственные права.