> 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/open-v5.3-en/linux/plataforma.md). # Editran/P Management ## Onesait Editran/P Manager The Editran/P manager is presented below: ![assets/image4.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-d02990b4e0b1b888723531dd87551c957e96d798%2Fimage4.png?alt=media) If this is the first time Editran is going to be started, it is necessary to enter the local environment data by following these steps: * Editran requires the license service to be active in order to work with profiles; to activate it, the following command must be run from ***\*****/bin**: `EDItran -l start` The message `Starting License Server... [OK]` to indicate that the license service is active. * Register the local environment as described in the chapter [Local Environment](#entorno-local). * Start Editran again from ***\*****/bin**: with the command: `EDItran start` At this point, startup should finish without any kind of error, displaying the final message `EDItran system started`. ### User interface description #### Screens In Editran UNIX screens, three areas can be distinguished: * **(1) Title** The title area displays general information about the EDITRAN system: * Current date and time (at the moment the screen is activated). * Screen object: administrator, operator, etc. * Version and operating system. * **(2) Options** In this area, the different menu options may appear, the parameters the operator must enter, or the results of the requested queries. * **(3) Information** This area displays the information EDITRAN sends to the operator: * Session. * Transmission and reception statuses. * Transmission and reception counters. * Information text or messages from the remote operator. #### Help EDITRAN UNIX has a context-sensitive help system. Thus, when the keys **F1** or **?** are pressed, a window appears with the help text associated with the field or screen where the cursor is currently located. #### Keys In Editran UNIX within the menu, the following keys can be used: | | | | ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **F1, ?** | Context-sensitive help. | | **F2** | Enters the default values for the current field, whenever possible. | | **F3** | Ends data entry for the current screen, validating all fields. | | **F4** | Enters the default values for the entire current screen, whenever possible. | | **F6** | Performs an exit to the operating system to execute other commands (shell), leaving EDITRAN resident. To return to EDITRAN, the command must be executed **exit**. | | **Enter** | Ends data entry for the current field, updating its value. If no value has been entered, it inserts the value from the last request. | | **Space** | Selects the field value from a list of enumerated values: A (**or**) B ( ) C ( ) or enables/disables the field value for only two possible values: D \[**X**] | | **Esc** | Aborts data entry and returns to the previous menu. | | **Delete** | Deletes the character before the cursor | | **Tab** | Moves to the next field without updating or modifying the value. | | **Arrow keys** | Move the cursor on the screen to the next/previous field or to the next/previous value within the field. | |

PgUp
Ctrl-U

| Page up. | |

PgDn
Ctrl-D

| Page down. | ### Onesait Editran/P Operator To manage exchange sessions, option 1.- OPERATOR from the main EDITRAN/P MANAGER menu will be selected, presenting the following options: ![assets/image5.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-9aa2d78fdfdf96787f4fd39f76dbbaeb48315dc1%2Fimage5.png?alt=media) #### Session inquiry Select option 1.- SESSION INQUIRY from the menu. The inquiry of active sessions can be performed in a general or specific way. To inquire about a specific session, enter the SESSION and press Enter. The information area of the screen (bottom section) will display the status information and the emission and reception counters of the requested session. For a general inquiry, complete the SESSION field with zeros. ![assets/image6.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-09d1a09fb15546841c3f0bcd8c94eeda764a60ad%2Fimage6.png?alt=media) #### Connection request To manually establish the physical connection with a remote Editran, select option 2.- CONNECTION REQUEST from the EDITRAN OPERATOR menu. This request is generated automatically when an emission or reception request is made if the value S is specified in the AUTOMATIC CALL parameter of the session profile. The information area shows indications about the result of the request (connection made or not). #### Release request To manually release the existing connection for a session, select the option **3**.- RELEASE REQUEST from the EDITRAN OPERATOR menu. #### Emission request To start the local emission of a file, select option 4.- EMISSION REQUEST from the EDITRAN OPERATOR menu. The request is not allowed when the operating mode of local Editran is Server. #### Reception request To start the reception of a file, which must be emitted by the remote side, select option 5.- RECEPTION REQUEST from the EDITRAN OPERATOR menu. The request is not accepted when the operating mode of local Editran is Server. #### End of emission To request forced termination of local emission (emission interruption), select option 6.- END OF EMISSION from the EDITRAN OPERATOR menu. The request is not accepted when the operating mode of local Editran is Server. #### End of reception To request forced termination of local reception (reception interruption), select option 7.- END OF RECEPTION from the EDITRAN OPERATOR menu. The request is not accepted when the operating mode of local Editran is Server. #### Message for the remote operator A connection to the remote Editran intended to receive the operator message is required. The following screen will appear, where the text to be sent will be written: ![assets/image7.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-6d210240b0ee79ec46773876a6132826fe520c40%2Fimage7.png?alt=media) #### Inquiry of remote emission file To inquire about the remote emission file, select option E.- INQUIRY OF REMOTE EMISSION FILE from the EDITRAN OPERATOR menu. The local Editran program will send the inquiry message to the remote side, and the local side will wait to receive the response from the remote side. This response will be displayed on the next screen. A connection between both ends must have been previously established. #### Inquiry of remote reception file To inquire about the remote reception file, select option R.- INQUIRY OF REMOTE RECEPTION FILE from the EDITRAN OPERATOR menu. The local Editran program will send the inquiry message to the remote side, and the local side will wait to receive the response from the remote side, which will be displayed on the next screen. A connection between both ends must have been previously established. ![assets/image8.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-5527357c4e9a15b63c514df6e9b6ad95e9d9e61f%2Fimage8.png?alt=media) ### File inquiry From option 2.- FILE INQUIRY of the EDITRAN/P MANAGER, the following options are shown. ![assets/image9.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-1bed8a386ea04154b34623f3feba64b13c309959%2Fimage9.png?alt=media) #### Inquiry of the emission/reception log To obtain information from the control log of the local emission or reception buffer file, select option 1.- INQUIRY OF EMISSION/RECEPTION LOG from the FILE INQUIRY menu. ![assets/image10.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-38a9ea8b75c73a8ca90fd5708eb653dc2d031c8b%2Fimage10.png?alt=media) Two screens will be displayed with the control log data for the local emission or reception file for the specified session. For an inquiry of the local emission file (when entering an E in the FILE field) For an inquiry of the reception file (when entering an R in the FILE field) #### Log file inquiry. All informative messages that Editran has sent to the operator are displayed. To consult these records, select option 2.- LOG INQUIRY from the FILE INQUIRY menu. ![assets/image11.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-a7bfa894288b4566d04885d6d6d89a830c7eb716%2Fimage11.png?alt=media) The SESSION, DATE and TIME fields may optionally be filled in. If no filter is specified, the last recorded entries will be shown. In the case of a general inquiry, enter zeros in the SESSION field. To display more records, use the PgDn/Control-D keys to move forward or PgUp/Control-U to move back. The file **editranp.log** is treated cyclically. ![assets/image12.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-182878573631a6e450bd8627c0402e24f23d2097%2Fimage12.png?alt=media) #### Generic session inquiry All sessions defined in the profile file are displayed. To consult these records, select option 3.- GENERIC SESSION INQUIRY from the FILE INQUIRY menu. ![assets/image13.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-1fb21ae6aef3b6a06470997ed463e8e2d9f304dd%2Fimage13.png?alt=media) ### Onesait Editran/P Administrator To access the Editran administration menu, select option 3.- ADMINISTRATOR from the main EDITRAN MANAGER menu. The following options will be displayed for managing Local Environment and Session parameters. ![assets/image14.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-2e459af8ba2e78f04adeb8143095d2664460fdb4%2Fimage14.png?alt=media) #### Local Environment The Primary Local Environment of Editran/P is managed from option 1.- LOCAL ENVIRONMENT of the ADMINISTRATOR menu. In those entities that have multi-environment licensing, that is, the possibility of being presented as several centers, it is not necessary to define a specific profile for secondary environments; it will be enough to specify the new code in the corresponding sessions. Enter the following requested data: ![assets/image15.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-c10383fead2879883c6c8cd9bf0a93e15457b350%2Fimage15.png?alt=media) * **LOCAL** The identification number of the Editran user entity will be entered. With this identification number it will be recognized by all interconnected entities. Editran entity codes consist of nine characters (NIF) with the following format **xnnnnnnnx**. * **NAME** The installation description will be entered. This field is for information only. * **MAXIMUM NUMBER OF SESSIONS** The maximum number of exchange sessions that can be run concurrently at a given time can be specified. * **IP ADDRESS** The address of the local machine in a TCP/IP network, supports up to 3 different addresses with 3 listening ports for each address. * **TCP CONNECTION TOUT** It is the maximum waiting time from when the connection of a *socket* remote until the session data are exchanged, which definitively establish a TCP connection in Editran/P. This timeout prevents other applications from connecting indefinitely to the port used by Editran. If you do not want to enable this timeout, set it to 0. #### Sessions To be able to connect and perform transmissions and/or receptions with a remote Editran, the parameters that describe the session profile must be specified, and it is essential to have previously registered the local environment (see [Local Environment](#entorno-local)). As many sessions as different connections you want to establish must be registered. Select option 2 from the EDITRAN ADMINISTRATOR menu. ![assets/image16.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-30cea543052a142101b02b3d0552a4e870fe213a%2Fimage16.png?alt=media) Once selected, the screens will appear where the user can fill in or view (depending on the chosen option) the parameters or characteristics that define the session. ![assets/image17.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-565a23082d79456b06dcd70a8df009e6b26e39f8%2Fimage17.png?alt=media) In all options, the following must be specified: * **SESSION** Session identification. Except for adding a new entry, a search filter may be specified; in that case, the list of sessions matching the mask will be shown so the user can choose. In A.- Add and M.- Modify, all fields except the Session identifier appear unprotected. To perform the option, you must reach the last screen. In C.- Query, all fields appear protected. The first screen shows the parameters affecting the connection: ![assets/image19.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-9ee8a43d514620cf489e85e40107ee946353b13f%2Fimage19.png?alt=media) * **LOCAL** Identification code of the local center. * **LOCAL NAME** Name of the local center associated with the session. This field is for information only. * **REMOTE** Remote center identification code. * **REMOTE NAME** Name of the remote center associated with the session. This is for information only. * **APPLICATION** Identification code of the application that uses the transmission service of the editran system. * **APPLICATION NAME** Name of the user application. This is for information only. * **VERSION NUMBER** Version of the remote Editran/P system. It can be 5.3, 5.2, 5.1, or 5.0. It must match the corresponding value in the remote session. * **CALLING PARTY (L/R/X)** * **L** Only the LOCAL end can call. * **R** Only the REMOTE end can call. * **X** Either end can call. * **TRAFFIC DIRECTION (E/R/X)** * **E** Only transmission is allowed in this session. * **R** Only reception is allowed in this session. * **X** Transmission and reception can be carried out simultaneously. * **AUTOMATIC CALL (S/N)** * **Y** The connection will be established automatically when the start of emission or reception is requested. * **N** A connection must be established before requesting transmission/reception. * **AUTOMATIC DISCONNECTION (S/N)** * **Y** The disconnection request is generated automatically when an emission or reception ends. * **N** The disconnection is not generated automatically. * **TIME-OUT (Seconds)** It is the time interval, expressed in seconds, during which editran waits to receive from the remote a response message to one previously sent control message. If the TIME-OUT period ends without a response being received, the same request will be sent again, starting a new waiting interval. Also equivalent for connection requests. * **MAX. NUMBER OF RETRIES** This is the number of times the previous TIME-OUT procedures are repeated. * **SAVE ROTATIONS (S/N)** * **Y** In the event of a call request, when the connection is eventually established through IP addresses that are not in the profile in the first position, they are saved in that position. The purpose is that, in later transmissions, the connection is achieved without call retries. * **N** In no case are the profile addresses updated. Once the values on this screen have been entered and validated, a new one will appear where the specific parameters for TCP are defined: ![assets/image20.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-aafa890ee25f55314b5037b13f4973bcf7940a92%2Fimage20.png?alt=media) * **REMOTE IP ADDRESSES** IP address and port of the remote side to connect to, with up to 6 different IP addresses allowed. * **VALIDATE REMOTE IP (S/N)** * **Y** For incoming calls, it is validated that the IP address of the entity attempting to connect is in the list of remote IP addresses. * **N** Connections from any remote IP are allowed. * **EDITRAN PROXY SERVER (S/N)** With value **Y** outgoing transmission requests will be made through an EDITRAN module (EDITRAN/PX) that acts as a proxy server. Incoming connections may arrive through the Proxy or directly, regardless of the value of this parameter. * **PROXY IP ADDRESSES** IP address and access port to the EDITRAN/PX server. Up to 2 possible addresses can be indicated. Once the network values have been configured, the screen appears where the session parameters that determine the general characteristics of the transmission are specified. ![assets/image21.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-3b3df264c3c0ed40d3fdeb9b2006b7bb76b7eccc%2Fimage21.png?alt=media) * **SERVER/CLIENT (OPER)** Operating mode: * **Y** Neither emissions nor receptions can be requested (server). * **C** Both transmissions and receptions can be requested (client). * **CRC (S/N)** * **Y** The cyclic redundancy code will be generated for each transmitted message; the CRC of each received message will be validated. * **N** The CRC is not calculated for outgoing messages nor validated for incoming messages. * **COMPRESSION (S/N/V)** * **Y** Compressed transmission of data. * **N** The data are transmitted in the application’s original format. * **V** The data are transmitted compressed or in the original format depending on the best result obtained. * **ASCII/EBCDIC (A/E)** * **A** The remote side uses the ASCII alphabet (Unix and Windows environments). * **E** The remote side uses the EBCDIC alphabet (CICS, IMS and iSeries environments). * **START TIME (HH:MM:SS)** Specifies the time of day from which transmission can be started, expressed in hours (HH), minutes (MM), and seconds (SS). * **END TIME (HH:MM:SS)** Specifies the time of day limit until which transmission can be started, expressed in hours (HH), minutes (MM), and seconds (SS). * **BUFFER LENGTH** Length of the records in the buffer files. Values from 13 to 9999 bytes are allowed (with versions later than 5.2 only a value equal to or greater than 4050 is valid, and in HOST environments only 4050). * **EMISSION BURST** Emission burst length (number of records emitted before receiving acknowledgment from the remote side). * **SYNC TOUT (Seconds)** This is the time interval, expressed in seconds, during which EDITRAN waits to receive from the remote side a synchronization message for the sending of a block of data (burst). If no response is received by the end of this time, the data are sent again, up to the configured number of retries. Once the session parameters have been configured, the screen appears where the session parameters that determine the general characteristics of the cryptography are specified ![](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-ddb2f42086c25e2a24fb9d70d133bdc2a3aaaed4%2Fimage22.png?alt=media) The parameters that appear on the screen are: * **CRYPTOGRAPHY (S/N)** * **Y** If you want EDITRAN/P cryptography. * **N** If you do not want to use EDITRAN/P cryptography. * **CRYPTOGRAPHY VERSION** This field is mandatory if Cryptography is enabled. * **3.0** Cryptography compatible with CRIPTO/lib V3.0. * **4.0** AES encryption and RSA keys of 2048 and 4096. * **EDITRAN/GC KEYS** When this facility is selected, the EDITRAN/GC module will be responsible for providing the corresponding labels for the active keys for the subsystems indicated in the LOCAL KEY and REMOTE KEY parameters. * **Y** Labels provided by EDITRAN/GC. * **N** Labels provided by the user. * **ENCRYPTION ALGORITHM** Algorithm to use to encrypt the data. Leave blank to transmit without encryption. * **TD3** DES encryption with triple key. * **AES** AES-128 encryption. * **AE2** AES-192 encryption. * **AE3** AES-256 encryption. * **AUTHENTICATION ALGORITHM** Algorithm used to protect the session key and the exchanged data to authenticate the ends. It is mandatory if a confidentiality algorithm exists. * **DES** if you want to authenticate the ends with the DES algorithm (valid with cryptography version 3.0). * **RSA** if you want to authenticate the ends with the RSA algorithm (valid only for version 3.0 and 4.0). * **LOCAL KEY** Label of the DES auxiliary key or the RSA private key. Mandatory when the cryptography version is 3.0 or higher and there is authentication. * **REMOTE KEY** Label of the DES auxiliary key or the remote RSA public key. Mandatory when the cryptography version is 3.0 or higher and there is authentication. ## Appendices ### Onesait Editran Components #### Current scheme Editran is a modular product. There are a series of components that we understand as the most common (G, P, TCP/IP and Proxy), which are acquired by the vast majority of customers (although some decide not to have the Proxy), and additionally there is another series of modules that help improve the product's Security, Control, or Functionality. ![assets/image23.png](https://780925830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiQfLim2uDaLOZRkgWkOk%2Fuploads%2Fgit-blob-97a616d282a35df6276ec00ba25b1364b37faeee%2Fimage23.png?alt=media) ### Commands #### EDItran It is the script that starts and stops the Editran system. **Syntax** The command syntax is: ```bash Usage: ./EDItran [-l] [-t] [-f] start|stop|status|version -l Operation restricted to the License Server -t Trace -f Ignore another EDITRAN already started start Starts the service stop Stops the service status Gets the service status version Displays the EDITRAN system version ``` #### editranp Main process of the Editran system. It handles communication with the different communication processes and with Editran/G. It is launched in the background when the Editran system starts. #### editcp Communications process when the protocol used for the connection is TCP/IP. #### makelog Creates an event file called editran.log that will contain a summary of the operations performed using editran. **Syntax** The command syntax is: ```bash Usage: makelog [-P] [-G] [-n <#entries>] [-v] Where: -P : EDItran/P log -G : EDItran/G log -n <#entries> : Number of entries -v : Verbose By default, the two files are created with 200 entries ``` where **<#entries>** is the maximum number of entries (number of events) you want to keep in the file. **Example** An event file, editran.log, is to be created with a capacity for 500 different entries. The command must be executed: `makelog -n 500` When using the system with a large number of simultaneous sessions, it is recommended to use 500 entries. #### menup Allows direct access to the Editran manager menu. #### menucmd Establishes a communication mechanism between applications or user programs and editran/P, allowing operations to be invoked unattended and automatically. **Syntax** The command syntax is: ``` Usage: menucmd {E00|E11} menucmd EOP ``` If we have `menucmd** s session x`: **s** is the signal sent to request an operation from editran, **session** is the session and **x** other options that depend on the type of operation or signal requested from editran. The possible signals are: * **E00** requests a connection request from editran. * **E11** requests a release request from editran. * **EOP** requests editran to send a message to the remote operator. #### copycfg Utility to copy Editran profiles from another one used as a template. **Syntax** The command syntax is: ``` copycfg -s source_ses [-d destination_ses] [-n] [-r remote_code] [-p | -a] Meaning: -n : number of sessions to create. -s : source session. -d : destination session. -r : destination remote code. -p : copies only editran/P sessions -a : creates editran/G applications ``` This command allows Editran profiles to be registered starting from a session taken as a template. The source session is given in option **-s**. By default, the Editran/P Session and its corresponding Presentation in Editran/G are created, but this behavior can be changed using option **-p** if only the session profiles are to be created. The profiles created will depend on the chosen option: * **Option -n*****\***: Sessions are created *\* Sessions. These sessions are named the same as the original, adding an index. For example, if we start from PRUEBA and want to generate 5 more, they will be created from PRUEBA-1 to PRUEBA-5. * **Option -d:** In this case the user decides the name that the created session will have, but this option is incompatible with the previous one. * **Option -r:** By default, created sessions are generated with the same local and remote code as the original. With this option, the user is allowed to change the remote code of the new profile. * Example **Example** To duplicate the INDRA-TEST session for a different remote by naming the new one editran-TEST, run:\ `copycfg -s INDRA-TEST -d editran-TEST -r 000001230` To create 10 sessions starting from PRUEBA, run: `copycfg -s PRUEBA -n 10` #### printcfg Editran session printing utility. **Syntax** ``` Usage : printcfg [ -grapsv ] Where: -g : EDItran/G presentations. -r : EDItran/G remotes. -a : EDItran/G applications. -p : EDItran/P local. -s : EDItran/P sessions. (Default) -v : Prints headers. ``` **Example** ``` SESSION LOCAL REMOTE APP LOCAL DIR REMOTE DIR ================================================== INDRA-TEST W00005100 000099990 PRUEBA TCP editran.indra.es ``` #### resetkey Reinitializes the encrypted exchange keys of a given session. It must be used with great caution, since it leaves the keys in a state different from the original. It is essential to perform the same operation at the remote end so that synchronization in the key exchange is possible. It should only be executed if this is the first time the keys are used, or if the keys from the last exchange in the profiles file have been lost. **Syntax** The command syntax is: `resetkey [session]` where session is the editran/P session. It must be written in uppercase, and if it contains any spaces, in double quotes: " **Example** In an installation, it is desired to set the key of session TEST-INDRA to an initial value. The command must be executed: `resetkey TEST-INDRA` #### importkey The file *ckds.des* keeps the master key and DES auxiliary keys in the editran system. In version 5.02 the format has changed so that simple and double keys can be stored. Therefore, in some cases it may be necessary to import keys from previous versions. For security, to export the keys the user must know the value of the HMK it stores and must provide the first two octets in hexadecimal as the password to access the file. It can be passed as a command argument, but if it is not provided the user will be prompted. **Syntax** The command syntax is: ``` importkey. DES key import command Usage: importkey [ -s ] -k -f [--] [tags] -- : End of options. The rest of the arguments are tags -s : The source file contains simple keys -k : File access key (HMK) -f : File that stores the keys to be imported tags: Tags of the keys to be imported ``` If no tag is provided, the command incorporates all the keys in the source file whose tag is not SI0000000000XX. If the tag of the key to be imported already exists in the destination file, the key will be updated with the value of the old one. **Example** To incorporate the auxiliary key used by editran for sessions with cryptography 2.2, run the command: `importkey -s -fc:\editran.520\ckds.des SI000000000016` To incorporate the user auxiliary keys by giving the access password as an argument, run: `importkey -s -fckds.des.520 -kA1A3` #### printlog Editran log printing utility. **Syntax** ``` printlog. EDItran log display command Usage: printlog -P|G [-s session] [-f DDMMYYYY] [-h HHMMSS] Meaning: -P EDItran/P log -G EDItran/G log -s session -f date DDMMYYYY -h time HHMMSS All parameters are optional ``` #### NL filter The filter **nl** is used to convert lines from one system to another. This filter is limited to reading and writing lines. The usefulness of the filter lies in the physical difference between systems when representing text lines. In general, a file containing lines is structured in one of two ways: With fixed-length records (a fixed number of characters is always stored for each line; for example, 100 characters for each line). With variable-length records (end-of-line delimiters are used to separate the lines). These in turn have different separators in each system. The filter knows those used by UNIX. To use the filter, simply tell it which starting structure to use (e.g. fixed records of 50 characters, or variable records with UNIX-type delimiter) and the structure we want to obtain. The filter will change the file structure to obtain the desired structure with the same content in each line. **Syntax** ``` File Format Conversion Command Usage: nl [ -<#> | -v ] -i -o [--] [files] -- : End of options. The rest of the arguments are files -<#>: Records of # length (fixed) without counting delimiters (Ex.: -80) -v : Variable-length records (default) -i: Input format (Ex.: -id) -o: Output format (Ex.: -on) can be: u (UNIX), d (MSDOS), n (no delimiter) files: Files to translate (stdin->stdout by default) ``` To indicate the type of record we are going to use (fixed or variable), we use the following options: * **option -#** (where # is a number, e.g. 80): fixed records of # characters. * **option -v**: variable records. * To indicate the end-of-line delimiter used in the input file, the **option -iX** (where X is 'n', 'u' or 'd'). * If X is n, the filter expects there to be no end-of-line delimiter in the input file (in this case -N must have been used to indicate the record length, since it must be fixed-length records). * If X is u, the filter expects there to be a '\n' delimiting each record. (unix type). * If X is d, the filter expects there to be a '\r\n' delimiting each record. (MSDOS type). * To indicate the end-of-line delimiter to use in the output file, the **option -oX** (where X is 'n', 'u' or 'd'). * If X is n, the filter does not write any delimiter after each line. * If X is u, the filter writes a '\n' after each record. * If X is d, the filter writes a '\r\n' after each record. #### ediperfi It is the command for managing Editran/P profiles. You can consult the User Guide Profile Management for more information about this utility. ### Data files #### CFG subdirectory * **editranp.cfg** Editran configuration file. Stores the local profile and the profiles of sessions for remote entities. Used exclusively by Editran. * **editranp.sdx** Editran configuration index file. * **ckds.des** File where the Auxiliary exchange keys of the encrypted editran sessions are located. #### BIN subdirectory * **editranp.msg** File where the messages that editran presents to the editran operator are stored. Used exclusively by editran. **SL subdirectory** * **licencia.dat** Editran license file. It is used to control the contracted functionality. If this file does not exist or its contents are altered, the Editran service cannot be started. #### LOG subdirectory * **editranp.out** File where all outputs produced by the process are recorded **editranp** and the procedures and commands launched by this process. It is generated by redirecting the standard output of the process **editranp**. * **editranp.log** File created by the command **makelog**. It cyclically stores the summary of the operations performed by EDITRAN, so once the maximum number of entries is reached it overwrites the oldest one. It can be consulted from the editran menus and using the command ***printlog***. ### Codes and messages to the operator These codes are the ones reflected in the file **editranp.log** to indicate the different states through which a session passes. On the editran/P operator screen, they appear in the form of messages. The messages are listed below, giving a brief explanation or recommended action, as appropriate: *** | MESSAGE | EXPLANATION/RECOMMENDED ACTION | | --------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Association established | Local association request accepted by remote end. | | Remote association accepted | Association between applications accepted by the local end. | | Start of transmission | Transmission to the remote starts. | | Connection established | A circuit has been established with the remote | | Remote connection rejected (Profiles) | Discrepancy in the remote and local profiles | | Status query | Response to a query about the status of a session | | Remote sender file query | The control record query of the remote transmission buffer file has been requested. | | Remote receiver file query | The control record query of the remote reception buffer file has been requested. | | Totals mismatch in sender process | In applications with total control, the confirmed exchanged totals do not match (synchronization) | | Totals mismatch in receiver process | In applications with total control, the confirmed exchanged totals do not match (synchronization). | | Transmission aborted | The transmission of a file to the remote has been aborted | | Transmission successful and finished | A transmission has finished successfully | | Local transmission | Start of local transmission of a file | | Error opening file | An error occurred while opening a file | | Error closing file | An error occurred while closing a file | | Error writing file | An error occurred while writing to a file | | Error reading file | An error occurred while reading from a file | | Error in execution of the *SCRIPT* | An error occurred while running a shell script. | | Error in remote batch process | An error occurred while running a remote shell script. | | General interface error | An error occurred while running a shell script. | | Remote cryptography error (ERR##) | A cryptography error has occurred. See section [Cryptography Errors](#errores-de-criptografía) | | Remote compression/decompression error | A compression/decompression error occurred at the remote end. | | Connection retries exhausted | Connection retries have been exhausted, according to the number of retries in the editran session profiles. | | Synchronization retries exhausted | Synchronization retries have been exhausted, according to the number of retries in the editran session profiles. | | Retries exhausted in sender process | Retries have been exhausted in the sender process for messages that require a response. | | Retries exhausted in receiver process | Retries have been exhausted in the receiver process for messages that require a response. | | Retries exhausted to transmit | Transmission start retries have been exhausted, according to the number of retries in the editran session profiles. | | Retries exhausted to establish session | Session establishment retries have been exhausted, according to the number of retries in the editran session profiles. | | Retries exhausted to end transmission | End-of-transmission retries have been exhausted, according to the number of retries in the editran session profiles. | | Retries exhausted to receive | Transmission start retries have been exhausted, according to the number of retries in the editran session profiles. | | Connection exists. Batch request ignored | A connection request has been made and it already exists. | | Invalid calling end (profiles) | Incompatibility in the values of that field in the profiles record. | | Profiles file is empty or does not exist | An error occurred when accessing the editran profiles file. | | Reception file not ready | The control record information exchanged between the two ends, in the transmission start request/response message, does not allow data exchange to start. Data exchange does not match. The exchange session number contained in the control records does not match. The send/receive file is not loaded, or is not available to editran (the batch process that is specified in profiles is triggered). | | Send buffer file not ready | Response to remote file query. | | Buffer files in incompatible state | The remote rejects the local request because its buffer file is not ready. It may have launched its corresponding prior automation for the request. | | End of transmission requested by operator | When the operator requests forced end of transmission | | End of transmission requested by remote operator | When the remote operator requests forced end of transmission. | | End of reception requested by operator | When the operator requests forced end of reception. | | End of reception requested by remote operator | End of transmission requested by the remote operator. | | End of local transmission requested by the remote | When the remote requests end of reception (end of local transmission). | | Remote transmission impossible due to profiles | Check the processes defined in the session profile. | | Remote reception impossible due to profiles | Check the processes defined in the session profile. | | Start of reception | When reception of the remote file begins. | | Remote application release | The connection has been released by the remote application. | | Transmission release XX XX | Circuit release message. | | Remote operator release | Occurs as a result of a release request by the remote operator. | | Release due to call crossing | There is a call crossing between the remote and the local, and only one is accepted. | | Release by the operator | Occurs as a result of a release request by the operator. | | Release due to compression error | Release is requested when an error occurs in the compression/decompression of a message. | | Release because another channel is established | A circuit is released because another one is already connected for a given session. | | Release due to invalid facilities | The type of facilities used when requesting the connection will be checked. editran will only manage reverse charging. | | Release due to incorrect schedule | Check the schedule given in the session profile and modify it. | | Release for not accepting reverse charging | Check the REVERSE CHARGING field in the session profile. | | Release due to no free channels | Circuit limitation. The connection can be established when another established session is released. | | Release due to network restart | A circuit release has occurred due to a network restart. | | Release due to invalid payment type (profiles) | Check the session PAYMENT METHOD in anticipation of conflicts. One end must support cost. | | Call rejected (invalid time) | Connection request outside the allowed time. Check profiles. | | Call rejected, invalid remote address (profiles) | Check the remote NRI/IP of the session in profiles. | | Remote call accepted | The remote connection request has been accepted. The connection is established. | | Remote call accepted (crossing) | Both ends requested the connection establishment and the local one was handled first. | | Remote call rejected (reverse charging) | The specification for that parameter does not match on both ends. | | Remote call rejected (crossing) | The incoming call from the remote is rejected. | | Remote call rejected (calling end) | The specification for that parameter does not match on both ends. | | Remote call rejected (payment type) | The specification for that parameter does not match on both ends. | | Local cannot transmit (profiles) | Transmission request rejected because the TRAFFIC DIRECTION parameter was not specified with value E or X or because the appropriate license is not available. | | Local cannot call (profiles) | Connection request rejected because the CALLING END parameter is specified as R, so only the remote can call. | | Local cannot receive (profiles) | Check the TRAFFIC DIRECTION parameter and the license for direction. | | Incorrect notification message | An error occurred in session establishment due to the notification message format. | | No connection exists | A request has been made that previously required the establishment of a connection. | | No session in profiles | Register the session in profiles. | | No resources available | The connection can be established once another already established one has been released. This is due to the limitation of physical circuits in the local environment. | | No network service | The local end does not have X.25 service. | | No session | The request requires the existence of a connection between applications. | | No post-transmission batch is launched | A transmission batch request has been received, which will not be processed because transmission is already in progress. | | No post-reception batch is launched | A reception batch request has been received, which will not be processed because reception is already in progress. | | No pre-transmission batch is launched | A reception batch request has been received, which will not be processed because reception is already in progress. | | No pre-reception batch is launched | A reception batch request has been received, which will not be processed because reception is already in progress. | | Connection pending | The request requires the existence of a connection between applications. The connection has not yet been completed. | | Lost sequence in sender process | A jump in the message sequence number has been detected. | | Lost sequence in receiver process | A jump in the message sequence number has been detected. | | Incompatible profiles (compression) | The value specified on both ends for the compression parameter does not match. | | Reception rejected by profiles (transmission direction) | The value specified on both ends for the transmission direction parameter does not match. | | Batch request for transmission download | A transmission download batch request has been received. | | Batch request for transmission start | A local transmission start batch request has been received. | | Batch request for reception start | A local reception start batch request has been received. | | Batch request for preparation and transmission start | A batch request has been received to launch a job specified in profiles. | | Batch request for preparation and reception start | A batch request has been received to launch a job specified in profiles. | | Post-transmission batch request | A batch request has been received to launch a job specified in profiles. | | Batch request after reception | A request has been received from the batch launch of a job that had been specified in profiles. | | Association request | A connection request between applications has been requested. | | Reception request | A reception request has been requested from the local or remote operator. | | Request not accepted. Server operating mode | An unauthorized request has been made in server operating mode. | | Post-emission finished successfully | A response is received from the batch confirming the successful completion of a process. | | Post-reception finished successfully | A response is received from the batch confirming the successful completion of a process. | | Pre-emission finished successfully | A response is received from the batch confirming the successful completion of a process. | | Pre-reception finished successfully | A response is received from the batch confirming the successful completion of a process. | | Start of session. Local emission | The first burst of the transmission has been sent. | | Remote operator network restart | A network restart requested by the remote operator has occurred. | | Reception aborted | Reception of a file has been aborted. | | Reception successful and completed | A file has been received successfully. | | Message received with invalid CRC | A message has been received from the remote in a session defined in profiles with CRC validation, and its CRC was incorrect. | | Incorrect message received from batch | Correct the A5P request type. | | Incorrect message received in sender process | Message out of protocol. | | Incorrect message received in receiver process | Message out of protocol. | | Remote without session / registered NRI (profiles) | The NRI of an incoming call does not match the one for the session registered in the profiles. | | SBP received in incorrect state | Message out of protocol. | | SBR with total mismatch | Negative response to a total synchronization because the totals in the receiver process do not match. | | SCP received in incorrect state | Message out of protocol. | | SEP received in incorrect state | Message out of protocol. | | Batch has been launched after emission | Batch process has been launched according to profiles. | | Batch has been launched after reception | A batch process has been launched according to profiles | | Batch has been launched before emission | A batch process has been launched according to profiles | | Batch has been launched before reception | Batch process has been launched according to profiles. | | Has already been called | A connection request has been received when a previous one for the same session was already being processed. | | The call is placed | An attempt is made to connect to the remote Editran system. | | Local key change requested | The local end has requested a key change in the application-to-application association establishment phase. | | Remote key change requested | The remote end has requested a key change in the application-to-application association establishment phase. | | Session rejected by profiles (Ascii/Ebcdic) | Correct the parameter in the session profile. | | Session rejected by profiles (CRC calculation) | Correct the parameter in the session profile. | | Session rejected by profiles (service quality) | Correct the parameter in the session profile. | | Session rejected by profiles (compression) | Correct the parameter in the session profile. | | Session rejected by profiles (totals control) | Correct the parameter in the session profile. | | Session rejected by profiles (cryptography) | Correct the parameter in the session profile (cryptography). | | Session rejected by profiles (record length) | Correct the parameter in the session profile. | | Session rejected by profiles (application type) | Correct the parameter in the session profile. | | Session rejected by profiles (connection type) | Correct the parameter in the session profile. | | Session rejected by profiles (version) | Correct the parameter in the session profile. | | Remote sender buffer inaccessible | An error occurred while accessing the remote send buffer file. | | Remote receiver buffer inaccessible | An error occurred while accessing the remote receive buffer file. | | Still transmitting | Request not processed because it is currently transmitting. | | Connection already exists | A connection request has been made to a session that was already connected. | | Already receiving | A duplicate request is received from the operator. | | Already transmitting | A duplicate request is received from the operator. | | Incorrect remote receiver file (prior launch) | The remote is preparing its receive buffer. | | Incorrect remote receiver file (no prior exists) | The remote does not have its receive buffer ready because it has no prior. | | Incorrect remote receiver file (prior possibly in execution) | The remote receive file is possibly being prepared. | | Incorrect remote receiver file (session no.) | The session number of the remote receiver file does not match the local one. | | Incorrect remote receiver file (total no. of records) | The total number of records in the remote receiver file does not match the local one. | | Incorrect remote sender file (prior launch) | The remote is preparing its send buffer. | | Incorrect remote sender file (no prior exists) | The remote does not have its send buffer ready because it has no prior. | | Incorrect remote sender file (prior possibly in execution) | The remote send file is possibly being prepared. | | Local Editran/G denies batch request | Editran/G does not execute the requested request. | | Buffer file loaded | Editran/G reports the loading of the send buffer. | | Error. encrypted sender buffer and profile without cryptography | IGA profile with cryptography and Editran profile without cryptography. | | Error. encrypted sender buffer and profile with key change | IGA encryption and key change in Editran are not allowed. | | Error. sender buffer key and transmission key differ | The key used by IGA to encrypt the buffer does not match the current Editran key. | | Error. sender buffer length and profile length differ | The length of the buffer loaded by Editran/G does not match the current length of Editran/P. | | Error. compressed sender buffer and profile with compression | The data has been compressed in Editran/G and compression is requested in Editran/P. | | Error. reception buffer length and profile differ | | | Error. encrypted sender buffer and profile with compression | The data has been encrypted in Editran/G and the Editran/P profile has compression. | | RTC - Port in use by another connection | The serial port is being used by another Editran connection. | | RTC - Port out of range | The port specified in the profile does not exist. | | Network adapter not installed or not operational | The network adapter (modem, X.25 card, etc.) is not working. | | RTC - The modem does not respond | The modem does not respond. | | RTC - Carrier not detected or lost | | | Error initializing the network adapter | | | RTC - No dial tone | | | RTC - Remote busy | The network identifies the called DTE as busy with other communications and therefore unable to accept the incoming call. | | RTC - No response from remote | | | RTC - Unrecognized modem response | | | RTC - Blank RTC number | | | X.28 - Release by the DTE(P) | The distant terminal equipment has released the communication. | | X.28 - Local procedural error | The DEP detects a procedural error caused by the DTE. | | X.28 - Network congestion | Condition produced within the network: due to temporary congestion. Due to temporary failure. | | X.28 - Out of service | The called number is out of service. | | X.28 - Remote procedural error | The network detects a procedural error caused by the DTE at the distant ETD/ETCD end. | | X.28 - Busy number | The network identifies the called DTE as busy with other communications and therefore unable to accept the incoming call. | | X.28 - Invalid facility request | Invalid facility requested by the calling DTE. | | X.28 - Access denied | The calling terminal equipment is not authorized to obtain communication with the called DTE. | | X.28 - Unobtainable | The address of the called DTE is not in the numbering plan or has not been assigned to any DTE. | | X.28 - Release by the PAD | The communication has been released by the local PAD in response to a release invitation from the distant DTE. | | X.28 - No reverse charge number | The called terminal equipment is not subscribed to accept reverse charging. | | X.28 - Incorrect IUR | The network user identifier is incorrect. | | X.28 - No additional information | Release with diagnostic 000 from the network. | | X.28 - Invalid command | Release with diagnostic 016 from the network. | | X.28 - Command not allowed | Release with diagnostic 032 from the network. | | X.28 - Timer expiration | Release with diagnostic 048 from the network. | | X.28 - Error connecting to the PAD | | | Session rejected by profiles (confidentiality) | Correct the parameter in the session profile. | | Session rejected by profiles (authentication) | Correct the parameter in the session profile. | | Session rejected by profiles (automatic disconnection) | Correct the parameter in the session profile. | | Session interrupted | Verify the interruption code | | Remote certificate accepted | The remote certificate is accepted correctly | | TCP - Connection reset | | | TCP - Destination address required | The remote IP address must be specified | | TCP - Address unavailable | The address being called is not available | | TCP - Network unreachable | The address being called is not available | | TCP - Connection refused | | | TCP - Host down | Check the status of the remote equipment | | TCP - No route to host | | | TCP - Host not found | | | TCP - Unrecoverable error | | | Incorrect local receiver file (total no. of records) | The total number of records at the sending end does not match the number of records expected to be received. | | Incorrect local receiver file (creation date) | The date of the local receiver file does not match the creation date of the remote end. | | Version ignored due to date control | | | Association timeout expired | | | Message received with unknown header | Invalid protocol message. | | Remote call rejected (network license) | The session does not have a license for the incoming call type. | | SWIFT -- GetFile request made | Informational. | | SWIFT -- GetFile request received | Informational. | | SWIFT -- PutFile request made | Informational. | | SWIFT -- PutFile request received | Informational. | | SWIFT -- Request accepted | Informational. | | SWIFT -- Request rejected | Informational. | | SWIFT -- Incorrect state | Informational. | | Option not available for SWIFT sessions | Informational. | | No batch is launched after emission. Data in SWIFT | Informative in operation | | SWIFT. Buffer in incompatible state | Informative in operation | | SWIFT. Message with unknown identifier | Informative in operation | | SWIFT response. | Informational. | | Reception rejected by profiles | | | Remote call rejected (session data) | Check that the session exists for the received ID: local-remote-application. | | Call from PAD rejected | Check the corresponding field in the session profile's X25 parameters. | | Release due to maximum number of sessions (profile) | Check the corresponding field in the local profile. | | Current session released | Informational. | | Different remote Editran version (accepted) | Check the session profile field. | | Release due to inactivity timeout | | | Download acknowledgment timeout expired | | | Download acknowledgment message | Result of sending/receiving the download acknowledgment | **Notes:** * DTE - Data terminal equipment. * DCE - Signal conversion equipment (modem) * I.U.R. - Network user identifier. ### Release messages in Onesait Editran When in Editran the connection cannot be established or a cut occurs during transmission, release messages are generated that identify, using two codes (cause and diagnostic), the reason that produced them. It is difficult to document all the possible causes and diagnostics that Editran/P can receive, since in many cases it depends on the network protocol used and the driver vendor; therefore, in this documentation we will focus only on the releases originated by the Editran protocol itself. Connection retry conditions are also included in this chapter, since action is taken based on the releases received. #### Onesait Editran causes and diagnostics The release or call rejection cause and diagnostic codes given by Editran are specified below. Cause = x'00'. Diagnostic = x'XX'. Where "XX" means the following: | | | | -- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | 03 | The maximum number of sessions defined in the Local Environment (Maximum Number of Circuits) has been reached, and therefore no channel is available. | | 04 | A crossed call in flight has occurred. The one with the lower Editran Installation Code is released. | | 05 | A release has occurred because a channel was already established for that Session. | | 08 | Editran release by the Operator. | | 09 | A network restart has occurred by the Operator. | | 0B | The circuit is released due to a compaction-compression error. | | 0C | An incoming call is rejected because the entry time is incorrect according to the Session specifications (START TIME and END TIME). | | 0D | The call is rejected because the Session has not been registered in Profiles. | | 0E | The call is rejected because the Calling End defined in the Session does not correspond to the one making the call. | | 0F | Generic Editran release (files not prepared, automation startup, etc.). | | | | #### Connection retry conditions The Editran protocol has a recovery mechanism for temporary network failures based on retrying the connection. The only cases in which it is not tried again are: * If the CALLING END field is Remote * If the release code is Cause = 0 and Diagnostic: 04 | | | | -- | ------------------------------------------------------------------------------------------------------------------------------------ | | 04 | A call crossing has occurred. | | 05 | There was already a connection for that Session. | | 08 | Release by Operator. | | 0F | Generic Editran release. | | 00 | No additional information. It is only retried if a connection is being established, not during drops in transmission. | | 04 | In all cases, when retrying the connection, it will rotate to the next remote as long as several have been specified in the profile. | ### Onesait Editran Cryptography System #### Introduction The cryptography used by EDITRAN provides maximum security for the communications channel and addresses the needs of authentication, confidentiality, and non-repudiation. The user is the one who decides how they want to transmit. The services provided are listed below. * **Information confidentiality** To keep the information secret during the transmission process, the information is encrypted at the sending end with an encryption key that only the final receiver can 'interpret', and with it the received information is decrypted. To encrypt/decrypt the information, symmetric-key algorithms are used: DES and AES symmetric-key algorithm (recommended). This key is different for each transmission and is exchanged encrypted with another higher-level key. * **Information integrity** So that what is actually sent is received, avoiding manipulation or alteration during transmission. For this, an error detection code for the information is generated at the sending end, also known as a hash, summary code, or digital fingerprint, which is verified by the final receiving end when it is received. The algorithms used are SHA1 and SHA256. * **Authenticity of the sender / final receiver pair** To ensure that they are really who they say they are and not fraudulent senders and/or receivers, it is possible to use end authentication techniques through RSA algorithms. Optionally, Editran implements an authentication mechanism based on DES encryption, although it is not recommended because it is less secure. * **Non-repudiation** So that neither party can deny having sent or received the exchanged information. For this purpose, during the Editran authentication procedure, using RSA keys and before the data exchange, the signatures presented by both ends are validated. In summary, the different possibilities for handling cryptography within Editran are described. * **V3.0 or external key exchange** In all cases, the confidentiality algorithm is TDES (with triple key). The authentication algorithm can be DES or RSA (1024-bit keys). The DES auxiliary keys and RSA public keys used in endpoint authentication must have been exchanged before transmission. In the case of RSA, the Editran/GC module is provided to facilitate this procedure. * **V4.0 (recommended)** Extends the functionality of mode 3.0 by providing more secure algorithms. The only allowed authentication algorithm is RSA with 2048 or 4096 keys. TDES (with triple key) is kept as the confidentiality algorithm, although using AES (128, 192 or 256) is recommended. #### DES key types * **HMK - Host Master Key** Its function is to encrypt the keys of the local user entity and it resides masked in the file **ckds.des**. * **AK - Auxiliary Key** Its function is to encrypt the Editran master key.\ It is generated randomly and included in the file **ckds.des** under a label. * **TKE, TKR - Transmission and Reception Transport Keys** Its function is to encrypt the Editran user application data sent to the remote. They are stored encrypted in the profile file. #### Cryptography Errors Any cryptography error will generate information for the local operator and a disconnect. The errors that can occur are: **Cryptography errors v3.0 and v4.0** | Error | Description | | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **ERR1** | An error occurred while obtaining the local key, either because it was not provided in Profiles or because of an error in the External Key Interface. | | **ERR2** | When trying to send an association request or a response, an error occurs when generating the uncertainty or the signature. If the algorithm used is DES, the error is in the local key. If it is RSA, the error is in the local key when generating the signature, or in the remote key when generating uncertainty. | | **ERR3** | Error while trying to generate the session key. If the algorithm used is DES, the error concerns the local key. If it is RSA, the incorrect key is the remote one. | | **ERR4** | An error occurred while obtaining the remote key, either because it was not provided in Profiles or because an error occurred in the External Key Interface. | | **ERR5** | When processing a request or response from the remote, an error occurs while trying to decrypt the uncertainty or the signature. If the DES algorithm is used, the incorrect key is the remote key. If RSA is used, the error is in the remote key when decrypting the signature, or in the local key when decrypting the uncertainty. | | **ERR6** | When processing a request or response from the remote, an error occurs while decrypting the session key. If the algorithm is DES, the error is in the remote key. If it is RSA, the key in error is the local one. | | **ERR7** | The end that is going to send a user data item or Operator Message has had an error in 'on-line' encryption. | | **ERR8** | The end that receives a user data item or Operator Message from the Remote has had an error in 'on-line' decryption. | | **ERR9** | When processing a request or a response, the session key and the signature are decrypted, but either the uncertainty does not match or the signature does not match (this case only in RSA). The error occurs because the exchange keys do not match at both ends. If an External Key Interface was used, the message must include the last 8 bytes of the label used. If the algorithm used is DES, the incorrect key is the local key of the end that generates the message. If it is RSA, the incorrect key is the local key (if an error occurs when validating the uncertainty) or the remote key (if an error occurs when verifying the signature). | --- # 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/open-v5.3-en/linux/plataforma.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.