host env VP write check #240
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tzemanovic
added a commit
that referenced
this pull request
Jul 29, 2022
tzemanovic
commented
Aug 1, 2022
tzemanovic
force-pushed
the
tomas+brentstone/host-env-vp-write-check
branch
from
6618fe8 to
4f8c283
Compare
tzemanovic
added a commit
that referenced
this pull request
Aug 17, 2022
* tomas+brentstone/host-env-vp-write-check: changelog: add #240 vm/host_env: disallow raw byte updates of validity predicates
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
to make sure that we're checking VPs written to storage in txs, the
tx_writehost function should disallow direct raw-bytes updates of VP storage keys. Instead, there'stx_update_validity_predicatethat performs some validation on the VP code