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
man EVP_PKEY_CTX_set_params: document params is a list #23986
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM though it looks obvious to me
doc/man3/EVP_PKEY_CTX_set_params.pod
Outdated
@@ -23,6 +23,8 @@ The EVP_PKEY_CTX_get_params() and EVP_PKEY_CTX_set_params() functions allow | |||
transfer of arbitrary key parameters to and from providers. | |||
Not all parameters may be supported by all providers. | |||
See L<OSSL_PROVIDER(3)> for more information on providers. | |||
The B<params> field is a pointer to a list of OSSL_PARAM structures, terminated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use I<params>
and B<OSSL_PARAM>
please.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sure, fixed
7a31e0b
to
0bdd2d2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
transfer of 'arbitrary key parameters' gives a good indication that it is a list.
We should probably do this generically because there are a lot of these setter/getters.
In multiple places this is handled as
'See L<OSSL_PARAM(3)> for information about passing parameters'
@t8m are you reviewing this? I think this is useful if only for the "terminated with a L<OSSL_PARAM_END(3)> struct" bit |
I've proposed this change because it wasn't obvious to my colleague and to me, and had to actually experiment to understand how to use the API. So, if not being explicit about this is stuff in openssl man pages is the policy, I'd say it's a bad policy for documentation aimed at people beginning programming with OpenSSL API. |
If you added what I suggested and then read it, it should be understandable. My point is that there are a lot of set and get params calls. Fixing it in one place its less than ideal. |
@slontis sorry, given that the man page already has |
Signed-off-by: Hubert Kario <hkario@redhat.com>
0bdd2d2
to
fb0e223
Compare
@slontis Fixed (BTW: I don't think that a 👍 shows up in notifications) |
Still LGTM |
the failure doesn't look at all to be related to the changes:
|
24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set. Please review the updates and set the label manually. |
Merged to all the active branches. Thank you. |
Signed-off-by: Hubert Kario <hkario@redhat.com> Reviewed-by: Shane Lontis <shane.lontis@oracle.com> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from #23986)
Make it clear in the man page that the parameters field in
EVP_PKEY_CTX_set_params
are a pointer to a list, not to a single struct.Checklist