Bruno Ciola 

Good question, and thank you for sharing this.  I wasn't aware of the change.  I have asked the developers to review this will respond once I know more.  If we do need to make some changes we certainly won't put them into anything older than 2022.  But we do open source the plugins so any developer could make the changes to older versions if they need it.

Hi Paul , thank you for replying. Any update on this topic? What's also interesting is that Deepl says "On or after July 29, 2024,", so we don't really know when this could cause any issues with Studio plugins.

Regards,

Bruno

Bruno Ciola 

Thanks for updating this post... I think it got lost in the backlog and hasn't been addressed!

We just looked at this and have run some tests on the plugin for Studio and also the add-on for Language Cloud.  It seems that starting with .NET Framework 4.5, TLS 1.2 is supported, but you have to enable it explicitly in your application.  For .NET Core and .NET 5 and above, TLS 1.2 and 1.3 are enabled by default.

So, we only need to address this in the plugin as the add-on is covered.  We'll make the changes for 2022 and 2024 since 2022 is still supported and this is going to be a critical error if we don't.  The updates should be available shortly.  If not today then tomorrow... QA will take longer than the fix!

Dear Paul ,

thank you for the update. I understand that Studio 2021 plugins will not be updated. As we are just about to migratate to Studio 2024, how likely is it that the Studio 2021 plugin will stop working on 2nd September (see extended deadline https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites) ?

Regards,

Bruno

Bruno Ciola 

Bruno Ciola said:

how likely is it that the Studio 2021 plugin will stop working on 2nd September

Very.  I spoke with the DeepL product manager and he said this:

"We'll be moving forward with the deprecation again on September 2 and won't be able to extend the deadline any further."