<!-- Provide a general summary of your proposed changes in the Title field above --> ### Description Smoke-test RFC 8879 TLS Certificate Compression. Depends on https://github.com/tlsfuzzer/tlslite-ng/pull/484 ### Motivation and Context GnuTLS has support for it now, I want it to test it against tlsfuzzer. ### Checklist <!-- go over following points. check them with an `x` if they do apply, (they turn into clickable checkboxes once the PR is submitted, so no need to do everything at once) if you're unsure about any of those items, just ask in comment to PR if the PR resolves an issue, please add further checkboxes that describe the action items or test scenarios from it --> - [ ] I have read the [CONTRIBUTING.md](https://github.com/tomato42/tlsfuzzer/blob/master/CONTRIBUTING.md) document and my PR follows [change requirements](https://github.com/tomato42/tlsfuzzer/blob/master/CONTRIBUTING.md#change-requirements) therein - [ ] the changes are also reflected in documentation and code comments - [ ] all new and existing tests pass (see CI results) - [ ] [test script checklist](https://github.com/tomato42/tlsfuzzer/wiki/Test-script-checklist) was followed for new scripts - [ ] new test script added to `tlslite-ng.json` and `tlslite-ng-random-subset.json` - [ ] new and modified scripts were ran against popular TLS implementations: - [ ] OpenSSL - [ ] NSS - [ ] GnuTLS - [ ] required version of tlslite-ng updated in requirements.txt and README.md <!-- Reviewable:start --> - - - This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/tlsfuzzer/tlsfuzzer/802) <!-- Reviewable:end --> __Originally posted by @t184256 in https://github.com/tlsfuzzer/tlsfuzzer/pull/802__
Description
Smoke-test RFC 8879 TLS Certificate Compression.
Depends on tlsfuzzer/tlslite-ng#484
Motivation and Context
GnuTLS has support for it now, I want it to test it against tlsfuzzer.
Checklist
tlslite-ng.jsonandtlslite-ng-random-subset.jsonThis change is
Originally posted by @t184256 in tlsfuzzer/tlsfuzzer#802