Skip to content

vtls: use Curl_safecmp for CRLfile and pinned_key comparison#21668

Closed
MegaManSec wants to merge 1 commit into
curl:masterfrom
MegaManSec:crlfile-safecmp
Closed

vtls: use Curl_safecmp for CRLfile and pinned_key comparison#21668
MegaManSec wants to merge 1 commit into
curl:masterfrom
MegaManSec:crlfile-safecmp

Conversation

@MegaManSec
Copy link
Copy Markdown
Contributor

Both are filesystem paths (or case-sensitive hash strings for pinned_key). curl_strequal is case-insensitive and would treat /etc/ssl/Crl.pem and /etc/ssl/crl.pem as the same file, unlike the other path fields (CApath, CAfile, issuercert, clientcert) which already use Curl_safecmp.

Both are filesystem paths (or case-sensitive hash strings for
pinned_key). curl_strequal is case-insensitive and would treat
/etc/ssl/Crl.pem and /etc/ssl/crl.pem as the same file, unlike
the other path fields (CApath, CAfile, issuercert, clientcert)
which already use Curl_safecmp.
@github-actions github-actions Bot added the TLS label May 19, 2026
@bagder bagder closed this in 81da4ee May 19, 2026
outcast36 pushed a commit to greearb/curl that referenced this pull request Jun 3, 2026
Both are filesystem paths (or case-sensitive hash strings for
pinned_key). curl_strequal is case-insensitive and would treat
/etc/ssl/Crl.pem and /etc/ssl/crl.pem as the same file, unlike the other
path fields (CApath, CAfile, issuercert, clientcert) which already use
Curl_safecmp.

Closes curl#21668
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

2 participants