Incompatibility between Java-DTLS 1.0.19 and Bouncy Castle 1.80

[hpanda-dev]

We are currently using Bouncy Castle v1.64, but due to multiple known vulnerabilities and security fixes introduced in later versions, we are planning to upgrade to a more recent release.

However, after upgrading to Bouncy Castle v1.80, we encountered compatibility issues with Java-DTLS v1.0.19. The DTLS handshake and cryptographic operations fail or behave unexpectedly. These issues appear to begin from Bouncy Castle v1.65 onwards.

Below are some of the errors observed during update:

java-dtls/src/main/java/com/mobius/software/iot/dal/crypto/AsyncDtlsRecordLayer.java:[61,22] cannot find symbol symbol: class ProtocolVersion location: class com.mobius.software.iot.dal.crypto.AsyncDtlsRecordLayer java-dtls/src/main/java/com/mobius/software/iot/dal/crypto/AsyncDtlsRecordLayer.java:[57,19] cannot find symbol symbol: class TlsPeer location: class com.mobius.software.iot.dal.crypto.AsyncDtlsRecordLayer java-dtls/src/main/java/com/mobius/software/iot/dal/crypto/AsyncDtlsRecordLayer.java:[71,13] cannot find symbol symbol: class TlsHandshakeHash location: class com.mobius.software.iot.dal.crypto.AsyncDtlsRecordLayer java-dtls/src/main/java/com/mobius/software/iot/dal/crypto/AsyncDtlsRecordLayer.java:[80,59] cannot find symbol symbol: class TlsPeer location: class com.mobius.software.iot.dal.crypto.AsyncDtlsRecordLayer java-dtls/src/main/java/com/mobius/software/iot/dal/crypto/AsyncDtlsRecordLayer.java:[80,140] cannot find symbol symbol: variable tlsContext location: variable tlsContext of type AsyncTlsContext java-dtls/src/main/java/com/mobius/software/iot/dal/crypto/AsyncDtlsRecordLayer.java:[80,160] cannot find symbol symbol: variable tlsContext location: variable tlsContext of type AsyncTlsContext java-dtls/src/main/java/com/mobius/software/iot/dal/crpyto/AysncDTLSRecorodLayeer.java:[108,12] cannot find symbol symbol: class ProtocolVersion location: class com.mobius.software.iot.dal.crypto

We would appreciate any insights or solutions to resolve this incompatibilty issue.

Thank you!