-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TLS issue with mysql_async_wasi #18
Comments
I've encountered this error, and I will update the rustls plugin to attempt to resolve it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since the mysql_async_wasi repo does not have an issue track, I'm reporting to this repo instead.
When testing greptimedb example against GreptimeCloud instance, we are not able to complete SSL handshake. But using the original mysql_async library for default linux target, with
default-rustls
feature enabled, it works smoothly. So I believe there is potential issue with our mysql_async fork or tls libraries.Steps to reproduce
wasmedge --env "DATABASE_URL=mysql://<username>:<password>@<host>:4002/<dbname>" --env "DATABASE_SSL=1" target/wasm32-wasi/debug/greptimedb.wasm
What I can see from wireshark (no outbound traffic captured)
There is no traffic after mysql server greeting.
Verify from default target
mysql_async
0.31 andtokio
1.0, set build target to defaultThe example executed successfully and wireshark shows encrypted traffic.
The text was updated successfully, but these errors were encountered: