Skip to content

Conversation

@hpshelton
Copy link

The cURL manual explains the correct usage of CURLOPT_SSL_VERIFYHOST as follows:

1 to check the existence of a common name in the SSL peer certificate. 2 to check the existence of a common name and also verify that it matches the hostname provided. In production environments the value of this option should be kept at 2 (default value).

CURLOPT_SSL_VERIFYHOST also cannot be used without CURLOPT_SSL_VERIFYPEER. See http://www.cs.utexas.edu/~shmat/shmat_ccs12.pdf for a full analysis of the security vulnerability here.

The cURL manual explains the correct usage of CURLOPT_SSL_VERIFYHOST as follows:

1 to check the existence of a common name in the SSL peer certificate. 2 to check the existence of a common name and also verify that it matches the hostname provided. In production environments the value of this option should be kept at 2 (default value).

CURLOPT_SSL_VERIFYHOST also cannot be used without CURLOPT_SSL_VERIFYPEER. See http://www.cs.utexas.edu/~shmat/shmat_ccs12.pdf for a full analysis of the security vulnerability here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant