nettle-bugs January 2016

nettle-bugs@lists.lysator.liu.se

6 participants
6 discussions

ANNOUNCE: Nettle-3.2
by nisse＠lysator.liu.se 28 Jan '16

28 Jan '16

I'm happy to announce a new release of GNU Nettle, a low-level cryptographics library. This is mainly a bug fix release, with few new features. The Nettle home page can be found at https://www.lysator.liu.se/~nisse/nettle/, and the manual at https://www.lysator.liu.se/~nisse/nettle/nettle.html. NEWS for the Nettle 3.2 release Bug fixes: * The SHA3 implementation is updated according to the FIPS 202 standard. It is not interoperable with earlier versions of Nettle. Thanks to Nikos Mavrogiannopoulos. To easily differentiate at compile time, sha3.h defines the constant NETTLE_SHA3_FIPS202. * Fix corner-case carry propagation bugs affecting elliptic curve operations on the curves secp_256r1 and secp_384r1 on certain platforms, including x86_64. Reported by Hanno Böck. New features: * New functions for RSA private key operations, identified by the "_tr" suffix, with better resistance to side channel attacks and to hardware or software failures which could break the CRT optimization. See the Nettle manual for details. Initial patch by Nikos Mavrogiannopoulos. * New functions nettle_version_major, nettle_version_minor, as a run-time variant of the compile-time constants NETTLE_VERSION_MAJOR and NETTLE_VERSION_MINOR. Optimizations: * New ARM Neon implementation of the chacha stream cipher. Miscellaneous: * ABI detection on mips, with improved default libdir location. Contributed by Klaus Ziegler. * Fixes for ARM assembly syntax, to work better with the clang assembler. Thanks to Jukka Ukkonen. * Disabled use of ifunc relocations for fat builds, to fix problems most easily triggered by using dlopen RTLD_NOW. The shared library names are libnettle.so.6.2 and libhogweed.so.4.2, with sonames still libnettle.so.6 and libhogweed.so.4. It is intended to be fully binary compatible with nettle-3.1. https://ftp.gnu.org/gnu/nettle/nettle-3.2.tar.gz ftp://ftp.gnu.org/gnu/nettle/nettle-3.2.tar.gz https://www.lysator.liu.se/~nisse/archive/nettle-3.2.tar.gz Happy hacking, /Niels Möller -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 0

Nettle-3.2 plans
by nisse＠lysator.liu.se 27 Jan '16

27 Jan '16

Now I think the documentation of the new RSA tr functions is in reasonable shape, and I'd like to get a release out real soon now. I've put a release candidate at https://www.lysator.liu.se/~nisse/archive/nettle-3.2rc1.tar.gz, and I've updated the release planning at https://www.lysator.liu.se/~nisse/nettle/plan.html. I've spent the day doing tests on various emulated systems. The ARM and PPC emulators have completed the tests with no issues, MIPS and M68K emulators still working hard. Currently, I'm doing tests on gnu/linux and freebsd (the sparc solaris systems I used to do some testing on have been powered down). If no last minute problems are discovered, I plan to make the release earliest on Wednesday evening (January 27). All testing is highly appreciated. In particular, if Mac, Windows, or some more obscure systems are important to you, now is the time to test. As a reminder, non-GNU make programs are not really supported. Review of the NEWS file and the new RSA material in the manual would also be very nice. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

3 3

Re: nettle-pbkdf2 dumps core when executed with an unknown option
by nisse＠lysator.liu.se 26 Jan '16

26 Jan '16

dongsheng zhang <dongsheng.zhang(a)oracle.com> writes: > Will a newer version of nettle with the fix be released soon please? Your bug report was very timely, a new relase, nettle-3.2, is planned this week. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 0

Re: nettle-pbkdf2 dumps core when executed with an unknown option
by nisse＠lysator.liu.se 26 Jan '16

26 Jan '16

dongsheng zhang <dongsheng.zhang(a)oracle.com> writes: > We have found that nettle-pbkdf2 dumps core when executed with an > unknown option. Thanks for the bug report. There was a missing "case '?':" in the option handling, and a similar bug also in nettle-hash. Fix checked in now, the programs should display a usage message and exit. (Some of the other programs just call exit (EXIT_FAILURE) in this situation, and some lack usage messages, so it's not completely consistent). Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 0

using gitlab CI for nettle
by Nikos Mavrogiannopoulos 25 Jan '16

25 Jan '16

Hi, gitlab now allows mirroring projects so I've setup a mirror of nettle at gitlab main server: https://gitlab.com/gnutls/nettle This has the advantage of using gnutls' CI servers. For that I attach the file needed to be present to enable using these servers. On every commit nettle will be tested for building + make check, in the available platforms and a mail will be sent to the author/committer. An example run can be seen at: https://gitlab.com/gnutls/nettle/builds?scope=finished regards, Nikos

2 7

Hashing with short input assertion question
by Tim Ruehsen 08 Jan '16

08 Jan '16

Hi, just experienced a crash (assertion) when using md5 on short input. test: md5.c:81: nettle_md5_digest: Assertion `length <= 16' failed. The code is struct md5_ctx md5; md5_init(&md5); md5_update(&md5, "moin", 4); md5_digest(&md5, 20, digest); My system is Debian SID (libnettle6:amd64 3.1.1-4). The example (http://www.lysator.liu.se/~nisse/nettle/nettle.html#Example) does not mention special handling for short input (nettle_sha1_digest() has a similar assert()). I searched the document for 'padding' but found nothing relevant. How should I proceed ? Pad with 0 bytes ? Is it reasonable to open a Debian bug suggesting to use -DNDEBUG ? IMO, these assertions needs to be disabled on a production system or replaced by proper error handling. It would be fine to have them in the respective -dbg (debugging) package though. Best regards, Tim

3 8

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

nettle-bugs January 2016