Author: amc
Date: Tue Dec 16 16:25:24 2014
New Revision: 1645997
URL: http://svn.apache.org/r1645997
Log:
Traffic Server 5.1.2 release updates.
Modified:
trafficserver/site/trunk/content/downloads.en.mdtext
trafficserver/site/trunk/content/index.html
Modified: trafficserver/site/trunk/content/downloads.en.mdtext
URL:
http://svn.apache.org/viewvc/trafficserver/site/trunk/content/downloads.en.mdtext?rev=1645997&r1=1645996&r2=1645997&view=diff
==============================================================================
--- trafficserver/site/trunk/content/downloads.en.mdtext (original)
+++ trafficserver/site/trunk/content/downloads.en.mdtext Tue Dec 16 16:25:24
2014
@@ -30,18 +30,18 @@ compatible signature. You can also
and checksum signatures.
-# Current v5.x Release -- 5.1.1 # {#5.1.1}
+# Current v5.x Release -- 5.1.2 # {#5.1.2}
- Apache Traffic Server 5.1.1 was released on October 31, 2014.
-
[[`PGP`](http://www.apache.org/dist/trafficserver/trafficserver-5.1.1.tar.bz2.asc)]
-
[[`MD5`](http://www.apache.org/dist/trafficserver/trafficserver-5.1.1.tar.bz2.md5)]
-
[[`SHA1`](http://www.apache.org/dist/trafficserver/trafficserver-5.1.1.tar.bz2.sha1)]
+ Apache Traffic Server 5.1.1 was released on December 16, 2014.
+
[[`PGP`](http://www.apache.org/dist/trafficserver/trafficserver-5.1.2.tar.bz2.asc)]
+
[[`MD5`](http://www.apache.org/dist/trafficserver/trafficserver-5.1.2.tar.bz2.md5)]
+
[[`SHA1`](http://www.apache.org/dist/trafficserver/trafficserver-5.1.2.tar.bz2.sha1)]
- <a
href="http://www.apache.org/dyn/closer.cgi/trafficserver/trafficserver-5.1.1.tar.bz2";
class="download_ts">Traffic Server 5.1.1</a>
+ <a
href="http://www.apache.org/dyn/closer.cgi/trafficserver/trafficserver-5.1.2.tar.bz2";
class="download_ts">Traffic Server 5.1.2</a>
-v5.1.1 is an incremental release over 5.0.1.
+v5.1.2 is an incremental release over 5.0.1.
-More details are also in the [CHANGES
log](https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;a=blob_plain;f=CHANGES;hb=refs/tags/5.1.1)
and the the Jira [Release
Notes](https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12327088&styleName=Html&projectId=12310963&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7Cfb6e85a9e82c27f61df95aadd1538645809197e9%7Clin)
+More details are also in the [CHANGES
log](https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12327089&styleName=Html&projectId=12310963&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7Ccf4a4c531a5e9f61e2695735edb0fc97d615481d%7Clin)
# Current v4.x Release (Long Term Support) -- 4.2.2 # {#4.2.2}
Modified: trafficserver/site/trunk/content/index.html
URL:
http://svn.apache.org/viewvc/trafficserver/site/trunk/content/index.html?rev=1645997&r1=1645996&r2=1645997&view=diff
==============================================================================
--- trafficserver/site/trunk/content/index.html (original)
+++ trafficserver/site/trunk/content/index.html Tue Dec 16 16:25:24 2014
@@ -67,12 +67,13 @@
<P>
All versions of Traffic Server prior to v5.0.1 (or v4.2.1.1) have a
vulnerability related to
the synthetic health checks as used by traffic_cop. We urge everyone
- to upgrade to the latest releases, either v4.2.1.1 or v5.1.1. See
+ to upgrade to the latest releases, either v4.2.1.1 or v5.1.2. See
CVE-2014-3525 for some details.
</P>
<p>
Traffic Server 5.1.0 has a security issue that can lead to acting as
an open relay under specific circumstances.
- We urge all deployments of 5.1.0 to upgrade to 5.1.1. See
CVE-2014-3624 and TS-2677 for more detail.
+ Traffic Server 5.1.1 has a security issue which makes it vulnerable
to denial of service attacks.
+ We urge all deployments of 5.1.0 and 5.1.1 to upgrade to 5.1.2. See
CVE-2014-3624 and TS-2677 for more detail.
</p>
</div>
</div>
@@ -266,6 +267,7 @@
<div class="twelvecol">
<div id="blurbbox">
<ul>
+ <li><b>December 16, 2014</b>5.1.2 is a security update for 5.1.1. We
urge everyone to upgrade from 5.1.0 or 5.1.1 to 5.1.2 as soon as possible.</li>
<li><b>October 31, 2014:</b>5.1.1 is a security update for 5.1.0. We
urge everyone to upgrade from 5.1.0 to 5.1.1 as soon as possible. See
CVE-2014-3566 and CVE-2014-3624.</li>
