> 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/novedades/previas.md). # Previous versions In versions earlier than 5.2.1.0, the following changes were made ## Editran v5.2.0 (previous) ### Discontinued functionality #### Editran protocol * Compatibility with Editran V4.0 is removed * PKI cryptography for entity authentication disappears. #### editran /X25 * Due to Telefónica/Movistar discontinuing X25/X28 lines, Editran removes these connection types. * The editran /TX module that provided access to the X25 network in mainframe environments without the need for a communications controller is discontinued. #### editran /EA -- Statistics and alarms * This module is temporarily discontinued. A new version designed as a Web application is being developed. ### New features #### Editran cryptography **New Version 4.0 for V5.2 transmissions** * Cryptography 4.0 only supports RSA as an end-to-end authentication mechanism. In the Editran/GC module, DES key exchange is removed. * Cryptography 3.0 only supports RSA keys of length 1024; in the new version this is extended to 2048 and 4096 keys. * The AES encryption algorithm is incorporated for data encryption. Supported keys are 128, 192 and 256 bits. The encryption key exchange is based on RSA cryptography of up to 4096 bits and SHA-2 hash mechanism. * These changes do not affect presentation sessions configured with previous encryption versions (v2.2 or v3.0). In these cases, the functionality remains the same. #### editran /PX * Route definition filtered by entity codes. The product can be configured so that remote connections are routed to different Editran servers on the internal network, depending on the code of the connecting entity. #### Other improvements **Different paths for Editran programs and data** In previous versions, configuration files and temporary files (buffers, status, etc.) are always stored in the Editran working directory. In the new version, it is possible to decouple them from the product installation path by defining the path where the processes look for and store those files. * This feature will be especially useful in production environments where several instances of Editran installed on different machines, in active-passive mode, can share those files. * The data path is set through the EDI\_DATA environment variable in Unix and through the DataPath registry key in Windows. See editran *V5.2 Installation Manual* for more information. **New parameter in post-send/receive processes** In this version, when Editran runs the user programs after send or receive, the parameter list is: Presentation, direction, local code, remote code, application, and the absolute path of the file containing the list of transmitted files. Unlike previous versions, the user will no longer need to know where Editran leaves that file, since it is provided. Post processes will only be run when the transmission has completed successfully. In these cases, the file list can be used for integration with other applications, for example, moving received files or deleting files already sent. **editran /GT (Windows)** In scheduled sends through editran /GT, the possibility of running the procedure implemented by the user (usually batch programs) has been added. In this process, the sent files must be deleted or moved so they are not transmitted again. The program is invoked with the following parameters: Presentation and the absolute path of the file containing the list of transmitted files. If, when configuring the Presentation in editran /GT, you select *"Run process"* and leave it blank, nothing will be done after sending. This may be useful when the post-send tasks have already been performed in the user program defined in editran /G. ### Fixed issues The table shows only the issues detected in V5.1.0 and which, due to their severity, have not been fixed in patches generated for that version itself. | **Code** | **Module** | **OS** | **Description** | | ----------- | ----------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **I510-75** | editran | All | In sessions configured with V3.0 key exchange and, for example, a different record length, the entity (A) that receives the association request rejects it due to profiles, but the calling entity (B) does not receive that rejection and ends with "Retries exhausted to establish session". It is necessary to stop Editran on entity (A) in order to associate again. | | **I510-85** | MenuG | Unix | A Presentation can be created with the APPLICATION field empty (blank). | | **I510-81** | editran /GT | Windows | If a scheduled Presentation is renamed from MenuG, editran /GT does not detect that change and continues launching transmission requests for the old Presentation. | | **I510-73** | editran /GT | Windows | It should be allowed to stop the search when there are presentations in state *"Finished with error. Retrying"*. It is only prevented when the status of some presentation is "T*ransmitting"*. | | **I510-70** | editran /GC | Windows | When the list of remotes associated with a local subsystem is so long that it needs scrolling, the panel with the list of own keys becomes so small that it does not allow any row to be displayed. | ## Onesait Editran V5.1.0. ### Discontinued functionality #### Onesait · Editran Protocol * Compatibility with editran V3.1 is removed. This version will only be able to communicate with remote entities that have at least editran V4.0 installed. If profiles from previous versions are migrated, sessions with version 3.1 or lower will be created with version 4.0. #### editran /IC -- Confirmed exchanges * The editran /IC module for confirmed exchanges has been discontinued. ### New features #### editran /P **The maximum number of concurrent transmissions is 500.** The limit of concurrent sessions in previous versions was 100. It has been increased to 500, which will be the new default value for the field *"Maximum number of sessions"* of the local profile. **Activity control for connected sessions.** The protocol establishes a new inactivity timeout that controls that if a session is connected but there is no data traffic for a given time, it is released. The default timeout value is 600 s, which the user can modify by defining the EDI\_TOUT\_IDLE environment variable. Once the timeout expires, the release is recorded in the log with the following message: *"Released due to inactivity timeout"*. **Alphabet negotiation in session establishment.** In V5.1 the protocol has been modified so that the alphabet is negotiated between entities whenever possible, removing from the user the responsibility of knowing that remote installation data. To maintain compatibility with version 5.0 or lower, the alphabet field has been kept in the editran /P profile, but it should be noted that it is only used when the connection is outgoing. If it is the remote entity that calls, regardless of the version and the value of the field, the connection is accepted and communication takes place in its alphabet. #### editran /TCP **Incorporation of cause and diagnosis into disconnections.** In earlier versions, in TCP transmissions when the Editran application is the one that rejects the connection (because the profile does not exist, due to time control, IP validation, etc.), the calling entity only receives the release, but cannot distinguish the reason. To avoid this situation, a TCP message has been added that sends the cause and diagnosis of the disconnection before closing the socket. #### editran /G **Download confirmation** The functionality of confirming remote downloads is implemented, so that the sender does not consider the transmission complete until it has evidence that the receiver downloaded correctly. In the editran /G profile, the new parameter *"Ask for download confirmation"* determines whether the send should behave as before or whether remote confirmation is desired. On reception, the result of the last download is returned whenever the sender requests it. When the sender requests remote confirmation, when the transmission ends the Presentation remains in TRANSMITTED state and starts a timeout waiting for the remote response. If the timeout expires without the receiver indicating the result of the download, the sender connects and asks for it. If the response is that the download process has not yet finished, a new timeout is started until retries are exhausted; otherwise, the post-send user process is launched with result 200 if the download has failed or 0 if it has completed successfully. #### Editran cryptography **Graphical utility for key management** A Java 6 application for key management has been added to CRIPTOlib, providing a graphical user interface that simplifies the consultation and generation of keys stored in the files ***ckds.des*** and ***ckds.rsa***. The utility is delivered in a JAR file called EDItranCript.jar. See the document *CRIPTOlib/DES 3.0 User Manual* for usage information. **Thread-safe CRIPTOlib/DES code** The code of the CRIPTOlib/DES library has been modified so that it can be used safely in multithreaded applications, that is, it works correctly during the simultaneous execution of several threads. #### editran /GT: Web application for transmission scheduling. Transmission manager that incorporates the following functionality: * Configuration for scheduling Sends and Receives, highly parameterizable, allowing definition of time windows, retries, post-processes, etc. * Consultation of information about the transmissions that have been carried out (sent files, transmission start and end date-time, current status of each transmission...). * Log of transmission incidents that have ended with some type of error. This functionality existed in previous versions only for Windows. In this version it is available for all OSs and has been designed as a Web application. The user can access the application from a browser. The web browsers tested are: IE8, IE9, Firefox and Chrome. #### editran /PX **Incorporation of route table** It has been added that the same proxy can listen on several IPs and/or ports and that each one can also be associated with different Hosts. Each route will establish a listening address and the corresponding list of Hosts so that for each incoming connection the Hosts will be tried in the order they are listed. That is, only if the connection with the first Host fails will the first backup be tried, and so on. A maximum of 10 routes can be defined. An example of a configuration with several routes would be: Current configuration of the local environment: Name (or IP) - listening port: 127.0.0.1 - 1111 Name (or IP) - HOST port: 1.1.1.1 - 1111 Name (or IP) - listening port: 127.0.0.1 - 2222 Name (or IP) - HOST port: 2.2.2.2 - 2222 Name (or IP) - HOST port: 3.3.3.3 - 3333 **Graphical utility for configuration** The configuration of the Editran Proxy in previous versions was done in command mode. In this version, a utility has also been incorporated that allows doing it through a graphical interface. It is a Java 6 application delivered in a JAR file called ConfigurarProxy.jar. See the document *EDItran/PX 5.1 Installation and User Manual* for usage information. **Log file size limit** The log file generated by the editran /PX and editran /TX gateways has been limited in this version to a maximum size configurable by the user. When this is exceeded, the log file is rotated, leaving the old one renamed as log\.txt. By default, the maximum assigned size is 1 GB. ### Fixed issues | **Code** | **Module** | **OS** | **Description** | | ----------- | ------------ | ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **I502-01** | editran /GC | All | editran /GC only generates DES subsystems with a single key length; however, they were mistakenly included as double in the ckds.des file. | | **I502-02** | Converters | HPs, Linux | When receiving from uncompressed V4.0 remote entities, the download fails due to total checking. | | **I502-04** | editran /X25 | Sun, Aix | Outgoing connections are rejected by the remote side due to NRI validation. | | **I502-05** | editran /X25 | HPs | Incoming calls always reach Editran as reverse charged even if it is not included in the facilities. | | **I502-13** | editran /X25 | Aix | Incoming calls without user data or facilities caused a memory failure. | | **I502-14** | EDITRAN/TCP | HP-Itanium | A transient failure in accept() caused Editran to stop handling incoming connections. Outgoing ones continued to work without problems. | | **I502-17** | MenuG | Windows | Fails with Presentations with names of length 26 (maximum possible). | | **I502-19** | editran /AL | All | Whenever the SMTP server supports the AUTH extension, the user was forced to authenticate even when it was not necessary. | | **I502-20** | Converters | All | Variable files with the last line without separator were loaded, but the remote download failed. | | **I502-22** | editran /CL | Windows | In some cases, the client Menu/G stored data in the server status file in an incorrect format. | | **I502-23** | editran /CL | Windows | In the distributed menus without administrator license, every time a key is pressed on the session list an error message appears. | | **I502-24** | editran /GT | Windows | In scheduled sends, if there is a post-process to move files and it fails, the task ends as successfully completed and this causes the file to be sent repeatedly until it manages to move it | | **I502-26** | editran /X25 | HPs | Random stop of the process related to connection failures. | | **I502-27** | Menus | Linux | The menus close when recovering the previous window due to a memory problem. | | **I502-28** | editran /GC | All | When generating an Own DES key, which must be signed, the exported file contains the version of the first local RSA subsystem instead of the version of the one that was actually chosen. | | **I502-29** | FichEmi | Windows | It did not modify the list of files to be sent in the editran /G profile. | | **I502-30** | editran /P | All | The connection time control did not work correctly with time ranges in which the start time is greater than the end time. | | **I502-31** | editran /GT | Windows | editran /G ignores hidden files, but editran /GT did not. This caused the scheduler to launch requests to editran /G that failed because there was no data to send. | | **I502-32** | Converters | All | On reception, the converter would get stuck when setting the reception destination to a year mask with maximum size (for example: %2Y). | | **I502-33** | editran /CL | Windows | When validation fails when creating/modifying the profile, the window does not close but the error is not reported to the user. | | **I502-34** | editran /GC | Windows | The graphical interface has a maximum limit of 100 subsystems. When this limit is exceeded the lists remain empty but no warning message is shown. | | **I502-36** | editran /GT | Windows | In reception windows, the user is allowed to modify the check for only one transmission per window. | | **I502-42** | License/SSL | All | The generation of SSL licenses fails when in the template the field **instances** exceeds the 40-byte limit. | | **I502-43** | IPCs | All | Random stop of Editran due to a failure in the exchange of information between the processes and the menus. | | **I502-44** | editran /GT | Windows | The process did not release resources correctly, which in the long run could have consequences for the OS. | | **I502-57** | editran /GC | All | When migrating data from editran /GC, keys were lost. | --- # 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/novedades/previas.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.