{"id":113577,"date":"2024-02-13T22:02:48","date_gmt":"2024-02-13T20:02:48","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/obnovlenie-openvpn-2-6-9-s-izmeneniem-liczenzii"},"modified":"2024-02-13T22:02:48","modified_gmt":"2024-02-13T20:02:48","slug":"obnovlenie-openvpn-2-6-9-s-izmeneniem-liczenzii","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/obnovlenie-openvpn-2-6-9-s-izmeneniem-liczenzii","title":{"rendered":"Update OpenVPN 2.6.9 with license change","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

The release of OpenVPN 2.6.7 is prepared, a package for creating virtual private networks that allows for establishing an encrypted connection between two client machines or operating a centralized VPN server for simultaneous use by multiple clients. This new version is notable for its re-licensing. The project's code has transitioned from using the pure GPLv2 license to a combined license, where the GPLv2 text has been extended with an exception allowing linkage with code under the Apache 2.0 license, which is generally not possible without re-licensing the code due to the incompatibility between GPLv2 and Apache 2.0 licenses. <\/p>\n

The exception allows linking OpenVPN code with code from libraries distributed under the Apache 2.0 license and distributing the combined derivative product without adhering to the GPLv2 requirement of distributing linked libraries under the same license, while maintaining the effectiveness of all other conditions, such as providing source code for the derivative work. Primarily, the change aims to enable linking with the OpenSSL library, which is provided under the Apache 2.0 license. All OpenVPN code that could not be transitioned to the new licensing conditions, for example, due to the inability to contact the authors, has been removed or completely rewritten. <\/p>\n

Among the functional changes: <\/p>\n