-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Ed25519 PK validation in Move should return None
instead of aborting on wrong length
#7043
Conversation
@mstraka100, I updated your PR's description to be a little more precise. Also, can you change the base branch of this PR to be https://github.com/aptos-labs/aptos-core/tree/alin/native-feature-flag-context? This way, only your commits & changes will show up in "Files Changed." |
aptos-move/aptos-release-builder/src/components/feature_flags.rs
Outdated
Show resolved
Hide resolved
Hey Michael, as you can see once my stuff merged, this PR got rebased to |
None
instead of aborting on wrong length
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approval pending removing the unused getter functions in features.move
aptos-move/aptos-release-builder/src/components/feature_flags.rs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but fix the errors, since it seems you might be missing a clause in a match
.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
✅ Forge suite
|
✅ Forge suite
|
✅ Forge suite
|
This PR updates the
native_public_key_validate
native Move function to returnfalse
when a key of the wrong length is passed in, rather than aborting.This change in behavior is feature-gated via a new
Ed25519PubkeyValidateReturnFalseWrongLength
feature flag which is checked inside the Rust native implementation itself.Testing
Ran replay tests here to see if they trigger any problems in past TXNs. All passed.