kmip-interop-tech — archive

[Mark Joseph <mark@p6r.com>]

The issue is what the key format type is used in the digest.   Looking at the variable items like you provided I did not see that.   But I am getting old so maybe I missed it :-). Best, Mark Joseph P6R,  Inc 408-205-0361 mark@p6r.com On Mar 20, 2018, at 12:01 PM, Felipe Kendi < kendi@kryptus.com > wrote: Hi everyone, We are in a dispute with P6R regarding the Key Format Type returned in the Digest Attribute (for KMIP 1.4). Kryptus Server returns the Key Format Type as Transparent (this was also our behavior in the last year Interop): <Attribute> <AttributeName   type = TextStrin g   value = Digest /> <AttributeValue> <HashingAlgorithm   type = Enumer ation   value = SHA_256 /> <DigestValue   type = ByteString   value = 0533e51dd2ead671fa9eb9 cd08baa7868fe94b42d579b4f0d3cf dacaefbe8688 /> <KeyFormatType   type = Enumerati on   value = TransparentRSAPriva teKey /> </AttributeValue> </Attribute> However, P6R expects the Key Format Type to be exactly like the in the test case: <Attribute>     <AttributeName type= TextString value= Digest />     <AttributeValue>         <HashingAlgorithm type= Enumeration value= SHA_256 />         <DigestValue type= ByteString value= 8eb422ae2b006a05d3c8a542a28536735241b6dc1c37926bc8007bd6220d9230 />         <KeyFormatType type= Enumeration value= PKCS_1 />     </AttributeValue> </Attribute> Kryptus' understanding is that the Key Format may vary from server to server, as stated in the KMIP Protocol Profiles 1.4 document, section 4.1.1 (variable items): http://docs.oasis-open.org/kmip/profiles/v1.4/os/kmip-profiles-v1.4-os.html#_Toc491431423 P6R thinks different and has informed us that this year the tests were expected to check for the Key Format Type. Can you folks please tell me when this was decided? And if this is indeed the expected behavior, why the profiles document was not updated? Thank you, -- Felipe Kendi Desenvolvedor de Software KRYPTUS EED S/A Trust in Cybersecurity +55 19 3112 5000 www.kryptus.com