aboutsummaryrefslogtreecommitdiff
path: root/RELEASE-NOTES
AgeCommit message (Collapse)Author
2013-01-28RELEASE-NOTES: only list Nick onceDaniel Stenberg
Even though he's a fine dude, once is enough for this time!
2013-01-18RELEASE-NOTES: add references to several bugfixes+changesDaniel Stenberg
2013-01-18RELEASE-NOTES: Added missing imap fixSteve Holme
Added missing imap fix as per commit 709b3506cd9b.
2013-01-18RELEASE-NOTES: synced with c43127414d89Daniel Stenberg
2013-01-15nss: fix error messages for CURLE_SSL_{CACERT,CRL}_BADFILEKamil Dudka
Do not use the error messages from NSS for errors not occurring in NSS.
2013-01-11nss: clear session cache if a client cert from file is usedKamil Dudka
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
2012-12-27RELEASE-NOTES: synced with e3ed2b82e6Daniel Stenberg
2012-12-03nss: prevent NSS from crashing on client auth hook failureKamil Dudka
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
2012-11-20bump: start working on 7.28.2Daniel Stenberg
2012-11-20RELEASE-NOTES: synced with 52af6e69f079 / 7.28.1Daniel Stenberg
2012-11-20RELEASE-NOTES: NSS can be used for metalink hashingAnthony Bryan
2012-11-19test2032: spurious failure caused by premature terminationKamil Dudka
Bug: http://curl.haxx.se/mail/lib-2012-11/0095.html
2012-11-17RELEASE-NOTES: synced with ee588fe08807778Daniel Stenberg
4 more bug fixes and 4 more contributors
2012-11-14RELEASE-NOTES: synced with fa1ae0abcdeDaniel Stenberg
2012-11-13RELEASE-NOTES: synced with 7c0cbcf2f617bDaniel Stenberg
2012-11-09tool_metalink: allow to use hash algorithms provided by NSSKamil Dudka
Fixes bug #3578163: http://sourceforge.net/tracker/?func=detail&atid=100976&aid=3578163&group_id=976
2012-11-07RELEASE-NOTES: synced with 487538e87a3d5eDaniel Stenberg
6 new bugfixes and 3 more contributors...
2012-11-06RELEASE-NOTES: synced with fa6d78829fd30adDaniel Stenberg
2012-10-10version-bump: towards 7.28.1!Daniel Stenberg
2012-10-10RELEASE-NOTES: synced with 8373ca3641Daniel Stenberg
One bug, one contributor. Getting ready for release.
2012-10-02RELEASE-NOTES: synced with 971f5bcedd418Daniel Stenberg
9 new bug fixes, 5 changes, 6 more contributors
2012-09-12ssh: do not crash if MD5 fingerprint is not provided by libssh2Kamil Dudka
The MD5 fingerprint cannot be computed when running in FIPS mode.
2012-09-09RELEASE-NOTES: synced with 6c6f1f64c2Daniel Stenberg
6 bug fixes to mention, 5 contributors
2012-09-03RELEASE-NOTES: synced with abb0da919300eDaniel Stenberg
2012-08-09nss: do not print misleading NSS error codesKamil Dudka
2012-08-08RELEASE-NOTES: synced with 0774386b23Daniel Stenberg
5 more bug fixes, one change, 6 contributors
2012-08-08RELEASE-NOTES: added missing linkDaniel Stenberg
2012-08-07RELEASE-NOTES: synced with b4a558041fdf65c0Daniel Stenberg
2012-07-27version bump: start towards next releaseDaniel Stenberg
Let's call it 7.27.1 for now, but it it probably going to become 7.28.0 when released.
2012-07-27RELEASE-NOTES: remove mentioned of bug never in a releaseDaniel Stenberg
The --silent bug came with 7561a0fc834c435 which was never in a release. Pointed out by Kamil Dudka
2012-07-27RELEASE-NOTES: synced with 33b815e894fbDaniel Stenberg
4 more bugfixes, 3 more contributors
2012-07-22http: print reason phrase from HTTP status line on errorKamil Dudka
Bug: https://bugzilla.redhat.com/676596
2012-07-20Fixed some typos in documentationDan Fandrich
2012-07-15RELEASE-NOTES: synced with 9d11716933616Daniel Stenberg
Fixed 6 bugs, added 3 contributors
2012-07-09docs: switch to proper UTF-8 for text file encodingDaniel Stenberg
2012-07-09RELEASE-NOTES: added a URL reference to cookie docsDaniel Stenberg
2012-07-07RELEASE-NOTES: synced with 5a99bce07dDaniel Stenberg
2012-06-25RELEASE-NOTES: link to more metalink infoDaniel Stenberg
2012-06-25RELEASE-NOTES: synced with d025af9bb576Daniel Stenberg
2012-06-13schannel: remove version number and identify its use with 'schannel' literalYang Tse
Version number is removed in order to make this info consistent with how we do it with other MS and Linux system libraries for which we don't provide this info. Identifier changed from 'WinSSPI' to 'schannel' given that this is the actual provider of the SSL/TLS support. libcurl can still be built with SSPI and without SCHANNEL support.
2012-06-11sspi: Updated RELEASE-NOTES, FEATURES and THANKSMarc Hoersken
2012-06-09pop3: Added support for apop authenticationSteve Holme
2012-06-08ssl: fix duplicated SSL handshake with multi interface and proxyKamil Dudka
Bug: https://bugzilla.redhat.com/788526 Reported by: Enrico Scholz
2012-06-04pop3: Added support for sasl digest-md5 authenticationSteve Holme
2012-06-03RELEASE-NOTES: Added missing addition of sasl login supportSteve Holme
2012-06-03pop3: Added support for sasl cram-md5 authenticationSteve Holme
2012-06-03RELEASE-NOTES: synced with c4e3578e4bfDaniel Stenberg
Also bumped the contributor number and next release is to become 7.27.0
2012-06-02pop3: Fixed the issue of having to supply the user name for all requestsSteve Holme
Previously it wasn't possible to connect to POP3 and not specify the user name as a CURLE_ACCESS_DENIED error would be returned. This error occurred because USER would be sent to the server with a blank user name if no mailbox user was specified as the server would reply with -ERR. This wasn't a problem prior to the 7.26.0 release but with the introduction of custom commands the user and/or application developer might want to issue a CAPA command without having to log in as a specific mailbox user. Additionally this fix won't send the newly introduced AUTH command if no user name is specified.
2012-05-28nss: use human-readable error messages provided by NSSKamil Dudka
Bug: http://lists.baseurl.org/pipermail/yum-devel/2012-January/009002.html
2012-05-24bump to 7.26.1: start working towards next releaseDaniel Stenberg
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-20 18:08:58 +0000