It leads to the "next family" tries starting from the wrong point and thus
fails!

Bug: http://curl.haxx.se/bug/view.cgi?id=1337
Reported-by: ricker

Because of the socket is unblocking, PolarSSL does need call to getsock to
get the action to perform in multi environment.

In some cases, it might happen we have not received yet all data to perform
the handshake. ssh_handshake returns POLARSSL_ERR_NET_WANT_READ, the state
is updated but because of the getsock has not the proper #define macro to,
the library never prevents to select socket for input thus the socket will
never be awaken when last data is available. Thus it leads to timeout.

Remove all #ifdef/else/endif macros that ensure compatibility with polarssl
version previous than 1.3.

API has changed since version 1.3. A compatibility header has been created
to ensure forward compatibility for code using old API:
 * x509 certificate structure has been renamed to from x509_cert to
   x509_crt
 * new dedicated setter for RSA certificates ssl_set_own_cert_rsa,
   ssl_set_own_cert is for generic keys
 * ssl_default_ciphersuites has been replaced by function
   ssl_list_ciphersuites()

This patch drops the use of the compatibly header.

Also fixed a function name change in the version requirement bump

Rename x509_cert to x509_crt and add "compat-1.2.h"
include.
This would still need some more thorough conversion
in order to drop "compat-1.2.h" include.

... if built against a new enough version of NSS

... if built against a new enough version of NSS

... but allow them to be enabled/disabled explicitly.  The default
policy should be maintained at the NSS level.

Also, removed an unneeded strippart

This one seems to come and go as the optimizer decides how best
to inline some functions.

This option is currently rather useless with these protocols
when no quote command is given, but it is valid.

... and use Curl_safefree() instead of free()

Patch-by: byte_bucket

The information about building with Kerberos4 support was half a year out
of date. We dropped support for that.

Also, combined a couple of #ifdef sections

Port number zero is perfectly allowed to connect to. I moved to storing
the remote port number in an int so that -1 means undefined and 0-65535
can be used for legitimate port numbers.

Setting the TIMER_STARTSINGLE timestamp first in CONNECT has the
drawback that for actions that go back to the CONNECT state, the time
stamp is reset and for the multi_socket API there's no corresponding
Curl_expire() then so the timeout logic gets wrong!

Reported-by: Brad Spencer
Bug: http://curl.haxx.se/mail/lib-2014-02/0036.html

... since that’s how the RFC calls it.

... as it isn't used then!