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

clarify that octets_to_point should be injective? #36

Open
kwantam opened this issue Feb 10, 2021 · 1 comment
Open

clarify that octets_to_point should be injective? #36

kwantam opened this issue Feb 10, 2021 · 1 comment

Comments

@kwantam
Copy link
Collaborator

kwantam commented Feb 10, 2021

If octets_to_point isn't injective, there could be malleability-like issues (i.e., swap one byte-string for another that represents the same point). Should we require octets_to_point to be injective?

@dot-asm
Copy link

dot-asm commented Mar 14, 2021

One can argue that this would be considered "naturally implied" requirement, but it's only appropriate to be explicit, so that nobody would be able to say "the requirement is not spelled, hence there is no such requirement." In other words 👍 👍 👍 Oh! Did I say 👍 ?

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