> 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.2.1-en/linux/plataforma.md). # Editran/P management ## Onesait Editran/P Manager The EDITRAN/P manager is presented below: ![assets/image4.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-93f886e240b6e7e679804d077d277016c50dc006%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 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]" will be displayed to indicate that the license service is active. * Register the local environment as described in chapter **Local Environment**. * Start Editran again from *\***/bin** with the command: > **$ EDItran start** At this point, startup must finish without any kind of error, displaying the final message "EDItran system started". ### User interface description #### Screens On the Editran UNIX screens, three areas can be distinguished: * **(1) Title** * General system information appears in the title area: * Current date and time (at the moment the screen is activated). * Screen object: administrator, operator, etc. * Version and operating system. * **(2) Options** * The different options of a menu, the parameters to be entered by the operator, or the results of the requested queries may appear in this area. * **(3) Information** * The information sent by EDITRAN to the operator appears in this area: * Session. * Emission and reception states. * Transmission and reception counters. * Information text or messages from the remote operator. #### Help EDITRAN UNIX has a context-sensitive help system. In this way, when the keys **F1** or **?** are pressed, a window appears with the help text associated with the field or screen where the cursor is at that moment. #### Keys Within the Editran UNIX 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 a system exit to run other commands (shell), leaving EDITRAN resident. To return to EDITRAN, the command **exit**. | | **Enter** | Ends data entry for the current field, updating its value. If no value has been entered, it inserts the one from the last request. | | **Space** | Selects the field value within a list of enumerated values: A (**or**) B ( ) C ( ) or activates/deactivates the field value with 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 the next/previous value within the field. | | **PgUp** **Control-U** | Page up. | | **PgDn** **Control-D** | Page down. | | | | ### Onesait Editran/P Operator To manage exchange sessions, option 1.- OPERATOR from the EDITRAN/P MANAGER main menu will be selected, showing the following options: ![assets/image5.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-52a983655f97e2f3c8ef0322ca945e8f4b045615%2Fimage5.png?alt=media) #### Session consultation Select option 1.- SESSION CONSULTATION from the menu. Active sessions can be queried generally or individually. To query a particular session, enter the SESSION and press Enter. In the information area of the screen (lower part), the information on the states and the transmission and reception counters of the requested session will appear. For the generic query, fill the SESSION field with zeros. ![assets/image6.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-e42f2a41dc3c342f20624fe8f46fe45a6176c069%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 a transmission or reception request is made if the value S is specified in the AUTOMATIC CALL parameter of the session profile. Indications on the result of the request (connection established or not) appear in the information area. #### Release request To manually release the existing connection for a session, select option **3**.- RELEASE REQUEST from the EDITRAN OPERATOR menu. #### Send request To start local file transmission, select option 4.- TRANSMISSION REQUEST from the EDITRAN OPERATOR menu. The request is not allowed when the local Editran operating mode is Server. #### Receive request To start the reception of a file, which must be sent by the remote, select option 5.- RECEPTION REQUEST from the EDITRAN OPERATOR menu. The request is not accepted when the local Editran operating mode is Server. #### End of transmission To request the forced end of local transmission (transmission interruption), select option 6.- END OF TRANSMISSION from the EDITRAN OPERATOR menu\*\*.\*\* The request is not accepted when the local Editran operating mode is Server. #### End of reception To request the forced end of local reception (reception interruption), select option 7.- END OF RECEPTION from the EDITRAN OPERATOR menu. The request is not accepted when the local Editran operating mode is Server. #### Message for the remote operator A connection with the remote Editran that is the recipient of the operator message is required. The following screen will appear, where the text to be sent will be written: ![assets/image7.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-01a62cc3809ecd2dc041bc0988b496648c5c6ced%2Fimage7.png?alt=media) #### Remote transmission file consultation To consult the remote transmission file, select option E.- CONSULT REMOTE TRANSMISSION FILE from the EDITRAN OPERATOR menu. The local Editran program will send the query message to the remote, leaving the local one waiting to receive the response from the remote. This response will be displayed on the next screen. A connection must have been previously established between both ends. #### Remote reception file consultation To consult the remote reception file, select option R.- CONSULT REMOTE RECEPTION FILE from the EDITRAN OPERATOR menu. The local Editran program will send the query message to the remote, leaving the local one waiting to receive the response from the remote, which will be displayed on the next screen. A connection must have been previously established between both ends. ![assets/image8.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-7a194ec9de83b86df6ab84fd156c527f5c862f28%2Fimage8.png?alt=media) ### File inquiry From option 2.- FILE CONSULTATION of the EDITRAN/P MANAGER, the following options are displayed. ![assets/image9.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-bd2494bc5e9ab373ff7265807a4bbfb2738a6064%2Fimage9.png?alt=media) #### Transmission / reception record consultation To obtain information from the control record of the local transmission or reception buffer file, select option 1.- TRANSMISSION/RECEPTION RECORD CONSULTATION from the FILE CONSULTATION menu. ![assets/image10.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-48720bb3de48783946730a3d685f98341f8bf511%2Fimage10.png?alt=media) Two screens will be displayed with the control record data for the local transmission or reception file for the specified session. For a consultation of the local transmission file (by entering an E in the FILE field) For a consultation of the reception file (by entering an R in the FILE field) #### Log file consultation. All informational messages that Editran has sent to the operator are displayed. To consult these records, select option 2.- LOG CONSULTATION from the FILE CONSULTATION menu. ![assets/image11.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-eeffd726bc28b2f98b8edc787f4a0b9fb8a9125f%2Fimage11.png?alt=media) The SESSION, DATE, and TIME fields are optionally filled in. If no filter is specified, the last recorded entries will be displayed. For a general query, write 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 handled cyclically. ![assets/image12.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-ac7fe622be1d2268ba9dfae8ee587ac49ccdfaf5%2Fimage12.png?alt=media) #### Generic session consultation All sessions defined in the profiles file are displayed. To consult these records, select option 3.- GENERIC SESSION CONSULTATION from the FILE CONSULTATION menu. ![assets/image13.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-586ccb8aed31f4f8cc84f4f2b2a882901d2477e3%2Fimage13.png?alt=media) \**\** ### Onesait Editran/P Administrator To access the Editran administration menu, select option 3.- ADMINISTRATOR from the EDITRAN main menu. The following options will be displayed for managing the Local Environment and Session parameters. ![assets/image14.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-5286ac34b4f94137e811973ab0baedd3b31001d0%2Fimage14.png?alt=media) #### Local Environment Editran/P's Primary Local Environment is managed from option 1.- LOCAL ENVIRONMENT of the ADMINISTRATOR menu. In those entities that have a multi-environment license, that is, the possibility of presenting themselves as several centers, it is not necessary to define a specific profile for the secondary environments; it will be enough to specify the new code in the corresponding sessions. Enter the following requested data: ![assets/image15.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-9afdd49e509f3c0add1b7459f844007408b2a381%2Fimage15.png?alt=media) * **LOCAL** The identification number of the entity using Editran will be entered. With this identification number it will be recognized by all interconnected entities. Entity codes in Editran consist of nine characters (NIF) with the following format **xnnnnnnnx**. * **NAME** The installation description will be entered. This field is for information purposes only. * **MAXIMUM NUMBER OF SESSIONS** The maximum number of exchange sessions that can run concurrently at a given moment can be specified. * **IP ADDRESS** The address of the local machine on a TCP/IP network, supports up to 3 different addresses with 3 listening ports for each address. * **TCP CONNECTION TIMEOUT** It is the maximum waiting time from the moment the connection of a *socket* remote is accepted 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 In order to connect and perform transmissions and/or receptions with a remote Editran, the parameters that describe the session profile must be specified and the local environment must have been registered beforehand. As many sessions as different connections you want to establish will be registered. Select option 2 from the EDITRAN ADMINISTRATOR menu. ![assets/image16.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-c37303b152d2e7ce1397ed616110f7c5c9afc7ef%2Fimage16.png?alt=media) Once selected, the screens will appear in which the user can fill in or view (depending on the chosen option) the parameters or characteristics that define the session. ![assets/image17.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-f31b54ccb8e571d95e3c8159a84f89a639f89c28%2Fimage17.png?alt=media) In all options, the following must be specified: * **SESSION** Session identification. Except when adding, a search filter may be specified; in that case, the list of sessions matching the mask will be shown for the user to choose from. ![assets/image18.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-83365efe1b18eed61e32ce22c855e8544c9a13fe%2Fimage18.png?alt=media) In A.- Add and M.- Modify, all fields except the Session identifier appear unprotected. To carry out the option, you must get to the last screen. In C.- Query, all fields appear protected. The first screen shows the parameters that affect the connection: ![assets/image19.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-baf1a4d87cd51ae17cb366f7e87d031d21657f36%2Fimage19.png?alt=media) * **LOCAL** Code identifying the local center. * **LOCAL NAME** Name of the local center associated with the session. This is for information purposes only. * **REMOTE** Code identifying the remote center. * **REMOTE NAME** Name of the remote center associated with the session. This is for information purposes only. * **APPLICATION** Identification code of the application using the editran transmission service. * **APPLICATION NAME** Name of the user application. This is for information purposes only. * **VERSION NUMBER** Version of the remote Editran/P system. It can be 5.1, 5.0, or 4.1. It must match the corresponding value in the remote session. * **CALLING END (L/R/X)** * **L** Only the LOCAL endpoint can call. * **R** Only the REMOTE endpoint can call. * **X** Either endpoint can call. * **TRAFFIC DIRECTION (E/R/X)** * **E** Only transmission is possible in this session. * **R** Only reception is possible in this session. * **X** Transmission and reception can occur simultaneously. * **AUTOMATIC CALL (S/N)** * **S** The connection will be established automatically when transmission or reception is requested to start. * **N** A prior connection must be established before requesting transmission/reception. * **AUTOMATIC DISCONNECTION (S/N)** * **S** The disconnection request is generated automatically when a transmission or reception ends\*\*.\*\* * **N** No automatic disconnection is generated\*\*.\*\* * **TIME-OUT (Seconds)** This is the time interval, expressed in seconds, in which EDITRAN waits to receive from the remote a response message to one previously sent control message. If no response has been received when the TIME-OUT period ends, the same request will be sent again, starting a new waiting interval. This also applies to connection requests. * **MAX. NUMBER OF RETRIES** This is the number of times the previous TIME-OUT procedures are repeated. * **SAVE ROTATIONS (S/N)** * **S** In the case of a call request, when the connection is eventually established by 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** The profile addresses are never updated. Once the values on this screen have been entered and validated, a new one will appear where the specific TCP parameters are defined: ![assets/image20.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-6955178767c18d1902c0f2890b7fae11926ebe17%2Fimage20.png?alt=media) * **REMOTE IP ADDRESSES** Remote IP address and port to connect to, with up to a maximum of 6 different IP addresses possible. * **VALIDATE REMOTE IP (S/N)** * **S** 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 **S** 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://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-081b472dba28578da113d213754010bc82ae3b64%2Fimage21.png?alt=media) * **SERVER/CLIENT (OPER)** * Operating mode: * **S** Neither transmissions nor receptions can be requested (server). * **C** Both transmissions and receptions can be requested (client). * **CRC (S/N)** * **S** Cyclic redundancy code will be generated for each transmitted message; the CRC of each received message will be validated. * **N** CRC is not calculated for outgoing messages nor validated on incoming messages. * **COMPRESSION (S/N/V)** * **S** Compressed transmission of data. * **N** Data are transmitted in the original format of the application. * **V** Data are transmitted compressed or in the original format depending on the best result obtained. * **ASCII/EBCDIC (A/E)** * **A** The remote uses the ASCII alphabet (Unix and Windows environments). * **E** The remote 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 cutoff time of day until which transmission can be started, expressed in hours (HH), minutes (MM), and seconds (SS). * **BUFFER LENGTH** Length of the buffer file records. 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) * **TRANSMISSION BURST** Length of the transmission burst (number of records sent before receiving the remote confirmation). * **SYNC TIMEOUT (Seconds)** This is the time interval, expressed in seconds, in which EDITRAN waits to receive from the remote a synchronization message for the sending of a data block (burst). If no response has been received when this time ends, the data sending is repeated, up to the maximum 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 > assets/image22.png The parameters that appear on the screen are: * **CRYPTOGRAPHY (S/N)** * **S** 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. * **2.2** For the security subsystem of version 2.2 of EDITRAN/P. * **3.0** Cryptography compatible with CRIPTO/lib V3.0. * **4.0** AES encryption and 2048 and 4096 RSA keys. * **KEY CHANGE V2.2 (S/N)** Selector for the cryptographic key change facility in the connection preamble. It only affects when the cryptography version is 2.2. * **S** Key change enabled. * **N** Key change disabled. * **KEY MANAGEMENT V3.0** When this facility is selected in cryptography versions 3.0, 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. * **S** Labels provided by EDITRAN/GC. * **N** Labels provided by the user. * **CONFIDENTIALITY ALGORITHM** Algorithm to use to encrypt the data. Leave blank to transmit without encryption. * **DES** DES encryption with a single key. * **TD2** DES encryption with a double key. * **TD3** DES encryption with a triple key. * **AES** AES-128 encryption. * **AE2** AES-192 encryption. * **AE3** AES-256 encryption. * **AUTHENTICATION ALGORITHM** Algorithm to use to protect the session key and the exchanged data to authenticate the endpoints. It is mandatory if there is a confidentiality algorithm. * **DES** if you want to authenticate the endpoints with the DES algorithm (valid with cryptography versions 2.2 and 3.0). * **RSA** if you want to authenticate the endpoints 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. ## Attachments ### Onesait Editran Components #### Current schema Editran is a modular product. There is 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 Proxy), and additionally there is another series of modules that help to improve the Security, Control or Functionality of the product. ![assets/image23.png](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-97a616d282a35df6276ec00ba25b1364b37faeee%2Fimage23.png?alt=media) ### Commands #### EDItran This is the script that starts and stops the Editran system. * Syntax The syntax of the command is: > 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 is responsible for dialoguing with the different communication processes and with Editran/G. It is launched in the background when the Editran system starts. #### editcp Communication 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 by editran. * Syntax The syntax of the command is: > **makelog** -n N where **N** is the maximum number of entries (number of events) to retain in the file. * Example An event file, editran.log, with capacity for 500 different entries, is to be created. The command must be run: **makelog** -n 500 If the system is used 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 syntax of the command is: > **menucmd** s session x > > where **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. Specifically, the exact syntax of the command depending on the value of **s** is as follows: > menucmd {E00|E11} \ > > menucmd EOP \ \ 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 syntax of the command is: > Use: copycfg -s source\_sess \[-d destination\_sess] \[-n] \[-r remote\_code] \[-p | -a] Where: > -n : number of sessions to create. > > -s : source session. > > -d : destination session. > > -r: destination remote code. > > -p: copy only Editran/P sessions > > -a: create Editran/G applications This command allows Editran profiles to be created from a session taken as a template. The source session is provided in option **--s**. By default, the Editran/P Session and its corresponding Presentation in Editran/G are created, but this behavior can be changed with option **--p** if only the session profiles are to be created. The created profiles will depend on the chosen option: * **Option -n**: The following 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 of the session to be created, but this option is incompatible with the previous one. * **Option -r:** By default, the created sessions are generated with the same local and remote code as the original one. With this option, the user can change the remote code of the new profile. * Example > To duplicate the INDRA-TEST session for a different remote, 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 \[ -lgrapsv ] > > Where: > > -l: Local Editran/G. > > -g: Editran/G presentations. > > -r: Editran/G remotes. > > -a: Editran/G applications. > > -p: Local Editran/P. > > -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 Resets the encrypted exchange keys of a given session. It must be used with great caution, since it leaves the keys in a different state from the original. It is essential to perform the same operation on 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 syntax of the command is: > **resetkey** \[session] where session is the Editran/P session. It must be written in uppercase, and if it contains any spaces, between double quotes: " * Example In an installation, the key for the TEST-INDRA session is to be set to an initial value. The command must be run: > 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 in order to store single and double keys. 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 they keep and must provide the first two octets in hexadecimal as the file access password. It can be given as a command argument, but if it is not provided the user will be prompted. * Syntax The syntax of the command is: > Usage: importkey \[ -s ] \[-k\] -f\ \[--] \[labels] > > \--: End of options. The rest of the arguments are labels > > -s: The source file contains single keys > > -k\: File access key (HMK) > > -f\: File that stores the keys to be exported > > labels: Labels of the keys to be imported If no label is provided, the command incorporates all keys from the source file whose label is not SI0000000000XX. If the label 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 providing the access password as an argument, run: > \> importkey -s -fckds.des.520 --kA1A3 #### printlog Editran log printing utility. * Syntax > **printlog** * Command options: > -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 the UNIX ones. To use the filter, just tell it what the starting structure is (for example, 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 > 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 be translated (stdin->stdout by default) To indicate the type of record we are going to use (fixed or variable), we use the following options: * **option -N** (where N is a number, e.g. 80): fixed records of N characters. * **option -v**: variable records. * To indicate the end-of-line delimiter used in the input file, the **option -iX** is used (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 a '\n' delimiting each record. (Unix type). * If X is d, the filter expects a '\r\n' delimiting each record. (MSDOS type). * To indicate the end-of-line delimiter to be used in the output file, the **option -oX** is used (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 manual *Profile Management* for more information about this utility. ### Data files #### CFG subdirectory * **editranp.cfg** Editran configuration file. It stores the local profile and the session profiles for remote entities. Used exclusively by Editran. * **editranp.sdx** Editran configuration index file. * **ckds.des** File where the auxiliary exchange keys of encrypted Editran sessions are found. #### 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 content is 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 process standard output **editranp**. * **editranp.log** File created by the command **makelog**. It cyclically stores the summary of operations performed by EDITRAN, so once the maximum number of entries is reached, the oldest one is overwritten. It can be consulted from the Editran menus and through the command ***printlog***. ### Codes and operator messages These codes are the ones reflected in the file **editranp.log** to indicate the different states a session goes through. On the Editran/P operator screen, they appear in the form of messages. The messages are listed below, with a brief explanation or recommended action, as appropriate: | MESSAGE | EXPLANATION/RECOMMENDED ACTION | | ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Association established | Local association request accepted by the remote end. | | Remote association accepted | Association between applications accepted by the local end. | | Start of transmission | Transmission to the remote begins. | | 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 | A query has been requested for the control record of the remote send buffer file. | | Remote receiver file query | A query has been requested for the control record of the remote receive buffer file. | | Totals mismatch in sender process | In applications with totals control, the exchanged confirmed totals do not match (synchronization). | | Totals mismatch in receiver process | In applications with totals control, the exchanged confirmed totals do not match (synchronization). | | Transmission aborted | The transmission of a file to the remote has been aborted. | | Transmission correct and completed | A transmission has finished correctly. | | Local transmission | Start of local file transmission. | | 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 executing a shell script. | | Error in remote batch process | An error occurred while executing a remote shell script. | | General interface error | An error occurred while executing a shell script. | | Remote cryptography error (ERR##) | A cryptography error occurred. See the Cryptography Errors section. | | 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 | The retries in the sender process for messages that require a response have been exhausted. | | Retries exhausted in receiver process | The retries in the receiver process for messages that require a response have been exhausted. | | Retries exhausted for sending | The transmission start retries have been exhausted, according to the number of retries in the Editran session profiles. | | Retries exhausted for establishing session | Session establishment retries have been exhausted, according to the number of retries in the Editran session profiles. | | Retries exhausted for ending transmission | Transmission end retries have been exhausted, according to the number of retries in the Editran session profiles. | | Retries exhausted for receiving | The 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 one already exists. | | Invalid calling end (profiles) | Incompatibility in the values of this field in the profiles record. | | Profiles file empty or does not exist | An error occurred while accessing the Editran profiles file. | | Receive file not prepared | The control record information exchanged between the two ends, in the transmission start request/response message, does not allow data exchange to begin. The exchange session number contained in the control records does not match. The send/receive file is not loaded, or is not available for Editran (the batch process specified in profiles is triggered). | | Send buffer file not prepared | Response to remote file query. | | Buffer files in incompatible state | The remote rejects the local request because its buffer file is not prepared. It may have launched the corresponding pre-automation for the request. | | Transmission end requested by operator | When the operator requests forced transmission end. | | Transmission end requested by remote operator | When the remote operator requests forced transmission end. | | Reception end requested by operator | When the operator requests forced reception end. | | Reception end requested by remote operator | Transmission end requested by the remote operator. | | Local transmission end requested by the remote | When the remote requests reception end (end of local transmission). | | Unable to send remotely due to profiles | Review the processes defined in the session profile. | | Unable to receive remotely due to profiles | Review 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 end and only one is accepted. | | Release by operator | Occurs as a result of a release request by the operator. | | Release due to compression error | Release is requested when a compression/decompression error occurs in a message. | | Release because another channel exists | 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 collect calls. | | Release due to incorrect schedule | Check the schedule registered in the session profile and modify it. | | Release due to collect call not accepted | Check the COLLECT CALL field in the session profile. | | Release due to no free channels available | 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. | | Call rejected (invalid time) | Connection request outside permitted hours. 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 connection establishment and the local one was handled first. | | Remote call rejected (collect call) | The specification for this parameter does not match at both ends. | | Remote call rejected (crossing) | The incoming call from the remote is rejected. | | Remote call rejected (calling end) | The specification for this parameter does not match at both ends. | | Local cannot send (profiles) | Send 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 license for the direction. | | Incorrect notification message | An error occurred while establishing the session due to the format of the notification message. | | No connection exists | A request was made that required a connection to be established beforehand. | | 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 batch launched after sending | A send batch request has been received, which will not be processed because sending is in progress. | | No batch launched after receiving | A receive batch request has been received, which will not be processed because receiving is in progress. | | No batch launched before sending | A receive batch request has been received, which will not be processed because receiving is in progress. | | No batch launched before receiving | A receive batch request has been received, which will not be processed because receiving is in progress. | | Connection pending | The request requires the existence of a connection between applications. The connection has not yet been completed. | | Sequence loss in sender process | A jump in the message sequence number has been detected. | | Sequence loss in receiver process | A jump in the message sequence number has been detected. | | Incompatible profiles (compression) | The specified value at both ends for the compression parameter does not match. | | Reception rejected by profiles (transmission direction) | The specified value at both ends for the transmission direction parameter does not match. | | Batch request for sending download | A batch request for sending download has been received. | | Batch request for sending start | A batch request for local transmission start has been received. | | Batch request for receiving start | A batch request for local reception start has been received. | | Batch request for preparation and sending start | A batch request has been received to launch a job specified in profiles. | | Batch request for preparation and receiving start | A batch request has been received to launch a job specified in profiles. | | Batch request after sending | A batch request has been received to launch a job specified in profiles. | | Batch request after receiving | A batch request has been received to launch a job that had been specified in profiles. | | Association request | A connection request between applications has been requested. | | Receive request | A reception request has been requested from the local or remote operator. | | Request not accepted. Server operation mode | A request not allowed in server operation mode has been requested. | | After sending completed successfully | A response is received from the batch indicating successful completion of a process. | | After receiving completed successfully | A response is received from the batch indicating successful completion of a process. | | Before sending completed successfully | A response is received from the batch indicating successful completion of a process. | | Before receiving completed successfully | A response is received from the batch indicating successful completion of a process. | | Start of session. Local transmission | 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 | A file reception has been aborted. | | Reception successful and completed | A file was received successfully. | | Received message with invalid CRC | A message has been received from the remote in a session defined in profiles with CRC validation, but its CRC was incorrect. | | Incorrect message received from batch | Correct A5P request type. | | Incorrect message received in sender process | Message outside protocol. | | Incorrect message received in receiver process | Message outside protocol. | | Remote without registered session (profiles) | The NRI of an incoming call does not match the one of the session registered in the profiles. | | SBP received in incorrect state | Message outside protocol. | | SBR with total mismatch | Negative response to a total synchronization because the totals in the receiving process do not match. | | SCP received in incorrect state | Message outside protocol. | | SEP received in incorrect state | Message outside protocol. incorrect | | The end of transmission is notified to Editran/G | A batch process has been launched according to profiles. | | The end of reception is notified to Editran/G | A batch process has been launched according to profiles. | | Transmission is requested from Editran/G | A batch process has been launched according to profiles. | | Reception is requested from Editran/G | A batch process has been launched according to profiles. | | It has been called before | A connection request was received when a previous one to the same session was already being processed. | | The call is made | An attempt is made to connect to the remote Editran system. | | Local key change requested | The local endpoint has requested a key change in the establishment phase of an application association. | | Remote key change requested | The remote endpoint has requested a key change in the establishment phase of an application association. | | 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. | | Session rejected by profiles (record length) | 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 transmission buffer file. | | Remote receiver buffer inaccessible | An error occurred while accessing the remote reception buffer file. | | Still transmitting | Request not processed because it is in transmission. | | 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 (launches previous) | The remote is preparing its reception buffer. | | Incorrect remote receiver file (no previous exists) | The remote has not prepared its reception buffer because it has no previous. | | Incorrect remote receiver file (previous in possible execution) | The remote reception 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 (launches previous) | The remote is preparing its transmission buffer. | | Incorrect remote sender file (no previous exists) | The remote has not prepared its transmission buffer because it has no previous. | | Incorrect remote sender file (previous in possible execution) | The remote transmission file is possibly being prepared. | | Local Editran/G denies batch request | Editran/G does not execute the requested operation. | | Loaded buffer file | Editran/G notifies the loading of the transmission 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 are not allowed in Editran. | | 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 the length of the buffer loaded by profile are different | Editran/G does not match the current length of Editran/P. | | Error. compressed sender buffer | The data have been compressed in Editran/G and compression is requested in Editran/P. | | Error. reception buffer length and profile different | | | Error. encrypted sender buffer and profile with compression | The data have been encrypted in Editran/G profile of Editran/P with compression. | | 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 disconnect) | 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 from the sender endpoint does not match the number of the record 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 endpoint. | | Version ignored due to date control | | | Association timeout exhausted | | | Received message with header | Invalid protocol message. unknown | | Remote call rejected (network license) | The session is not licensed 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 transmission. Data in SWIFT | Informational in operation of the Swift gateway. | | SWIFT. Incompatible buffer state | Informational in operation of the Swift gateway. | | SWIFT. Message with unknown identifier | Informational in operation of the Swift gateway. | | SWIFT response. | Informational. | | Reception rejected by profiles | | | Remote call rejected (data. Check that the session exists for the session) | Received ID: local-remote-application. | | Release due to maximum number of | Check the corresponding field in the sessions (profile) local profile. | | Session in progress released | Informational. | | Different remote Editran version (supported) | Check the field in the session profile. | | Release due to inactivity timeout | | | Remote download confirmation timeout exhausted | | | Remote reception inquiry | | | Remote download in progress | | | | | ### Release messages in Onesait Editran When in Editran the connection cannot be established or a break occurs during transmission, release messages are generated that identify, using two codes (cause and diagnosis), the reason that produced them. It is difficult to document all the possible causes and diagnoses that Editran/P can receive, since in many cases it depends on the network protocol used and the driver supplier, so in this documentation we will focus only on the releases that are originated by the Editran protocol itself. The connection retry conditions are also included in this chapter, since action is taken according to the releases received. #### Onesait Editran causes and diagnoses Next, the cause and diagnosis codes for release or call rejection given by editran are specified. Cause = x'00'. Diagnosis = x'XX'. Where "XX" means the following: | | | | -- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | 03 | The maximum number of sessions defined in the Local Environment (Maximum Number of Circuits) has reached the limit and therefore no channel is available. | | 04 | A crossing of in-flight calls has occurred. The one with the lower Editran Installation Code is released. | | 05 | A release has occurred because there is already a channel 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 Compactation-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 Endpoint defined in the Session does not correspond to the one making the call. | | 0F | Generic Editran release (files not prepared, startup of automatons, etc.). | | | | #### Connection retry conditions The Editran protocol has a fault-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 ENDPOINT field is Remote * If the release code is Cause = 0 and Diagnosis: 04 A crossing of calls 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 the connection is being established, not in drops during transmission. In all cases, when retrying the connection, it will rotate to the next remote whenever several have been specified in the profile. ### Onesait Editran Cryptography System #### Introduction The cryptography used by EDITRAN provides maximum security to the communications channel and addresses the needs of authentication, confidentiality, and non-repudiation. The user decides the mode in which they want to transmit. The services provided are listed below. * **Information confidentiality** To keep information secret during the transmission process, the information is encrypted at the sender end with an encryption key that only the final receiver can 'interpret', and with it decrypts the received information. To perform encryption/decryption of the information, symmetric-key algorithms are used: DES and AES (recommended). This key is different in each transmission and is exchanged encrypted with another higher-level key. * **Information integrity** So that what is actually sent is received, avoiding manipulations or alterations during transmission. For this, an error-detection code for the information, also called hash, summary code or fingerprint, is generated at the sender end and verified by the final recipient end when it is received. The algorithms used are SHA1 and SHA256. * **Authenticity of the sender / final recipient pair** To ensure that they are truly who they say they are and not fraudulent senders and/or recipients, there is the possibility of using endpoint authentication techniques using RSA algorithms. Optionally, Editran implements a DES-based authentication mechanism, 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, during Editran's authentication procedure, the signatures presented by the two endpoints will be validated using RSA keys, prior to the data exchange. As a summary, the different possibilities for handling cryptography within Editran are described. * **V2.2 or automatic key exchange** This mode does not require a prior key exchange. It starts from a common one that, for greater security, is automatically modified at the discretion of the endpoints. Both the authentication and confidentiality algorithms are DES. * **V3.0 or external key exchange** In all cases the confidentiality algorithm is DES (single, double, triple). The authentication algorithm can be DES or RSA (1024-bit keys). The auxiliary DES keys and the 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 permitted authentication algorithm is RSA with 2048 or 4096 keys. DES remains as the confidentiality algorithm (single, double, triple), although using AES is recommended (128, 192 or 256). #### 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 master Editran key. > > It is randomly generated and incorporated into the file **ckds.des** under a label. * **TKE, TKR - Transmission Keys for Sending and Receiving** > Its function is to encrypt the data of Editran user applications that are sent to the remote. > > They are stored encrypted in the profiles file. #### Cryptography errors Any cryptography error will generate information for the local operator and a disconnection. The errors that can occur are: **Cryptography errors v2.2.** | | | | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **ERR1** | The endpoint requesting a Connection Request has been unable to Re-encrypt the Keys in its file. | | **ERR2** | The endpoint requesting to authenticate its TKE key has been unable to encrypt the Authentication Code, although it did perform the re-encryption. | | **ERR3** | The endpoint requesting a Connection Request with Key Change has been unable to generate a new TKE transmission key. | | **ERR4** | The endpoint receiving the Remote Notification Indication had an error when Re-encrypting the TKR key in its file. | | **ERR5** | The endpoint receiving the Notification Indication has been unable to decrypt the Authentication Code sent by the Remote, although it did perform the Re-encryption. | | **ERR6** | The endpoint receiving a Notification Indication with Key Change had an error when re-encrypting the new Reception key coming from the remote (new TKR). | | **ERR7** | The endpoint that is going to send user data or Operator Message has had an error in "on-line" encryption. | | **ERR8** | The endpoint receiving user data or Operator Message from the Remote has had an error in "on-line" decryption. | | **ERR9** | The endpoint receiving a Notification from the Remote (with or without Key Change) has decrypted the Authentication Code, but it is incorrect (despite keeping the old reception key). Possibly some endpoint deregistered and registered the Editran session in Profiles. This is the most serious error. The only way out of this situation is to deregister and register the Session in Profiles on both endpoints. | | | | | **Cryptography errors v3.0 and v4.0** | | | ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **ERR1** | An error occurred when obtaining the local key, either because it was not supplied in Profiles or because of an error in the External Keys 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 the uncertainty. | | **ERR3** | Error when trying to generate the session key. If the algorithm used is DES, the error concerns the local key. If it is RSA, the erroneous key is the remote one. | | **ERR4** | An error occurred when obtaining the remote key, either because it was not supplied in Profiles or because an error occurred in the External Keys Interface. | | **ERR5** | When processing a request or a response from the remote, an error occurs when trying to decrypt the uncertainty or the signature. If the DES algorithm is used, the erroneous 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 a response from the remote, an error occurs when 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 endpoint that is going to send user data or Operator Message has had an error in "on-line" encryption. | | **ERR8** | The endpoint receiving user data 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 on both ends. If an External Keys Interface was used, the message must include the last 8 bytes of the label used. If the algorithm used is DES, the erroneous key is the local key of the endpoint generating the message. If it is RSA, the erroneous 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.2.1-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.