requesting help or documentation for "Expected EphemeralKeyIut but was not supplied"

[ehanson7]

environment

DEMO

testSessionId

437462

vsId

1822672

Expected behavior A clear and concise description of what you expected to happen.

We are requesting KAS-FFC-SHA2-256 and looking for help or description on how to fix: "Expected EphemeralKeyIut but was not supplied"

  {
    "tcId": 71,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 72,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 73,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 74,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 75,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 76,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 77,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 78,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 79,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 80,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 81,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 82,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 83,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 84,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 85,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 86,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 87,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 88,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 89,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },
  {
    "tcId": 90,
    "result": "failed",
    "reason": "Expected EphemeralKeyIut but was not supplied"
  },

[Kritner]

The FFC schema you're testing against requires the IUT (you) to provide an ephemeral public key for this test case/schema.

I can't look at your vector set, but just as the general idea, for a schema where both parties contribute a keypair to the diffie hellman calculation, the server would provide to the IUT an ephemeral public key where the server has the private. Similarly, the expectation is that the IUT would provide to the server its ephemeral public key, so that both parties can perform the diffie hellman calculation, and potentially subsequent KDF against the same shared secret.

https://pages.nist.gov/ACVP/draft-fussell-acvp-kas-ffc.html#name-generation-requirements-per contains the chart describing server and IUT expectations for each schema/role combination

[jbrock24]

@ehanson7 Can this be closed? Do you still require further help?

[ehanson7]

Yes, Please do close out. Thank You!

On Mon, Dec 11, 2023 at 11:33 AM Joel Brockman @.***> wrote:

@ehanson7 https://github.com/ehanson7 Can this be closed? Do you still require further help?

— Reply to this email directly, view it on GitHub https://github.com/usnistgov/ACVP-Server/issues/286#issuecomment-1850752326, or unsubscribe https://github.com/notifications/unsubscribe-auth/BCYOAQSJG7FUAHLN4XAMAD3YI5NXBAVCNFSM6AAAAAA5DVDLYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJQG42TEMZSGY . You are receiving this because you were mentioned.Message ID: @.***>