Created attachment 240659 [details] mbedtls-3.3.0.patch see https://github.com/Mbed-TLS/mbedtls/releases/tag/v3.3.0 PORTLINT(1),PORTCLIPPY(1) Compliant.
Do you need this for something? 2.28 is the current stable branch. 3.x is unstable.
(In reply to Tijl Coosemans from comment #1) There is no particular need, but there is no special problem, so I put out SendPR. Should I close this SendPR because -devel isn't a new one?
Hiawatha webserver (www/hiawatha) requires mbed TLS since 11.0 to support TLSv1.3 [0]. In some first releases it was patched-out in FreeBSD, but the latest 11.6 and 11.5 are failing to build. Would it be reasonable to have a separate mbedtls-devel port for 3.0 branch? [0] https://hiawatha.leisink.net/weblog/137
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=01623d80e0268a9c2e6590d74740486c804d0dcd commit 01623d80e0268a9c2e6590d74740486c804d0dcd Author: Tijl Coosemans <tijl@FreeBSD.org> AuthorDate: 2024-08-24 16:32:59 +0000 Commit: Tijl Coosemans <tijl@FreeBSD.org> CommitDate: 2024-08-24 16:42:58 +0000 security/mbedtls3: New port, version 3.6.0 PR: 270024 security/Makefile | 1 + security/mbedtls3/Makefile (new) | 45 ++++++++++ security/mbedtls3/distinfo (new) | 3 + security/mbedtls3/pkg-descr (new) | 2 + security/mbedtls3/pkg-plist (new) | 175 ++++++++++++++++++++++++++++++++++++++ 5 files changed, 226 insertions(+)
(In reply to commit-hook from comment #4) Look like security/mbedtls conflicts with security/mbedtls3.
https://github.com/Mbed-TLS/mbedtls/issues/8723
Thank you! :) Now I can try to build the newest hiawatha with this. Hope this will help.