[DONE] wml://{security/2016/dsa-3660.wml}
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
- --- english/security/2016/dsa-3660.wml 2016-09-06 09:55:34.000000000 +0500
+++ russian/security/2016/dsa-3660.wml 2016-09-06 11:18:16.411107488 +0500
@@ -1,106 +1,107 @@
- -<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-5147";>CVE-2016-5147</a>
- - <p>A cross-site scripting issue was discovered.</p></li>
+ <p>Ð?Ñ?л обнаÑ?Ñ?жен межÑ?айÑ?овÑ?й Ñ?кÑ?ипÑ?инг.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5148";>CVE-2016-5148</a>
- - <p>Another cross-site scripting issue was discovered.</p></li>
+ <p>Ð?Ñ?л обнаÑ?Ñ?жен еÑ?Ñ? один Ñ?лÑ?Ñ?ай межÑ?айÑ?ового Ñ?кÑ?ипÑ?инга.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5149";>CVE-2016-5149</a>
- - <p>Max Justicz discovered a script injection issue in extension handling.</p></li>
+ <p>Ð?акÑ? ЮÑ?Ñ?иÑ? обнаÑ?Ñ?жил возможноÑ?Ñ?Ñ? инÑ?екÑ?ии Ñ?Ñ?енаÑ?иÑ? в коде Ñ?абоÑ?Ñ? Ñ? Ñ?аÑ?Ñ?иÑ?ениÑ?ми.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5150";>CVE-2016-5150</a>
- - <p>A use-after-free issue was discovered in Blink/Webkit.</p></li>
+ <p>Ð? Blink/Webkit бÑ?ло обнаÑ?Ñ?жено иÑ?полÑ?зование Ñ?казаÑ?елей поÑ?ле оÑ?вобождениÑ? памÑ?Ñ?и.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5151";>CVE-2016-5151</a>
- - <p>A use-after-free issue was discovered in the pdfium library.</p></li>
+ <p>Ð? библиоÑ?еке pdfium бÑ?ло обнаÑ?Ñ?жено иÑ?полÑ?зование Ñ?казаÑ?елей поÑ?ле оÑ?вобождениÑ? памÑ?Ñ?и.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5152";>CVE-2016-5152</a>
- - <p>GiWan Go discovered a heap overflow issue in the pdfium library.</p></li>
+ <p>Ð?иван Ð?о обнаÑ?Ñ?жил пеÑ?еполнение динамиÑ?еÑ?кой памÑ?Ñ?и в библиоÑ?еке pdfium.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5153";>CVE-2016-5153</a>
- - <p>Atte Kettunen discovered a use-after-destruction issue.</p></li>
+ <p>Ð?Ñ?Ñ?е Ð?еÑ?Ñ?Ñ?нен обнаÑ?Ñ?жил иÑ?полÑ?зование обÑ?екÑ?ов поÑ?ле иÑ? Ñ?азÑ?Ñ?Ñ?ениÑ?.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5154";>CVE-2016-5154</a>
- - <p>A heap overflow issue was discovered in the pdfium library.</p></li>
+ <p>Ð? библиоÑ?еке pdfium бÑ?ло обнаÑ?Ñ?жено пеÑ?еполнение динамиÑ?еÑ?кой памÑ?Ñ?и.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5155";>CVE-2016-5155</a>
- - <p>An address bar spoofing issue was discovered.</p></li>
+ <p>Ð?Ñ?л обнаÑ?Ñ?жен Ñ?поÑ?об подделки адÑ?еÑ?ной Ñ?Ñ?Ñ?оки.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5156";>CVE-2016-5156</a>
- - <p>jinmo123 discovered a use-after-free issue.</p></li>
+ <p>jinmo123 обнаÑ?Ñ?жил иÑ?полÑ?зование Ñ?казаÑ?елей поÑ?ле оÑ?вобождениÑ? памÑ?Ñ?и.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5157";>CVE-2016-5157</a>
- - <p>A heap overflow issue was discovered in the pdfium library.</p></li>
+ <p>Ð? библиоÑ?еке pdfium бÑ?ло обнаÑ?Ñ?жено пеÑ?еполнение динамиÑ?еÑ?кой памÑ?Ñ?и.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5158";>CVE-2016-5158</a>
- - <p>GiWan Go discovered a heap overflow issue in the pdfium library.</p></li>
+ <p>Ð?иван Ð?о обнаÑ?Ñ?жил пеÑ?еполнение динамиÑ?еÑ?кой памÑ?Ñ?и в библиоÑ?еке pdfium.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5159";>CVE-2016-5159</a>
- - <p>GiWan Go discovered another heap overflow issue in the pdfium library.</p></li>
+ <p>Ð?иван Ð?о обнаÑ?Ñ?жил еÑ?Ñ? одно пеÑ?еполнение динамиÑ?еÑ?кой памÑ?Ñ?и в библиоÑ?еке pdfium.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5160";>CVE-2016-5160</a>
- - <p>@l33terally discovered an extensions resource bypass.</p></li>
+ <p>@l33terally обнаÑ?Ñ?жил обÑ?од огÑ?аниÑ?ениÑ? Ñ?еÑ?Ñ?Ñ?Ñ?ов Ñ?аÑ?Ñ?иÑ?ений.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5161";>CVE-2016-5161</a>
- - <p>A type confusion issue was discovered.</p></li>
+ <p>Ð?Ñ?ло обнаÑ?Ñ?жено Ñ?меÑ?ение Ñ?ипов.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5162";>CVE-2016-5162</a>
- - <p>Nicolas Golubovic discovered an extensions resource bypass.</p></li>
+ <p>Ð?иколаÑ? Ð?олÑ?бовиÑ? обнаÑ?Ñ?жил обÑ?од огÑ?аниÑ?ениÑ? Ñ?еÑ?Ñ?Ñ?Ñ?ов Ñ?аÑ?Ñ?иÑ?ений.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5163";>CVE-2016-5163</a>
- - <p>Rafay Baloch discovered an address bar spoofing issue.</p></li>
+ <p>РаÑ?ай Ð?алоÑ? обнаÑ?Ñ?жил Ñ?поÑ?об подделки адÑ?еÑ?ной Ñ?Ñ?Ñ?оки.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5164";>CVE-2016-5164</a>
- - <p>A cross-site scripting issue was discovered in the developer tools.</p></li>
+ <p>Ð? инÑ?Ñ?Ñ?Ñ?менÑ?аÑ? Ñ?азÑ?абоÑ?Ñ?ика бÑ?л обнаÑ?Ñ?жен межÑ?айÑ?овÑ?й Ñ?кÑ?ипÑ?инг.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5165";>CVE-2016-5165</a>
- - <p>Gregory Panakkal discovered a script injection issue in the developer
- - tools.</p></li>
+ <p>Ð?Ñ?егоÑ?и Ð?анаккал обнаÑ?Ñ?жил возможноÑ?Ñ?Ñ? ввеÑ?Ñ?и Ñ?Ñ?енаÑ?ий в инÑ?Ñ?Ñ?Ñ?менÑ?аÑ?
+ Ñ?азÑ?абоÑ?Ñ?ика.</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5166";>CVE-2016-5166</a>
- - <p>Gregory Panakkal discovered an issue with the Save Page As feature.</p></li>
+ <p>Ð?Ñ?егоÑ?и Ð?анаккал обнаÑ?Ñ?жил пÑ?облемÑ? Ñ? возможноÑ?Ñ?Ñ?Ñ? Save Page As (СоÑ?Ñ?аниÑ?Ñ? как).</p></li>
<li><a href="https://security-tracker.debian.org/tracker/CVE-2016-5167";>CVE-2016-5167</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 53.0.2785.89-1~deb8u1.</p>
+<p>Ð? Ñ?Ñ?абилÑ?ном вÑ?пÑ?Ñ?ке (jessie) Ñ?Ñ?и пÑ?облемÑ? бÑ?ли иÑ?пÑ?авленÑ? в
+веÑ?Ñ?ии 53.0.2785.89-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 53.0.2785.89-1.</p>
+<p>Ð? неÑ?Ñ?абилÑ?ном вÑ?пÑ?Ñ?ке (sid) Ñ?Ñ?и пÑ?облемÑ? бÑ?ли иÑ?пÑ?авленÑ? в
+веÑ?Ñ?ии 53.0.2785.89-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-----
iQIcBAEBCgAGBQJXzl+rAAoJEF7nbuICFtKlTvMP/ibt09I7fsYsZmBqewSRFxYN
z6UAt8Jb+hJHEzGZC2i3rSiFSK/9Fog6qczjljiW2Kd6Pg12ofyR42mBQVkkMEDu
YsSE/dh4kE5bYjmp7xKL9K55m9WNZpqsicH3Y2G8r3K2cFZN+dFxd6lOA3XoNxMK
pyg84xlzimSrsJS4DV4RYJS7E0z+R4r2vgg0rsNZzMfoZvYAkTpqZd0GGDQLkWUR
D7F1LyDGMp1rY0PO3NrmKcryWTXDOQb46hRMQLtZmZsuCdJ408YxeGntOkeY0Ybt
JdG2u6HcrSB4Gr4cP2xXtl4sqQwEhFTBuL1tQWijOfm0hzc85gRYqfVP6/swbV66
yQcmIKWhqxcfSmKUFA9AUVS6tWiLJfjlE+M+KKQMeU5ywXZiXy2KICVt6aOFW+1W
70BxZnmXoOPyd1Neon8bvN6pJJFrUV56RekLNT85SG7kBSYiyfXmqO2s/N2yJImV
XCbSRza4LF7mJR6V/Ovf4kjN6wHKAllf5Dr9rselb2sV4ipyUhfRx3AitNegaC3d
pqi9Q26sSiExkh/cJxFtp6IWmcjSYQNVSALsdW3h4q0z/tIYeEYNvwxBEae03pSJ
jhGQYDmA+Yaf718/PVwEcraLiYHzBqXC8fnltAXyWLgwMPLtYWfk8GSuBWBFT7Q4
CTsNKniRopZOy1Qy0mVX
=50ZF
-----END PGP SIGNATURE-----
Reply to: