The option needs to be set on the SSL socket.  Setting it on the model
takes no effect.  Note that the non-blocking mode is still not enabled
for the handshake because the code is not yet ready for that.

8 more bug fixes mentioned

Added recent additions and fixes following the changes to imap, pop3
and smtp. Additionally added another contributor that helped to test
the imap sasl changes.

Even though he's a fine dude, once is enough for this time!

Added missing imap fix as per commit 709b3506.

Do not use the error messages from NSS for errors not occurring in NSS.

This commit fixes a regression introduced in 052a08ff.

NSS caches certs/keys returned by the SSL_GetClientAuthDataHook callback
and if we connect second time to the same server, the cached cert/key
pair is used.  If we use multiple client certificates for different
paths on the same server, we need to clear the session cache to force
NSS to call the hook again.  The commit 052a08ff prevented the session
cache from being cleared if a client certificate from file was used.

The condition is now fixed to cover both cases: consssl->client_nickname
is not NULL if a client certificate from the NSS database is used and
connssl->obj_clicert is not NULL if a client certificate from file is
used.

Review by: Kai Engert

Although it is not explicitly stated in the documentation, NSS uses
*pRetCert and *pRetKey even if the client authentication hook returns
a failure.  Namely, if we destroy *pRetCert without clearing *pRetCert
afterwards, NSS destroys the certificate once again, which causes a
double free.

Reported by: Bob Relyea

Bug: http://curl.haxx.se/mail/lib-2012-11/0095.html

4 more bug fixes and 4 more contributors

Fixes bug #3578163:
http://sourceforge.net/tracker/?func=detail&atid=100976&aid=3578163&group_id=976

6 new bugfixes and 3 more contributors...

One bug, one contributor. Getting ready for release.

9 new bug fixes, 5 changes, 6 more contributors

The MD5 fingerprint cannot be computed when running in FIPS mode.

6 bug fixes to mention, 5 contributors

5 more bug fixes, one change, 6 contributors

Let's call it 7.27.1 for now, but it it probably going to become 7.28.0
when released.

The --silent bug came with 7561a0fc which was never in a release.
Pointed out by Kamil Dudka