[
https://issues.redhat.com/browse/JGRP-2274?page=com.atlassian.jira.plugin...
]
Bela Ban commented on JGRP-2274:
--------------------------------
[~nsawadsky]: the above config doesn't work:
{noformat}
java.security.InvalidAlgorithmParameterException: Unsupported parameter:
javax.crypto.spec.IvParameterSpec@d5acec0
at com.sun.crypto.provider.CipherCore.init(CipherCore.java:520) ~[?:?]
at com.sun.crypto.provider.AESCipher.engineInit(AESCipher.java:346) ~[?:?]
at javax.crypto.Cipher.init(Cipher.java:1442) ~[?:?]
at javax.crypto.Cipher.init(Cipher.java:1375) ~[?:?]
at org.jgroups.protocols.Encrypt.initCipher(Encrypt.java:262) ~[classes/:?]
at org.jgroups.protocols.Encrypt.code(Encrypt.java:361) ~[classes/:?]
at org.jgroups.protocols.Encrypt.encrypt(Encrypt.java:350) ~[classes/:?]
at org.jgroups.protocols.Encrypt.down(Encrypt.java:149) ~[classes/:?]
{noformat}
ASYM_ENCRYPT: deprecate sign_msgs
---------------------------------
Key: JGRP-2274
URL:
https://issues.redhat.com/browse/JGRP-2274
Project: JGroups
Issue Type: Enhancement
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Major
Fix For: 4.0.12
In {{ASYM_ENCRYPT}}, signing messages means that the checksum of an encrypted message is
computed and used together with the secret key of the sender to sign the message. On the
receiver side, the public key of the sender is used to validate the signature.
However, this is redundant, as decryption of a message will fail if the contents have
been changed.
If needed, signing of messages can be done in a separate protocol.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)