> 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-cics-en/utilities-and-codes/appendix-d.-cryptography-system-in-onesait-editran/conclusions-and-application-in-onesait-editran-parameterization.md). # Conclusions and application in Onesait ยท Editran parameterization When in an editran session we indicate: * Confidentiality algorithm (TD3C) we are indicating the algorithm to encrypt the data (TD3C = triple DES with a 24-octet key). * Authentication algorithm (DES, RSA) we are indicating the algorithm to authenticate the data (and to encrypt the operational data) Data encryption (confidentiality algorithm) can be done: * In editran, by taking the application file and encrypting it so that it is stored encrypted in the buffer file In this way, it is recommended (some of the values depend on V 3.00 or 4.00): * In editran, indicate CRYPTOGRAPHY = S, CONFIDENTIALITY = XXXX (TD3C, AES1, AES2, AES3), AUTHENTICATION = XXXX (DES, RSA). The rest of the parameters; KEY INTERFACE, PARM, LOCAL key, REMOTE KEY, will depend on other factors, which are explained later, Other recommendations: 1. When we use cryptography 3.0 or 4.0 (parameter CRYPTOGRAPHY VERSION: 3.00 or 4.0), as we have seen, at least the parameters CRYPTOGRAPHY, CONFIDENTIALITY, and AUTHENTICATION come into play. > If the CRYPTOGRAPHY VERSION: 3.00 or 4.00). If CRYPTOGRAPHY is set to S, whatever is in the confidentiality algorithm will be used. The possible values are TD3C (encrypts the buffer data), TD2C (with double DES key), DES (with simple DES key), AES3 (encrypts the buffer data), AES2 (with double AES key), AES1 (with simple AES key), and spaces (does not encrypt them). What is indicated in the authentication algorithm also comes into play. The possible values are DES or RSA, and logically a value consistent with the keys that have been exchanged must be entered. 3. In cryptography 3.0 and 4.0, if we have indicated CRYPTOGRAPHY S and CRYPTOGRAPHY VERSION: 3.00 or 4.00, other values also come into play, depending on the authentication algorithm and the way we have exchanged the key (transport or exchange): > * If we carry out an external DES or RSA key exchange, without key-exchange management, the values LOCAL KEY and REMOTE KEY also come into play. In those values, the following will be indicated: > * If authentication is DES > * In local key, the label of the generated DES local key sent to the remote side is indicated. (the remote side will insert that key into its key system with whatever label it wants and will encode that label in its remote key). > * In remote key, the label is indicated with which we have incorporated into our key system the DES key sent to us by the remote side (and which the remote side will have placed with its label in its local key parameter) > * If authentication is RSA > * In local key, the label of the generated RSA private key is indicated and not sent to the remote side. The remote side will incorporate the public part of that key (which we sent) into its key system, with whatever label it wants in the remote key field). > * In remote key, the label is indicated with which we have incorporated into our key system the RSA public key sent to us by the remote side (and which the remote side will have placed the label that contains the private part of that public key it sent us in its local key parameter) > * If we carry out an external RSA key exchange, with key-exchange management, only the KEY INTERFACE and PARAMETERS fields come into play. In those values, the following will be indicated: > * In editran, KEY INTERFACE ZTBGBIGC (program that is responsible for determining in editran which is the active key of the exchanged subsystems > * PARAMETERS, \*, A, B will be indicated, A being the exchanged local subsystem and B being the exchanged remote subsystem. --- # 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-cics-en/utilities-and-codes/appendix-d.-cryptography-system-in-onesait-editran/conclusions-and-application-in-onesait-editran-parameterization.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.