You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by "Colm O hEigeartaigh (Jira)" <ji...@apache.org> on 2025/03/04 11:56:00 UTC

[jira] [Comment Edited] (SANTUARIO-625) Security warning is always logged when using ECDH with AES-KW

    [ https://issues.apache.org/jira/browse/SANTUARIO-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17932292#comment-17932292 ] 

Colm O hEigeartaigh edited comment on SANTUARIO-625 at 3/4/25 11:55 AM:
------------------------------------------------------------------------

[~jrihtarsic] Perhaps you can help with this?


was (Author: coheigea):
[~rihtajo] Perhaps you can help with this?

> Security warning is always logged when using ECDH with AES-KW
> -------------------------------------------------------------
>
>                 Key: SANTUARIO-625
>                 URL: https://issues.apache.org/jira/browse/SANTUARIO-625
>             Project: Santuario
>          Issue Type: Bug
>          Components: Java
>    Affects Versions: Java 3.0.5, Java 4.0.3
>            Reporter: Thomas Beckers
>            Assignee: Colm O hEigeartaigh
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: image-2025-03-04-12-44-37-670.png
>
>
> In SANTUARIO-511 ECDH was implemented for key agreement.
> But when using ECDH with AES key wrapping Santuario always produces a warning message that "Cryptographic algorithm may not be secure":
> !image-2025-03-04-12-44-37-670.png|width=456,height=232!
> There seems to be no way to disable this message exception muting the logger. What was the reason behind this warning message?
> The use of ECDH (with ephermeral keys) with AES-KW is e.g. mandatory in the German energy market ([https://www.bundesnetzagentur.de/DE/Beschlusskammern/BK06/BK6_83_Zug_Mess/835_mitteilungen_datenformate/Mitteilung_46/Anlagen/AS4-Profil_1.1_v13.pdf?__blob=publicationFile&v=1).]
> Should this warning be just removed?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)