Hi all,
I have some questions.
1) If you have an established TLS connection (mbed TLS 3.x) and while the
connection is up the (server-) certificate expires: Will the connection stay
up? Or is a new handshake (with valid cert) REQUIRED?
2) Related to question 1: CAN mbed TLS switch to a new cert on an existing
TLS connection? (e.g. by doing another handshake from server OR client side)
3) With 3.x some struct members are now "private". Even if you can allow
private access by a define it would be better to use a getter. But for ssl
context's "state" I am missing this and also for "p_bio" (to access fd). Is
there a chance to get this implemented?
BTW - a big "LIKE" for 3.x! I really appreciate the changes. Thank you!
kind regards,
Frank
Hi All,
A gentle reminder that the US-Europe timezone-friendly MBed TLS Tech forum
is tomorrow (Monday) at 4:30 PM UK time.
If you have any topics, please let Dave Rodgman know. :)
Best regards,
Don Harbin
TrustedFirmware Community Manager
don.harbin(a)linaro.org
Hi Mbed TLS users,
We have released Mbed TLS version 3.2.1.
This release is functionally identical to 3.2.0, but includes a file that was missing from the 3.2.0 release (see https://github.com/Mbed-TLS/mbedtls/issues/6084).
Full details are available in the release notes (https://github.com/Mbed-TLS/mbedtls/releases/tag/v3.2.1).
We recommend all users to consider whether they are impacted, and to upgrade appropriately.
Many thanks,
Mbed TLS Team.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
--
Mbed-tls-announce mailing list -- mbed-tls-announce(a)lists.trustedfirmware.org
To unsubscribe send an email to mbed-tls-announce-leave(a)lists.trustedfirmware.org
Hi Mbed TLS users,
We have released Mbed TLS versions 3.2.0 and 2.28.1.
These releases of Mbed TLS address several security issues, provide bug fixes, and for 3.2.0, add various features. Full details are available in the release notes (https://github.com/Mbed-TLS/mbedtls/releases/tag/v3.2.0, https://github.com/Mbed-TLS/mbedtls/releases/tag/v2.28.1).
We recommend all users to consider whether they are impacted, and to upgrade appropriately.
Dave Rodgman
Hi mbed-tls Team,
I notice that https://tls.mbed.org has been directed to https://www.trustedfirmware.org/projects/mbed-tls/. However, I does not see any link to the old Mbed TLS knowledge base. It is a good resource for learning Mbed TLS. What is the URL to access it?
Thanks,
Max Peng
Hi all,
it feels like the state of documentation has deteriorated since the last
time I've used mbedtls (a couple of months ago). I'm not sure if the google
index hasn't fully been updated yet, or I don't understand the new
structure of the docs or ...
Also, is this the proper forum to make suggestions? Should I raise an issue
on Github?
1.) a lot of previously linked, useful information now redirects here:
https://www.trustedfirmware.org/projects/mbed-tls/ which (please excuse my
frankness) feels like an utterly useless abomination that only marketing
people could love.
- Some examples of previously useful links: from the wiki (
https://developer.trustedfirmware.org/w/mbed-tls/) :
> Old Mbed TLS website
> Documentation: Mbed TLS API Reference; Knowledge base; Dev corner
all redirect to trustedfirmware.org ! As do nearly all the links in
https://github.com/Mbed-TLS/mbedtls/blob/development/SUPPORT.md
2.) there is no longer an doxygen generated API documentation anywhere
only. I could generate it myself, but then I'd need to get and install
Doxygen, figure how to use it, etc. It would be great if this were
restored. It can't be that expensive to host :)
Anyway, it feels like I've been running around for hours trying to find
_anything_ useful, but I just realized everything is redirected to
trustedfirmware.org ... Is there any way to still access the old, useful
docs?
Thanks & sorry that this post is so negative,
-tim
Hello Sir/Madam,
I am developing TI's EFM32 series micro controller based IOT device. This
device will connect to mqtt broker and publish/ subscribes to/from data.
In my application, I am trying to connect to AWS using mbedtls library over
lwIP (no rtos mode). While my device is in debug mode (i.e. JTAG programmer
connected) then it gets connected to AWS successfully. But when I remove
JTAG programmer and operate device in normal running mode, then it failed to
get connect to broker (i.e. AWS).
I observe following errors occured while performing TLS handshaking stage:
SSL - The connection indicated an EOF
X509 - Certificate verification failed, e.g. CRL, CA or signatur
SSL - Processing of the ServerHello handshake message failed
Hi all,
First of all apologies if this is not the right place for this topic. For my master thesis I am using the mbedtls library to analyze it using side channel analysis.
My objective was to use it as a starting point to analyze the resistance of different exponentiation algorithms.
With this objective I am trying to set up a environment where I can call the function "mbedtls_mpi_exp_mod" https://github.com/Mbed-TLS/mbedtls/blob/f5b7082f6e8af72868966b6ea99eae228f… and debug it. I have been trying for at least two weeks but I couldn't be able to succeed.
I believe that when If I can get a debugging environment for that function I will be able to adapt it and use other exponentiation algorithms such as the Left-to-right k-ary (HAC 14.82).
I am using VScode and the code is located in WLS Ubuntu 20.04. So far I been able to compile the full library and run all the tests.
Anyone here could give mean indication on how to set up the environment to debug this function?
Thanks!
Victor.
Hello,
Currently, we are evaluating the MbedLib to be eventually used in small and midsized automotive ECUs.
* Since we have to follow the UNECE Regulation R155, R156, and ISO/SAE 21434 I need some information regarding the long-term support of the library and how the communication of bugs is organized?
* I also do not understand the involvement and responsibility of ARM company?
* Furthermore, I'm not sure if I understood the terms PSA and MbedTls and their mutual dependencies as well as the technical meaning?
I checked the web for I but did not find anything about it yet.
It would be just great if somebody can give me some hints or links to the information I am looking for.
Regards Heico