Open Tartopoms opened 1 year ago
Just out of curiosity what would be the use case? Cryptoki frequently needs PKCS11 driver anyway and you'd have to be able to access the device somehow (eg. via pcsclite).
I'm working on a light web client to interact with an HSM and a database.
Cannot compile
cryptoki-sys
to wasm targetRelated to: Cannot compile dependency: could not find
Library
inlibloading
#1641When I build, watch & serve a Rust WASM app with
cryptoki
, its dependencycryptoki-sys
raise a compilation error.The error is:
Steps To Reproduce
wasm32-unknown-unknown
target for rust is installedrustup target add wasm32-unknown-unknown
rust/toolchains/$custom-toolchain/components/
foldercargo install dioxus-cli
dx --help
dx create
, and select the following options:download/unzip
the dioxus-templatedx create --template dioxus-template-main
$USER
not found ->export USER=any
, the value do not matterExpected behavior
Being able to compile after running
dx serve
:Environment:
I'm working on a Docker Container, offline, with a custom Rust toolchain and a custom registry. I've been working with them for 3 months and have never had a problem so far, so I want to remove these two from the possible error case.
With my toolchain and registry: I have two full Rust apps working. One with an Axum server and Dioxus client, communicating with REST and WebSockets. Another with cryptoki (RSA PKCS#11), without any issue so far.
v0.4.0
v0.4.1
v0.6.1
1.70.0
,stable
Docker container
:Debian GNU/Linux 11 (bullseye)
Questionnaire