Age | Commit message (Collapse) | Author |
|
|
|
|
|
On second thought, I think CURLE_TLSAUTH_FAILED should be eliminated. It
was only being raised when an internal error occurred while allocating
or setting the GnuTLS SRP client credentials struct. For TLS
authentication failures, the general CURLE_SSL_CONNECT_ERROR seems
appropriate; its error string already includes "passwords" as a possible
cause. Having a separate TLS auth error code might also cause people to
think that a TLS auth failure means the wrong username or password was
entered, when it could also be a sign of a man-in-the-middle attack.
|
|
|
|
Reported by: Ian D Allen
Bug: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/714895
Forwarded to us by:
Reported by: Andreas Olsson
Bug: http://curl.haxx.se/bug/view.cgi?id=3175422
|
|
|
|
"6.7 What are my obligations when using libcurl in my commercial apps?"
got the piece about what exactly "in all copies" mean to a user of the
code.
This interpretation is based on what other MIT-like licenses have made
more explicit.
|
|
|
|
|
|
|
|
|
|
|
|
The default value is 1.
curl _uses_ a default CA bundle, it doesn't install one.
Drop the references to 7.10 as that is now >8 years old!
|
|
Extended the intial HTTP protcol part and added a mention of --trace and
--trace-ascii.
Replaced most URLs in the text to use example.com instead of all the
made up strange names.
Shortened a bunch of lines.
|
|
Extended the descriptions somewhat and made the options get listed next
to each other.
|
|
... and update the curl.1 and curl_easy_setopt.3 man pages such that
they do not suggest to use an OpenSSL utility if curl is not built
against OpenSSL.
Bug: https://bugzilla.redhat.com/669702
|
|
Bug: http://curl.haxx.se/bug/view.cgi?id=3157232
Reported by: John Bradshaw
|
|
|
|
Bug: https://bugzilla.redhat.com/623663
|
|
|
|
|
|
|
|
Also spelling fix for RECIPIENT #define.
|
|
example.
|
|
Even if libcurl might to do it for us, it is more correct.
|
|
|
|
Without this you won't get the next (Subject) line.
|
|
|
|
|
|
|
|
|
|
|
|
This example shows how to send SMTP with TLS
|
|
Add a simple SMTP example program, patterned after some of the existing
examples, and the curl application.
This version addresses issues raised by David Woodhouse on comments in
the simplesmtp.c example.
|
|
|
|
Bug: http://curl.haxx.se/mail/lib-2010-12/0192.html
|
|
|
|
|
|
It was added in 7.17.0 and is not deprecated
|
|
|
|
and the traditional source header
|
|
|
|
|
|
|
|
This script is the start of a helper tool that scans a source code and
outputs the most recent libcurl version it finds symbols for. Meaning
that if there's no conditions in the code, that's the earliest libcurl
version the scanned code requires.
It is not added to the Makefile.am yet as it is still a bit crude, but
I'm committing it to keep it and allow us to work on it.
|
|
This is a meta symbol. OR this value together with a single specific
auth value to force libcurl to probe for un-restricted auth and if not,
only that single auth algorithm is acceptable.
For example you can use CURLAUTH_DIGEST|CURLAUTH_ONLY to make libcurl
first probe for what method to use, but yet only consider Digest to be
acceptable.
Using _only_ CURLAUTH_DIGEST without the CURLAUTH_ONLY field, will make
libcurl explicitly use Digest right away and not do any probing.
|
|
I also documented the filtering logic in the symbol-scan.pl function to
clarify why not all CURL_* symbols are included.
|
|
|
|
|
|
|