[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[DONE] wml://security/2016/dsa-362{4,5}.wml



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

- --- english/security/2016/dsa-3624.wml	2016-07-22 00:44:09.000000000 +0500
+++ russian/security/2016/dsa-3624.wml	2016-07-23 14:39:44.695470272 +0500
@@ -1,9 +1,10 @@
- -<define-tag description>security update</define-tag>
+#use wml::debian::translation-check translation="1.1" maintainer="Lev Lamberov"
+<define-tag description>обновление безопаÑ?ноÑ?Ñ?и</define-tag>
 <define-tag moreinfo>
- -<p>Several issues have been discovered in the MySQL database server. The
- -vulnerabilities are addressed by upgrading MySQL to the new upstream
- -version 5.5.50. Please see the MySQL 5.5 Release Notes and Oracle's
- -Critical Patch Update advisory for further details:</p>
+<p>Ð? Ñ?еÑ?веÑ?е баз даннÑ?Ñ? MySQL бÑ?ло обнаÑ?Ñ?жено неÑ?колÑ?ко Ñ?Ñ?звимоÑ?Ñ?ей. ЭÑ?и
+Ñ?Ñ?звимоÑ?Ñ?и бÑ?ли иÑ?пÑ?авленÑ? пÑ?Ñ?Ñ?м обновлениÑ? MySQL до новой веÑ?Ñ?ии из оÑ?новной
+веÑ?ки Ñ?азÑ?абоÑ?ки, 5.5.50. Ð?одÑ?обноÑ?Ñ?и Ñ?моÑ?Ñ?иÑ?е в инÑ?оÑ?маÑ?ии о вÑ?пÑ?Ñ?ке MySQL 5.5 и Ñ?екомендаÑ?ии
+по кÑ?иÑ?иÑ?еÑ?ким обновлениÑ?м Oracle:</p>
 
 <ul>
 <li><a href="https://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-50.html";>\
@@ -12,10 +13,10 @@
 http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html</a></li>
 </ul>
 
- -<p>For the stable distribution (jessie), these problems have been fixed in
- -version 5.5.50-0+deb8u1.</p>
+<p>Ð? Ñ?Ñ?абилÑ?ном вÑ?пÑ?Ñ?ке (jessie) Ñ?Ñ?и пÑ?облемÑ? бÑ?ли иÑ?пÑ?авленÑ? в
+веÑ?Ñ?ии 5.5.50-0+deb8u1.</p>
 
- -<p>We recommend that you upgrade your mysql-5.5 packages.</p>
+<p>РекомендÑ?еÑ?Ñ?Ñ? обновиÑ?Ñ? пакеÑ?Ñ? mysql-5.5.</p>
 </define-tag>
 
 # do not modify the following line
- --- english/security/2016/dsa-3625.wml	2016-07-22 17:05:32.000000000 +0500
+++ russian/security/2016/dsa-3625.wml	2016-07-23 14:49:36.448473159 +0500
@@ -1,52 +1,53 @@
- -<define-tag description>security update</define-tag>
+#use wml::debian::translation-check translation="1.1" maintainer="Lev Lamberov"
+<define-tag description>обновление безопаÑ?ноÑ?Ñ?и</define-tag>
 <define-tag moreinfo>
- -<p>Several security issues have been discovered in the Squid caching proxy.</p>
+<p>Ð? Squid, кеÑ?иÑ?Ñ?Ñ?Ñ?ем пÑ?окÑ?и, бÑ?ло обнаÑ?Ñ?жено неÑ?колÑ?ко Ñ?Ñ?звимоÑ?Ñ?ей.</p>
 
 <ul>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-4051";>CVE-2016-4051</a>:
 
- -    <p>CESG and Yuriy M. Kaminskiy discovered that Squid cachemgr.cgi was
- -    vulnerable to a buffer overflow when processing remotely supplied
- -    inputs relayed through Squid.</p></li>
+    <p>СоÑ?Ñ?Ñ?дники CESG и ЮÑ?ий Ð?аминÑ?кий обнаÑ?Ñ?жили, Ñ?Ñ?о Ñ?Ñ?енаÑ?ий cachemgr.cgi в Squid
+    Ñ?Ñ?звим к пеÑ?еполнениÑ? бÑ?Ñ?еÑ?а пÑ?и обÑ?абоÑ?ке пеÑ?еданнÑ?Ñ? Ñ?далÑ?нно
+    вÑ?однÑ?Ñ? даннÑ?Ñ?, пеÑ?еÑ?Ñ?лаемÑ?Ñ? Ñ?еÑ?ез Squid.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-4052";>CVE-2016-4052</a>:
 
- -    <p>CESG discovered that a buffer overflow made Squid vulnerable to a
- -    Denial of Service (DoS) attack when processing ESI responses.</p></li>
+    <p>СоÑ?Ñ?Ñ?дники CESG обнаÑ?Ñ?жили, Ñ?Ñ?о пеÑ?еполнение бÑ?Ñ?еÑ?а делаеÑ? Squid Ñ?Ñ?звимÑ?м к
+    оÑ?казÑ? в обÑ?лÑ?живании (DoS) пÑ?и обÑ?абоÑ?ке ESI-оÑ?веÑ?ов.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-4053";>CVE-2016-4053</a>:
 
- -    <p>CESG found that Squid was vulnerable to public information
- -    disclosure of the server stack layout when processing ESI responses.</p></li>
+    <p>СоÑ?Ñ?Ñ?дники CESG обнаÑ?Ñ?жили, Ñ?Ñ?о Squid Ñ?Ñ?звим к пÑ?блиÑ?номÑ? Ñ?аÑ?кÑ?Ñ?Ñ?иÑ?
+    инÑ?оÑ?маÑ?ии о Ñ?опологии Ñ?еÑ?веÑ?ного Ñ?Ñ?ека пÑ?и обÑ?абоÑ?ке ESI-оÑ?веÑ?ов.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-4054";>CVE-2016-4054</a>:
 
- -    <p>CESG discovered that Squid was vulnerable to remote code execution
- -    when processing ESI responses.</p></li>
+    <p>СоÑ?Ñ?Ñ?дники CESG обнаÑ?Ñ?жили, Ñ?Ñ?о Squid Ñ?Ñ?звим к Ñ?далÑ?нномÑ? вÑ?полнениÑ? кода
+    пÑ?и обÑ?абоÑ?ке ESI-оÑ?веÑ?ов.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-4554";>CVE-2016-4554</a>:
 
- -    <p>Jianjun Chen found that Squid was vulnerable to a header smuggling
- -    attack that could lead to cache poisoning and to bypass of
- -    same-origin security policy in Squid and some client browsers.</p></li>
+    <p>ЦзÑ?нÑ?зÑ?нÑ? ЧÑ?нÑ? обнаÑ?Ñ?жил, Ñ?Ñ?о Squid Ñ?Ñ?звим к подделке заголовка,
+    Ñ?Ñ?о пÑ?иводиÑ? к оÑ?Ñ?авлениÑ? кеÑ?а и обÑ?одÑ?
+    пÑ?авила одного иÑ?Ñ?оÑ?ника в Squid и некоÑ?оÑ?Ñ?Ñ? клиенÑ?Ñ?киÑ? бÑ?аÑ?зеÑ?аÑ?.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-4555";>CVE-2016-4555</a>,
     <a href="https://security-tracker.debian.org/tracker/CVE-2016-4556";>CVE-2016-4556</a>:
 
- -    <p>"bfek-18" and "@vftable" found that Squid was vulnerable to a Denial
- -    of Service (DoS) attack when processing ESI responses, due to
- -    incorrect pointer handling and reference counting.</p></li>
+    <p>"bfek-18" и "@vftable" обнаÑ?Ñ?жили, Ñ?Ñ?о Squid Ñ?Ñ?звим к оÑ?казÑ? в
+    обÑ?лÑ?живании (DoS) пÑ?и обÑ?абоÑ?ке ESI-оÑ?веÑ?ов из-за
+    некоÑ?Ñ?екÑ?ной обÑ?абоÑ?ки Ñ?казаÑ?елей и подÑ?Ñ?Ñ?Ñ?а Ñ?Ñ?Ñ?лок.</p></li>
 
 </ul>
 
- -<p>For the stable distribution (jessie), these problems have been fixed in
- -version 3.4.8-6+deb8u3.</p>
+<p>Ð? Ñ?Ñ?абилÑ?ном вÑ?пÑ?Ñ?ке (jessie) Ñ?Ñ?и пÑ?облемÑ? бÑ?ли иÑ?пÑ?авленÑ? в
+веÑ?Ñ?ии 3.4.8-6+deb8u3.</p>
 
- -<p>For the testing (stretch) and unstable (sid) distributions, these
- -problems have been fixed in version 3.5.19-1.</p>
+<p>Ð? Ñ?еÑ?Ñ?иÑ?Ñ?емом (stretch) и неÑ?Ñ?абилÑ?ном (sid) вÑ?пÑ?Ñ?каÑ? Ñ?Ñ?и
+пÑ?облемÑ? бÑ?ли иÑ?пÑ?авленÑ? в веÑ?Ñ?ии 3.5.19-1.</p>
 
- -<p>We recommend that you upgrade your squid3 packages.</p>
+<p>РекомендÑ?еÑ?Ñ?Ñ? обновиÑ?Ñ? пакеÑ?Ñ? squid3.</p>
 </define-tag>
 
 # do not modify the following line
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXkz2yAAoJEF7nbuICFtKlOxwP/1UO87ERyF+CMuA9qW9CVS3S
W2hOEQ3m83xg1tN9AYLNA5lPDgG9Gi5XCWGZYXUluVMdYh7gmY6G+BGvwWCxAyyg
AdplPfsEq0Ezoq6MHamr5YhTQCY0aKCz8dhb2iLBtkTfjwcZJJ0uq8s1S9dNpPj3
9SPFWIDJxvgsa1MCE731fvCcwJPjgWhOwMjfHscDyVzh57KdHrFsE11pr9Y2vDS1
UU09fJBwrB8QGydoGAye2d09C+29imiM3RTMxZoQ344/lHAzuXfSPEpd3dBQ3oeC
/BFrHY5yNPvzv00BR9HW0FtqkZGoLkIJBqZ5B/ByMYyxjLOOosSUyD/YLY5cw8g5
dOj8xfP/AlrbSjbVqbVbJpGzKnqRnVt+l9UGw4V80jKGclZ0PvkJxCorNTccO1B2
KJ2iQaLLGJhfBDvbXNxbvO5vsFyWW7l5FUofpa2ld9pYvncUAxfCwnYlLK+lcedi
/3zDj67UICgtstElSVLeJ3D0On/jsIoAzVE+i7zDZP4ndjuzMTJ7SuNhWz9Lq+il
Jf9+diQjkmS3YFz1meVuwiQ0NKpJlh+9yjvnKi8WAZ/hneeL2Q54UBfV3MNK3ol0
V2HiWkJwBWkz++sVE2z16xwfBVcCfQrtBO2kkhoi/ZaXpEHTJKeJ/85rp08R6Swf
90TldBSDLkBnTMUcagqC
=Kfd+
-----END PGP SIGNATURE-----


Reply to: