summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorQuinn Slack <sqs@cs.stanford.edu>2011-02-09 23:34:30 +0100
committerDaniel Stenberg <daniel@haxx.se>2011-02-09 23:34:30 +0100
commit3cffcba3d0cf78a2aa17197059f810f5a7ce05a5 (patch)
tree867e13892108814d96daf573f06ca22baf7e9696 /include
parentae7fe3b7f45564569324e07ffeb1be4eabfef713 (diff)
downloadcurl-3cffcba3d0cf78a2aa17197059f810f5a7ce05a5.tar.gz
CURLE_TLSAUTH_FAILED: removed
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.
Diffstat (limited to 'include')
-rw-r--r--include/curl/curl.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/include/curl/curl.h b/include/curl/curl.h
index bf6542076..4744f4830 100644
--- a/include/curl/curl.h
+++ b/include/curl/curl.h
@@ -502,7 +502,6 @@ typedef enum {
CURLE_RTSP_SESSION_ERROR, /* 86 - mismatch of RTSP Session Identifiers */
CURLE_FTP_BAD_FILE_LIST, /* 87 - unable to parse FTP file list */
CURLE_CHUNK_FAILED, /* 88 - chunk callback reported error */
- CURLE_TLSAUTH_FAILED, /* 89 - Failed TLS authentication */
CURL_LAST /* never use! */
} CURLcode;