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

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



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

- --- english/security/2016/dsa-3549.wml	2016-04-15 18:01:20.000000000 +0500
+++ russian/security/2016/dsa-3549.wml	2016-04-15 18:11:46.213062826 +0500
@@ -1,54 +1,55 @@
- -<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-1651";>CVE-2016-1651</a>
 
- -    <p>An out-of-bounds read issue was discovered in the pdfium library.</p></li>
+    <p>Ð?Ñ?ла обнаÑ?Ñ?жена пÑ?облема Ñ? Ñ?Ñ?ением за пÑ?еделами вÑ?деленного бÑ?Ñ?еÑ?а памÑ?Ñ?и в библиоÑ?еке pdfium.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-1652";>CVE-2016-1652</a>
 
- -    <p>A cross-site scripting issue was discovered in extension bindings.</p></li>
+    <p>Ð?Ñ?л обнаÑ?Ñ?жен межÑ?айÑ?овÑ?й Ñ?кÑ?ипÑ?инг в пÑ?ивÑ?зкаÑ? Ñ?аÑ?Ñ?иÑ?ений.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-1653";>CVE-2016-1653</a>
 
- -    <p>Choongwoo Han discovered an out-of-bounds write issue in the v8
- -    javascript library.</p></li>
+    <p>ЧÑ?нгвÑ? ХанÑ? обнаÑ?Ñ?жил пÑ?облемÑ? Ñ? запиÑ?Ñ?Ñ? за пÑ?еделами вÑ?деленного бÑ?Ñ?еÑ?а памÑ?Ñ?и в
+    javascript-библиоÑ?еке v8.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-1654";>CVE-2016-1654</a>
 
- -    <p>Atte Kettunen discovered an uninitialized memory read condition.</p></li>
+    <p>Ð?Ñ?Ñ?е Ð?еÑ?Ñ?Ñ?нен обнаÑ?Ñ?жил Ñ?оÑ?Ñ?оÑ?ние Ñ?Ñ?ениÑ? неиниÑ?иализиÑ?ованной памÑ?Ñ?и.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-1655";>CVE-2016-1655</a>
 
- -    <p>Rob Wu discovered a use-after-free issue related to extensions.</p></li>
+    <p>Роб Ð?Ñ? обнаÑ?Ñ?жил иÑ?полÑ?зование Ñ?казаÑ?елей поÑ?ле оÑ?вобождениÑ? памÑ?Ñ?и, Ñ?вÑ?занное Ñ? Ñ?аÑ?Ñ?иÑ?ениÑ?ми.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-1657";>CVE-2016-1657</a>
 
- -    <p>Luan Herrera discovered a way to spoof URLs.</p></li>
+    <p>Ð?Ñ?ан ХеÑ?Ñ?еÑ?а обнаÑ?Ñ?жил Ñ?поÑ?об подделки URL.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-1658";>CVE-2016-1658</a>
 
- -    <p>Antonio Sanso discovered an information leak related to extensions.</p></li>
+    <p>Ð?нÑ?онио СанÑ?о обнаÑ?Ñ?жил Ñ?Ñ?еÑ?кÑ? инÑ?оÑ?маÑ?ии, Ñ?вÑ?заннÑ?Ñ? Ñ? Ñ?аÑ?Ñ?иÑ?ениÑ?ми.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2016-1659";>CVE-2016-1659</a>
 
- -    <p>The chrome development team found and fixed various issues during
- -    internal auditing.</p></li>
+    <p>Ð?оманда Ñ?азÑ?абоÑ?ки chrome обнаÑ?Ñ?жила и иÑ?пÑ?авила Ñ?азлиÑ?нÑ?е пÑ?облемÑ? в
+    Ñ?оде внÑ?Ñ?Ñ?еннего аÑ?диÑ?а.</p></li>
 
 </ul>
 
- -<p>For the stable distribution (jessie), these problems have been fixed in
- -version 50.0.2661.75-1~deb8u1.</p>
+<p>Ð? Ñ?Ñ?абилÑ?ном вÑ?пÑ?Ñ?ке (jessie) Ñ?Ñ?и пÑ?облемÑ? бÑ?ли иÑ?пÑ?авленÑ? в
+веÑ?Ñ?ии 50.0.2661.75-1~deb8u1.</p>
 
- -<p>For the testing distribution (stretch), these problems will be fixed soon.</p>
+<p>Ð? Ñ?еÑ?Ñ?иÑ?Ñ?емом вÑ?пÑ?Ñ?ке (stretch) Ñ?Ñ?и пÑ?облемÑ? бÑ?дÑ?Ñ? иÑ?пÑ?авленÑ? позже.</p>
 
- -<p>For the unstable distribution (sid), these problems have been fixed in
- -version 50.0.2661.75-1.</p>
+<p>Ð? неÑ?Ñ?абилÑ?ном вÑ?пÑ?Ñ?ке (sid) Ñ?Ñ?и пÑ?облемÑ? бÑ?ли иÑ?пÑ?авленÑ? в
+веÑ?Ñ?ии 50.0.2661.75-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-----

iQIcBAEBCgAGBQJXEOixAAoJEF7nbuICFtKlN2YP/0Ce8togtuAXxOiPd98B9nEw
TZ/Xwm7uNvvKB8aSsR3a38fcJnJ3V0xtZSz3lO4YSRCHhB8kbgVBbpP2FIZTb+UP
czpb4GAt5UnahgR0LiRCkNqujSPV7CUerpV0wEidyO/fiVBEdzckjF5MmpzYBeVn
nPHMp00TFbl70CwGLgFv7Eui6oUZSyOgJVOTXF5dtgjbYdQFRjS+YUZ3tSMilsiF
npSXiXsF3GW7T/kuQtf2eLUKH7W8VR34p+GbOeUpccGRaToPxgZTLX95VnTnA9nN
+TBYszvKOLK1opkcj923anF2izkxi7gxGhhiYSN//afsGOWSgveWYyCpA/hnOh1V
QjJwwyol7XXzJ9a71yBKm95yVWCg4uar2ceiUR9IKjnDBIwgdAjDG9qrFuWd4NR8
epd9rhUZQsgjquJbNgDIlbbSKsAuENTt7xJs+ZfY1Ai/766H/2YV3CMv/l1I53so
c39lvs5QIzPfZCNYojZJYhEVI8mcdc26p3Xa28b1WIJsXSLMknBgbE5KnhjvuBty
Ks23jscwMtgmU/XBdpVjIg4O3epS/vgW9SbY0aFD4i+8Dc3AXmzhH/N0WpdPknew
UPBQ1iNdsjyTgu8kJHVZhzf+U3BRDSEJ5J56lzvpniPLWiQuKL/QWMH37YuoqpR+
5QzWifBwLUqC8ClRgnm4
=3oHc
-----END PGP SIGNATURE-----


Reply to: