-
-
Notifications
You must be signed in to change notification settings - Fork 491
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 transport #3
Labels
Comments
+1 for mbedTLS |
mbedTLS +1
…On Feb 11, 2017 19:45, "scubadriver" ***@***.***> wrote:
+1 for mbedTLS
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAedbJudo2VurKw5rnyakvrZqiDaowEAks5rbgGwgaJpZM4LkGlA>
.
|
any update on TLS implementation? |
I've actually been working hard on this the past week and half... there is a TLS branch in github, but it is unusable at present. That said, I'm at the point of debugging this right now, so stay tuned. With a little luck, I'll be able to close this out this week. |
Closed
This was referenced May 7, 2020
Closed
muryliang
pushed a commit
to muryliang/nng
that referenced
this issue
Mar 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We can implement at TLS transport now, pretty easily, I think. We just need to choose a TLS framework (mbed TLS?) and implement it.
The text was updated successfully, but these errors were encountered: