#107018SSL Compatibility Issue: localize.typo3.org's 2048-bit keys conflict with BSI guidelines and FIPS:OSPP compliance requirements
Description
One of our customers must comply with strict BSI (German Federal Office for Information Security) guidelines that recommend SSL key lengths of at least 3000 bits, preferably 4096 bits for RSA algorithms. We are operating under the crypto policy “FIPS:OSPP” which enforces that SSL keys must not be shorter than 3072 bits.
Issue Description:
- The TYPO3 translation service at https://localize.typo3.org uses SSL certificates with 2048-bit keys
- Our security compliance policy prevents connections to servers with keys shorter than 3072 bits
- We cannot downgrade our crypto policy from “FIPS:OSPP” to less restrictive policies due to contractual and regulatory compliance requirements
- This prevents our TYPO3 installations from accessing translation services, which are essential for proper system functionality
We kindly request one of the following solutions to be implemented:
1. Primary Solution (Preferred):
Upgrade the SSL certificates on localize.typo3.org to use 4096-bit keys to comply with BSI recommendations and FIPS:OSPP requirements.
2. Alternative Solutions (if primary solution is not feasible):
a) Provide an official alternative access method to translation services that supports stronger encryption (e.g., an API gateway or proxy with 4096-bit keys)
b) Implement a feature in TYPO3 core that allows downloading and bundling translations during deployment rather than runtime
c) Create official documentation on how to securely operate TYPO3 in high-security environments with restricted SSL requirements
## Impact
The current situation forces organizations under strict security compliance to choose between:
- Breaking security compliance by allowing weaker encryption
- Operating with incomplete or outdated translations
- Implementing custom workarounds that may not be maintainable across TYPO3 updates
Many government agencies and regulated industries in Germany and other countries operating under similar security frameworks face this challenge.
## Proposed Timeline
We understand that certificate changes require planning, but request this issue to be addressed in the next 3-6 months as it affects security-critical environments.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 6
-
Janine Schendel changed tracker
FeatureTask TYPO3 Version 13 <span data-processor="relativetime" data-value="2025-07-02T12:30:29+00:00" > 07/02/25, 12:30 </span> -
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-07-02T19:27:13+00:00" > 07/02/25, 19:27 </span>
-
Garvin Hicking commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2025-07-03T09:46:27+00:00" > 07/03/25, 09:46 </span>Thanks for creating this issue and bringing awareness to it.
The localization server is also used by older servers on existing ELTS and LTS instances. Updating encryption parameters can have an adverse effect to supporting the broadest range of supported installations and need to be handled with care.
The server team is investigating matters and current best practices and compatibility matrixes. Implementing a new cert for these servers is something that will unlikely happen within the next months, though.
Your suggestion to decouple translations from the TYPO3 runtime instance to prevent connections to the localization server is something we should address.
We have a CLI command (“bin/typo3 language:update”), which however is currently bound to the runtime instance as you pointed out. It uses registry informations of the database.
This would not need to be a hard requirement in the future, and the CLI command could be improved to make this adaptable without a database connection. This would then allow to bundle files and upload them in the deployment step.
Additionally, we would need a new setting (for system maintainers) to disable localization handling from the install tool / backend GUI for these cases. And clear specification (documentation) about which directories/files are needed to be deployed to servers.Another way could be to allow configuration of localization servers, and allowing custom mirrors that you could setup locally. Then the GUI could stay intact, and your own infra would deliver xlff files. This would need attention from the localization team, and see how/if crowdin as the source might already easily allow this (so your network could re-route requests to a different host than localize.typo3.org).
Would you be interested in providing help (patches or by sponsorships) to move forward with this to implement your needs? That would maybe help to move things forward in the timeframe you asked about.
-
Andri Steiner commented <span data-processor="relativetime" data-value="2025-07-04T12:53:37+00:00" > 07/04/25, 12:53 </span>
Server team here, we finished the aforementioned investigation. It is not possible to adjust these settings on the current server; however, we prepared the required options for the next version. This new server version will be based on Debian 13, which is not released yet. After the release, which will be presumably later this summer, we have to migrate localize.typo3.org and any other websites on this server to the new version. Assumed that there are no other (client-) compatibility issues coming up, we can complete this migration during the on-site community sprint in November at the earliest.
-
Georg Ringer changed status
Needs FeedbackIn Progress <span data-processor="relativetime" data-value="2025-08-06T09:38:35+00:00" > 08/06/25, 09:38 </span> -
Georg Ringer commented and changed status
In ProgressClosed <span data-processor="relativetime" data-value="2026-10-07T09:09:27+00:00" > 10/07/26, 09:09 </span>after talking to the server team: this will be solved next year with upgrade of the OS. closing the issue as the server team is doing their own tasks
(I’ve pinged the server team about this)