[jira] [Commented] (JCS-229) LateralTCPListener class uses always StandardSerializer
[ https://issues.apache.org/jira/browse/JCS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518692#comment-17518692 ] Dorota Oeknigk-Urbanska commented on JCS-229: - https://github.com/apache/commons-jcs/pull/89 > LateralTCPListener class uses always StandardSerializer > --- > > Key: JCS-229 > URL: https://issues.apache.org/jira/browse/JCS-229 > Project: Commons JCS > Issue Type: Bug > Components: TCP Lateral Cache >Affects Versions: jcs-3.1 >Reporter: Dorota Oeknigk-Urbanska >Assignee: Thomas Vandahl >Priority: Major > Attachments: patch.diff > > Original Estimate: 4h > Remaining Estimate: 4h > > Version jcs-3.1 introduced an option to use EncryptingSerializer instead of > StandardSerializer. > However when EncryptingSerializer is configured for LTCP by : > jcs.auxiliary.LTCP.serializer=org.apache.commons.jcs3.utils.serialization.EncryptingSerializer > synchronization does not work. > LateralTCPSender supports custom Serializer (by constructor which allowed > LateralTCPService to pass Serializer as parameter)- and it's properly sending > encripted messages. LateralTCPListener does not support custom Serializer and > uses always StandardSerializer - which in this case when received message is > encripted fails. > > > Solution attached in patch.diff file. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (JCS-230) UDPDiscoveryReceiver with EncryptingSerializer fails
[ https://issues.apache.org/jira/browse/JCS-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518505#comment-17518505 ] Dorota Oeknigk-Urbanska commented on JCS-230: - https://github.com/apache/commons-jcs/pull/88 > UDPDiscoveryReceiver with EncryptingSerializer fails > > > Key: JCS-230 > URL: https://issues.apache.org/jira/browse/JCS-230 > Project: Commons JCS > Issue Type: Bug > Components: TCP Lateral Cache >Affects Versions: jcs-3.1 >Reporter: Dorota Oeknigk-Urbanska >Assignee: Thomas Vandahl >Priority: Major > Attachments: patch.diff, unitTests.patch.diff > > > Version jcs-3.1 introduced an option to use EncryptingSerializer instead of > StandardSerializer. > However when EncryptingSerializer is configured for LTCP by : > jcs.auxiliary.LTCP.serializer=org.apache.commons.jcs3.utils.serialization.EncryptingSerializer > UDPDiscoveryReceiver throws an error when trying to serialize received > message ( error bellow). > > Root cause of this error: > calling deSerialize method in line 265 : > serializer.deSerialize(byteBuffer.array(), null); > byteBuffer.array() - returns byte[] which size is the full capacity of > ByteBuffer not the size of recived message. > > > Apr 04, 2022 2:16:19 PM > org.apache.commons.jcs3.utils.discovery.UDPDiscoveryReceiver > SEVERE: Error receiving multicast packet > java.io.IOException: Error while decrypting > at > org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.decrypt(EncryptingSerializer.java:209) > at > org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.deSerialize(EncryptingSerializer.java:247) > at > org.apache.commons.jcs3.utils.discovery.UDPDiscoveryReceiver.run(UDPDiscoveryReceiver.java:265) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: javax.crypto.IllegalBlockSizeException: Input length must be > multiple of 16 when decrypting with padded cipher > at > java.base/com.sun.crypto.provider.CipherCore.prepareInputBuffer(CipherCore.java:1005) > at > java.base/com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:848) > at > java.base/com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:446) > at java.base/javax.crypto.Cipher.doFinal(Cipher.java:2202) > at > org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.decrypt(EncryptingSerializer.java:203) > ... 3 more > > > Solution attached in patch.diff file. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (JCS-230) UDPDiscoveryReceiver with EncryptingSerializer fails
[ https://issues.apache.org/jira/browse/JCS-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518220#comment-17518220 ] Dorota Oeknigk-Urbanska commented on JCS-230: - [~tv] - in attached file : initTests.patch.diff - I have attached new class with unit tests for UDPDiscoverySender with EncryptingSerializer. > UDPDiscoveryReceiver with EncryptingSerializer fails > > > Key: JCS-230 > URL: https://issues.apache.org/jira/browse/JCS-230 > Project: Commons JCS > Issue Type: Bug > Components: TCP Lateral Cache >Affects Versions: jcs-3.1 >Reporter: Dorota Oeknigk-Urbanska >Assignee: Thomas Vandahl >Priority: Major > Attachments: patch.diff, unitTests.patch.diff > > > Version jcs-3.1 introduced an option to use EncryptingSerializer instead of > StandardSerializer. > However when EncryptingSerializer is configured for LTCP by : > jcs.auxiliary.LTCP.serializer=org.apache.commons.jcs3.utils.serialization.EncryptingSerializer > UDPDiscoveryReceiver throws an error when trying to serialize received > message ( error bellow). > > Root cause of this error: > calling deSerialize method in line 265 : > serializer.deSerialize(byteBuffer.array(), null); > byteBuffer.array() - returns byte[] which size is the full capacity of > ByteBuffer not the size of recived message. > > > Apr 04, 2022 2:16:19 PM > org.apache.commons.jcs3.utils.discovery.UDPDiscoveryReceiver > SEVERE: Error receiving multicast packet > java.io.IOException: Error while decrypting > at > org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.decrypt(EncryptingSerializer.java:209) > at > org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.deSerialize(EncryptingSerializer.java:247) > at > org.apache.commons.jcs3.utils.discovery.UDPDiscoveryReceiver.run(UDPDiscoveryReceiver.java:265) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: javax.crypto.IllegalBlockSizeException: Input length must be > multiple of 16 when decrypting with padded cipher > at > java.base/com.sun.crypto.provider.CipherCore.prepareInputBuffer(CipherCore.java:1005) > at > java.base/com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:848) > at > java.base/com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:446) > at java.base/javax.crypto.Cipher.doFinal(Cipher.java:2202) > at > org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.decrypt(EncryptingSerializer.java:203) > ... 3 more > > > Solution attached in patch.diff file. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (JCS-230) UDPDiscoveryReceiver with EncryptingSerializer fails
[ https://issues.apache.org/jira/browse/JCS-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dorota Oeknigk-Urbanska updated JCS-230: Attachment: unitTests.patch.diff > UDPDiscoveryReceiver with EncryptingSerializer fails > > > Key: JCS-230 > URL: https://issues.apache.org/jira/browse/JCS-230 > Project: Commons JCS > Issue Type: Bug > Components: TCP Lateral Cache >Affects Versions: jcs-3.1 >Reporter: Dorota Oeknigk-Urbanska >Assignee: Thomas Vandahl >Priority: Major > Attachments: patch.diff, unitTests.patch.diff > > > Version jcs-3.1 introduced an option to use EncryptingSerializer instead of > StandardSerializer. > However when EncryptingSerializer is configured for LTCP by : > jcs.auxiliary.LTCP.serializer=org.apache.commons.jcs3.utils.serialization.EncryptingSerializer > UDPDiscoveryReceiver throws an error when trying to serialize received > message ( error bellow). > > Root cause of this error: > calling deSerialize method in line 265 : > serializer.deSerialize(byteBuffer.array(), null); > byteBuffer.array() - returns byte[] which size is the full capacity of > ByteBuffer not the size of recived message. > > > Apr 04, 2022 2:16:19 PM > org.apache.commons.jcs3.utils.discovery.UDPDiscoveryReceiver > SEVERE: Error receiving multicast packet > java.io.IOException: Error while decrypting > at > org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.decrypt(EncryptingSerializer.java:209) > at > org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.deSerialize(EncryptingSerializer.java:247) > at > org.apache.commons.jcs3.utils.discovery.UDPDiscoveryReceiver.run(UDPDiscoveryReceiver.java:265) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: javax.crypto.IllegalBlockSizeException: Input length must be > multiple of 16 when decrypting with padded cipher > at > java.base/com.sun.crypto.provider.CipherCore.prepareInputBuffer(CipherCore.java:1005) > at > java.base/com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:848) > at > java.base/com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:446) > at java.base/javax.crypto.Cipher.doFinal(Cipher.java:2202) > at > org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.decrypt(EncryptingSerializer.java:203) > ... 3 more > > > Solution attached in patch.diff file. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (JCS-229) LateralTCPListener class uses always StandardSerializer
[ https://issues.apache.org/jira/browse/JCS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dorota Oeknigk-Urbanska updated JCS-229: Description: Version jcs-3.1 introduced an option to use EncryptingSerializer instead of StandardSerializer. However when EncryptingSerializer is configured for LTCP by : jcs.auxiliary.LTCP.serializer=org.apache.commons.jcs3.utils.serialization.EncryptingSerializer synchronization does not work. LateralTCPSender supports custom Serializer (by constructor which allowed LateralTCPService to pass Serializer as parameter)- and it's properly sending encripted messages. LateralTCPListener does not support custom Serializer and uses always StandardSerializer - which in this case when received message is encripted fails. Solution attached in patch.diff file. was: Version jcs-3.1 introduced an option to use EncryptingSerializer instead of StandardSerializer. However when EncryptingSerializer is configured for LTCP by : jcs.auxiliary.LTCP.serializer=org.apache.commons.jcs3.utils.serialization.EncryptingSerializer synchronization does not work. LateralTCPSender supports custom Serializer (by constructor which allowed LateralTCPService to pass Serializer as parameter)- and it's properly sending encripted messages. LateralTCPListener does not support custom Serializer and uses always StandardSerializer - which in this case when received message is encripted fails. > LateralTCPListener class uses always StandardSerializer > --- > > Key: JCS-229 > URL: https://issues.apache.org/jira/browse/JCS-229 > Project: Commons JCS > Issue Type: Bug > Components: TCP Lateral Cache >Affects Versions: jcs-3.1 >Reporter: Dorota Oeknigk-Urbanska >Priority: Major > Attachments: patch.diff > > Original Estimate: 4h > Remaining Estimate: 4h > > Version jcs-3.1 introduced an option to use EncryptingSerializer instead of > StandardSerializer. > However when EncryptingSerializer is configured for LTCP by : > jcs.auxiliary.LTCP.serializer=org.apache.commons.jcs3.utils.serialization.EncryptingSerializer > synchronization does not work. > LateralTCPSender supports custom Serializer (by constructor which allowed > LateralTCPService to pass Serializer as parameter)- and it's properly sending > encripted messages. LateralTCPListener does not support custom Serializer and > uses always StandardSerializer - which in this case when received message is > encripted fails. > > > Solution attached in patch.diff file. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (JCS-230) UDPDiscoveryReceiver with EncryptingSerializer fails
[ https://issues.apache.org/jira/browse/JCS-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dorota Oeknigk-Urbanska updated JCS-230: Description: Version jcs-3.1 introduced an option to use EncryptingSerializer instead of StandardSerializer. However when EncryptingSerializer is configured for LTCP by : jcs.auxiliary.LTCP.serializer=org.apache.commons.jcs3.utils.serialization.EncryptingSerializer UDPDiscoveryReceiver throws an error when trying to serialize received message ( error bellow). Root cause of this error: calling deSerialize method in line 265 : serializer.deSerialize(byteBuffer.array(), null); byteBuffer.array() - returns byte[] which size is the full capacity of ByteBuffer not the size of recived message. Apr 04, 2022 2:16:19 PM org.apache.commons.jcs3.utils.discovery.UDPDiscoveryReceiver SEVERE: Error receiving multicast packet java.io.IOException: Error while decrypting at org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.decrypt(EncryptingSerializer.java:209) at org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.deSerialize(EncryptingSerializer.java:247) at org.apache.commons.jcs3.utils.discovery.UDPDiscoveryReceiver.run(UDPDiscoveryReceiver.java:265) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: javax.crypto.IllegalBlockSizeException: Input length must be multiple of 16 when decrypting with padded cipher at java.base/com.sun.crypto.provider.CipherCore.prepareInputBuffer(CipherCore.java:1005) at java.base/com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:848) at java.base/com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:446) at java.base/javax.crypto.Cipher.doFinal(Cipher.java:2202) at org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.decrypt(EncryptingSerializer.java:203) ... 3 more Solution attached in patch.diff file. was: Version jcs-3.1 introduced an option to use EncryptingSerializer instead of StandardSerializer. However when EncryptingSerializer is configured for LTCP by : jcs.auxiliary.LTCP.serializer=org.apache.commons.jcs3.utils.serialization.EncryptingSerializer UDPDiscoveryReceiver throws an error when trying to serialize received message ( error bellow). Root cause of this error: calling deSerialize method in line 265 : serializer.deSerialize(byteBuffer.array(), null); byteBuffer.array() - returns byte[] which size is the full capacity of ByteBuffer not the size of recived message. Apr 04, 2022 2:16:19 PM org.apache.commons.jcs3.utils.discovery.UDPDiscoveryReceiver SEVERE: Error receiving multicast packet java.io.IOException: Error while decrypting at org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.decrypt(EncryptingSerializer.java:209) at org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.deSerialize(EncryptingSerializer.java:247) at org.apache.commons.jcs3.utils.discovery.UDPDiscoveryReceiver.run(UDPDiscoveryReceiver.java:265) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: javax.crypto.IllegalBlockSizeException: Input length must be multiple of 16 when decrypting with padded cipher at java.base/com.sun.crypto.provider.CipherCore.prepareInputBuffer(CipherCore.java:1005) at java.base/com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:848) at java.base/com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:446) at java.base/javax.crypto.Cipher.doFinal(Cipher.java:2202) at org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.decrypt(EncryptingSerializer.java:203) ... 3 more > UDPDiscoveryReceiver with EncryptingSerializer fails > > > Key: JCS-230 > URL: https://issues.apache.org/jira/browse/JCS-230 > Project: Commons JCS > Issue Type: Bug > Components: TCP Lateral Cache >Affects Versions: jcs-3.1 >Reporter: Dorota Oeknigk-Urbanska >Priority: Major > Attachments: patch.diff > > > Version jcs-3.1 introduced an option to use EncryptingSerializer instead of > StandardSerializer. > However when EncryptingSerializer is configured for LTCP by : > jcs.auxiliary.LTCP.serializer=org.apache.commons.jcs3.utils.serialization.EncryptingSerializer > UDPDiscoveryReceiver throws an error when trying to serialize received > message ( error bellow). > > Root cause of this error: > calling deSerialize method in line 265 : > serializer.deSerialize(byteBuffer.array(), null); > byteBuffer.array() - returns byte[] which size is the full capacity of > ByteBuffer not the size of recived message. > > > Apr 04, 2022 2:16:19 PM > org.apache.commons.jcs3.utils.discovery.UDPDiscoveryReceiver > SEVERE: Error receiving multicast packet > java.io.IOException: Error whi
[jira] [Created] (JCS-230) UDPDiscoveryReceiver with EncryptingSerializer fails
Dorota Oeknigk-Urbanska created JCS-230: --- Summary: UDPDiscoveryReceiver with EncryptingSerializer fails Key: JCS-230 URL: https://issues.apache.org/jira/browse/JCS-230 Project: Commons JCS Issue Type: Bug Components: TCP Lateral Cache Affects Versions: jcs-3.1 Reporter: Dorota Oeknigk-Urbanska Attachments: patch.diff Version jcs-3.1 introduced an option to use EncryptingSerializer instead of StandardSerializer. However when EncryptingSerializer is configured for LTCP by : jcs.auxiliary.LTCP.serializer=org.apache.commons.jcs3.utils.serialization.EncryptingSerializer UDPDiscoveryReceiver throws an error when trying to serialize received message ( error bellow). Root cause of this error: calling deSerialize method in line 265 : serializer.deSerialize(byteBuffer.array(), null); byteBuffer.array() - returns byte[] which size is the full capacity of ByteBuffer not the size of recived message. Apr 04, 2022 2:16:19 PM org.apache.commons.jcs3.utils.discovery.UDPDiscoveryReceiver SEVERE: Error receiving multicast packet java.io.IOException: Error while decrypting at org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.decrypt(EncryptingSerializer.java:209) at org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.deSerialize(EncryptingSerializer.java:247) at org.apache.commons.jcs3.utils.discovery.UDPDiscoveryReceiver.run(UDPDiscoveryReceiver.java:265) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: javax.crypto.IllegalBlockSizeException: Input length must be multiple of 16 when decrypting with padded cipher at java.base/com.sun.crypto.provider.CipherCore.prepareInputBuffer(CipherCore.java:1005) at java.base/com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:848) at java.base/com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:446) at java.base/javax.crypto.Cipher.doFinal(Cipher.java:2202) at org.apache.commons.jcs3.utils.serialization.EncryptingSerializer.decrypt(EncryptingSerializer.java:203) ... 3 more -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (JCS-229) LateralTCPListener class uses always StandardSerializer
[ https://issues.apache.org/jira/browse/JCS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dorota Oeknigk-Urbanska updated JCS-229: Attachment: patch.diff > LateralTCPListener class uses always StandardSerializer > --- > > Key: JCS-229 > URL: https://issues.apache.org/jira/browse/JCS-229 > Project: Commons JCS > Issue Type: Bug > Components: TCP Lateral Cache >Affects Versions: jcs-3.1 >Reporter: Dorota Oeknigk-Urbanska >Priority: Major > Attachments: patch.diff > > Original Estimate: 4h > Remaining Estimate: 4h > > Version jcs-3.1 introduced an option to use EncryptingSerializer instead of > StandardSerializer. > However when EncryptingSerializer is configured for LTCP by : > jcs.auxiliary.LTCP.serializer=org.apache.commons.jcs3.utils.serialization.EncryptingSerializer > synchronization does not work. > LateralTCPSender supports custom Serializer (by constructor which allowed > LateralTCPService to pass Serializer as parameter)- and it's properly sending > encripted messages. LateralTCPListener does not support custom Serializer and > uses always StandardSerializer - which in this case when received message is > encripted fails. > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (JCS-229) LateralTCPListener class uses always StandardSerializer
Dorota Oeknigk-Urbanska created JCS-229: --- Summary: LateralTCPListener class uses always StandardSerializer Key: JCS-229 URL: https://issues.apache.org/jira/browse/JCS-229 Project: Commons JCS Issue Type: Bug Components: TCP Lateral Cache Affects Versions: jcs-3.1 Reporter: Dorota Oeknigk-Urbanska Version jcs-3.1 introduced an option to use EncryptingSerializer instead of StandardSerializer. However when EncryptingSerializer is configured for LTCP by : jcs.auxiliary.LTCP.serializer=org.apache.commons.jcs3.utils.serialization.EncryptingSerializer synchronization does not work. LateralTCPSender supports custom Serializer (by constructor which allowed LateralTCPService to pass Serializer as parameter)- and it's properly sending encripted messages. LateralTCPListener does not support custom Serializer and uses always StandardSerializer - which in this case when received message is encripted fails. -- This message was sent by Atlassian Jira (v8.20.1#820001)
