Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #21470
Closed (moved) (moved)
Open
Created Feb 15, 2017 by teor@teor

Write unit tests for security regressions

When we fix a security vulnerability like the ones in [ https://trac.torproject.org/projects/tor/wiki/TROVE TROVE], we sometimes forget to include a unit test.

Some security vulnerabilities are easy to test, such as parsing errors. We should write tests that fail with the bug, but succeed when it is fixed.

Here's an initial list of security fixes we can write unit tests for:

  • #20894 (moved)
  • #21018 (moved)
  • #21278 (moved) (and #21450 (moved))

Let's open a child ticket of this ticket for each one.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking