<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <style type="text/css"> /* <![CDATA[ */ @import "branding/css/tigris.css"; @import "branding/css/inst.css"; /* ]]> */</style> <link rel="stylesheet" type="text/css" media="print" href="branding/css/print.css"/> <script type="text/javascript" src="branding/scripts/tigris.js"></script> <title>Subversion Security</title> </head> <body> <div class="app"> <h2>Subversion Security</h2> <p>If you discover a security vulnerability in Subversion, please email this address (which is not hosted at tigris.org due to the need for complete privacy):</p> <!-- See http://www.cdt.org/speech/spam/030319spamreport.shtml for evidence that this has some effect. --> <blockquote> <p><strong><span>s</span><span>v</span><span>n</span><span>s</span><span>e</span><span>c</span><span>u</span><span>r</span><span>i</span><span>t</span><span>y</span><span> </span><span>{</span><span>@</span><span>}</span><span> </span><span>r</span><span>e</span><span>d</span><span>-</span><span>b</span><span>e</span><span>a</span><span>n</span><span>.</span><span>c</span><span>o</span><span>m</span></strong></p> </blockquote> <p>(Take off the spaces and curly braces, of course.)</p> <p>It is safe to send sensitive reports to this address: list membership is controlled, and the archives are not publicly accessible. We will analyze your report and take appropriate action. Our usual procedure is to</p> <ol> <li>Make a fix for the vulnerability.</li> <li>Discreetly distribute the fix to a few large sites that run Subversion servers and are trusted to be discreet themselves.</li> <li>Release a new version of Subversion (containing just that fix) and publicly announce the vulnerability on the same day.</li> </ol> <p>This procedure may vary depending on the nature of the vulnerability and the degree of pre-existing public awareness, of course.</p> <p><span style="color: red"><i>Please do not reproduce the above email address on other web pages or in public postings.</i></span> Due to the need for responsiveness, the security list is unmoderated, which makes it particularly vulnerable to spammers. We want to avoid changing the list address, because it's good to have a consistent, dependable place to report security holes.</p> <p>On this page, the address has been encoded in various ways to reduce the likelihood of a spam harvester noticing it. But if the address starts appearing in other places on the Internet, then the harvesters will inevitably pick it up, and we'll be stuck wading through ever-increasing amounts of spam, trying not to lose important vulnerability reports in the noise.</p> </div> </body> </html>