#20383: Create a Tor-specific vulnerabilty enumeration scheme ------------------------------+-------------------------------- Reporter: nickm | Owner: Type: defect | Status: new Priority: Medium | Milestone: Tor: 0.2.9.x-final Component: Core Tor/Tor | Version: Severity: Normal | Keywords: Actual Points: | Parent ID: Points: | Reviewer: Sponsor: | ------------------------------+-------------------------------- We've been bad at reliably getting CVE numbers for stuff, but it's still useful for packages to have a "this security issue got fixed by that thing" cross reference. So let's make our own. We can even match them up to bug numbers and CVE numbers if we want: they aren't mutually exclusive.
Right now I like TROVE: Tor Registry Of Vulnerabilities and Exposures . Any objection? If not, I am allocating TROVE-2016-001. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20383> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs