Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #2160

Closed (moved)
Open
Opened Nov 06, 2010 by Mike Perry@mikeperry

Document rule review process

We need to publicly document our rule review process in the rule development howto. The document should be written to be read by rule authors as well as rule set administrators/reviewers. It should describe both common pitfalls in rule authorship, as well as potential vectors for malicious rules, and examples of each.

To motivate this, it should also briefly define an adversary model. As far as I am aware, the two classes of adversaries we face are network adversaries that exploit poorly written existing rules, and rule author adversaries that try to subtly smuggle malicious rewrite rules into rulesets for purposes of MITM/phishing.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#2160