search

usnistgov / ESV-Server

Entropy Source Validation Protocol and Server specifications
13 stars 12 forks source link

SHA3-256: no vetted conditioning component #1

Closed smuellerDD closed 3 years ago

smuellerDD commented 3 years ago

My noise source has a SHA3-256 conditioning component.

I register:

    "conditioningComponent":[
      {
        "sequencePosition":1,
        "description":"SHA3-256",
        "vetted":true,
        "validationNumber":"A770",
        "minNin":392,
        "minHin":1,
        "nw":256,
        "nOut":256
      }

The server returns the following error:

  {
    "conditioningComponents": {
      "conditioningComponentList": [
        {
          "location": "SequencePosition:1",
          "errorList": [
            "DescriptionError: description: SHA3-256 does not exist in the VettedConditioningComponentAttributes table.",
            "DependencyFailed: nw cannot be validated because its dependent property description Result Code is Fail.",
            "DependencyFailed: nOut cannot be validated because its dependent property description Result Code is Fail.",
            "RequiredPropertyError: conditionedBitsSHA256 was not found in the JSON payload."
          ]
        }
      ]
    }
  }
]
celic commented 3 years ago

SHA3 is currently not yet supported by ACVP SP800-90A testing. So it has been left off here. We should probably add it in as an option though, even if the testing isn't yet ready.

smuellerDD commented 3 years ago

Thanks. But even when changing it to a SHA2-256 with all else the same, I get:

  {
    "conditioningComponents": {
      "conditioningComponentList": [
        {
          "location": "SequencePosition:1",
          "errorList": [
            "DescriptionError: description: SHA2-256 does not exist in the VettedConditioningComponentAttributes table.",
            "DependencyFailed: nw cannot be validated because its dependent property description Result Code is Fail.",
            "DependencyFailed: nOut cannot be validated because its dependent property description Result Code is Fail.",
            "RequiredPropertyError: conditionedBitsSHA256 was not found in the JSON payload."
          ]
        }
      ]
    }
celic commented 3 years ago

Ah I see. Currently we have "SHA-2-256" and "SHA-3-256" rather than "SHA2-256" and "SHA3-256". This will be fixed in the next patch.