Awesome, Lance! Thank you.

While I was implementing and doing benchmarks of AF_KTLS, I used [1]. It is not the best possible solution, but it was/is useful (note some errors are not handled now - e.g. when a client does not connect to a TCP server, ...). I would like to reorganize this git repo and make the repo easier for development/testing/benchmarks, as suggested by @nmav in https://github.com/fridex/af_ktls/issues/17 Could we introduce one tool for automated tests and benchmarks not to diverge?

I don't have time to make a bigger review now, but few notes:

I see that you use OpenSSL, that's great, since I use GnuTLS in [1]. We can cross-test the implementation to be sure that AF_KTLS works with OpenSSL and GnuTLS as well.
I see that you copied parts of AF_KLTS. I would like to avoid it.
Since we are trying to make TLS/DTLS faster in AF_KTLS in some scenarios, I would like to have benchmarks evaluated automatically during the implementation to see if we are actually making our solution faster.
Each time there will be a bug/enhancement, we can introduce a test case in one tool to cover examples/exceptions/...

Take a look at [1] to save some time and efforts. Some parts could be reused.

[1] https://github.com/fridex/af_ktls-tool

Test suite #47

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions