Skip to content

Conversation

@jedisct1
Copy link
Member

In order to avoid probing signatures that don't match a public key, signatures are prefixed with an algorithm identifier.

That identifier was present in examples, but not in the specification.

So, mention it in the specification.

In addition, current implementations don't consider that the identifier is part of the signature, so match these implementations. It doesn't make any difference beyond the encoded signature length.

In order to avoid probing signatures that don't match a public
key, signatures are prefixed with an algorithm identifier.

That identifier was present in examples, but not in the specification.

So, mention it in the specification.

In addition, current implementations don't consider that the
identifier is part of the signature, so match these implementations.
It doesn't make any difference beyond the encoded signature length.
@jedisct1
Copy link
Member Author

jedisct1 commented Feb 2, 2024

Ping?

@dschuff dschuff merged commit 4dd47d2 into WebAssembly:main Feb 2, 2024
@jedisct1 jedisct1 deleted the sig-update branch February 2, 2024 19:56
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

Successfully merging this pull request may close these issues.

2 participants