diff options
| author | Quinn Slack <sqs@cs.stanford.edu> | 2011-02-09 23:34:30 +0100 |
|---|---|---|
| committer | Daniel Stenberg <daniel@haxx.se> | 2011-02-09 23:34:30 +0100 |
| commit | 3cffcba3d0cf78a2aa17197059f810f5a7ce05a5 (patch) | |
| tree | 867e13892108814d96daf573f06ca22baf7e9696 /lib/strerror.c | |
| parent | ae7fe3b7f45564569324e07ffeb1be4eabfef713 (diff) | |
| download | curl-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 'lib/strerror.c')
| -rw-r--r-- | lib/strerror.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/lib/strerror.c b/lib/strerror.c index 6b67a8777..a88cdc4eb 100644 --- a/lib/strerror.c +++ b/lib/strerror.c @@ -281,9 +281,6 @@ curl_easy_strerror(CURLcode error) case CURLE_CHUNK_FAILED: return "Chunk callback failed"; - case CURLE_TLSAUTH_FAILED: - return "TLS Authentication failed"; - /* error codes not used by current libcurl */ case CURLE_OBSOLETE4: case CURLE_OBSOLETE10: |