[0.3.0-draft] Include the full wasi:random/imports #203
Conversation
This file contains hidden or 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
lukewagner
approved these changes
Oct 17, 2025
|
Oops, sorry neglecting this; could you rebase and update the markdown and then we can merge? |
This switches `wasi:http/proxy` from just using `wasi:random/random` to also including `wasi:random/insecure` and `wasi:random/insecure-seed`. These "insecure" interfaces allow applications which need random numbers for purposes other than cryptography or UUIDs to request them, which can give hosts more flexibility when running in environments with scarce entropy, such as early boot environments. These interfaces should be easy to support in any host that already supports `wasi:random/random`. They permit alternate implementation strategies, but don't require them.
sunfishcode
force-pushed
the
sunfishcode/random
branch
from
95d18cc to
dc53ad8
Compare
|
Done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This switches
wasi:http/proxyfrom just usingwasi:random/randomto also includingwasi:random/insecureandwasi:random/insecure-seed.These "insecure" interfaces allow applications which need random numbers for purposes other than cryptography or UUIDs to request them, which can give hosts more flexibility when running in environments with scarce entropy, such as early boot environments.
These interfaces should be easy to support in any host that already supports
wasi:random/random. They permit alternate implementation strategies, but don't require them.