Baz00k@
FileSniffer QT Icon
System / Development

FileSniffer QT

0.1.0.1

File search by extension. Disk scan, exclude patterns, CSV export.

What the project solves

FileSniffer QT is an audit tool and controlled extraction of files from large directory trees. Combines the scan by connections, path rules, capture into separate output, hash deduplication and optional cleanup with detailed session log.

How the application works and what it is for

Overview and purpose

FileSniffer _ QT is a robust desktop analytic and maintenance tool designed for recursive file system search, selective capture (capture) data according to defined connections and controlled cleanup (cleaning) of unnecessary ballast. The tool is designed for forensic and system work, where emphasis is placed on determinism, auditability and security.

Key operating pillars:

  • Determinist run: The combination of path rules, prefix limits and hash deduplication ensures that you get an identical output for identical input and configuration.
  • Clearup safety: The Ignored Basenames, Ignor Patterson, Path- Too-Long Skips (IHO) prevents the unauthorised deletion of critical system components.
  • Auditability: Each operation generates a telemetry event that is aggregated into and then exported to a structured JSON / CSV package.

Export of contracts (Data structure)

08.1 Package Metadata (JSON)

Each Capture package contains with the following keys (Appendix N):

  • : root path, start _ time, end _ time, duration in seconds.
  • : whitelists, blacklists, active _ extensions (for audit).
  • : throughput (MB / s), file _ frequency, error _ ratio.
  • : Complete Dump Object with all counters.

08.2 Metric Summary (CSV)

Table export for analytical tools:

  • : Sum of sizes and numbers of found / copied files by extension.
  • : Detailed list of all deleted files with time stamp and method used (RECYCLE / FORCE).

Operations-first runbooks

9.1 Baseline Audit (Read Only)

Objective: Find the status without modification of the disk.

  1. Configure Scan- root directory.
  2. In Path Rules dialog, turn off Cleanup i Copy files (Checkbox "Audit only").
  3. Run the scan.
  4. Result: Complete inventory of files in the log and main table without interference with FS.

9.2 Safe Cleanup

Objective: Remove the known ballast to the Windows basket.

  1. Set Whitelist to target the work area.
  2. Activate "Enable Cleanup" in Rules.
  3. Make sure that the Force delete is VYPNUTO (stays in Recycle Bin).
  4. Run the scan.
  5. Check the Recycle Bin after completion for possible renewal.

9.3 Forensic Capture (Deduplicated)

Objective: Collect all documents, omit duplicity for saving the site.

  1. Set Formats (found in extension dialog via "Select All Documents").
  2. Activate Hash Deduction (SHA-256).
  3. Activate Copy Files.
  4. Run the scan.
  5. Result: Unique set of files in one package.

Scenario matrix (Code branches)

The branch (Scenario)Code / FlatulenceResult / Action
Init: Missing Config in config managerCreates default config with fallback language (EN).
Scan: Path Too Long in LoopHigher , file is not deleted (safety).
Copy: Hash Hit RepositorySkips copying, increments .
Cleanup: Permission Denied in lubricating phaseLogs in the log panel, continues to the next file.
UI: Close while running interruptIt will call , waiting for the signal before closing.
Finalize: at the end He writes a session log, creates an empty manifesto, skips the zipping.