<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apf.git/src, branch master</title>
<subtitle>Active Port Forwarder
</subtitle>
<link rel='alternate' type='text/html' href='https://cgit.hackerposse.com/apf.git/'/>
<entry>
<title>Prepare for v0.8.5 release</title>
<updated>2015-02-17T05:43:54+00:00</updated>
<author>
<name>Joshua Judson Rosen</name>
</author>
<published>2015-02-17T05:43:54+00:00</published>
<link rel='alternate' type='text/html' href='https://cgit.hackerposse.com/apf.git/commit/?id=c0101ba5d78758d30503682935b5b7602269aa93'/>
<id>c0101ba5d78758d30503682935b5b7602269aa93</id>
<content type='text'>
Update version-strings and summarise the changes since v0.8.4 in ChangeLog.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Update version-strings and summarise the changes since v0.8.4 in ChangeLog.
</pre>
</div>
</content>
</entry>
<entry>
<title>Update autotools-generated files</title>
<updated>2015-02-17T05:42:02+00:00</updated>
<author>
<name>Joshua Judson Rosen</name>
</author>
<published>2015-02-17T05:42:02+00:00</published>
<link rel='alternate' type='text/html' href='https://cgit.hackerposse.com/apf.git/commit/?id=b1f97ed484182ecb842a08c422e7b69dd5959ab4'/>
<id>b1f97ed484182ecb842a08c422e7b69dd5959ab4</id>
<content type='text'>
via autoreconf.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
via autoreconf.
</pre>
</div>
</content>
</entry>
<entry>
<title>Remove HTTP proxy support.</title>
<updated>2015-02-17T05:37:08+00:00</updated>
<author>
<name>Joshua Judson Rosen</name>
</author>
<published>2015-02-17T05:37:08+00:00</published>
<link rel='alternate' type='text/html' href='https://cgit.hackerposse.com/apf.git/commit/?id=714aebccbd7a4ab6ec0964d4580efd49171ba140'/>
<id>714aebccbd7a4ab6ec0964d4580efd49171ba140</id>
<content type='text'>
There are plenty of popular, readily-available external tools
that, frankly, provide better options for going through proxies--
both of the HTTP variety and others (corkscrew, httptunnel, socat...);
and dropping our internal implementation results in a significant
reduction in code complexity--including the complete elimination
of multithreading and all of the worries that go along with it.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
There are plenty of popular, readily-available external tools
that, frankly, provide better options for going through proxies--
both of the HTTP variety and others (corkscrew, httptunnel, socat...);
and dropping our internal implementation results in a significant
reduction in code complexity--including the complete elimination
of multithreading and all of the worries that go along with it.
</pre>
</div>
</content>
</entry>
<entry>
<title>Nix mysleep().</title>
<updated>2015-02-17T04:33:02+00:00</updated>
<author>
<name>Joshua Judson Rosen</name>
</author>
<published>2015-02-17T04:33:02+00:00</published>
<link rel='alternate' type='text/html' href='https://cgit.hackerposse.com/apf.git/commit/?id=b3be641eeddce360692d3a3e872d769f86f1b293'/>
<id>b3be641eeddce360692d3a3e872d769f86f1b293</id>
<content type='text'>
Just use sleep() where only whole-second resolution is used
to delay between reconnect-attempts; and nanosleep where
sub-second resolution is used.

sleep() should actually be OK, because we don't intermix those calls
with alarm() or any other signals or itimer functions.

nanosleep() should be OK because POSIX.1-2001 requires
that it not have the crazy signal interactions
that its predecessors are known for.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Just use sleep() where only whole-second resolution is used
to delay between reconnect-attempts; and nanosleep where
sub-second resolution is used.

sleep() should actually be OK, because we don't intermix those calls
with alarm() or any other signals or itimer functions.

nanosleep() should be OK because POSIX.1-2001 requires
that it not have the crazy signal interactions
that its predecessors are known for.
</pre>
</div>
</content>
</entry>
<entry>
<title>afserver: support per-realm CA-certificate settings</title>
<updated>2014-11-19T04:16:55+00:00</updated>
<author>
<name>Joshua Judson Rosen</name>
</author>
<published>2014-11-19T04:16:55+00:00</published>
<link rel='alternate' type='text/html' href='https://cgit.hackerposse.com/apf.git/commit/?id=fe9bda8d2aad33e0f71d5699bcf90fb78b3fb5bb'/>
<id>fe9bda8d2aad33e0f71d5699bcf90fb78b3fb5bb</id>
<content type='text'>
This makes it possible to have different CA certificates for different realms,
or certificate auth for only some realms and password auth for others.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This makes it possible to have different CA certificates for different realms,
or certificate auth for only some realms and password auth for others.
</pre>
</div>
</content>
</entry>
<entry>
<title>Add missing const qualifier on SSL_METHOD* vars.</title>
<updated>2014-11-19T02:10:13+00:00</updated>
<author>
<name>Joshua Judson Rosen</name>
</author>
<published>2014-11-19T02:10:13+00:00</published>
<link rel='alternate' type='text/html' href='https://cgit.hackerposse.com/apf.git/commit/?id=41bf28a5efad5aa5cd47a180c03ea5434fb98ddc'/>
<id>41bf28a5efad5aa5cd47a180c03ea5434fb98ddc</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>afserver: log which protocol version was accepted by SSL_accept.</title>
<updated>2014-10-20T05:18:48+00:00</updated>
<author>
<name>Joshua Judson Rosen</name>
</author>
<published>2014-10-20T05:18:48+00:00</published>
<link rel='alternate' type='text/html' href='https://cgit.hackerposse.com/apf.git/commit/?id=c9d9807956a09e5219366abdad39901786a53718'/>
<id>c9d9807956a09e5219366abdad39901786a53718</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>afclient: make "SERVER SSL" log show which protocol version is in use, if any</title>
<updated>2014-10-20T05:06:15+00:00</updated>
<author>
<name>Joshua Judson Rosen</name>
</author>
<published>2014-10-20T05:06:15+00:00</published>
<link rel='alternate' type='text/html' href='https://cgit.hackerposse.com/apf.git/commit/?id=b0d4313bc85dc8fc1449e52cd63a0a09db89a3ff'/>
<id>b0d4313bc85dc8fc1449e52cd63a0a09db89a3ff</id>
<content type='text'>
(rather than just "yes")
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
(rather than just "yes")
</pre>
</div>
</content>
</entry>
<entry>
<title>afclient: use whatever version of TLS (or better) we can.</title>
<updated>2014-10-20T04:31:21+00:00</updated>
<author>
<name>Joshua Judson Rosen</name>
</author>
<published>2014-10-20T04:31:21+00:00</published>
<link rel='alternate' type='text/html' href='https://cgit.hackerposse.com/apf.git/commit/?id=91a72baa658628354bd7adba45fb6071356898bd'/>
<id>91a72baa658628354bd7adba45fb6071356898bd</id>
<content type='text'>
Refuse to use pre-TLS SSL, since now SSLv3 has been broken by POODLE attack.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Refuse to use pre-TLS SSL, since now SSLv3 has been broken by POODLE attack.
</pre>
</div>
</content>
</entry>
<entry>
<title>afserver: avoid requiring a specific SSL protocol version</title>
<updated>2014-10-20T04:31:09+00:00</updated>
<author>
<name>Joshua Judson Rosen</name>
</author>
<published>2014-10-20T04:31:09+00:00</published>
<link rel='alternate' type='text/html' href='https://cgit.hackerposse.com/apf.git/commit/?id=fc04c7ac1f50aa5c147af5c0f8cd4a68b9e37990'/>
<id>fc04c7ac1f50aa5c147af5c0f8cd4a68b9e37990</id>
<content type='text'>
Trust the clients to negotiate the latest/best protocol version they can.

This should generally improve security over time (as OpenSSL improves
and implements improved protocols) without having the APF codebase
or server/client deployments need to chase latest OpenSSL API additions,
causing portability problems, or breaking client deployments that
are hard to upgrade.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Trust the clients to negotiate the latest/best protocol version they can.

This should generally improve security over time (as OpenSSL improves
and implements improved protocols) without having the APF codebase
or server/client deployments need to chase latest OpenSSL API additions,
causing portability problems, or breaking client deployments that
are hard to upgrade.
</pre>
</div>
</content>
</entry>
</feed>
