<feed xmlns='http://www.w3.org/2005/Atom'>
<title>nginx.git/src/event, branch release-1.7.10</title>
<subtitle>nginx</subtitle>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/'/>
<entry>
<title>SSL: safeguard use of SSL3_FLAGS_NO_RENEGOTIATE_CIPHERS.</title>
<updated>2014-12-17T14:12:50+00:00</updated>
<author>
<name>Lukas Tribus</name>
<email>luky-37@hotmail.com</email>
</author>
<published>2014-12-17T14:12:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=cf9283113151fa4572bfdb639a0934b5a3a052bb'/>
<id>cf9283113151fa4572bfdb639a0934b5a3a052bb</id>
<content type='text'>
The flag was recently removed by BoringSSL.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The flag was recently removed by BoringSSL.
</pre>
</div>
</content>
</entry>
<entry>
<title>SSL: loading certificate keys via ENGINE_load_private_key().</title>
<updated>2014-08-04T07:03:20+00:00</updated>
<author>
<name>Dmitrii Pichulin</name>
<email>unknown</email>
</author>
<published>2014-08-04T07:03:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=cf5013dd3fb2531ca465cae7481ddc4cc16e56c5'/>
<id>cf5013dd3fb2531ca465cae7481ddc4cc16e56c5</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>SSL: logging level of "inappropriate fallback" (ticket #662).</title>
<updated>2014-11-17T13:38:48+00:00</updated>
<author>
<name>Maxim Dounin</name>
<email>mdounin@mdounin.ru</email>
</author>
<published>2014-11-17T13:38:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=1fd4cd0b96dfe5e87c652da93737add073fda34b'/>
<id>1fd4cd0b96dfe5e87c652da93737add073fda34b</id>
<content type='text'>
Patch by Erik Dubbelboer.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Patch by Erik Dubbelboer.
</pre>
</div>
</content>
</entry>
<entry>
<title>Events: introduced cancelable timers.</title>
<updated>2014-08-13T18:45:04+00:00</updated>
<author>
<name>Valentin Bartenev</name>
<email>vbart@nginx.com</email>
</author>
<published>2014-08-13T18:45:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=8b30fb7c9771e24543f7fcc82431a4741f6e9d48'/>
<id>8b30fb7c9771e24543f7fcc82431a4741f6e9d48</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Events: simplified cycle in ngx_event_expire_timers().</title>
<updated>2014-08-25T09:37:06+00:00</updated>
<author>
<name>Valentin Bartenev</name>
<email>vbart@nginx.com</email>
</author>
<published>2014-08-25T09:37:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=16403bc7b1af41433bfcd1bda4db8216b57e0810'/>
<id>16403bc7b1af41433bfcd1bda4db8216b57e0810</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Events: removed broken thread support from event timers.</title>
<updated>2014-08-25T09:34:39+00:00</updated>
<author>
<name>Valentin Bartenev</name>
<email>vbart@nginx.com</email>
</author>
<published>2014-08-25T09:34:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=246152c864a7136cc81abe6d2c5926288748d65c'/>
<id>246152c864a7136cc81abe6d2c5926288748d65c</id>
<content type='text'>
It's mostly dead code.  And the idea of thread support for this task has
been deprecated.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
It's mostly dead code.  And the idea of thread support for this task has
been deprecated.
</pre>
</div>
</content>
</entry>
<entry>
<title>SSL: simplified ssl_password_file error handling.</title>
<updated>2014-10-24T11:28:00+00:00</updated>
<author>
<name>Sergey Kandaurov</name>
<email>pluknet@nginx.com</email>
</author>
<published>2014-10-24T11:28:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=33f55559408f20e88b11fb45535ce6a6127f676e'/>
<id>33f55559408f20e88b11fb45535ce6a6127f676e</id>
<content type='text'>
Instead of collecting a number of the possible SSL_CTX_use_PrivateKey_file()
error codes that becomes more and more difficult with the rising variety of
OpenSSL versions and its derivatives, just continue with the next password.

Multiple passwords in a single ssl_password_file feature was broken after
recent OpenSSL changes (commit 4aac102f75b517bdb56b1bcfd0a856052d559f6e).

Affected OpenSSL releases: 0.9.8zc, 1.0.0o, 1.0.1j and 1.0.2-beta3.

Reported by Piotr Sikora.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Instead of collecting a number of the possible SSL_CTX_use_PrivateKey_file()
error codes that becomes more and more difficult with the rising variety of
OpenSSL versions and its derivatives, just continue with the next password.

Multiple passwords in a single ssl_password_file feature was broken after
recent OpenSSL changes (commit 4aac102f75b517bdb56b1bcfd0a856052d559f6e).

Affected OpenSSL releases: 0.9.8zc, 1.0.0o, 1.0.1j and 1.0.2-beta3.

Reported by Piotr Sikora.
</pre>
</div>
</content>
</entry>
<entry>
<title>Upstream: proxy_limit_rate and friends.</title>
<updated>2014-10-28T09:29:59+00:00</updated>
<author>
<name>Roman Arutyunyan</name>
<email>arut@nginx.com</email>
</author>
<published>2014-10-28T09:29:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=18e4d042b04e1ec09d1b74537541b3bb99a75c3f'/>
<id>18e4d042b04e1ec09d1b74537541b3bb99a75c3f</id>
<content type='text'>
The directives limit the upstream read rate.  For example,
"proxy_limit_rate 42" limits proxy upstream read rate to
42 bytes per second.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The directives limit the upstream read rate.  For example,
"proxy_limit_rate 42" limits proxy upstream read rate to
42 bytes per second.
</pre>
</div>
</content>
</entry>
<entry>
<title>Core: added limit to recv_chain().</title>
<updated>2014-10-28T09:29:58+00:00</updated>
<author>
<name>Roman Arutyunyan</name>
<email>arut@nginx.com</email>
</author>
<published>2014-10-28T09:29:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=0989d63f06376ab9434a6449cd316a3c555167d6'/>
<id>0989d63f06376ab9434a6449cd316a3c555167d6</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Win32: fixed wrong type cast.</title>
<updated>2014-10-11T11:56:35+00:00</updated>
<author>
<name>Kouhei Sutou</name>
<email>kou@cozmixng.org</email>
</author>
<published>2014-10-11T11:56:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=3df66a632a8fae75511b4c96219dd3801f04c737'/>
<id>3df66a632a8fae75511b4c96219dd3801f04c737</id>
<content type='text'>
GetQueuedCompletionStatus() document on MSDN says the
following signature:

    http://msdn.microsoft.com/en-us/library/windows/desktop/aa364986.aspx

    BOOL WINAPI GetQueuedCompletionStatus(
      _In_   HANDLE CompletionPort,
      _Out_  LPDWORD lpNumberOfBytes,
      _Out_  PULONG_PTR lpCompletionKey,
      _Out_  LPOVERLAPPED *lpOverlapped,
      _In_   DWORD dwMilliseconds
    );

In the latest specification, the type of the third argument
(lpCompletionKey) is PULONG_PTR not LPDWORD.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
GetQueuedCompletionStatus() document on MSDN says the
following signature:

    http://msdn.microsoft.com/en-us/library/windows/desktop/aa364986.aspx

    BOOL WINAPI GetQueuedCompletionStatus(
      _In_   HANDLE CompletionPort,
      _Out_  LPDWORD lpNumberOfBytes,
      _Out_  PULONG_PTR lpCompletionKey,
      _Out_  LPOVERLAPPED *lpOverlapped,
      _In_   DWORD dwMilliseconds
    );

In the latest specification, the type of the third argument
(lpCompletionKey) is PULONG_PTR not LPDWORD.
</pre>
</div>
</content>
</entry>
</feed>
