[Threat]: Archived web content as evidentiary weapon
edsu opened this issue · 1 comments
edsu commented
Describe a use case for WACZ format.
A member of a harassment community collects the output of a targeted individual. Here, the goal is to develop a richly detailed database of said individuals -- both of their own output, but also material related to them (online criminal records, sensitive photos, previous aliases, abandoned online presences, etc).
Additional Requirements
- List of entry pages to start browsing from
- Full-text search index
- Technical metadata about the web archive
- User-defined descriptive metadata
- Screenshots of key pages
- Encryption of data
- Proof of Authenticity (Signing and Verification)
- Fast access to multiple WACZ files in aggregate
- Crawl or capture logs
How will web archives be created for this use case?
- Manually, using a browser to capture exact content as directed by the user.
- Automatically, using a crawler to crawl desired content, either once or on a specified schedule.
Sensitive private content and access
- No, this use case focuses on archiving publicly accessible data only, and web archive can be made public.
- No, this use case focuses on archiving publicly data only, but web archive is not inteded to be public.
- Yes, this use case involves archiving data that is not public, and the web archive should not be made public.
edsu commented
This has been added to the current use cases document.