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. リンク先の出典はそれぞれの権利を保持します。

機械アクセス