Switch to MbedTLS 3.x

[Tachi107]

Hi!

I'm working towards transitioning Debian to MbedTLS 3.6 from MbedTLS 2.28, the new LTS. Unfortunately, python-mbedtls is one of the software packages which are currently failing to build when using MbedTLS 3.x instead of 2.x.

The situation for your project is peculiar since, I believe, you need to integrate pretty deeply with MbedTLS - for instance, you include some _internal headers which are now inaccessible in MbedTLS 3.x.

Are you interested in switching to version 3.x?

Thanks!

[Synss]

Hi!

Thank you for your interest.

Yes, I am interested in switching to mbedtls 3. I will most likely drop a lot of features and concentrate on TLS and DTLS.

I have actually started working in that direction,
s. https://github.com/Synss/python-mbedtls/tree/mbedtls-3.x
but it’s a lot of work and my time is limited, so progress is slow.

[Tachi107]

Nice, thanks for letting me know! I'll keep an eye on this issue :)

[Nilsonfsilva]

Hi @Tachi107

I have actually started working in that direction,
s. https://github.com/Synss/python-mbedtls/tree/mbedtls-3.x
but it’s a lot of work and my time is limited, so progress is slow.

First of all, congratulations on your project.

I am a maintainer of your package in Debian!

From the conversation above, you have already started the transition to MbedTLS 3.x? How is the transition going?

Your package is crucial for others, this situation currently prevents other packages that depend on it from migrating to the new version of Debian that will be released, I believe, in July.

Thanks in advance!

[Synss]

Hi and sorry for the late answer. I will most likely abandon this project as I unfortunately don’t have the necessary time for this anymore. Moreover, upstream recently announced an mbedtls 4 version, most likely again with breaking changes and I am not able to keep up.

[Synss]

Thank you for your interest.

Due to time constraints, active development on this project has ceased and this repository is now read-only.
I am open to transferring ownership to a new maintainer; if you are interested in taking over, please contact me
via the email listed on my GitHub profile. In the meantime, users are encouraged to fork the repository for their own continued use.