Fortifying Security: 4D Embraces OpenSSL 3.1

In an era where data security is paramount, updating security libraries is crucial.
4D v20 has taken a significant step forward by upgrading its OpenSSL library from version 1.1 to 3.1.
This advancement brings forth a multitude of advantages and improvements for 4D developers, enabling them to build applications that are not only highly secure but also exceptionally efficient.
Now, let’s explore these benefits in detail.


First of all, don’t worry about this security update.
Blobs and zip files encrypted with OpenSSL 1.1 can still be decrypted with OpenSSL3.1.
The digests generated with the Generate digest command are identical to the two versions.
And the data encryption is not impacted by the update.

Enhanced Security

OpenSSL has a large community of developers who actively contribute to its development and maintenance. By upgrading to the latest version (3.1), 4D developers gain access to the expertise of this community. The upgraded OpenSSL library receives continuous bug fixes, security updates, and feature enhancements, ensuring that potential vulnerabilities or issues are addressed promptly. This community-driven support helps maintain the stability, reliability, and security of 4D applications in the face of evolving cybersecurity challenges.

About the Transport Layer Security (TLS)

TLS is used in the server parts of 4D: Web server, SQL server, Web Sockets server, and so on.
TLS 1.0 (released in 1999) and TLS 1.1 (released in 2006) are deprecated. To follow best practices, these TLS versions are also deprecated in 4D. All server parts of 4D now use TLS 1.3 (released in 2018) as the default version. You can force the servers to use TLS 1.2 (released in 2008) as a minimal version using the SET DATABASE PARAMETER command with the Min TLS version selector. But remember that if you try to define TLS 1.0 or TLS 1.1 as a minimal version, 4D will use the default version: TLS 1.3.
Note that there are no changes about TLS versions on client parts of 4D (Web Area, HTTPRequest, mail transporters, etc.).

4D continues to get increasingly secure without having to do a thing!

We constantly strive to provide our users with the best possible experience, and we encourage you to share your thoughts and feedback on the 4D forum. Your feedback helps us better understand your needs and continuously improve our products and services.

• Product Owner •Damien Fuzeau has joined the 4D Product team in February 2019. As a Product Owner, he is in charge of writing user stories, then translating them to functional specifications. His job also entails making sure that the feature implementations delivered are meeting the customer needs.Damien is graduated from the University of Nantes in software engineering. He spent more than 23 years in its former company, first as developer (discovering 4D in 1997), and later as engineering manager and software architect. This company is a 4D OEM partner and deployed 4D based business softwares for thousands users, on hundreds servers. So, Damien is used to 4D development and deployment in a multi-language context.