This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new c0c69284a8ea CAMEL-25992: camel-pqc - sync the 4.22 and 4.18 upgrade
guides on main (#28332)
c0c69284a8ea is described below
commit c0c69284a8ea4ab3fd78ad4384d1f12e38a3a9b8
Author: Claus Ibsen <[email protected]>
AuthorDate: Fri Oct 23 10:21:45 2026 +0200
CAMEL-25992: camel-pqc - sync the 4.22 and 4.18 upgrade guides on main
(#28332)
Add the camel-pqc note of the CAMEL-25992 backports (4.22.3 and 4.18.6) to
the 4.22 and 4.18 upgrade guides on main, next to the 4.24 entry from #28296.
Docs only.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
---
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 14 ++++++++++++++
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 15 +++++++++++++++
2 files changed, 29 insertions(+)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
index 79a128f6f35c..8491caa57913 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
@@ -422,6 +422,20 @@ channel of its endpoint, for every operation. To choose a
different channel for
`CamelPubNubOverrideChannel` header (`PubNubConstants.OVERRIDE_CHANNEL`).
Routes that set `CamelPubNubChannel` to pick
the channel of a pubnub producer must set `CamelPubNubOverrideChannel` instead.
+=== camel-pqc - message bodies are signed and verified over their bytes
+
+The `sign` and `verify` operations now sign and verify the message body over
its bytes for every body type that has a
+well-defined binary form. A `byte[]` or `InputStream` body, a `java.io.File`
or `java.nio.file.Path` body, and a file
+from a file consumer (a `GenericFile` body), are read as bytes. A `String` (or
any `CharSequence`) body is encoded as
+UTF-8, and any other body that has a binary type converter (for example a
`java.nio.ByteBuffer`, a
+`java.io.ByteArrayOutputStream`, a Netty `ByteBuf` or a Vert.x `Buffer`) is
signed over those bytes.
+
+A body with no binary representation (for example a `Map` or a POJO) is no
longer signed over its `toString()`: it is
+now rejected with an `InvalidPayloadException`. Convert such a body to a
`String`, `byte[]` or other binary type
+earlier in the route.
+
+Signatures created by earlier versions may not verify and need to be created
again.
+
== Upgrading from 4.18.4 to 4.18.5
=== camel-azure-eventhubs
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
index 58e8a8ebe589..dbe1c1b8eb7f 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
@@ -2093,6 +2093,21 @@ already UTF-8 (JEP 400), so this is a no-op there; on
Java 17 with a non-UTF-8 d
signature of a non-ASCII `String` payload changes. Binary bodies (`byte[]`,
`InputStream`) are
unaffected, as they are signed byte-for-byte.
+=== camel-pqc - message bodies are signed and verified over their bytes
+
+The `sign`, `verify`, `hybridSign` and `hybridVerify` operations now read a
`java.io.File` or `java.nio.file.Path`
+body, and a file from a file consumer (a `GenericFile` body), as bytes from
the file, the same way as a `byte[]` or
+`InputStream` body. A `String` (or any `CharSequence`) body is encoded as
UTF-8, and any other body that has a binary
+type converter (for example a `java.nio.ByteBuffer`, a
`java.io.ByteArrayOutputStream`, a Netty `ByteBuf` or a Vert.x
+`Buffer`) is signed over those bytes.
+
+A body with no binary representation (for example a `Map` or a POJO) is no
longer signed over its `toString()`: it is
+now rejected with an `InvalidPayloadException`. Convert such a body to a
`String`, `byte[]` or other binary type
+earlier in the route.
+
+Signatures created by earlier versions over a `File`, `Path`, `GenericFile` or
other non-`byte[]`/`InputStream` body
+may not verify and need to be created again.
+
=== camel-sql - Schema-qualified aggregation repository names
The table-name validation in `JdbcAggregationRepository` now accepts
schema-qualified names
