Stream: git-wasmtime

Topic: wasmtime / issue #4213 wasi-crypto: unable to build on Wi...

view this post on Zulip Wasmtime GitHub notifications bot (Jun 02 2022 at 22:02):

abrown opened issue #4213:

@jedisct1, I thought it would be interesting to build in the

Note: if you want to report a security issue, please read our security policy!

Test Case

TODO: upload Wasm file here

Steps to Reproduce

Expected Results

TODO: What do you expect to happen?

Actual Results

TODO: What actually happens? Panic? Segfault? Incorrect result?

Versions and Environment

Wasmtime version or commit: TODO

Operating system: TODO

Architecture: TODO

Extra Info

Anything else you'd like to add?

view this post on Zulip Wasmtime GitHub notifications bot (Jun 02 2022 at 22:03):

abrown labeled issue #4213:

@jedisct1, I thought it would be interesting to build in the

Note: if you want to report a security issue, please read our security policy!

Test Case

TODO: upload Wasm file here

Steps to Reproduce

Expected Results

TODO: What do you expect to happen?

Actual Results

TODO: What actually happens? Panic? Segfault? Incorrect result?

Versions and Environment

Wasmtime version or commit: TODO

Operating system: TODO

Architecture: TODO

Extra Info

Anything else you'd like to add?

view this post on Zulip Wasmtime GitHub notifications bot (Jun 02 2022 at 22:07):

abrown edited issue #4213:

@jedisct1, I thought it would be interesting to build in wasi-crypto to the benchmarking engine used in Sightglass over in #4207. I changed the wasmtime-bench-api default features to include wasi-crypto, but when I did, I observed build errors on Windows related to pqcrypto-internals:

https://github.com/bytecodealliance/wasmtime/runs/6700498078?check_suite_focus=true#step:12:399

Understanding that neither the wasmtime-bench-api crate or the wasi-crypto feature are completely "done," this issue is not a high priority one; I did want to get your eyes on this to see if there is anything simple that can be done to fix things. In the meantime, I will leave wasi-crypto disabled by default in wasmtime-bench-api.

view this post on Zulip Wasmtime GitHub notifications bot (Jun 02 2022 at 22:31):

jedisct1 commented on issue #4213:

Thanks for reporting this!

I think it was fixed here, about a week after the crate published :/

So, the next release won't have that issue. As a workaround, the wasi-crypto hostcalls can be compiled without the default features, effectively removing the pqcrypto dependency.

view this post on Zulip Wasmtime GitHub notifications bot (Jun 02 2022 at 22:32):

jedisct1 edited a comment on issue #4213:

Thanks for reporting this!

I think it was fixed here, about a week after the crate was published :/

So, the next release won't have that issue. As a workaround, the wasi-crypto hostcalls can be compiled without the default features, effectively removing the pqcrypto dependency.

view this post on Zulip Wasmtime GitHub notifications bot (Mar 20 2024 at 23:10):

alexcrichton closed issue #4213:

@jedisct1, I thought it would be interesting to build in wasi-crypto to the benchmarking engine used in Sightglass over in #4207. I changed the wasmtime-bench-api default features to include wasi-crypto, but when I did, I observed build errors on Windows related to pqcrypto-internals:

https://github.com/bytecodealliance/wasmtime/runs/6700498078?check_suite_focus=true#step:12:399

Understanding that neither the wasmtime-bench-api crate or the wasi-crypto feature are completely "done," this issue is not a high priority one; I did want to get your eyes on this to see if there is anything simple that can be done to fix things. In the meantime, I will leave wasi-crypto disabled by default in wasmtime-bench-api.

view this post on Zulip Wasmtime GitHub notifications bot (Mar 20 2024 at 23:10):

alexcrichton commented on issue #4213:

We've since removed wasi-crypto from in-tree, so Im' going to close this.

Last updated: Dec 23 2024 at 12:05 UTC