If you are among those who would like to use PSA from RUST, then you probably
know about:
https://github.com/parallaxsecond/rust-psa-crypto
and
https://github.com/fortanix/rust-mbedtls
One is relatively up-to-date with MBEDTLS 3.x, and does not (I think) have
thread issues. But, pretty difficult to use beyond crypto operations.
The other is idiomatic RUST and is a pleasure to use, but ran into thread
safety issues with MBEDTLS 3.x, and abandonned that work when it was realized
that even a big-lock couldn't make it work.
MBEDTLS/PSA is mostly the best choice for embedded OSs like RIOT-OS, Ariel.
I think FreeRTOS and Zephyr use it as well. This good fit is due to the
excellent offloading of operations to specialized hardware.
I realize that this isn't an ARM/PSA problem exactly.
I'm hoping, though, to collect interested parties towards finding a solution
going forward. Should we use this list? Or make a new one?
If you are among those who would like to use PSA from RUST, then you probably
know about:
https://github.com/parallaxsecond/rust-psa-crypto
and
https://github.com/fortanix/rust-mbedtls
One is relatively up-to-date with MBEDTLS 3.x, and does not (I think) have
thread issues. But, pretty difficult to use beyond crypto operations.
The other is idiomatic RUST and is a pleasure to use, but ran into thread
safety issues with MBEDTLS 3.x, and abandonned that work when it was realized
that even a big-lock couldn't make it work.
MBEDTLS/PSA is mostly the best choice for embedded OSs like RIOT-OS, Ariel.
I think FreeRTOS and Zephyr use it as well. This good fit is due to the
excellent offloading of operations to specialized hardware.
I realize that this isn't an ARM/PSA problem exactly.
I'm hoping, though, to collect interested parties towards finding a solution
going forward. Should we use this list? Or make a new one?
--
Michael Richardson <mcr+IETF(a)sandelman.ca> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
Hi!
I'm looking into packaging the TF-PSA-Crypto library in Debian for the
upcoming MbedTLS 4.0.0 release.
I've noticed that there are two (identical?) tags for version
1.0.0-beta: tf-psa-crypto-1.0.0-beta and v1.0.0-beta.
Maybe it is a dumb question, but: which of the two tags am I supposed to
use? Which of the two forms should I "watch" for updates?
Also: why are there two identical tags in the first place? This also
happens with MbedTLS!
Curious to know, bye :)
MBed-TLS Technical Forum - Asia
Every 4 weeks from 10am to 10:50am on Monday
United Kingdom Time
Trusted Firmware is inviting you to a scheduled Zoom meeting.Topic:
MBed-TLS Technical Forum - AsiaTime: Jun 16, 2025 10:00 AM London
Every 4 weeks on Mon, 39 occurrence(s)Please download and import the
following iCalendar (.ics) files to your calendar system.Weekly:
https://linaro-org.zoom.us/meeting/tJMqcuGuqDotGtIbACm498ytl0ZhydWKdu1b/ics…
Zoom
Meetinghttps://linaro-org.zoom.us/j/97758661706?pwd=baMjUvnWbY20z3ignQca7QVahhozkI.1Meeting
ID: 977 5866 1706Passcode: 577208---One tap
mobile+16892781000,,97758661706# US+17193594580,,97758661706# US---Dial by
your location• +1 689 278 1000 US• +1 719 359 4580 US• +1 253 205 0468 US•
+1 253 215 8782 US (Tacoma)• +1 301 715 8592 US (Washington DC)• +1 305 224
1968 US• +1 309 205 3325 US• +1 312 626 6799 US (Chicago)• +1 346 248 7799
US (Houston)• +1 360 209 5623 US• +1 386 347 5053 US• +1 507 473 4847 US•
+1 564 217 2000 US• +1 646 558 8656 US (New York)• +1 646 931 3860 US• +1
669 444 9171 US• +1 669 900 9128 US (San Jose)• 833 548 0282 US Toll-free•
833 928 4608 US Toll-free• 833 928 4609 US Toll-free• 833 928 4610 US
Toll-free• 877 853 5247 US Toll-free• 888 788 0099 US Toll-free• 833 548
0276 US Toll-freeMeeting ID: 977 5866 1706Find your local number:
https://linaro-org.zoom.us/u/acdtApJNbc
Guests
mbed-tls(a)lists.trustedfirmware.org
psa-crypto(a)lists.trustedfirmware.org
View all guest info
https://calendar.google.com/calendar/event?action=VIEW&eid=NjI4c3NnYjFoZHRh…
Reply for psa-crypto(a)lists.trustedfirmware.org and view more details
https://calendar.google.com/calendar/event?action=VIEW&eid=NjI4c3NnYjFoZHRh…
Your attendance is optional.
~~//~~
Invitation from Google Calendar: https://calendar.google.com/calendar/
You are receiving this email because you are an attendee on the event.
Forwarding this invitation could allow any recipient to send a response to
the organizer, be added to the guest list, invite others regardless of
their own invitation status, or modify your RSVP.
Learn more https://support.google.com/calendar/answer/37135#forwarding
Dear Mbed TLS and PSA Crypto users,
We would like to update you on the release timeline for Mbed TLS 4.0/TF-PSACrypto1.0 release.
As a reminder, the key objectives of the release are a separate TF-PSA Crypto repo., PSA Crypto becoming the de facto Crypto API and Mbed TLS using PSA Crypto APIs as the crypto API by default.
While TF-PSA Crypto repository is now available, the remaining effort to be ready for the release is more than we originally planned for.
Based on remaining effort estimates, we plan to make Mbed TLS 4.0-Beta and TF-PSA Crypto 1.0-Beta release around end of June. The Mbed TLS 4.0, and TF-PSA Crypto 1.0 release is expected around end of September.
We don’t expect users to integrate the Beta release. Beta is aimed to pipeclean the separate Mbed TLS and TF-PSA Crypto release process and get any early feedback. The release in September is expected to be integrated by users to their projects.
We wanted to provide these revised release dates so that the users can plan accordingly. In the meantime, bug fixes and security fixes will continue to be provided via. Mbed TLS 3.6.x LTS releases.
Thanks,
Mbed TLS/PSA Crypto Maintainers.
Dear PSA Crypto users,
Mbed TLS has contained the reference implementation of the PSA Crypto API since the early days of the standard. This implementation was experimental at first, but over years of development it reached maturity, and the experimental status was removed three years ago (in version 3.6.1.).
Shortly after that, in 2022, the TF-PSA-Crypto<https://github.com/Mbed-TLS/TF-PSA-Crypto> repository was created just for the PSA Crypto API implementation to make it more accessible for users only interested in that. This repository was only a mirror of the main one and the development of the PSA Crypto API implementation remained integral part of Mbed TLS.
In the background, work has been started to make this repository the place where the development of the PSA Crypto API reference implementation happens. This work has finally been completed and from now on TF-PSA-Crypto<https://github.com/Mbed-TLS/TF-PSA-Crypto> is ready to receive contributions, bug reports and enhancement requests. TF-PSA-Crypto<https://github.com/Mbed-TLS/TF-PSA-Crypto> will now be the development repository for the PSA Crypto reference implementation.
Many thanks,
Janos Follath
TF PSA Crypto developer
Hi All,
A gentle reminder that the US-Europe timezone-friendly MBed TLS Tech forum
is next Monday at 4:30pm UK time. Invite details can be found on the online
calendar here <https://www.trustedfirmware.org/meetings/>.
If you have any topics, please let Janos know. :)
Don
