> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-iseries-en/gestor-de-claves/appendix/verification-of-exchanged-keys.md). # Verification of exchanged keys When 2 entities have used key exchange, they can validate as follows, in case the cryptography fails: * In **editran, you must have the following values set:** encryption = **‘S’,** version = **400**, editran-gc = ‘**Y**’, local-subsystem, remote-subsystem and appropriate algorithms. * If one endpoint has set **local-subsystem = P,** **remote-subsystem = D** of an encrypted session, on the remote entity, they must have set **the inverse value**, that is, D,P. * Once the above values have been agreed upon: * Query the version and key sent in one direction. * The local endpoint queries the subsystem it has with the remote entity, for example, subsystem p (option 2 for RSA and 3 for DES). * The remote endpoint queries the SAME subsystem (option 4 for RSA or 5 for DES). * At both ends, the same ACTIVE VERSION MUST APPEAR. If not, activate one manually, agreeing on both ends so that the same version remains active at both ends. * Select the version label (module-exponent calculation for RSA and encryption for DES). Both ends must “display” the same thing. * Query the version and key sent in the other direction. * The remote endpoint queries the subsystem it has with our entity, for example, subsystem p (option 2 for RSA and 3 for DES). * The local endpoint queries the SAME subsystem (option 4 for RSA or 5 for DES). * At both ends, the same ACTIVE VERSION MUST APPEAR. If not, activate one manually, agreeing on both ends so that the same version remains active at both ends. * Select the version label (module-exponent calculation for RSA and encryption for DES). Both ends must “display” the same thing. Example: * If they work, leave TELEGC with CRIPTO N. * Agree to modify ALL SESSIONS with the following values: * EDITRAN: CRIPTO S, Crypto Version 4.0, confidentiality AES3, Authentication RSA4, Local subsystems=N, Remote subsystems=N
Check that the next transmission in both directions works properly. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-iseries-en/gestor-de-claves/appendix/verification-of-exchanged-keys.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.