You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2026/10/23 05:26:00 UTC
[jira] [Resolved] (CAMEL-25992) camel-pqc - sign and verify File and Path bodies over their raw bytes
[ https://issues.apache.org/jira/browse/CAMEL-25992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-25992.
---------------------------------
Resolution: Fixed
Fixed via https://github.com/apache/camel/pull/28296 (merged to main as 014b1c1b26d1).
> camel-pqc - sign and verify File and Path bodies over their raw bytes
> ---------------------------------------------------------------------
>
> Key: CAMEL-25992
> URL: https://issues.apache.org/jira/browse/CAMEL-25992
> Project: Camel
> Issue Type: Bug
> Components: camel-pqc
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.18.6, 4.22.3, 4.24.0
>
>
> h3. Change
> Sign and verify {{java.io.File}}, {{java.nio.file.Path}} and file consumer ({{GenericFile}}) bodies over their raw content, the same way {{byte[]}} and {{InputStream}} bodies are handled since CAMEL-23847. Today a binary file from the file consumer cannot be signed at all ({{MalformedInputException}}). The hybrid operations (hybridSign / hybridVerify) get the same handling.
> h3. Details
> * {{PQCProducer}}: one body resolver shared by sign, verify, hybridSign and hybridVerify.
> * {{pqc-component.adoc}}: update the NOTE on supported body types.
> * Upgrade guide notes for 4.24, 4.22.3 and 4.18.6: signatures created by earlier versions over such bodies may not verify and need to be created again.
> * Tests for {{File}}, {{Path}} and file consumer bodies, including the hybrid operations.
> h3. Backports
> * 4.22.x: the same change as on main.
> * 4.18.x: the same change, together with the {{byte[]}} / {{InputStream}} handling of CAMEL-23847.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)