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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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
  • #13968

Closed (moved)
Open
Opened Dec 15, 2014 by Trac@tracbot

Document a metaproject security policy

Considering the year of heartbleed, shell shock, and POODLE exploits, as well as internal vulnerabilities and high profile attention catchers, a security page might help folks in tricky situations determine if their Tor component is secure. Right now security advisories are published on the blog and there's no formal maintenance window.

As with #13966 (moved) (exploit reporting), it might be useful to study FreeBSD security information and pick out the parts we'd like to apply.

Trac:
Username: michael

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