Hello,
The attached patch corrects the name used for the windows dlls. With
the current naming, it is not possible to update an existing version
of nettle by dropping the new files in place and the patch fixes that.
regards,
Nikos
Hello,
I've now completed enabling the undefined sanitizer for gnutls, and
may be a good idea to use it for nettle to. The following patch
enables running the test suite of nettle under libasan (to detect any
invalid memory accesses/writes), and the undefined sanitizer.
I've run a test build, and the libasan build succeeds but the libubsan
builds fail:
https://gitlab.com/gnutls/nettle/builds/773956
Its complaints are not that critical for the targetted platforms but
may be nice not to rely on undefined behavior.
regards,
Nikos
Hi,
I did a quick fuzzing test of the command line tools coming with nettle.
echo "]"|sexp-conv
will cause an abort call and
echo "{MiM}"|sexp-conv
causes an assert:
sexp-conv: /var/tmp/portage/dev-libs/nettle-3.2/work/nettle-3.2/tools/input.c:128:
sexp_input_start_coding: Assertion `!input->coding' failed.
Not sure how relevant these tools are, but usually abort/assert calls
are debugging tools for situations in a software that should never
happen on normal operations.
--
Hanno Böck
https://hboeck.de/
mail/jabber: hanno(a)hboeck.de
GPG: BBB51E42
Hello Niels,
Do you plan a backport of the carry propagation fix in secp384 [0] for
nettle 2.7.1? My limited understanding of the 3.2 assembly file
wouldn't work out of the box in 2.7 due to the change from ecc_curve to
ecc_modulus.
The fix for the secp256r1 issue [1] looks quite trivial to backport if
p->m is replaced by ecc->p. Is my understanding correct?
regards,
Nikos
[0]. https://git.lysator.liu.se/nettle/nettle/commit/fa269b6ad06dd13c90
1dbd84a12e52b918a09cd7
[1]. https://git.lysator.liu.se/nettle/nettle/commit/c71d2c9d20eeebb985
e3872e4550137209e3ce4d