We conducted tests using the library's TLS implementation and noticed that the configuration does not match the one given in the SHIP specification. In particular, ECDSA-SHA1 is offered as a signature and hash algorithm. Since this library could be used in products that require approval from the German Federal Office for Information Security (BSI), it might be good to adjust the library’s default configuration so that it complies with the requirements of the specification. This would also bring it into compliance with BSI-TR 02102-2.
However, there is one area where it might make sense to deviate from the specification’s requirements: The current configuration already supports TLS 1.3 post-quantum algorithms (X25519MLKEM768).
Summary: SHA-1 should definitely be disabled, and support for PQC algorithms should perhaps be optional.
We conducted tests using the library's TLS implementation and noticed that the configuration does not match the one given in the SHIP specification. In particular, ECDSA-SHA1 is offered as a signature and hash algorithm. Since this library could be used in products that require approval from the German Federal Office for Information Security (BSI), it might be good to adjust the library’s default configuration so that it complies with the requirements of the specification. This would also bring it into compliance with BSI-TR 02102-2.
However, there is one area where it might make sense to deviate from the specification’s requirements: The current configuration already supports TLS 1.3 post-quantum algorithms (X25519MLKEM768).
Summary: SHA-1 should definitely be disabled, and support for PQC algorithms should perhaps be optional.