Repository navigation
docs(threat-model): news feed sources as an entry point - #522
Merged
Merged
Conversation
News feeds (#453) are fetched like iCal feeds: through netguard, with their address and password sealed. The threat model now says so: a News feed sources entry point, and news feeds beside iCal in P-SECRETS, P-ADMIN-GUARD, N-EGRESS, the outbound domains and the web networks hazard. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SWH8a26M9wkAPq2eRrfWZK
# Conflicts: # threat-model.yaml
# Conflicts: # threat-model.yaml
# Conflicts: # threat-model.yaml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Adeel · project thread
Description
Before: the threat model didn't mention the news feed sources merged in #453.
After: it has a News feed sources entry point (the feed's address or a site's page, a user and password; the feed's XML and its posts' HTML, controlled by whoever serves the feed), and lists news feeds beside iCal wherever iCal's guards are described: P-SECRETS (the address is sealed and write-only), P-ADMIN-GUARD (fetched like web captures; the password never goes on to a server a feed redirects to, or to a feed a site's page names on another server), N-EGRESS, the outbound port and address-guard rows, the remote-identity row and the wide
LENS_WEB_NETWORKShazard. The JSON and YAML sidecars carry the same, with the documented counts up by one.How: this was part of #453, split out because every other change to the threat model conflicted with that pull request while its CI ran.
Motivation and Context
New attack surface goes into the threat model (AGENTS.md, Private and secure).
Steps to reproduce (if appropriate):
python3 ci/validate_threat_model.py→ "prose, YAML and JSON agree".Types of changes
!in the title)Checklist:
make hookschecks it on commit).docs/accordingly. (the threat model is the documentation)## UnreleasedinCHANGELOG.md. (n/a)Done questions (AGENTS.md)
Generated by Claude Code