search

cfrg / draft-irtf-cfrg-hash-to-curve

Hashing to Elliptic Curves
Other
79 stars 27 forks source link

Compliance with draft #271

Closed armfazh closed 4 years ago

armfazh commented 4 years ago

Is there some part in the document that talks about what a library needs to implement in order to be compliant or compatible with the document?

kwantam commented 4 years ago

I might be misunderstanding the question, but: does {{suites-howto}} do this?

armfazh commented 4 years ago

The section {{suites-howto}} tells the pieces that a library needs to implement. And this section is useful.

However, my question is regarding the following situation; Suppose a library XX claims that has compatible methods for hashing to curves. Then, what is the minimal functionality an auditor of XX must look for in order to approve or disprove the claim?

-- I consider that the implementation of suites must be enough, and this should be pointed somewhere in the document.

Nothing prevents that a library YY only implements part of the suite, say e.g. only the SSWU map, but without implementing the full suite (which could or not violate the security guarantees we provide with the full suite). Hence, does library YY is compatible with the document?

kwantam commented 4 years ago

I agree, anything that implements a suite according to the guidelines in section 8 should be considered compatible.

chris-wood commented 4 years ago

Yeah, I don't think we ought to specify any sort of "mandatory to implement" suites. If an application implements any one of the suites (per the spec), it's compatible.

armfazh commented 4 years ago

Closing as no action is required.