exhaustive checks on DC tests about go HOT 5 CLOSED

Yes, it is expected. It is really not needed to test all the conditions as the other ones will fail one way or another. The added of a dcCounter was a request, which I think is unnecessary as it tests with every possible algorithm the tls connection (while in truthness if the DC is able to be created and validated, then it should work).

I expected to change the way DC test work when the new API lands (next week when I return to work): the usage of callbacks make it almost impossible to check with different algos and variables.

from go.

I'm going to leave this open for a while until the design of the new API is taken into account.

from go.

the usage of callbacks make it almost impossible to check with different algos and variables

it is possible to create a factory of functions, so each produced function must use one combination of dc and signature scheme.

from go.

it is possible to create a factory of functions, so each produced function must use one combination of dc and signature scheme.

The callbacks will likely disappear in the new API by using the cert ones, so no need of it then.

from go.

Solved now.

from go.