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

Fix and generalize the setting of the recipient field in subsequent messages of a transaction #9

Open
DDvO opened this issue Jan 31, 2023 · 0 comments

Comments

@DDvO
Copy link
Member

DDvO commented Jan 31, 2023

According to the Lightweight CMP profile:

  recipient                   REQUIRED
    -- SHOULD be the name of the intended recipient; otherwise, the
    --   NULL-DN MUST be used
    -- In the first message of a PKI management operation: SHOULD be
    --   the subject DN of the CA the PKI management operation is
    --   requested from
    -- In all other messages: SHOULD contain the value of the sender
    --   field of the previous message in the same PKI management
    --   operation

So also the client should mirror whatever it received from the server.

When doing so (which is already done by the server side),
not only the directoryName choice of type X509_NAME, but any GENERAL_NAME should be supported.

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

No branches or pull requests

1 participant