[krbdev.mit.edu #7929] git commit

[Greg Hudson via RT]

HTTPS transport (Microsoft KKDCPP implementation)

Add an 'HTTPS' transport type which connects to an [MS-KKDCP] proxy
server using HTTPS to communicate with a KDC.  The KDC's name should
take the form of an HTTPS URL (e.g. "https://proxybox/KdcProxy").

An HTTPS connection's encryption layer can be reading and writing when
the application layer is expecting to write and read, so the HTTPS
callbacks have to handle being called multiple times.

[nalin at redhat.com: use cleanup labels, make sure we always send the
 realm name, keep a copy of the URI on-hand, move most of the
 conditionally-compiled sections into their own conditionally-built
 functions, break out HTTPS request formatting into a helper function,
 handle the MS-KKDCP length bytes, update comments to mention specific
 versions of the MS-KKDCP spec, differentiate TCP and HTTP trace
 messages, trace unparseable responses]

https://github.com/krb5/krb5/commit/d950809ff49e3e7603594186d77135a09ab6b1b2
Author: Nalin Dahyabhai <nalin at dahyabhai.net>
Committer: Greg Hudson <ghudson at mit.edu>
Commit: d950809ff49e3e7603594186d77135a09ab6b1b2
Branch: master
 src/include/k5-trace.h         |   13 ++
 src/lib/krb5/os/locate_kdc.c   |   63 ++++++-
 src/lib/krb5/os/os-proto.h     |    2 +
 src/lib/krb5/os/sendto_kdc.c   |  417 ++++++++++++++++++++++++++++++++++++++--
 src/lib/krb5/os/t_locate_kdc.c |    2 +
 src/lib/krb5/os/trace.c        |    2 +
 6 files changed, 471 insertions(+), 28 deletions(-)