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

[DONE] wml://{security/2016/dsa-3637.wml}



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

- --- english/security/2016/dsa-3637.wml	2016-08-01 17:15:17.000000000 +0500
+++ russian/security/2016/dsa-3637.wml	2016-08-01 17:29:03.970596643 +0500
@@ -1,99 +1,100 @@
- -<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 vulnerabilities have been discovered in the chromium web browser.</p>
+<p>Ð? веб-бÑ?аÑ?зеÑ?е chromium бÑ?ло обнаÑ?Ñ?жено неÑ?колÑ?ко Ñ?Ñ?звимоÑ?Ñ?ей.</p>
 
 <ul>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-1704";>CVE-2016-1704</a>
 
- -    <p>The chrome development team found and fixed various issues during
- -    internal auditing.</p></li>
+    <p>Ð?оманда Ñ?азÑ?абоÑ?ки chrome обнаÑ?Ñ?жила и иÑ?пÑ?авила Ñ?азлиÑ?нÑ?е пÑ?облемÑ? в Ñ?оде
+    внÑ?Ñ?Ñ?еннего аÑ?диÑ?а.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-1705";>CVE-2016-1705</a>
 
- -    <p>The chrome development team found and fixed various issues during
- -    internal auditing.</p></li>
+    <p>Ð?оманда Ñ?азÑ?абоÑ?ки chrome обнаÑ?Ñ?жила и иÑ?пÑ?авила Ñ?азлиÑ?нÑ?е пÑ?облемÑ? в Ñ?оде
+    внÑ?Ñ?Ñ?еннего аÑ?диÑ?а.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-1706";>CVE-2016-1706</a>
 
- -    <p>Pinkie Pie discovered a way to escape the Pepper Plugin API sandbox.</p></li>
+    <p>Ð?инки Ð?ай обнаÑ?Ñ?жил Ñ?поÑ?об вÑ?Ñ?ода за пÑ?еделÑ? пеÑ?оÑ?ниÑ?Ñ? Pepper Plugin API.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-1707";>CVE-2016-1707</a>
 
- -    <p>xisigr discovered a URL spoofing issue.</p></li>
+    <p>xisigr обнаÑ?Ñ?жил пÑ?облемÑ? Ñ? подделкой URL.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-1708";>CVE-2016-1708</a>
 
- -    <p>Adam Varsan discovered a use-after-free issue.</p></li>
+    <p>Ð?дам Ð?аÑ?Ñ?ан обнаÑ?Ñ?жил иÑ?полÑ?зование Ñ?казаÑ?елей поÑ?ле оÑ?вобождениÑ? памÑ?Ñ?и.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-1709";>CVE-2016-1709</a>
 
- -    <p>ChenQin a buffer overflow issue in the sfntly library.</p></li>
+    <p>ChenQin обнаÑ?Ñ?жил пеÑ?еполнение бÑ?Ñ?еÑ?а в библиоÑ?еке sfntly.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-1710";>CVE-2016-1710</a>
 
- -    <p>Mariusz Mlynski discovered a same-origin bypass.</p></li>
+    <p>Ð?аÑ?иÑ?Ñ? Ð?линÑ?кий обнаÑ?Ñ?жил возможноÑ?Ñ?Ñ? обÑ?ода пÑ?авила одного иÑ?Ñ?оÑ?ника.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-1711";>CVE-2016-1711</a>
 
- -    <p>Mariusz Mlynski discovered another same-origin bypass.</p></li>
+    <p>Ð?аÑ?иÑ?Ñ? Ð?линÑ?кий обнаÑ?Ñ?жил еÑ?Ñ? один Ñ?поÑ?об обÑ?ода пÑ?авила одного иÑ?Ñ?оÑ?ника.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5127";>CVE-2016-5127</a>
 
- -    <p>cloudfuzzer discovered a use-after-free issue.</p></li>
+    <p>cloudfuzzer обнаÑ?Ñ?жил иÑ?полÑ?зование Ñ?казаÑ?елей поÑ?ле оÑ?вобождениÑ? памÑ?Ñ?и.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5128";>CVE-2016-5128</a>
 
- -    <p>A same-origin bypass issue was discovered in the v8 javascript library.</p></li>
+    <p>Ð? javascript-библиоÑ?еке v8 бÑ?ла обнаÑ?Ñ?жена возможноÑ?Ñ?Ñ? обÑ?ода пÑ?авила одного иÑ?Ñ?оÑ?ника.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5129";>CVE-2016-5129</a>
 
- -    <p>Jeonghoon Shin discovered a memory corruption issue in the v8 javascript
- -    library.</p></li>
+    <p>ЦзÑ?н Шин обнаÑ?Ñ?жил повÑ?еждение Ñ?одеÑ?жимого памÑ?Ñ?и в javascript-библиоÑ?еке
+    v8.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5130";>CVE-2016-5130</a>
 
- -    <p>Widih Matar discovered a URL spoofing issue.</p></li>
+    <p>Ð?идиÑ? Ð?аÑ?аÑ? обнаÑ?Ñ?жил пÑ?облемÑ? Ñ? подделкой URL.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5131";>CVE-2016-5131</a>
 
- -    <p>Nick Wellnhofer discovered a use-after-free issue in the libxml2 library.</p></li>
+    <p>Ð?ик УÑ?лÑ?оÑ?еÑ? обнаÑ?Ñ?жил иÑ?полÑ?зование Ñ?казаÑ?елей поÑ?ле оÑ?вобождениÑ? памÑ?Ñ?и в библиоÑ?еке libxml2.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5132";>CVE-2016-5132</a>
 
- -    <p>Ben Kelly discovered a same-origin bypass.</p></li>
+    <p>Ð?ен Ð?елли обнаÑ?Ñ?жил Ñ?поÑ?об обÑ?ода пÑ?авила одного иÑ?Ñ?оÑ?ника.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5133";>CVE-2016-5133</a>
 
- -    <p>Patch Eudor discovered an issue in proxy authentication.</p></li>
+    <p>Ð?аÑ? Ð?доÑ? обнаÑ?Ñ?жил пÑ?облемÑ? Ñ? аÑ?Ñ?енÑ?иÑ?икаÑ?ией пÑ?окÑ?и.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5134";>CVE-2016-5134</a>
 
- -    <p>Paul Stone discovered an information leak in the Proxy Auto-Config
- -    feature.</p></li>
+    <p>Ð?ол СÑ?оÑ?н обнаÑ?Ñ?жил Ñ?Ñ?еÑ?кÑ? инÑ?оÑ?маÑ?ии в
+    Proxy Auto-Config.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5135";>CVE-2016-5135</a>
 
- -    <p>ShenYeYinJiu discovered a way to bypass the Content Security Policy.</p></li>
+    <p>ShenYeYinJiu обнаÑ?Ñ?жил Ñ?поÑ?об обÑ?ода пÑ?авила безопаÑ?ноÑ?Ñ?и Ñ?одеÑ?жимого.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5136";>CVE-2016-5136</a>
 
- -    <p>Rob Wu discovered a use-after-free issue.</p></li>
+    <p>Роб Ð?Ñ? обнаÑ?Ñ?жил иÑ?полÑ?зование Ñ?казаÑ?елей поÑ?ле оÑ?вобождениÑ? памÑ?Ñ?и.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5137";>CVE-2016-5137</a>
 
- -    <p>Xiaoyin Liu discovered a way to discover whether an HSTS web side had been
- -    visited.</p></li>
+    <p>СÑ?оинÑ? Ð?Ñ? наÑ?Ñ?л Ñ?поÑ?об обнаÑ?Ñ?жениÑ? Ñ?ого, поÑ?еÑ?алаÑ?Ñ? ли Ñ?еÑ?веÑ?наÑ? Ñ?аÑ?Ñ?Ñ?
+    HSTS.</p></li>
 
 </ul>
 
- -<p>For the stable distribution (jessie), these problems have been fixed in
- -version 52.0.2743.82-1~deb8u1.</p>
+<p>Ð? Ñ?Ñ?абилÑ?ном вÑ?пÑ?Ñ?ке (jessie) Ñ?Ñ?и пÑ?облемÑ? бÑ?ли иÑ?пÑ?авленÑ? в
+веÑ?Ñ?ии 52.0.2743.82-1~deb8u1.</p>
 
- -<p>For the testing (stretch) and unstable (sid) distributions, these problems
- -have been fixed in version 52.0.2743.82-1.</p>
+<p>Ð? Ñ?еÑ?Ñ?иÑ?Ñ?емом (stretch) и неÑ?Ñ?абилÑ?ном (sid) вÑ?пÑ?Ñ?каÑ? Ñ?Ñ?и пÑ?облемÑ?
+бÑ?ли иÑ?пÑ?авленÑ? в веÑ?Ñ?ии 52.0.2743.82-1.</p>
 
- -<p>We recommend that you upgrade your chromium-browser packages.</p>
+<p>РекомендÑ?еÑ?Ñ?Ñ? обновиÑ?Ñ? пакеÑ?Ñ? chromium-browser.</p>
 </define-tag>
 
 # do not modify the following line
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXn0CWAAoJEF7nbuICFtKlxzgP/3c/G3Q02U0teaWTwFkF7tl2
mj+YzozRbfCtqKRVnkjzvlt+ON4wpmRrKoxpfOYlTHeswTytUZ9na14DkknI1nJL
C1tkDWttO1o87IuTRMv4bcbsORa3nvlXUb9saRbvTtIX4MdXN7mW+wTiBpaunr2a
PdQQyWR+jZOYQCceDzlHEIgrvXaJMuigQ8RwgfmcwNSAkXuYyj89c4ryMUrTnM5O
FNs9t0zX08tFPjsyZp0SGa7hQzF0OtAFvIO38eFNcua3LLbXtLVnIwq4PwKs3vYO
/HMKaa+dRYrWqb7nmAnDrb4ub5ErFnqjthbttpVuRhggTq46DEmUBf+Wf4DUgMBI
E7iSNT5hLce5WqXRyA4OmaohDkcQngHYnRewVaGye1Y6DB04XojoTZHAZ3SMOxWh
Rroz5xCzXPWHtNcmXuuEPa79O17po/m76lW5x1LCLWJ7YIXxgcr7kHhJLQxI/x7l
tmf0X3YnQ8sstccmtBTAeHsaG8tN5Q8w6s6RYxilLFx3vHojbmJGv8hTj/GdBjhK
FzmCJ6YYI8jjNlZjagJBmYQBSUOfpLI07Wa0yJ81PdRqAHI4OQa/Rl2HQ2m7qqfq
Dmb6jH2ZmqQvqeYa3dizvHHBrfQEalFzK9WdX7cLy8RZgwLf1gEKrXodfs+8nTx+
Gcir2qk3qNOqGF6RvxsK
=PLQ8
-----END PGP SIGNATURE-----


Reply to: