You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an implementation with a limited number of bits for the exponent field for RSA SigVer.
For now, I am specifying fixed values for the exponent but it would be great if the exponent field could be a domain that can be specified so I can have more flexibility and test cases.
The text was updated successfully, but these errors were encountered:
This is likely not something we will support on the server. We try to avoid capabilities that disrupt or impact FIPS validations. For RSA SigGen, it is not well defined in the standard how to handle public keys that are not valid for a specific implementation. We wouldn't want people to interpret the ability to specify various e sizes as an implicit encouragement for general implementations. It is understandable in specific instances where you know the key is coming from a specific source. I recognize there's a chance that our 64-bit e values are the most that implementations could handle, the same way your implementation uses a 32-bit e.
We can generate test vectors for you or show you where to make modifications to create your own. Feel free to provide an RSA SigVer registration.json file.
I have an implementation with a limited number of bits for the exponent field for RSA SigVer.
For now, I am specifying fixed values for the exponent but it would be great if the exponent field could be a domain that can be specified so I can have more flexibility and test cases.
The text was updated successfully, but these errors were encountered: