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

GetCACert can't return both an RA and a CA certificate #3280

Closed
pki-bot opened this issue Oct 3, 2020 · 4 comments
Closed

GetCACert can't return both an RA and a CA certificate #3280

pki-bot opened this issue Oct 3, 2020 · 4 comments

Comments

@pki-bot
Copy link

pki-bot commented Oct 3, 2020

This issue was migrated from Pagure Issue #3163. Originally filed by cipherboy (@cipherboy) on 2020-03-16 16:49:51:


Description of problem:
When handling GetCACert requests, the logic currently doesn't attempt to return an application/x-x509-ca-ra-cert PKCS7 blob when the RA's certifying chain has more than one certificate in it. Unless a client "knows" to start with "message" set to 0 and attempt to walk the certifying chain, it will not be able to retrieve all of the certificates which are needed in order to successfully interact with the server.

Version-Release number of selected component (if applicable):
pki-common-9.0.3-38.el6_6.noarch

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from cipherboy (@cipherboy) at 2020-03-16 16:49:59

Metadata Update from @cipherboy:

  • Custom field component adjusted to None
  • Custom field feature adjusted to None
  • Custom field origin adjusted to None
  • Custom field proposedmilestone adjusted to None
  • Custom field proposedpriority adjusted to None
  • Custom field reviewer adjusted to None
  • Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1198262
  • Custom field type adjusted to None
  • Custom field version adjusted to None

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from cipherboy (@cipherboy) at 2020-03-16 16:56:06

Metadata Update from @cipherboy:

  • Issue close_status updated to: duplicate
  • Issue status updated to: Closed (was: Open)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant