nettle-bugs

nettle-bugs@lists.lysator.liu.se

2191 discussions

Two issues found by Address sanitizer
by Tomáš Chvátal 21 Jun '15

21 Jun '15

Hello everybody, we at suse ran address sanitizer against libnettle and found two bugs [1][2]. The first one is easy to fix (simple off by one) and thus we already have the patch (see attachment 0001-...). The second one is about memory leaks, and it would be better if someone more aware of the source took a look wether and how to fix it. Cheers Tom [1] https://bugzilla.suse.com/show_bug.cgi?id=928328 [2] https://bugzilla.suse.com/show_bug.cgi?id=929109 PS: I am not subscribed so keep me in CC please.

2 1

Re: Bug#783699: nettle-dev is not Multi-Arch compatible
by nisse＠lysator.liu.se 28 May '15

28 May '15

[I'm cross-posting to the nettle list and a debian bug, so please take care when replying] The issue is that there are some differences in generated nettle header files depending on architecture and compiler version. Francois Gouget <fgouget(a)free.fr> writes: > Here is a proposed patch for the compiler version issue in nettle-stdint.h: > > $ cat debian/patches/multiarch.patch > --- a/aclocal.m4 > +++ b/aclocal.m4 > @@ -857,7 +857,7 @@ > fi # shortcircut to system "stdint.h" > # ------------------ PREPARE VARIABLES ------------------------------ > if test "$GCC" = "yes" ; then > -ac_cv_stdint_message="using gnu compiler "`$CC --version | head -1` > +ac_cv_stdint_message="using gnu compiler $CC" > else > ac_cv_stdint_message="using $CC" > fi If we go this path, maybe just drop the conditional and unconditionally print "using $CC"? I'm not sure about the reason for displaying the version, but I guess some older gcc versions did stdint and/or inttypes.h differently. If you have the time, it would be helpful to look at the latest version of AX_CREATE_STDINT_H (from autoconf archive) and see if it does anything differently. Nettle uses a pretty old version (which seems to work fine). > For GMP_NUMB_BITS here are some thoughts: You must understand that nettle defines GMP_NUMB_BITS only if configured with --enable-mini-gmp. This configuration is not intended to be compatible with anything else, and should never be installed on a normal debian system. It's intended for small embedded systems which needs to verify digital signatures, but which consider the real libgmp too large. > * Is it really necessary to install version.h? > IMHO the right place for other packages to figure out library versions is through > some scripting in the configure script rather than through a > header. This has been requested by users. Not everyone uses autoconf. And it's very common practice, I think both gmp and gnutls have similar version defines. > * GMP_NUMB_BITS is already defined by libgmp-dev in gmp.h. More > preceisely Exactly, and when not configuring with --enable-mini-gmp, that's the definitions which is used. Getting into the details, Nettle's definition of GMP_NUMB_BITS conceptually belongs in mini-gmp.h. However, mini-gmp is a standalone package which doesn't use autoconf. And it has to be a preprocessor *constant*, so definiting it like sizeof(unsigned long) * CHAR_BIT won't cut it, since the preprocessor doesn't understand sizeof. Therefore the definition, for the --enable-mini-gmp configuration which needs it, should be in a nettle include file. Then the cleanest way would be to omit the definition completely when not using --enable-mini-gmp. I haven't done that, because it would make the substitution logic harder, and because I was thinking that #define NETTLE_USE_MINI_GMP 0 #if NETTLE_USE_MINI_GMP # define GMP_NUMB_BITS 64 #endif is harmless whatever value appears in the second define. If it helps, I guess this could be changed into the architecture independent #define NETTLE_USE_MINI_GMP 0 #if NETTLE_USE_MINI_GMP # define GMP_NUMB_BITS the moon is made of green cheese #endif Opinions? Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

2 1

Version API
by Elliot Saba 12 May '15

12 May '15

Hello there, I saw the recent addition of the version #define's, which are great, but a runtime function that I can call to find out libnettle's API is essential for dynamic bindings. I maintain the Julia language bindings for Nettle <https://github.com/staticfloat/Nettle.jl> which loads the dynamic library and generates methods to use Nettle's cryptographic functions on the fly. This process does not use header files, it's similar to Python's ctypes functionality, and thus knowing which API version we're dealing with by only using the dynamic library itself is necessary. Most other projects have some method or other for determining this, as you guys have already discussed, but simply placing the information into a header file is not sufficient for this use case. Is this something it would be possible to support? Thanks! -E

2 5

nettle-3.1 transition and symbol versions
by nisse＠lysator.liu.se 02 May '15

02 May '15

Now we see some transition problems, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784009, and it's going to also hit other distributions than debian. Would it make sense to issue a nettle-2.7.2, which is nettle-2.7.1 + symbol versions? There's at least one bugfix which could be backported if we do another 2.7.x: 2014-06-30 Niels Möller <nisse(a)lysator.liu.se> * camellia-absorb.c: Include <limits.h>, needed for correct use of HAVE_NATIVE_64_BIT. Reported and debugged by Magnus Holmgren. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

2 1

ANNOUNCE: Nettle-3.1.1
by nisse＠lysator.liu.se 24 Apr '15

24 Apr '15

I've made another release of GNU Nettle, a low-level cryptographics library, to fix bugs reported for Nettle 3.1. The Nettle home page can be found at http://www.lysator.liu.se/~nisse/nettle/, and the manual at http://www.lysator.liu.se/~nisse/nettle/nettle.html. NEWS for the Nettle 3.1.1 release This release fixes a couple of non-critical bugs. Bug fixes: * By accident, nettle-3.1 disabled the assembly code for the secp_224r1 and secp_521r1 elliptic curves on all x86_64 configurations, making signature operations on those curves 10%-30% slower. This code is now re-enabled. * The x86_64 assembly implementation of gcm hashing has been fixed to work with the Sun/Oracle assembler. The shared library names are libnettle.so.6.1 and libhogweed.so.4.1, with sonames still libnettle.so.6 and libhogweed.so.4. It is intended to be fully binary compatible with nettle-3.1. Available at: https://ftp.gnu.org/gnu/nettle/nettle-3.1.1.tar.gz ftp://ftp.gnu.org/gnu/nettle/nettle-3.1.1.tar.gz http://www.lysator.liu.se/~nisse/archive/nettle-3.1.1.tar.gz ftp://ftp.lysator.liu.se/pub/security/lsh/nettle-3.1.1.tar.gz (soon) 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

Re: bug against .short value
by nisse＠lysator.liu.se 22 Apr '15

22 Apr '15

dongsheng zhang <dongsheng.zhang(a)oracle.com> writes: > Solaris doesn't take .short value, but instead only takes .value value. > We thus cannot compile the following file: > nettle-3.1/x86_64/gcm-hash8.asm I've checked in a fix. Can you try to check out https://git.lysator.liu.se/nettle/nettle.git and test if it solves the problem? You need to run the script ./.boostrap before configure and make. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 0

Re: bug against .short value
by nisse＠lysator.liu.se 21 Apr '15

21 Apr '15

dongsheng zhang <dongsheng.zhang(a)oracle.com> writes: > Solaris doesn't take .short value, but instead only takes .value value. > We thus cannot compile the following file: > nettle-3.1/x86_64/gcm-hash8.asm I see. From some testing, it seems that GNU as treats all of .short, .word, .value and .2byte as aliases, defining 16-bit constants. We currently use .short, and that breaks x86_64 builds using the Sun/Oracle assembler. Does anyone know which of ".word", ".value" and ".2byte" is more portable (.value sounds very unspecific to me)? I'd prefer to use a pseudo op supported by all relevant x86_64 assemblers, and not have to add a configure test for this. I think the relevant assemblers are GNU as (including older versions), Sun/Oracle as, and the assembler used with clang on freebsd. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 0

ANNOUNCE: Nettle-3.0
by nisse＠lysator.liu.se 13 Apr '15

13 Apr '15

I'm happy to announce a new version of GNU Nettle, a low-level cryptographics library. The Nettle home page can be found at http://www.lysator.liu.se/~nisse/nettle/. This release is dual licensed as LGPLv3 or later, or GPLv2 or later. See the manual for details. NEWS for the Nettle 3.0 release This is a major release, including several interface changes, and new features, some of which are a bit experimental. Feedback is highly appreciated. It is *not* binary (ABI) compatible with earlier versions. It is mostly source-level (API) compatible, with a couple of incompatibilities noted below. The shared library names are libnettle.so.5.0 and libhogweed.so.3.0, with sonames libnettle.so.5 and libhogweed.so.3. There may be some problems in the new interfaces and new features which really need incompatible fixes. It is likely that there will be an update in the form of a 3.1 release in the not too distant future, with small but incompatible changes, and if that happens, bugfix-only releases 3.0.x are unlikely. Users and applications which desire better API and ABI stability are advised to stay with nettle-2.7.x (latest version is now 2.7.1) until the dust settles. Interface changes: * For the many _set_key functions, it is now consider the normal case to have a fixed key size, with no key_size arguments. _set_key functions with a length parameter are provided only for algorithms with a truly variable keysize, and where it makes sense for backwards compatibility. INCOMPATIBLE CHANGE: cast128_set_key no longer accepts a key size argument. The old function is available under a new name, cast5_set_key. INCOMPATIBLE CHANGE: The function typedef nettle_set_key_func no longer accepts a key size argument. In particular, this affects users of struct nettle_cipher. * The nettle_cipher abstraction (in nettle-meta.h) is restricted to block ciphers only. The encrypt and decrypt functions now take a const argument for the context. INCOMPATIBLE CHANGE: nettle_arcfour, i.e., the nettle_cipher abstraction for the arcfour stream cipher, is deleted. INCOMPATIBLE CHANGE: New type, nettle_cipher_func, for the encrypt and decrypt fields of struct nettle_cipher. * New DSA interface, with a separate struct dsa_param to represent the underlying group, and generalized dsa_sign and dsa_verify functions which don't care about the hash function used. Limited backwards compatibility provided in dsa-compat.h. INCOMPATIBLE CHANGE: Declarations of the old interface, e.g., struct dsa_public_key, dsa_sha1_sign, etc, is moved to dsa-compat.h. INCOMPATIBLE CHANGE: The various key conversion functions, e.g., dsa_keypair_to_sexp, all use the new DSA interface, with no backwards compatible functions. INCOMPATIBLE CHANGE: dsa_generate_keypair also uses the new interface. dsa-compat.h declares a function dsa_compat_generate_keypair, implementing the old interface, and #defines dsa_generate_keypair to refer to this backwards compatible function. * New AES and Camellia interfaces. There are now separate context structs for each key size, e.g., aes128_ctx and camellia256_ctx, and corresponding new functions. The old interface, with struct aes_ctx and struct camellia_ctx, is kept for backwards compatibility, but might be removed in later versions. * The type of most length arguments is changed from unsigned to size_t. The memxor functions have their pointer arguments changed from uint8_t * to void *, for consistency with related libc functions. * For hash functions, the constants *_DATA_SIZE have been renamed to *_BLOCK_SIZE. Old names kept for backwards compatibility. Removed features: * The nettle_next_prime function has been deleted. Applications should use GMP's mpz_nextprime instead. * Deleted the RSAREF compatibility, including the header file rsa-compat.h and everything declared therein. * Also under consideration for removal is des-compat.h and everything declared therein. This implements a subset of the old libdes/ssleay/openssl interface for DES and triple-DES, and it is poorly tested. If anyone uses this interface, please speak up! Otherwise, it will likely be removed in the next release. Bug fixes: * Building with ./configure --disable-static now works. * Use GMP's allocation functions for temporary storage related to bignums, to avoid potentially large stack allocations. * Fixes for shared libraries on M$ Windows. New features: * Support for Poly1305-AES MAC. * Support for the ChaCha stream cipher and EXPERIMENTAL support for the ChaCha-Poly1305 AEAD mode. Specifications are still in flux, and future releases may do incompatible changes to track standardization. Currently uses 256-bit key and 64-bit nonce. * Support for EAX mode. * Support for CCM mode. Contributed by Owen Kirby. * Additional variants of SHA512 with output size of 224 and 256 bits. Contributed by Joachim Strömbergson. * New interface, struct nettle_aead, for mechanisms providing authenticated encryption with associated data (AEAD). * DSA: Support a wider range for the size of q and a wider range for the digest size. Optimizations: * New x86_64 assembly for GCM and MD5. Modest speedups on the order of 10%-20%. Miscellaneous: * SHA3 is now documented as EXPERIMENTAL. Nettle currently implements SHA3 as specified at the time Keccak won the SHA3 competition. However, the final standard specified by NIST is likely to be incompatible, in which case future releases may do incompatible changes to track standardization. * The portability fix for the rotation macros, mentioned in NEWS for 2.7.1, actually didn't make it into that release. It is included now. * cast128_set_key rewritten for clarity, also eliminating a couple of compiler warnings. * New command line tool nettle-pbkdf2. Available at: https://ftp.gnu.org/gnu/nettle/nettle-3.0.tar.gz ftp://ftp.gnu.org/gnu/nettle/nettle-3.0.tar.gz http://www.lysator.liu.se/~nisse/archive/nettle-3.0.tar.gz ftp://ftp.lysator.liu.se/pub/security/lsh/nettle-3.0.tar.gz (soon) Happy hacking, /Niels Möller -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

5 12

nettle-3.1rc1
by nisse＠lysator.liu.se 03 Apr '15

03 Apr '15

Available now, at http://www.lysator.liu.se/~nisse/archive/nettle-3.1rc1.tar.gz http://www.lysator.liu.se/~nisse/archive/nettle-3.1rc1.tar.gz.sig There's also a corresponding tag in the repo (except that the suffix "rc1" on the package version in configure.ac is not committed). All testing and proof-reading highly appreciated. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

4 12

Getting closer to nettle-3.1
by nisse＠lysator.liu.se 26 Mar '15

26 Mar '15

I think the remaining items on http://www.lysator.liu.se/~nisse/nettle/plan.html aren't very urgent, and can be postponed. Discussed recently, but not on that list, is mem_equalp (or whatever it should be called). That's also not very urgent. I plan to move NETTLE_USE_MINI_GMP from bignum.h to version.h, and drop bignum.h.in. It should be enough with one configure-generated header like that. It also has the advantage that version.h actually gets used during the build. That change touches a couple of files, so I don't want to check that in tonight. Anyway, I think it's time to get into final testing. I've done some tests on freebsd, revealing one real bug (triggered only when compiled with the ancient gcc version freebsd keeps in /usr/bin). And I've made some fixes to what gets included by make dist. I hope to be able to create a nettle-3.1rc1.tar.gz in a day or two. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

2 2

Jump to page:

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