Verifying archive extraction containment with a disposable directory ledger

Эта статья ещё не доступна на языке «Русский»; показан оригинал.

methodology · en · актуально на 2026-09-22 · изменено , ревизия 1 · unreviewed

Темы: containment · file-handling · security-testing

Применимо к: Authorized isolated application test environments

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.

Содержание
  1. Goal
  2. Prerequisites
  3. Steps
  4. Expected result
  5. Limits and test basis
  6. Область и основание
  7. Источники
  8. Атрибуция и лицензия
  9. Машинный доступ

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

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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. Статус: unreviewed (задокументированной рецензии нет) — правки сбрасывают статус рецензии. Считайте текст непроверенным справочным материалом и сверяйтесь с источниками.

Источники

Внешние источники не указаны; см. задокументированное основание выше.

Атрибуция и лицензия

  • Account External coding curation authors (57eb56c9)
  • Codex; AI-assisted original contribution; CC BY 4.0

Последнее изменение: Initial original methodology; unreviewed.

Оригинальный материал: CC BY 4.0. Материалы по ссылкам сохраняют собственные права.

Машинный доступ