[kmip-interop-tech] TC-RSA-SIGN-DIGESTEDDATA

Felipe,
The testcase name gives part of the answer...since there are no parameters given, there is no hashing/digesting done (presumed to have already been done, if necessary)
And if I recall correctly, padding not having been specified means padding is "none" (but others might have a better recollection on this point).
The Private Key has a Cryptographic Usage Mask of Sign, and the Public Key has a Cryptographic Usage Mask of Verify, so that's all that's needed for this testcase.  It's the "just sign this binary data, please" testcase.
Regards,  Bruce Rich
On Mon, Mar 19, 2018 at 2:37 PM, Felipe Kendi  < 
>  wrote:
Hi everyone,  I have a doubt about the Digest Data test:
http://docs.oasis-open.org/ kmip/testcases/v1.4/cn01/test- cases/kmip-v1.4/TC-RSA-SIGN- DIGESTEDDATA-1-14.xml
When the private key is registered, it's only informed the cryptographic algorithm (RSA) and length (2048 bits). When the "Sign" operation is requested, no cryptographic parameters are informed, so I believe there is no way for the server to know what padding method and hash algorithm to use in the signature. However, we've noticed that some servers actually sign the data, even without these parameters. Is there an expected behavior that we are missing (default padding/hashing type)?  Thank you,

--
Felipe Kendi Desenvolvedor de Software KRYPTUS EED S/A Trust in Cybersecurity  +55 19 3112 5000
www.kryptus.com