Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFE / PointFormatExtension elided takes default value test #9

Open
1 task
cipherboy opened this issue Jul 28, 2022 · 1 comment
Open
1 task

RFE / PointFormatExtension elided takes default value test #9

cipherboy opened this issue Jul 28, 2022 · 1 comment

Comments

@cipherboy
Copy link

cipherboy commented Jul 28, 2022

Description of the problem

Per RFC 8422 section 5.1.2:

RFC 4492 specified that if this extension is missing, it means that only the uncompressed point format is supported, so interoperability with implementations that support the uncompressed format should work with or without the extension.

It further states:

Implementations of this document MUST support the uncompressed format for all of their supported curves and MUST NOT support other formats for curves defined in this specification.

IOW, per my reading, specifying some combination of SupportedCurvesExtension without the PointFormatExtension should work and result in the uncompressed point format being used.

However, I don't see a test under the RFC 8422 directory for this behavior, and I see no directory for RFC 4492.

If this is of interest, I'd be happy to submit a PR (with a little guidance on building and running) to add this missing test case.

Additional Information

  • TLS-Anvil version: 283e10f
  • Issue occurred using TLS-Anvil while testing the following TLS server/client: n/a
  •  Attachted TLS-Anvil logs -- n/a
@mmaehren
Copy link
Contributor

mmaehren commented Aug 4, 2022

Hey,
I agree with your interpretation of the RFCs. We initially started adding tests based on requirements that contain one of the mandatory keywords defined in RFC 2119. There are other requirements, such as the one you quoted first, which are still missing. You are welcome to submit a PR. If you run into any issues, feel free to leave questions here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants