Re: Issue with TC-ECC-3-30?

[Tim Hudson <tjh@cryptsoft.com>]

Indeed that is incorrect - and has been incorrect since that test case was created.

I have updated all versions to fix that so any future updated test lists will have the corrected value in place.

1_0/tc-ecc-3-10.xml Â1_2/tc-ecc-3-12.xml Â1_4/tc-ecc-3-14.xml Â2_1/tc-ecc-3-21.xml
1_1/tc-ecc-3-11.xml Â1_3/tc-ecc-3-13.xml Â2_0/tc-ecc-3-20.xml Â3_0/tc-ecc-3-30.xml

Thanks,

Tim.

On Sat, Aug 19, 2023 at 2:20âPM Mark Joseph <mark@p6r.com> wrote:

Hi Tim,

In the Request Message sequence $UNIQUE_IDENTIFER_0 is for the first registered PRIVATE KEY

so it looks like the PublicKeyLink value below should be $UNIQUE_IDENTIFER_1

<RequestMessage>

 <RequestHeader>

  <ProtocolVersion>

   <ProtocolVersionMajor type="Integer" value="3"/>

   <ProtocolVersionMinor type="Integer" value="0"/>

  </ProtocolVersion>

  <ClientCorrelationValue type="TextString" value="TC-ECC-3-30 step=2"/>

 </RequestHeader>

 <BatchItem>

  <Operation type="Enumeration" value="Register"/>

  <RequestPayload>

   <ObjectType type="Enumeration" value="Certificate"/>

   <Attributes>

    <CryptographicUsageMask type="Integer" value="Verify Sign"/>

    <PublicKeyLink type="Reference" value="$UNIQUE_IDENTIFIER_0"/>

    <Attribute>

     <VendorIdentification type="TextString" value="x"/>

     <AttributeName type="TextString" value="ID"/>

     <AttributeValue type="TextString" value="TC-ECC-3-30-cert1"/>

    </Attribute>

   </Attributes>

   <Certificate>

    <CertificateType type="Enumeration" value="X_509"/>

    <CertificateValue type="ByteString" value="308201d9cd ..... 6cc7641c76bb"/>

   </Certificate>

  </RequestPayload>

 </BatchItem>

</RequestMessage>

Best,
Mark Joseph, Ph.D.Â

President P6R, IncÂ

408-205-0361Â

http://www.linkedin.com/pub/mark-joseph/0/752/4b4