Skip to content
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

Don't make SSL_CN mandatory #53

Merged
merged 1 commit into from
Nov 9, 2020
Merged

Conversation

emersion
Copy link
Contributor

@emersion emersion commented Nov 8, 2020

In case the client didn't present a certificate, then there's no CN TLV that
could be populated by the proxy.

haproxy also omits this field in this case. The TLV is only appended if
ssl_sock_get_remote_common_name returns a positive integer 1. The
function returns 0 in case the CN isn't found 2.

In case the client didn't present a certificate, then there's no CN TLV that
could be populated by the proxy.

haproxy also omits this field in this case. The TLV is only appended if
ssl_sock_get_remote_common_name returns a positive integer [1]. The
function returns 0 in case the CN isn't found [2].

[1]: https://github.com/haproxy/haproxy/blob/233ad288cd4b855ba5fd08342433a0f5d20e625d/src/connection.c#L1510
[2]: https://github.com/haproxy/haproxy/blob/4299528390ce197a06c0ef1d59a4696fa9c19c30/src/ssl_sock.c#L6092
@coveralls
Copy link

Coverage Status

Coverage remained the same at 93.487% when pulling cd4b0ca on emersion:lax-parse-ssl-tlv into 84376ea on pires:master.

Copy link
Owner

@pires pires left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch! Thanks a lot.

@pires pires merged commit 9d53ed5 into pires:master Nov 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants