1. Introduction
Deutsche Börse continuously strengthens its SSH server security by updating configurations and deactivating outdated ciphers, key exchange algorithms, and MAC algorithms.
To ensure secure and reliable connectivity to the Common Report and Upload Engine (CRE & CUE), Deutsche Börse will remove the deprecated “SSH rsa” key type and the “Diffie Hellman Group 14 with SHA-256 hash” Key Exchange Method from its SSH 2.0 connectivity suite, effective 31 August 2026.
2. Required action
To access CRE and CUE, Trading Participants must upload a compliant SSH key in the Member Section. The following key types are supported:
A. Ed25519 (Edwards Curve 25519)
Modern elliptic curve key and signature algorithm based on EdDSA/Curve25519.
Offers strong cryptographic security, small key sizes and fast authentication.
B. OpenSSH SSH 2 RSA (minimum 4096 bits)
Must use SHA256, SHA384, or SHA512 as the signature algorithm.
No maximum key length is defined.
Trading Participants must ensure that all SSH keys fully comply with the current CRE/CUE security requirements. Non-compliant keys must be replaced. Trading Participants remain responsible for maintaining secure key management practices.
3. Details of the initiative
The above-mentioned changes will be transparent for users of standard SFTP or SSH clients. However, participants using scripts with hard coded key types or Key Exchange Methods must review and update their scripts accordingly.
Please note:
Further information
Recipients: | All Frankfurt Stock Exchange (Frankfurter Wertpapierbörse, FWB®) Trading Participants and Vendors | |
Target groups: | Traders, Technical Contacts, Security Administrators, System Administrators | |
Contact: | Your Technical Key Account Manager via VIP number or cts@deutsche-boerse.com | |
Web: | ||
Authorized by: | Quinten Koekenbier, Frank Hoba |
Market Status XETR ⓘ
XETR
The market status window is an indication regarding the current technical availability of the trading system. It indicates whether news board messages regarding current technical issues of the trading system have been published or will be published shortly.
Please find further information about incident handling in the Emergency Playbook published on the webpage under Data & Tech > Information Channels > Emergency procedures. Detailed information about incident communication, market re-opening procedures and best practices for order and trade reconciliation can be found in the chapters 4.2, 4.3 and 4.5, respectively. Concrete information for the respective incident will be published during the incident via newsboard message
We strongly recommend not to take any decisions based on the indications in the market status window but to always check the production news board for comprehensive information on an incident.
An instant update of the Market Status requires an enabled up-to date Java™ version within the browser.