The branch master has been updated
       via  b1e610b11def5706bf71a06c9f403aca0a7333fa (commit)
      from  d1965e911dbe4ef77506e13620506893824599fa (commit)


- Log -----------------------------------------------------------------
commit b1e610b11def5706bf71a06c9f403aca0a7333fa
Author: Mark J. Cox <m...@awe.com>
Date:   Mon Jan 29 15:16:35 2018 +0000

    So we can link directly to severities

-----------------------------------------------------------------------

Summary of changes:
 policies/secpolicy.html | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/policies/secpolicy.html b/policies/secpolicy.html
index 9bca8c2..24b7b25 100644
--- a/policies/secpolicy.html
+++ b/policies/secpolicy.html
@@ -46,7 +46,7 @@
            We use the following severity categories:</p>
 
            <ul>
-              <li><em>CRITICAL Severity.</em>
+              <li><em><a name="critical">CRITICAL</a> Severity.</em>
               This affects common configurations and which are also likely to
               be exploitable. Examples include significant disclosure of the
               contents of server memory (potentially revealing user details),
@@ -59,7 +59,7 @@
               soon as possible.</li>
 
              <li>
-              <em>HIGH Severity.</em>
+              <em><a name="high">HIGH</a> Severity.</em>
               This includes issues that are of a lower risk than critical,
               perhaps due to affecting less common configurations, or which
               are less likely to be exploitable.  These issues will be kept
@@ -69,7 +69,7 @@
               where this is something under our control</li>
               
              <li>
-             <em>MODERATE Severity.</em>
+             <em><a name="moderate">MODERATE</a> Severity.</em>
              This includes issues like crashes in client applications,
              flaws in protocols that are less commonly used (such as DTLS),
              and local flaws.  These will in general be kept private until
@@ -77,7 +77,7 @@
              can roll up several such flaws at one time.</li>
               
              <li>
-             <em>LOW Severity.</em>
+             <em><a name="low">LOW</a> Severity.</em>
              This includes issues such as those that only affect the
              openssl command line utility, unlikely configurations, or hard
              to exploit timing (side channel) attacks.  These will in general
_____
openssl-commits mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-commits

Reply via email to