-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question about validation logic #549
Comments
@mbrandonw The original behavior was to require the entire chain to be trusted. Like you, I am under the impression that only one cert needs to match. #412 added a boolean to control the behavior. If you set validateEntireChain=false, it will short circuit out of that loop. |
oh wow, that's it! I saw that option but didn't look further into it. Thanks for the help! |
I should add-- I left the existing behavior as default in the PR so that current Starscream users wouldn't suddenly have a change in their security model. I do think it should be the default behavior in a future major release such as 4.0 hint hint @daltoniam 😄 |
Looking at the source I found this:
Starscream/Sources/SSLSecurity.swift
Lines 177 to 188 in 70fd033
and I'm curious why all of the certificates from the server are required to match one of the certificates provided. I was under the impression that it is sufficient for at least one of the certificates to match.
Is this logic correct?
Thanks!
The text was updated successfully, but these errors were encountered: