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

[DONE] wml://security/2017/dsa-406{3,4}.wml

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

- --- english/security/2017/dsa-4063.wml	2017-12-12 10:43:57.000000000 +0500
+++ russian/security/2017/dsa-4063.wml	2017-12-12 23:01:28.785668085 +0500
@@ -1,18 +1,19 @@
- -<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>Toshifumi Sakaguchi discovered that PowerDNS Recursor, a high-performance
- -resolving name server was susceptible to denial of service via a crafted
- -CNAME answer.</p>
+<p>ТоÑ?иÑ?Ñ?ми СакагÑ?Ñ?и обнаÑ?Ñ?жил, Ñ?Ñ?о PowerDNS Recursor, вÑ?Ñ?окопÑ?оизводиÑ?елÑ?нÑ?й
+Ñ?еÑ?веÑ? Ñ?азÑ?еÑ?ениÑ? имÑ?н, подвеÑ?жен оÑ?казÑ? в обÑ?лÑ?живании из-за Ñ?пеÑ?иалÑ?но Ñ?Ñ?оÑ?миÑ?ованного
+оÑ?веÑ?а CNAME.</p>
 
- -<p>The oldstable distribution (jessie) is not affected.</p>
+<p>Ð?Ñ?едÑ?дÑ?Ñ?ий Ñ?Ñ?абилÑ?нÑ?й вÑ?пÑ?Ñ?к (jessie) не подвеÑ?жен данной пÑ?облеме.</p>
 
- -<p>For the stable distribution (stretch), this problem has been fixed in
- -version 4.0.4-1+deb9u3.</p>
+<p>Ð? Ñ?Ñ?абилÑ?ном вÑ?пÑ?Ñ?ке (stretch) Ñ?Ñ?а пÑ?обема бÑ?ла иÑ?пÑ?авлена в
+веÑ?Ñ?ии 4.0.4-1+deb9u3.</p>
 
- -<p>We recommend that you upgrade your pdns-recursor packages.</p>
+<p>РекомендÑ?еÑ?Ñ?Ñ? обновиÑ?Ñ? пакеÑ?Ñ? pdns-recursor.</p>
 
- -<p>For the detailed security status of pdns-recursor please refer to
- -its security tracker page at:
+<p>С подÑ?обнÑ?м Ñ?Ñ?аÑ?Ñ?Ñ?ом поддеÑ?жки безопаÑ?ноÑ?Ñ?и pdns-recursor можно ознакомиÑ?Ñ?Ñ?Ñ? на
+Ñ?ооÑ?веÑ?Ñ?Ñ?вÑ?Ñ?Ñ?ей Ñ?Ñ?Ñ?аниÑ?е оÑ?Ñ?леживаниÑ? безопаÑ?ноÑ?Ñ?и по адÑ?еÑ?Ñ?
 <a href="https://security-tracker.debian.org/tracker/pdns-recursor";>\
 https://security-tracker.debian.org/tracker/pdns-recursor</a></p>
 </define-tag>
- --- english/security/2017/dsa-4064.wml	2017-12-12 16:37:40.000000000 +0500
+++ russian/security/2017/dsa-4064.wml	2017-12-12 23:09:56.245267917 +0500
@@ -1,88 +1,89 @@
- -<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-2017-15407";>CVE-2017-15407</a>
 
- -    <p>Ned Williamson discovered an out-of-bounds write issue.</p></li>
+    <p>Ð?ед УилÑ?Ñ?мÑ?он обнаÑ?Ñ?жил запиÑ?Ñ? за пÑ?еделами вÑ?деленного бÑ?Ñ?еÑ?а памÑ?Ñ?и.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2017-15408";>CVE-2017-15408</a>
 
- -    <p>Ke Liu 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-2017-15409";>CVE-2017-15409</a>
 
- -    <p>An out-of-bounds write issue was discovered in the skia library.</p></li>
+    <p>Ð? библиоÑ?еке skia бÑ?ла обнаÑ?Ñ?жена запиÑ?Ñ? за пÑ?еделами вÑ?деленного бÑ?Ñ?еÑ?а памÑ?Ñ?и.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2017-15410";>CVE-2017-15410</a>
 
- -    <p>Luat Nguyen discovered a use-after-free issue in the pdfium library.</p></li>
+    <p>Ð?Ñ?аÑ? Ð?гÑ?ен обнаÑ?Ñ?жил иÑ?полÑ?зование Ñ?казаÑ?елей поÑ?ле оÑ?вобождениÑ? памÑ?Ñ?и в библиоÑ?еке pdfium.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2017-15411";>CVE-2017-15411</a>
 
- -    <p>Luat Nguyen discovered a use-after-free issue in the pdfium library.</p></li>
+    <p>Ð?Ñ?аÑ? Ð?гÑ?ен обнаÑ?Ñ?жил иÑ?полÑ?зование Ñ?казаÑ?елей поÑ?ле оÑ?вобождениÑ? памÑ?Ñ?и в библиоÑ?еке pdfium.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2017-15413";>CVE-2017-15413</a>
 
- -    <p>Gaurav Dewan discovered a type confusion issue.</p></li>
+    <p>Ð?аÑ?Ñ?ав Ð?еван обнаÑ?Ñ?жил Ñ?меÑ?ение Ñ?ипов.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2017-15415";>CVE-2017-15415</a>
 
- -    <p>Viktor Brange discovered an information disclosure issue.</p></li>
+    <p>Ð?икÑ?оÑ? Ð?Ñ?анге обнаÑ?Ñ?жил Ñ?аÑ?кÑ?Ñ?Ñ?ие инÑ?оÑ?маÑ?ии.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2017-15416";>CVE-2017-15416</a>
 
- -    <p>Ned Williamson discovered an out-of-bounds read issue.</p></li>
+    <p>Ð?ед УилÑ?Ñ?мÑ?он обнаÑ?Ñ?жил Ñ?Ñ?ение за пÑ?еделами вÑ?деленного бÑ?Ñ?еÑ?а памÑ?Ñ?и.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2017-15417";>CVE-2017-15417</a>
 
- -    <p>Max May discovered an information disclosure issue in the skia
- -    library.</p></li>
+    <p>Ð?акÑ? Ð?Ñ?й обнаÑ?Ñ?жил Ñ?аÑ?кÑ?Ñ?Ñ?ие инÑ?оÑ?маÑ?ии в библиоÑ?еке
+    skia.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2017-15418";>CVE-2017-15418</a>
 
- -    <p>Kushal Arvind Shah discovered an uninitialized value in the skia
- -    library.</p></li>
+    <p>Ð?Ñ?Ñ?ал Ð?Ñ?винд ШаÑ? обнаÑ?Ñ?жил неиниÑ?иализиÑ?ованное знаÑ?ение в библиоÑ?еке
+    skia.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2017-15419";>CVE-2017-15419</a>
 
- -    <p>Jun Kokatsu discoved an information disclosure issue.</p></li>
+    <p>Ð?жÑ?н Ð?окаÑ?Ñ?Ñ? обнаÑ?Ñ?жил Ñ?аÑ?кÑ?Ñ?Ñ?ие инÑ?оÑ?маÑ?ии.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2017-15420";>CVE-2017-15420</a>
 
- -    <p>WenXu Wu discovered a URL spoofing issue.</p></li>
+    <p>Ð?Ñ?нÑ?СÑ?й Ð?Ñ? обнаÑ?Ñ?жил подделкÑ? URL.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2017-15423";>CVE-2017-15423</a>
 
- -    <p>Greg Hudson discovered an issue in the boringssl library.</p></li>
+    <p>Ð?Ñ?ег ХадÑ?он обнаÑ?Ñ?жил пÑ?облемÑ? в библиоÑ?еке boringssl.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2017-15424";>CVE-2017-15424</a>
 
- -    <p>Khalil Zhani discovered a URL spoofing issue.</p></li>
+    <p>Халил Ð?ани обнаÑ?Ñ?жил подделкÑ? URL.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2017-15425";>CVE-2017-15425</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-2017-15426";>CVE-2017-15426</a>
 
- -    <p>WenXu Wu discovered a URL spoofing issue.</p></li>
+    <p>Ð?Ñ?нÑ?СÑ?й Ð?Ñ? обнаÑ?Ñ?жил подделкÑ? URL.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2017-15427";>CVE-2017-15427</a>
 
- -    <p>Junaid Farhan discovered an issue with the omnibox.</p></li>
+    <p>Ð?жÑ?наид ФаÑ?Ñ?ан обнаÑ?Ñ?жил пÑ?облемÑ? Ñ? omnibox.</p></li>
 
 </ul>
 
- -<p>For the stable distribution (stretch), these problems have been fixed in
- -version 63.0.3239.84-1~deb9u1.</p>
+<p>Ð? Ñ?Ñ?абилÑ?ном вÑ?пÑ?Ñ?ке (stretch) Ñ?Ñ?и пÑ?облемÑ? бÑ?ли иÑ?пÑ?авленÑ? в
+веÑ?Ñ?ии 63.0.3239.84-1~deb9u1.</p>
 
- -<p>We recommend that you upgrade your chromium-browser packages.</p>
+<p>РекомендÑ?еÑ?Ñ?Ñ? обновиÑ?Ñ? пакеÑ?Ñ? chromium-browser.</p>
 
- -<p>For the detailed security status of chromium-browser please refer to
- -its security tracker page at:
+<p>С подÑ?обнÑ?м Ñ?Ñ?аÑ?Ñ?Ñ?ом поддеÑ?жки безопаÑ?ноÑ?Ñ?и chromium-browser можно ознакомиÑ?Ñ?Ñ?Ñ? на
+Ñ?ооÑ?веÑ?Ñ?Ñ?вÑ?Ñ?Ñ?ей Ñ?Ñ?Ñ?аниÑ?е оÑ?Ñ?леживаниÑ? безопаÑ?ноÑ?Ñ?и по адÑ?еÑ?Ñ?
 <a href="https://security-tracker.debian.org/tracker/chromium-browser";>\
 https://security-tracker.debian.org/tracker/chromium-browser</a></p>
 </define-tag>
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3mumcdV9mwCc9oZQXudu4gIW0qUFAlowG3wACgkQXudu4gIW
0qXIig//Ts48P7TM5ZiK04FVAFQC0dpNPAGsQNDAkouIKhh9k/IOly16i6PhxRz6
iHmbk5NdeJfvmTpvY8KgZRL0ZWi+zONhpiK/ZFYCNNm939UzEvfY8CWAuZ+03k7N
mRfv9ONpyNXbBCUBa7I/kVOF/820qacGCW2KCuessGFvXKbazNBfbLaT0q8HkR6g
/SaT2Ght/BehJR9pv0rYYKStd90ibi34JiKl8yZcadPYNIC5K6ybRlYozHUvkoMs
P4I3Qh3lrwY0zszROF330mnm4BSqtXnFFZF3tatmGOm8I25ABq9UBuh0Q1Cjryvr
gh+HUJvjM6Jg9qs3zko0Q8k1PSLP1yJsDjyc21RTiY1j2DkerSTyb0jlWwdgka28
+gbMJxNCwogFjcNN2tog0JvOANb4W8ZbMYmCaXcimW3sM/k2rnz/MeRewKCzK3iD
gj77F37eL7+TnX3hLOaHd84Eiz9211PGdwhiBxX1UrvYJE9zUBTpuL5Ug7AMgL/2
Ep70pKMChRu5orXpMamIksqUjEpfwIAK4f+Z4xtcI9EGXUlMY+ZUS17MPk2Nmou2
G82HXm7qPGlgl/7JF++uBuPugUqwvGQmbPxBO2zma3xT4i2gDB1BV2iRyNBroOuP
Y5i3PGABE+vfnUa2elYJYF7DWjkGBVMfvonHx0CqqiE535Ljn5c=
=h0Tp
-----END PGP SIGNATURE-----
Reply to: