Loading docs/DISTRO-DILEMMA +4 −4 Original line number Diff line number Diff line Loading @@ -59,7 +59,7 @@ GnuTLS OpenSSL does. Now, you can build and distribute an TLS/SSL capable libcurl without including any Original BSD licensed code. I believe Debian is the first (only?) distro that provides libcurl/GnutTLS I believe Debian is the first (only?) distro that provides libcurl/GnuTLS packages. yassl Loading @@ -72,20 +72,20 @@ GnuTLS vs OpenSSL vs yassl While these three libraries offer similar features, they are not equal. libcurl does not (yet) offer a standardized stable ABI if you decide to switch from using libcurl-openssl to libcurl-gnutls or vice versa. The GnuTLS switch from using libcurl-openssl to libcurl-gnutls or vice-versa. The GnuTLS and yassl support is very recent in libcurl and it has not been tested nor used very extensively, while the OpenSSL equivalent code has been used and thus matured since 1999. GnuTLS - LGPL licensened - LGPL licensed - supports SRP - lacks SSLv2 support - lacks MD2 support (used by at least some CA certs) - lacks the crypto functions libcurl uses for NTLM OpenSSL - Original BSD licensened - Original BSD licensed - lacks SRP - supports SSLv2 - older and more widely used Loading docs/FEATURES +3 −3 Original line number Diff line number Diff line Loading @@ -55,7 +55,7 @@ HTTP - reads/writes the netscape cookie file format - custom headers (replace/remove internally generated headers) - custom user-agent string - custom referer string - custom referrer string - range - proxy authentication - time conditions Loading Loading @@ -161,8 +161,8 @@ IMAP - SASL based authentication: Plain, Login, CRAM-MD5, Digest-MD5 and NTLM (*9) - list the folders of a mailbox - select a mailbox with support for verifing the UIDVALIDITY - fetch e-mails with support for specifing the UID and SECTION - select a mailbox with support for verifying the UIDVALIDITY - fetch e-mails with support for specifying the UID and SECTION - upload e-mails via the append command - enhanced command support for: EXAMINE, CREATE, DELETE, RENAME, STATUS, STORE, COPY and UID via custom requests Loading docs/INSTALL.cmake +1 −1 Original line number Diff line number Diff line Loading @@ -71,7 +71,7 @@ Command Line CMake $ make install (The teste suit does not work with the cmake build) (The test suite does not work with the cmake build) ccmake ========= Loading docs/INTERNALS +1 −1 Original line number Diff line number Diff line Loading @@ -300,7 +300,7 @@ Persistent Connections o When libcurl is told to perform a transfer, it first checks for an already existing connection in the cache that we can use. Otherwise it creates a new one and adds that the cache. If the cache is full already when a new conncetion is added added, it will first close the oldest unused one. connection is added added, it will first close the oldest unused one. o When the transfer operation is complete, the connection is left open. Particular options may tell libcurl not to, and protocols may signal closure on connections and then they won't be kept open of course. Loading docs/KNOWN_BUGS +5 −5 Original line number Diff line number Diff line Loading @@ -6,13 +6,13 @@ may have been fixed since this was written! 87. -J/--remote-header-name doesn't decode %-encoded file names. RFC6266 details how it should be done. The can of worm is basically that we have no charset handling in curl and ascii >=128 is a challenge for us. Not to mention that decoding also means that we need to check for nastyness that is mention that decoding also means that we need to check for nastiness that is attempted, like "../" sequences and the like. Probably everything to the left of any embedded slashes should be cut off. http://curl.haxx.se/bug/view.cgi?id=1294 86. The disconnect commands (LOGOUT and QUIT) may not be sent by IMAP, POP3 and SMTP if a failure occures during the authentication phase of a and SMTP if a failure occurs during the authentication phase of a connection. 85. Wrong STARTTRANSFER timer accounting for POST requests Loading @@ -38,9 +38,9 @@ may have been fixed since this was written! such in the build. http://curl.haxx.se/bug/view.cgi?id=1222 81. When using -J (with -O), automaticly resumed downloading together with "-C -" fails. Without -J the same command line works! This happens because the resume logic is worked out before the target file name (and thus its 81. When using -J (with -O), automatically resumed downloading together with "-C -" fails. Without -J the same command line works! This happens because the resume logic is worked out before the target file name (and thus its pre-transfer size) has been figured out! http://curl.haxx.se/bug/view.cgi?id=1169 Loading Loading
docs/DISTRO-DILEMMA +4 −4 Original line number Diff line number Diff line Loading @@ -59,7 +59,7 @@ GnuTLS OpenSSL does. Now, you can build and distribute an TLS/SSL capable libcurl without including any Original BSD licensed code. I believe Debian is the first (only?) distro that provides libcurl/GnutTLS I believe Debian is the first (only?) distro that provides libcurl/GnuTLS packages. yassl Loading @@ -72,20 +72,20 @@ GnuTLS vs OpenSSL vs yassl While these three libraries offer similar features, they are not equal. libcurl does not (yet) offer a standardized stable ABI if you decide to switch from using libcurl-openssl to libcurl-gnutls or vice versa. The GnuTLS switch from using libcurl-openssl to libcurl-gnutls or vice-versa. The GnuTLS and yassl support is very recent in libcurl and it has not been tested nor used very extensively, while the OpenSSL equivalent code has been used and thus matured since 1999. GnuTLS - LGPL licensened - LGPL licensed - supports SRP - lacks SSLv2 support - lacks MD2 support (used by at least some CA certs) - lacks the crypto functions libcurl uses for NTLM OpenSSL - Original BSD licensened - Original BSD licensed - lacks SRP - supports SSLv2 - older and more widely used Loading
docs/FEATURES +3 −3 Original line number Diff line number Diff line Loading @@ -55,7 +55,7 @@ HTTP - reads/writes the netscape cookie file format - custom headers (replace/remove internally generated headers) - custom user-agent string - custom referer string - custom referrer string - range - proxy authentication - time conditions Loading Loading @@ -161,8 +161,8 @@ IMAP - SASL based authentication: Plain, Login, CRAM-MD5, Digest-MD5 and NTLM (*9) - list the folders of a mailbox - select a mailbox with support for verifing the UIDVALIDITY - fetch e-mails with support for specifing the UID and SECTION - select a mailbox with support for verifying the UIDVALIDITY - fetch e-mails with support for specifying the UID and SECTION - upload e-mails via the append command - enhanced command support for: EXAMINE, CREATE, DELETE, RENAME, STATUS, STORE, COPY and UID via custom requests Loading
docs/INSTALL.cmake +1 −1 Original line number Diff line number Diff line Loading @@ -71,7 +71,7 @@ Command Line CMake $ make install (The teste suit does not work with the cmake build) (The test suite does not work with the cmake build) ccmake ========= Loading
docs/INTERNALS +1 −1 Original line number Diff line number Diff line Loading @@ -300,7 +300,7 @@ Persistent Connections o When libcurl is told to perform a transfer, it first checks for an already existing connection in the cache that we can use. Otherwise it creates a new one and adds that the cache. If the cache is full already when a new conncetion is added added, it will first close the oldest unused one. connection is added added, it will first close the oldest unused one. o When the transfer operation is complete, the connection is left open. Particular options may tell libcurl not to, and protocols may signal closure on connections and then they won't be kept open of course. Loading
docs/KNOWN_BUGS +5 −5 Original line number Diff line number Diff line Loading @@ -6,13 +6,13 @@ may have been fixed since this was written! 87. -J/--remote-header-name doesn't decode %-encoded file names. RFC6266 details how it should be done. The can of worm is basically that we have no charset handling in curl and ascii >=128 is a challenge for us. Not to mention that decoding also means that we need to check for nastyness that is mention that decoding also means that we need to check for nastiness that is attempted, like "../" sequences and the like. Probably everything to the left of any embedded slashes should be cut off. http://curl.haxx.se/bug/view.cgi?id=1294 86. The disconnect commands (LOGOUT and QUIT) may not be sent by IMAP, POP3 and SMTP if a failure occures during the authentication phase of a and SMTP if a failure occurs during the authentication phase of a connection. 85. Wrong STARTTRANSFER timer accounting for POST requests Loading @@ -38,9 +38,9 @@ may have been fixed since this was written! such in the build. http://curl.haxx.se/bug/view.cgi?id=1222 81. When using -J (with -O), automaticly resumed downloading together with "-C -" fails. Without -J the same command line works! This happens because the resume logic is worked out before the target file name (and thus its 81. When using -J (with -O), automatically resumed downloading together with "-C -" fails. Without -J the same command line works! This happens because the resume logic is worked out before the target file name (and thus its pre-transfer size) has been figured out! http://curl.haxx.se/bug/view.cgi?id=1169 Loading
