History log of /wasmtime-44.0.1/crates/test-programs/src/tls.rs (Results 1 – 3 of 3)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: dev, v36.0.9, v44.0.1, v43.0.2, v36.0.8, v24.0.8, v44.0.0, v43.0.1, v42.0.2, v36.0.7, v24.0.7, v43.0.0, v42.0.1, v41.0.4, v42.0.0, v40.0.4, v36.0.6, v24.0.6, v41.0.3, v41.0.2, v41.0.1, v36.0.5, v40.0.3, v41.0.0, v36.0.4, v39.0.2, v40.0.2, v40.0.1, v40.0.0, v39.0.1, v39.0.0, v38.0.4, v37.0.3, v36.0.3, v24.0.5, v38.0.3, v38.0.2, v38.0.1, v37.0.2, v37.0.1, v37.0.0, v36.0.2, v36.0.1, v36.0.0, v35.0.0, v24.0.4, v33.0.2, v34.0.2, v34.0.1, v33.0.1, v24.0.3, v32.0.1, v34.0.0, v33.0.0
# 90ac295e 19-May-2025 Alex Crichton <[email protected]>

Update Wasmtime to the 2024 Rust Edition (#10806)

* Update Wasmtime to the 2024 Rust Edition

Now that our MSRV supports the 2024 edition it's possible to make this
switch. This commit moves Wasmtim

Update Wasmtime to the 2024 Rust Edition (#10806)

* Update Wasmtime to the 2024 Rust Edition

Now that our MSRV supports the 2024 edition it's possible to make this
switch. This commit moves Wasmtime to the 2024 Edition to keep
up-to-date with Rust idioms and access many of the edition features
exclusive to the 2024 edition.

prtest:full

* Reformat with the 2024 edition

show more ...


Revision tags: v32.0.0
# 0ca6d4fd 21-Mar-2025 Dave Bakker <[email protected]>

Expose Wasi-TLS handshake error (#10429)

* Expose TLS errors to the guest.

* Add a test to check the non-happy flow and verify that the error is properly propagated into the guest.

* Update WIT ve

Expose Wasi-TLS handshake error (#10429)

* Expose TLS errors to the guest.

* Add a test to check the non-happy flow and verify that the error is properly propagated into the guest.

* Update WIT versions

show more ...


Revision tags: v31.0.0
# e8d5e3ae 07-Mar-2025 James Sturtevant <[email protected]>

Initial implementation of Wasi-tls (Transport Layer Security) (#10249)

* Initial implementation of wasi-tls

This crate provides the Wasmtime host implementation for the [wasi-tls] API.
The [wasi-t

Initial implementation of Wasi-tls (Transport Layer Security) (#10249)

* Initial implementation of wasi-tls

This crate provides the Wasmtime host implementation for the [wasi-tls] API.
The [wasi-tls] world allows WebAssembly modules to perform SSL/TLS operations,
such as establishing secure connections to servers. TLS often relies on other wasi networking systems
to provide the stream so it will be common to enable the [wasi:cli] world as well with the networking features enabled.

The initial implemntation is using rustls.

Signed-off-by: James Sturtevant <[email protected]>

* Remove configuration object for now

Signed-off-by: James Sturtevant <[email protected]>

* Update cargo patch to use temp branch

Signed-off-by: James Sturtevant <[email protected]>

* Rename tcp streams to wasistreams to be more generic

Signed-off-by: James Sturtevant <[email protected]>

* gate the wasi-tls ctx behind a feature

Signed-off-by: James Sturtevant <[email protected]>

* cleanup and clippy fixes

Signed-off-by: James Sturtevant <[email protected]>

* Fix issue when another pollable cancels

Signed-off-by: James Sturtevant <[email protected]>

* prtest:full

Signed-off-by: James Sturtevant <[email protected]>

* Skip test on riscv64/s390x

Signed-off-by: James Sturtevant <[email protected]>

* Drop debug info to support tests on pulley based platforms

Signed-off-by: James Sturtevant <[email protected]>

* Update signature of `close-notify`

* Use draft version

Signed-off-by: James Sturtevant <[email protected]>

* Remove patches

Signed-off-by: James Sturtevant <[email protected]>

* Ungate tls on riscv64 and s390x

* Un-gate wais-http on riscv64/s390x as well

* Add wasmtime-wasi-tls to publish list

* Add wasmtime-wasi-tls to public API crate list

* Revert some changes to Cargo.lock

---------

Signed-off-by: James Sturtevant <[email protected]>
Signed-off-by: James Sturtevant <[email protected]>
Co-authored-by: badeend <[email protected]>
Co-authored-by: Alex Crichton <[email protected]>

show more ...