Telekom Security preliminary incident report: OCSP responder used incorrect signature algorithm for P-384 signing key
Deutsche Telekom Security GmbH opened this case after receiving a Certificate Problem Report about its OCSP responder producing non-compliant OCSP responses. The report said the responder used an incorrect signature algorithm for a P-384 signing key, contrary to the Baseline Requirements requirement that P-384 signatures use ECDSA with SHA-384 and a specific AlgorithmIdentifier encoding. The incident was disclosed as third-party reported, not self-discovered. Telekom Security filed a preliminary incident report and said it needed more time to complete the full incident report. It stated that the full report would be provided no later than 2026-10-23.
- A Certificate Problem Report was received about non-compliant OCSP responses using an incorrect signature algorithm for a P-384 signing key.
- Telekom Security opened a preliminary incident report describing the OCSP responder issue.
- Telekom Security said it would provide the full incident report by this date.
- Telekom representative — Reported that the OCSP responder used an incorrect signature algorithm for a P-384 signing key and identified the case as third-party reported.
- Telekom representative — Said more time was needed to complete the full incident report and promised it by 2026-10-23.