Drivers with deactivated encryption may silently enable encryption
Details
| Detail name | Value |
|---|---|
| Changelog Number | 15398 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 7.0.0 |
| Fix Versions | Exasol 7.1.0 |
| Resolution Date | 2021-08-03 |
Background
Exasol drivers (JDBC, ODBC, ADO.NET) use encrypted connections by default to communicate with the database. Encryption can be deactivated on the driver-side.
Description
The driver will silently enable encryption if the following conditions are met
- Encryption is deactivated in the driver (e.g. by using the connection string parameter encryption=0 for JDBC)
- Encryption is enforced in the database (database parameter -forceProtocolEncryption=1)
Workaround
There is no workaround
Fix
Those connections now fail instead of silently enabling encryption.