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

pki/root/sign-intermediate ignoring signer pathLen if use_csr_values=true #4459

Closed
robison opened this issue Apr 25, 2018 · 3 comments · Fixed by #4469
Closed

pki/root/sign-intermediate ignoring signer pathLen if use_csr_values=true #4459

robison opened this issue Apr 25, 2018 · 3 comments · Fixed by #4469
Milestone

Comments

@robison
Copy link
Contributor

robison commented Apr 25, 2018

Environment:

  • Vault Version: Vault v0.10.1 ('bc15f5547919e01d83d89a1527317b96c0a74baa')
  • Operating System/Architecture: macOS 10.13.4

Expected Behavior:

  • Have CA certificate with pathLen=1 at /pki
  • Sign an intermediate CSR with CA certificate at /pki/root/sign-intermediate, and use CSR values from request (use_csr_values=true)
  • Receive signed CA certificate with pathLen=0, and all other CSR values copied over.

Actual Behavior:

  • Receive signed CA certificate with pathLen unset, and all other CSR values copied over.

I do understand the rationale for directly copying over CSR values, but I don't think that ignoring the pathLen on the signing certificate is quite right. I'm curious to learn if this is intended behavior, or something for which a PR would be accepted. Thanks!

@robison
Copy link
Contributor Author

robison commented Apr 26, 2018

N.b., the behavior is the same, regardless of whether max_path_length is specified.

@jefferai
Copy link
Member

Unintended. If you're happy to work up a PR that would be great! Otherwies I can whip one up.

@jefferai jefferai added this to the 0.10.2 milestone Apr 26, 2018
@robison
Copy link
Contributor Author

robison commented Apr 26, 2018

Yup, I'll have one submitted today. Thanks for the quick feedback!

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 a pull request may close this issue.

2 participants