RELEASE-NOTES: mention the SASL buffer overflow

RELEASE-NOTES: synced with 25f351424b3538

8 more bug fixes mentioned

RELEASE-NOTES: Updated following recent changes to the email protocols

Added recent additions and fixes following the changes to imap, pop3
and smtp. Additionally added another contribut

RELEASE-NOTES: Updated following recent changes to the email protocols

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.

show more ...

RELEASE-NOTES: only list Nick once

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

RELEASE-NOTES: add references to several bugfixes+changes

RELEASE-NOTES: Added missing imap fix

Added missing imap fix as per commit 709b3506cd9b.

RELEASE-NOTES: synced with c43127414d89

nss: fix error messages for CURLE_SSL_{CACERT,CRL}_BADFILE

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

nss: clear session cache if a client cert from file is used

This commit fixes a regression introduced in 052a08ff.

NSS caches certs/keys returned by the SSL_GetClientAuthDataHook ca

nss: clear session cache if a client cert from file is used

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

show more ...

RELEASE-NOTES: synced with e3ed2b82e6

nss: prevent NSS from crashing on client auth hook failure

Although it is not explicitly stated in the documentation, NSS uses
*pRetCert and *pRetKey even if the client authentication ho

nss: prevent NSS from crashing on client auth hook failure

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

show more ...

bump: start working on 7.28.2

RELEASE-NOTES: synced with 52af6e69f079 / 7.28.1

RELEASE-NOTES: NSS can be used for metalink hashing

test2032: spurious failure caused by premature termination

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

RELEASE-NOTES: synced with ee588fe08807778

4 more bug fixes and 4 more contributors

RELEASE-NOTES: synced with fa1ae0abcde

RELEASE-NOTES: synced with 7c0cbcf2f617b

tool_metalink: allow to use hash algorithms provided by NSS

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

RELEASE-NOTES: synced with 487538e87a3d5e

6 new bugfixes and 3 more contributors...

RELEASE-NOTES: synced with fa6d78829fd30ad

version-bump: towards 7.28.1!

RELEASE-NOTES: synced with 8373ca3641

One bug, one contributor. Getting ready for release.

RELEASE-NOTES: synced with 971f5bcedd418

9 new bug fixes, 5 changes, 6 more contributors

ssh: do not crash if MD5 fingerprint is not provided by libssh2

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