Migration Guide 3.8

Table of Contents

• Breaking Changes
  • (3.8.1) Vert.x TCP Clients need to set the hostname verification algorithm

Note	We highly recommend the use of quarkus update to update to a new version of Quarkus. Items marked below with ⚙️ ✅ are automatically handled by quarkus update.

Quarkus 3.8 is an LTS version and the direct continuation of the 3.7 branch.

Breaking Changes

(3.8.1) Vert.x TCP Clients need to set the hostname verification algorithm

Until now, when a Vert.x TCP client establishes a TLS connection without setting the hostname verification algorithm, "" was used as the algorithm. "" skips the validation, meaning that you can be affected by man-in-the-middle attacks. This behavior changed in Vert.x 4.5.4 (integrated into Quarkus 3.8.1), as now, when establishing a TLS connection, the verification hostname algorithm must be set explicitly. It can be set to NONE (in the Quarkus configuration) or "" (programmatically) to have the same behavior.

This change of behavior only affects users explicitly creating Vert.x TCP clients directly (with Vertx.createNetClient())