-
Notifications
You must be signed in to change notification settings - Fork 513
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
private mbedtls in communications library #940
Conversation
…cations can include their own version of mbedtls
Testing (mdma):
|
@m-mcgowan wiring/no_fixture tests pass on Electron U260 as well as connecting and restoring sessions with the tinker usb debugging v0.4.8-rc.6 app. |
It might be nice to add some kind of bare minimum example to the Docs of what someone can do with this now in User firmware. |
That's not quite how it is - it's not in user firmware, it's still in system firmware, but private - the changes allows developers to include their own copy of mbedtls in user firmware without conflicts from the system copy. |
Oh is that kind of beyond the scope of our Docs? They would have to acquire a copy of mbedtls, and can't duplicate anything used in our stack? |
When we include our own, this allows us to push data to services like AWS that require an SSL/TLS connection? Essentially bypassing webhooks? |
@rayjanwilson, yes potentially. |
the mbedtls headers are private to the communications module so applications can include their own version of mbedtls
Doneness: