Add DTLS 1.2 wolfSSL Client/Server Cert Req / NReq arg files#219
Conversation
|
I added DTLS 1.2 server cert req / nreq arg files. to test wolfSSL 5.7.6 server cert reqto test wolfSSL 5.7.6 server cert nreq |
|
I use the following command: and I get the following output (about 10 hours for the full learning): And it costs about 78 minutes to get the last hypothesis. Also, after generating PDF I didn't see happy path, so I also added the happy path. For your convenience, the happy path looks like this: |
|
I got different number of states and hypotheses that you mentioned in email: I use command: I get the following output (about 4.44 hours for the full learning): And it costs about 24.65 minutes to get the last hypothesis. |
|
Thanks for these results. Indeed, I also get different results (for some configurations) depending on the machine I use, so there seems to be some non-determinism (and sometimes some warnings/crashes) either due to the timeout values used, due to the DTLS 1.2 SUT, or some other unknown issue. Before we investigate this further, I suggest we first check the files in this PR. I've requested a review from @pfg666 once he finds some time or is back from vacations. |
|
Here are my findings so far:
I suspect the cause of non-determinism lies in wolfSSL, as its support for completing a handshake with certificates via the client utility is recent. Of course, more investigation is needed. For now, I will try learning using the multi-query oracle, and check whether I get consistent results (two experiments for the same configuration result in the same results). If that's the case, then it might be worth changing all experiments in the paper to use multi-query oracle. |
a61952c to
dcbba79
Compare
|
@kostis @pfg666 We can install latest wolfSSL by: After that, we can try to complete DTLS handshake by: Client (CERT REQ) Client (CERT OPT) Similarly, we can run the learning by: Client (CERT OPT) |
…and-Nreq-Arg-Files


Currently, I added wolfSSL DTLS 1.2 Client Cert Req / NReq arg files
I don't know how to name these files, so I use 'x' as a placeholder.
Also, wolfSSL 5.7.6 is the default version, so we don't need to specify version number manually.
And I tested that we can complete handshake with the following tests:
to test wolfSSL 5.7.6 client cert req
to test wolfSSL 5.7.6 client cert nreq