Skip to content

Conversation

@michaelherold
Copy link
Contributor

When using mutual TLS, you must specify the CA certificate chain to use
for verifying the peer. Using Puma's ssl_bind DSL did not give you the
option of doing so, which lead to confusing errors when attempting to
use it.

Now, when specifying the verify_mode as either peer or force_peer,
you can use the DSL to set the ca value as needed within the Binder.
This allows you to use the DSL instead of falling back to the default
bind syntax via the URI-style configuration pattern.

@evanphx
Copy link
Member

evanphx commented Feb 20, 2019

Could you rebase this on master? There have been a few fixes around this code merged lately.

When using mutual TLS, you must specify the CA certificate chain to use
for verifying the peer. Using Puma's `ssl_bind` DSL did not give you the
option of doing so, which lead to confusing errors when attempting to
use it.

Now, when specifying the `verify_mode` as either `peer` or `force_peer`,
you can use the DSL to set the `ca` value as needed within the `Binder`.
This allows you to use the DSL instead of falling back to the default
`bind` syntax via the URI-style configuration pattern.
@michaelherold michaelherold force-pushed the allow-ca-to-be-set-in-bind-dsl branch from 489eef4 to 5a92683 Compare February 20, 2019 20:27
@michaelherold
Copy link
Contributor Author

Done!

@evanphx evanphx merged commit 6568aae into puma:master Mar 11, 2019
@michaelherold michaelherold deleted the allow-ca-to-be-set-in-bind-dsl branch December 10, 2019 16:12
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.

2 participants