Although we were doing the right thing with punycode
(as far as I can see) for the IDNA entries, we were
forgetting that the comparisons needed to be case
insensitive (checked the RFCs). Now they are.

Test-Information:
Added unit tests for the three flows that were
modified.

Change-Id: Ib17ae3df66159f38339996580dc85a5d99356274

Test-Information:
Unit tests still pass.

Change-Id: I4e5b63104e482a79a933f337082c579db7bb8cff

The std::endl is now added by ~Log, but only for output to stderr or a
log file.  Calls to the Android logging system or manually set callbacks
will not include the newline in the logging output.

JIRA: SWIFT-430

Test-Information:

Unit tests pass on Debian 9
Checked that running Swift with logging to stderr still had a newline.

Change-Id: I096fdba78a3b8f87db2097951c28c528592183e8

A batching mechanism was added to EventLoop::handleNextEvent, which
caused it to be renamed to handleNextEvents.  The problem with the
batching was that it breaks EventLoop::removeEventsFromOwner: events
already grabbed off the events_ queue for invocation could be removed,
leading to issues in cases where two events were grabbed off the queue
that referred to the same entity, the second event was a timer event,
and the first event caused the timer to be stopped.  The timer event
would in this case be executed, leading to unexpected behaviour or
crashes, as shown by the added unit test.

Test-Information:

Unit tests pass on Debian 9 and macOS 10.14.
Benchmarked the eventloop on Debian and macOS, and did not notice a
performance degradation.
Transferred files using S5B and IBB, and checked there were no UI hangs.
Transfer speed before and after the change are roughly the same.

Change-Id: Ife7312f533e8f0976c2e8077d16e0b63fbac6eb1

This gets rid of std::auto_ptr usage and its deprecation
warnings.

Test-Information:

Builds and tests pass on macOS.

Change-Id: I299a0a8d9aa2ead15c933e83a2e3e53f84a4f5b7

clang-trunk complained about them and ideally Swift would
build without warnings.

Test-Information:

Builds find and tests pass.

Change-Id: I1896befef0e65a980cc22f402e126aec8b56e71f

This is needed on macOS so that the running compiler
knows what SDK to build against.

Test-Information:

Builds with system and custom build clang on macOS
10.14.6.

Change-Id: I80a76937834d681c322bf36bfcb034565be9b2f5

All logging in OpenSSLContext is now at debug level.

Test-Information:

Unit tests pass.

Change-Id: I44d01ff23a05676a26ec547d6454dcb6883ebd88

When parsing a PEM string containing a chain of
certificates, createCertificateChain calls
PEM_read_bio_X509 until it returns NULL (end of chain). But
this will have set OpenSSL's internal error chain. Creating
a new OpenSSL context has the side effect of clearing this chain,
but if you are using a context which has already been created,
the context sees that the error chain is set and fails.

All that is needed is for createCertificateChain to clear the
OpenSSL error chain before returning.
JIRA: LINK-1868

Change-Id: Ife2a3dabfeecff9e430648d63e4b4ba001e80a00

This adds a method to set a logging callback.  If such a callback is
set, all SWIFT_LOG calls will invoke this callback instead of writing to
either stderr or the swift logging file.

Test-Information:

Updated unit tests pass.
Checked that logs generated by Swift and Sluift (which do not set the
callback) resulted in logging in the expected location.

Change-Id: I0eb2a1057aa77839e1b8d5f320205eb9d5fdc253