<div dir="ltr"><div>Hello Nginx users,<br><br><font face="arial, sans-serif">Now available: </font><span style="font-family:arial,sans-serif;font-size:13px">Nginx</span><font face="arial, sans-serif"> 1.8.1 for Windows <a href="https://kevinworthington.com/nginxwin181">https://kevinworthington.com/nginxwin181</a> </font><span style="font-family:arial,sans-serif;font-size:13px">(32-bit and 64-bit versions)</span><br style="font-family:arial,sans-serif;font-size:13px">
<br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">These versions are to support legacy <span>users</span> who are already using Cygwin based builds of <span>Nginx</span>. Officially supported native Windows binaries are at </span><a href="http://nginx.org/" style="font-family:arial,sans-serif;font-size:13px" target="_blank"><span>nginx</span>.org</a><span style="font-family:arial,sans-serif;font-size:13px">.</span><br style="font-family:arial,sans-serif;font-size:13px">
<br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">Announcements are also available here:<br>Twitter </span><a href="http://twitter.com/kworthington" style="font-family:arial,sans-serif;font-size:13px" target="_blank">http://twitter.com/kworthington</a><span style="font-family:arial,sans-serif;font-size:13px"></span><br>
</div>Google+ <a href="https://plus.google.com/+KevinWorthington/" target="_blank">https://plus.google.com/+KevinWorthington/</a><br style="font-family:arial,sans-serif;font-size:13px"><div>
<br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">Thank you,</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">Kevin</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">--</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">Kevin Worthington</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">kworthington *@* (gmail] [dot} {com)</span><br style="font-family:arial,sans-serif;font-size:13px"><a href="http://kevinworthington.com/" style="font-family:arial,sans-serif;font-size:13px" target="_blank">http://kevinworthington.com/</a><br style="font-family:arial,sans-serif;font-size:13px">
<a href="http://twitter.com/kworthington" style="font-family:arial,sans-serif;font-size:13px" target="_blank">http://twitter.com/kworthington</a><br><a href="https://plus.google.com/+KevinWorthington/" target="_blank">https://plus.google.com/+KevinWorthington/</a><br>
</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 26, 2016 at 11:31 AM, Maxim Dounin <span dir="ltr"><<a href="mailto:mdounin@mdounin.ru" target="_blank">mdounin@mdounin.ru</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Changes with nginx 1.8.1 26 Jan 2016<br>
<br>
*) Security: invalid pointer dereference might occur during DNS server<br>
response processing if the "resolver" directive was used, allowing an<br>
attacker who is able to forge UDP packets from the DNS server to<br>
cause segmentation fault in a worker process (CVE-2016-0742).<br>
<br>
*) Security: use-after-free condition might occur during CNAME response<br>
processing if the "resolver" directive was used, allowing an attacker<br>
who is able to trigger name resolution to cause segmentation fault in<br>
a worker process, or might have potential other impact<br>
(CVE-2016-0746).<br>
<br>
*) Security: CNAME resolution was insufficiently limited if the<br>
"resolver" directive was used, allowing an attacker who is able to<br>
trigger arbitrary name resolution to cause excessive resource<br>
consumption in worker processes (CVE-2016-0747).<br>
<br>
*) Bugfix: the "proxy_protocol" parameter of the "listen" directive did<br>
not work if not specified in the first "listen" directive for a<br>
listen socket.<br>
<br>
*) Bugfix: nginx might fail to start on some old Linux variants; the bug<br>
had appeared in 1.7.11.<br>
<br>
*) Bugfix: a segmentation fault might occur in a worker process if the<br>
"try_files" and "alias" directives were used inside a location given<br>
by a regular expression; the bug had appeared in 1.7.1.<br>
<br>
*) Bugfix: the "try_files" directive inside a nested location given by a<br>
regular expression worked incorrectly if the "alias" directive was<br>
used in the outer location.<br>
<br>
*) Bugfix: "header already sent" alerts might appear in logs when using<br>
cache; the bug had appeared in 1.7.5.<br>
<br>
*) Bugfix: a segmentation fault might occur in a worker process if<br>
different ssl_session_cache settings were used in different virtual<br>
servers.<br>
<br>
*) Bugfix: the "expires" directive might not work when using variables.<br>
<br>
*) Bugfix: if nginx was built with the ngx_http_spdy_module it was<br>
possible to use the SPDY protocol even if the "spdy" parameter of the<br>
"listen" directive was not specified.<br>
<span><font color="#888888"><br>
<br>
--<br>
Maxim Dounin<br>
<a href="http://nginx.org/" rel="noreferrer" target="_blank">http://nginx.org/</a><br>
<br>
_______________________________________________<br>
nginx-announce mailing list<br>
<a href="mailto:nginx-announce@nginx.org" target="_blank">nginx-announce@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx-announce" rel="noreferrer" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx-announce</a><br>
</font></span></blockquote></div><br></div></div>