Skip to content

Latest commit

 

History

History
67 lines (41 loc) · 3.6 KB

README.md

File metadata and controls

67 lines (41 loc) · 3.6 KB
Raw

Californium logo

Californium (Cf) - Interoperability Tests

Californium (Cf) is commonly used only on one side, e.g. as server or client, and an other implementation is used on the other side.

These Californium (Cf) - Interoperability Tests are intended to ensure interoperability with libcoap with gnutls, openssl, mbedtls and tinydtls DTLS 1.2 bindings.

Additionally, Mbed-TLS, openssl and tinydtls are tested for interoperability on their own.

Usage

This Interoperability Tests requires to have some binaries build and installed ahead.

For libcoap you will find some notes in LibCoapProcessUtil. The DTLS bindings requires also to install the DTLS libraries in order to build libcoap with that binding.

For openssl some notes are in OpenSslProcessUtil

For Mbed-TLS some notes are in MbedTlsProcessUtil

For tinydtls some notes are in TinydtlsProcessUtil. Ensure to use the ""feature/connection_id" to enable DTLS 1.2 CID support.

When the binaries a build and install in the "PATH", the tests are execute using

mvn test

This executes a common set of DTLS parameters. If you want more complete tests, use

mvn test -DINTENSIVE_TESTS=true

If you want to test the interoperability usingthe Bouncy Castle JCE use

mvn test -Pbc-tests

Both options may be used together.

Testing for randomly occurring failures

DTLS 1.2 uses handshake with some random artifacts, e.g. ECDHE uses ephemeral EC keys. Especially encoding errors in that parts are hard to find. Using the makes it simpler to execute the test much more times in order to check, if such a random failure occurs.

Californium comes for that case with the RepeatingTestRunner and the ParameterizedRepeatingTestRunner. Using them requires to edit the interop-tests, which are intended to be run multiple times.

 * @since 3.3
 */
@RunWith(RepeatingTestRunner.class)
public class MbedTlsClientAuthenticationInteroperabilityTest {

Adding @RunWith(RepeatingTestRunner.class) marks the test for that. The default is 100 times and using

mvn test -Dorg.eclipse.californium.elements.runner.TestRepeater.repeats=1000

enables to select an other number, here 1000.

Testing Interoperability Of Specific Versions

Just in the case someone needs to test with specific versions of the other implementations, that may work "out of the box" or not. Some of the libraries have bugs in single features on single versions so a failure requires then analysis and the knowledge to do so. Sometimes the CLI-API is changing, so also be careful with that.