[gnutls-devel] GnuTLS | algorithms: implement X448 key exchange and Ed448 signature scheme (!984)

Development of GNU's TLS library gnutls-devel at lists.gnutls.org
Thu Jan 23 10:00:54 CET 2020

Tim Rühsen commented on a discussion: https://gitlab.com/gnutls/gnutls/merge_requests/984#note_275772226

The fuzzer code is very small and should be easy to read (see `fuzz/gnutls_x509_parser_fuzzer.c`).

So it does call gnutls_x509_crt_import() with GNUTLS_X509_FMT_DER - so a DER cert is the right thing to have.

To check the code coverage of a single fuzzer:
./configure --enable-code-coverage --disable-doc
make clean
make check -C fuzz TESTS=gnutls_x509_parser_fuzzer
make code-coverage-capture
xdg-open file:///usr/oms/src/gnutls/GnuTLS-3.6.12-coverage/index.html

So you can see if the new code is really covered by the fuzzer when used with the existing corpora in `fuzz/gnutls_x509_parser_fuzzer.in` (in this case the "fuzzer" is compiled as a unit-test).

Possibly, you need to run the real fuzzer first to generate new corpora (= new discovered code paths). To do that, see `fuzz/README.md` and best go with clang fuzzing, then let the fuzzer run for ~10 minutes and check code coverage again. The switch between 'test' and 'fuzzer' mode requires a rebuild starting with `./configure...`.

Let me know if I can help. E.g. you add the cert to the branch, I check it out, generate new corpora and add them via git commit.

Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/merge_requests/984#note_275772226
You're receiving this email because of your account on gitlab.com.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20200123/e132c6cd/attachment-0001.html>

More information about the Gnutls-devel mailing list