Add outputLength property to schema - #931
Conversation
|
Thanks for the addition @jvdsn, that's useful! I had two questions regarding edge cases:
|
|
Perhaps use oneOf to account for either an integer which would represent a single output length, or an object which would have min and max properties. Refer to: https://json-schema.org/understanding-json-schema/reference/combining#oneOf This would look something like: |
e0285d7 to
34d8d11
Compare
|
@stevespringett apologies for the delay. I have updated the PR now. Let me know what you think. One open question: do we want to enforce that both min and max are required (as they are currently)? Or should we allow one of them to be omitted? |
Signed-off-by: Joachim Vandersmissen <git@jvdsn.com>
|
@stevespringett I fixed the DCO |
|
RFC notice sent on July 23, 2026
Public RFC period ends August 20, 2026 |
| }, | ||
| { | ||
| "type": "object", | ||
| "required": [ |
There was a problem hiding this comment.
are both required, always?
not have a atleast one of them required?
There was a problem hiding this comment.
Currently both are required for simplicity. If there's any strong opinions one way or another, I can change it.
Fixes #799
Adds the outputLength property that indicates the output length of the cryptographic algorithm. This is not restricted to key derivation functions, but could also be used for MAC tags, XOF output lengths, and more.