Pull request comments, #1

Attempt to address comments from the old pull request, #31.
Always include the realm name in MS-KKDCP requests

Always pass a realm name to set_conn_state_msg_length(), to ensure that
we include the not-actually-optional target-domain field if we're using
MS-KKDCP.
Don't check the kpasswd server's reply address

Don't check the address of the kpasswd server when parsing the reply we
received from it.  This test breaks when we're sending password changes
over HTTP, and most likely under NAT, too.
Differentiate HTTPS and TCP in trace messages

We were previously using trace messages which mentioned "TCP"
specifically, when notionally we were using HTTPS.  It became confusing
for me.
Fix overflow in the HTTPS reply receipt buffer

Fix a buffer overrun bug which could have caused us to zero a byte after
the end of the buffer in which we expected to store an HTTPS reply.  The
buffer's larger than it probably needs to be, so this was always
unlikely.
Add http_anchors, _revoke, and _hostname settings

Add http_anchors, http_revoke, http_hostname and
http_require_crl_checking settings, mimicking both the locations and
effects of their similarly-named PKINIT counterparts, but affecting
HTTPS connections to KDC proxy servers.

The hostname checking currently assumes UTF-8 everywhere.
Check for strtoul() correctly

When parsing port numbers, the intent was to use strtol() when
available, but the test for its availability wasn't being made.
Add a simple KDC proxy test server

This proxy server uses python-paste to run the kdcproxy from
https://pypi.python.org/pypi/kdcproxy.  It should be used along
with the proxy.pem certificate in ../tests/dejagnu/proxy-certs.
Add tests for MS-KKDCP client support

Exercise the MS-KKDCP client support using the test proxy server.