Skip to content

Conversation

@sunfishcode
Copy link
Member

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.

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.
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